Current problem reports assigned to you
Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description --- o [2005/08/10] usb/84750 usb [hang] 6-BETA2 reboot/shutdown with root_ o [2006/01/11] usb/91629 usb usbd_abort_pipe() may result in infinite 2 problems total. Serious problems S Submitted Tracker Resp. Description --- o [2002/07/19] usb/40792 usb signals lead to data loss on device ugen o [2002/12/10] usb/46176 usb [panic] umass causes kernel panic if devi o [2002/12/19] i386/46371 usb USB controller cannot be initialized on I o [2003/08/13] usb/5 usb [ums] system freezes with access to /dev/ o [2003/09/06] usb/56513 usb [ugen] [panic] panic in ugen w/ moused -p o [2003/09/26] bin/57255 usb usbd and multi-function devices s [2003/12/15] usb/60276 usb [usb] Kernel panic when plugging in USB ( o [2004/01/20] usb/61627 usb [usb] [patch] New USB printer not support o [2004/01/30] usb/62088 usb [usb] Logitech Cordless/Optical Mouse not o [2004/02/03] usb/62309 usb [ugen] [panic] panic: ugen(4) driver o [2004/03/01] usb/63621 usb [usb] USB MemoryStick Reader stalls/crash o [2004/07/13] usb/69006 usb [patch] Apple Cinema Display hangs USB po o [2004/08/30] usb/71155 usb [usb] misbehaving usb-printer hangs proce o [2004/10/30] usb/73307 usb [panic] Kernel panics on USB disconnect o [2004/12/06] usb/74771 usb [umass] mounting write-protected umass de o [2005/01/01] usb/75705 usb [panic] da0 attach / Optio S4 (with backt o [2005/01/04] usb/75797 usb 5.3-STABLE(2005 1/4) detect USB headset, o [2005/01/13] usb/76204 usb panic while using usb attached modem o [2005/01/18] usb/76395 usb USB printer does not work, usbdevs says o [2005/01/21] usb/76554 usb Panram yoyo USB MP3 player causes panic o [2005/01/25] usb/76684 usb [hang] Toshiba PDR-M4 camera connected vi o [2005/02/06] usb/77184 usb kernel panic on USB device disconnect o [2005/02/09] usb/77294 usb ucom + ulpcom panic o [2005/02/16] usb/77604 usb Sluggish Logitch LX700 USB Mouse o [2005/02/23] usb/77940 usb [patch] [panic] insertion of usb keyboard o [2005/03/01] i386/78218 usb [kue] kue not detected on Sony PCG-F370 V o [2005/03/18] usb/78989 usb please add USB keyboard support to instal o [2005/03/22] usb/79140 usb WD Firewire/USB Combo hangs under load on o [2005/03/27] usb/79269 usb USB ohci da0 plug/unplug causes crashes a o [2005/03/27] usb/79287 usb UHCI hang after interrupt transfer o [2005/04/04] usb/79524 usb printing to Minolta PagePro 1[23]xxW via o [2005/04/07] usb/79656 usb [usb] RHSC interrupts lost o [2005/04/09] usb/79722 usb [usb] wrong alignments in ehci.h o [2005/04/17] usb/80040 usb [hang] Use of sound mixer causes system f o [2005/04/22] usb/80260 usb Travan USB tape drive fails to write o [2005/04/26] usb/80361 usb mounting of usb-stick fails o [2005/04/26] usb/80373 usb usb keyboard does not respond o [2005/05/04] usb/80628 usb recent USB MFCs cause panics o [2005/05/06] usb/80685 usb panic in usb_cold_explore() at begining o [2005/05/09] usb/80829 usb possible panic when loading USB-modules o [2005/05/10] usb/80862 usb [patch] USB locking issues: missing some o [2005/05/20] usb/81308 usb [ugen] [patch] polling a ugen(4) control o [2005/05/26] usb/81524 usb panic: usb_cold_explore: busses to explor o [2005/06/13] usb/82198 usb Panic on attaching of ONKI N-338 USB MP3 o [2005/06/15] usb/82272 usb Can not recognize Casio camera EX-Z40 as o [2005/06/17] usb/82350 usb [usb] null pointer dereference in USB sta o [2005/06/22] usb/82520 usb Reboot when USL101 connected o [2005/06/26] usb/82660 usb EHCI: I/O stuck in state 'physrd'/panic o [2005/07/15] usb/83504 usb [usb] SpeedTouch USB stop working on rece o [2005/07/16] usb/83563 usb [panic] Page Fault while detaching Mpman o [2005/07/18] usb/83677 usb [usb] usb controller often not detected ( o [2005/07/19] usb/83756 usb Microsoft Intellimouse Explorer 4.0A does o [2005/07/24] usb/83977 usb [ucom] [panic] ucom1: open bulk out error o [2005/07/30] usb/84326 usb [umass] Panic trying to connect SCSI tape o [2005/07/30] usb/84336 usb [usb] [reboot] instant system reboot when o [2005/08/15] usb/84936 usb install - usb keyboard not recognized o [2005/09/12] usb/86031 usb need support usb nic rt2500 in my 5.4 STA o [2005/09/30] usb/86767
Re: usb/86767: [usb] bogus slice starts beyond end of the disk:...
The following reply was made to PR usb/86767; it has been noted by GNATS. From: Gilbert C Healton [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: Subject: Re: usb/86767: [usb] bogus slice starts beyond end of the disk:... Date: Mon, 6 Feb 2006 12:08:01 -0500 (EST) Fix: There are actually two bugs in two different sections of the kernel. Individual fixes for each problem follow: 86767-beyond.patch fixes main slice starts beyond end of the disk:... problem. Floppy disks are not expected to contain partition tables. See additional documentation within the patch. 86767-unsupportedUFI.patch fixes umass0: contained Unsupported UFI command 0x35 problem also reported in 86767. Originally I thought it was another symptom of the same problem. USB floppy drives now return success on SYNCHRONIZE_CACHE requests These patches have been running for some months without causing any problems. 86767-beyond.patch -- [] FreeBSD bug: kern/86767 bogus slice starts beyond end of the disk:... mount. [] Most accesses to USB floppy drives, especially mounts, tend to result in bogus slice starts beyond end of the disk:... errors. [] if the boot parameter block claims the device is a floppy media then it is NOW assumed there is no partition table to check. [] Much thanks to Bruce Evans [EMAIL PROTECTED] for hints on where to drop this patch. --- sys/msdosfs/bootsect.h Fri Aug 27 20:48:06 1999 +++ sys/msdosfs/bootsect.h Mon Oct 3 18:04:27 2005 @@ -94,6 +94,34 @@ struct bootsector710 bs710; }; + + /* selected media description bytes within bsPBP. used to detect + * media that only has one slice on it. for now this is expected + * to be floppy media. +[EMAIL PROTECTED]... @lumeta.com */ + /* (as of 2005-09 floppy media description bytes were available at + http://support.microsoft.com/default.aspx?scid=kb;en-us;140418 + http://www.win.tue.nl/~aeb/linux/fs/fat/fat-1.html) + /* size DOS Capicty sides tks spt */ +#define MSDOS_MEDIA_ONESLICE0 0xF9 /* 5.25 3.0 1200KB 2 80 15 */ +#define MSDOS_MEDIA_ONESLICE1 0xFF /* 5.25 1.1 320KB 2 40 8 */ + +#define MSDOS_MEDIA_ONESLICE2 0xF0 /* 3.5 ?.? 2880KB 2 80 36 */ + +#define MSDOS_MEDIA_oneslice(c) ( \ + ( md = MSDOS_MEDIA_ONESLICE0 md = MSDOS_MEDIA_ONESLICE1 ) \ + || ( md == MSDOS_MEDIA_ONESLICE2 ) \ + ) + /* if floppies with slice tables are ever used I suspose + that a check for s1-s4 could be made to verify the + first byte of each slice table is 0x00 or 0x80 AND + at most one byte has the 0x80 value in it AND the + remaining bytes of each slice table are not all zeros. If + this test is met you might be able to assume a slice + table exists. But I would make such a compile-option for + those expressly asking for it. */ + + #if 0 /* * Shorthand for fields in the bpb. --- sys/kern/subr_diskmbr.cFri Jan 28 05:22:07 2000 +++ sys/kern/subr_diskmbr.cMon Oct 3 18:16:19 2005 @@ -42,6 +42,7 @@ #include sys/systm.h #include sys/buf.h #include sys/conf.h +#include msdosfs/bootsect.h /* BOOTSIG0, BOOTSIG1, MSDOS_MEDIA_oneslice */ #ifdef PC98 #define PC98_ATCOMPAT #define dsinit atcompat_dsinit @@ -200,13 +201,26 @@ /* Weakly verify it. */ cp = bp-b_data; sname = dsname(dev, dkunit(dev), WHOLE_DISK_SLICE, RAW_PART, partname); - if (cp[0x1FE] != 0x55 || cp[0x1FF] != 0xAA) { + if (cp[0x1FE] != BOOTSIG0 || cp[0x1FF] != BOOTSIG1) { if (bootverbose) printf(%s: invalid primary partition table: no magic\n, sname); error = EINVAL; goto done; } + + { /* [EMAIL PROTECTED] also [EMAIL PROTECTED] */ + /* check if media description byte within range of known floppy medias */ + + u_char md = cp[0x15]; /* set local easy access variable */ + + if ( MSDOS_MEDIA_oneslice(md) ) { + /* this media only uses a single slice (e.g., floppies) */ + + error = 0; + goto done; /* no partition table to process */ + } + } /* Make a copy of the partition table to avoid alignment problems. */ memcpy(dpcopy[0], cp + DOSPARTOFF, sizeof(dpcopy)); 86767-unsupportedUFI.patch -- [] FreeBSD bug: kern/86767 bogus slice starts beyond end of the disk:... mount. (also umass0: contained Unsupported UFI command 0x35,
Re: usb/86767: [usb] bogus slice starts beyond end of the disk:...
The following reply was made to PR usb/86767; it has been noted by GNATS. From: Gilbert C Healton [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: Subject: Re: usb/86767: [usb] bogus slice starts beyond end of the disk:... Date: Mon, 6 Feb 2006 12:08:44 -0500 (EST) Fix: There are actually two bugs in two different sections of the kernel. Individual fixes for each problem follow: 86767-beyond.patch fixes main slice starts beyond end of the disk:... problem. Floppy disks are not expected to contain partition tables. See additional documentation within the patch. 86767-unsupportedUFI.patch fixes umass0: contained Unsupported UFI command 0x35 problem also reported in 86767. Originally I thought it was another symptom of the same problem. USB floppy drives now return success on SYNCHRONIZE_CACHE requests These patches have been running for some months without causing any problems. 86767-beyond.patch -- [] FreeBSD bug: kern/86767 bogus slice starts beyond end of the disk:... mount. [] Most accesses to USB floppy drives, especially mounts, tend to result in bogus slice starts beyond end of the disk:... errors. [] if the boot parameter block claims the device is a floppy media then it is NOW assumed there is no partition table to check. [] Much thanks to Bruce Evans [EMAIL PROTECTED] for hints on where to drop this patch. --- sys/msdosfs/bootsect.h Fri Aug 27 20:48:06 1999 +++ sys/msdosfs/bootsect.h Mon Oct 3 18:04:27 2005 @@ -94,6 +94,34 @@ struct bootsector710 bs710; }; + + /* selected media description bytes within bsPBP. used to detect + * media that only has one slice on it. for now this is expected + * to be floppy media. +[EMAIL PROTECTED]... @lumeta.com */ + /* (as of 2005-09 floppy media description bytes were available at + http://support.microsoft.com/default.aspx?scid=kb;en-us;140418 + http://www.win.tue.nl/~aeb/linux/fs/fat/fat-1.html) + /* size DOS Capicty sides tks spt */ +#define MSDOS_MEDIA_ONESLICE0 0xF9 /* 5.25 3.0 1200KB 2 80 15 */ +#define MSDOS_MEDIA_ONESLICE1 0xFF /* 5.25 1.1 320KB 2 40 8 */ + +#define MSDOS_MEDIA_ONESLICE2 0xF0 /* 3.5 ?.? 2880KB 2 80 36 */ + +#define MSDOS_MEDIA_oneslice(c) ( \ + ( md = MSDOS_MEDIA_ONESLICE0 md = MSDOS_MEDIA_ONESLICE1 ) \ + || ( md == MSDOS_MEDIA_ONESLICE2 ) \ + ) + /* if floppies with slice tables are ever used I suspose + that a check for s1-s4 could be made to verify the + first byte of each slice table is 0x00 or 0x80 AND + at most one byte has the 0x80 value in it AND the + remaining bytes of each slice table are not all zeros. If + this test is met you might be able to assume a slice + table exists. But I would make such a compile-option for + those expressly asking for it. */ + + #if 0 /* * Shorthand for fields in the bpb. --- sys/kern/subr_diskmbr.cFri Jan 28 05:22:07 2000 +++ sys/kern/subr_diskmbr.cMon Oct 3 18:16:19 2005 @@ -42,6 +42,7 @@ #include sys/systm.h #include sys/buf.h #include sys/conf.h +#include msdosfs/bootsect.h /* BOOTSIG0, BOOTSIG1, MSDOS_MEDIA_oneslice */ #ifdef PC98 #define PC98_ATCOMPAT #define dsinit atcompat_dsinit @@ -200,13 +201,26 @@ /* Weakly verify it. */ cp = bp-b_data; sname = dsname(dev, dkunit(dev), WHOLE_DISK_SLICE, RAW_PART, partname); - if (cp[0x1FE] != 0x55 || cp[0x1FF] != 0xAA) { + if (cp[0x1FE] != BOOTSIG0 || cp[0x1FF] != BOOTSIG1) { if (bootverbose) printf(%s: invalid primary partition table: no magic\n, sname); error = EINVAL; goto done; } + + { /* [EMAIL PROTECTED] also [EMAIL PROTECTED] */ + /* check if media description byte within range of known floppy medias */ + + u_char md = cp[0x15]; /* set local easy access variable */ + + if ( MSDOS_MEDIA_oneslice(md) ) { + /* this media only uses a single slice (e.g., floppies) */ + + error = 0; + goto done; /* no partition table to process */ + } + } /* Make a copy of the partition table to avoid alignment problems. */ memcpy(dpcopy[0], cp + DOSPARTOFF, sizeof(dpcopy)); 86767-unsupportedUFI.patch -- [] FreeBSD bug: kern/86767 bogus slice starts beyond end of the disk:... mount. (also umass0: contained Unsupported UFI command 0x35,
Re: usb/86767: [usb] bogus slice starts beyond end of the disk:...
The following reply was made to PR usb/86767; it has been noted by GNATS. From: Gilbert C Healton [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: Subject: Re: usb/86767: [usb] bogus slice starts beyond end of the disk:... Date: Mon, 6 Feb 2006 12:20:36 -0500 (EST) Fix: There are actually two bugs in two different sections of the kernel. Individual fixes for each problem follow: 86767-beyond.patch fixes main slice starts beyond end of the disk:... problem. Floppy disks are no longer expected to contain partition tables. See additional documentation within the patch. 86767-unsupportedUFI.patch fixes umass0: contained Unsupported UFI command 0x35 problem also reported in 86767. Originally I thought it was another symptom of the same problem. USB drives now return success on SYNCHRONIZE_CACHE requests These patches have been running for some months without causing any problems. 86767-beyond.patch -- [] FreeBSD bug: kern/86767 bogus slice starts beyond end of the disk:... mount. [] Most accesses to USB floppy drives, especially mounts, tend to result in bogus slice starts beyond end of the disk:... errors. [] if the boot parameter block claims the device is a floppy media then it is NOW assumed there is no partition table to check. [] Much thanks to Bruce Evans [EMAIL PROTECTED] for hints on where to drop this patch. --- sys/msdosfs/bootsect.h Fri Aug 27 20:48:06 1999 +++ sys/msdosfs/bootsect.h Mon Oct 3 18:04:27 2005 @@ -94,6 +94,34 @@ struct bootsector710 bs710; }; + + /* selected media description bytes within bsPBP. used to detect + * media that only has one slice on it. for now this is expected + * to be floppy media. +[EMAIL PROTECTED]... @lumeta.com */ + /* (as of 2005-09 floppy media description bytes were available at + http://support.microsoft.com/default.aspx?scid=kb;en-us;140418 + http://www.win.tue.nl/~aeb/linux/fs/fat/fat-1.html) + /* size DOS Capicty sides tks spt */ +#define MSDOS_MEDIA_ONESLICE0 0xF9 /* 5.25 3.0 1200KB 2 80 15 */ +#define MSDOS_MEDIA_ONESLICE1 0xFF /* 5.25 1.1 320KB 2 40 8 */ + +#define MSDOS_MEDIA_ONESLICE2 0xF0 /* 3.5 ?.? 2880KB 2 80 36 */ + +#define MSDOS_MEDIA_oneslice(c) ( \ + ( md = MSDOS_MEDIA_ONESLICE0 md = MSDOS_MEDIA_ONESLICE1 ) \ + || ( md == MSDOS_MEDIA_ONESLICE2 ) \ + ) + /* if floppies with slice tables are ever used I suspose + that a check for s1-s4 could be made to verify the + first byte of each slice table is 0x00 or 0x80 AND + at most one byte has the 0x80 value in it AND the + remaining bytes of each slice table are not all zeros. If + this test is met you might be able to assume a slice + table exists. But I would make such a compile-option for + those expressly asking for it. */ + + #if 0 /* * Shorthand for fields in the bpb. --- sys/kern/subr_diskmbr.cFri Jan 28 05:22:07 2000 +++ sys/kern/subr_diskmbr.cMon Oct 3 18:16:19 2005 @@ -42,6 +42,7 @@ #include sys/systm.h #include sys/buf.h #include sys/conf.h +#include msdosfs/bootsect.h /* BOOTSIG0, BOOTSIG1, MSDOS_MEDIA_oneslice */ #ifdef PC98 #define PC98_ATCOMPAT #define dsinit atcompat_dsinit @@ -200,13 +201,26 @@ /* Weakly verify it. */ cp = bp-b_data; sname = dsname(dev, dkunit(dev), WHOLE_DISK_SLICE, RAW_PART, partname); - if (cp[0x1FE] != 0x55 || cp[0x1FF] != 0xAA) { + if (cp[0x1FE] != BOOTSIG0 || cp[0x1FF] != BOOTSIG1) { if (bootverbose) printf(%s: invalid primary partition table: no magic\n, sname); error = EINVAL; goto done; } + + { /* [EMAIL PROTECTED] also [EMAIL PROTECTED] */ + /* check if media description byte within range of known floppy medias */ + + u_char md = cp[0x15]; /* set local easy access variable */ + + if ( MSDOS_MEDIA_oneslice(md) ) { + /* this media only uses a single slice (e.g., floppies) */ + + error = 0; + goto done; /* no partition table to process */ + } + } /* Make a copy of the partition table to avoid alignment problems. */ memcpy(dpcopy[0], cp + DOSPARTOFF, sizeof(dpcopy)); 86767-unsupportedUFI.patch -- [] FreeBSD bug: kern/86767 bogus slice starts beyond end of the disk:... mount. (also umass0: contained Unsupported UFI command 0x35, which