From: David Monro <davidm@amberdata.demon.co.uk>
To: linuxppc-workstation@lists.linuxppc.org, linuxppc-dev@lists.linuxppc.org
Subject: Re: IRQ problems on IBM 850
Date: Wed, 08 Dec 1999 17:33:38 +0000 [thread overview]
Message-ID: <384E9672.7632BAB9@amberdata.demon.co.uk> (raw)
In-Reply-To: Pine.HPX.4.10.9911050931010.2724-100000@gra-ux1.iram.es
Sorry to reply so late, but I went on holiday.
Gabriel Paubert wrote:
>
> On Thu, 4 Nov 1999, Hollis R Blanchard wrote:
>
[..]
>
> Using interrupt 13 is strange, to say the least. It was reserved for FPU
> errors on x86 processors. In your case obviously the interrupts are
> expected (since you have a timeout) but have stayed masked for some
> reason. We have to find where this happens. Some code paths might have an
> unbalanced enable/disable_irq but I suspect that it will be hard to find.
>
Umm. Possible data point which may help here - I cannot cause my machine
to do anything silly unless I hit two interrupt sources at the same
time. I can compile kernels on the IDE disk (irq 13) till the cows come
home if I don't have the ethernet enabled and don't play with the mouse
too much. If I enable the ethernet (irq 15 I think), or play with the
mouse a lot (irq 12), sooner or later I die. My (very uneducated) guess
is that it has something to do with getting two interrupts in a very
short space of time. I guess I should try thrashing one of the lower 8
interrupts (serial mouse I guess would do it) and see if that can cause
problems, or whether it is restricted to the second controller.
[..]
Cheers,
David
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-12-08 17:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.HPX.4.10.9910252356120.21757-100000@gra-ux1.iram.es>
1999-11-04 5:33 ` IRQ problems on IBM 850 Hollis R Blanchard
1999-11-04 13:27 ` Gabriel Paubert
1999-11-04 20:32 ` Hollis R Blanchard
1999-11-05 8:42 ` Gabriel Paubert
1999-12-08 17:33 ` David Monro [this message]
1999-12-09 1:33 ` Hollis R Blanchard
1999-12-09 9:14 ` Gabriel Paubert
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=384E9672.7632BAB9@amberdata.demon.co.uk \
--to=davidm@amberdata.demon.co.uk \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=linuxppc-workstation@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.