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
Task Type Bug Report
Category Kernel
Status Closed
Assigned To No-one
Architecture x86_64
Severity High
Priority Normal
Reported Version 2007.05 Duke
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

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
Comment by Attila (attila) - Monday, 09 July 2007, 19:18 GMT
The author of https://bugs.kde.org/show_bug.cgi?id=147676 seems to have the same problem but he could produce output with 'k3b --nocrashhandler'. Perhaps it works for you too and one the devs can find out the problem with this information. Good luck and sorry that i have no better idea because k3b works normal for me.
Comment by (N/A) (wantilles) - Monday, 09 July 2007, 19:31 GMT
Perhaps you don't get it.

I never even reach the point to see the k3b main application window, much less see the KDE crash-handler window.
Comment by Attila (attila) - Monday, 09 July 2007, 20:06 GMT
Ah, you be right i've overseen that the author has gotten the kde crash handler. Sorry, i mistake the above bugreport for this report https://bugs.kde.org/show_bug.cgi?id=147663. Good luck again.
Comment by (N/A) (wantilles) - Monday, 09 July 2007, 20:17 GMT
Yes, that seems to be it.
Comment by Radu Popescu (radumash) - Tuesday, 10 July 2007, 10:16 GMT
Yeah, I'm having exactly the same problem with k3b 1.0.2-1. Also, k3b 1.0.1 works just fine. With the exception of the k3b package, my system is up to date.
Comment by Eric Belanger (Snowman) - Tuesday, 10 July 2007, 18:38 GMT
In fact, it seems to be kernel related. According to a bug report I've seen on bugs.kde.org and the confirmation of a user in that thread:
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)
Comment by ozar (ozar) - Monday, 23 July 2007, 00:14 GMT
I'm having basically the same issue on the first K3b startup, except that the kernel doesn't actually crash. It takes K3b quite some time to scan for drives, but it eventually finds them. After closing K3b and restarting it, the Plextor DVD drive residing on /dev/sr0 is no longer detected. Rebooting, then restarting K3b repeats the process. I've included quite a bit more information regarding this issue here:

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
Comment by Jules (Misfit138) - Monday, 23 July 2007, 01:20 GMT
Same exact issue here. Entire system up to date. Using Ignorepkg=k3b for now.
Comment by Jules (Misfit138) - Monday, 23 July 2007, 01:24 GMT
To clarify: same exact issue as original bug report above...my whole machine freezes..reverting to 1.0.1 and using Ignorepkg=k3b for now
Comment by Damir Perisa (damir.perisa) - Monday, 23 July 2007, 15:52 GMT
1.0.3 introduces different behaviour and some bugfixes, that may solve this. please test and report back (i cannot reproduce your troubpe, for me it works)
Comment by ozar (ozar) - Monday, 23 July 2007, 16:20 GMT
No luck... I've just tried k3b 1.0.3-1 that just came out earlier today, but it has the same problem. Gotta go all the way back to version 1.0.1 to get things working again.
Comment by ozar (ozar) - Tuesday, 24 July 2007, 03:58 GMT
Update... the new 2.6.22 kernel seems to have fixed this issue for me. Hope it works for the rest of you.
Comment by (N/A) (wantilles) - Tuesday, 24 July 2007, 12:40 GMT
With the new kernel 2.6.22-1, this abnormal k3b-1.0.2-1 behavior does not take place.
Comment by Radu Popescu (radumash) - Tuesday, 24 July 2007, 16:53 GMT
I've just tried k3b 1.0.3-1 with the new kernel 2.6.22-1 and the problem seems to have been dealt with. It works now.

Loading...