linux-kernel - Re: udevd cannot modprobe snd-hda-intel with 3.9.8

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-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <201306282208.23429.s.L-H@gmx.de>
Date:	Fri, 28 Jun 2013 22:08:20 +0200
From:	"Stefan Lippers-Hollmann" <s.L-H@....de>
To:	Riccardo Magliocchetti <riccardo.magliocchetti@...il.com>
Cc:	Takashi Iwai <tiwai@...e.de>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	David Henningsson <david.henningsson@...onical.com>,
	Kay Sievers <kay@...hat.com>
Subject: Re: udevd cannot modprobe snd-hda-intel with 3.9.8

Hi

On Friday 28 June 2013, Riccardo Magliocchetti wrote:
> Hello,
> 
> at boot udev (175-7.2 from debian unstable) blocks for maybe 30 seconds 
> and then gives (handcopied)
> 
>   timeout: killing '/sbin/modprobe -b 
> pci:v00008086d0000293Esv0000144Dsd0000C045bc04sc03i00'
> 
> when booting 3.9.8. 3.8.13 has the same issue, 3.6.0 is fine.
[…]

I think oss-compat might interfere here. Given that it was recently 
(2013-06-18) updated, this would explain why only new'ish kernels are 
affected (initramfs not updated for the older ones). Therefore I'd 
suggest to purge oss-compat (simple removal is not sufficient, as the 
modprobe.d/ snippets are dpkg conffiles) for testing - and to file a 
bug[1] against the new version of oss-compat, if you can confirm it 
to be responsible.

Regards
	Stefan Lippers-Hollmann

[1]	http://www.debian.org/Bugs/Reporting
--
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/