linux-kernel - Re: [4/4] 2.6.23-rc4: known regressions

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: <1188470552.22467.8.camel@localhost>
Date:	Thu, 30 Aug 2007 12:42:32 +0200
From:	Soeren Sonnenburg <kernel@....de>
To:	Michal Piotrowski <michal.k.k.piotrowski@...il.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>,
	linux-pm@...ts.linux-foundation.org,
	"Rafael J\. Wysocki" <rjw@...k.pl>, Pavel Machek <pavel@....cz>,
	Arkadiusz Miskiewicz <arekm@...en.pl>,
	Thomas Voegtle <tv@...96.de>,
	linux-usb-devel@...ts.sourceforge.net, Greg KH <gregkh@...e.de>,
	Alan Stern <stern@...land.harvard.edu>,
	Oliver Neukum <oliver@...kum.org>,
	Tino Keitel <tino.keitel@....de>
Subject: Re: [4/4] 2.6.23-rc4: known regressions

On Wed, 2007-08-29 at 17:27 +0200, Michal Piotrowski wrote:

> Power management
> 
> Subject         : something broke resume from s2ram on mbp c1d (??? :))
> References      : http://lkml.org/lkml/2007/8/28/67
> Last known good : 2.6.23-rc3
> Submitter       : Soeren Sonnenburg <kernel@....de>
> Caused-By       : ?
> Handled-By      : Rafael J. Wysocki <rjw@...k.pl>
> Status          : unknown

> Subject         : resume from ram much slower
> References      : http://lkml.org/lkml/2007/8/10/275
> Last known good : 2.6.23-rc1 ?
> Submitter       : Arkadiusz Miskiewicz <arekm@...en.pl>
> Caused-By       : ?
> Handled-By      : Rafael J. Wysocki <rjw@...k.pl>
> Status          : problem is being debugged


I am not sure whether the problem I am having is not the very same as
the one Arkadiusz is seeing. At least I've found resume from s2ram to be
working a couple of times. Only sometimes it took long to resume, that
is >30 seconds (around 5 - which I already consider long - is normal). 

anyway this this is with the closed source fglrx kernel module, as
without the machine freezes when X is running on resume...

well and fglrx seems to cause this ...

BUG: scheduling while atomic: Xorg/0x00000002/3408
 [<c03c39a2>] schedule+0x5d2/0x6d0
 [<c0127038>] __wake_up+0x38/0x50
 [<f8c2df71>] irqmgr_wrap_shutdown+0xe1/0x150 [fglrx]
 [<f8c1b42f>] firegl_release_helper+0x55f/0x7d0 [fglrx]
 [<f8c1ed8b>] firegl_takedown+0x5b/0xc40 [fglrx]
 [<f8c1e41f>] firegl_release+0x12f/0x190 [fglrx]
 [<f8c126ff>] ip_firegl_release+0xf/0x20 [fglrx]
 [<c017a451>] __fput+0x91/0x160
 [<c01776f9>] filp_close+0x49/0x80
 [<c012f56c>] put_files_struct+0x9c/0xc0
 [<c013080e>] do_exit+0x12e/0x7c0
 [<f8c6dd09>] IRQMGR_WorkerThreadRoutine+0x29/0x30 [fglrx]
 [<f8c0fb90>] kasThreadRoutineHelper+0x0/0x20 [fglrx]
 [<f8c0fb90>] kasThreadRoutineHelper+0x0/0x20 [fglrx]
 [<f8c2dd1e>] IRQMGR_CallbackWrapper+0xe/0x20 [fglrx]
 [<f8c0fb90>] kasThreadRoutineHelper+0x0/0x20 [fglrx]
 [<c0104f85>] kernel_thread_helper+0xd/0x18

well...
Soeren
-- 
Sometimes, there's a moment as you're waking, when you become aware of
the real world around you, but you're still dreaming.
-
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/