From: Nick Piggin <piggin@cyberone.com.au>
To: Valdis.Kletnieks@vt.edu
Cc: thunder7@xs4all.nl, linux-kernel@vger.kernel.org
Subject: Re: cdrecord dev=/dev/hdd in 2.9.0-test9-mm2: lots (LOTS) of error messages
Date: Sat, 08 Nov 2003 13:23:38 +1100 [thread overview]
Message-ID: <3FAC53AA.7070807@cyberone.com.au> (raw)
In-Reply-To: <200311070708.hA778Pe8008356@turing-police.cc.vt.edu>
Valdis.Kletnieks@vt.edu wrote:
>On Thu, 06 Nov 2003 14:43:14 +0100, Jurriaan <thunder7@xs4all.nl> said:
>
>
>>I tried to burn a CD using this command-line in 2.6.0-test9-mm2:
>>
>>sudo cdrecord -v dev="/dev/hdd" -dao -useinfo *.wav
>>
>>Result:
>>
>>[this about 5 times per second]
>>Nov 6 14:37:17 middle kernel: arq->state 4
>>Nov 6 14:37:17 middle kernel: Badness in as_put_request at drivers/block/as-
>>
>>
>iosched.c:1783
>
>I'm seeing this as well burning an ISO in TAO mode on /dev/hdb, but slightly different traceback:
>
>Nov 6 16:03:06 turing-police kernel: arq->state 4
>Nov 6 16:03:07 turing-police kernel: Badness in as_put_request at drivers/block/as-iosched.c:1783
>Nov 6 16:03:07 turing-police kernel: Call Trace:
>Nov 6 16:03:07 turing-police kernel: [as_put_request+113/140] as_put_request+0x71/0x8c
>Nov 6 16:03:07 turing-police kernel: [elv_put_request+19/23] elv_put_request+0x13/0x17
>Nov 6 16:03:07 turing-police kernel: [__blk_put_request+91/133] __blk_put_request+0x5b/0x85
>Nov 6 16:03:07 turing-police kernel: [blk_put_request+35/67] blk_put_request+0x23/0x43
>Nov 6 16:03:07 turing-police kernel: [sg_io+955/1072] sg_io+0x3bb/0x430
>Nov 6 16:03:07 turing-police kernel: [scsi_cmd_ioctl+520/1204] scsi_cmd_ioctl+0x208/0x4b4
>Nov 6 16:03:07 turing-police kernel: [avc_has_perm+57/67] avc_has_perm+0x39/0x43
>Nov 6 16:03:07 turing-police kernel: [__copy_from_user_ll+76/90] __copy_from_user_ll+0x4c/0x5a
>Nov 6 16:03:07 turing-police kernel: [cdrom_ioctl+29/3404] cdrom_ioctl+0x1d/0xd4c
>Nov 6 16:03:07 turing-police kernel: [write_chan+432/451] write_chan+0x1b0/0x1c3
>Nov 6 16:03:07 turing-police kernel: [default_wake_function+0/24] default_wake_function+0x0/0x18
>Nov 6 16:03:07 turing-police kernel: [selinux_file_permission+289/300] selinux_file_permission+0x121/0x12c
>Nov 6 16:03:07 turing-police kernel: [idecd_ioctl+55/66] idecd_ioctl+0x37/0x42
>Nov 6 16:03:07 turing-police kernel: [blkdev_ioctl+797/816] blkdev_ioctl+0x31d/0x330
>Nov 6 16:03:07 turing-police kernel: [sys_ioctl+512/583] sys_ioctl+0x200/0x247
>Nov 6 16:03:07 turing-police kernel: [syscall_call+7/11] syscall_call+0x7/0xb
>Nov 6 16:03:07 turing-police kernel: [pfkey_xfrm_state2msg+686/2757] pfkey_xfrm_state2msg+0x2ae/0xac5
>
>(pfkey_xfrm_state2msg()??? But I'm not doing ipsec - is the traceback on crack? ;)
>
>
Yes.
I have fixed this. It will be in the next mm.
next prev parent reply other threads:[~2003-11-08 2:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-06 13:43 Jurriaan
2003-11-07 7:08 ` Valdis.Kletnieks
2003-11-08 2:23 ` Nick Piggin [this message]
2003-11-07 9:37 ` Gene Heskett
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=3FAC53AA.7070807@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=thunder7@xs4all.nl \
/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
all inboxes | Powered by JetHome®