linux-kernel - Re: PROBLEM: snd_hda

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]

Message-ID: <CAErSpo7sHD=vLGmkS9Cd0cFxiGnBoY3Khcq9Fr33i6xKhhq43g@mail.gmail.com>
Date:	Thu, 9 Aug 2012 11:34:26 -0700
From:	Bjorn Helgaas <bhelgaas@...gle.com>
To:	Alexei Kornienko <alexei.kornienko@...il.com>
Cc:	Jesper Juhl <jj@...osbits.net>, linux-kernel@...r.kernel.org
Subject: Re: PROBLEM: snd_hda_intel bug during boot

If you can collect complete dmesg logs from the working kernel and the
broken kernel and post them, the differences might have a clue.  You
might also collect /proc/iomem and "lspci -vv" for both cases while
you're at it.

On Wed, Aug 8, 2012 at 10:38 PM, Alexei Kornienko
<alexei.kornienko@...il.com> wrote:
> Hi,
>
> Yes it used to work with 2.6 kernel.
> Ok I will do a bisect and try to find the source of the problem.
> I'll notify you if I'll find something but don't expect it to be fast
> cause the problem happens on my home laptop (pretty old and rusty :) )
> and I also have a lot of other stuff to do.
>
> Regards,
> Alexei
>
> 2012/8/8 Jesper Juhl <jj@...osbits.net>:
>> On Wed, 8 Aug 2012, Jesper Juhl wrote:
>>
>>> On Wed, 8 Aug 2012, Alexei Kornienko wrote:
>>>
>>> > Seems like I have a bug in audio driver on my laptop. Cause of this I
>>> > don't have any sound card detected.
>>> > Please find more details below:
>>> >
>>> > ** Version:
>>> > Linux version 3.2.0-29-generic-pae (buildd@...eapple) (gcc version
>>> > 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #46-Ubuntu SMP Fri Jul 27
>>> > 17:25:43 UTC 2012
>>> >
>>> Ok, so I openly admit that I have no clue as to what your problem might
>>> be. But, one thing I do know is that, a *lot* has changed since the 3.2
>>> kernel you are running and the most recent stable (3.5) kernel. So,
>>> perhaps you could test the 3.5 kernel and tell us if you still see the
>>> problem with that one or not?
>>> If you are feeling adventurous you could also try a snapshot of the latest
>>> Linus (to become 3.6) kernel and tell us your experiences with that...?
>>>
>> Also, if this used to work with an older kernel, then it would probably
>> be helpful if you could do a "git bisect" between the older (working)
>> kernel version and your current (broken) kernel version in order to zoom
>> in on the commit that broke things for you.
>>
>> --
>> Jesper Juhl <jj@...osbits.net>       http://www.chaosbits.net/
>> Don't top-post http://www.catb.org/jargon/html/T/top-post.html
>> Plain text mails only, please.
>>
> --
> 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/
--
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/