From: Riccardo Magliocchetti <riccardo.magliocchetti@gmail.com>
To: Stefan Lippers-Hollmann <s.L-H@gmx.de>
Cc: Takashi Iwai <tiwai@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
David Henningsson <david.henningsson@canonical.com>,
Kay Sievers <kay@redhat.com>
Subject: Re: udevd cannot modprobe snd-hda-intel with 3.9.8
Date: Sat, 29 Jun 2013 14:39:58 +0200 [thread overview]
Message-ID: <51CED59E.2030307@gmail.com> (raw)
In-Reply-To: <201306282208.23429.s.L-H@gmx.de>
Hi Stefan,
Il 28/06/2013 22:08, Stefan Lippers-Hollmann ha scritto:
> 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.
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
thanks a lot,
riccardo
next prev parent reply other threads:[~2013-06-29 12:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 18:10 Riccardo Magliocchetti
2013-06-28 20:08 ` Stefan Lippers-Hollmann
2013-06-29 12:39 ` Riccardo Magliocchetti [this message]
2013-07-01 15:50 ` Marc Haber
2013-07-02 4:47 ` Damien Wyart
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=51CED59E.2030307@gmail.com \
--to=riccardo.magliocchetti@gmail.com \
--cc=david.henningsson@canonical.com \
--cc=kay@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=s.L-H@gmx.de \
--cc=tiwai@suse.de \
/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