mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tester <tester@videotron.ca>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Bizzare crashes on IBM Thinkpad A22e.. yenta_socket related
Date: Tue, 4 Sep 2001 18:17:51 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.33.0109041803010.1614-100000@TesterTop.PolyDom> (raw)
In-Reply-To: <200109011456.f81EutI16218@penguin.transmeta.com>

Hi,

On Sat, 1 Sep 2001, Linus Torvalds wrote:

> In article <Pine.LNX.4.33.0109010022440.1295-100000@TesterTop.PolyDom>,
> Olivier Crete  <Tester@videotron.ca> wrote:
> >
> >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.
>
> What they are doing, however, is to generate a SCI, ie "System Control
> Interrupt". Which, I bet you five bucks, is routed to the same interrupt
> that your CardBus controller is on.

Seems like you may have lost five bucks... When ACPI is enabled the sci is
on IRQ 9, while the CardBus controller is on a IRQ 11 along with
the Sound card, the ethernet card, the modem and the usb controller. The
SCI seems to go to irq 9... and be alone there...  The bug does not happen
when acpi is enabled tho... So I can't confirm...

> So the fact that the system hangs only with the CardBus module loaded
> really has nothing to do with the yenta code itself - it's just that
> before the yenta module is loaded, the SCI will be entirely ignored.
> Once yenta _is_ loaded, however, we have a interrupt handler for the
> interrupt and will start accepting it.
>
> However, the interrupt handler we have is _not_ aware of system
> control interrupts. So it won't be able to handle them, and the
> interrupts will go on forever - locking up the machine.

Where would that loop occur?



-- 
Tester
tester@videotron.ca

Those who do not understand Unix are condemned to reinvent it, poorly. -- Henry Spencer



  parent reply	other threads:[~2001-09-04 22:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
2001-09-07 15:52   ` Linus Torvalds
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
2001-09-01 10:08   ` Erik Mouw
2001-09-01 14:56   ` 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=Pine.LNX.4.33.0109041803010.1614-100000@TesterTop.PolyDom \
    --to=tester@videotron.ca \
    --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

all inboxes | Powered by JetHome®