Bug 411408 - Deleting images from camera in digikam kills access to hard drive
Summary: Deleting images from camera in digikam kills access to hard drive
Status: RESOLVED NORESPONSE
Alias: None
Product: openSUSE 11.0
Classification: openSUSE
Component: Kernel (show other bugs)
Version: Final
Hardware: x86-64 openSUSE 11.0
: P5 - None : Normal with 5 votes (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-22 21:48 UTC by Matthias Bach
Modified: 2009-05-15 18:18 UTC (History)
0 users

See Also:
Found By: Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
Camera description as given by system:/media/camera/summary.txt (2.48 KB, text/plain)
2008-07-22 21:50 UTC, Matthias Bach
Details
Picture of the dump to console 10 (sharp but flash kills some chars) (438.98 KB, image/jpeg)
2008-07-22 21:51 UTC, Matthias Bach
Details
Picture of the dump to console 10 (as sharp as possible without flash) (822.86 KB, image/jpeg)
2008-07-22 21:53 UTC, Matthias Bach
Details
Console 10 without NVidia driver (152.90 KB, image/jpeg)
2008-08-10 11:06 UTC, Matthias Bach
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Matthias Bach 2008-07-22 21:48:13 UTC
Trying to delete images from a Canon Ixus 60 that is connected by the original USB cable from within digikam seems to kill access to my harddrive.

By kill I mean the following. The system seems to be unable to read anything that's not in file buffers. Login e.g. on terminal is impossible. Upon entering the username the terminal restarts. Ctrl-Alt-Backspace kills the X-Server but it doesn't come back. Ctrl-Alt-Del in KDE does not work. It is also not possible to start a system shutdown via the "Start"-Menu. Powerbutton does not work. Only way to recover the computer is hard power-off/reset.

On terminal 10 the following message is shown:
eddie kernel: ehci_hcd 0000:00:02.1: HC died; cleaning up Disabling IRQ #23

After a while it starts printing out disk access errors. After a restart fsck replays a journel and may raid 5 used for /home in some cases has to be started manually as it's superblocks seem not to be in sync (it starts up fine with -force, so. In the first attempt, where I had waited for a while before forcefully shutting down the system it afterwards synced for a while, so).

In one occasion it showed a dump on console 10. I attached two pictures of it.

Deleting files from the camera using konqueror (system:/media/camera) seems to work fine. I was also able to delete some single pictures from the cam, but anytime I tried to delete multiple pictures all at one time it crashed the mashine.

The installation is an upgrade to 11.0 from 10.3 on which the problem did not appear, therefore I am pretty confident it's not some hardware problem like conflicting IRQs or so.
Comment 1 Matthias Bach 2008-07-22 21:50:42 UTC
Created attachment 229402 [details]
Camera description as given by system:/media/camera/summary.txt
Comment 2 Matthias Bach 2008-07-22 21:51:47 UTC
Created attachment 229403 [details]
Picture of the dump to console 10 (sharp but flash kills some chars)
Comment 3 Matthias Bach 2008-07-22 21:53:00 UTC
Created attachment 229404 [details]
Picture of the dump to console 10 (as sharp as possible without flash)
Comment 4 Greg Kroah-Hartman 2008-08-07 00:20:30 UTC
Can you reproduce this without the closed source kernel module installed?
Comment 5 Greg Kroah-Hartman 2008-08-07 00:21:11 UTC
Also, that message is not an "oops", but a warning message from the kernel, the system shoudl continue to keep working afterward, right?
Comment 6 Matthias Bach 2008-08-10 11:03:42 UTC
I completely removed the NVIDIA driver from the system. However the problem remains the same. I was however not able to reproduce the warning message, however that had happened with the NVidia driver, too. In that case it only says "ehci_hcd 0000:00:02.1: HC died; cleaning up
Disabling IRQ #23" (I attached another screenshot)
Comment 7 Matthias Bach 2008-08-10 11:06:20 UTC
Created attachment 232590 [details]
Console 10 without NVidia driver
Comment 8 Matthias Bach 2008-08-10 11:08:01 UTC
Technically the system keeps working, however it more and more stalls as more and more applications seem to be waiting for the filesystem. After a while even switching in between consoles no longer works.
Comment 9 Greg Kroah-Hartman 2008-10-23 14:51:19 UTC
Ick, that's some bad hardware :(

Can you verify that there are no bios updates for this system, and that memtest passes properly?
Comment 10 Jeff Mahoney 2009-05-15 18:18:40 UTC
Closing due to lack of response.