Re: IO errors after "block: remove bio_get_nr_vecs()"

[Artem S. Tashkinov]

On 2015-12-21 06:38, Ming Lei wrote:
> On Mon, Dec 21, 2015 at 1:51 AM, 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?
>
> BTW, I have posted very similar issue in the link:
>
> http://marc.info/?l=linux-ide&m=145066119623811&w=2
>
> Artem, I noticed from bugzillar that the hardware is i386, just
> wondering if PAE is enabled?  If yes, I am more confident
> that both the two kinds of report are similar or same.

Yes, I'm on i686 with PAE (16GB of RAM here) - it's specifically 
mentioned in the corresponding bug report.

P.S. I know Linus doesn't condone PAE but I still find it more 
preferrable than running a mixed environment with almost zero benefit in 
regard to performance and quite obvious performance regressions related 
to an increased number of libraries being loaded (i686 + x86_64) and 
slightly bloated code which sometimes cannot fit in the CPU cache. Call 
me old fashioned but I won't upgrade to x86_64 until most of the things 
that I run locally are available for x86_64 and that won't happen any 
time soon.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/