From: Ralf Baechle <ralf@mailhost.uni-koblenz.de>
To: miguel@nuclecu.unam.mx (Miguel de Icaza)
Cc: ralf@mailhost.uni-koblenz.de, linux@cthulhu.engr.sgi.com
Subject: Re: Bottom half bug
Date: Tue, 12 Aug 1997 06:07:06 +0200 (MET DST) [thread overview]
Message-ID: <199708120407.GAA03608@informatik.uni-koblenz.de> (raw)
In-Reply-To: <199708112359.SAA03734@athena.nuclecu.unam.mx> from "Miguel de Icaza" at Aug 11, 97 06:59:07 pm
> Well, the major problem with getting gdb up was that init is for
> some reason setting the blocked signal mask to 0x39 (this includes
> sighup, sigtrap and a couple of others).
>
> I will debug this next, right now I have this gross hack on gdb to
> reset the signal mask to zero. Any ideas of why would init be doing this?
Well, I'll look at this when I get off the plane or so ...
I finally tracked the problem with <CTRL>-s locking up the machine down.
It's a missing restore_flags() in the newport driver that makes the
keyboard driver bottom half go bobo. Also we were missing irq_enter/
irq_leave in the Indy interrupt handler. The patch, well, it's in my
suit case. Have fun with your crashing boxes :-)
California, I'm comin',
Ralf
WARNING: multiple messages have this Message-ID (diff)
From: Ralf Baechle <ralf@mailhost.uni-koblenz.de>
To: Miguel de Icaza <miguel@nuclecu.unam.mx>
Cc: ralf@mailhost.uni-koblenz.de, linux@cthulhu.engr.sgi.com
Subject: Re: Bottom half bug
Date: Tue, 12 Aug 1997 06:07:06 +0200 (MET DST) [thread overview]
Message-ID: <199708120407.GAA03608@informatik.uni-koblenz.de> (raw)
Message-ID: <19970812040706.Kz4ImWd3fQxQRm4yhcWQRphcqrVRGzdUxdzpAuGtcMk@z> (raw)
In-Reply-To: <199708112359.SAA03734@athena.nuclecu.unam.mx> from "Miguel de Icaza" at Aug 11, 97 06:59:07 pm
> Well, the major problem with getting gdb up was that init is for
> some reason setting the blocked signal mask to 0x39 (this includes
> sighup, sigtrap and a couple of others).
>
> I will debug this next, right now I have this gross hack on gdb to
> reset the signal mask to zero. Any ideas of why would init be doing this?
Well, I'll look at this when I get off the plane or so ...
I finally tracked the problem with <CTRL>-s locking up the machine down.
It's a missing restore_flags() in the newport driver that makes the
keyboard driver bottom half go bobo. Also we were missing irq_enter/
irq_leave in the Indy interrupt handler. The patch, well, it's in my
suit case. Have fun with your crashing boxes :-)
California, I'm comin',
Ralf
next prev parent reply other threads:[~1997-08-12 4:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-08-10 2:06 Bottom half bug Ralf Baechle
1997-08-11 23:59 ` Miguel de Icaza
1997-08-12 4:07 ` Ralf Baechle [this message]
1997-08-12 4:07 ` Ralf Baechle
1997-08-12 16:26 ` Miguel de Icaza
1997-08-12 16:26 ` Miguel de Icaza
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=199708120407.GAA03608@informatik.uni-koblenz.de \
--to=ralf@mailhost.uni-koblenz.de \
--cc=linux@cthulhu.engr.sgi.com \
--cc=miguel@nuclecu.unam.mx \
/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.