From: Sid Boyce <sboyce@blueyonder.co.uk>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Len Brown <len.brown@intel.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.7-rc2-mm1 (nforce2 lockup)
Date: Sat, 05 Jun 2004 23:08:11 +0100 [thread overview]
Message-ID: <40C2444B.4080403@blueyonder.co.uk> (raw)
In-Reply-To: <200406050937.29163.bjorn.helgaas@hp.com>
Bjorn Helgaas wrote:
>On Friday 04 June 2004 10:00 pm, Sid Boyce wrote:
>
>
>>I just built and successfully booted 2.6.7-rc2-mm2 IOAPIC enabled and
>>without boot option acpi=off. I guess somewhere IOAPIC was inadvertently
>>disabled in .config.
>>
>>
>
>So I guess IOAPIC was enabled in your pre-mm1 builds that worked?
>
>I just want to make sure my patch doesn't add a requirement for
>IOAPIC where it wasn't required before.
>
>My assumption is that
> - 2.6.7-rc2 without IOAPIC fails (I'm not sure you've tried
> this; I don't think I've seen a report either way)
>
>
That works. Somewhere along the way, IOAPIC got removed from my .config.
> - 2.6.7-rc2 with IOAPIC works
>
>
I haven't tried.
> - 2.6.7-rc2-mm2 without IOAPIC fails
>
>
Correct.
> - 2.6.7-rc2-mm2 with IOAPIC works
>
>
Correct.
Regards
Sid.
--
Sid Boyce .... Hamradio G3VBV and keen Flyer
Linux Only Shop.
next prev parent reply other threads:[~2004-06-05 22:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A6974D8E5F98D511BB910002A50A6647615FD33E@hdsmsx403.hd.intel.com>
2004-06-04 21:45 ` 2.6.7-rc2-mm1 (nforce2 lockup) Len Brown
2004-06-05 2:55 ` Sid Boyce
2004-06-05 4:00 ` Sid Boyce
2004-06-05 4:46 ` Len Brown
2004-06-06 18:50 ` Sid Boyce
2004-06-05 15:37 ` Bjorn Helgaas
2004-06-05 22:08 ` Sid Boyce [this message]
2004-06-10 22:51 ` Bjorn Helgaas
2004-06-11 1:07 ` Sid Boyce
2004-06-11 15:46 ` Sid Boyce
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=40C2444B.4080403@blueyonder.co.uk \
--to=sboyce@blueyonder.co.uk \
--cc=bjorn.helgaas@hp.com \
--cc=len.brown@intel.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 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.