mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Christoph Pfister" <christophpfister@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: apic doesn't work with 32bit kernel (fine with 64bit) [asus m2n-mx se+]
Date: Sun, 13 Apr 2008 10:54:09 -0700	[thread overview]
Message-ID: <86802c440804131054y73fa94e3jd12172d206eea510@mail.gmail.com> (raw)
In-Reply-To: <200804131459.21494.christophpfister@gmail.com>

On Sun, Apr 13, 2008 at 5:59 AM, Christoph Pfister
<christophpfister@gmail.com> wrote:
> Am Sonntag 13 April 2008 01:15:51 schrieb Yinghai Lu:
>
> > On Sat, Apr 12, 2008 at 12:20 PM, Christoph Pfister
>  >
>  > <christophpfister@gmail.com> wrote:
>  > > Hi,
>  > >
>  > >  Using a new motherboard, I came across a kernel panic (dmesg using
>  > > 2.6.25-rc9 [x86_32] transcribed from screenshot attached; also dmesg when
>  > >  using "apic=debug").
>  > >  The system works nearly fine when using "noapic" (setting rtc doesn't
>  > > work).
>  > >
>  > >  Everything (including apic and rtc) works like a charm when I use the
>  > > x86_64 version with (nearly) the same kernel config (dmesg attached as
>  > > well).
>  >
>  > how about booting 64 bit apic=debug?
>
>  Attached.
>
>
>  > wonder if using kexec to load 32bit kernel from 64 bit kernel help.
>
>  What should it help? Btw, grabbed a good old RS232 cable to get more than 25
>  lines of dmesg :) - attached as well.

only difference, it seems 32bit enable io_apic after all cpus up.  and
64 bit will enable that just after first cpu.

YH

  reply	other threads:[~2008-04-13 17:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-12 19:20 Christoph Pfister
2008-04-12 23:15 ` Yinghai Lu
2008-04-13 12:59   ` Christoph Pfister
2008-04-13 17:54     ` Yinghai Lu [this message]
     [not found] <fa.cFaRDMDkljz4TwOkZV0Dhak5m18@ifi.uio.no>
     [not found] ` <fa.zwnYdR7hO236OsY7D7xpBHFqamg@ifi.uio.no>
     [not found]   ` <fa.I3ijyTO9+3ZregkYrEZysrj5r6g@ifi.uio.no>
2008-04-13 17:52     ` Robert Hancock

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=86802c440804131054y73fa94e3jd12172d206eea510@mail.gmail.com \
    --to=yhlu.kernel@gmail.com \
    --cc=christophpfister@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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®