Hi.
I think I rang the bell a bit early. The corruption is in grub legacy (I
assumed that would be in Linux too, but it wasn't). The on disk format
of ext4 apparently stores byte ordering somehow? I thought the on disk
format of ext4 was a specific endian (little). Since only that file is
unr
Never mind my ranting.
The problem was in the extent disk format of ext4. I had forgot that
ext4 uses extents for all new files by default. Old grub won't read extents.
Oh, well... nothing like wasting hard working peoples time with stupid
things. Anyway. SWIOTLB for 32-bit PAE should be a goo
On Sat, Oct 03, 2015 at 02:00:19PM -0400, Konrad Rzeszutek Wilk wrote:
> Aye. I presume that you had done a small change already for this?
> Would you be willing to post it on lkml and CC me ?
Yes, I also think it is needed. SWIOTLB already correctly handles
buffers in HighMem, so enabling it for
On Sat, Oct 03, 2015 at 09:36:30AM -0500, Bjorn Helgaas wrote:
> [+cc Konrad, Joerg, iommu list]
>
> On Fri, Oct 02, 2015 at 04:20:16PM +0200, Christian Melki wrote:
> > I discovered a strange error on my machine. 32-bit PAE 4.2.0 without
> > IOMMU code (yeah, I know).
> > When writing to an ext4
[+cc Konrad, Joerg, iommu list]
On Fri, Oct 02, 2015 at 04:20:16PM +0200, Christian Melki wrote:
> I discovered a strange error on my machine. 32-bit PAE 4.2.0 without
> IOMMU code (yeah, I know).
> When writing to an ext4 filesystem on a USB disk my kernel would hang
> and not return control to u
