From: Shawn Starr <spstarr@sh0n.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: desai@mcs.anl.gov, alan@lxorguk.ukuu.org.uk
Subject: 2.5.66-bk5 spinlock warnings/errors - Specifically ide-io:109 spinlock notice
Date: Wed, 2 Apr 2003 14:29:49 -0500 [thread overview]
Message-ID: <200304021429.49589.spstarr@sh0n.net> (raw)
>List: linux-kernel
>Subject: 2.5.66-bk5 spinlock warnings/errors
From: Narayan Desai <desai () mcs ! anl ! gov>
>Date: 2003-04-02 4:01:02
>hda: dma_timer_expiry: dma status == 0x24
>drivers/ide/ide-io.c:109: spin_lock(drivers/ide/ide.c:c037abe8) already
>locked by drivers/ide/ide-io.c/948 drivers/ide/ide-io.c:990:
>spin_unlock(drivers/ide/ide.c:c037abe8) not locked
>hda: lost interrupt
>hda: dma_intr: bad DMA status (dma_stat=30)
>hda: dma_intr: status=0x50 { DriveReady SeekComplete }
I had this problem last night while making a huge debian package (tar.bz2
stage). It occured once.
Switching to Debian unstable and already two new interesting kernel notices
and one 3c59x NETDEV Watchdog - eth0 transmit timeout bug.
next reply other threads:[~2003-04-02 19:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-02 19:29 Shawn Starr [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-03 5:48 2.5.66-bk5 spinlock warnings/errors - Specifically ide-io:109 spinlock notice Manfred Spraul
2003-04-03 16:36 ` Shawn Starr
2003-04-16 16:28 ` Shawn Starr
2003-04-16 16:59 ` Manfred Spraul
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=200304021429.49589.spstarr@sh0n.net \
--to=spstarr@sh0n.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=desai@mcs.anl.gov \
--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