mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: rct@gherkin.frus.com (Bob Tracy)
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Randy Dunlap <randy.dunlap@oracle.com>, linux-kernel@vger.kernel.org
Subject: Re: [BUG] (regression) AMD k6-III/450 won't boot w/2.6.22-rc1
Date: Wed, 16 May 2007 08:15:58 -0500 (CDT)	[thread overview]
Message-ID: <20070516131558.E15BFDBA1@gherkin.frus.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0705160903130.9570@yvahk01.tjqt.qr> "from Jan Engelhardt at May 16, 2007 09:03:43 am"

Jan Engelhardt wrote:
> >On Tue, 15 May 2007 22:13:14 -0500 (CDT) Bob Tracy wrote:
> >
> >> The 2.6.22-rc1 boot panics early in amd_mcheck_init() with my k6-III/450.
> 
> In short, boot with vga=6 (80x50), or even vga=ask, selecting something with
> lots of chars (132x60 for example)

That did it...

(...)
CPU: L1 I Cache: (...)
CPU: L2 Cache: (...)
Intel machine check architecture supported.
general protection fault: 0000 [#1]
PREEMPT
Modules linked in:
CPU:   0
EIP: 0060:[<c01079f4>]  Not tainted VLI
EFLAGS: 00010286   (2.6.22-rc1 #1)
EIP is at amd_mcheck_init+0x2b/0xc3
eax: 0000002f  ebx: 00000000  ecx: 00000179  edx: 00000001
esi: 000a0b00  edi: c03c1000  ebp: 00843007  esp: c03c7fb0
ds:007b  es:007b  fs:0000  gs:0000  ss:0068
Process swapper (pid:0, ti=c03c6000 task=c0399a20 task.ti=c03c6000)
Stack: c03569fc 00000000 00843007 c0189398 ffffffff 00000000 000a0600 c03cb34f
       00000002 c03a2b40 00000000 c03cb79c 00040000 00000000 00000000 c03c8842
       00000054 c03c8388 c03dfb40 00000000
Call Trace:
 [<c0189398>] proc_register+0x3b/0xb7
 [<c03cb34f>] identify_boot_cpu+0xd/0x1f
 [<c03cb79c>] check_bugs+0x8/0x4e
 [<c03c8842>] start_kernel+0x19a/0x1a3
 [<c03c8388>] unknown_bootoption+0x0/0x191
==========================================
Code: 56 53 83 ec 14 c7 05 08 f1 39 c0 3c 78 10 c0 8b 40 0c a8 80 0f 84 a0 00 00 00 c7 04 24 fc 69 35 c0 e8 79 f3 00 00 b9 79 01 00 00 <0f> 32 f6 c4 01 89 c3 74 0a b1 7b 83 c8 ff 83 ca ff 0f 30 0f b6
EIP:[<c01079f4>] amd_mcheck_init+0x2b/0xc3 SS:ESP 0068:c03c7fb0
Kernel panic - not syncing: Attempted to kill the idle task!

-- 
-----------------------------------------------------------------------
Bob Tracy                   WTO + WIPO = DMCA? http://www.anti-dmca.org
rct@frus.com
-----------------------------------------------------------------------

  reply	other threads:[~2007-05-16 13:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-16  3:13 Bob Tracy
2007-05-16  4:27 ` Randy Dunlap
2007-05-16  7:03   ` Jan Engelhardt
2007-05-16 13:15     ` Bob Tracy [this message]
2007-05-16 15:53       ` Chuck Ebbert
2007-05-16 16:30         ` Dave Jones
2007-05-16 19:11           ` Bob Tracy
2007-05-16 19:22             ` Dave Jones
2007-05-16 21:07               ` Dave Jones
2007-05-17  4:36                 ` Bob Tracy
2007-05-17  6:08                   ` Dave Jones
2007-05-17 12:34                     ` Bob Tracy
2007-05-17 12:35         ` Andi Kleen
2007-05-17 12:54           ` Bob Tracy
2007-05-17 23:38           ` Bob Tracy
2007-05-18 14:38             ` Joachim Deguara

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=20070516131558.E15BFDBA1@gherkin.frus.com \
    --to=rct@gherkin.frus.com \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    /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

Powered by JetHome