[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <74a4e37024ed59315a9b5e8ad792cae2@lycos.com>
Date: Mon, 21 Dec 2015 04:23:01 +0500
From: "Artem S. Tashkinov" <t.artem@...os.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Kent Overstreet <kent.overstreet@...il.com>,
Christoph Hellwig <hch@....de>,
Ming Lin <ming.l@....samsung.com>, Jens Axboe <axboe@...com>,
"Artem S. Tashkinov" <t.artem@...lcity.com>,
Steven Whitehouse <swhiteho@...hat.com>,
Tejun Heo <tj@...nel.org>, IDE-ML <linux-ide@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linus971@...il.com
Subject: Re: IO errors after "block: remove bio_get_nr_vecs()"
On 2015-12-20 22:51, Linus Torvalds wrote:
> Kent, Jens, Christoph et al,
> please see this bugzilla:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=109661
>
> where Artem Tashkinov bisected his problems with 4.3 down to commit
> b54ffb73cadc ("block: remove bio_get_nr_vecs()") that you've all
> signed off on.
>
> (Also Tejun - maybe you can see what's up - maybe that error message
> tells you something)
>
> I'm not sure what's up with his machine, the disk doesn't seem to be
> anyuthing particularly unusual, it looks like a 1TB Seagate Barracuda:
>
> ata1.00: ATA-8: ST1000DM003-1CH162, CC44, max UDMA/133
>
> which doesn't strike me as odd.
>
> Looking at the dmesg, it also looks like it's a pretty normal
> Sandybridge setup with Intel chipset. Artem, can you confirm? The PCI
> ID for the AHCI chip seems to be (INTEL, 0x1c02).
>
> Any ideas? Anybody?
>
That's correct. That's a very usual Asus P8P67 Pro motherboard (Intel
P67 chipset) in AHCI mode and run of the mill HDD which is the one you
identified.
--
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/
Powered by blists - more mailing lists