[Bug 335475] New: Incorrectly treating mass storage digital camera ( lumix tz3) - hald problem
https://bugzilla.novell.com/show_bug.cgi?id=335475#c1 Summary: Incorrectly treating mass storage digital camera (lumix tz3) - hald problem Product: openSUSE 10.3 Version: Final Platform: i586 OS/Version: openSUSE 10.3 Status: NEW Severity: Major Priority: P5 - None Component: Hotplug AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: vmicho@gmail.com QAContact: qa@suse.de Found By: --- Hi I had lots of trouble with this problem. I have Panasonic lumix dmc-tz3 digital camera (this will surely apply to other similar cameras like TZ2, TZ1, LX2 ..), I'm using KDE. The problem is when I plug the camera into USB,I cannot access any filen in the camera. I searched on Internet and I got interesting conclusion: - it is mass storage camera (you can see my experiment at the end and also the messages) - it works correctly (in windows, it is indeed detected as mass storage without any drivers needed. Also lots of people say it works well in other linuxes like ubuntu, mandriva and probably in older opensuse) So I looked at the kernel messages and I now know there is some problem with HALD who is umounting sdb1 just after it's mounted (sdaX are my internal ATA hard drives). Unfortunately I couldn't reproduce that message today. Instead I'm joining several messages I got today from multiple USB cable plugs to camera and one plug of my USB stick. So in conclusion there is some weirg HALD configuration for this and it seems it treats my camera both like usb mass storage AND as a camera (really dunno hot it works) Hope this gets fixed soon. Thanks. Here I post some log messages: ------------------------------ *** USB memory stick: *** Oct 20 10:45:36 suse kernel: usb 4-5: new high speed USB device using ehci_hcd and address 3 Oct 20 10:45:36 suse kernel: usb 4-5: new device found, idVendor=4146, idProduct=ba63 Oct 20 10:45:36 suse kernel: usb 4-5: new device strings: Mfr=1, Product=2, SerialNumber=3 Oct 20 10:45:36 suse kernel: usb 4-5: Product: USB Mass Storage Device Oct 20 10:45:36 suse kernel: usb 4-5: Manufacturer: PRETEC Technology Oct 20 10:45:36 suse kernel: usb 4-5: SerialNumber: 39012f9365c4db Oct 20 10:45:36 suse kernel: usb 4-5: configuration #1 chosen from 1 choice Oct 20 10:45:36 suse kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 Oct 20 10:45:36 suse kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx Oct 20 10:45:36 suse kernel: Initializing USB Mass Storage driver... Oct 20 10:45:36 suse kernel: scsi2 : SCSI emulation for USB Mass Storage devices Oct 20 10:45:36 suse kernel: usb-storage: device found at 3 Oct 20 10:45:36 suse kernel: usb-storage: waiting for device to settle before scanning Oct 20 10:45:36 suse kernel: usbcore: registered new interface driver usb-storage Oct 20 10:45:36 suse kernel: USB Mass Storage support registered. Oct 20 10:45:37 suse kernel: scsi 2:0:0:0: Direct-Access -Pretec 04GB 2.10 PQ: 0 ANSI: 2 Oct 20 10:45:37 suse kernel: sd 2:0:0:0: [sdb] 8060927 512-byte hardware sectors (4127 MB) Oct 20 10:45:37 suse kernel: sd 2:0:0:0: [sdb] Write Protect is off Oct 20 10:45:37 suse kernel: sd 2:0:0:0: [sdb] Mode Sense: 00 00 00 00 Oct 20 10:45:37 suse kernel: sd 2:0:0:0: [sdb] Assuming drive cache: write through Oct 20 10:45:37 suse kernel: sd 2:0:0:0: [sdb] 8060927 512-byte hardware sectors (4127 MB) Oct 20 10:45:37 suse kernel: sd 2:0:0:0: [sdb] Write Protect is off Oct 20 10:45:37 suse kernel: sd 2:0:0:0: [sdb] Mode Sense: 00 00 00 00 Oct 20 10:45:37 suse kernel: sd 2:0:0:0: [sdb] Assuming drive cache: write through Oct 20 10:45:37 suse kernel: sdb: sdb1 Oct 20 10:45:37 suse kernel: sd 2:0:0:0: [sdb] Attached SCSI removable disk Oct 20 10:45:37 suse kernel: sd 2:0:0:0: Attached scsi generic sg2 type 0 Oct 20 10:45:37 suse kernel: usb-storage: device scan complete Oct 20 10:45:39 suse hald: mounted /dev/sdb1 on behalf of uid 1000 ls -la /dev/sd* brw-r----- 1 root disk 8, 0 2007-10-20 09:51 /dev/sda brw-r----- 1 root disk 8, 1 2007-10-20 09:51 /dev/sda1 brw-r----- 1 root disk 8, 10 2007-10-20 09:51 /dev/sda10 brw-r----- 1 root disk 8, 11 2007-10-20 09:51 /dev/sda11 brw-r----- 1 root disk 8, 2 2007-10-20 09:51 /dev/sda2 brw-r----- 1 root disk 8, 3 2007-10-20 09:51 /dev/sda3 brw-r----- 1 root disk 8, 5 2007-10-20 09:51 /dev/sda5 brw-r----- 1 root disk 8, 6 2007-10-20 09:51 /dev/sda6 brw-r----- 1 root disk 8, 7 2007-10-20 09:51 /dev/sda7 brw-r----- 1 root disk 8, 8 2007-10-20 09:51 /dev/sda8 brw-r----- 1 root disk 8, 9 2007-10-20 09:51 /dev/sda9 brw-r----- 1 root disk 8, 16 2007-10-20 10:45 /dev/sdb brw-r----- 1 root disk 8, 17 2007-10-20 10:45 /dev/sdb1 Oct 20 10:47:46 suse hald: unmounted /dev/sdb1 from '/media/MojeUSB' on behalf of uid 1000 Oct 20 10:48:09 suse kernel: usb 4-5: USB disconnect, address 3 *** Panasonic DMC-TZ3: *** Oct 20 10:49:12 suse kernel: usb 2-1: new full speed USB device using uhci_hcd and address 2 Oct 20 10:49:13 suse kernel: usb 2-1: new device found, idVendor=04da, idProduct=2372 Oct 20 10:49:13 suse kernel: usb 2-1: new device strings: Mfr=1, Product=2, SerialNumber=0 Oct 20 10:49:13 suse kernel: usb 2-1: Product: DMC-TZ3 Oct 20 10:49:13 suse kernel: usb 2-1: Manufacturer: Panasonic Oct 20 10:49:13 suse kernel: usb 2-1: configuration #1 chosen from 1 choice Oct 20 10:49:13 suse kernel: scsi3 : SCSI emulation for USB Mass Storage devices Oct 20 10:49:13 suse kernel: usb-storage: device found at 2 Oct 20 10:49:13 suse kernel: usb-storage: waiting for device to settle before scanning Oct 20 10:49:14 suse kernel: scsi 3:0:0:0: Direct-Access MATSHITA DMC-TZ3 0100 PQ: 0 ANSI: 2 Oct 20 10:49:14 suse kernel: sd 3:0:0:0: [sdb] 1983999 512-byte hardware sectors (1016 MB) Oct 20 10:49:14 suse kernel: sd 3:0:0:0: [sdb] Write Protect is off Oct 20 10:49:14 suse kernel: sd 3:0:0:0: [sdb] Mode Sense: 04 00 00 00 Oct 20 10:49:14 suse kernel: sd 3:0:0:0: [sdb] Assuming drive cache: write through Oct 20 10:49:14 suse kernel: sd 3:0:0:0: [sdb] 1983999 512-byte hardware sectors (1016 MB) Oct 20 10:49:14 suse kernel: sd 3:0:0:0: [sdb] Write Protect is off Oct 20 10:49:14 suse kernel: sd 3:0:0:0: [sdb] Mode Sense: 04 00 00 00 Oct 20 10:49:14 suse kernel: sd 3:0:0:0: [sdb] Assuming drive cache: write through Oct 20 10:49:14 suse kernel: sdb: sdb1 Oct 20 10:49:14 suse kernel: sd 3:0:0:0: [sdb] Attached SCSI removable disk Oct 20 10:49:14 suse kernel: sd 3:0:0:0: Attached scsi generic sg2 type 0 Oct 20 10:49:14 suse kernel: usb-storage: device scan complete ls -la /dev/sd* brw-r----- 1 root disk 8, 0 2007-10-20 09:51 /dev/sda brw-r----- 1 root disk 8, 1 2007-10-20 09:51 /dev/sda1 brw-r----- 1 root disk 8, 10 2007-10-20 09:51 /dev/sda10 brw-r----- 1 root disk 8, 11 2007-10-20 09:51 /dev/sda11 brw-r----- 1 root disk 8, 2 2007-10-20 09:51 /dev/sda2 brw-r----- 1 root disk 8, 3 2007-10-20 09:51 /dev/sda3 brw-r----- 1 root disk 8, 5 2007-10-20 09:51 /dev/sda5 brw-r----- 1 root disk 8, 6 2007-10-20 09:51 /dev/sda6 brw-r----- 1 root disk 8, 7 2007-10-20 09:51 /dev/sda7 brw-r----- 1 root disk 8, 8 2007-10-20 09:51 /dev/sda8 brw-r----- 1 root disk 8, 9 2007-10-20 09:51 /dev/sda9 No sdb/sdb1 devices are created KDE asks BOTH to open usb drive and camera (two dialogs at once) Oct 20 10:53:14 suse kernel: usb 2-1: usbfs: USBDEVFS_CONTROL failed cmd kio_kamera rqt 33 rq 102 len 0 ret -71 Oct 20 10:53:15 suse syslog-ng[2250]: last message repeated 3 times Oct 20 10:53:15 suse kernel: usb 2-1: USB disconnect, address 2 *** Panasonic DMC-TZ3, try 2 *** I got twice this output. Note that weird (at least for me) message about accessing /block/sdb. Oct 20 10:53:40 suse kernel: usb 2-1: new full speed USB device using uhci_hcd and address 3 Oct 20 10:53:40 suse kernel: usb 2-1: new device found, idVendor=04da, idProduct=2372 Oct 20 10:53:40 suse kernel: usb 2-1: new device strings: Mfr=1, Product=2, SerialNumber=0 Oct 20 10:53:40 suse kernel: usb 2-1: Product: DMC-TZ3 Oct 20 10:53:40 suse kernel: usb 2-1: Manufacturer: Panasonic Oct 20 10:53:40 suse kernel: usb 2-1: configuration #1 chosen from 1 choice Oct 20 10:53:40 suse kernel: scsi4 : SCSI emulation for USB Mass Storage devices Oct 20 10:53:40 suse kernel: usb-storage: device found at 3 Oct 20 10:53:40 suse kernel: usb-storage: waiting for device to settle before scanning Oct 20 10:53:41 suse kernel: scsi 4:0:0:0: Direct-Access MATSHITA DMC-TZ3 0100 PQ: 0 ANSI: 2 Oct 20 10:53:41 suse kernel: sd 4:0:0:0: [sdb] 1983999 512-byte hardware sectors (1016 MB) Oct 20 10:53:41 suse kernel: sd 4:0:0:0: [sdb] Write Protect is off Oct 20 10:53:41 suse kernel: sd 4:0:0:0: [sdb] Mode Sense: 04 00 00 00 Oct 20 10:53:41 suse kernel: sd 4:0:0:0: [sdb] Assuming drive cache: write through Oct 20 10:53:41 suse kernel: sd 4:0:0:0: [sdb] READ CAPACITY failed Oct 20 10:53:41 suse kernel: sd 4:0:0:0: [sdb] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK Oct 20 10:53:41 suse kernel: sd 4:0:0:0: [sdb] Sense not available. Oct 20 10:53:42 suse kernel: sd 4:0:0:0: [sdb] Write Protect is off Oct 20 10:53:42 suse kernel: sd 4:0:0:0: [sdb] Mode Sense: 00 00 00 00 Oct 20 10:53:42 suse kernel: sd 4:0:0:0: [sdb] Assuming drive cache: write through Oct 20 10:53:42 suse kernel: sd 4:0:0:0: [sdb] READ CAPACITY failed Oct 20 10:53:42 suse kernel: sd 4:0:0:0: [sdb] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK Oct 20 10:53:42 suse kernel: sd 4:0:0:0: [sdb] Sense not available. Oct 20 10:53:42 suse kernel: sd 4:0:0:0: [sdb] Write Protect is off Oct 20 10:53:42 suse kernel: sd 4:0:0:0: [sdb] Mode Sense: 00 00 00 00 Oct 20 10:53:42 suse kernel: sd 4:0:0:0: [sdb] Assuming drive cache: write through Oct 20 10:53:42 suse kernel: sd 4:0:0:0: [sdb] Attached SCSI removable disk Oct 20 10:53:42 suse kernel: sd 4:0:0:0: Attached scsi generic sg2 type 0 Oct 20 10:53:42 suse kernel: usb-storage: device scan complete Oct 20 10:53:42 suse usb_id[4436]: usb_id: unable to access '/block/sdb' Oct 20 10:53:42 suse scsi_id[4437]: scsi_id: unable to access '/block/sdb' KDE asks to open camera (system:/media/camera) Again, no sdb device is created. Oct 20 10:55:21 suse kernel: usb 2-1: USB disconnect, address 3 *** Panasonic DMC-TZ3, try 2 *** I got several times this output. Oct 20 10:55:44 suse kernel: usb 2-1: new full speed USB device using uhci_hcd and address 4 Oct 20 10:55:44 suse kernel: usb 2-1: new device found, idVendor=04da, idProduct=2372 Oct 20 10:55:44 suse kernel: usb 2-1: new device strings: Mfr=1, Product=2, SerialNumber=0 Oct 20 10:55:44 suse kernel: usb 2-1: Product: DMC-TZ3 Oct 20 10:55:44 suse kernel: usb 2-1: Manufacturer: Panasonic Oct 20 10:55:44 suse kernel: usb 2-1: configuration #1 chosen from 1 choice Oct 20 10:55:44 suse kernel: scsi5 : SCSI emulation for USB Mass Storage devices Oct 20 10:55:44 suse kernel: usb-storage: device found at 4 Oct 20 10:55:44 suse kernel: usb-storage: waiting for device to settle before scanning Oct 20 10:55:45 suse kernel: scsi 5:0:0:0: Direct-Access MATSHITA DMC-TZ3 0100 PQ: 0 ANSI: 2 Oct 20 10:55:45 suse kernel: sd 5:0:0:0: [sdb] 1983999 512-byte hardware sectors (1016 MB) Oct 20 10:55:45 suse kernel: sd 5:0:0:0: [sdb] Write Protect is off Oct 20 10:55:45 suse kernel: sd 5:0:0:0: [sdb] Mode Sense: 04 00 00 00 Oct 20 10:55:45 suse kernel: sd 5:0:0:0: [sdb] Assuming drive cache: write through Oct 20 10:55:45 suse kernel: sd 5:0:0:0: [sdb] 1983999 512-byte hardware sectors (1016 MB) Oct 20 10:55:45 suse kernel: sd 5:0:0:0: [sdb] Write Protect is off Oct 20 10:55:45 suse kernel: sd 5:0:0:0: [sdb] Mode Sense: 04 00 00 00 Oct 20 10:55:45 suse kernel: sd 5:0:0:0: [sdb] Assuming drive cache: write through Oct 20 10:55:45 suse kernel: sdb: sdb1 Oct 20 10:55:45 suse kernel: sd 5:0:0:0: [sdb] Attached SCSI removable disk Oct 20 10:55:45 suse kernel: sd 5:0:0:0: Attached scsi generic sg2 type 0 Oct 20 10:55:46 suse kernel: usb-storage: device scan complete KDE asks to open camera (system:/media/camera) No sdb device(s) created. Oct 20 10:57:16 suse kernel: usb 2-1: USB disconnect, address 4 *** Panasonic DMC-TZ3, try 2 *** I got once this output. There are some weird errors. Oct 20 10:57:34 suse kernel: usb 2-1: new full speed USB device using uhci_hcd and address 5 Oct 20 10:57:34 suse kernel: usb 2-1: new device found, idVendor=04da, idProduct=2372 Oct 20 10:57:34 suse kernel: usb 2-1: new device strings: Mfr=1, Product=2, SerialNumber=0 Oct 20 10:57:34 suse kernel: usb 2-1: Product: DMC-TZ3 Oct 20 10:57:34 suse kernel: usb 2-1: Manufacturer: Panasonic Oct 20 10:57:34 suse kernel: usb 2-1: configuration #1 chosen from 1 choice Oct 20 10:57:34 suse kernel: scsi6 : SCSI emulation for USB Mass Storage devices Oct 20 10:57:34 suse kernel: usb-storage: device found at 5 Oct 20 10:57:34 suse kernel: usb-storage: waiting for device to settle before scanning Oct 20 10:57:35 suse kernel: scsi 6:0:0:0: Direct-Access MATSHITA DMC-TZ3 0100 PQ: 0 ANSI: 2 Oct 20 10:57:35 suse kernel: sd 6:0:0:0: [sdb] 1983999 512-byte hardware sectors (1016 MB) Oct 20 10:57:35 suse kernel: sd 6:0:0:0: [sdb] Write Protect is off Oct 20 10:57:35 suse kernel: sd 6:0:0:0: [sdb] Mode Sense: 04 00 00 00 Oct 20 10:57:35 suse kernel: sd 6:0:0:0: [sdb] Assuming drive cache: write through Oct 20 10:57:35 suse kernel: sd 6:0:0:0: [sdb] 1983999 512-byte hardware sectors (1016 MB) Oct 20 10:57:35 suse kernel: sd 6:0:0:0: [sdb] Write Protect is off Oct 20 10:57:35 suse kernel: sd 6:0:0:0: [sdb] Mode Sense: 04 00 00 00 Oct 20 10:57:35 suse kernel: sd 6:0:0:0: [sdb] Assuming drive cache: write through Oct 20 10:57:35 suse kernel: sdb: sdb1 Oct 20 10:57:35 suse kernel: sd 6:0:0:0: [sdb] Attached SCSI removable disk Oct 20 10:57:35 suse kernel: sd 6:0:0:0: Attached scsi generic sg2 type 0 Oct 20 10:57:35 suse kernel: usb-storage: device scan complete Oct 20 10:57:37 suse kernel: scsi 6:0:0:0: rejecting I/O to dead device Oct 20 10:57:37 suse kernel: Buffer I/O error on device sdb1, logical block 1983488 Oct 20 10:57:37 suse kernel: scsi 6:0:0:0: rejecting I/O to dead device Oct 20 10:57:37 suse kernel: Buffer I/O error on device sdb1, logical block 1983489 Oct 20 10:57:37 suse kernel: Buffer I/O error on device sdb1, logical block 1983490 Oct 20 10:57:37 suse kernel: Buffer I/O error on device sdb1, logical block 1983491 Oct 20 10:57:37 suse kernel: Buffer I/O error on device sdb1, logical block 1983492 Oct 20 10:57:37 suse kernel: Buffer I/O error on device sdb1, logical block 1983493 Oct 20 10:57:37 suse kernel: Buffer I/O error on device sdb1, logical block 1983494 Oct 20 10:57:37 suse kernel: scsi 6:0:0:0: rejecting I/O to dead device Oct 20 10:57:37 suse kernel: Buffer I/O error on device sdb1, logical block 1983488 Oct 20 10:57:37 suse kernel: scsi 6:0:0:0: rejecting I/O to dead device Oct 20 10:57:37 suse kernel: Buffer I/O error on device sdb1, logical block 1983489 Oct 20 10:57:37 suse kernel: scsi 6:0:0:0: rejecting I/O to dead device Oct 20 10:57:37 suse kernel: Buffer I/O error on device sdb1, logical block 1983490 Oct 20 10:57:37 suse kernel: scsi 6:0:0:0: rejecting I/O to dead device .. Oct 20 10:58:15 suse kernel: usb 2-1: USB disconnect, address 5 **** Now I try WITHOUT HALD **** # /etc/init.d/haldaemon stop Shutting down HAL daemon done Plug in TZ3: Oct 20 11:01:44 suse kernel: usb 3-1: new full speed USB device using uhci_hcd and address 5 Oct 20 11:01:45 suse kernel: usb 3-1: new device found, idVendor=04da, idProduct=2372 Oct 20 11:01:45 suse kernel: usb 3-1: new device strings: Mfr=1, Product=2, SerialNumber=0 Oct 20 11:01:45 suse kernel: usb 3-1: Product: DMC-TZ3 Oct 20 11:01:45 suse kernel: usb 3-1: Manufacturer: Panasonic Oct 20 11:01:45 suse kernel: usb 3-1: configuration #1 chosen from 1 choice Oct 20 11:01:45 suse kernel: scsi9 : SCSI emulation for USB Mass Storage devices Oct 20 11:01:45 suse kernel: usb-storage: device found at 5 Oct 20 11:01:45 suse kernel: usb-storage: waiting for device to settle before scanning Oct 20 11:01:46 suse kernel: scsi 9:0:0:0: Direct-Access MATSHITA DMC-TZ3 0100 PQ: 0 ANSI: 2 Oct 20 11:01:46 suse kernel: sd 9:0:0:0: [sdb] 1983999 512-byte hardware sectors (1016 MB) Oct 20 11:01:46 suse kernel: sd 9:0:0:0: [sdb] Write Protect is off Oct 20 11:01:46 suse kernel: sd 9:0:0:0: [sdb] Mode Sense: 04 00 00 00 Oct 20 11:01:46 suse kernel: sd 9:0:0:0: [sdb] Assuming drive cache: write through Oct 20 11:01:46 suse kernel: sd 9:0:0:0: [sdb] 1983999 512-byte hardware sectors (1016 MB) Oct 20 11:01:46 suse kernel: sd 9:0:0:0: [sdb] Write Protect is off Oct 20 11:01:46 suse kernel: sd 9:0:0:0: [sdb] Mode Sense: 04 00 00 00 Oct 20 11:01:46 suse kernel: sd 9:0:0:0: [sdb] Assuming drive cache: write through Oct 20 11:01:46 suse kernel: sdb: sdb1 Oct 20 11:01:46 suse kernel: sd 9:0:0:0: [sdb] Attached SCSI removable disk Oct 20 11:01:46 suse kernel: sd 9:0:0:0: Attached scsi generic sg2 type 0 Oct 20 11:01:46 suse kernel: usb-storage: device scan complete # ls -la /dev/sd* brw-r----- 1 root disk 8, 0 2007-10-20 09:51 /dev/sda brw-r----- 1 root disk 8, 1 2007-10-20 09:51 /dev/sda1 brw-r----- 1 root disk 8, 10 2007-10-20 09:51 /dev/sda10 brw-r----- 1 root disk 8, 11 2007-10-20 09:51 /dev/sda11 brw-r----- 1 root disk 8, 2 2007-10-20 09:51 /dev/sda2 brw-r----- 1 root disk 8, 3 2007-10-20 09:51 /dev/sda3 brw-r----- 1 root disk 8, 5 2007-10-20 09:51 /dev/sda5 brw-r----- 1 root disk 8, 6 2007-10-20 09:51 /dev/sda6 brw-r----- 1 root disk 8, 7 2007-10-20 09:51 /dev/sda7 brw-r----- 1 root disk 8, 8 2007-10-20 09:51 /dev/sda8 brw-r----- 1 root disk 8, 9 2007-10-20 09:51 /dev/sda9 brw-r----- 1 root disk 8, 16 2007-10-20 11:01 /dev/sdb brw-r----- 1 root disk 8, 17 2007-10-20 11:01 /dev/sdb1 # ls -la /dev/sg* crw-r----- 1 root disk 21, 0 2007-10-20 09:51 /dev/sg0 crw-rw----+ 1 root disk 21, 1 2007-10-20 09:51 /dev/sg1 crw-r----- 1 root disk 21, 2 2007-10-20 11:01 /dev/sg2 So the sdb devices are now created and not destroyed. Let's just mount the camera: # mount /dev/sdb1 /mnt/a # mount .. /dev/sdb1 on /mnt/a type vfat (rw) TADA! Oct 20 11:05:55 suse kernel: usb 3-1: USB disconnect, address 5 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=335475#c1 Matej Horvath <mhorvath@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |vmicho@gmail.com --- Comment #1 from Matej Horvath <mhorvath@novell.com> 2007-10-24 07:45:41 MST --- Could you please attach output of hwinfo? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=335475#c2 --- Comment #2 from Michal Veselenyi <vmicho@gmail.com> 2007-10-27 03:10:47 MST --- Sorry, didn't have time last couple of days. I'll attach hwinfo output bit later. I'm now out and I don't have my usb cable with me. Just a note: using a SD card reader works perfectly. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=335475#c3 Michal Veselenyi <vmicho@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|vmicho@gmail.com | --- Comment #3 from Michal Veselenyi <vmicho@gmail.com> 2007-10-31 02:07:52 MST --- Created an attachment (id=181367) --> (https://bugzilla.novell.com/attachment.cgi?id=181367) hwinfo with camera connected hwinfo with camera connected There are 3 lines containing "TZ3" string. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=335475#c4 --- Comment #4 from Michal Veselenyi <vmicho@gmail.com> 2007-10-31 02:09:55 MST --- Created an attachment (id=181369) --> (https://bugzilla.novell.com/attachment.cgi?id=181369) Hwinfo without camera -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=335475 Cyril Hrubis <chrubis@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |dkukawka@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=335475#c5 --- Comment #5 from Danny Kukawka <dkukawka@novell.com> 2007-11-01 06:34:36 MST --- Please don't add such long logs to a comment/description. For this we have attachments. This description is horrible to read -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=335475#c6 Danny Kukawka <dkukawka@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mhorvath@novell.com AssignedTo|dkukawka@novell.com |kernel-maintainers@forge.provo.novell.com Component|Hotplug |Kernel --- Comment #6 from Danny Kukawka <dkukawka@novell.com> 2007-11-01 06:37:40 MST --- Btw. It's not a HAL problem if a dev device get not created. This is not the job of HAL, but of the kernel or maybe udev. I reassign it to the kernel guys. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=335475#c7 --- Comment #7 from Michal Veselenyi <vmicho@gmail.com> 2007-11-01 09:29:05 MST --- (In reply to comment #6 from Danny Kukawka)
Btw. It's not a HAL problem if a dev device get not created. This is not the job of HAL, but of the kernel or maybe udev. I reassign it to the kernel guys.
In this case it is a hald problem. The device is properly created by the kernel (HALD not running). But if hald is running, it is also destroyed (by mistake) quite fast. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=335475#c8 Danny Kukawka <dkukawka@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dkukawka@novell.com --- Comment #8 from Danny Kukawka <dkukawka@novell.com> 2007-11-12 13:47:15 MST --- How should HAL be able to destroy a device? HAL do nothing that could cause this. If this is triggered by HAL it's a kernel bug anyway. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=335475#c9 Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeffm@novell.com Status|NEW |NEEDINFO Info Provider| |dkukawka@novell.com --- Comment #9 from Jeff Mahoney <jeffm@novell.com> 2007-11-30 11:54:51 MST --- Well before we can debug it, a bit of an idea of what HAL is doing here would be useful. The only thing that's clear so far is that the bug is reproducible with haldaemon running and not without it. It's likely that HAL is probing the device somehow and the device isn't handling it as expected. This could be a kernel driver issue, but there's not enough information to debug what the problem is. Danny, can you work with Michal to generate some debugging information? I'm not familiar enough with HAL to know what's going on here. Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=335475 User behlert@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=335475#c10 --- Comment #10 from Stefan Behlert <behlert@novell.com> 2008-01-31 05:28:24 MST --- Danny? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=335475 User gregkh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=335475#c11 Greg Kroah-Hartman <gregkh@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|dkukawka@novell.com | Resolution| |NORESPONSE --- Comment #11 from Greg Kroah-Hartman <gregkh@novell.com> 2008-02-04 11:44:48 MST --- Closing due to inactivity. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=335475 User meissner@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=335475#c12 Marcus Meissner <meissner@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |meissner@novell.com --- Comment #12 from Marcus Meissner <meissner@novell.com> 2008-08-24 14:14:54 MDT --- This is actually a libgphoto2 issue, which had wrong USB ids included (mass storage ids in the ptp2 driver). This caused libgphoto2 to detach the mass storage driver and cause this behaviour. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com