linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Schwinge <thomas@codesourcery.com>
To: Borislav Petkov <bp@amd64.org>
Cc: Borislav Petkov <bp@alien8.de>,
	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: Fri, 7 Sep 2012 11:14:33 +0200	[thread overview]
Message-ID: <877gs69oue.fsf@schwinge.name> (raw)
In-Reply-To: <20120618155141.GF8378@aftab.osrc.amd.com>

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

Hi Borislav!

I'm sorry for the late answer.


On Mon, 18 Jun 2012 17:51:41 +0200, Borislav Petkov <bp@amd64.org> wrote:
> On Mon, Jun 18, 2012 at 04:52:36PM +0200, Thomas Schwinge wrote:
> > > Ok, can you do the following:
> > > 
> > > $ setpci -s 18.0 0x68.l
> > 
> >     $ sudo setpci -s 18.0 0x68.l
> >     0f00cc0f
> > 
> > > $ 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?

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+.

> 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

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

  reply	other threads:[~2012-09-07  9:14 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
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 [this message]
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=877gs69oue.fsf@schwinge.name \
    --to=thomas@codesourcery.com \
    --cc=bp@alien8.de \
    --cc=bp@amd64.org \
    --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;
as well as URLs for NNTP newsgroup(s).