From: Alexander Holler <holler@ahsoftware.de>
To: Joerg Roedel <joro@8bytes.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: AMD-IOMMU and problem with __init(data)?
Date: Sat, 26 Sep 2015 10:18:24 +0200 [thread overview]
Message-ID: <560654D0.7040202@ahsoftware.de> (raw)
In-Reply-To: <5602F7BF.4020009@ahsoftware.de>
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
next prev parent reply other threads:[~2015-09-26 8:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 10:22 AMD-IOMMU and problem with __init(data)? Alexander Holler
2015-09-23 11:43 ` Joerg Roedel
2015-09-23 15:50 ` Alexander Holler
2015-09-23 19:04 ` Alexander Holler
2015-09-26 8:18 ` Alexander Holler [this message]
2015-09-29 15:06 ` Joerg Roedel
2015-09-29 17:17 ` Alexander Holler
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=560654D0.7040202@ahsoftware.de \
--to=holler@ahsoftware.de \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
/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.