From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933465Ab0EJXlb (ORCPT ); Mon, 10 May 2010 19:41:31 -0400 Received: from mail-gw0-f46.google.com ([74.125.83.46]:62010 "EHLO mail-gw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933425Ab0EJXlD (ORCPT ); Mon, 10 May 2010 19:41:03 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=NxueDjTXQXUvwi0wgi6LrrgqleXIv+KJJOL1g2YyLKds5TGSteyeIHlwSr0IcHwjoR 1wUddJa7UaO2Hdfyi74ORx67ijgtpzAfiC13a0Ps7IGAbWJyjxTBwjqlrwZGXdpg+wge dPSfCUOrbIMNaEuWUxQ0jfDwOUqLC/FPclTzc= Message-ID: <4BE8998A.4040905@gmail.com> Date: Mon, 10 May 2010 17:40:58 -0600 From: Robert Hancock User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100430 Fedora/3.0.4-2.fc12 Thunderbird/3.0.4 MIME-Version: 1.0 To: Andrew Morton CC: Thomas Fjellstrom , linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org, Jens Axboe Subject: Re: burning small isos repeatedly failing with hangcheck error References: <201004261855.29335.tfjellstrom@strangesoft.net> <20100510140121.0e2e2d3e.akpm@linux-foundation.org> In-Reply-To: <20100510140121.0e2e2d3e.akpm@linux-foundation.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 05/10/2010 03:01 PM, Andrew Morton wrote: > (lotsa cc's added) > > On Mon, 26 Apr 2010 18:55:28 -0600 > Thomas Fjellstrom wrote: > >> I'm having problems burning a small iso image to a DVDR, >> every single attempt leads to the following type of errors: >> >> [ 192.190114] cdrom: This disc doesn't have any tracks I recognize! >> [ 192.220213] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE >> [ 192.220217] sr 1:0:0:0: [sr0] Sense Key : Illegal Request [current] >> [ 192.220220] Info fld=0x0 >> [ 192.220221] sr 1:0:0:0: [sr0] Add. Sense: Logical block address out of range >> [ 192.220231] sr 1:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 00 00 00 01 00 >> [ 192.220242] end_request: I/O error, dev sr0, sector 0 >> [ 192.220246] Buffer I/O error on device sr0, logical block 0 >> [ 192.222931] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE >> [ 192.222934] sr 1:0:0:0: [sr0] Sense Key : Illegal Request [current] >> [ 192.222936] Info fld=0x0 >> [ 192.222938] sr 1:0:0:0: [sr0] Add. Sense: Logical block address out of range >> [ 192.222940] sr 1:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 00 00 00 01 00 >> [ 192.222946] end_request: I/O error, dev sr0, sector 0 >> [ 192.222948] Buffer I/O error on device sr0, logical block 0 >> [ 600.489102] INFO: task wodim:3587 blocked for more than 120 seconds. >> [ 600.489106] "echo 0> /proc/sys/kernel/hung_task_timeout_secs" disables this message. >> [ 600.489107] wodim D ffff880005515680 0 3587 2994 0x00000000 >> [ 600.489111] ffff88011ad80700 0000000000000082 0000000000000000 ffff88013b7700d0 >> [ 600.489115] ffff88013b771e50 000000000000f8e0 ffff880078d6dfd8 0000000000015680 >> [ 600.489118] 0000000000015680 ffff8800a891e200 ffff8800a891e4f0 000000013b771e50 >> [ 600.489121] Call Trace: >> [ 600.489147] [] ? atapi_xlat+0x0/0x125 [libata] >> [ 600.489153] [] ? scsi_done+0x0/0xc [scsi_mod] >> [ 600.489160] [] ? __ata_scsi_queuecmd+0x185/0x1dc [libata] >> [ 600.489170] [] ? schedule_timeout+0x2e/0xdd >> [ 600.489174] [] ? blk_peek_request+0x18b/0x19f >> [ 600.489179] [] ? scsi_dispatch_cmd+0x1d2/0x23f [scsi_mod] >> [ 600.489185] [] ? scsi_request_fn+0x429/0x506 [scsi_mod] >> [ 600.489187] [] ? wait_for_common+0xde/0x15b >> [ 600.489191] [] ? default_wake_function+0x0/0x9 >> [ 600.489194] [] ? blk_execute_rq+0x9c/0xcc >> [ 600.489197] [] ? __freed_request+0x26/0x83 >> [ 600.489199] [] ? freed_request+0x23/0x43 >> [ 600.489202] [] ? capable+0x22/0x41 >> [ 600.489204] [] ? sg_io+0x26e/0x396 >> [ 600.489207] [] ? scsi_cmd_ioctl+0x217/0x3fe >> [ 600.489210] [] ? cpumask_next_and+0x2a/0x3a >> [ 600.489213] [] ? update_curr+0xa6/0x147 >> [ 600.489218] [] ? cdrom_ioctl+0x42/0xef7 [cdrom] >> [ 600.489222] [] ? sched_clock+0x5/0x8 >> [ 600.489224] [] ? sched_clock_local+0x13/0x74 >> [ 600.489227] [] ? try_to_wake_up+0x248/0x255 >> [ 600.489230] [] ? pollwake+0x53/0x5b >> [ 600.489233] [] ? current_fs_time+0x1e/0x24 >> [ 600.489235] [] ? default_wake_function+0x0/0x9 >> [ 600.489239] [] ? sr_block_ioctl+0x49/0x85 [sr_mod] >> [ 600.489242] [] ? __blkdev_driver_ioctl+0x7c/0xa4 >> [ 600.489245] [] ? blkdev_ioctl+0x880/0x8d3 >> [ 600.489247] [] ? schedule+0x7f6/0x875 >> [ 600.489250] [] ? do_sync_write+0xab/0xed >> [ 600.489254] [] ? block_ioctl+0x38/0x3c >> [ 600.489257] [] ? vfs_ioctl+0x21/0x92 >> [ 600.489259] [] ? do_vfs_ioctl+0x495/0x4d3 >> [ 600.489262] [] ? vfs_write+0xcd/0x102 >> [ 600.489264] [] ? sys_ioctl+0x51/0x70 >> [ 600.489267] [] ? system_call_fastpath+0x16/0x1b >> [ 640.816056] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen >> [ 640.816061] sr 1:0:0:0: [sr0] CDB: Synchronize Cache(10): 35 00 00 00 00 00 00 00 00 00 >> [ 640.816070] ata2.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0 >> [ 640.816071] res 40/00:03:00:00:f8/00:00:00:00:00/a0 Emask 0x4 (timeout) >> [ 640.816073] ata2.00: status: { DRDY } >> [ 640.816078] ata2: hard resetting link >> [ 641.137050] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) >> [ 641.141821] ata2.00: ACPI cmd ef/10:06:00:00:00:a0 (SET FEATURES) succeeded >> [ 641.141824] ata2.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out >> [ 641.151672] ata2.00: ACPI cmd ef/10:06:00:00:00:a0 (SET FEATURES) succeeded >> [ 641.151675] ata2.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out >> [ 641.155383] ata2.00: configured for UDMA/133 >> [ 641.160639] ata2: EH complete >> >> What can I do to fix this problem? >> >> The machine is a Lenovo SL500 laptop, w 2.53ghz core2duo, 4G ram, >> kernel 2.6.33-2-amd64 from debian sid (also happens with 2.6.32-5 from sid) >> > > You appear to have hit several problems here. The initial IO error is > one. The 440-second sulk is another. The initial I/O error might just be from something trying to read the disc before it's burned. > > Does wodim _ever_ terminate, or is a reboot required after this has happened? > > Are you able to determine whether the hardware is OK? Does it burn OK > with other versions of Linux, or other OS'es? Indeed.. For a synchronize cache command to take that long, I would suspect that the drive is having trouble with the media somehow.. > > Thanks. > -- > To unsubscribe from this list: send the line "unsubscribe linux-ide" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html >