summaryrefslogtreecommitdiffstats
path: root/sys
Commit message (Collapse)AuthorAgeFilesLines
* fix comment and whitespacesam2006-02-131-3/+2
|
* fix merge botch (duplicate processing of cabq for old cards)sam2006-02-131-1/+0
|
* Tie the ipmi driver into the i386/amd64 builds.ambrisko2006-02-133-0/+9
|
* Use a wildcard unit (-1) to device_find_child() in our identify routine tojhb2006-02-131-1/+1
| | | | match the wildcard unit passed to BUS_ADD_CHILD().
* Don't conflict with the DEBUG define.ambrisko2006-02-131-1/+1
|
* Add a reset of the AHCI machinery to the ICH6/ICH7 support.sos2006-02-131-0/+12
| | | | This should fix the missed devices on some systems.
* In order to speed up process suspension on MP machine, send IPI todavidxu2006-02-132-31/+34
| | | | | | remote CPU. While here, abstract thread suspension code into a function called sig_suspend_threads, the function is called when a process received a STOP signal.
* On component state change to ACTIVE don't forget to update metadata.pjd2006-02-122-6/+4
| | | | MFC after: 3 days
* Use time_uptime instead of time_second, as the latter may go backwards.pjd2006-02-122-8/+8
| | | | | Suggested by: ru MFC after: 3 days
* Typo: s/fint/find/glebius2006-02-121-1/+1
|
* Add USB polling calls to umass_cam_poll(). This appears to be enoughiedowse2006-02-121-7/+3
| | | | | to make kernel crash dumps to umass devices work, at least in some cases.
* avoided the use of purged address structure when an address becameume2006-02-121-2/+1
| | | | | | | | | | | invalid in nd6_timer(). PR: kern/93170 Reported by: kris Submitted by: JINMEI Tatuya <jinmei__at__isl.rdc.toshiba.co.jp> Confirmed by: kris Obtained from: KAME MFC after: 2 days
* Improve consistency of return() style.rwatson2006-02-121-8/+8
| | | | MFC after: 3 days
* In quotaoff(), lock the vnode instead of asserting it when manipulatingrwatson2006-02-121-1/+2
| | | | | | | v_vflags. MFC after: 1 week Submitted by: Antoine Brodin <antoine at brodin at laposte dot net>
* Fix possible DMA leak and locking violation especiallyariff2006-02-121-14/+15
| | | | | | | during suspend <-> resume and module load <-> unload. PR: kern/92764 MFC after: 3 days
* Give the asr softc list global a proper name.scottl2006-02-121-5/+5
|
* Allow to set kern.geom.raid3.disconnect_on_failure from loader.conf.pjd2006-02-121-0/+2
| | | | MFC after: 3 days
* Add stub AUE_EACCESS entry.rwatson2006-02-111-0/+1
| | | | Obtained from: TrustedBSD Project
* Initialize user process audit ID to AU_DEFAUDITID so that init andrwatson2006-02-111-0/+1
| | | | | | its pre-authentication children are covered by naflags. Obtained from: TrustedBSD Project
* Instead of asserting the vnode lock before manipulating v_vflag, acquirerwatson2006-02-111-1/+2
| | | | | | | it and drop it afterwards. Found by: kris MFC after: 1 week
* Don't count output bytes twice (the byte accouting is doneru2006-02-111-7/+4
| | | | | | in if.c). Count output errors. MFC after: 3 days
* Correct the spinlock nesting of the idle thread of the APs before wemarcel2006-02-111-12/+10
| | | | | | | | | | save the MCA state of the AP. Saving the MCA state of the AP requires us to allocate memory, which uses sleep locks. Now that we correct the spinlock nesting of the AP without having schedlock, avoid calling spinlock_exit(). Instead call critical_exit() and manually clear the MD spinlock count. MFC after: 3 days
* Skip per-cpu caches associated with absent CPUs when generating arwatson2006-02-111-0/+2
| | | | | | memory statistics record stream via sysctl. MFC after: 3 days
* - Add kern.geom.raid3.disconnect_on_failure sysctl/tunnable (default to 1pjd2006-02-112-31/+76
| | | | | | | | | | | | | | | to preserve currect behaviour). When set to 0, components are not disconnected - graid3 will try to still use them (only first error will be logged). This is helpful when we have two broken components, but in different places, so actually all data is available. Such buggy component will be visible in 'graid3 list' output with flag BROKEN. - Never disconnect the last valid component. If we detect errors there we will just pass them up. This wasn't reasonable to deny access to the whole provider because of one broken sector. Prodded by: ru MFC after: 3 days
* - Add kern.geom.mirror.disconnect_on_failure sysctl/tunnable (default to 1pjd2006-02-112-10/+47
| | | | | | | | | | | | | | | to preserve currect behaviour). When set to 0, components are not disconnected - gmirror will try to still use them (only first error will be logged). This is helpful when we have two broken components, but in different places, so actually all data is available. Such buggy component will be visible in 'gmirror list' output with flag BROKEN. - Never disconnect the last valid component. If we detect errors there we will just pass them up. This wasn't reasonable to deny access to the whole provider because of one broken sector. Prodded by: ru MFC after: 3 days
* Correct typo. 'fbp' is NULL here so this will result in a panic.pjd2006-02-111-1/+1
| | | | MFC after: 3 days
* Mark array as CLEAN when there are no write requests inpjd2006-02-112-101/+53
| | | | | | | | kern.geom.raid3.idletime seconds. Write, not any requests. Mark array as clean immediatelly on last write close. Prodded by: ru MFC after: 3 days
* Mark array as CLEAN when there are no write requests inpjd2006-02-112-103/+54
| | | | | | | | kern.geom.mirror.idletime seconds. Write, not any requests. Mark array as clean immediatelly on last write close. Prodded by: ru MFC after: 3 days
* Teach geli how to load keyfiles before root file system is mounted.pjd2006-02-111-19/+106
| | | | | | | | | | | | | | | | | | | | | | An example entries for loader.conf to make it possible: geli_da0_keyfile0_load="YES" geli_da0_keyfile0_type="da0:geli_keyfile0" geli_da0_keyfile0_name="/boot/keys/da0.key0" geli_da0_keyfile1_load="YES" geli_da0_keyfile1_type="da0:geli_keyfile1" geli_da0_keyfile1_name="/boot/keys/da0.key1" geli_da0_keyfile2_load="YES" geli_da0_keyfile2_type="da0:geli_keyfile2" geli_da0_keyfile2_name="/boot/keys/da0.key2" geli_da1s3a_keyfile0_load="YES" geli_da1s3a_keyfile0_type="da1s3a:geli_keyfile0" geli_da1s3a_keyfile0_name="/boot/keys/da1s3a.key" Thanks for jhb and kan who showed me the right direction. MFC after: 3 days
* Check rootvnode variable to see if we still want to ask for passphrase onpjd2006-02-112-29/+3
| | | | | | boot. Other methods just don't work properly. MFC after: 3 days
* CPU time accounting speedup (step 2)phk2006-02-1112-88/+217
| | | | | | | | | | | | | | | | | | | Keep accounting time (in per-cpu) cputicks and the statistics counts in the thread and summarize into struct proc when at context switch. Don't reach across CPUs in calcru(). Add code to calibrate the top speed of cpu_tickrate() for variable cpu_tick hardware (like TSC on power managed machines). Don't enforce monotonicity (at least for now) in calcru. While the calibrated cpu_tickrate ramps up it may not be true. Use 27MHz counter on i386/Geode. Use TSC on amd64 & i386 if present. Use tick counter on sparc64
* Use the correct address for the ohci device.imp2006-02-111-1/+1
|
* Use ETHER_ADDR_LEN rather than 6.imp2006-02-111-1/+1
|
* Improve the memory resoruce allocation and usage during the probe.imp2006-02-111-8/+29
| | | | I've had these improvements in my tree for almost a year now...
* Use the release version as a floor, not an exact match. Add comment to thatimp2006-02-111-1/+4
| | | | | effect and draw attention to the fact that the list has stronger ordering requirements than before.
* Give ohci_intr a proper return value. In FreeBSD, this is void. Removeimp2006-02-113-7/+7
| | | | now-redundant cast on establishing the interrupt.
* Update the keyspan product list from NetBSD.imp2006-02-111-7/+28
|
* Do initial cut of SAS HBA support. These controllers (106X) seem to supportmjacob2006-02-115-223/+587
| | | | | | | | | | | | | | | | automatically both SATA and SAS drives. The async SAS event handling we catch but ignore at present (so automagic attach/detach isn't hooked up yet). Do 64 bit PCI support- we can now work on systems with > 4GB of memory. Do large transfer support- we now can support up to reported chain depth, or the length of our request area. We simply allocate additional request elements when we would run out of room for chain lists. Tested on Ultra320, FC and SAS controllers on AMD64 and i386 platforms. There were no RAID cards available for me to regression test. The error recovery for this driver still is pretty bad.
* Add an OpenIPMI mostly compatible driver. This driver was developedambrisko2006-02-106-0/+2209
| | | | | | | | | | | | | | | | | | | | | | | | | | | to work with ipmitools. It works with other tools that have an OpenIPMI driver interface. The port will need to get updated to used this. I have not implemented the IPMB mode yet so ioctl's for that don't really do much otherwise it should work like the OpenIPMI version. The ipmi.h definitions was derived from the ipmitool header file. The bus attachments are done for smbios and pci/smbios. Differences in bus probe order for modules/static are delt with. ACPI attachment should be done. This drivers registers with the watchdod(4) interface Work to do: - BT interface - IPMB mode This has been tested on Dell PE2850, PE2650 & PE850 with i386 & amd64 kernel. I will link this into the build on next week. Tom Rhodes, helped me with the man page. Sponsored by: IronPort Systems Inc. Inspired from: ipmitool & Linux
* Update for rev 0.9.16.16 hal:sam2006-02-102-29/+291
| | | | | | | | | | | | o add dfs+radar hooks; DFS is presently disabled in the hal o channel and mode handling changes o various api changes o be more aggressive about iq calibration settling so ap mode operation is better immediately after startup o rfkill/rfsilent sysctl support o tpc ack/cts sysctl support MFC after: 2 weeks
* resolve merge conflictssam2006-02-101-4/+6
| | | | MFC after: 2 weeks
* This commit was generated by cvs2svn to compensate for changes in r155511,sam2006-02-1065-69379/+109156
|\ | | | | | | which included commits to RCS files with non-trunk default branches.
| * Version 0.9.16.16:sam2006-02-1066-69383/+109162
| | | | | | | | | | | | | | | | | | o new chip support o new platforms: powerpc-be-elf, sparc64-be-elf, and alpha-elf (alpha is untested, others are known to work) o many fixes and improvements MFC after: 2 weeks
* | Cleaned the memory initialization up, moved some defines from the framebufferrink2006-02-103-20/+18
| | | | | | | | | | | | | | to an include file. Reviewed by: imp Approved by: imp (mentor)
* | Bump the MODULE_VERSION for HEAD, as the vlan(4) API is different inemaste2006-02-101-1/+1
| | | | | | | | | | | | | | RELENG_6, and would require a lower version number. Requested by: glebius Approved by: rwatson (mentor)
* | Correctly set MNTK_MPSAFE flag from the lower vnode's mount rather thanjhb2006-02-101-1/+1
| | | | | | | | | | | | | | | | always turning it on along with any flags set in the lower mount. Tested by: kris Reviewed by: jeff MFC after: 3 days
* | Test before modifying p_sflag to avoid unconditionally cache linedavidxu2006-02-101-2/+4
| | | | | | | | ping-pong on SMP.
* | Avoid frobbing IFF_UP at any cost (which is close toyar2006-02-101-2/+0
| | | | | | | | | | | | | | | | zero in this case.) A kernel driver has IFF_DRV_RUNNING at its full disposal while IFF_UP may be toggled only by humans or their daemonic deputies from the userland. MFC after: 3 days
* | Call thread_stopped in thr_exit to notify parent that the child processdavidxu2006-02-101-0/+1
| | | | | | | | is now fully stopped, this was already in kse_exit().
* | pad for future statisticssam2006-02-091-0/+1
| | | | | | | | MFC after: 2 weeks
OpenPOWER on IntegriCloud