linux-kernel - Re: 3.1-rc5 is the worst

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: <s5haaaa865l.wl%tiwai@suse.de>
Date:	Mon, 12 Sep 2011 11:24:38 +0200
From:	Takashi Iwai <tiwai@...e.de>
To:	Francis Moreau <francis.moro@...il.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: 3.1-rc5 is the worst

At Sat, 10 Sep 2011 11:57:06 +0200,
Francis Moreau wrote:
> 
> Hello,
> 
> Maybe the subject sounds rude so apologize since I just want to report
> that 3.1-rc5 gives me bad impression.
> 
> Of course it's all about my hw support which seems to get some
> regressions (I attached lspci).
> 
> 1/ I'm getting this now at each boot:
> 
>   [   38.349671] hda_codec: too deep connection for 0x18
>   [   38.349748] hda_codec: too deep connection for 0x18
>   [   38.349842] hda_codec: too deep connection for 0x18
>   [   38.349843] hda_codec: too deep connection for 0x18
>   [   38.349844] hda_codec: too deep connection for 0x18
>   [   38.349939] hda_codec: too deep connection for 0x18
>   <repeated 252 times>
> 
> I've no idea what it does mean or it's simply a warning I can ignore
> (and it that case it would be nice to limit it at least) or if it's
> worse getting a fix before 3.1 is out would be great.

Could you give alsa-info.sh outputs (run with --no-upload option)
for both working and non-working kernels?  lspci doesn't expose
anything about codecs and other details.


thanks,

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