From: Alex Williamson <alex.williamson-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Tobias Geiger <tobias.geiger-9woOUGhjKTphl2p70BpVqQ@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: Regression since 4.1
Date: Wed, 09 Dec 2015 12:07:48 -0700 [thread overview]
Message-ID: <1449688068.15753.461.camel@redhat.com> (raw)
In-Reply-To: <5418503.92eb9JWhCR@t400>
On Wed, 2015-12-09 at 18:01 +0100, Tobias Geiger wrote:
> Hello!
>
> in short:
> No Kernel since 4.1 boots on my machine.
>
> I can make newer kernels boot, but ONLY when i remove "iommu=on
> intel_iommu=on" from the cmdline.
> If i leave it in, as with all the kernels before and including 4.1, newer
> kernels dont boot, and in a really not very informative way:
> They dont even print a single message to the console, i only see the grub-
> messages (like "loading kernel" and "loading initial ramdisk") - after these
> messages NO more output of any kind - also no SysRQ keys working - nothing.
>
> Because of this complete lack of information, i guess its hard to debug for
> you the cause of this.
> Perhaps i can help - but how?
>
> i'm writing from a pure IOMMU-User perspective - i can compile kernels, but
> never git-bisected, so maybe a hint to a tutorial for that would be great!
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 19: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 [this message]
[not found] ` <1449688068.15753.461.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-12-09 23:07 ` Tobias Geiger
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=1449688068.15753.461.camel@redhat.com \
--to=alex.williamson-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=tobias.geiger-9woOUGhjKTphl2p70BpVqQ@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 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.