From: Simon Sudler <Simon.Sudler@gmx.net>
To: Marcel Naziri <silent@zwobbl.de>
Cc: linux-kernel@vger.kernel.org, Jeff Garzik <jgarzik@pobox.com>
Subject: Re: sata_promise KERNEL_BUG on 2.6.12
Date: Mon, 20 Jun 2005 15:25:20 +0200 [thread overview]
Message-ID: <42B6C3C0.9010209@gmx.net> (raw)
In-Reply-To: <200506201432.30628.silent@zwobbl.de>
I can confirm the the problem on my Promise SATAII-150 TX4
with the 2.6.12. However after a immediate downgrade to
2.6.11 the problem persist.
updating the controller bios to 1.00.0.34 didn't helped either.
The kernel freezes the interrupt from the satalib after a short
time. strangly it occurs only after even numbers (like
200000 or 300000). Bevor the freez, all devices are working fine
except for some
[kernel] irq 18: nobody cared!
messages.
Simon
prev parent reply other threads:[~2005-06-20 13:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-20 2:02 sata_promise KERNEL_BUG on 2.6.12 Marcel Naziri
2005-06-20 2:25 ` Jeff Garzik
2005-06-20 2:38 ` Marcel Naziri
2005-06-20 2:41 ` Jeff Garzik
2005-06-20 12:32 ` Marcel Naziri
2005-06-20 13:25 ` Simon Sudler [this message]
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=42B6C3C0.9010209@gmx.net \
--to=simon.sudler@gmx.net \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=silent@zwobbl.de \
/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