public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Schwinge <thomas@codesourcery.com>
To: Borislav Petkov <bp@alien8.de>
Cc: debian-kernel@lists.debian.org, linux-ide@vger.kernel.org,
	linux-scsi@vger.kernel.org
Subject: Re: Linux kernel crash (3.2.0-2-amd64) when trying to play audio CD
Date: Mon, 18 Jun 2012 07:28:07 +0200	[thread overview]
Message-ID: <87ehpddw9k.fsf@schwinge.name> (raw)
In-Reply-To: <20120616181008.GB20623@liondog.tnic>

[-- Attachment #1: Type: text/plain, Size: 1773 bytes --]

Hi!

On Sat, 16 Jun 2012 20:10:08 +0200, Borislav Petkov <bp@alien8.de> wrote:
> On Sat, Jun 16, 2012 at 12:14:14PM +0200, Thomas Schwinge wrote:
> > 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.
> 
> Let me guess: AMD K8?

Correct.

> 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

[-- Attachment #2: Type: application/pgp-signature, Size: 489 bytes --]

  reply	other threads:[~2012-06-18  5:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-16 10:14 Linux kernel crash (3.2.0-2-amd64) when trying to play audio CD Thomas Schwinge
2012-06-16 13:40 ` Ben Hutchings
2012-06-18  5:29   ` Thomas Schwinge
2012-06-16 18:10 ` Borislav Petkov
2012-06-18  5:28   ` Thomas Schwinge [this message]
2012-06-18 14:29     ` Borislav Petkov
2012-06-18 14:52       ` Thomas Schwinge
2012-06-18 15:51         ` Borislav Petkov
2012-09-07  9:14           ` Thomas Schwinge
2012-09-13 12:58             ` Borislav Petkov
2012-09-17 17:23               ` Borislav Petkov
2012-09-22 11:53                 ` Thomas Schwinge
2014-06-16  7:13                   ` Thomas Schwinge
2014-06-16  9:43                     ` Borislav Petkov
2014-06-16 10:33                       ` Thomas Schwinge
2014-06-16 10:46                         ` Borislav Petkov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ehpddw9k.fsf@schwinge.name \
    --to=thomas@codesourcery.com \
    --cc=bp@alien8.de \
    --cc=debian-kernel@lists.debian.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox