* Oops on x86_64 after upgrade to 2.6.19.1. (ACPI related?)
@ 2007-01-08 20:10 Andrew Walrond
2007-01-10 13:53 ` Andrew Walrond
0 siblings, 1 reply; 2+ messages in thread
From: Andrew Walrond @ 2007-01-08 20:10 UTC (permalink / raw)
To: LKML
[-- Attachment #1: Type: text/plain, Size: 209 bytes --]
I was running 2.6.18.3 before, which worked fine.
Only managed to get a screen grab from remote KVM, but hope its useful.
I'll try latest rc when I can get someone to reset the (remote) box.
Andrew Walrond
[-- Attachment #2: oops.JPG --]
[-- Type: image/jpeg, Size: 33542 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Oops on x86_64 after upgrade to 2.6.19.1. (ACPI related?)
2007-01-08 20:10 Oops on x86_64 after upgrade to 2.6.19.1. (ACPI related?) Andrew Walrond
@ 2007-01-10 13:53 ` Andrew Walrond
0 siblings, 0 replies; 2+ messages in thread
From: Andrew Walrond @ 2007-01-10 13:53 UTC (permalink / raw)
To: LKML
[-- Attachment #1: Type: text/plain, Size: 460 bytes --]
Andrew Walrond wrote:
> I was running 2.6.18.3 before, which worked fine.
>
> Only managed to get a screen grab from remote KVM, but hope its useful.
>
> I'll try latest rc when I can get someone to reset the (remote) box.
>
Same result with 2.6.20-rc4. Screen grab attached.
To reiterate, 2.6.18.3 works fine. 2.6.19.1+ panics on boot.
This is a dual opteron system with recent BIOS
Anything I can try to diagnose, please shout :)
> Andrew Walrond
[-- Attachment #2: 2.6.20-rc4.JPG --]
[-- Type: image/jpeg, Size: 50575 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2007-01-10 13:53 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-01-08 20:10 Oops on x86_64 after upgrade to 2.6.19.1. (ACPI related?) Andrew Walrond
2007-01-10 13:53 ` Andrew Walrond
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox