linux-kernel - Re: WARNING: at drivers/ata/libata-core.c:5027 ata_qc

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <4AC3316F.4080200@pobox.com>
Date:	Wed, 30 Sep 2009 06:22:39 -0400
From:	Jeff Garzik <jgarzik@...ox.com>
To:	Zdenek Kabelac <zdenek.kabelac@...il.com>
CC:	linux-ide@...r.kernel.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: WARNING: at drivers/ata/libata-core.c:5027 ata_qc_complete+0x200/0x210()

On 09/30/2009 05:33 AM, Zdenek Kabelac wrote:
> 2009/9/17 Zdenek Kabelac<zdenek.kabelac@...il.com>:
>> Hi
>>
>> Somewhere during recent merge commits this message started to appear
>> in my qemu kvm guest
>> (already present with some 2.6.31-040xxx commit)
>>
>> Is this fault of kvm emulation ?
>>
>>
>> WARNING: at drivers/ata/libata-core.c:5027 ata_qc_complete+0x200/0x210()
>> Hardware name:
>> Modules linked in:
>> Pid: 167, comm: ata/0 Not tainted 2.6.31-05317-ged0ecd1 #42
>> Call Trace:
>>   [<ffffffff81051ddb>] warn_slowpath_common+0x7b/0xc0
>>   [<ffffffff81051e34>] warn_slowpath_null+0x14/0x20
>>   [<ffffffff81323690>] ata_qc_complete+0x200/0x210
>>   [<ffffffff81330243>] ata_do_link_abort+0xf3/0x110
>>   [<ffffffff81330270>] ata_port_abort+0x10/0x20
>>   [<ffffffff813302af>] ata_port_freeze+0x2f/0x50
>>   [<ffffffff81334101>] ata_hsm_qc_complete+0x131/0x140
>>   [<ffffffff81335347>] ata_sff_hsm_move+0x197/0x760
>>   [<ffffffff8125891a>] ? delay_tsc+0x8a/0xe0
>>   [<ffffffff81335ca0>] ? ata_pio_task+0x0/0x120
>>   [<ffffffff81335ca0>] ? ata_pio_task+0x0/0x120
>>   [<ffffffff81335cd7>] ata_pio_task+0x37/0x120
>>   [<ffffffff8106f88a>] worker_thread+0x21a/0x400
>>   [<ffffffff8106f839>] ? worker_thread+0x1c9/0x400
>>   [<ffffffff81075a20>] ? autoremove_wake_function+0x0/0x40
>>   [<ffffffff8106f670>] ? worker_thread+0x0/0x400
>>   [<ffffffff810755f6>] kthread+0x96/0xa0
>>   [<ffffffff8100d29a>] child_rip+0xa/0x20
>>   [<ffffffff81041574>] ? finish_task_switch+0x74/0xf0
>>   [<ffffffff8140d14b>] ? _spin_unlock_irq+0x3b/0x60
>>   [<ffffffff8100cc00>] ? restore_args+0x0/0x30
>>   [<ffffffff81075560>] ? kthread+0x0/0xa0
>>   [<ffffffff8100d290>] ? child_rip+0x0/0x20
>>
>>
>
> Just confirmation that WARNING trace is still present with 2.6.32-rc1.

hrm, I thought we'd fixed that with 4dc738ed2adf28f62f46dd53ef700a51603777f7

	Jeff



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/