mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Malte Schröder" <maltesch@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Hard lockup with kernel 2.6.25 and 2.6.25.1
Date: Sat, 3 May 2008 16:18:13 -0700	[thread overview]
Message-ID: <20080503231813.GA18248@kroah.com> (raw)
In-Reply-To: <20080504005209.13af2b2c@highlander.home.lan>

On Sun, May 04, 2008 at 12:52:09AM +0200, Malte Schröder wrote:
> Hello,
> my Athlon XP locks up hard with the current stable kernel. Output of
> lspci, the .config and dump from serial console is attached.
> This happens without warning or special actions. 
> This incident happened only a few hours after booting the new kernel,
> SysRq-keys didn't work. 2.6.24.5 has been running fine.
> 
> The problem starts at line 390 of the dump ([42323.063854] eth0:
> command 0x3002 did not complete! Status=0x9000), after that it looks like all pci devices get stuck.
> I hope this mail contains all relevant information.

Hm, this doesn't look good.  Is it repeatable?  Your log shows all the
PCI devices pretty much going out to lunch, which is very odd.

If it's repeatable, it would be interesting if you are able to do a
git-bisect to try to narrow the issue down...

> [    0.674334] ACPI: PCI Interrupt Link [ALKA] disabled and referenced, BIOS bug
> [    0.675016] ACPI: PCI Interrupt Link [ALKA] enabled at IRQ 20
> [    0.675909] ACPI: PCI Interrupt 0000:00:0f.0[A] -> Link [ALKA] -> GSI 20 (level, low) -> IRQ 20

Does these lines also show up in 2.6.24.5?

thanks,

greg k-h

  parent reply	other threads:[~2008-05-03 23:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-03 22:52 Malte Schröder
2008-05-03 23:05 ` Christian Kujau
2008-05-04  9:54   ` Malte Schröder
2008-05-03 23:18 ` Greg KH [this message]
2008-05-04  9:51   ` Malte Schröder
2008-05-04 11:49     ` Malte Schröder
2008-05-04 19:56     ` Jan Engelhardt
2008-05-04 20:22       ` Malte Schröder
2008-05-12 13:28         ` Malte Schröder

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=20080503231813.GA18248@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maltesch@gmx.de \
    /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

all inboxes | Powered by JetHome®