From: Mark v Wolher <trilight@ns666.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Badness in as_insert_request at drivers/block/as-iosched.c:1519
Date: Sat, 07 Jan 2006 14:49:57 +0100 [thread overview]
Message-ID: <43BFC705.50509@ns666.com> (raw)
In-Reply-To: <43BFC3FF.5080908@ns666.com>
Mark v Wolher wrote:
> Hiya all,
>
> I was just playing a cd as usual and i noticed suddenly the errors
> below, they repeated like 8 times.
>
> kernel: 2.6.14.5
>
>
> Jan 7 14:32:40 localhost kernel: Badness in as_insert_request at
> drivers/block/as-iosched.c:1519
> Jan 7 14:32:40 localhost kernel: [as_insert_request+100/384]
> Jan 7 14:32:40 localhost kernel: [__elv_add_request+120/192]
> Jan 7 14:32:40 localhost kernel: [elv_add_request+76/112]
> Jan 7 14:32:40 localhost kernel: [blk_execute_rq_nowait+72/96]
> Jan 7 14:32:40 localhost kernel: [blk_execute_rq+148/192]
> Jan 7 14:32:40 localhost kernel: [blk_end_sync_rq+0/64]
> Jan 7 14:32:40 localhost kernel: [blk_rq_bio_prep+115/160]
> Jan 7 14:32:40 localhost kernel: [cdrom_read_cdda_bpc+391/496]
> Jan 7 14:32:40 localhost kernel: [cdrom_read_cdda+68/176]
> Jan 7 14:32:40 localhost kernel: [mmc_ioctl+1373/2752]
> Jan 7 14:32:40 localhost kernel: [cdrom_read_cdda+68/176]
> Jan 7 14:32:40 localhost kernel: [mmc_ioctl+1373/2752]
> Jan 7 14:32:40 localhost kernel: [scsi_cmd_ioctl+125/1232]
> Jan 7 14:32:40 localhost last message repeated 3 times
> Jan 7 14:32:40 localhost kernel: [cdrom_ioctl+3228/3392]
> Jan 7 14:32:40 localhost kernel: [activate_task+141/160]
> Jan 7 14:32:40 localhost kernel: [try_to_wake_up+730/832]
> Jan 7 14:32:40 localhost kernel: [idecd_ioctl+133/144]
> Jan 7 14:32:40 localhost kernel: [blkdev_driver_ioctl+82/144]
> Jan 7 14:32:40 localhost kernel: [blkdev_ioctl+168/432]
> Jan 7 14:32:40 localhost kernel: [block_ioctl+43/48]
> Jan 7 14:32:40 localhost kernel: [do_ioctl+142/160]
> Jan 7 14:32:40 localhost kernel: [vfs_ioctl+101/496]
> Jan 7 14:32:40 localhost kernel: [sys_ioctl+103/144]
> Jan 7 14:32:40 localhost kernel: [syscall_call+7/11]
> Jan 7 14:32:40 localhost kernel: arq->state: 4
>
> Appreciate it if any one can take a look.
>
> Thanks,
>
> Mark
> -
I have 2 drives, when i put the same cd or other cd's in the other drive
then nothing happens. It happens only with the other drive.
Which is this one:
Model=DVDRW DRW-1S45, FwRev=GBG2, SerialNo=
Config={ Fixed Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic }
RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
BuffType=unknown, BuffSize=0kB, MaxMultSect=0
(maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0
IORDY=yes, tPIO={min:227,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 *udma2
AdvancedPM=no
Drive conforms to: device does not report version:
* signifies the current active mode
next prev parent reply other threads:[~2006-01-07 13:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-07 13:37 Badness in as_insert_request at drivers/block/as-iosched.c:1519 Mark v Wolher
2006-01-07 13:49 ` Mark v Wolher [this message]
2006-01-07 14:33 ` Mark v Wolher
2006-01-07 14:34 ` Jens Axboe
2006-01-07 14:50 ` Mark v Wolher
2006-01-07 14:55 ` Jens Axboe
2006-01-07 15:03 ` Mark v Wolher
-- strict thread matches above, loose matches on Subject: below --
2005-10-31 20:40 Bongani Hlope
2005-11-01 6:59 ` Jens Axboe
2005-11-01 20:47 ` Bongani Hlope
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=43BFC705.50509@ns666.com \
--to=trilight@ns666.com \
--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