From: Reuben Farrelly <reuben-lkml@reub.net>
To: Andrew Morton <akpm@osdl.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
torvalds@osdl.org, gregkh@suse.de, linux-kernel@vger.kernel.org,
linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: [GIT PATCH] PCI patches for 2.6.15 - retry
Date: Tue, 10 Jan 2006 23:03:29 +1300 [thread overview]
Message-ID: <43C38671.4030805@reub.net> (raw)
In-Reply-To: <20060109174941.41b617f6.akpm@osdl.org>
On 10/01/2006 2:49 p.m., Andrew Morton wrote:
> Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
>> On Llu, 2006-01-09 at 16:44 -0800, Andrew Morton wrote:
>>> - Reuben Farrelly's oops in make_class_name(). Could be libata, or scsi
>>> or driver core.
>> libata I think. I reproduced it on 2.6.14-mm2 by accident with a buggy
>> pata driver.
>
> Well that's all merged up now. Reuben, could you please test 2.6.15git6
> tomorrow?
A couple of reboots later with git6 and at this stage it seems all OK, no oopses.
I'm still having 100% repeatable "soft" hangs when booting up though, both with
-mm2 (-mm1 seems OK in this regard) and git6. It's enough to make git6 and mm2
unusable because the machine never finishes booting userspace. I'll put more
details of that in another email following up to the original -mm2 thread, as
it's unrelated to the oops above (but probably equally as nasty).
But it means I can't test the git6 fixes much more because every time I boot it
I have to alt-sysrq S+U+B or uncleanly kill the box by hitting the reset button.
reuben
next prev parent reply other threads:[~2006-01-10 10:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 20:37 [GIT PATCH] PCI patches for 2.6.15 - retry Greg KH
2006-01-10 0:00 ` Linus Torvalds
2006-01-10 0:44 ` Andrew Morton
2006-01-10 1:49 ` Alan Cox
2006-01-10 1:49 ` Andrew Morton
2006-01-10 10:03 ` Reuben Farrelly [this message]
2006-01-12 3:55 ` Reuben Farrelly
2006-01-12 4:29 ` Andrew Morton
2006-01-12 4:55 ` Reuben Farrelly
2006-01-12 11:42 ` Alan Cox
2006-01-12 20:59 ` Jeff Garzik
2006-01-16 13:11 ` Reuben Farrelly
2006-01-12 20:55 ` Jeff Garzik
2006-01-13 0:16 ` Alan Cox
2006-01-10 2:28 ` Greg KH
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=43C38671.4030805@reub.net \
--to=reuben-lkml@reub.net \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--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