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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo _at_ vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/