[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <560654D0.7040202@ahsoftware.de>
Date: Sat, 26 Sep 2015 10:18:24 +0200
From: Alexander Holler <holler@...oftware.de>
To: Joerg Roedel <joro@...tes.org>
Cc: linux-kernel@...r.kernel.org
Subject: Re: AMD-IOMMU and problem with __init(data)?
Am 23.09.2015 um 21:04 schrieb Alexander Holler:
> Am 23.09.2015 um 17:50 schrieb Alexander Holler:
>> Am 23.09.2015 um 13:43 schrieb Joerg Roedel:
>>>> If it's necessary, I could try put together a small patch which
>>>> kills a system (reproducible here).
>>>
>>> That would help too, please also send me your .config and I'll try to
>>> reproduce the issue here.
>>
>> Will do. Later.
>
> Done. Patch(es) and config attached. Note, while reducing the patch,
> I've noted that when I change
Just in case of, the command line I'm using is
ro root=/dev/sdb2 rootfstype=btrfs rootflags=compress=zlib enforcing=0
selinux=0 cgroup_disable=memory swapaccount=0
earlycon=uart8250,io,0x3f8,115200n8 console=ttyS0,115200n8 console=tty0
memtest=3 LANG=de_DE.UTF-8 video=DVI-D-1:1920x1080-32@60
And memtest never failed (I'm always using that). So it's unlikely it's
a problem with the memory.
But usually I don't have enabled the serial, that means normally I'm
booting with
root=/dev/sdb2 rootfstype=btrfs rootflags=compress=zlib enforcing=0
selinux=0 cgroup_disable=memory swapaccount=0 console=tty0 memtest=3
LANG=de_DE.UTF-8 video=DVI-D-1:1920x1080-32@60
so maybe enabling the serial does something bad. Also I've enabled it
before and haven't seen something bad. And because I assume the IOMMU is
the problem, I don't use any cards, just the HW on mb.
Regards,
Alexander Holler
--
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