From: Stef van der Made <svdmade@planet.nl>
To: linux-kernel@vger.kernel.org
Subject: ide-scsi for DI-30 and strange messages in dmesg
Date: Wed, 31 Dec 2003 21:01:42 +0100 [thread overview]
Message-ID: <3FF32B26.1030006@planet.nl> (raw)
On a stock 2.6.0-mm2 kernel I see these 'dumps' into dmesg. I'm using a
onstream Di-30 on a Ak32E with a via chipset. Is this normal as I've
never seen this symptom before ?
Thanks for your feedback,
Stef
Debug: sleeping function called from invalid context at kernel/sched.c:1814
in_atomic():0, irqs_disabled():1
Call Trace:
[<c011bc6b>] __might_sleep+0xab/0xd0
[<c011aa0f>] wait_for_completion+0x1f/0x100
[<c02343e1>] idetape_wait_for_request+0x71/0x90
[<c0235509>] idetape_wait_first_stage+0x69/0x70
[<c0235dd9>] idetape_get_logical_blk+0x139/0x260
[<c0238378>] idetape_chrdev_ioctl+0x268/0x380
[<c0165384>] sys_ioctl+0xf4/0x2b0
[<c032abbf>] syscall_call+0x7/0xb
atkbd.c: Unknown key released (translated set 2, code 0x7a on
isa0060/serio0).
atkbd.c: Unknown key released (translated set 2, code 0x7a on
isa0060/serio0).
request_module: failed /sbin/modprobe -- net-pf-10. error = 65280
request_module: failed /sbin/modprobe -- net-pf-10. error = 65280
request_module: failed /sbin/modprobe -- sound-slot-1. error = 65280
Debug: sleeping function called from invalid context at kernel/sched.c:1814
in_atomic():0, irqs_disabled():1
Call Trace:
[<c011bc6b>] __might_sleep+0xab/0xd0
[<c011aa0f>] wait_for_completion+0x1f/0x100
[<c02343e1>] idetape_wait_for_request+0x71/0x90
[<c0235509>] idetape_wait_first_stage+0x69/0x70
[<c0235dd9>] idetape_get_logical_blk+0x139/0x260
[<c0238378>] idetape_chrdev_ioctl+0x268/0x380
[<c0165384>] sys_ioctl+0xf4/0x2b0
[<c032abbf>] syscall_call+0x7/0xb
next reply other threads:[~2003-12-31 20:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-31 20:01 Stef van der Made [this message]
[not found] <fa.e0q2cec.1f2sao0@ifi.uio.no>
2003-12-31 20:24 ` ide-scsi for DI-30 and strange messages in dmesg Willem Riede
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=3FF32B26.1030006@planet.nl \
--to=svdmade@planet.nl \
--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