linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Len Brown <len.brown@intel.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Adrian Bunk <bunk@stusta.de>, Chris Wright <chrisw@osdl.org>,
	Bjorn Helgaas <bjorn.helgaas@hp.com>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: 2.6.10-rc2 doesn't boot (if no floppy device)
Date: 19 Nov 2004 13:51:06 -0500	[thread overview]
Message-ID: <1100890266.987.124.camel@d845pe> (raw)
In-Reply-To: <Pine.LNX.4.58.0411190935210.2222@ppc970.osdl.org>

On Fri, 2004-11-19 at 12:36, Linus Torvalds wrote:
> 
> On Fri, 19 Nov 2004, Adrian Bunk wrote:
> >
> > It's not a problem (I just wasn't sure, whether enabling APIC might
> > change something relevant.
> 
> It did. You no longer show the problem. No irq storm.
> 
> So can you disable APIC again, and just remove the non-relevant APIC
> print
> calls to get it to compile?

I think if you boot the kernel you have with "nolapic" that will be a
valid test for us to examine PIC mode.

thanks,
-Len

ps. I'm curious why you were running with !IOAPIC kernel suport on a
system which has an IOAPIC.



  reply	other threads:[~2004-11-19 18:52 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <F7DC2337C7631D4386A2DF6E8FB22B30020B7225@hdsmsx401.amr.corp.intel.com>
2004-11-19 15:57 ` 2.6.10-rc2 doesn't boot (if no floppy device) Adrian Bunk
2004-11-19 17:36   ` Linus Torvalds
2004-11-19 18:51     ` Len Brown [this message]
2004-11-19 19:11     ` Adrian Bunk
2004-11-19 21:05       ` Len Brown
2004-11-15 23:27 2.6.10-rc2 doesn't boot Chris Wright
2004-11-18 23:14 ` 2.6.10-rc2 doesn't boot (if no floppy device) Len Brown
2004-11-19  7:09   ` Chris Wright
2004-11-20  9:02     ` Len Brown
2004-11-20 12:40       ` Adrian Bunk
2004-11-20 18:28         ` Linus Torvalds
2004-11-20 19:10           ` Linus Torvalds
2004-11-22 19:55             ` Len Brown
2004-11-24 16:26             ` Alan Cox
2004-11-21 16:29           ` Adrian Bunk
2004-11-22 19:29           ` Len Brown
2004-11-22 20:02             ` Linus Torvalds
2004-11-22 20:10               ` Linus Torvalds
2004-11-22 20:38               ` Len Brown
2004-11-23  2:45                 ` Linus Torvalds
2004-11-23  4:57                   ` Linus Torvalds
2004-11-23  7:06                     ` Len Brown
2004-11-23 20:13                       ` Stian Jordet
2004-11-23  2:00           ` Chris Wright
2004-11-22 18:28         ` Len Brown
2004-11-23  0:46           ` Adrian Bunk
2004-11-20 16:41       ` Linus Torvalds
2004-11-22 19:07         ` Len Brown
2004-11-22 19:23           ` Linus Torvalds
2004-11-22 20:24             ` Len Brown
2004-11-22 20:31               ` Linus Torvalds
2004-11-22 20:36                 ` Linus Torvalds
2004-11-22 20:54                   ` Len Brown
2004-11-22 20:51                 ` Len Brown
2004-11-23  1:58       ` Chris Wright
2004-11-19 13:47   ` Adrian Bunk
2004-11-23  1:57   ` Chris Wright

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=1100890266.987.124.camel@d845pe \
    --to=len.brown@intel.com \
    --cc=akpm@osdl.org \
    --cc=bjorn.helgaas@hp.com \
    --cc=bunk@stusta.de \
    --cc=chrisw@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).