netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@vyatta.com>
To: Rene Mayrhofer <rene.mayrhofer@gibraltar.at>
Cc: netdev@vger.kernel.org, Richard Leitner <leitner@esys.at>
Subject: Re: Kernel oops on setting sky2 interfaces down
Date: Mon, 27 Jul 2009 09:30:18 -0700	[thread overview]
Message-ID: <20090727093018.4a830259@nehalam> (raw)
In-Reply-To: <4A6D8975.4050000@gibraltar.at>

On Mon, 27 Jul 2009 13:03:17 +0200
Rene Mayrhofer <rene.mayrhofer@gibraltar.at> wrote:

> Stephen Hemminger schrieb:
> > You could try commenting out sky2_shutdown which does the Wol
> > power down stuff. Maybe changing setting of Wake On Lan would
> > help as well.
> > 
> > What happens if you take interface down 'ip link set eth0 down' (or ifconfig)?
> > 
> > There are several different register writes in the shutdown path.
> > You could add code to check if a particular access is disabling
> > the PCI buss with:
> > 
> >     sky2_write(... som register...)
> >     BUG_ON(sky2_read16(sky2->hw, B0_CTST) == 0xffff);
> 
> I tried adding that wherever it seemed to make sense, resulting in

Does the platform use MSI? Perhaps it generates a bogus interrupt when
powered off.

  reply	other threads:[~2009-07-27 16:30 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-21 16:26 Kernel oops on setting sky2 interfaces down Rene Mayrhofer
2009-07-21 16:58 ` Stephen Hemminger
2009-07-21 19:59   ` Rene Mayrhofer
2009-07-21 20:54     ` Stephen Hemminger
2009-07-23 17:28 ` Stephen Hemminger
2009-07-27 11:03   ` Rene Mayrhofer
2009-07-27 16:30     ` Stephen Hemminger [this message]
2009-07-28  7:21       ` Rene Mayrhofer
2009-07-27 22:35     ` Stephen Hemminger
2009-07-28  7:25       ` Rene Mayrhofer
2009-07-28  9:48       ` Rene Mayrhofer
2009-08-03 11:55       ` Rene Mayrhofer
2009-08-03 18:19         ` Rene Mayrhofer
2009-08-04  7:38           ` Rene Mayrhofer
2009-08-04 11:18             ` Mike McCormack
2009-08-04 21:31               ` Rene Mayrhofer
     [not found]             ` <392fb48f0908040445pc21105bo3182773b76d49596@mail.gmail.com>
2009-08-04 22:55               ` Rene Mayrhofer
2009-08-04 22:59                 ` Rene Mayrhofer
2009-08-04 23:08                   ` Stephen Hemminger
2009-08-04 23:53                   ` Mike McCormack
2009-08-05 12:14                     ` Rene Mayrhofer
2009-08-05 22:50                       ` Mike McCormack
2009-08-10 10:28                         ` Rene Mayrhofer
2009-08-11  8:54                           ` Rene Mayrhofer
2009-08-19  7:01                             ` Rene Mayrhofer
2009-08-19 15:00                               ` Mike McCormack
2009-08-19 15:11                                 ` Rene Mayrhofer
2009-08-19 21:07                                 ` Rene Mayrhofer
2009-08-19 21:25                                   ` Rene Mayrhofer
2009-08-19 22:05                                   ` Mike McCormack
2009-08-20  0:46                                     ` Stephen Hemminger
2009-08-20 20:37                                       ` Rene Mayrhofer
2009-08-21 11:03                                         ` Mike McCormack
2009-08-20 19:42                                     ` Rene Mayrhofer

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=20090727093018.4a830259@nehalam \
    --to=shemminger@vyatta.com \
    --cc=leitner@esys.at \
    --cc=netdev@vger.kernel.org \
    --cc=rene.mayrhofer@gibraltar.at \
    /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).