From: Jonathan Nieder <jrnieder@gmail.com>
To: trouble daemon <troubledaemon@gmail.com>
Cc: Adam Belay <abelay@mit.edu>, Bjorn Helgaas <bhelgaas@google.com>,
linux-kernel@vger.kernel.org
Subject: Re: Possible PNP issue on Dell PowerEdge 4200 unless noapic used
Date: Sat, 24 Sep 2011 19:28:32 -0500 [thread overview]
Message-ID: <20110925002831.GA32152@elie> (raw)
In-Reply-To: <CAK82gMF0EbPiTATjPZ2-K5fCtuJHAXH2aJgpwCD5CRDLS2YpqQ@mail.gmail.com>
(just cc-ing linux-kernel so any work on this gets archived)
trouble daemon wrote:
> Greetings,
>
> Hello Adam and Bjorn. I am sending this email to you as suggested by
> Jonathan regarding a problem that I was having with Linux on a pair of
> old Dell PowerEdge 4200 machines that I own (yes, they still run!).
>
> I have left the most recent reply between Jonathan and I quoted below,
> but you can find the original bug report at the Debian bug tracker
> under bug #586494 [1]. As a brief recap, I have been required to use
> the noapic kernel option in these systems in order to allow them to
> boot, and appears to have originated after a commit to the kernel
> relating to EISA (although it has come to my attention now that PNP
> may be related as well).
>
> As suggested, I have attached a copy of the "quick & dirty" config I
> used for a vanilla 3.1.0-rc7 kernel I compiled, along with the boot
> log of the machine, and a diff against the apic log of a working boot
> of the same kernel when using noapic. One thing that I should mention
> is that on these dells, I also usually use the pnpbios=off option to
> hide the pesky warnings on boot, in addition to noapic.
>
> I hope these logs help you in some way. If there is anything else you
> might be interested in knowing or testing, don't hesitate to ask!
Original report: http://thread.gmane.org/gmane.linux.kernel/1000807
Logs: http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=86;bug=586494
> Dan McGrath
>
> PS - Not a problem Jonathan, thanks!
>
> [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586494
next parent reply other threads:[~2011-09-25 0:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAK82gMF0EbPiTATjPZ2-K5fCtuJHAXH2aJgpwCD5CRDLS2YpqQ@mail.gmail.com>
2011-09-25 0:28 ` Jonathan Nieder [this message]
2011-09-25 12:24 ` Possible PNP issue on Dell PowerEdge 4200 unless noapic used Bjorn Helgaas
2011-09-25 18:40 ` trouble daemon
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=20110925002831.GA32152@elie \
--to=jrnieder@gmail.com \
--cc=abelay@mit.edu \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=troubledaemon@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.