From: thomas schorpp <t.schorpp@gmx.de>
To: SCSI development list <linux-scsi@vger.kernel.org>
Subject: Re: aic7xxx: aic7892(B): BUG: soft lockup detected on CPU#0!
Date: Fri, 23 Mar 2007 00:00:42 +0100 [thread overview]
Message-ID: <46030A9A.2060604@gmx.de> (raw)
In-Reply-To: <4602EED5.5070503@gmx.de>
[ 48.848796] Loading iSCSI transport class v2.0-724.
[ 48.854066] iscsi: registered transport (tcp)
[ 48.858479] ahc_linux_pci_init
[ 48.861676] ahc_linux_pci_dev_probe
[ 48.865208] ACPI: PCI Interrupt 0000:00:06.0[A] -> GSI 17 (level, low) -> IRQ
17
[ 48.872628] ahc_pci_config
[ 48.875335] set_power_state
[ 48.878126] map_registers
[ 48.880744] ahc_pci_map_registers enter
[ 48.884571] .read_config
[ 48.887106] .reserve_mem
[ 48.889647] .write_config_iferr0
[ 48.892871] .test_registers_iferr0
[ 48.896265] ahc_pci_test_register_access enter
[ 48.900699] .read_config
[ 48.903235] .write_config_noserr
[ 48.906462] .hcnctrl
[ 48.908648] .hcntrl pause cmd
[ 48.911616] .I will pause 4E4 if missing errh before :/
ok, as expected, the wait for pause ended loop, (someone with the specs pls say max HZ
for a) wait_interruptible(_timeout)() here.
yes, I know that case must not happen and it should bug cause
the pci config is messed up already, but generally such loops are
surely inacceptable in such a kernel thread.
will dump the config data to here, maybe its readable to the aic devs.
then disable test and will let it bug somewhere further where the
cause can possibly be easier seen.
next prev parent reply other threads:[~2007-03-22 23:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 15:14 aic7xxx: aic7892(B): BUG: soft lockup detected on CPU#0! thomas schorpp
2007-03-22 16:57 ` thomas schorpp
2007-03-22 21:02 ` thomas schorpp
2007-03-22 23:00 ` thomas schorpp [this message]
2007-03-23 1:26 ` thomas schorpp
2007-03-23 4:45 ` James Bottomley
2007-03-23 7:32 ` thomas schorpp
2007-03-23 16:28 ` thomas schorpp
2007-03-23 17:23 ` James Bottomley
2007-03-23 18:23 ` thomas schorpp
2007-03-23 18:59 ` thomas schorpp
2007-03-24 0:51 ` thomas schorpp
2007-03-24 1:17 ` James Bottomley
2007-03-24 3:44 ` thomas schorpp
2007-03-24 4:05 ` thomas schorpp
2007-03-27 6:52 ` thomas schorpp
2007-03-29 20:13 ` thomas schorpp
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=46030A9A.2060604@gmx.de \
--to=t.schorpp@gmx.de \
--cc=linux-scsi@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