public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gerd Knorr <kraxel@bytesex.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Bizzare crashes on IBM Thinkpad A22e.. yenta_socket related
Date: 1 Sep 2001 06:17:07 GMT	[thread overview]
Message-ID: <slrn9p0vb3.1md.kraxel@bytesex.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0108311244070.2899-100000@TesterTop.PolyDom> <Pine.LNX.4.33.0109010022440.1295-100000@TesterTop.PolyDom>

Olivier Crete wrote:
>  Hi,
>  
>  Ok, I've tried removing different parts of the kernel and I have been able
>  to find that the instability (repetable freezes) start to appear when the
>  yenta_socket.o module is loaded. I dont see the link between this module
>  and the events that trigger the freezes... It crashes when I do the
>  following things: use any of the non-keyboard buttons (thinkpad buttons
>  and volume control), brightness control, etc.. These buttons fn-X
>  combination have in common that they do not generate a scancode as shown
>  by showkey.

Try -ac kernels with PNPBIOS enabled ...

  Gerd

-- 
Damn lot people confuse usability and eye-candy.

  reply	other threads:[~2001-09-01  6:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20010831081028.A12005@dev.sportingbet.com>
2001-08-31 16:46 ` Bizzare crashes on IBM Thinkpad A22e Tester
2001-09-01  4:50   ` Bizzare crashes on IBM Thinkpad A22e.. yenta_socket related Olivier Crete
2001-09-01  6:17     ` Gerd Knorr [this message]
2001-09-01 10:08     ` Erik Mouw
2001-09-01 14:56     ` Linus Torvalds
     [not found] <200109011456.f81EutI16218@penguin.transmeta.com>
2001-09-01 19:21 ` Tester
2001-09-02  1:25   ` Linus Torvalds
2001-09-02  6:29     ` Tester
2001-09-02 18:22       ` Gunther Mayer
2001-09-02 21:51         ` Tester
2001-09-02 22:38           ` Alan Garrison
2001-09-04 22:17 ` Tester
2001-09-07 15:52   ` Linus Torvalds

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=slrn9p0vb3.1md.kraxel@bytesex.org \
    --to=kraxel@bytesex.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