From: Andrew Morton <akpm@osdl.org>
To: "Barry K. Nathan" <barryn@pobox.com>
Cc: mingo@elte.hu, arjan@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.17-rc5-mm1-lockdep: a rather strange oops
Date: Wed, 31 May 2006 21:33:28 -0700 [thread overview]
Message-ID: <20060531213328.406e71fe.akpm@osdl.org> (raw)
In-Reply-To: <986ed62e0605311947o1eb18b6qce3bb04c41625ffc@mail.gmail.com>
On Wed, 31 May 2006 19:47:10 -0700
"Barry K. Nathan" <barryn@pobox.com> wrote:
> On 5/31/06, Andrew Morton <akpm@osdl.org> wrote:
> > The original oops was a jump-to-null. I had a few of those when getting
> > the latest git-libata-all tree working, due to missing
> > ata_port_operations.data_xfer vectors. But it appears that both sata_sil.c
> > and sata_promise.c do have those filled in.
>
> Ah, but pata_pdc2027x.c doesn't. (Oh, by the way, neither does sata_sil24.c.)
>
> I tried filling it in, with the following patch, but booting that gave
> me lots of weird output before the kernel finally failed to boot from
> the root device. "Lots" meaning, enough that I think I'll need a
> serial console to get anything meaningful. I didn't see any oopses;
> rather, it seemed like the driver was misbehaving. I don't know
> whether the fault is in my patch, or elsewhere in the pdc2027x driver.
> I don't have time tonight (or probably this week, for that matter) to
> look into this further.
>
> As a reminder (in case anyone else jumps into this thread in the
> future), 2.6.17-rc4-mm3 works perfectly...
Right, thanks. I'll drop the ata tree. I have no idea what they were
thinking of, checking in that stuff.
prev parent reply other threads:[~2006-06-01 4:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-01 0:47 Barry K. Nathan
2006-06-01 1:14 ` Andrew Morton
2006-06-01 2:47 ` Barry K. Nathan
2006-06-01 4:33 ` Andrew Morton [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=20060531213328.406e71fe.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=barryn@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
Powered by JetHome