netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Grant Grundler <grundler@parisc-linux.org>
Cc: netdev@vger.kernel.org
Subject: Re: PATCH for [Bug 8952] tulip driver oops in tulip_interrupt when hibernating with swsusp/suspend2
Date: Fri, 30 May 2008 22:09:35 -0400	[thread overview]
Message-ID: <4840B35F.7080807@pobox.com> (raw)
In-Reply-To: <20080512063751.GH32317@colo.lackof.org>

Grant Grundler wrote:
> Jeff,
> The following patch is seems to fix the tulip suspend/resume panic:
> 	http://bugzilla.kernel.org/show_bug.cgi?id=8952#c46
> 
> My attempts at a cleaner patch failed and Pavel thinks this is OK.
> Since suspend/resume is getting an overhaul in 2.6.27 (per comment
> #49 by  Rafael J. Wysocki), it makes sense to invest more time as
> part of that rework and apply the known fix to 2.6.26.
> 
> hth,
> grant
> 
> Original from:  kernelbugs@tap.homeip.net
> Signed-off-by: Grant Grundler <grundler@parisc-linux.org>
> 
> diff --git a/drivers/net/tulip/tulip_core.c b/drivers/net/tulip/tulip_core.c
> index f9d13fa..088d3bf 100644
> --- a/drivers/net/tulip/tulip_core.c
> +++ b/drivers/net/tulip/tulip_core.c
> @@ -1729,12 +1729,15 @@ static int tulip_suspend (struct pci_dev *pdev, pm_message_t state)
>  	if (!dev)
>  		return -EINVAL;
>  
> -	if (netif_running(dev))
> -		tulip_down(dev);
> +	if (!netif_running(dev))
> +		goto save_state:
> +
> +	tulip_down(dev);

how could this be tested if it doesn't even compile?

Oh well, seems sane, let's see...




  reply	other threads:[~2008-05-31  2:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-12  6:37 PATCH for [Bug 8952] tulip driver oops in tulip_interrupt when hibernating with swsusp/suspend2 Grant Grundler
2008-05-31  2:09 ` Jeff Garzik [this message]
2008-05-31 23:54   ` Grant Grundler
2008-05-31  2:12 ` Jeff Garzik

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=4840B35F.7080807@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=grundler@parisc-linux.org \
    --cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).