From: Tobias Geiger <tobias.geiger-9woOUGhjKTphl2p70BpVqQ@public.gmane.org>
To: Alex Williamson
<alex.williamson-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: Regression since 4.1
Date: Thu, 10 Dec 2015 00:07:57 +0100 [thread overview]
Message-ID: <6847091.8HQyRDvvTU@pc> (raw)
In-Reply-To: <1449688068.15753.461.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Hello Alex,
thanks for looking into this.
Nothing helps - not adding "ignore_loglevel" , not removing everything but the
most necessary (="BOOT_IMAGE=/boot/vmlinuz-4.3.0-trunk-amd64 ro
root=LABEL=dom0root panic=15 iommu=on intel_iommu=on ignore_loglevel") - grub
loads the kernel, loads initrd, execs the kernel - and then nothing. no output
of any kind from the kernel. no sysrq, no panic-reboot despite panic=15 ...
nothing. not even a blinking cursor, just a steady cursor which is still from
grub i guess...
It all comes down to kernel > 4.1 && iommu=on = not working here
Hardware is:
Intel DX58SO, Intel CPU i7 920... all pretty solid running for years now,
always with iommo=on.
I'd love to debug this further, just dont know how...
Greetings!
Tobias
Am Mittwoch, 9. Dezember 2015, 12:07:48 schrieb Alex Williamson:
> Try simply removing the "quiet" and "splash" or "rhgb" options if there
> are any from the kernel command line in grub first. You can temporarily
> just editing the commandline manually as you boot. If you don't have a
> serial console available, at least have a camera handy to take a picture
> of the screen. You can also add "ignore_loglevel" to the kernel
> commandline to get more logging. Thanks,
>
> Alex
next prev parent reply other threads:[~2015-12-09 23:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 17:01 Regression since 4.1 Tobias Geiger
2015-12-09 19:07 ` Alex Williamson
[not found] ` <1449688068.15753.461.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-12-09 23:07 ` Tobias Geiger [this message]
2015-12-28 16:49 ` Joerg Roedel
2016-04-04 17:06 ` Tom Wimmenhove
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=6847091.8HQyRDvvTU@pc \
--to=tobias.geiger-9wooughjktphl2p70bpvqq@public.gmane.org \
--cc=alex.williamson-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox