From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Alexander V. Inyukhin" <shurick@sectorb.msk.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] 2.6.15-rc1, soft lockup detected while probing IDE devices on AMD7441
Date: Sun, 20 Nov 2005 23:07:13 +0000 [thread overview]
Message-ID: <1132528033.459.12.camel@localhost.localdomain> (raw)
In-Reply-To: <20051120204656.GA17242@shurick.s2s.msu.ru>
On Sul, 2005-11-20 at 23:46 +0300, Alexander V. Inyukhin wrote:
> I've got soft lockups during IDE probes with 2.6.15-rc1 kernel.
> The box is dual Athlon MP with ASUS A7M266-D board.
> Full dmesg, config and lspci -vvv output are in the attachment.
> Disabling second channel with "hdc=noprobe hdd=noprobe" did not help.
Quite normal. The old IDE probe code takes a long time and it makes the
soft lockup code believe a lockup occurred - rememeber its a debugging
tool not a 100% reliable detector of failures.
Alan
next prev parent reply other threads:[~2005-11-20 22:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-20 20:46 [BUG] 2.6.15-rc1, soft lockup detected while probing IDE devices on AMD7441 Alexander V. Inyukhin
2005-11-20 23:07 ` Alan Cox [this message]
2005-11-21 1:29 ` Andrew Morton
2005-11-21 20:38 ` Alan Cox
2005-11-23 19:17 ` Jesper Juhl
2005-11-30 10:59 ` Alexander V. Inyukhin
2005-11-30 12:00 ` Jesper Juhl
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=1132528033.459.12.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=shurick@sectorb.msk.ru \
/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