From: Borislav Petkov <bp@alien8.de>
To: "Alexandra N. Kossovsky" <Alexandra.Kossovsky@oktetlabs.ru>
Cc: Matt Fleming <matt@console-pimps.org>,
Bjorn Helgaas <bhelgaas@google.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Matt Fleming <matt.fleming@intel.com>,
Matthew Garrett <matthew.garrett@nebula.com>
Subject: Re: 3.13.0: crash on boot
Date: Fri, 7 Feb 2014 15:44:47 +0100 [thread overview]
Message-ID: <20140207144447.GJ24395@pd.tnic> (raw)
In-Reply-To: <20140207090043.GB24536@oktetlabs.ru>
On Fri, Feb 07, 2014 at 01:00:45PM +0400, Alexandra N. Kossovsky wrote:
> I asked. He installed an update. No difference.
Ok.
> > Btw, did this box boot any kernels successfully in EFI mode at all?
>
> Yes. It booted, for example, the same 3.13 kernel from Debian - without
> debug options.
Huh, what debug options?
I see
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-3.13.0-debug-amd64 root=UUID=c5078 393-d2ff-435d-82e8-e85990b3c9e2 ro console=tty1 console=ttyS2,115200n8 intel_iommu=on nmi_watchdog=nopanic
which fails.
Which one doesn't fail?
Also, does "intel_iommu=off" change anything?
Thanks.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2014-02-07 14:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 8:37 Alexandra N. Kossovsky
2014-01-31 18:29 ` Bjorn Helgaas
2014-02-03 14:41 ` Matt Fleming
2014-02-03 14:54 ` Borislav Petkov
2014-02-04 13:30 ` Alexandra N. Kossovsky
2014-02-05 1:32 ` Borislav Petkov
2014-02-07 9:00 ` Alexandra N. Kossovsky
2014-02-07 14:44 ` Borislav Petkov [this message]
[not found] ` <20140207172618.GA8385@sanechka.spb.ru>
2014-02-07 17:42 ` Borislav Petkov
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=20140207144447.GJ24395@pd.tnic \
--to=bp@alien8.de \
--cc=Alexandra.Kossovsky@oktetlabs.ru \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=matt@console-pimps.org \
--cc=matthew.garrett@nebula.com \
/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
Powered by JetHome