Skip to contentSkip to conversation

Linux kernel crash (3.2.0-2-amd64) when trying to play audio CD

DISCUSSION Thomas Schwinge 4 participants 16 messages Jun 16, 2012 – Jun 16, 2014

Subsystems (2)
SCSI libata
lore
Share & tools
lore

Thomas Schwinge

author
#0 lore raw

Hi!

After many others that played with no problems, I just tried playing Guano Apes' audio CD »Proud Like a God« (1997) in Rhythmbox, on my mostly up-to-date Debian GNU/Linux testing system.

    $ uname -a
    Linux boole 3.2.0-2-amd64 #1 SMP Mon May 21 17:45:41 UTC 2012 x86_64 GNU/Linux

... which specifically is »linux-image-3.2.0-2-amd64 3.2.18-1«.

While "loading" the CD in Rhythmbox, after a few seconds the kernel crashed. I rebooted, tried again, and it crashed again. At
<http://schwinge.homeip.net/~thomas/tmp/linux-crash-audio-cd.jpeg> you can find the panic message (low resolution, sorry), pointing to the SCSI/ATA code.

Are there any such known issues? Does the panic message give any clue already, or would you want me to reproduce that with debugging symbols, etc.?

Grüße,
Thomas

#1 lore raw
Quoted 17 lines · Thomas Schwinge

Hi!

After many others that played with no problems, I just tried playing Guano Apes' audio CD »Proud Like a God« (1997) in Rhythmbox, on my mostly up-to-date Debian GNU/Linux testing system.

    $ uname -a
    Linux boole 3.2.0-2-amd64 #1 SMP Mon May 21 17:45:41 UTC 2012 x86_64 GNU/Linux

... which specifically is »linux-image-3.2.0-2-amd64 3.2.18-1«.

While "loading" the CD in Rhythmbox, after a few seconds the kernel crashed. I rebooted, tried again, and it crashed again. At
<http://schwinge.homeip.net/~thomas/tmp/linux-crash-audio-cd.jpeg> you can find the panic message (low resolution, sorry), pointing to the SCSI/ATA code.

Quoted 3 lines

Are there any such known issues? Does the panic message give any clue already, or would you want me to reproduce that with debugging symbols, etc.?

Your computer is broken; Machine Check Exception indicates a hardware fault. The other text at the top of the screen may help to identify which component is at fault.

Ben.

Signature · 3 lines
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
                                                              - Albert Camus
author
#2 lore raw

Hi!

Quoted 16 lines · Ben Hutchings
Quoted 15 lines · Thomas Schwinge

After many others that played with no problems, I just tried playing Guano Apes' audio CD »Proud Like a God« (1997) in Rhythmbox, on my mostly up-to-date Debian GNU/Linux testing system.

    $ uname -a
    Linux boole 3.2.0-2-amd64 #1 SMP Mon May 21 17:45:41 UTC 2012 x86_64 GNU/Linux

... which specifically is »linux-image-3.2.0-2-amd64 3.2.18-1«.

While "loading" the CD in Rhythmbox, after a few seconds the kernel crashed. I rebooted, tried again, and it crashed again. At
<http://schwinge.homeip.net/~thomas/tmp/linux-crash-audio-cd.jpeg> you can find the panic message (low resolution, sorry), pointing to the SCSI/ATA code.

Quoted 6 lines
Quoted 3 lines

Are there any such known issues? Does the panic message give any clue already, or would you want me to reproduce that with debugging symbols, etc.?

Your computer is broken; Machine Check Exception indicates a hardware fault.

Hmm, I see, thanks. Nothing the kernel could do to catch that, I suppose? (Scary that simply putting a regular audio CD into the drive can crash the kernel.)

Quoted 2 lines

The other text at the top of the screen may help to identify which component is at fault.

Grüße,
Thomas

#3 lore raw
In reply to Thomas Schwinge
Quoted 9 lines · Thomas Schwinge

Hi!

After many others that played with no problems, I just tried playing Guano Apes' audio CD »Proud Like a God« (1997) in Rhythmbox, on my mostly up-to-date Debian GNU/Linux testing system.

    $ uname -a
    Linux boole 3.2.0-2-amd64 #1 SMP Mon May 21 17:45:41 UTC 2012 x86_64 GNU/Linux
Quoted 7 lines

... which specifically is »linux-image-3.2.0-2-amd64 3.2.18-1«.

While "loading" the CD in Rhythmbox, after a few seconds the kernel crashed. I rebooted, tried again, and it crashed again. At
<http://schwinge.homeip.net/~thomas/tmp/linux-crash-audio-cd.jpeg> you can find the panic message (low resolution, sorry), pointing to the SCSI/ATA code.

Let me guess: AMD K8?

Also, can I get /proc/cpuinfo please?

Thanks.

Signature · 6 lines
Regards/Gruss,
    Boris.
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
author
#4 lore raw

Hi!

Quoted 10 lines · Borislav Petkov
Quoted 9 lines · Thomas Schwinge

After many others that played with no problems, I just tried playing Guano Apes' audio CD »Proud Like a God« (1997) in Rhythmbox, on my mostly up-to-date Debian GNU/Linux testing system.

    $ uname -a
    Linux boole 3.2.0-2-amd64 #1 SMP Mon May 21 17:45:41 UTC 2012 x86_64 GNU/Linux

... which specifically is »linux-image-3.2.0-2-amd64 3.2.18-1«.

Quoted 7 lines
Quoted 5 lines

While "loading" the CD in Rhythmbox, after a few seconds the kernel crashed. I rebooted, tried again, and it crashed again. At
<http://schwinge.homeip.net/~thomas/tmp/linux-crash-audio-cd.jpeg> you can find the panic message (low resolution, sorry), pointing to the SCSI/ATA code.

Let me guess: AMD K8?

Correct.

Quoted 1 line

Also, can I get /proc/cpuinfo please?

    $ cat < /proc/cpuinfo
    processor       : 0
    vendor_id       : AuthenticAMD
    cpu family      : 15
    model           : 47
    model name      : AMD Sempron(tm) Processor 3000+
    stepping        : 2
    cpu MHz         : 1000.000
    cache size      : 128 KB
    fpu             : yes
    fpu_exception   : yes
    cpuid level     : 1
    wp              : yes
    flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext fxsr_opt lm 3dnowext 3dnow up rep_good nopl pni lahf_lm
    bogomips        : 2000.16
    TLB size        : 1024 4K pages
    clflush size    : 64
    cache_alignment : 64
    address sizes   : 40 bits physical, 48 bits virtual
    power management: ts fid vid ttp tm stc

Grüße,
Thomas

#5 lore raw
Quoted 8 lines · Thomas Schwinge
Quoted 1 line

Let me guess: AMD K8?

Correct.

Quoted 1 line

Also, can I get /proc/cpuinfo please?

    $ cat < /proc/cpuinfo
    processor       : 0

Ok, a single core.

Quoted 15 lines
    vendor_id       : AuthenticAMD
    cpu family      : 15
    model           : 47
    model name      : AMD Sempron(tm) Processor 3000+
    stepping        : 2
    cpu MHz         : 1000.000
    cache size      : 128 KB
    fpu             : yes
    fpu_exception   : yes
    cpuid level     : 1
    wp              : yes
    flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext fxsr_opt lm 3dnowext 3dnow up rep_good nopl pni lahf_lm
    bogomips        : 2000.16
    TLB size        : 1024 4K pages
    clflush size    : 64
Quoted 3 lines

cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management: ts fid vid ttp tm stc

Ok, can you do the following:

$ setpci -s 18.0 0x68.l

and

$ rdmsr 0xc001001f

and send me the output of both commands. Btw, rdmsr should be in a package called msr-tools, at least on Debian.

Thanks.

Signature · 8 lines
Regards/Gruss,
Boris.

Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
GM: Alberto Bozzo
Reg: Dornach, Landkreis Muenchen
HRB Nr. 43632 WEEE Registernr: 129 19551
author
#6 lore raw

Hi Borislav!

First, thanks for helping!

Quoted 31 lines · Borislav Petkov
Quoted 8 lines · Thomas Schwinge
Quoted 1 line

Let me guess: AMD K8?

Correct.

Quoted 1 line

Also, can I get /proc/cpuinfo please?

    $ cat < /proc/cpuinfo
    processor       : 0

Ok, a single core.

Quoted 15 lines
    vendor_id       : AuthenticAMD
    cpu family      : 15
    model           : 47
    model name      : AMD Sempron(tm) Processor 3000+
    stepping        : 2
    cpu MHz         : 1000.000
    cache size      : 128 KB
    fpu             : yes
    fpu_exception   : yes
    cpuid level     : 1
    wp              : yes
    flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext fxsr_opt lm 3dnowext 3dnow up rep_good nopl pni lahf_lm
    bogomips        : 2000.16
    TLB size        : 1024 4K pages
    clflush size    : 64
Quoted 3 lines

cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management: ts fid vid ttp tm stc

Quoted 3 lines

Ok, can you do the following:

$ setpci -s 18.0 0x68.l
    $ sudo setpci -s 18.0 0x68.l
    0f00cc0f
Quoted 1 line
$ rdmsr 0xc001001f
    $ sudo modprobe msr
    $ sudo rdmsr 0xc001001f
    8

Grüße,
Thomas

#7 lore raw
Quoted 3 lines · Thomas Schwinge

Hi Borislav!

First, thanks for helping!

Sure, np! :-)

Quoted 4 lines
Quoted 3 lines

Ok, can you do the following:

$ setpci -s 18.0 0x68.l
Quoted 8 lines
    $ sudo setpci -s 18.0 0x68.l
    0f00cc0f
Quoted 1 line
$ rdmsr 0xc001001f
    $ sudo modprobe msr
    $ sudo rdmsr 0xc001001f
    8

Ok, this is a BIOS bug - we have a recommendation about what the BIOS should do but yours doesn't do it. Are you sure you're using the latest BIOS for your motherboard?

Can you check for updates and if you get a newer version, can you update your BIOS and do the two commands above?

If there's no newer BIOS, we can try applying the workaround at boot in an init script to fix your issue.

Signature · 8 lines
Regards/Gruss,
Boris.

Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
GM: Alberto Bozzo
Reg: Dornach, Landkreis Muenchen
HRB Nr. 43632 WEEE Registernr: 129 19551
author
#8 lore raw

Hi Borislav!

I'm sorry for the late answer.

Quoted 14 lines · Borislav Petkov
Quoted 4 lines · Thomas Schwinge
Quoted 3 lines

Ok, can you do the following:

$ setpci -s 18.0 0x68.l
Quoted 8 lines
    $ sudo setpci -s 18.0 0x68.l
    0f00cc0f
Quoted 1 line
$ rdmsr 0xc001001f
    $ sudo modprobe msr
    $ sudo rdmsr 0xc001001f
    8
Quoted 6 lines

Ok, this is a BIOS bug - we have a recommendation about what the BIOS should do but yours doesn't do it. Are you sure you're using the latest BIOS for your motherboard?

Can you check for updates and if you get a newer version, can you update your BIOS and do the two commands above?

I have now finally been able to check this, and yes, I'm already using the latest version of the BIOS, which is Phoenix cME FirstBIOS Desktop Pro version 5.00 R1.07.2264.A1 (a.k.a. 5.00.1.07, 25.04.2006) for Fujitsu Siemens Esprimo E5600, mainboard D2264-A1, CPU AMD Sempron 3000+.

Quoted 2 lines

If there's no newer BIOS, we can try applying the workaround at boot in an init script to fix your issue.

How'd that be done?

Grüße,
Thomas

#9 lore raw
Quoted 4 lines · Thomas Schwinge

I have now finally been able to check this, and yes, I'm already using the latest version of the BIOS, which is Phoenix cME FirstBIOS Desktop Pro version 5.00 R1.07.2264.A1 (a.k.a. 5.00.1.07, 25.04.2006) for Fujitsu Siemens Esprimo E5600, mainboard D2264-A1, CPU AMD Sempron 3000+.

Ok.

Quoted 4 lines
Quoted 2 lines

If there's no newer BIOS, we can try applying the workaround at boot in an init script to fix your issue.

How'd that be done?

Well, you need to run the following script when the machine boots. I.e., you'd probably have to add it to /etc/init.d/ and make it run at some runlevel, sometime early-ish, before a user can login.

Here's the script, let me know how it goes:

--
#!/bin/bash

# assuming a single CPU system

nb_cfg=0xc001001f
ht_tr_ctl=0x68

val="0x"$(rdmsr $nb_cfg)
val=$(( $val | (1 << 32) ))
val=$(printf "0x%08x" $val)
wrmsr $nb_cfg $val

val="0x"$(setpci -s 18.0 $ht_tr_ctl.l)
val=$(( $val | (1 << 21) ))
val=$(printf "0x%08x" $val)
setpci -s 18.0 $ht_tr_ctl.l=$val

echo "Erratum 169 workaround applied."
---

HTH.

Signature · 8 lines
Regards/Gruss,
Boris.

Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
GM: Alberto Bozzo
Reg: Dornach, Landkreis Muenchen
HRB Nr. 43632 WEEE Registernr: 129 19551
#10 lore raw
Quoted 1 line · Borislav Petkov

Here's the script, let me know how it goes:

Here's a more correct version. I'm not saying yours won't work based on the rdmsr and setpci output on your box, but here's a version which should pay attention to one other workaround and work on all K8s.

HTH.

--
#!/bin/bash

# assuming a single CPU system

nb_cfg=0xc001001f
ht_tr_ctl=0x68

val="0x"$(rdmsr $nb_cfg)

# revert E131 workaround
val=$(( $val & ~(1 << 20) ))

val=$(( $val | (1 << 32) ))
val=$(printf "0x%08x" $val)
wrmsr $nb_cfg $val

val="0x"$(setpci -s 18.0 $ht_tr_ctl.l)

# clear bits [22:21]
val=$(( $val & ~( 0x3 << 21) ))

val=$(( $val | (1 << 21) ))
val=$(printf "0x%08x" $val)
setpci -s 18.0 $ht_tr_ctl.l=$val

echo "Erratum 169 workaround applied."
--

Signature · 8 lines
Regards/Gruss,
Boris.

Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
GM: Alberto Bozzo
Reg: Dornach, Landkreis Muenchen
HRB Nr. 43632 WEEE Registernr: 129 19551
author
#11 lore raw

Hi Borislav!

Quoted 6 lines · Borislav Petkov
Quoted 1 line · Borislav Petkov

Here's the script, let me know how it goes:

Here's a more correct version. I'm not saying yours won't work based on the rdmsr and setpci output on your box, but here's a version which should pay attention to one other workaround and work on all K8s.

Thanks for that. I invoke it from /etc/rc.local, and then get:

    $ sudo setpci -s 18.0 0x68.l
    0f20cc0f
    $ sudo rdmsr 0xc001001f
    100000008

Previously that was:

    $ sudo setpci -s 18.0 0x68.l
    0f00cc0f
    $ sudo rdmsr 0xc001001f
    8

However, putting in that one audio CD still crashes the machine:
<http://schwinge.homeip.net/~thomas/tmp/linux-crash-audio-cd-2.jpeg>.
Original (identical, from a quick glance) MCE is at
<http://schwinge.homeip.net/~thomas/tmp/linux-crash-audio-cd.jpeg>.

Grüße,
Thomas

author
#12 lore raw

Hi!

Quoted 7 lines · On Sat, 22 Sep 2012 13:53:20 +0200, I wrote:
Quoted 4 lines · Borislav Petkov
Quoted 1 line · Borislav Petkov

Here's the script, let me know how it goes:

Here's a more correct version. [...]

However, putting in that one audio CD still crashes the machine: [...]

The problem "solved itself": the machine recently died of hardware failure. ;-|

Grüße,
Thomas

#13 lore raw

Hi Thomas,

Quoted 2 lines · Thomas Schwinge

The problem "solved itself": the machine recently died of hardware failure. ;-|

How convenient. :-P

What happened?

Signature · 5 lines
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--
author
#14 lore raw

Hi Borislav!

Quoted 5 lines · Borislav Petkov
Quoted 2 lines · Thomas Schwinge

The problem "solved itself": the machine recently died of hardware failure. ;-|

How convenient. :-P

;-P

Quoted 1 line

What happened?

The power supply and/or mainboard didn't "wake up" after a recent power cycle. As both these aren't standard form factors (and the machine/architecture had some issues, as discussed, and see also
<http://news.gmane.org/find-root.php?message_id=%3C87r45fajun.fsf%40schwinge.name%3E>
for another issue), I didn't bother looking for spare parts. Want me to ship it to you? ;-)

Grüße,
Thomas

#15 lore raw
Quoted 4 lines · Thomas Schwinge

The power supply and/or mainboard didn't "wake up" after a recent power cycle. As both these aren't standard form factors (and the machine/architecture had some issues, as discussed, and see also
<http://news.gmane.org/find-root.php?message_id=%3C87r45fajun.fsf%40schwinge.name%3E>

Fun.

Quoted 2 lines

for another issue), I didn't bother looking for spare parts. Want me to ship it to you? ;-)

That's nice but I have enough broken hardware here as it is. :-)

You could probably find a better use for it, say a flower pot? :-D

Good luck.

Signature · 5 lines
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--