From: Dave Jones <davej@redhat.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Linus Torvalds <torvalds@osdl.org>, Tomasz Torcz <zdzichu@irc.pl>,
Greg KH <gregkh@suse.de>, Adrian Bunk <bunk@stusta.de>,
Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-pci@atrey.karlin.mff.cuni.cz,
pcihpd-discuss@lists.sourceforge.net,
Ben Collins <ben.collins@ubuntu.com>
Subject: Re: State of the Linux PCI and PCI Hotplug Subsystems for 2.6.16-rc5
Date: Thu, 9 Mar 2006 15:46:39 -0500 [thread overview]
Message-ID: <20060309204639.GA453@redhat.com> (raw)
In-Reply-To: <1141936671.2883.33.camel@laptopd505.fenrus.org>
On Thu, Mar 09, 2006 at 09:37:50PM +0100, Arjan van de Ven wrote:
> On Thu, 2006-03-09 at 11:49 -0800, Linus Torvalds wrote:
> >
> > On Thu, 9 Mar 2006, Tomasz Torcz wrote:
> > > >
> > > > "Fedora rawhide kernel stopped booting for a bunch of people, all with
> > > > 686-SMP boxes. I saw it myself too, it hung just after the 'write
> > > > protecting kernel rodata'.
> > > >
> > >
> > > Ubuntu has similar problem:
> > > https://launchpad.net/distros/ubuntu/+source/linux-source-2.6.15/+bug/29601
> > > I believe Ubuntu's 2.6.15 source is vanilla+git patches.
> >
> > Interesting. He also apparently boots with "noapic nolapic" on the "386"
> > kernel, but not the "686" kernel.
>
> hmm curious; I wonder if the "weird" (as in, Arjan considers it a stupid
> idea and broken) "enable APIC on UP but not really" patch is at fault
> here, which isn't in mainline....
Not present in the Fedora kernels any more, and this bug has been seen in
ones without it.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-03-09 20:48 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-06 22:35 State of the Linux PCI and PCI Hotplug Subsystems for 2.6.16-rc5 Greg KH
2006-03-06 22:47 ` Sam Ravnborg
2006-03-06 23:00 ` Greg KH
2006-03-08 22:26 ` Adrian Bunk
2006-03-08 22:50 ` Greg KH
2006-03-08 23:03 ` Linus Torvalds
2006-03-08 23:18 ` Greg KH
2006-03-08 23:30 ` Linus Torvalds
2006-03-09 18:40 ` Tomasz Torcz
2006-03-09 19:49 ` Linus Torvalds
2006-03-09 20:10 ` Ben Collins
2006-03-09 20:24 ` Linus Torvalds
2006-03-15 16:03 ` Ben Collins
2006-03-09 20:52 ` Lee Revell
2006-03-09 21:06 ` SMP on UP (Was Re: State of the Linux PCI and PCI Hotplug Subsystems for 2.6.16-rc5) Ben Collins
2006-03-09 21:47 ` Lee Revell
2006-03-09 21:07 ` State of the Linux PCI and PCI Hotplug Subsystems for 2.6.16-rc5 David S. Miller
2006-03-09 20:37 ` Arjan van de Ven
2006-03-09 20:46 ` Dave Jones [this message]
2006-03-09 21:15 ` Arjan van de Ven
2006-03-08 23:29 ` Andrew Morton
2006-03-08 23:45 ` Dave Hansen
2006-03-08 23:52 ` Andrew Morton
2006-03-09 10:24 ` Martin MOKREJŠ
2006-03-08 23:05 ` Adrian Bunk
2006-03-08 23:18 ` Lee Revell
2006-03-08 23:23 ` Greg KH
2006-03-08 23:34 ` Lee Revell
2006-03-08 23:40 ` Greg KH
2006-03-09 0:03 ` Lee Revell
2006-03-08 23:21 ` Greg KH
2006-03-09 4:01 ` Kenji Kaneshige
2006-03-09 5:34 ` Greg KH
2006-03-09 5:11 ` Lee Revell
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=20060309204639.GA453@redhat.com \
--to=davej@redhat.com \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=ben.collins@ubuntu.com \
--cc=bunk@stusta.de \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=pcihpd-discuss@lists.sourceforge.net \
--cc=torvalds@osdl.org \
--cc=zdzichu@irc.pl \
/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