linux-kernel - Re: Hard lockup with kernel 2.6.25 and 2.6.25.1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080503231813.GA18248@kroah.com>
Date:	Sat, 3 May 2008 16:18:13 -0700
From:	Greg KH <greg@...ah.com>
To:	Malte Schröder <maltesch@....de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Hard lockup with kernel 2.6.25 and 2.6.25.1

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/