From: Thomas Fjellstrom <tfjellstrom@shaw.ca>
To: linux-kernel@vger.kernel.org
Subject: 2.6.31-rc8 libata WARNING?
Date: Wed, 9 Sep 2009 04:14:41 -0600 [thread overview]
Message-ID: <200909090414.41274.tfjellstrom@shaw.ca> (raw)
Ok, After doing some more tests, I can be fairly certain that my disk is not
at fault, testing just ONE of my 2 WD Green drives, not using any md raid, or
filesystem on top I get the following:
[ 329.394283] ------------[ cut here ]------------
[ 329.394361] WARNING: at drivers/ata/libata-core.c:5129
ata_qc_issue+0x10a/0x347 [libata]()
[ 329.394367] Hardware name: GA-MA790FXT-UD5P
[ 329.394371] Modules linked in: powernow_k8 cpufreq_conservative
cpufreq_stats cpufreq_userspace cpufreq_powersave kvm_amd kvm nfsd exportfs
nfs lockd fscache nfs_acl auth_rpcgss sunrpc bridge stp it87 hwmon_vid adt7473
firewire_sbp2 loop md_mod snd_hda_codec_realtek snd_hda_intel snd_hda_codec
snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm amd64_edac_mod snd_seq_midi
snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device edac_core snd
i2c_piix4 soundcore i2c_core snd_page_alloc evdev parport_pc parport button
wmi processor ext3 jbd mbcache dm_mod sg usbhid sr_mod hid cdrom pata_jmicron
firewire_ohci firewire_core ata_generic sd_mod crc_t10dif ohci_hcd crc_itu_t
atiixp ide_pci_generic ide_core ahci mvsas ehci_hcd libsas libata
scsi_transport_sas scsi_mod r8169 mii floppy thermal fan thermal_sys [last
unloaded: scsi_wait_scan]
[ 329.394488] Pid: 3103, comm: hddtemp Not tainted 2.6.31-rc8 #1
[ 329.394493] Call Trace:
[ 329.394540] [<ffffffffa007cf90>] ? ata_qc_issue+0x10a/0x347 [libata]
[ 329.394583] [<ffffffffa007cf90>] ? ata_qc_issue+0x10a/0x347 [libata]
[ 329.394596] [<ffffffff8104aca0>] ? warn_slowpath_common+0x77/0xa3
[ 329.394639] [<ffffffffa00810ce>] ? ata_scsi_pass_thru+0x0/0x240 [libata]
[ 329.394680] [<ffffffffa007cf90>] ? ata_qc_issue+0x10a/0x347 [libata]
[ 329.394726] [<ffffffffa00401d6>] ? scsi_get_command+0x75/0x97 [scsi_mod]
[ 329.394768] [<ffffffffa00810ce>] ? ata_scsi_pass_thru+0x0/0x240 [libata]
[ 329.394807] [<ffffffffa003f7aa>] ? scsi_done+0x0/0xc [scsi_mod]
[ 329.394850] [<ffffffffa00824d5>] ? __ata_scsi_queuecmd+0x185/0x1dc
[libata]
[ 329.394889] [<ffffffffa003f7aa>] ? scsi_done+0x0/0xc [scsi_mod]
[ 329.394911] [<ffffffffa00abc8e>] ? sas_queuecommand+0x83/0x25d [libsas]
[ 329.394949] [<ffffffffa003fa7c>] ? scsi_dispatch_cmd+0x1c0/0x23c
[scsi_mod]
[ 329.394988] [<ffffffffa0044ff0>] ? scsi_request_fn+0x3a5/0x506 [scsi_mod]
[ 329.394999] [<ffffffff810546e0>] ? del_timer+0x59/0x62
[ 329.395009] [<ffffffff81163b08>] ? blk_execute_rq_nowait+0x65/0x89
[ 329.395024] [<ffffffffa016764f>] ? sg_common_write+0x489/0x4ab [sg]
[ 329.395034] [<ffffffff8115deee>] ? __freed_request+0x26/0x83
[ 329.395048] [<ffffffffa01681da>] ? sg_new_write+0x23e/0x269 [sg]
[ 329.395062] [<ffffffffa0168473>] ? sg_ioctl+0x26e/0xb63 [sg]
[ 329.395072] [<ffffffff81100ef8>] ? inotify_d_instantiate+0x12/0x39
[ 329.395081] [<ffffffff8105eee6>] ? autoremove_wake_function+0x0/0x2e
[ 329.395090] [<ffffffff810d8097>] ? fd_install+0x2e/0x5a
[ 329.395097] [<ffffffff810e5207>] ? vfs_ioctl+0x56/0x6c
[ 329.395104] [<ffffffff810e56ca>] ? do_vfs_ioctl+0x437/0x475
[ 329.395111] [<ffffffff810e5759>] ? sys_ioctl+0x51/0x70
[ 329.395121] [<ffffffff81010a02>] ? system_call_fastpath+0x16/0x1b
[ 329.395127] ---[ end trace 2e6f5d9886b0398e ]---
And that happens after only a couple minutes of: dd if=/dev/sdc of=/dev/null
And this is with the WD that wasn't previously showing up in any dmesg logs.
I'm assuming if I let the dd test run, I will continue to see more errors
until the entire libata subsystem causes the sata driver to kneel over and
die.
I'm going to let it run for a while to see what happens.
--
Thomas Fjellstrom
tfjellstrom@shaw.ca
next reply other threads:[~2009-09-09 10:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 10:14 Thomas Fjellstrom [this message]
2009-09-09 16:30 ` 2.6.31-rc9 kernel BUG (was: Re: 2.6.31-rc8 libata WARNING?) Thomas Fjellstrom
2009-09-09 18:52 ` 2.6.31-rc9 kernel BUG and mvsas Jeff Garzik
2009-09-09 19:10 ` Thomas Fjellstrom
2009-09-09 20:07 ` Thomas Fjellstrom
2009-09-10 23:55 ` Thomas Fjellstrom
2009-09-11 16:04 ` Thomas Fjellstrom
2009-09-13 0:43 ` Jeff Garzik
2009-09-13 4:56 ` Thomas Fjellstrom
2009-09-15 16:20 ` Thomas Fjellstrom
2009-09-17 15:39 ` 2.6.31-git4 mvsas DRIVER_TIMEOUT Thomas Fjellstrom
2009-11-04 0:50 ` 2.6.31-rc9 kernel BUG and mvsas Andre Tomt
2009-11-04 1:05 ` Andre Tomt
2009-12-03 21:17 ` Mikael Abrahamsson
2009-12-03 21:36 ` Kristleifur Daðason
2009-12-04 19:00 ` Mikael Abrahamsson
2009-12-04 19:08 ` Kristleifur Daðason
2009-12-05 10:54 ` Mikael Abrahamsson
2009-12-10 19:25 ` Mikael Abrahamsson
2009-12-10 21:04 ` Thomas Fjellstrom
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=200909090414.41274.tfjellstrom@shaw.ca \
--to=tfjellstrom@shaw.ca \
--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