FS#7514 - System lock up on CD ripping

Attached to Project: Arch Linux
Opened by Clement (Manifold) - Monday, 25 June 2007, 19:15 GMT
Last edited by Aaron Griffin (phrakture) - Friday, 11 January 2008, 19:15 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To No-one
Architecture i686
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:

Upon ripping a CD in grip which uses cdparanoia, machine will sporadically lock. Reboot is needed.

Additional info:
* kernel26 version: 2.6.21.5-1

From /var/log/everything.log:

Jun 25 20:01:15 clemmonster modprobe: WARNING: Error inserting rtc (/lib/modules/2.6.21-ARCH/kernel/drivers/char/rtc.ko): Input/output error
Jun 25 20:01:15 clemmonster snd_rtctimer: Unknown symbol rtc_register
Jun 25 20:01:15 clemmonster snd_rtctimer: Unknown symbol rtc_unregister
Jun 25 20:01:15 clemmonster snd_rtctimer: Unknown symbol rtc_control
Jun 25 20:01:15 clemmonster modprobe: FATAL: Error inserting snd_rtctimer (/lib/modules/2.6.21-ARCH/kernel/sound/core/snd-rtctimer.ko): Unknown symbol in module, or unknown parameter (see dmesg)

From dmesg:

rtc: I/O resource 70 is not free.
snd_rtctimer: Unknown symbol rtc_register
snd_rtctimer: Unknown symbol rtc_unregister
snd_rtctimer: Unknown symbol rtc_control

I believe that this error may have some link to another problem that I have been experiencing, please see attached link from forums:

http://bbs.archlinux.org/viewtopic.php?id=34547


Steps to reproduce:

1. Use listed version of kernel.
2. Rip a CD with grip.

Any more information, just ask. I will provide ASAP.
This task depends upon

Closed by  Aaron Griffin (phrakture)
Friday, 11 January 2008, 19:15 GMT
Reason for closing:  Fixed
Comment by Tobias Powalowski (tpowa) - Monday, 25 June 2007, 20:56 GMT
please try this kernel:
[kernel]
http://www.archlinux.org/~tpowa/rc-kernel/

thanks
greetings
tpowa
Comment by Clement (Manifold) - Monday, 25 June 2007, 22:03 GMT
I get the same error after trying that Kernel and rebooting (/var/log/everything.log):

Jun 25 22:19:56 clemmonster rtc: I/O resource 70 is not free.
Jun 25 22:19:56 clemmonster modprobe: WARNING: Error inserting rtc (/lib/modules/2.6.22-rc5-ARCH/kernel/drivers/char/rtc.ko): Input/output error
Jun 25 22:19:56 clemmonster snd_rtctimer: Unknown symbol rtc_register
Jun 25 22:19:56 clemmonster snd_rtctimer: Unknown symbol rtc_unregister
Jun 25 22:19:56 clemmonster snd_rtctimer: Unknown symbol rtc_control
Jun 25 22:19:56 clemmonster modprobe: FATAL: Error inserting snd_rtctimer (/lib/modules/2.6.22-rc5-ARCH/kernel/sound/core/snd-rtctimer.ko): Unknown symbol in module, or unknown parameter (see dmesg)

And in dmesg:
rtc: I/O resource 70 is not free.
snd_rtctimer: Unknown symbol rtc_register
snd_rtctimer: Unknown symbol rtc_unregister
snd_rtctimer: Unknown symbol rtc_control
Comment by Jan de Groot (JGC) - Thursday, 28 June 2007, 06:23 GMT
What hardware do you have?
Comment by Clement (Manifold) - Thursday, 28 June 2007, 08:46 GMT
K7S41 ASRock Motherboard: http://www.asrock.com/mb/overview.asp?Model=K7S41

From HardInfo summary:

Summary
Computer
Processor AMD Duron(tm)
Memory 515MB (281MB used)
User Name clem (Clement Law)
Date/Time Thu 28 Jun 2007 09:41:12 PDT
Display
Resolution 1024x768 pixels
OpenGL Renderer Mesa DRI R300 20060815 AGP 1x x86/MMX+/3DNow!+/SSE TCL
X11 Vendor The X.Org Foundation
Multimedia
Audio Adapter ICH - SiS SI7012
Input Devices
Macintosh mouse button emulation
AT Translated Set 2 keyboard
Power Button (FF)
Power Button (CM)
PC Speaker
Analog 2-axis 4-button joystick
Logitech USB-PS/2 Optical Mouse
HID 1267:0103
HID 1267:0103

IDE Disks
ST380011A
HDS728080PLAT20
LITE-ON DVDRW SHM-165P6S (more info on optical drive here: http://www.hardware.info/en-UK/productdb/bGNkaZiUmJPK/viewproduct/LiteOn_SHM165P6S/)
Comment by Jan de Groot (JGC) - Saturday, 30 June 2007, 12:04 GMT
The rtc errors are only for playback, so they're not related to grip. Looking at your hardware, I don't see big problems, as the SiS chipset on your mainboard is quite recent and supported very well by the sis5513 driver. (I used to run SiS boards for a very long while and have never ever seen this one). I don't know what's the status of the sis libata driver, but given the fact you're using /dev/hd*, you're not using libata.

I would expect I/O errors due to a broken CD-ROM drive, bad cabling or blown capacitors on your mainboard (yes, Asrock is famous for this also, had two K7S8XE+ boards with blown caps). Could you try to rip a CD from the commandline with cdparanoia and see what it gives there before it locks up? Also, dmesg output would be useful, but I guess you can't get to that when it locks up. A way to catch dmesg messages is to launch cdparanoia from 1st console without syslog-ng running, the kernel should log on that console in that case.
Comment by Clement (Manifold) - Saturday, 30 June 2007, 16:59 GMT
I can get no useful logs from ripping with cdparanoia from the commandline with syslog-ng disabled, as the whole computer (with the screen) literally freezes. I have checked all the logs from /var/logs/ and I can discern nothing more relevant than:

Jun 25 22:19:56 clemmonster rtc: I/O resource 70 is not free.
Jun 25 22:19:56 clemmonster modprobe: WARNING: Error inserting rtc (/lib/modules/2.6.22-rc5-ARCH/kernel/drivers/char/rtc.ko): Input/output error
Jun 25 22:19:56 clemmonster snd_rtctimer: Unknown symbol rtc_register
Jun 25 22:19:56 clemmonster snd_rtctimer: Unknown symbol rtc_unregister
Jun 25 22:19:56 clemmonster snd_rtctimer: Unknown symbol rtc_control
Jun 25 22:19:56 clemmonster modprobe: FATAL: Error inserting snd_rtctimer (/lib/modules/2.6.22-rc5-ARCH/kernel/sound/core/snd-rtctimer.ko): Unknown symbol in module, or unknown parameter (see dmesg)

And in dmesg:
rtc: I/O resource 70 is not free.
snd_rtctimer: Unknown symbol rtc_register
snd_rtctimer: Unknown symbol rtc_unregister
snd_rtctimer: Unknown symbol rtc_control

Which I had posted before.

Am I missing something?
Comment by (N/A) (wantilles) - Monday, 09 July 2007, 14:23 GMT
I am posting it here since I think it is directly related.

Since I upgraded to this same latest kernel, when I click on the k3b launcher to launch the application, a full system lockup takes place.

Keyboard and mouse are not responding, the CapsLock and ScrollLock indicators on the keyboard are blinking continuously, and the only possible option is a hardware reset.

Hardware is Athlon64 X2 on nForce4-SLI.

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

I will test for the same behavior on a i686 machine (an AthlonXP Barton) that I have. It is running the same version on all software.
Comment by (N/A) (wantilles) - Monday, 09 July 2007, 15:40 GMT
I just attempted to reproduce the same bug on the above mentioned i686 hardware.

It does not happen.

So it may be a specific x86_64 issue.
Comment by Jan de Groot (JGC) - Monday, 09 July 2007, 15:54 GMT
Blinking keyboard LEDs are kernel panics usually. This could be nforce-specific also.
Comment by (N/A) (wantilles) - Monday, 09 July 2007, 16:02 GMT
So do you think I should open a new bug report, about kernel26-2.6.21.6-1 on x86_64?
Comment by (N/A) (wantilles) - Monday, 09 July 2007, 17:17 GMT
I think I have isolated the problem.

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 k3b issue.

I will open a new relevant bug report.
Comment by (N/A) (wantilles) - Monday, 09 July 2007, 17:31 GMT
The new k3b bug report is here:

http://bugs.archlinux.org/task/7591
Comment by Jan de Groot (JGC) - Monday, 09 July 2007, 17:31 GMT
There's a thread on the forum about it, don't know if there's a bugreport for it already. It seems to be fixed with kernel 2.6.22, so the question is: what changed in k3b, and what bug in the kernel did it trigger?
Comment by Roman Kyrylych (Romashka) - Friday, 11 January 2008, 13:34 GMT
can we close this?

Loading...