All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe De Muyter <phdm@macqel.be>
To: David Miller <davem@davemloft.net>
Cc: kyle@mcmartin.ca, linux-pm@lists.linux-foundation.org,
	linux-laptop@vger.kernel.org, grundler@parisc-linux.org,
	jarkao2@gmail.com
Subject: apm/pm bug [was Re: tulip : kernel BUG in tulip_up/tulip_resume]
Date: Sun, 6 Dec 2009 18:10:57 +0100	[thread overview]
Message-ID: <20091206171057.GA4363__30443.0366996259$1260202962$gmane$org@frolo.macqel> (raw)
In-Reply-To: <20091203084742.GA23867@frolo.macqel>

[CCing linux-laptop@vger.kernel.org and linux-pm@lists.linux-foundation.org]

On Thu, Dec 03, 2009 at 09:47:42AM +0100, Philippe De Muyter wrote:
> Hi Jarek and David,
> On Wed, Dec 02, 2009 at 10:25:26PM -0800, David Miller wrote:
> > From: Jarek Poplawski <jarkao2@gmail.com>
> > Date: Sun, 29 Nov 2009 12:36:59 +0100
> > 
> > > On Sun, Nov 29, 2009 at 01:17:10AM +0100, Jarek Poplawski wrote:
> > >> Philippe De Muyter wrote, On 11/08/2009 11:33 PM:
> > >> > Does someone know what could be wrong and have a fix or should I look myself ?
> > >> 
> > >> Don't know, guess only...
> > > 
> > > ...And maybe a second guess btw. (to try together or separate).
> > 
> > Philippe please test Jarek's patches.
> 
> Busy doing that. I had some problems trying to activate apm's debug.
> Will report later.

The problem seems not to be in tulip driver, but in apm or power management.
I see, with some debugging added by me :

[  488.585707] eth0: Digital DS21142/43 Tulip rev 17 at Port 0xec00, 00:00:f8:02:cf:08, IRQ 11.
[  508.888374] eth0: 21143 10baseT link beat good.
[  530.754453] apm: BIOS version 1.1 Flags 0x03 (Driver version 1.16ac)
[  530.754723] apm: entry f690:7ca cseg16 f690 dseg 40 cseg len ffff, dseg len ffff
[  531.016684] apm: Connection version 1.1
[  531.018853] apm: AC on line, battery status unknown, battery life unknown
[  531.028277] apm: battery flag 0x80, battery life unknown
[  864.060751] apm: received system standby notify
[  864.063111] check_events : calling standby()
[ 1141.088550] apm: received system standby resume notify
[ 1141.090195] check_events : calling dpm_resume_end(PMSG_RESUME)
[ 1141.096173] tulip_resume

I do not see there a call to tulip_suspend after the call to standby(),
but I think there should be one.

Philippe

      parent reply	other threads:[~2009-12-06 17:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-27 16:57 [PATCH] tulip : fix 21142 with 10Mbps without negotiation Philippe De Muyter
2009-01-30 21:49 ` David Miller
     [not found] ` <20090129210701.GA8092@frolo.macqel>
2009-11-08 22:33   ` tulip : kernel BUG in tulip_up/tulip_resume Philippe De Muyter
2009-11-21 19:10     ` David Miller
2009-11-29  0:17     ` Jarek Poplawski
2009-11-29 11:36       ` Jarek Poplawski
2009-12-03  6:25         ` David Miller
2009-12-03  8:47           ` Philippe De Muyter
2009-12-06 17:10             ` apm/pm bug [was Re: tulip : kernel BUG in tulip_up/tulip_resume] Philippe De Muyter
2009-12-06 17:10             ` Philippe De Muyter [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='20091206171057.GA4363__30443.0366996259$1260202962$gmane$org@frolo.macqel' \
    --to=phdm@macqel.be \
    --cc=davem@davemloft.net \
    --cc=grundler@parisc-linux.org \
    --cc=jarkao2@gmail.com \
    --cc=kyle@mcmartin.ca \
    --cc=linux-laptop@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.