From: Dave Jones <davej@redhat.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.20rc1 oops.
Date: Thu, 28 Dec 2006 15:55:16 -0500 [thread overview]
Message-ID: <20061228205516.GA9462@redhat.com> (raw)
In-Reply-To: <20061228204003.GE20714@stusta.de>
On Thu, Dec 28, 2006 at 09:40:03PM +0100, Adrian Bunk wrote:
> On Sun, Dec 17, 2006 at 10:05:42PM -0500, Dave Jones wrote:
> > On Mon, Dec 18, 2006 at 03:57:10AM +0100, Adrian Bunk wrote:
> > > On Thu, Dec 14, 2006 at 04:02:15PM -0500, Dave Jones wrote:
> > >
> > > > Hmm. Puzzling.
> > >
> > > CONFIG_PCI_MULTITHREAD_PROBE=y ?
> >
> > I pondered that too, and set a kernel building before I left the
> > office on Friday without it. Will try booting it when I get
> > back to it tomorrow.
>
> Did it fix it?
The machine I saw this happen on seemed to have committed suicide.
It didn't even get past the BIOS POST when I was fighting it
just before the holidays.
Tis the season for dead hardware it seems. My home router
ate its disk today too. Hrmph.
Dave
--
http://www.codemonkey.org.uk
prev parent reply other threads:[~2006-12-28 20:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-14 21:02 2.6.20rc1 oops Dave Jones
2006-12-18 2:57 ` Adrian Bunk
2006-12-18 3:05 ` Dave Jones
2006-12-28 20:40 ` Adrian Bunk
2006-12-28 20:55 ` Dave Jones [this message]
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=20061228205516.GA9462@redhat.com \
--to=davej@redhat.com \
--cc=bunk@stusta.de \
--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