Bug#452782: marked as done (Errors on Connecting Digital Camera (Nikon D80))

Debian Bug Tracking System Sun, 25 Nov 2007 03:32:32 -0800

Your message dated Sun, 25 Nov 2007 12:24:49 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#452782: Errors on Connecting Digital Camera (Nikon D80)
has caused the attached Bug report to be marked as done.


This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---

Package: udev
Version: 0.114-2
Severity: normal

--- Please enter the report below this line. ---

Hi,

I recently noticed my digital camera didn't work anymore. If I connect it, I 
get:

usb 4-3: new high speed USB device using ehci_hcd and address 5
usb 4-3: configuration #1 chosen from 1 choice
scsi3 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 5
usb-storage: waiting for device to settle before scanning
usb-storage: device scan complete
scsi 3:0:0:0: Direct-Access     NIKON    D80              1.01 PQ: 0 ANSI: 2
sd 3:0:0:0: [sda] 3932161 512-byte hardware sectors (2013 MB)
sd 3:0:0:0: [sda] Write Protect is off
sd 3:0:0:0: [sda] Mode Sense: 0f 00 00 00
sd 3:0:0:0: [sda] Assuming drive cache: write through
sd 3:0:0:0: [sda] 3932161 512-byte hardware sectors (2013 MB)
sd 3:0:0:0: [sda] Write Protect is off
sd 3:0:0:0: [sda] Mode Sense: 0f 00 00 00
sd 3:0:0:0: [sda] Assuming drive cache: write through
 sda: sda1
sd 3:0:0:0: [sda] Attached SCSI removable disk
end_request: I/O error, dev sda, sector 3932160
printk: 613 messages suppressed.
Buffer I/O error on device sda, logical block 3932160
end_request: I/O error, dev sda, sector 3932160
Buffer I/O error on device sda, logical block 3932160
end_request: I/O error, dev sda, sector 3932160
Buffer I/O error on device sda, logical block 3932160
end_request: I/O error, dev sda, sector 3932160
Buffer I/O error on device sda, logical block 3932160
end_request: I/O error, dev sda, sector 3932160
Buffer I/O error on device sda, logical block 3932160
end_request: I/O error, dev sda, sector 3932160
Buffer I/O error on device sda, logical block 3932160
end_request: I/O error, dev sda, sector 3932160
Buffer I/O error on device sda, logical block 3932160
end_request: I/O error, dev sda, sector 40
Buffer I/O error on device sda, logical block 40
end_request: I/O error, dev sda, sector 41
Buffer I/O error on device sda, logical block 41
Buffer I/O error on device sda, logical block 42
end_request: I/O error, dev sda, sector 40
end_request: I/O error, dev sda, sector 41
end_request: I/O error, dev sda, sector 40
end_request: I/O error, dev sda, sector 41
end_request: I/O error, dev sda, sector 40
end_request: I/O error, dev sda, sector 41
end_request: I/O error, dev sda, sector 40
end_request: I/O error, dev sda, sector 41
end_request: I/O error, dev sda, sector 0
end_request: I/O error, dev sda, sector 0
end_request: I/O error, dev sda, sector 1
end_request: I/O error, dev sda, sector 0
end_request: I/O error, dev sda, sector 1
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 263
end_request: I/O error, dev sda, sector 264
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 263
end_request: I/O error, dev sda, sector 264
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 255
end_request: I/O error, dev sda, sector 256
end_request: I/O error, dev sda, sector 0
end_request: I/O error, dev sda, sector 1
end_request: I/O error, dev sda, sector 0
end_request: I/O error, dev sda, sector 1
end_request: I/O error, dev sda, sector 0
end_request: I/O error, dev sda, sector 1

/dev/da and /dev/sda1 exist, but if I try to mount /dev/sda1 I just get more 
errors. Downgrading to udev 105-4 solved the problem. 113 had the same issue.

I'm not sure how to troubleshoot this, but I'd be happy to provide more info.

Cheers,
Carlos




--- System information. ---
Architecture: i386
Kernel:       Linux 2.6.22.071109

Debian Release: lenny/sid
  500 unstable        www.debian-multimedia.org 
  500 unstable        http.us.debian.org 

--- Package information. ---
Depends              (Version) | Installed
==============================-+-=============
libc6             (>= 2.3.6-6) | 2.7-1
libselinux1          (>= 1.32) | 2.0.15-2+b1
libvolume-id0     (>= 0.103-1) | 0.114-2
debconf              (>= 0.5)  | 1.5.17
 OR debconf-2.0                | 
lsb-base            (>= 3.0-6) | 3.1-24

--- End Message ---

--- Begin Message ---

On Nov 25, Carlos Moffat <[EMAIL PROTECTED]> wrote:

> sd 3:0:0:0: [sda] Attached SCSI removable disk
> end_request: I/O error, dev sda, sector 3932160
> printk: 613 messages suppressed.
Your hardware is broken. This is not related to udev.

-- 
ciao,
Marco

signature.asc
Description: Digital signature

--- End Message ---

Bug#452782: marked as done (Errors on Connecting Digital Camera (Nikon D80))

Reply via email to