FS#7591 - k3b 1.0.2-1 causes kernel panic at launch
Attached to Project:
Arch Linux
Opened by (N/A) (wantilles) - Monday, 09 July 2007, 17:29 GMT
Last edited by Damir Perisa (damir.perisa) - Tuesday, 24 July 2007, 17:20 GMT
Opened by (N/A) (wantilles) - Monday, 09 July 2007, 17:29 GMT
Last edited by Damir Perisa (damir.perisa) - Tuesday, 24 July 2007, 17:20 GMT
|
Details
Description:
When launched, k3b 1.0.2-1 causes kernel panic. A full system lockup takes place. Keyboard and mouse are not responding, the Caps-Lock and Scroll-Lock indicators on the keyboard are blinking continuously, and the only possible option is a hardware reset. Hardware is: - Athlon64-X2 - nForce4-SLI. - Plextor PX-116A2 - NEC 4571A Kernel version: uname -a && cat /proc/version Linux 2.6.21-ARCH #1 SMP PREEMPT Sat Jul 7 06:35:11 UTC 2007 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ AuthenticAMD GNU/Linux Linux version 2.6.21-ARCH (root@workstation64) (gcc version 4.2.1 20070704 (prerelease)) #1 SMP PREEMPT Sat Jul 7 06:35:11 UTC 2007 It is not the kernel's fault. I downgraded from 2.6.21.6-1 to 2.6.21.5-1 and the same happened. I restored back the new 2.6.21.6-1 kernel and downgraded k3b from 1.0.2-1 to 1.0.1-1 and it works. So it seems to be a specific k3b 1.0.2-1 issue. I also tested for the same behavior on a i686 machine and there it works. However, that machine does not have a DVD-Writer present, but only a DVD-Reader. Additional info: * package version(s) 1.0.2-1 * config and/or log files etc. Nothing is present on log files since a total system lockup occurs. Steps to reproduce: Just launch the application from the Gnome Menu or a Gnome Panel Launcher. Relevant comments in other bug reports: See from http://bugs.archlinux.org/task/7514#comment17733 and downwards. |
This task depends upon
Closed by Damir Perisa (damir.perisa)
Tuesday, 24 July 2007, 17:20 GMT
Reason for closing: Fixed
Additional comments about closing: upstream fix with k3b 1.0.3 and kernel 2.6.22
Tuesday, 24 July 2007, 17:20 GMT
Reason for closing: Fixed
Additional comments about closing: upstream fix with k3b 1.0.3 and kernel 2.6.22
I never even reach the point to see the k3b main application window, much less see the KDE crash-handler window.
http://bbs.archlinux.org/viewtopic.php?id=34892 using kernel 2.6.22 fixes the problem. I can't confirm myself as k3b 1.0.2 works fine with kernel 2.6.21 for my two systems (i686 with IDE burner and x86_64 with sata burner)
http://bbs.archlinux.org/viewtopic.php?id=35396
Just as with the above poster, reverting back to K3b version 1.0.1 fixes things. That's the reason I think this is the same bug. If it's not the same, please let me know and I'll open a new bug report.
Thanks in advance for your help.
oz