Re: Recommended USB 2.0 controller fr. 5.2+
Bernd Walter wrote: On Tue, Apr 06, 2004 at 01:58:42PM +0200, Heinrich Rebehn wrote: Bernd Walter wrote: [snip] Apr 3 12:32:32 antsrv1 kernel: da1: 19077MB (39070080 512 byte sectors: 255H 63S/T 2432C) Apr 3 12:33:03 antsrv1 login: ROOT LOGIN (root) ON ttyv0 Apr 3 12:38:08 antsrv1 syslogd: kernel boot file is /boot/kernel/kernel Apr 3 12:38:08 antsrv1 kernel: panic: ehci_abort_xfer: not in process context OK - we have an abort_xfer without any reason given. The panic is because the aborted transfer doesn't exist, which could mean that someone aborted an already completed transfer. Can you please add USB_DEBUG to your kernel and retry. I did, but with USB_DEBUG the system reproducibly crashes during boot: Without a stacktrace or at least the last kernel messages this output is almost useless. kernel: kernel: kernel: Fatal trap 12: page fault while in kernel mode kernel: cpuid = 0; apic id = 00 kernel: fault virtual address = 0xd kernel: fault code = supervisor write, page not present kernel: instruction pointer = 0x8:0xc0535482 kernel: stack pointer = 0x10:0xeaccfbb0 kernel: frame pointer = 0x10:0xeaccfbc8 kernel: code segment= base 0x0, limit 0xf, type 0x1b kernel: = DPL 0, pres 1, def32 1, gran 1 kernel: processor eflags= interrupt enabled, resume, IOPL = 0 kernel: current process = 246 (sysctl) kernel: trap number = 12 kernel: panic: page fault kernel: cpuid = 0; kernel: kernel: syncing disks, buffers remaining... 6564 6564 6563 6563 6563 6563 6563 6563 6563 6563 6563 6563 6563 6563 6563 6563 6563 6563 6563 6563 6563 6563 You have 6563 dirty buffers when it crashed? That's amazing - so you are at least already on the way getting multiuser - otherwise everything is still read-only. I can't guess what services, etc.. you are starting - you really have to tell what happens. The normal startup procedure was executing, dunno what was running at the exact time of the crash. Anyway, i tossed in a firewire card (VIA VT6306) and it's running perfect, no problems so far. Thanks for your help anyway. Greetings, Heinrich ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Recommended USB 2.0 controller fr. 5.2+
> >>To be more specific I found a controllre by Q-Tec (425U) wtih a Via > >> VT6202 chipset. Anyone know if this will work? As a follow-up: That Q-Tec controller (that I ended up buying) didn't work... USB1 works as usual, but no luck with ehci. When plugging in a usb2 drive either nothing happens, or I get an error followed by a kernel panic when unplugging it. (I posted already about this, offering help, to the usb-dev list. If someone here wants details I can provide them, but otherwise the above is mostly meant as a heads-up for future USB controller buyers reading the archives.) -- / Peter Schuller, InfiDyne Technologies HB PGP userID: 0xE9758B7D or 'Peter Schuller <[EMAIL PROTECTED]>' Key retrieval: Send an E-Mail to [EMAIL PROTECTED] E-Mail: [EMAIL PROTECTED] Web: http://www.scode.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Recommended USB 2.0 controller fr. 5.2+
On Tue, Apr 06, 2004 at 01:58:42PM +0200, Heinrich Rebehn wrote: > Bernd Walter wrote: > [snip] > > > >>Apr 3 12:32:32 antsrv1 kernel: da1: 19077MB (39070080 512 byte sectors: > >>255H 63S/T 2432C) > >>Apr 3 12:33:03 antsrv1 login: ROOT LOGIN (root) ON ttyv0 > >>Apr 3 12:38:08 antsrv1 syslogd: kernel boot file is /boot/kernel/kernel > >>Apr 3 12:38:08 antsrv1 kernel: panic: ehci_abort_xfer: not in process > >>context > > > > > >OK - we have an abort_xfer without any reason given. > >The panic is because the aborted transfer doesn't exist, which could > >mean that someone aborted an already completed transfer. > >Can you please add USB_DEBUG to your kernel and retry. > > > > > I did, but with USB_DEBUG the system reproducibly crashes during boot: Without a stacktrace or at least the last kernel messages this output is almost useless. > kernel: > kernel: > kernel: Fatal trap 12: page fault while in kernel mode > kernel: cpuid = 0; apic id = 00 > kernel: fault virtual address = 0xd > kernel: fault code = supervisor write, page not present > kernel: instruction pointer = 0x8:0xc0535482 > kernel: stack pointer = 0x10:0xeaccfbb0 > kernel: frame pointer = 0x10:0xeaccfbc8 > kernel: code segment= base 0x0, limit 0xf, type 0x1b > kernel: = DPL 0, pres 1, def32 1, gran 1 > kernel: processor eflags= interrupt enabled, resume, IOPL = 0 > kernel: current process = 246 (sysctl) > kernel: trap number = 12 > kernel: panic: page fault > kernel: cpuid = 0; > kernel: > kernel: syncing disks, buffers remaining... 6564 6564 6563 6563 6563 > 6563 6563 6563 6563 6563 6563 6563 6563 6563 6563 6563 6563 6563 6563 > 6563 6563 6563 You have 6563 dirty buffers when it crashed? That's amazing - so you are at least already on the way getting multiuser - otherwise everything is still read-only. I can't guess what services, etc.. you are starting - you really have to tell what happens. -- B.Walter BWCThttp://www.bwct.de [EMAIL PROTECTED] [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Recommended USB 2.0 controller fr. 5.2+
Bernd Walter wrote: [snip] Apr 3 12:32:32 antsrv1 kernel: da1: 19077MB (39070080 512 byte sectors: 255H 63S/T 2432C) Apr 3 12:33:03 antsrv1 login: ROOT LOGIN (root) ON ttyv0 Apr 3 12:38:08 antsrv1 syslogd: kernel boot file is /boot/kernel/kernel Apr 3 12:38:08 antsrv1 kernel: panic: ehci_abort_xfer: not in process context OK - we have an abort_xfer without any reason given. The panic is because the aborted transfer doesn't exist, which could mean that someone aborted an already completed transfer. Can you please add USB_DEBUG to your kernel and retry. I did, but with USB_DEBUG the system reproducibly crashes during boot: kernel: kernel: kernel: Fatal trap 12: page fault while in kernel mode kernel: cpuid = 0; apic id = 00 kernel: fault virtual address = 0xd kernel: fault code = supervisor write, page not present kernel: instruction pointer = 0x8:0xc0535482 kernel: stack pointer = 0x10:0xeaccfbb0 kernel: frame pointer = 0x10:0xeaccfbc8 kernel: code segment= base 0x0, limit 0xf, type 0x1b kernel: = DPL 0, pres 1, def32 1, gran 1 kernel: processor eflags= interrupt enabled, resume, IOPL = 0 kernel: current process = 246 (sysctl) kernel: trap number = 12 kernel: panic: page fault kernel: cpuid = 0; kernel: kernel: syncing disks, buffers remaining... 6564 6564 6563 6563 6563 6563 6563 6563 6563 6563 6563 6563 6563 6563 6563 6563 6563 6563 6563 6563 6563 6563 kernel: giving up on 6557 buffers kernel: Uptime: 3m22s -- Heinrich ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Recommended USB 2.0 controller fr. 5.2+
Bernd Walter wrote: On Mon, Apr 05, 2004 at 05:45:00PM +0200, Heinrich Rebehn wrote: Bernd Walter wrote: Which kind of IO errors? USB / SCSI / DA / Application? This i from "ktrace tunefs -p /dev/da0s1a" 4640 tunefs RET read 0 4640 tunefs CALL stat(0xbfbfea4a,0xbfbfe5a0) 4640 tunefs NAMI "/dev/da0s1a" 4640 tunefs RET stat 0 4640 tunefs CALL open(0xbfbfea4a,0,0) 4640 tunefs NAMI "/dev/da0s1a" 4640 tunefs RET open -1 errno 5 Input/output error 4640 tunefs CALL write(0x2,0xbfbfdf30,0x8) 4640 tunefs GIO fd 2 wrote 8 bytes "tunefs: " 4640 tunefs RET write 8 4640 tunefs CALL write(0x2,0xbfbfdf50,0x2a) 4640 tunefs GIO fd 2 wrote 42 bytes "/dev/da0s1a: could not open special device" 4640 tunefs RET write 42/0x2a Yes - but that's symptoms - there must be a USB and/or SCSI error too. That's what i found in the logfile: (I had just mounted the device on /export/backup). Mount reported "unexpected softupdates inconsistency" and i issued "tunefs -p /dev/da0s1a" to check if i had really enabled softupdates) Apr 5 13:43:56 antsrv1 kernel: WARNING: /export/backup was not properly dismounted Apr 5 13:45:21 antsrv1 kernel: ehci_idone: need toggle update Apr 5 13:45:25 antsrv1 kernel: ehci_idone: need toggle update Apr 5 13:46:02 antsrv1 fsck: /dev/twed1s1e: Reclaimed: 0 directories, 0 files, 8 fragments Apr 5 13:46:02 antsrv1 fsck: /dev/twed1s1e: 1103265 files, 105407382 used, 21632531 free (256971 frags, 2671945 blocks, 0.2% fragmentation) Apr 5 14:05:00 antsrv1 cron[4146]: login_getclass: unknown class 'des_users' Apr 5 14:37:10 antsrv1 kernel: ehci_idone: need toggle update Apr 5 14:37:14 antsrv1 kernel: ehci_idone: need toggle update Apr 5 14:37:20 antsrv1 kernel: (da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x4, scsi status == 0x0 Apr 5 14:37:29 antsrv1 kernel: Opened disk da0 -> 5 Apr 5 14:37:59 antsrv1 last message repeated 3 times Apr 5 14:38:19 antsrv1 last message repeated 2 times -- Heinrich ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Recommended USB 2.0 controller fr. 5.2+
On Mon, Apr 05, 2004 at 05:45:00PM +0200, Heinrich Rebehn wrote: > Bernd Walter wrote: > >Which kind of IO errors? > >USB / SCSI / DA / Application? > > > This i from "ktrace tunefs -p /dev/da0s1a" > > 4640 tunefs RET read 0 > 4640 tunefs CALL stat(0xbfbfea4a,0xbfbfe5a0) > 4640 tunefs NAMI "/dev/da0s1a" > 4640 tunefs RET stat 0 > 4640 tunefs CALL open(0xbfbfea4a,0,0) > 4640 tunefs NAMI "/dev/da0s1a" > 4640 tunefs RET open -1 errno 5 Input/output error > 4640 tunefs CALL write(0x2,0xbfbfdf30,0x8) > 4640 tunefs GIO fd 2 wrote 8 bytes >"tunefs: " > 4640 tunefs RET write 8 > 4640 tunefs CALL write(0x2,0xbfbfdf50,0x2a) > 4640 tunefs GIO fd 2 wrote 42 bytes >"/dev/da0s1a: could not open special device" > 4640 tunefs RET write 42/0x2a Yes - but that's symptoms - there must be a USB and/or SCSI error too. -- B.Walter BWCThttp://www.bwct.de [EMAIL PROTECTED] [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Recommended USB 2.0 controller fr. 5.2+
Bernd Walter wrote: On Mon, Apr 05, 2004 at 05:09:32PM +0200, Heinrich Rebehn wrote: Bernd Walter wrote: On Mon, Apr 05, 2004 at 02:58:33PM +0200, Heinrich Rebehn wrote: i am using a NEC USB2 controller and am just about to give up on using it. I don't know if it's the controller, the disk or the ehci driver. However, man ehci(4) states that "The driver is not finished and is quite buggy." This seems to be true. I get all sorts of trouble ranging from hangs during boot to system crashes. I am reverting back to USB1 although its terribly slow. FreeBSD 5.2.1-RELEASE-p3 usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb2 usb3 usb4: on ehci0 usb4: USB revision 2.0 uhub4: NEC EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub4: 3 ports with 3 removable, self powered umass0: Maxtor OneTouch, rev 2.00/2.00, addr 2 umass0: Get Max Lun not supported (STALLED) GEOM: create disk da0 dp=0xc82ad450 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-0 device da0: 1.000MB/s transfers da0: 239371MB (490232832 512 byte sectors: 255H 63S/T 30515C) Sorry i can't report anything posivtive on this. And I can't see anything wrong with your log. Sorry, the log should only show what hardware i am using. I could not find any log for the hangs, probably because it occurs while the kernel is starting and i have to press reset, so it never gets written to a logfile. The crash happend when i hotplugged an MP3 Jukebox and tried to mount it: Apr 3 12:32:26 antsrv1 kernel: umass1: ARCHOS ARCHOS USB2.0 (P4a), rev 2.00/11.01, addr 3 Apr 3 12:32:32 antsrv1 kernel: GEOM: create disk da1 dp=0xca5f0850 Apr 3 12:32:32 antsrv1 kernel: da1 at umass-sim1 bus 1 target 0 lun 0 Apr 3 12:32:32 antsrv1 kernel: da1: Fixed Direct Access SCSI-0 device SCSI-0 - how funny - there was never a SCSI revision 0. If we would have been strict then da driver wouldn't attach, because it can't really know a SCSI-0 direct access. At least a disk should be SCSI-1 with CCS which is the first revision that definied the command set. Apr 3 12:32:32 antsrv1 kernel: da1: 1.000MB/s transfers Also not very smart - but harmless. Apr 3 12:32:32 antsrv1 kernel: da1: 19077MB (39070080 512 byte sectors: 255H 63S/T 2432C) Apr 3 12:33:03 antsrv1 login: ROOT LOGIN (root) ON ttyv0 Apr 3 12:38:08 antsrv1 syslogd: kernel boot file is /boot/kernel/kernel Apr 3 12:38:08 antsrv1 kernel: panic: ehci_abort_xfer: not in process context OK - we have an abort_xfer without any reason given. The panic is because the aborted transfer doesn't exist, which could mean that someone aborted an already completed transfer. Can you please add USB_DEBUG to your kernel and retry. I will, if i find an opportunity. Problem is that the machine is our main server and each crash dirties all our filesystems. Luckily, 5.2.1 permits fsck in the background, so we don't have 30 min. downtime anymore. I hope i can retry this week. Apr 3 12:38:08 antsrv1 kernel: cpuid = 0; Apr 3 12:38:08 antsrv1 kernel: Apr 3 12:38:08 antsrv1 kernel: syncing disks, buffers remaining... 6418 6418 6418 6418 6418 6418 6418 6418 6418 6418 6418 6418 6418 6418 6418 6418 6418 6418 6418 6418 Apr 3 12:38:08 antsrv1 kernel: giving up on 3004 buffers Apr 3 12:38:08 antsrv1 kernel: Uptime: 22h44m54s A stack trace would be fine too so we see the function issuing the abort. The cause might be with USB-1.1 too, but not triggered because of less speed. Also, i get I/O-errors and the disk is inaccessible after having worked ok for days. Rebooting the machine fixes this. Which kind of IO errors? USB / SCSI / DA / Application? This i from "ktrace tunefs -p /dev/da0s1a" 4640 tunefs RET read 0 4640 tunefs CALL stat(0xbfbfea4a,0xbfbfe5a0) 4640 tunefs NAMI "/dev/da0s1a" 4640 tunefs RET stat 0 4640 tunefs CALL open(0xbfbfea4a,0,0) 4640 tunefs NAMI "/dev/da0s1a" 4640 tunefs RET open -1 errno 5 Input/output error 4640 tunefs CALL write(0x2,0xbfbfdf30,0x8) 4640 tunefs GIO fd 2 wrote 8 bytes "tunefs: " 4640 tunefs RET write 8 4640 tunefs CALL write(0x2,0xbfbfdf50,0x2a) 4640 tunefs GIO fd 2 wrote 42 bytes "/dev/da0s1a: could not open special device" 4640 tunefs RET write 42/0x2a -- Heinrich ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Recommended USB 2.0 controller fr. 5.2+
On Mon, Apr 05, 2004 at 05:09:32PM +0200, Heinrich Rebehn wrote: > Bernd Walter wrote: > >On Mon, Apr 05, 2004 at 02:58:33PM +0200, Heinrich Rebehn wrote: > > > >>i am using a NEC USB2 controller and am just about to give up on using > >>it. I don't know if it's the controller, the disk or the ehci driver. > >>However, man ehci(4) states that "The driver is not finished and is > >>quite buggy." This seems to be true. I get all sorts of trouble ranging > >>from hangs during boot to system crashes. > >>I am reverting back to USB1 although its terribly slow. > >> > >>FreeBSD 5.2.1-RELEASE-p3 > >> > >>usb4: EHCI version 1.0 > >>usb4: companion controllers, 2 ports each: usb2 usb3 > >>usb4: on ehci0 > >>usb4: USB revision 2.0 > >>uhub4: NEC EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 > >>uhub4: 3 ports with 3 removable, self powered > >> > >>umass0: Maxtor OneTouch, rev 2.00/2.00, addr 2 > >>umass0: Get Max Lun not supported (STALLED) > >>GEOM: create disk da0 dp=0xc82ad450 > >>da0 at umass-sim0 bus 0 target 0 lun 0 > >>da0: Fixed Direct Access SCSI-0 device > >>da0: 1.000MB/s transfers > >>da0: 239371MB (490232832 512 byte sectors: 255H 63S/T 30515C) > >> > >>Sorry i can't report anything posivtive on this. > > > > > >And I can't see anything wrong with your log. > > > > Sorry, the log should only show what hardware i am using. > I could not find any log for the hangs, probably because it occurs while > the kernel is starting and i have to press reset, so it never gets > written to a logfile. > > The crash happend when i hotplugged an MP3 Jukebox and tried to mount it: > > Apr 3 12:32:26 antsrv1 kernel: umass1: ARCHOS ARCHOS USB2.0 (P4a), rev > 2.00/11.01, addr 3 > Apr 3 12:32:32 antsrv1 kernel: GEOM: create disk da1 dp=0xca5f0850 > Apr 3 12:32:32 antsrv1 kernel: da1 at umass-sim1 bus 1 target 0 lun 0 > Apr 3 12:32:32 antsrv1 kernel: da1: Fixed > Direct Access SCSI-0 device SCSI-0 - how funny - there was never a SCSI revision 0. If we would have been strict then da driver wouldn't attach, because it can't really know a SCSI-0 direct access. At least a disk should be SCSI-1 with CCS which is the first revision that definied the command set. > Apr 3 12:32:32 antsrv1 kernel: da1: 1.000MB/s transfers Also not very smart - but harmless. > Apr 3 12:32:32 antsrv1 kernel: da1: 19077MB (39070080 512 byte sectors: > 255H 63S/T 2432C) > Apr 3 12:33:03 antsrv1 login: ROOT LOGIN (root) ON ttyv0 > Apr 3 12:38:08 antsrv1 syslogd: kernel boot file is /boot/kernel/kernel > Apr 3 12:38:08 antsrv1 kernel: panic: ehci_abort_xfer: not in process > context OK - we have an abort_xfer without any reason given. The panic is because the aborted transfer doesn't exist, which could mean that someone aborted an already completed transfer. Can you please add USB_DEBUG to your kernel and retry. > Apr 3 12:38:08 antsrv1 kernel: cpuid = 0; > Apr 3 12:38:08 antsrv1 kernel: > Apr 3 12:38:08 antsrv1 kernel: syncing disks, buffers remaining... 6418 > 6418 6418 6418 6418 6418 6418 6418 6418 6418 6418 6418 6418 6418 6418 > 6418 6418 6418 6418 6418 > Apr 3 12:38:08 antsrv1 kernel: giving up on 3004 buffers > Apr 3 12:38:08 antsrv1 kernel: Uptime: 22h44m54s A stack trace would be fine too so we see the function issuing the abort. The cause might be with USB-1.1 too, but not triggered because of less speed. > Also, i get I/O-errors and the disk is inaccessible after having worked > ok for days. Rebooting the machine fixes this. Which kind of IO errors? USB / SCSI / DA / Application? -- B.Walter BWCThttp://www.bwct.de [EMAIL PROTECTED] [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Recommended USB 2.0 controller fr. 5.2+
Bernd Walter wrote: On Mon, Apr 05, 2004 at 02:58:33PM +0200, Heinrich Rebehn wrote: i am using a NEC USB2 controller and am just about to give up on using it. I don't know if it's the controller, the disk or the ehci driver. However, man ehci(4) states that "The driver is not finished and is quite buggy." This seems to be true. I get all sorts of trouble ranging from hangs during boot to system crashes. I am reverting back to USB1 although its terribly slow. FreeBSD 5.2.1-RELEASE-p3 usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb2 usb3 usb4: on ehci0 usb4: USB revision 2.0 uhub4: NEC EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub4: 3 ports with 3 removable, self powered umass0: Maxtor OneTouch, rev 2.00/2.00, addr 2 umass0: Get Max Lun not supported (STALLED) GEOM: create disk da0 dp=0xc82ad450 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-0 device da0: 1.000MB/s transfers da0: 239371MB (490232832 512 byte sectors: 255H 63S/T 30515C) Sorry i can't report anything posivtive on this. And I can't see anything wrong with your log. Sorry, the log should only show what hardware i am using. I could not find any log for the hangs, probably because it occurs while the kernel is starting and i have to press reset, so it never gets written to a logfile. The crash happend when i hotplugged an MP3 Jukebox and tried to mount it: Apr 3 12:32:26 antsrv1 kernel: umass1: ARCHOS ARCHOS USB2.0 (P4a), rev 2.00/11.01, addr 3 Apr 3 12:32:32 antsrv1 kernel: GEOM: create disk da1 dp=0xca5f0850 Apr 3 12:32:32 antsrv1 kernel: da1 at umass-sim1 bus 1 target 0 lun 0 Apr 3 12:32:32 antsrv1 kernel: da1: Fixed Direct Access SCSI-0 device Apr 3 12:32:32 antsrv1 kernel: da1: 1.000MB/s transfers Apr 3 12:32:32 antsrv1 kernel: da1: 19077MB (39070080 512 byte sectors: 255H 63S/T 2432C) Apr 3 12:33:03 antsrv1 login: ROOT LOGIN (root) ON ttyv0 Apr 3 12:38:08 antsrv1 syslogd: kernel boot file is /boot/kernel/kernel Apr 3 12:38:08 antsrv1 kernel: panic: ehci_abort_xfer: not in process context Apr 3 12:38:08 antsrv1 kernel: cpuid = 0; Apr 3 12:38:08 antsrv1 kernel: Apr 3 12:38:08 antsrv1 kernel: syncing disks, buffers remaining... 6418 6418 6418 6418 6418 6418 6418 6418 6418 6418 6418 6418 6418 6418 6418 6418 6418 6418 6418 6418 Apr 3 12:38:08 antsrv1 kernel: giving up on 3004 buffers Apr 3 12:38:08 antsrv1 kernel: Uptime: 22h44m54s Also, i get I/O-errors and the disk is inaccessible after having worked ok for days. Rebooting the machine fixes this. Heinrich ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Recommended USB 2.0 controller fr. 5.2+
On Mon, Apr 05, 2004 at 02:58:33PM +0200, Heinrich Rebehn wrote: > i am using a NEC USB2 controller and am just about to give up on using > it. I don't know if it's the controller, the disk or the ehci driver. > However, man ehci(4) states that "The driver is not finished and is > quite buggy." This seems to be true. I get all sorts of trouble ranging > from hangs during boot to system crashes. > I am reverting back to USB1 although its terribly slow. > > FreeBSD 5.2.1-RELEASE-p3 > > usb4: EHCI version 1.0 > usb4: companion controllers, 2 ports each: usb2 usb3 > usb4: on ehci0 > usb4: USB revision 2.0 > uhub4: NEC EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 > uhub4: 3 ports with 3 removable, self powered > > umass0: Maxtor OneTouch, rev 2.00/2.00, addr 2 > umass0: Get Max Lun not supported (STALLED) > GEOM: create disk da0 dp=0xc82ad450 > da0 at umass-sim0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-0 device > da0: 1.000MB/s transfers > da0: 239371MB (490232832 512 byte sectors: 255H 63S/T 30515C) > > Sorry i can't report anything posivtive on this. And I can't see anything wrong with your log. -- B.Walter BWCThttp://www.bwct.de [EMAIL PROTECTED] [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Recommended USB 2.0 controller fr. 5.2+
Bernd Walter wrote: On Mon, Mar 22, 2004 at 02:09:01PM +0100, Peter Schuller wrote: So - if I want a USB 2 controller that works fine with FreeBSD, which one shojuld I get / which chipset should it be using? To be more specific I found a controllre by Q-Tec (425U) wtih a Via VT6202 chipset. Anyone know if this will work? NEC Controllers are known to work. Never tested any of the VIA ones. Hi, i am using a NEC USB2 controller and am just about to give up on using it. I don't know if it's the controller, the disk or the ehci driver. However, man ehci(4) states that "The driver is not finished and is quite buggy." This seems to be true. I get all sorts of trouble ranging from hangs during boot to system crashes. I am reverting back to USB1 although its terribly slow. FreeBSD 5.2.1-RELEASE-p3 usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb2 usb3 usb4: on ehci0 usb4: USB revision 2.0 uhub4: NEC EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub4: 3 ports with 3 removable, self powered umass0: Maxtor OneTouch, rev 2.00/2.00, addr 2 umass0: Get Max Lun not supported (STALLED) GEOM: create disk da0 dp=0xc82ad450 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-0 device da0: 1.000MB/s transfers da0: 239371MB (490232832 512 byte sectors: 255H 63S/T 30515C) Sorry i can't report anything posivtive on this. Heinrich -- Heinrich Rebehn University of Bremen Physics / Electrical and Electronics Engineering - Department of Telecommunications - Phone : +49/421/218-4664 Fax :-3341 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Recommended USB 2.0 controller fr. 5.2+
On Mon, Mar 22, 2004 at 02:09:01PM +0100, Peter Schuller wrote: > > So - if I want a USB 2 controller that works fine with FreeBSD, which one > > shojuld I get / which chipset should it be using? > > To be more specific I found a controllre by Q-Tec (425U) wtih a Via VT6202 > chipset. Anyone know if this will work? NEC Controllers are known to work. Never tested any of the VIA ones. -- B.Walter BWCThttp://www.bwct.de [EMAIL PROTECTED] [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Recommended USB 2.0 controller fr. 5.2+
> So - if I want a USB 2 controller that works fine with FreeBSD, which one > shojuld I get / which chipset should it be using? To be more specific I found a controllre by Q-Tec (425U) wtih a Via VT6202 chipset. Anyone know if this will work? -- / Peter Schuller, InfiDyne Technologies HB PGP userID: 0xE9758B7D or 'Peter Schuller <[EMAIL PROTECTED]>' Key retrieval: Send an E-Mail to [EMAIL PROTECTED] E-Mail: [EMAIL PROTECTED] Web: http://www.scode.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Recommended USB 2.0 controller fr. 5.2+
Hello, I am planning on buying a PCI USB 2.0 controller for a machine running FreeBSD. The only experience I have so far is with my laptop which has some Intel controller that there are problems with, leading to controller shutdown when plugging in a USB 2.0 mass storage device. I read somewhere that there was a problem with that particular controller but I don't remember why. So - if I want a USB 2 controller that works fine with FreeBSD, which one shojuld I get / which chipset should it be using? Thanks! -- / Peter Schuller, InfiDyne Technologies HB PGP userID: 0xE9758B7D or 'Peter Schuller <[EMAIL PROTECTED]>' Key retrieval: Send an E-Mail to [EMAIL PROTECTED] E-Mail: [EMAIL PROTECTED] Web: http://www.scode.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
