From: Alexander Viro <viro@math.psu.edu>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: oops in bk pull (oct 03)
Date: Fri, 4 Oct 2002 20:51:10 -0400 (EDT) [thread overview]
Message-ID: <Pine.GSO.4.21.0210042045010.21250-100000@weyl.math.psu.edu> (raw)
In-Reply-To: <Pine.LNX.4.44.0210041737500.2993-100000@home.transmeta.com>
On Fri, 4 Oct 2002, Linus Torvalds wrote:
>
> On Fri, 4 Oct 2002, Alexander Viro wrote:
> >
> > It is repeatable, it does happen with current BK (well, as of couple
> > of hours ago) and reverting pci/probe.c change apparently cures it.
>
> Really? That probe.c diff is _really_ small, and looks truly obvious. In
> particular, I don't see how it could possibly cause that kind of
> behaviour. What am I missing?
Hell knows. The only explanation I see (and that's not worth much) is that
we somehow confuse the chipset and get crapped on something like next cache
miss.
I'm out of ideas on that one - if you have any suggestions / questions on
details of behaviour I'll be glad to try and see what I can do, but for
now I'm reverting the probe.c patch in my tree so that I could return to
initramfs work. Originally I thought it was a bug in my own code, but oops
is present in 2.5.40-BK and disappears in 2.5.40-BK minus probe.c changeset...
next prev parent reply other threads:[~2002-10-05 0:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-04 20:14 oops in bk pull (oct 03) Paul E. Erkkila
2002-10-04 21:58 ` Linus Torvalds
2002-10-05 0:03 ` Paul E. Erkkila
2002-10-05 0:33 ` Alexander Viro
2002-10-05 0:40 ` Linus Torvalds
2002-10-05 0:51 ` Alexander Viro [this message]
2002-10-05 1:02 ` Linus Torvalds
2002-10-05 1:13 ` David S. Miller
2002-10-05 1:27 ` Alexander Viro
2002-10-05 1:41 ` Linus Torvalds
2002-10-05 2:00 ` David S. Miller
2002-10-05 2:22 ` Linus Torvalds
2002-10-05 2:22 ` David S. Miller
2002-10-05 2:00 ` Linus Torvalds
2002-10-05 3:20 ` Alexander Viro
2002-10-05 3:26 ` Linus Torvalds
2002-10-05 9:35 ` Ivan Kokshaysky
2002-10-05 1:14 ` Alexander Viro
2002-10-05 0:44 ` Alexander Viro
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=Pine.GSO.4.21.0210042045010.21250-100000@weyl.math.psu.edu \
--to=viro@math.psu.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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).