linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Lord <lkml@rtr.ca>
To: Pavel Machek <pavel@ucw.cz>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Phillip Susi <psusi@cfl.rr.com>, Tejun Heo <htejun@gmail.com>,
	noah <noah123@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-ide@vger.kernel.org
Subject: Re: Possibly SATA related freeze killed networking and RAID
Date: Fri, 30 Nov 2007 10:00:55 -0500	[thread overview]
Message-ID: <475025A7.9010107@rtr.ca> (raw)
In-Reply-To: <20071126075517.GA4141@ucw.cz>

Pavel Machek wrote:
> On Fri 2007-11-30 13:13:44, Alan Cox wrote:
>>> Why does a single spurious interrupt cause it to be shut down?  I can 
>> It doesn't.
>>
>>> see if the interrupt is stuck on and keeps interrupting constantly, but 
>>> if it's just the occasional spurious interrupt, why not just ignore it 
>>> and move on?
>> The interrupt is usually level triggered so it continues to create
>> interrupts until you silence it. The thresholds are about 10,000
>> interrupt events and on newer kernels we also reset the count if we don't
>> see any for a while. That works for most stuff except the thinkpad
>> bluetooth problem.
> 
> Which is confirmed hw problem now, btw.
...

What problem is that, exactly?

My Dell has an internal USB BT adapter that briefly appears
and then disappears again on resume (or stays if I have "enabled" it
via the BIOS key).

I wonder if that has anything to do with the (new in) 2.6.23 pauses
that machine has on resume (about every 10th time).

Cheers

  reply	other threads:[~2007-11-30 15:01 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-20 19:09 Possibly SATA related freeze killed networking and RAID noah
2007-11-20 22:05 ` Alan Cox
2007-11-20 22:16   ` noah
2007-11-21  0:45     ` Alan Cox
2007-11-21 19:06       ` noah
2007-12-10 12:33         ` noah
2007-11-26 12:06   ` Pavel Machek
2007-11-28  1:55     ` Tejun Heo
2007-11-29 22:16       ` Phillip Susi
2007-11-30  0:02         ` Tejun Heo
2007-11-30 18:45           ` Phillip Susi
2007-11-30 23:56             ` Tejun Heo
2007-12-03 17:15               ` Phillip Susi
2007-12-04  1:32                 ` Tejun Heo
2007-11-30 13:13         ` Alan Cox
2007-11-26  7:55           ` Pavel Machek
2007-11-30 15:00             ` Mark Lord [this message]
2007-11-30 20:25               ` Pavel Machek
     [not found] <fa.hz1AWBbuhaxCXiVbvWdM1r83meE@ifi.uio.no>
     [not found] ` <fa.fUEfthqYoWrlov4j7OjtVSgx42g@ifi.uio.no>
     [not found]   ` <fa.qGibmi9xfm4JHJhvn0KM4rdFM+M@ifi.uio.no>
     [not found]     ` <fa.YcQmwdppCKfJhxSMgOb0RJPmHg8@ifi.uio.no>
     [not found]       ` <fa.0muxGr+d7CjnQ/J5GaB+TSqouuU@ifi.uio.no>
2007-11-30  0:03         ` Robert Hancock
2007-12-10 21:25 Thiemo Nagel

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=475025A7.9010107@rtr.ca \
    --to=lkml@rtr.ca \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=htejun@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=noah123@gmail.com \
    --cc=pavel@ucw.cz \
    --cc=psusi@cfl.rr.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;
as well as URLs for NNTP newsgroup(s).