linux-kernel - Re: [GIT PATCH] Driver Core patches for 2.6.18

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:	Tue, 26 Sep 2006 12:34:05 +0000
From:	Mike Galbraith <efault@....de>
To:	Greg KH <gregkh@...e.de>
Cc:	Linus Torvalds <torvalds@...l.org>, Andrew Morton <akpm@...l.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [GIT PATCH] Driver Core patches for 2.6.18

On Mon, 2006-09-25 at 22:37 -0700, Greg KH wrote:
> Here are a bunch of driver core and sysfs patches and fixes for 2.6.18.

Hi,

Just as an fyi, these patches cause a ~regression on my P4/HT box.

Suspend stopped here working after 2.6.17.  I haven't dug into why, but
since then, I get a message "Class driver suspend failed for cpu0", and
the suspend fails, but everything works fine afterward.  If I ignore the
return of drv->suspend(), the box will suspend and resume just fine,
both with this patch set and without.  (which is what I've been doing
while waiting for it to fix itself or for my round toit to turn up)

In the fail case _with_ this set though, all is not well after a failed
suspend.  The box isn't locked up, but it's ding-dong dead.  The GUI
freezes, but I can switch to command line.  I get to a login prompt, but
as I try to login, that VT is toast.  I tried a SysRq-T to see what
everybody's up to, but after the failure, we apparently never get as far
as restoring serial.  SysRq-B works.  SysRq-O don't.

It seems to be just me, (and I apparently don't care very much), but I
figured I should let you know about it.

	Cheers,

	-Mike

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