mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "willy tarreau" <wtarreau@yahoo.fr>
To: alan@lxorguk.ukuu.org.uk, jdthood@mail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.19pre3-ac2
Date: Tue, 19 Mar 2002 20:35:53 +0100 (CET)	[thread overview]
Message-ID: <20020319193553.25896.qmail@web20501.mail.yahoo.com> (raw)

Hi !

Well, I discovered today that reading /proc/bus/pnp/0e
oopsed on me on 2.4.19p2 with the 2.4.17 pnpbios
patch (+lots of other patches that don't help to
make easy reports). Didn't try without pnpbios yet.
lspnp -v triggers it very easily. 0e is the PS2 port
(PNP0f13). I had this on at least two P3's with
different hardware and bioses.

So I tried plain 2.4.19-pre3-ac2, and now it
reboots immediately. I've tried 3 versions
down to 2.4.10-ac12 which segfaults too.
Other pnp entries can be read perfectly
(can provide dump if it helps).

I will send the ksymoops report from 2.4.19p2
with 2.4.17 pnpbios when I get home (because
I'd like to get a real email client - elm). At least
at the moment, I can resume the end of the
report to this :

>>EIP; 0000879a Before first symbol   <=====
c014daf8 <get_new_inode+48/1a4>
c014dbca <get_new_inode+11a/1a4>
c021aa2c <__pnp_bios_get_dev_node+110/16c>
c0120000 <sys_capset+238/288>
c0120018 <sys_capset+250/288>
c021aa9e <pnp_bios_get_dev_node+16/34>
c021bbe0 <proc_read_node+44/88>
c0156f0a <proc_file_read+f2/1bc>
c0139326 <sys_read+8e/110>
c010744a <tracesys+1e/22>

Please note that it doesn't really affect me
because I don't need pnpbios on these hosts,
but some people may be concerned about the
security risk since the entry is world-readable.
I'm just always trying to build better kernels ;-)

Hope this helps. I'll be able to do more tests
if other people cannot reproduce.

Cheers,
Willy


___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com

             reply	other threads:[~2002-03-19 19:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-19 19:35 willy tarreau [this message]
2002-03-19 20:02 ` Alan Cox
2002-03-19 21:29   ` willy tarreau
  -- strict thread matches above, loose matches on Subject: below --
2002-03-19 18:52 willy tarreau
2002-03-19 19:08 ` Mike Fedyk
2002-03-19 19:45   ` willy tarreau
2002-03-19 17:28 Alan Cox
2002-03-19 17:57 ` Adrian Bunk
2002-03-19 18:43   ` Randy.Dunlap
2002-03-19 23:56   ` Randy.Dunlap
2002-03-20  0:14     ` Alan Cox
2002-03-19 18:42 ` Adrian Bunk
2002-03-19 18:59   ` Alan Cox
2002-03-19 19:01     ` Mike Fedyk
2002-03-20  9:49 ` Christoph Hellwig
2002-03-20 17:54 ` Christoph Hellwig
2002-03-20 23:54   ` Alan Cox

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=20020319193553.25896.qmail@web20501.mail.yahoo.com \
    --to=wtarreau@yahoo.fr \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jdthood@mail.com \
    --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®