netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@vyatta.com>
To: Sven Joachim <svenjoac@gmx.de>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
	linux-kernel@vger.kernel.org
Subject: Re: sky2 driver breaks reboot/shutdown
Date: Wed, 16 Nov 2011 14:48:06 -0800	[thread overview]
Message-ID: <20111116144806.0b6e327f@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <878vnfpy6y.fsf@turtle.gmx.de>

On Wed, 16 Nov 2011 22:14:13 +0100
Sven Joachim <svenjoac@gmx.de> wrote:

> [ Resending since my first attempt apparently did not make it to the
>   mailing lists.  Apologies to anyone who receives duplicates. ]
> 
> Hi,
> 
> after upgrading from Linux 3.1 to 3.2-rc2 I noticed that the kernel
> would no longer reboot or shutdown properly, hanging instead.  Removing
> the sky2 driver works around this.  According to "lspci -v", I have the
> following network card:
> 
> ,----
> | 03:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller (rev 13)
> | 	Subsystem: ABIT Computer Corp. Device 108f
> | 	Flags: bus master, fast devsel, latency 0, IRQ 17
> | 	Memory at fdefc000 (64-bit, non-prefetchable) [size=16K]
> | 	I/O ports at ce00 [size=256]
> | 	[virtual] Expansion ROM at fdd00000 [disabled] [size=128K]
> | 	Capabilities: <access denied>
> | 	Kernel driver in use: sky2
> `----
> 
> Bisecting shows 0bdb0bd01 as the first bad commit:
> 

Already reported. I am testing a fix. The hang is happening in synchronize_irq
in sky2_hw_all_down; but there are several other bugs that were introduced at the
same time.

      reply	other threads:[~2011-11-16 22:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-16 21:14 sky2 driver breaks reboot/shutdown Sven Joachim
2011-11-16 22:48 ` Stephen Hemminger [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=20111116144806.0b6e327f@nehalam.linuxnetplumber.net \
    --to=shemminger@vyatta.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=svenjoac@gmx.de \
    /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).