linux-kernel - Re: 3.13.0: crash on boot

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20140207144447.GJ24395@pd.tnic>
Date:	Fri, 7 Feb 2014 15:44:47 +0100
From:	Borislav Petkov <bp@...en8.de>
To:	"Alexandra N. Kossovsky" <Alexandra.Kossovsky@...etlabs.ru>
Cc:	Matt Fleming <matt@...sole-pimps.org>,
	Bjorn Helgaas <bhelgaas@...gle.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Matt Fleming <matt.fleming@...el.com>,
	Matthew Garrett <matthew.garrett@...ula.com>
Subject: Re: 3.13.0: crash on boot

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.
--
--
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/