From: David Gibson <hermes@gibson.dropbear.id.au>
To: "John T. Guthrie" <guthrie@counterexample.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [OOPS] reading /proc/hermes/eth1/recs causes an oops in 2.5.69
Date: Wed, 28 May 2003 09:40:39 +1000 [thread overview]
Message-ID: <20030527234039.GA20861@zax> (raw)
In-Reply-To: <200305270803.h4R83dMc010911@gauss.counterexample.org>
On Tue, May 27, 2003 at 04:03:39AM -0400, John T. Guthrie wrote:
> Hello all,
>
> I'm currently running Red Hat linux 8.0 on my Inspiron 8100 laptop. Last
> night, I decided to check out a recent 2.5 kernel. While wandering around
> in the /proc filesystem, I came across /proc/hermes/eth1/recs. From what I
> had seen in under 2.4.21-pre4, it should have just given me a whole bunch of
> interesting information about my wireless card. Instead, just attempting to
> read the file caused an oops. After the initial oops, the machine wasn't
> completely unresponsive, I could still press the keyboard one more time to
> generate yet another oops, but then the machine would be completely
> unresponsive and had to be power cycled.
Doesn't surprise me all that much - there are a lot of bugs in 0.13a,
the driver version in 2.5.69.
In 0.13e, the latest version, the /proc support has been abolished in
favour of a simpler debugging hack. I intend to retransmit a patch to
update the driver today.
--
David Gibson | For every complex problem there is a
david@gibson.dropbear.id.au | solution which is simple, neat and
| wrong.
http://www.ozlabs.org/people/dgibson
prev parent reply other threads:[~2003-05-27 23:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-27 8:03 John T. Guthrie
2003-05-27 9:07 ` Zwane Mwaikambo
2003-05-27 23:40 ` David Gibson [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=20030527234039.GA20861@zax \
--to=hermes@gibson.dropbear.id.au \
--cc=guthrie@counterexample.org \
--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
all inboxes | Powered by JetHome®