linux-kernel - Re: 3.4.4: Oops in snd_hda_codec_realtek (alc_auto_create_multi_out

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

Date:	Tue, 17 Jul 2012 17:46:27 -0600
From:	Robert Hancock <hancockrwd@...il.com>
To:	Takashi Iwai <tiwai@...e.de>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>,
	Alsa-Devel <alsa-devel@...a-project.org>
Subject: Re: 3.4.4: Oops in snd_hda_codec_realtek (alc_auto_create_multi_out_ctls)

On Tue, Jul 17, 2012 at 6:25 AM, Takashi Iwai <tiwai@...e.de> wrote:
> At Mon, 9 Jul 2012 13:40:09 -0600,
> Robert Hancock wrote:
>>
>> I've got a sort of industrial portable PC that uses a Supermicro C2SBX
>> motherboard. Running an RHEL6 kernel (2.6.32-ish) it works fine, but
>> if I run a 3.4.4 kernel (using the kernel-ml builds provided by ELRepo
>> for RHEL6) it blows up on boot inside snd_hda_codec_realtek. Below is
>> the dmesg output from bootup up to the oops, after I blacklisted
>> snd_hda_intel from auto-loading and then manually modprobed it. Is
>> this a known problem?
>
> I don't know of this issue, so need to check more.
> Could you load snd-hda-intel module with probe_only=1 option, and run
> alsa-info.sh with --no-upload option and give the output?
> Then I can try the emulator to see what's wrong.
>
> Also, of course, testing a newer kernel like 3.5-rc7 would be helpful,
> too.

Unfortunately this machine is about to ship back out to a customer so
there's not really any more info I can gather from it at this point.
If I can get hold of it or a similar machine again in the future, I
can try to get more information.
--
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/