linux-kernel - mei oopses at startup if it's built-in (3.11-rc5)

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <CALCETrXmy1KwGUNbG0pgsbAt=mk27P3xd0ja4i9sPB6RhbcOeg@mail.gmail.com>
Date:	Wed, 14 Aug 2013 17:14:40 -0700
From:	Andy Lutomirski <luto@...capital.net>
To:	Tomas Winkler <tomas.winkler@...el.com>,
	linux-kernel@...r.kernel.org
Subject: mei oopses at startup if it's built-in (3.11-rc5)

It blows up early enough that it's awkward to get the whole oops, but
it's in the probe function.  If it's a module, I get instead:

[   73.401679] mei_me 0000:00:16.0: Device doesn't have valid ME Interface
[   73.401684] mei_me 0000:00:16.0: initialization failed.

Let me know if I should debug further, but this may be obvious.

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