From: Prakash Punnoor <prakash@punnoor.de>
To: "Gerd v. Egidy" <lists@egidy.de>
Cc: linux-kernel@vger.kernel.org,
Thomas Richter <thor@mail.math.tu-berlin.de>
Subject: Re: APIC on Asus M2N SLI Deluxe
Date: Mon, 18 Sep 2006 18:17:39 +0200 [thread overview]
Message-ID: <200609181817.39498.prakash@punnoor.de> (raw)
In-Reply-To: <200609181804.36428.lists@egidy.de>
[-- Attachment #1: Type: text/plain, Size: 1239 bytes --]
Am Montag 18 September 2006 18:04 schrieb Gerd v. Egidy:
> > > > recently, I tried to upgrade the bios of the ASUS M2N SLI Deluxe
> > > > board from release 0202 to 0307. With the 0307 bios, I get a kernel
> > > > panic that the APIC cannot be found. Concerning this, I've two
> > > > explanations, could possibly confirm someone here this:
> > >
> > > I can confim this problem.
> >
> > Does it boot with no_timer_check boot parameter?
>
> no, same bug.
>
> Booting with apic=debug as suggested in the error message doesn't reveal
> any additional details. Maybe I have to compile with some special debug
> options?
I don't think so. I once had the same problem with my board. On 2.6.16.x I got
same message. 2.6.18-rcx booted further, but hanged. Above parameter helped
though with 2.6.18-rc. As I haven't tested 2.6.17 nor 2.6.16 with obve
parameter, I could only guess. The real fix for me though was to disable the
nvidia quirk. Then my system boots and runs fine with 2.6.18-rc kernel w/o
any additional parameter. You may want to look into:
http://marc.theaimsgroup.com/?l=linux-kernel&m=115545986619977&w=2
Cheers,
--
(°= =°)
//\ Prakash Punnoor /\\
V_/ \_V
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-09-18 16:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-14 10:17 Thomas Richter
2006-09-17 19:21 ` Gerd v. Egidy
2006-09-17 20:03 ` Prakash Punnoor
2006-09-18 16:04 ` Gerd v. Egidy
2006-09-18 16:17 ` Prakash Punnoor [this message]
2006-09-17 20:03 Olivier Nicolas
2006-09-17 22:31 ` Gerd v. Egidy
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=200609181817.39498.prakash@punnoor.de \
--to=prakash@punnoor.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@egidy.de \
--cc=thor@mail.math.tu-berlin.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®