From: Saulo <slima@tse.gov.br>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: IDE cs5530 hda: lost interrupt
Date: Wed, 08 Nov 2006 20:17:00 -0300 [thread overview]
Message-ID: <4552656C.9090807@tse.gov.br> (raw)
In-Reply-To: <1163023173.23956.111.camel@localhost.localdomain>
Other strange think is that after lots and lots of "lost interrupts"
this work. I can mount and list files but with lots of "lost interrupts"
and after a long time.
this is the strange.
before ls in primary master
14: 2 XT-PIC ide0 >>> just 2 interrupts
15: 3893 XT-PIC ide1
after ls and many "lost interrupts"
14: 2 XT-PIC ide0 >>> just 2 interrupts
15: 3901 XT-PIC ide1 >>> more interrupts
[]´s Saulo Alessandre
next prev parent reply other threads:[~2006-11-08 22:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-08 22:05 IDE cs5530 hda: lost interrupt Saulo
2006-11-08 21:44 ` Alan Cox
[not found] ` <45525EB0.1070907@tse.gov.br>
2006-11-08 21:59 ` Alan Cox
2006-11-08 23:17 ` Saulo [this message]
2006-11-09 13:30 ` Saulo
2006-11-09 13:28 ` Alan Cox
2006-11-08 22:56 ` Saulo
2006-11-08 23:53 ` Mark Lord
2006-11-09 13:59 ` Saulo
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=4552656C.9090807@tse.gov.br \
--to=slima@tse.gov.br \
--cc=alan@lxorguk.ukuu.org.uk \
--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