On Fri, 4 Jul 2003, Antonio Fiol wrote: > Hello, > > Following Paul's advice, I installed kernel 2.4.74, and... it does not > work correctly either. In fact, I believe it is a bit worse. > > In the beginning, there was a system log...
> Jul 4 10:58:50 devmaster kernel: uhci-hcd 0000:00:1f.2: Intel Corp. > 82801BA/BAM USB (Hub > Jul 4 10:58:50 devmaster kernel: uhci-hcd 0000:00:1f.2: irq 11, io base > 0000d000 > Jul 4 10:58:50 devmaster kernel: Please use the 'usbfs' filetype > instead, the 'usbdevfs' name is deprecated. > Jul 4 10:58:50 devmaster kernel: uhci-hcd 0000:00:1f.2: new USB bus > registered, assigned bus number 1 > Jul 4 10:58:50 devmaster kernel: drivers/usb/host/uhci-hcd.c: detected > 2 ports > Jul 4 10:58:50 devmaster kernel: uhci-hcd 0000:00:1f.2: root hub device > address 1 > Jul 4 10:58:50 devmaster kernel: usb usb1: new device strings: Mfr=3, > Product=2, SerialNumber=1 This was your first USB controller. Notice that it has PCI address 00:1f.2, io base address d000, and is named usb1. > Jul 4 10:58:50 devmaster kernel: uhci-hcd 0000:00:1f.4: Intel Corp. > 82801BA/BAM USB (Hub > Jul 4 10:58:50 devmaster kernel: uhci-hcd 0000:00:1f.4: irq 9, io base > 0000d800 > Jul 4 10:58:50 devmaster kernel: uhci-hcd 0000:00:1f.4: new USB bus > registered, assigned bus number 2 > Jul 4 10:58:50 devmaster kernel: drivers/usb/host/uhci-hcd.c: detected > 2 ports > Jul 4 10:58:50 devmaster kernel: uhci-hcd 0000:00:1f.4: root hub device > address 1 > Jul 4 10:58:50 devmaster kernel: usb usb2: new device strings: Mfr=3, > Product=2, SerialNumber=1 This was your second USB controller. It has PCI address 00:1f.4, io base address d800, and is named usb2. > Jul 4 10:58:50 devmaster kernel: drivers/usb/host/uhci-hcd.c: d000: > suspend_hc > Jul 4 10:58:50 devmaster kernel: drivers/usb/host/uhci-hcd.c: d800: > suspend_hc Both controllers were suspended because nothing was plugged in. That's why you have 2 suspend lines with no wakeup in the middle. > Jul 4 10:58:50 devmaster kernel: drivers/usb/host/uhci-hcd.c: d800: > wakeup_hc > Jul 4 10:58:50 devmaster kernel: drivers/usb/host/uhci-hcd.c: d800: > suspend_hc > Jul 4 10:58:50 devmaster kernel: drivers/usb/host/uhci-hcd.c: d800: > wakeup_hc > [... i am amazed about having 2 suspend lines one after the other, w/o a > wakeup in the middle...] > [... i have 31 lines in the same second with suspend or wakeup...] The second controller is misbehaving. It is waking up without anything being plugged in. This looks a lot like the problem that Paul experienced, and I wouldn't be surprised to find it has the same cause. > [... latre, I plug a device (usb-storage 128M memory stick) ...] > Jul 4 11:05:14 devmaster kernel: drivers/usb/host/uhci-hcd.c: d000: > wakeup_hc > Jul 4 11:05:14 devmaster kernel: hub 1-0:0: port 1, status 101, change > 1, 12 Mb/s As you can see, the memory stick was plugged in to the first controller, the one that was working okay. > [... I see that the sd_mod module has not been loaded automagically, so > I load it by hand...] > Jul 4 11:05:38 devmaster kernel: SCSI device sda: 252160 512-byte hdwr > sectors (129 MB) > Jul 4 11:05:38 devmaster kernel: sda: test WP failed, assume Write Enabled > Jul 4 11:05:38 devmaster kernel: sda: asking for cache data failed > Jul 4 11:05:38 devmaster kernel: sda: assuming drive cache: write through > Jul 4 11:05:38 devmaster kernel: /dev/scsi/host2/bus0/target0/lun0: p1 > [... up to here, it seems normal. The following lines do not seem quite > normal to me... ] > Jul 4 11:05:38 devmaster kernel: devfs_put(cbc38f00): poisoned pointer > Jul 4 11:05:38 devmaster kernel: Forcing Oops > Jul 4 11:05:38 devmaster kernel: ------------[ cut here ]------------ > Jul 4 11:05:38 devmaster kernel: kernel BUG at fs/devfs/base.c:921! > Jul 4 11:05:38 devmaster kernel: invalid operand: 0000 [#1] > Jul 4 11:05:38 devmaster kernel: CPU: 0 > Jul 4 11:05:38 devmaster kernel: EIP: 0060:[devfs_put+250/263] > Not tainted > Jul 4 11:05:38 devmaster kernel: EFLAGS: 00010282 > Jul 4 11:05:38 devmaster kernel: eax: 0000000d ebx: cbc38f00 ecx: > 00000001 edx: c0333af8 > Jul 4 11:05:38 devmaster kernel: esi: c03b74a0 edi: 00000021 ebp: > 00000000 esp: cf93bed8 > Jul 4 11:05:38 devmaster kernel: ds: 007b es: 007b ss: 0068 > Jul 4 11:05:38 devmaster kernel: Process devfsd (pid: 68, > threadinfo=cf93a000 task=cfcec780) > Jul 4 11:05:38 devmaster kernel: Stack: c02f31c4 c02e0160 cbc38f00 > 00000000 c018d9e1 cbc38f00 c1359c1f 00000001 > Jul 4 11:05:38 devmaster kernel: c1359c1f cf93bf50 c1359800 > ca74942c cbc38f00 00000021 00000000 000003ff > Jul 4 11:05:38 devmaster kernel: 00000000 00000000 00000001 > 00000000 cfcec780 c0118165 00000000 00000000 > Jul 4 11:05:38 devmaster kernel: Call Trace: [devfsd_read+745/1183] > [default_wake_function+0/46] [update_process_times+70/82] > [default_wake_function > +0/46] [do_timer+223/228] [rcu_process_callbacks+125/247] > [vfs_read+208/309] [sys_read+66/99] [syscall_call+7/11] > Jul 4 11:05:38 devmaster kernel: Code: 0f 0b 99 03 d2 31 2f c0 e9 19 ff > ff ff 55 57 56 53 83 ec 10 > Jul 4 11:05:38 devmaster kernel: <5>Attached scsi removable disk sda > at scsi2, channel 0, id 0, lun 0 > [... should I trust the device?? ... I do not ...] That's not normal at all. However, it's a separate unrelated issue; it looks like a problem with devfs. > [... I prepare the beginning of this mail ...] > [... then I unplug the device, not having even mounted it ...] > Jul 4 11:19:32 devmaster kernel: hub 1-0:0: port 1, status 100, change > 3, 12 Mb/s > Jul 4 11:19:32 devmaster kernel: usb 1-1: USB disconnect, address 2 > Jul 4 11:19:32 devmaster kernel: usb 1-1: unregistering interfaces > Jul 4 11:19:32 devmaster kernel: drivers/usb/core/usb.c: usb_hotplug > Jul 4 11:19:32 devmaster kernel: usb 1-1: unregistering device > Jul 4 11:19:32 devmaster kernel: drivers/usb/core/usb.c: usb_hotplug > Jul 4 11:19:32 devmaster kernel: hub 1-0:0: port 1 enable change, > status 100 > Jul 4 11:19:32 devmaster kernel: drivers/usb/host/uhci-hcd.c: d000: > suspend_hc > Jul 4 11:19:32 devmaster kernel: drivers/usb/host/uhci-hcd.c: d800: > suspend_hc > Jul 4 11:19:33 devmaster kernel: drivers/usb/host/uhci-hcd.c: d800: > wakeup_hc And then the first controller was suspended, as it should be, while the second controller continued to misbehave. Do you have 2 USB connectors on your computer? If not, then quite likely your problem is the same as Paul's. We could change the part of Paul's patch that checks for affected motherboards so that it would recognize your chipset as well as the PIIX4. Alan Stern ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
