linux-kernel - Re: regression: fireware causes oops during system

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: <46E6F076.5000006@s5r6.in-berlin.de>
Date:	Tue, 11 Sep 2007 21:45:58 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Pavel Machek <pavel@....cz>
CC:	Ben Collins <ben.collins@...ntu.com>,
	kernel list <linux-kernel@...r.kernel.org>,
	linux1394-devel@...ts.sourceforge.net
Subject: Re: regression: fireware causes oops during system

>> On Tue, 2007-09-11 at 21:00 +0200, Pavel Machek wrote:
>>> I noticed empty suspend stopped working around 2.6.23-rc4, and it is
>>> still present in 2.6.23-rc6.
...
>>> Unsetting
>>>
>>> CONFIG_IEEE1394=y
>>>
>>> solves the problem.
...

Between -rc3 and -rc4:

	ieee1394: sbp2: fix sbp2_remove_device for error cases
	a2ee3f9bbb0ce57102dad8928d54f59acdc4b8f7
	should not occur in suspend path

Between -rc1 and -rc2:

	ieee1394: sbp2: more correct Kconfig dependencies
	e4f8cac5e07528f7e0bc21d3682c16c9de993ecb
	unrelated

	ieee1394: revert "sbp2: enforce 32bit DMA mapping"
	a9c2f18800753c82c45fc13b27bdc148849bdbb2
	unrelated

	(not via linux1394-2.6.git)
	raw1394 __user annotation
	5b26e64ea39e45802c5736c8261bf8a8704d212f
	unrelated

So it must be something older which was somehow uncovered.
Dmesg with the oops or/and bisection would be good.
-- 
Stefan Richter
-=====-=-=== =--= -=-==
http://arcgraph.de/sr/
-
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/