Bug#317982: udev: Does not properly add/remove usb disk drives
On Sun, Jul 17, 2005 at 01:30:41PM +0200, Kurt Roeckx wrote: On Sun, 2005-07-17 at 09:44 +0200, Kurt Roeckx wrote: Horms [EMAIL PROTECTED] wrote: Hi Kurt, Could you please send the output of lsmod and lspci -v, hopefully your hardware is reasonably common and i can reproduce this problem. However, a quick fix might be to try the 2.6.11 kernels in unstable. I'll try the 2.6.11 kernel later. The 2.6.11-7 kernel seems to work without problems. Thanks, that is valuable information. I'll try and isolate the fix (please feel free to help there), but if its a massive backport its never going to be done. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#317982: udev: Does not properly add/remove usb disk drives
On Sun, 2005-07-17 at 09:44 +0200, Kurt Roeckx wrote: Horms [EMAIL PROTECTED] wrote: Hi Kurt, Could you please send the output of lsmod and lspci -v, hopefully your hardware is reasonably common and i can reproduce this problem. However, a quick fix might be to try the 2.6.11 kernels in unstable. I'll try the 2.6.11 kernel later. The 2.6.11-7 kernel seems to work without problems. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#317982: udev: Does not properly add/remove usb disk drives
Horms [EMAIL PROTECTED] wrote: Hi Kurt, Could you please send the output of lsmod and lspci -v, hopefully your hardware is reasonably common and i can reproduce this problem. However, a quick fix might be to try the 2.6.11 kernels in unstable. lsmod: Module Size Used by i830 78596 3 ndiswrapper 138612 0 ipv6 264740 8 ds 18756 2 thermal12656 0 fan 3980 0 button 6296 0 processor 17264 1 thermal ac 4812 0 battery 9388 0 af_packet 22568 6 pcspkr 3592 0 rtc12760 0 parport_pc 36900 0 parport41800 1 parport_pc 8139cp 20672 0 snd_intel8x0m 20264 0 snd_intel8x0 36460 0 snd_ac97_codec 69988 2 snd_intel8x0m,snd_intel8x0 snd_pcm98728 2 snd_intel8x0m,snd_intel8x0 snd_timer 25732 1 snd_pcm snd_page_alloc 11752 3 snd_intel8x0m,snd_intel8x0,snd_pcm gameport4704 1 snd_intel8x0 snd_mpu401_uart 7968 1 snd_intel8x0 snd_rawmidi25124 1 snd_mpu401_uart snd_seq_device 8200 1 snd_rawmidi snd57156 8 snd_intel8x0m,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer,snd_mpu401_uart,snd_rawmidi,snd_seq_device pci_hotplug34640 0 intel_agp 22816 1 uhci_hcd 33136 0 usbcore 119012 4 ndiswrapper,uhci_hcd eth139421576 0 i810_audio 37588 0 ac97_codec 18956 1 i810_audio soundcore 10336 2 snd,i810_audio 8139too26112 0 mii 5120 2 8139cp,8139too ohci1394 35492 0 yenta_socket 21728 1 pcmcia_core70868 2 ds,yenta_socket agpgart34664 4 intel_agp tsdev 7392 0 mousedev 10476 2 joydev 9984 0 evdev 9600 0 capability 4520 0 commoncap 7232 1 capability sr_mod 17316 0 sbp2 24392 0 ieee1394 111512 3 eth1394,ohci1394,sbp2 psmouse20360 0 ide_cd 42656 0 cdrom 40732 2 sr_mod,ide_cd ext3 127240 1 jbd62616 1 ext3 mbcache 9348 1 ext3 ide_generic 1408 0 piix 13440 1 ide_disk 19296 3 ide_core 139940 4 ide_cd,ide_generic,piix,ide_disk sd_mod 21728 0 ata_piix8132 0 libata 41700 1 ata_piix scsi_mod 125228 4 sr_mod,sbp2,sd_mod,libata unix 28756 518 font8320 0 vesafb 6656 0 cfbcopyarea 3872 1 vesafb cfbimgblt 3040 1 vesafb cfbfillrect 3776 1 vesafb lspci -v :00:00.0 Host bridge: Intel Corp. 82830 830 Chipset Host Bridge (rev 03) Subsystem: Asustek Computer, Inc.: Unknown device 1402 Flags: bus master, fast devsel, latency 0 Memory at unassigned (32-bit, prefetchable) Capabilities: [40] #09 [2105] :00:02.0 VGA compatible controller: Intel Corp. 82830 CGC [Chipset Graphics Controller] (rev 03) (prog-if 00 [VGA]) Subsystem: Asustek Computer, Inc.: Unknown device 1492 Flags: bus master, fast devsel, latency 0, IRQ 10 Memory at f000 (32-bit, prefetchable) [size=128M] Memory at e780 (32-bit, non-prefetchable) [size=512K] Capabilities: [d0] Power Management version 1 :00:02.1 Display controller: Intel Corp. 82830 CGC [Chipset Graphics Controller] Subsystem: Asustek Computer, Inc.: Unknown device 1492 Flags: bus master, fast devsel, latency 0 Memory at e800 (32-bit, prefetchable) [disabled] [size=128M] Memory at e700 (32-bit, non-prefetchable) [disabled] [size=512K] Capabilities: [d0] Power Management version 1 :00:1d.0 USB Controller: Intel Corp. 82801CA/CAM USB (Hub #1) (rev 01) (prog-if 00 [UHCI]) Subsystem: Asustek Computer, Inc.: Unknown device 1402 Flags: bus master, medium devsel, latency 0, IRQ 10 I/O ports at d800 [size=32] :00:1d.1 USB Controller: Intel Corp. 82801CA/CAM USB (Hub #2) (rev 01) (prog-if 00 [UHCI]) Subsystem: Asustek Computer, Inc.: Unknown device 1402 Flags: bus master, medium devsel, latency 0, IRQ 9 I/O ports at d400 [size=32] :00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev 41) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=32 I/O behind bridge: c000-cfff Memory behind bridge: e380-e6ff :00:1f.0
Bug#317982: udev: Does not properly add/remove usb disk drives
[EMAIL PROTECTED] (Marco d'Itri) wrote: On Jul 12, Kurt Roeckx [EMAIL PROTECTED] wrote: So I guess my hardware isn't sending the notification to the kernel, or the kernel isn't listening for it, and the kernel detects that it's plugged in at the moment I touch the device (try to read from it). So this is probably more a hardware and/or kernel problem. The kernel can atleast detect that it's there or not and maybe should poll instead of expecting to be told it was changed. Could you please clone and reassign this as a wishlist bug if it doesn't exist yet? The need for all_partitions is a fundamental design limitation of some hardware devices, and there is nothing you can do about it. Please try again with an appropriate all_partitions rule. When I use that, the kernel does detect the insertion of the CF card around the moment I plug it in. udev creates the /dev/sda1 properly, but I get the following messages from the kernel too: usb 1-2: control timeout on ep0in usb 1-2: control timeout on ep0in And when trying to mount /dev/sda1, the mount hangs in kernel space. When not using that rule I never get that problem. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#317982: udev: Does not properly add/remove usb disk drives
reassign 317982 kernel thanks On Jul 16, Kurt Roeckx [EMAIL PROTECTED] wrote: When I use that, the kernel does detect the insertion of the CF card around the moment I plug it in. udev creates the /dev/sda1 properly, but I get the following messages from the kernel too: usb 1-2: control timeout on ep0in usb 1-2: control timeout on ep0in I understand that these messages may be normal. And when trying to mount /dev/sda1, the mount hangs in kernel space. This looks like a kernel bug. When not using that rule I never get that problem. mount should not hang anyway. -- ciao, Marco signature.asc Description: Digital signature
Bug#317982: udev: Does not properly add/remove usb disk drives
reassign 317982 kernel-source-2.6.8 thanks On Sat, Jul 16, 2005 at 08:14:04PM +0200, Marco d'Itri wrote: reassign 317982 kernel thanks On Jul 16, Kurt Roeckx [EMAIL PROTECTED] wrote: When I use that, the kernel does detect the insertion of the CF card around the moment I plug it in. udev creates the /dev/sda1 properly, but I get the following messages from the kernel too: usb 1-2: control timeout on ep0in usb 1-2: control timeout on ep0in I understand that these messages may be normal. And when trying to mount /dev/sda1, the mount hangs in kernel space. This looks like a kernel bug. When not using that rule I never get that problem. mount should not hang anyway. Hi Marco, When reassigning bugs to the kernel, it would be totally awsome if you could determine which kernel-source package the kernel was derived from, and reassign the bug to that package. Hi Kurt, Could you please send the output of lsmod and lspci -v, hopefully your hardware is reasonably common and i can reproduce this problem. However, a quick fix might be to try the 2.6.11 kernels in unstable. Thanks -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#317982: udev: Does not properly add/remove usb disk drives
On Tue, 2005-07-12 at 21:01 +0200, Kurt Roeckx wrote: [EMAIL PROTECTED] (Marco d'Itri) wrote: On Jul 12, Kurt Roeckx [EMAIL PROTECTED] wrote: It also not creating /dev/sda1 at the time I plug in the CF card while the kernel does detect that I plug it in. It only seems to detect it after 5 minutes or something. Did you read README.Debian about all_partitions? So I guess my hardware isn't sending the notification to the kernel, or the kernel isn't listening for it, and the kernel detects that it's plugged in at the moment I touch the device (try to read from it). So this is probably more a hardware and/or kernel problem. The kernel can atleast detect that it's there or not and maybe should poll instead of expecting to be told it was changed. Could you please clone and reassign this as a wishlist bug if it doesn't exist yet? I guess I should explain this a little better. If I read from /dev/sda, the kernel will detect that the CF card is there and create the partition and things like that. At that point the kernel knows about an sda1 while udev does not create it. So in any case it looks like udev is not creating sda1 when it should have, and I doubt that it's going to work properly with any hardware. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#317982: udev: Does not properly add/remove usb disk drives
Package: udev Version: 0.056-3 Severity: serious Hi, udev seems to be not working properly when I plug in/out my usb CF/SM/SD card reader, plug it out, and plug it in again. After plugging it out, some devices seem to be left, after plugging it in some aren't created. After some time it seems to try to correct itself, but sometimes removes drives that really still are there. It also not creating /dev/sda1 at the time I plug in the CF card while the kernel does detect that I plug it in. It only seems to detect it after 5 minutes or something. Example: ~$ ls -l /dev/sd* brw-r- 1 root hal 8, 0 Jul 12 19:04 /dev/sda brw-r- 1 root hal 8, 1 Jul 12 19:06 /dev/sda1 brw-r- 1 root hal 8, 16 Jul 12 19:00 /dev/sdb brw-r- 1 root hal 8, 48 Jul 12 19:00 /dev/sdd brw-r- 1 root hal 8, 64 Jul 12 19:00 /dev/sde Then I plug things out, and get: brw-r- 1 root hal 8, 0 Jul 12 19:04 /dev/sda dmesg showed: usb 1-2: USB disconnect, address 6 It's still showing sda for some reason while it does not exists. If I know plug it in dmesg showed: usb 1-2: new full speed USB device using address 7 scsi4 : SCSI emulation for USB Mass Storage devices Vendor: USB CRW Model: CF Card CF Rev: 1.4F Type: Direct-Access ANSI SCSI revision: 02 SCSI device sda: 1006992 512-byte hdwr sectors (516 MB) sda: assuming Write Enabled sda: assuming drive cache: write through /dev/scsi/host4/bus0/target0/lun0: p1 Attached scsi removable disk sda at scsi4, channel 0, id 0, lun 0 Vendor: USB CRW Model: MS card MS Rev: 1.4F Type: Direct-Access ANSI SCSI revision: 02 Attached scsi removable disk sdb at scsi4, channel 0, id 0, lun 1 Vendor: USB CRW Model: SM card SM Rev: 1.4F Type: Direct-Access ANSI SCSI revision: 02 Attached scsi removable disk sdd at scsi4, channel 0, id 0, lun 2 Vendor: USB CRW Model: SD card MMC/SD Rev: 1.4F Type: Direct-Access ANSI SCSI revision: 02 Attached scsi removable disk sde at scsi4, channel 0, id 0, lun 3 USB Mass Storage device found at 7 And I see: brw-r- 1 root hal 8, 0 Jul 12 19:04 /dev/sda Which is not what I expect. I get to expect the input from the first time again. After about 1 minutes I get: brw-r- 1 root hal 8, 16 Jul 12 19:11 /dev/sdb brw-r- 1 root hal 8, 48 Jul 12 19:11 /dev/sdd brw-r- 1 root hal 8, 64 Jul 12 19:11 /dev/sde Which really isn't what I want, now sda is completly gone. Waiting 2 minutes, I get: brw-r- 1 root hal 8, 0 Jul 12 19:13 /dev/sda brw-r- 1 root hal 8, 16 Jul 12 19:11 /dev/sdb brw-r- 1 root hal 8, 48 Jul 12 19:11 /dev/sdd brw-r- 1 root hal 8, 64 Jul 12 19:11 /dev/sde Which is better, but it's still missing sda1 After waiting for some more I get: brw-r- 1 root hal 8, 0 Jul 12 19:13 /dev/sda brw-r- 1 root hal 8, 1 Jul 12 19:15 /dev/sda1 brw-r- 1 root hal 8, 16 Jul 12 19:11 /dev/sdb brw-r- 1 root hal 8, 48 Jul 12 19:11 /dev/sdd brw-r- 1 root hal 8, 64 Jul 12 19:11 /dev/sde Which is what I expect to get at the moment I plugged it in, not 5 minutes after plugging it in. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#317982: udev: Does not properly add/remove usb disk drives
severity 317982 normal thanks On Jul 12, Kurt Roeckx [EMAIL PROTECTED] wrote: udev seems to be not working properly when I plug in/out my usb CF/SM/SD card reader, plug it out, and plug it in again. After plugging it out, some devices seem to be left, after plugging it in some aren't created. Which kernel version are you using? Are you using custom rules? After some time it seems to try to correct itself, but sometimes removes drives that really still are there. Are you sure that you do not have any other program installed which could interfere? It also not creating /dev/sda1 at the time I plug in the CF card while the kernel does detect that I plug it in. It only seems to detect it after 5 minutes or something. Did you read README.Debian about all_partitions? -- ciao, Marco signature.asc Description: Digital signature
Bug#317982: udev: Does not properly add/remove usb disk drives
[EMAIL PROTECTED] (Marco d'Itri) wrote: On Jul 12, Kurt Roeckx [EMAIL PROTECTED] wrote: udev seems to be not working properly when I plug in/out my usb CF/SM/SD card reader, plug it out, and plug it in again. After plugging it out, some devices seem to be left, after plugging it in some aren't created. Which kernel version are you using? I'm using kernel-image-2.6.8-2-686 2.6.8-16 (the one in sarge) Are you using custom rules? No, and I was not aware that I was supposed to create custom rules to get this working. After some time it seems to try to correct itself, but sometimes removes drives that really still are there. Are you sure that you do not have any other program installed which could interfere? I would have no idea which programs could possible interfere, and this is mostly a basic sarge install using the desktop task, only some small unrelated things got added. If there are programs that can interfere with this, you should either fix it so it works or Conflict with it. It also not creating /dev/sda1 at the time I plug in the CF card while the kernel does detect that I plug it in. It only seems to detect it after 5 minutes or something. Did you read README.Debian about all_partitions? So I guess my hardware isn't sending the notification to the kernel, or the kernel isn't listening for it, and the kernel detects that it's plugged in at the moment I touch the device (try to read from it). So this is probably more a hardware and/or kernel problem. The kernel can atleast detect that it's there or not and maybe should poll instead of expecting to be told it was changed. Could you please clone and reassign this as a wishlist bug if it doesn't exist yet? Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#317982: udev: Does not properly add/remove usb disk drives
On Jul 12, Kurt Roeckx [EMAIL PROTECTED] wrote: So I guess my hardware isn't sending the notification to the kernel, or the kernel isn't listening for it, and the kernel detects that it's plugged in at the moment I touch the device (try to read from it). So this is probably more a hardware and/or kernel problem. The kernel can atleast detect that it's there or not and maybe should poll instead of expecting to be told it was changed. Could you please clone and reassign this as a wishlist bug if it doesn't exist yet? The need for all_partitions is a fundamental design limitation of some hardware devices, and there is nothing you can do about it. Please try again with an appropriate all_partitions rule. -- ciao, Marco signature.asc Description: Digital signature
