From: Jeff Garzik <jeff@garzik.org>
To: tfjellstrom@shaw.ca
Cc: linux-kernel@vger.kernel.org,
linux-scsi <linux-scsi@vger.kernel.org>,
Linux IDE mailing list <linux-ide@vger.kernel.org>
Subject: Re: 2.6.31-rc9 kernel BUG and mvsas
Date: Wed, 09 Sep 2009 14:52:21 -0400 [thread overview]
Message-ID: <4AA7F965.6020408@garzik.org> (raw)
In-Reply-To: <200909091030.13147.tfjellstrom@shaw.ca>
On 09/09/2009 12:30 PM, Thomas Fjellstrom wrote:
> No errors on that disk. Other than the one above, and its more of a warning.
> However, I just rebooted to add some extra drives, thinking everything was
> working a little better now that I've updated to 2.6.31-rc9, I'm treated to
> the following two messages right after boot (and a system lockup to boot):
>
> kernel: [ 971.033138] ------------[ cut here ]------------
> kernel: [ 971.033211] WARNING: at drivers/ata/libata-core.c:4913
> __ata_qc_complete+0x5a/0xe1 [libata]()
> kernel: [ 971.033217] Hardware name: GA-MA790FXT-UD5P
> kernel: [ 971.033221] 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 snd_seq_midi snd_rawmidi
> snd_seq_midi_event snd_seq snd_timer snd_seq_device snd amd64_edac_mod
> edac_core i2c_piix4 soundcore snd_page_alloc i2c_core evdev wmi parport_pc
> button parport processor ext3 jbd mbcache dm_mod sg sr_mod cdrom sd_mod
> crc_t10dif usbhid ata_generic ide_pci_generic hid mvsas firewire_ohci libsas
> firewire_core crc_itu_t scsi_transport_sas r8169 atiixp ide_core floppy ahci
> mii ohci_hcd libata ehci_hcd scsi_mod thermal fan thermal_sys [last unloaded:
> scsi_wait_scan]
> kernel: [ 971.033337] Pid: 0, comm: swapper Not tainted 2.6.31-rc9 #2
> kernel: [ 971.033342] Call Trace:
> kernel: [ 971.033346]<IRQ> [<ffffffffa00562ca>] ?
> __ata_qc_complete+0x5a/0xe1 [libata]
> kernel: [ 971.033434] [<ffffffffa00562ca>] ? __ata_qc_complete+0x5a/0xe1
> [libata]
> kernel: [ 971.033446] [<ffffffff8104aca0>] ? warn_slowpath_common+0x77/0xa3
> kernel: [ 971.033455] [<ffffffff81038d06>] ? enqueue_task+0x5c/0x65
> kernel: [ 971.033496] [<ffffffffa00562ca>] ? __ata_qc_complete+0x5a/0xe1
> [libata]
> kernel: [ 971.033519] [<ffffffffa00f7b59>] ? sas_ata_task_done+0x178/0x210
> [libsas]
> kernel: [ 971.033528] [<ffffffff8115ead1>] ? blk_run_queue+0x21/0x35
> kernel: [ 971.033548] [<ffffffffa010e2ce>] ? mvs_slot_complete+0x3df/0x41b
> [mvsas]
> kernel: [ 971.033565] [<ffffffffa010e39c>] ? mvs_int_rx+0x92/0x101 [mvsas]
> kernel: [ 971.033583] [<ffffffffa01112ba>] ? mvs_int_full+0x25/0x88 [mvsas]
> kernel: [ 971.033600] [<ffffffffa011134e>] ? mvs_64xx_isr+0x31/0x40 [mvsas]
> kernel: [ 971.033617] [<ffffffffa010d0e5>] ? mvs_interrupt+0x61/0x78 [mvsas]
> kernel: [ 971.033625] [<ffffffff8108aaac>] ? handle_IRQ_event+0x58/0x135
> kernel: [ 971.033633] [<ffffffff8108c1a1>] ? handle_fasteoi_irq+0x7d/0xb5
> kernel: [ 971.033642] [<ffffffff8101388d>] ? handle_irq+0x17/0x1d
That warning is triggered when an ata_queued_cmd is passed to completion
without the ATA_QCFLAG_ACTIVE flag being set (which indicates the qc was
started with some activity).
That possibly indicates the low-level driver (or libsas) was passing an
already-completed cmd to libata.
> The added hard drives are connected to a Supermicro AOC-SASLP-MV8, which is
> based on a marvel MV64460/64461/64462 chipset, which uses the sata_mv driver.
Surely you mean 'mvsas' driver?
Jeff
next prev parent reply other threads:[~2009-09-09 18:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 10:14 2.6.31-rc8 libata WARNING? Thomas Fjellstrom
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 ` Jeff Garzik [this message]
2009-09-09 19:10 ` 2.6.31-rc9 kernel BUG and mvsas 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-09-13 4:59 ` 2.6.31-rc9 kernel BUG and mvsas Thomas Fjellstrom
2009-11-04 0:50 ` 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=4AA7F965.6020408@garzik.org \
--to=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=tfjellstrom@shaw.ca \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.