netdev - Re: [patch 0/6] sky2 driver update (v1.11)

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

Date:	Mon, 15 Jan 2007 20:12:11 +0100
From:	Tino Keitel <tino.keitel@...ei.de>
To:	Stephen Hemminger <shemminger@...l.org>
Cc:	netdev@...r.kernel.org
Subject: Re: [patch 0/6] sky2 driver update (v1.11)

On Mon, Jan 15, 2007 at 10:21:49 -0800, Stephen Hemminger wrote:
> On Sat, 13 Jan 2007 14:03:29 +0100
> Tino Keitel <tino.keitel@...ei.de> wrote:
> 
> > On Tue, Jan 02, 2007 at 20:10:15 +0100, Tino Keitel wrote:
> > 
> > [...]
> > 
> > > Btw., I just built 2.6.20-rc3 with patches 4 and 5 and wake on LAN now
> > > works. Thanks for your work.
> > 
> > Hi,
> > 
> > I had some failures during resume from suspend with 2.6.20-rc3 and
> > -rc4. I enabled pm_trace and it looks like the sky2 driver is the
> > culprit:
> > 
> > hash matches drivers/base/power/resume.c:56
> > hash matches device 0000:01:00.0
> > 
> > $ lspci | grep 01:00.0
> > 01:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8053
> > PCI-E Gigabit Ethernet Controller (rev 22)
> > 
> > I removed the patches and had no resume failure so far.
> > 
> > Regards,
> > Tino
> > 
> 
> What kind of failures, did the system just not come up?

Yes, screen stayed dark and machine was dead. However, it was hardly
reproducable. I set up a suspend/resume loop for an hour without
failures. Then, when I just wanted to suspend for a while, resume
failed.

> Did you have WOL enabled or not?

I had WOL enabled.

Regards,
Tino
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html