| Summary: | hang when scanning for CD devices | ||
|---|---|---|---|
| Product: | [Applications] k3b | Reporter: | Inge Svensson <inge.s.svensson> |
| Component: | general | Assignee: | Sebastian Trueg <trueg> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | crash | ||
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Inge Svensson
2004-09-09 13:22:45 UTC
Today I tried to take away my cdrom after I found out it hade strange behavior when I tried to play a music CD - and suddenly I could run both k3b setup and k3b. The cdrom is ATAPI 50 X cdrom version 1.10. Maybe it's a Linux problem not k3b. inge.s.svensson@svenskakyrkan.se Same here. I start KDE, system continues running, but can't do any disk access anymore. Access LED on main system hard disk (/dev/sda) is stuck on. Appears like k3b is doing something on /dev/sg* that it shouldn't be doing, hanging systems that have the root filesystem on a SCSI drive. Update: The hang isn't permanent. After letting the system sit there hung for a couple of minutes, it came back to life, k3b and everything else working fine again. dmesg reports a pile of SCSI errors, including a bus reset for the disk drive. (sr 0:0:1 and 0:0:0 are a Plextor CDR and a Yamaha CDRW, sd 1:0:1 is the system root drive. It isn't even on the same SCSI channel.) This is k3b 0.12.5 on KDE 3.4.3 on Linux x86-64 2.6.14-rc5. Snippet: sr 0:0:1:0: phase change 2-1 12@0785a368 resid=6. sr 0:0:1:0: phase change 2-1 12@0785a368 resid=6. sr 0:0:1:0: phase change 2-1 12@0785a368 resid=2. sr 0:0:1:0: phase change 2-1 12@0785a368 resid=2. sr 0:0:1:0: phase change 2-1 12@0785a368 resid=2. sr 0:0:1:0: phase change 2-1 12@0785a368 resid=2. sr 0:0:1:0: phase change 2-1 12@0785a368 resid=2. sr 0:0:1:0: phase change 2-1 12@0785a368 resid=2. sr 0:0:1:0: phase change 2-1 12@0785a368 resid=2. sr 0:0:1:0: phase change 2-1 12@0785a368 resid=2. sr 0:0:1:0: phase change 2-1 12@0785a368 resid=2. sr 0:0:1:0: phase change 2-1 12@0785a368 resid=2. sr 0:0:1:0: phase change 2-1 12@0785a368 resid=2. sr 0:0:1:0: phase change 2-1 12@0785a368 resid=2. sr 0:0:1:0: phase change 2-1 12@0785a368 resid=2. sr 0:0:1:0: phase change 2-1 12@0785a368 resid=2. sr 0:0:1:0: phase change 2-0 12@0785a368 resid=2. sr 0:0:1:0: phase change 2-0 12@0785a368 resid=2. sr 0:0:1:0: phase change 2-0 12@0785a368 resid=2. sr 0:0:1:0: phase change 2-0 12@0785a368 resid=2. sr 0:0:1:0: phase change 2-0 12@0785a368 resid=2. sr 0:0:1:0: phase change 2-0 12@0785a368 resid=2. sr 0:0:1:0: phase change 2-0 12@0785a368 resid=2. sr 0:0:1:0: phase change 2-1 12@0785a368 resid=2. sr 0:0:1:0: phase change 2-1 12@0785a368 resid=2. sr 0:0:1:0: phase change 2-1 12@0785a368 resid=2. sr 0:0:1:0: phase change 2-1 12@0785a368 resid=2. sr 0:0:1:0: phase change 2-3 12@0785a368 resid=2. sr 0:0:1:0: phase change 2-1 12@0785a368 resid=6. sr 0:0:0:0: phase change 2-1 12@0785a368 resid=6. sr 0:0:0:0: phase change 2-1 12@0785a368 resid=6. sr 0:0:0:0: phase change 2-3 12@0785a368 resid=2. sr 0:0:0:0: phase change 2-3 12@0785a368 resid=2. sr 0:0:0:0: phase change 2-3 12@0785a368 resid=2. sr 0:0:0:0: phase change 2-3 12@0785a368 resid=2. sr 0:0:0:0: phase change 2-3 12@0785a368 resid=2. sr 0:0:0:0: phase change 2-3 12@0785a368 resid=2. sr 0:0:0:0: phase change 2-3 12@0785a368 resid=2. sr 0:0:0:0: phase change 2-3 12@0785a368 resid=2. sr 0:0:0:0: phase change 2-3 12@0785a368 resid=2. sr 0:0:0:0: phase change 2-3 12@0785a368 resid=2. sr 0:0:0:0: phase change 2-3 12@0785a368 resid=2. sr 0:0:0:0: phase change 2-3 12@0785a368 resid=2. sr 0:0:0:0: phase change 2-3 12@0785a368 resid=2. sr 0:0:0:0: phase change 2-3 12@0785a368 resid=2. sr 0:0:0:0: phase change 2-3 12@0785a368 resid=2. sr 0:0:0:0: phase change 2-1 12@0785a368 resid=6. sd 1:0:1:0: phase change 2-1 12@1fd46368 resid=6. sd 1:0:1:0: ABORT operation started. sd 1:0:1:0: ABORT operation timed-out. sd 1:0:1:0: ABORT operation started. sd 1:0:1:0: ABORT operation timed-out. sd 1:0:1:0: DEVICE RESET operation started. sd 1:0:1:0: DEVICE RESET operation timed-out. sd 1:0:1:0: BUS RESET operation started. sym1: SCSI BUS reset detected. sym1: SCSI BUS has been reset. sd 1:0:1:0: BUS RESET operation complete. sd 1:0:1:0: phase change 2-7 12@1fd46368 resid=6. sd 1:0:1:0: phase change 2-7 12@1fcc1368 resid=6. sd 1:0:1:0: phase change 2-7 12@1fcc1368 resid=6. sr 0:0:0:0: phase change 2-1 12@0785a368 resid=6. sr 0:0:1:0: phase change 2-1 12@0785a368 resid=6. sd 1:0:1:0: phase change 2-1 12@1fd4fb68 resid=6. sd 1:0:1:0: phase change 2-1 12@1fd4fb68 resid=6. sd 1:0:1:0: phase change 2-1 12@1fd4fb68 resid=6. sd 1:0:1:0: phase change 2-1 12@1fd4fb68 resid=6. hardware problem. Not a bug in KDE. Definitely NOT a hardware problem. The box runs as a media server 24/7, and does not EVER do this except when starting k3b. The SCSI error is triggered on every single SCSI device, including the machine's main hard disk (which is on an entirely separate SCSI channel altogether). The "fun" thing about this is that all those devices are then reverted to asynchronous SCSI, with abysmal performance. As it is, k3b is flat out useless with SCSI machines, and it even manages to break it thoroughly enough to require a reboot. The backend programs that k3b uses work just fine too, which is further proof that there is nothing wrong at all with neither the SCSI hardware nor the SCSI drivers. It's just k3b's own drive detection that kills it, no other program ever does it, but k3b does every single time. How about a little less audacity and a little more debugging? btw, meanwhile I've updated to KDE 3.5, k3b 0.12.10-3 and latest Linux kernel 2.6.15-rc. Bug finally gone in K3b 0.12.15. Thanks. |