summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Return EIO if vdev->v_phys_read is NULL.mm2010-08-091-0/+3
| | | | | | | | | This fixes booting from a ZFS mirror with a unavailable primary device. PR: kern/148655 Reviewed by: avg Approved by: delphij (mentor) MFC after: 3 days
* It seems some old Sundace(now IC Plus Corp.) controllers do notyongari2010-08-091-7/+20
| | | | | | | | | | | | | | | | | | like memory mapped register access. Typical problem from the issue was MII access returned unreliable values. I'm not sure this comes from lack of register flushing in MII access after accessing STE_PHYCTL register though. To address the issue, read hints data that controls which type of memory mapping should be used in driver. ste(4) still prefers memory mapping to io mapping but honor hints entered by user except for controllers that have problems with memory mapping. The hint to use iomapping could be given by adding the following line to /boot/device.hints file. hint.ste.0.prefer_iomap="1" PR: kern/149285 MFC after: 5 days
* Add a multipath oriented test.mjacob2010-08-093-1/+436
|
* The r208165 fixed a bug related to unsigned integer overflowing for theattilio2010-08-091-4/+1
| | | | | | | | | | | | | | | | number of CPUs detection. However, that was not mention at all, the problem was not reported, the patch has not been MFCed and the fix is mostly improper. Fix the original overflow (caused when 32 CPUs must be detected) by just using a different mathematical computation (it also makes more explicit the size of operands involved, which is good in the moment waiting for a more complete support for a large number of CPUs). PR: kern/148698 Submitted by: Joe Landers <jlanders at vmware dot com> Tested by: gianni MFC after: 10 days
* Back out r210975, which changed documentation to match the now backed-outjamie2010-08-081-5/+5
| | | | r210974.
* Back out r210974. Any convenience of not typing "persist" is outweighedjamie2010-08-081-2/+6
| | | | by the possibility of unintended partially-formed jails.
* Remove unnecessary duplicate letters in mksyntax.c,jilles2010-08-081-2/+2
| | | | the table elements would just be overwritten twice.
* The PL2302X can support any baud rate <= 6Mbps, allow any rate to be set.gavin2010-08-081-12/+20
| | | | | | PR: usb/128324 Submitted by: Mike Durian <durian shadetreesoftware.com> (original patch) MFC after: 2 weeks
* Don't pass sizeof(u_int) to an argument of SYSCLT_PROC that ends up notdwmalone2010-08-082-2/+2
| | | | being used.
* sh: Add more testcases for ${var:-word}.jilles2010-08-081-0/+38
| | | | | | Whether POSIX requires these is unclear. They pass with 8-stable sh as well.
* Merge r114010 of head/usr.bin/login/login.c into PicoBSD's login.c:gavin2010-08-081-1/+2
| | | | | | | | Correct the login.conf variable name used for obtaining the login prompt. PR: conf/44717 (indirectly) Spotted by: gcooper MFC after: 1 week
* Correct two error messages to match the failure they are reporting.gavin2010-08-081-2/+2
| | | | MFC after: 1 week
* Wrap some sun4u-only symbols.marius2010-08-081-5/+3
|
* - As it is not possible for sched_bind(9) to context switch withmarius2010-08-085-34/+113
| | | | | | | | | | | | td_critnest > 1 when not already running on the desired CPU read the TICK counter of the BSP via a direct cross trap request in that case instead. - Treat the STICK based timecounter the same way as the TICK based one regarding its quality and obtaining the counter value from the BSP. Like the TICK timers the STICK ones also are only synchronized during their startup (which might not result in good synchronicity in the first place) but not afterwards and might drift over time, causing problems when the time is read from different CPUs (see r135972).
* loadandclear() for PTEs are not needed on MIPS. The PTEs are softwarejchandra2010-08-081-3/+9
| | | | | | managed and we already take pmap lock for PTE operations(see r210922) Reviewed by: alc
* Add a termcap entry for rxvt-256color.gavin2010-08-081-0/+3
| | | | | | PR: conf/147726 Submitted by: Sterling (Chip) Camden <sterling camdensoftware.com> MFC after: 2 weeks
* License ACK is not required for the wpifw module nor when buildingbschmidt2010-08-081-1/+1
| | | | | | | | it into the kernel. PR: conf/148758 Submitted by: Joe Talbott <josepht at dragonflybsd.org> MFC after: 3 days
* Remove unneeded struct timezone passed to gettimeofday().ed2010-08-081-5/+3
|
* Small style(9) fix: use tabs instead of spaces.ed2010-08-081-8/+8
|
* Address an edge condition that we found at work, where the carp(4)delphij2010-08-081-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | interface goes to issue LINK_UP, then LINK_DOWN, then LINK_UP at cold boot. This behavior is not observed when carp(4) interface is created slightly later, when the underlying interface is fully up. Before this change what happen at boot is roughly: - ifconfig creates em0 interface; - ifconfig clones a carp device using em0; (em0's link state is DOWN at this point) - carp state: INIT -> BACKUP [*] - carp state: BACKUP -> MASTER - [Some negotiate between em0 and switch] - em0 kicks up link state change event (em0's link state is now up DOWN at this point) - do_link_state_change() -> carp_carpdev_state() - carp state: MASTER -> INIT (via carp_set_state(sc, INIT)) [+] - carp state: INIT -> BACKUP - carp state: BACKUP -> MASTER At the [*] stage, em0 did not received any broadcast message from other node, and assume our node is the master, thus carp(4) sets the link state to "UP" after becoming a master. At [+], the master status is forcely set to "INIT", then an election is casted, after which our node would actually become a master. We believe that at the [*] stage, the master status should remain as "INIT" since the underlying parent interface's link state is not up. Obtained from: iXsystems, Inc. Reported by: jpaetzel MFC after: 2 months
* Do not build real mode emulator for i386. We use VM86 again since r210877.jkim2010-08-082-3/+5
|
* Don't use struct timezone.ed2010-08-081-4/+2
| | | | | The timezone structure acquired by gettimeofday() is not used at all. Just remove it.
* Remove unneeded use of struct timezone.ed2010-08-082-6/+4
| | | | | We can safely call gettimeofday() without passing a struct timezone. We're not using it at all.
* This isn't WARNS=6 safe. It fails to build on mips. Retore oldimp2010-08-081-0/+2
| | | | WARNS?=3 until that's resolved.
* Fix -R when used with -p. Previously, thekientzle2010-08-083-4/+18
| | | | | | | | | | uname and gname weren't overwritten, so the disk restore would use those to lookup the original uid/gid again. Clearing the uname and gname prevents this. Reported by: swell.k MFC after: 7 days
* Cache PCIY_PMG and PCIY_EXPRESS capability pointer to softc and useyongari2010-08-082-10/+17
| | | | it instead of calling pci_find_extcap().
* Remove unnecessary assignment.yongari2010-08-081-1/+0
|
* Always disable ASPM L0s and enable L1 before entering into WOLyongari2010-08-081-12/+10
| | | | | | suspend state. Also disable master clock after PHY power down, this is supposed to save more power. The master clock should be enabled if WOL is active.
* - Introduce a cpu_ipi_single() function pointer in order to send IPIsmarius2010-08-082-25/+176
| | | | | | | | | | to single CPUs more efficiently with Cheetah(-class) and Jalapeno CPUs. Besides being used to implement the ipi_cpu() introduced in r210939, cpu_ipi_single() will also be used internally by the sparc64 MD code. - Factor out the Jalapeno support from the Cheetah IPI send functions in order to be able to more easily and efficiently implement support for more than 32 target CPUs as well as a workaround for Cheetah+ erratum 25 for the latter.
* For CPUs which ignore TD_CV and support hardware unaliasing don'tmarius2010-08-086-60/+80
| | | | | bother doing page coloring. This results in a small but measurable performance improvement in buildworld times.
* Do not touch CMB TX threshold register when CMB is not used.yongari2010-08-071-3/+3
| | | | Note, alc(4) does not use CMB at all due to silicon bug.
* Controller does not seem to support more than 1024 bytes DMA burst.yongari2010-08-071-0/+4
| | | | Limit DMA burst size to be less than or equal to 1024 bytes.
* Marvell model number 0x06 is 88E1101 PHY.yongari2010-08-072-2/+2
|
* jh pointed out that src/usr.sbin already has a globalolli2010-08-071-2/+0
| | | | | | | | WARNS=6 setting in HEAD (unlike stable/8), so it's best to remove the line entirely. Pointed out by: jh Approved by: des (mentor)
* To help with sequential read UFS performance on modern systems, increaseivoras2010-08-071-1/+1
| | | | | | | | | | | | | | the vfs.read_max default. For most systems this means going from 128 KiB to 256 KiB, which is still very conservative and lower than what most other operating systems use, but as a sane default should not interfere much with existing systems. For systems with RAID volumes and/or virtualization envirnments, where read performance is very important, increasing this sysctl tunable to 32 or even more will demonstratively yield additional performance benefits. If MAXPHYS ever gets bumped up, it will probably be a good idea to slave read_max to it.
* Fix a bug where MSG_TRUNC was not returned in all necessary cases fortuexen2010-08-071-1/+6
| | | | | | | | | SOCK_DGRAM socket. MSG_TRUNC was only returned when some mbufs could not be copied to the application. If some data was left in the last mbuf, it was correctly discarded, but MSG_TRUNC was not set. Reviewed by: bz MFC after: 3 weeks
* Add a keymap for the Swiss-German Macbook keyboard.gavin2010-08-073-0/+141
| | | | | | | PR: conf/139997 Submitted by: Andreas Tobler <andreast fgznet.ch> MFC after: 2 weeks Committed from: Bugathon #7
* syslogd(8) already supports *sending* log messages to non-olli2010-08-073-9/+60
| | | | | | | | | | | | | | standard ports, but it can't *receive* them (port 514 is hardcoded). This commit adds that missing feature. (NB: I actually needed this feature for a server farm where multiple jails run with shared IP addresses, and every jail should have its own syslogd process.) As a side effect, syslogd now compiles with WARNS=6. Approved by: des (mentor) MFC after: 3 weeks
* Sync the list of devices supported by uslcom(4) with NetBSD, Linux, OpenBSDgavin2010-08-072-4/+113
| | | | | | | | | | | | | | | and BeOS. The devices supported by uslcom(4) are now in sync with: NetBSD src/sys/dev/usb/uslsa.c 1.11 OpenBSD src/sys/dev/usb/uslcom.c 1.20 Linux source/drivers/usb/serial/cp210x.c from kernel 2.6.35 BeOS usb_serial/driver.c 1.32 Two vendor/product IDs from Linux have not been added to uslcom(4): SILABS SAEL - This device has special code in u3g to support it SILABS GSM2228 - I suspect this should also be covered by u3g(4). MFC after: 1 week
* Sort this file a little better: the vendors are supposed to be sorted bygavin2010-08-071-10/+9
| | | | | | | | vendor ID in the vendor section, and by symbolic name in the product section. Products are sorted by product ID. While here, get rid of a duplicate Microsoft Mouse entry, revealed by sorting. MFC after: 1 week
* Document the MEXTADD macro.des2010-08-071-2/+55
| | | | MFC after: 2 weeks
* Prefer struct sysentvec sv_psstrings to hardcoding FREEBSD32_PS_STRINGSkib2010-08-073-10/+13
| | | | | | in the compat32 code. Use sv_usrstack instead of FREEBSD32_USRSTACK as well. MFC after: 1 week
* Add compat32 definition for (old) struct ostat.kib2010-08-071-0/+18
| | | | MFC after: 1 week
* Clean up the style and markup of the paragraph on fractional wait intervals.yar2010-08-071-4/+6
| | | | MFC after: 3 days
* Properly spell and mark up the name of kern.hz.yar2010-08-071-2/+3
| | | | MFC after: 3 days
* Move the sentences telling the defaults for -c and -wyar2010-08-071-6/+6
| | | | | | | to where they belong. Previously they were misplaced, i.e., swapped. MFC after: 3 days
* In FreeBSD we use 'jailed' property.pjd2010-08-071-1/+1
| | | | MFC after: 2 weeks
* Fix typo in comment.joel2010-08-072-2/+2
|
* Properly bounds check ioctl/pioctl data arguments for Coda:rwatson2010-08-073-3/+12
| | | | | | | | | | | | | | | | | | | | | | 1. Use unsigned rather than signed lengths 2. Bound messages to/from Venus to VC_MAXMSGSIZE 3. Bound messages to/from general user processes to VC_MAXDATASIZE 4. Update comment regarding data limits for pioctl Without (1) and (3), it may be possible for unprivileged user processes to read sensitive portions of kernel memory. This issue is only present if the Coda kernel module is loaded and venus (the userspace Coda daemon) is running and has /coda mounted. As Coda is considered experimental and production use is warned against in the coda(4) man page, and because Coda must be explicitly configured for a configuration to be vulnerable, we won't be issuing a security advisory. However, if you are using Coda, then you are advised to apply these fixes. Reported by: Dan J. Rosenberg <drosenberg at vsecurity.com> Obtained from: NetBSD (Christos Zoulas) Security: Kernel memory disclosure; no advisory as feature experimental MFC after: 3 days
* Protect shared palette and state buffer with a mutex. Remove defunctjkim2010-08-071-14/+27
| | | | spltty() calls while I am here.
OpenPOWER on IntegriCloud