linux-kernel - Re: Linux 3.4 released

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]

Date:	Wed, 23 May 2012 13:26:57 -0700
From:	Tejun Heo <tj@...nel.org>
To:	Jörg-Volker Peetz <jvpeetz@....de>
Cc:	linux-kernel@...r.kernel.org, Takashi Iwai <tiwai@...e.de>
Subject: Re: Linux 3.4 released

Cc'ing Takashi.  Hi!

On Wed, May 23, 2012 at 09:56:36PM +0200, Jörg-Volker Peetz wrote:
> May 23 21:32:33 hostname kernel: XXX delayed_work_timer_fn: cwq
> (null), fn=hdmi_repoll_eld

So, we have the winner.

Takashi, sound/pci/hda/patch_hdmi.c::hdmi_repoll_eld() is causing
workqueue code dereference %NULL pointer.  It *looks* like something
is corrupting the work item while it's queued.  It could be a
workqueue bug but I don't think that's likely - the code has been
stable for quite some time now.  I glanced through the code and
nothing stands out.  Does something ring a bell?

> (without line-break).
> 
> By the way, don't know if this is related, I have a phenomenon with a spurious
> interrupt with every linux version I've used before on this notebook. Half a
> minute after starting the system the computer produces approx. 220 lines like
> 
> ... kernel: hda-intel: spurious response 0x0:0x0, last cmd=0x170503
> 
> Now with 3.4.0, I see an additional message right before (the minute before) the
> "XXX ..." line:
> 
> ...kernel: hda_intel: azx_get_response timeout, switching to single_cmd mode:
> last cmd=0x003f0900

These too seem to be for you, Takashi. :)

Thanks.

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