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: <20130701155016.GA23358@torres.zugschlus.de>
Date:	Mon, 1 Jul 2013 17:50:16 +0200
From:	Marc Haber <mh+linux-kernel@...schlus.de>
To:	Riccardo Magliocchetti <riccardo.magliocchetti@...il.com>
Cc:	Stefan Lippers-Hollmann <s.L-H@....de>,
	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

On Sat, Jun 29, 2013 at 02:39:58PM +0200, Riccardo Magliocchetti wrote:
> Confirm that after purging oss-compat 3.9.8 boot is fine. Please
> note that a yesterday build of 3.6.11 used to work fine too so
> there's also something that changed kernel side.
> FYI there was already a bug in debian bug tracker:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660803#130

I found myself in the same situation. Unfortunately, right after doing
a BIOS update on my T520, which has led me into the wrong direction.
Additionally, he real colprit is snd.ko, which is loaded as a
dependency of snd-hda-intel and - surprisingly for me - thinkpad_acpi.
The latter sent me into another round of trying to debug ACPI. I
suspected ACPI to be the culprit because my notebook wouldn't suspend.

The issue does not appear when one uses a Debian kernel, or uses the
configuration that Debian uses for its kernels to build a vanilla
kernel.org kernel. This has, after a gazillion of reoboots and
experimenting with man different blacklist entries and kernel
configuration, led me to the fact that this bug does not show if the
kernel is compiled with CONFIG_SND_SUPPORT_OLD_API=y.

So it was my error to dump backwards compatibility and to remove the
old api support. I have now set CONFIG_SND_SUPPORT_OLD_API=y again and
everything is fine.

Greetings
Marc

-- 
-----------------------------------------------------------------------------
Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany  |  lose things."    Winona Ryder | Fon: *49 621 31958061
Nordisch by Nature |  How to make an American Quilt | Fax: *49 621 31958062
--
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/