summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* g_read_data() can return NULL, check for it.phk2005-03-181-0/+2
| | | | Found by: Coverity (ID#258)
* After rejecting the bio request early, return instead of panicing.phk2005-03-181-1/+3
| | | | Found by: Coverity (ID#450)
* Avoid null pointer dereference.phk2005-03-181-3/+2
|
* Fix a bad copy&paste mistake I made.phk2005-03-181-1/+1
| | | | Spotted by: truckman
* If mlx_attach() returns an error, don't free sc again.das2005-03-181-3/+1
| | | | | Spotted by: Ted Unangst using the Coverity Prevent static analysis tool Reviewed by: scottl
* Don't read past the end of pVDevice[]. (Previously, we would iteratedas2005-03-181-1/+1
| | | | | | | twice as many times as there were entries in the array.) Spotted by: Ted Unangst using the Coverity Prevent static analysis tool Reviewed by: scottl
* Don't write past the end of the VendorId field (and into the ProductIddas2005-03-181-1/+1
| | | | | | | field). Spotted by: Ted Unangst using the Coverity Prevent static analysis tool Reviewed by: scottl
* Use STAILQ in preference to SLIST for the resources. Insert new resourcesimp2005-03-187-21/+21
| | | | | | | | | last in the list rather than first. This makes the resouces print in the 4.x order rather than the 5.x order (eg fdc0 at 0x3f0-0x3f5,0x3f7 is 4.x, but 0x3f7,0x3f0-0x3f5 is 5.x). This also means that the pci code will once again print the resources in BAR ascending order.
* Split configure into 3 steps ala sparc64grehan2005-03-181-1/+20
| | | | Obtained from: iedowse, sparc64
* Autogenerate device listings for sr(4) and rc(4).brueffer2005-03-183-22/+8
| | | | MFC after: 3 days
* Further refine information about supported hardware (from the hardware notes).brueffer2005-03-181-4/+6
|
* - move supported hardware information into a HARDWARE sectionbrueffer2005-03-181-9/+10
| | | | | | | | - consistently capitalize RISCom - fix typo - bump .Dd MFC after: 3 days
* Fix the double rounding problem with subnormals, anddas2005-03-182-16/+36
| | | | remove the XXX comments, which no longer apply.
* - add a HARDWARE sectionbrueffer2005-03-181-10/+13
| | | | | | | | - correct a language nit - remove outdated FILES section - bump .Dd MFC after: 3 days
* Reflect devnode naming change from /dev/ubser?.? to /dev/ttyy??ticso2005-03-181-2/+2
|
* Add missing prototypes for fma() and fmaf(), and remove an inaccuratedas2005-03-181-1/+2
| | | | comment.
* fix aio+kq... I've been running ambrisko's test program for much longerjmg2005-03-183-10/+18
| | | | | | | | | | | | w/o problems than I was before... This simply brings back the knote_delete as knlist_delete which will also drop the knote's, instead of just clearing the list and seeing _ONESHOT... Fix a race where if a note was _INFLUX and _DETACHED, it could end up being modified... whoopse.. MFC after: 1 week Prodded by: ambrisko and dwhite
* Use the correct variable name for the description of multi-volumemurray2005-03-182-6/+6
| | | | support in cdrom.inf. Should be CD_VOLUME.
* Recover gracefully if the user puts in the wrong CD volume after beingmurray2005-03-181-5/+3
| | | | | | prompted to insert another CD for a package. MFC After: 3 days
* Bring back some of the cleanups and fixes jmg did in the TS7200 port.cognet2005-03-171-18/+16
|
* initialize pp->p_sc so it can be referenced later.ticso2005-03-172-20/+34
| | | | | | dynamicaly allocate the per port array. allow up to 32 serials per USB device. ask the device for correct pipe sizes.
* Introduce a general name for the previously cmbat-only ioctls. It has thenjl2005-03-172-20/+22
| | | | | | | same value as the previous ioctls so no binary change. Also, make a few style changes to reduce diffs to my tree. Loosely based on code from: Hans Petter Selasky
* Remove the 'usbd' keyword (it isn't necessary for mixer). Also, usenjl2005-03-171-1/+1
| | | | | | | BEFORE instead of REQUIRE. Probably ok by: jhb MFC after: 3 days
* Make the fenv.h routines work for programs that use SSE fordas2005-03-172-85/+262
| | | | | | | | | | | | | | | | | | | | | | | | | floating-point arithmetic on i386. Now I'm going to make excuses for why this code is kinda scary: - To avoid breaking the ABI with 5.3-RELEASE, we can't change sizeof(fenv_t). I stuck the saved mxcsr in some discontiguous reserved bits in the existing structure. - Attempting to access the mxcsr on older processors results in an illegal instruction exception, so support for SSE must be detected at runtime. (The extra baggage is optimized away if either the application or libm is compiled with -msse{,2}.) I didn't run tests to ensure that this doesn't SIGILL on older 486's lacking the cpuid instruction or on other processors lacking SSE. Results from running the fenv regression test on these processors would be appreciated. (You'll need to compile the test with -DNO_STRICT_DFL_ENV.) If you have an 80386, or if your processor supports SSE but the kernel didn't enable it, then you're probably out of luck. Also, I un-inlined some of the functions that grew larger as a result of this change, moving them from fenv.h to fenv.c.
* Initialize the mxcsr properly, so the initial value in a process isn'tdas2005-03-172-0/+11
| | | | just the value that was left over from some other application.
* Fix typo in comments (spell Linux correctly)emax2005-03-171-1/+1
| | | | | Submitted by: Markus Brueffer < markus at brueffer dot de > MFC after: 3 days
* When locking a MTX_SPIN, one needs to use mtx_lock_spin.imp2005-03-171-5/+7
| | | | | | Lock the timeout routine as well. Submitted by: bde
* Split configure() into 3 separate steps like we do on otheriedowse2005-03-171-3/+23
| | | | | architectures. This makes it possible to insert hooks before and after the device attachment step.
* New release notes: BIND 9.3.1.hrs2005-03-172-0/+6
|
* I keep forgetting that I wanted the customize logs collected too.phk2005-03-171-4/+6
| | | | Reminded by: Lennart Sorth, Andrea Campi and others.
* Defer boot-time exploration of USB busses until all devices in theiedowse2005-03-171-1/+30
| | | | | | | | | | | | | system have been attached, but no later. This ensures that we do not explore ohci or uhci busses before the companion echi controller has been initialised, so it should fix the problem of multi-speed USB devices getting attached as USB 1 devices first and then re-attached as USB 2. Some further changes are needed on architectures that do not currently allow hooks to be inserted before configure_final() - alpha, ia64, powerpc and sparc64. On these architectures the exploration will now be delayed until the usb kthread runs.
* add m_copyup function.. This can be used to help make our ip stack lessjmg2005-03-173-0/+78
| | | | | | | | | | alignment restrictive, and help performance on some ethernet cards which currently copy the entire packet a couple bytes to get the packet aligned properly... Wordsmithing by: dwhite Obtained from: NetBSD (code only) I'll clean it up later: rwatson
* eisa attachment is safe to be in this module, both on eisa andimp2005-03-171-1/+1
| | | | non-eisa configured kernels.
* Now that the Adaptec 2842 has its own probe routine, no need to haveimp2005-03-171-3/+1
| | | | a comment saying its probe routine needs to be fixed.
* Style(9) pass before some planned larger changes.imp2005-03-171-91/+61
| | | | | | | o return (foo); o if (a == NULL) in preference to if (!a) o () and {} reduction o minor indentation fixes
* A further step on the journey of meaking panics and debugging more reliable:rwatson2005-03-171-2/+3
| | | | | | | | | | | | | | | in the window between the beginning of panic() and entering the debugger, it's possible to receive interrupts. If we receive an interrupt, don't preempt if panicstr != NULL, as the system is in the process of failing, and the preempting thread is likely to stumble over the failure. The typical scenario is during the printf() in panic() prior to entering the debugger, but when running with a slower console type such as serial console. It could be that the panic string should be passed to the debugger to print, so that it can run from the debugger's environment rather than a regular kernel printf. Glanced at by: jhb
* Also remember to set the fsid here.phk2005-03-171-0/+1
|
* Forgot to replace code to set fsid in vop_getattr.phk2005-03-172-0/+2
|
* Do not try to free non allocated memory in error case.bz2005-03-174-26/+122
| | | | | | | | | | | | | | | | Do our best to plug some memory leaks (VPD data, jumbo memory buffer,...). Log if we cannot free because memory still in use[1]. Change locking to avoid ''acquiring duplicate lock of same type: "network driver"'' and potential deadlock. Also seems to fix LOR #063. [1] This change does not solve problems if buffers are still in use when unloading if_sk.ko. There is ongoing work which will address jumbogram allocations in a more general way. PR: kern/75677 (with changes, no mii fixes in here) Tested by: net, Antoine Brodin (slightly different version) Approved by: rwatson (mentor) MFC after: 5 days
* * Lower interrupt moderation timer 200->100.bz2005-03-174-2/+130
| | | | | | | | Obtained from: NetBSD if_sk.c rev. 1.11 * Make interrupt moderation configurable via sysctl/tuneable. PR: kern/41220 Approved by: rwatson (mentor)
* * Improve chip identification.bz2005-03-174-64/+284
| | | | | | | | | | | Obtained from: NetBSD if_sk.c rev. 1.11 * Take PHY out of reset for Yukon Lite Rev. A3. Submitted by: postings on net@ in thread "skc0: no PHY found", 2005-02-22 Tested by: net Approved by: rwatson (mentor) MFC after: 5 days
* * When adding/deleting multicast addresses, only whack the address filterbz2005-03-172-12/+30
| | | | | | | | | | | | | | | | if the interface is marked RUNNING. Obtained from: NetBSD if_sk.c rev. 1.12 * Don't initialize the card (and start an autonegotiation) every time the IP address changes. Makes 'dhclient sk0' invocations way faster and more consistant. i.e. one DHCPREQUEST elicits the DHCPACK. Obtained from: OpenBSD if_sk.c rev. 1.56 * Additional locking changes in sk_ioctl. PR: kern/61296 should see improvements by the last two. Approved by: rwatson (mentor) MFC after: 5 days
* Releasing TX/RX descriptor dmamaps during device detachment instead ofavatar2005-03-171-5/+4
| | | | | | | | | | | | | | | | doing that in bfe_stop(). This should fix a panic recently reported on -current occuring when taking device down then up. In the original implementation, an "ifconfig bfe0 down" triggers bfe_stop(), which also destroys all TX/RX descriptor dmamaps. Hence the subsequent "ifconfig bfe0 up" would force the device to use those already-released dmamap and thus panic the kernel. PR: kern/77804 Submitted by: Frank Mayhar <frank at exit dot com> Reviewed by: dmlb, sam (mentor) Tested by: Phil <pcasidy at casidy dot com>, myself MFC after: 1 week
* Kill MAJOR_AUTOphk2005-03-173-11/+3
|
* Prepare for the final onslaught on devices:phk2005-03-174-13/+19
| | | | | | | | Move uid/gid/mode from cdev to cdevsw. Add kind field to use for devd(8) later. Bump both D_VERSION and __FreeBSD_version
* - Don't lock the vnode interlock in vm_object_set_writeable_dirty() ifjeff2005-03-171-2/+4
| | | | | | we've already set the object flags. Reviewed by: alc
* - Lock the clearing of v_data so it is safe to inspect it with thejeff2005-03-171-1/+7
| | | | | | interlock. Sponsored by: Isilon Systems, Inc.
* - Lock the clearing of v_data in ufs_reclaim() to prevent a pagefaultjeff2005-03-171-1/+7
| | | | | | in ffs_lock() when it acesses v_data without the vnlock. Sponsored by: Isilon Systems, Inc.
* There is no longer a KNOWN_DEFECTS file, so don't try to install it.dougb2005-03-171-1/+1
|
* Remove unused variable.phk2005-03-171-6/+0
| | | | Detected by: Coverity (ID#704)
OpenPOWER on IntegriCloud