From: Stephen Hemminger <shemminger@linux-foundation.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Sky2 Driver Issue
Date: Wed, 24 Oct 2007 21:41:31 -0700 [thread overview]
Message-ID: <20071024214131.50f36fee@freepuppy.rosehill> (raw)
In-Reply-To: <7b9198260710241106l1c24ef8cgbd56da60ba28122@mail.gmail.com>
On Wed, 24 Oct 2007 19:06:37 +0100
"Tom Spink" <tspink@gmail.com> wrote:
> On 24/10/2007, Tom Spink <tspink@gmail.com> wrote:
> > Hi,
> >
> > A couple of kernels ago, I ran into an issue with the sky2 driver.
> > Basically, I began getting repeated errors on my console of the
> > following:
> >
> > Oct 21 16:33:39 holly kernel: sky2 0000:04:00.0: error interrupt
> > status=0x80000000
> > Oct 21 16:33:39 holly kernel: sky2 0000:04:00.0: error interrupt
> > status=0xc0000000
> >
> > Which eventually led to:
> > Oct 21 16:33:49 holly kernel: printk: 92 messages suppressed.
> >
> > Here is a section of the log that may be useful:
> > Oct 21 16:33:37 holly kernel: sky2 eth1: enabling interface
> > Oct 21 16:33:38 holly dhclient: DHCPDISCOVER on eth1 to
> > 255.255.255.255 port 67 interval 8
> > Oct 21 16:33:39 holly kernel: sky2 0000:04:00.0: error interrupt
> > status=0x80000010
> > Oct 21 16:33:39 holly kernel: sky2 eth1: Link is up at 1000 Mbps, full
> > duplex, flow control both
> > Oct 21 16:33:39 holly kernel: sky2 0000:04:00.0: error interrupt
> > status=0x80000000
> > Oct 21 16:33:39 holly kernel: sky2 0000:04:00.0: error interrupt
> > status=0xc0000000
> > Oct 21 16:33:40 holly kernel: sky2 0000:04:00.0: error interrupt
> > status=0x80000000
> > Oct 21 16:33:40 holly kernel: sky2 0000:04:00.0: error interrupt
> > status=0xc0000000
> > Oct 21 16:33:41 holly kernel: sky2 0000:04:00.0: error interrupt
> > status=0x80000000
> > Oct 21 16:33:41 holly kernel: sky2 0000:04:00.0: error interrupt
> > status=0xc0000000
> > Oct 21 16:33:42 holly kernel: sky2 0000:04:00.0: error interrupt
> > status=0x80000000
> >
> > These messages are appearing on all the VTs, and because they keep
> > popping up, I can't reasonably use the consoles to test if the network
> > driver is working.
> >
> > The kernel I've got going at the moment is 2.6.23-rc9 with git
> > revision g804b3f9a, and it's fine. The error surfaced _sometime_
> > after this. Attached is my .config.
> >
> > I'll try rebooting and pinging the machine to see if the network
> > driver is working, and this is just (unnecessary?) spew from the
> > kernel.
> >
> > --
> > Regards,
> > Tom Spink
> > University of Edinburgh
> >
> >
>
> Hi again,
>
> So it seems the driver and the network card is functioning, but I'm
> getting the 'error interrupt' message plastered over every console.
>
> I can ping and ssh into the computer, but the message is still
> scrolling everything off my screens.
>
Your system is not supporting MMCONFIG access to allow driver to turn off
PCI express error value. It looks like the hw error irq mask doesn't work
as expected either.
What is your kernel config?
--
Stephen Hemminger <shemminger@linux-foundation.org>
next prev parent reply other threads:[~2007-10-25 4:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 17:58 Tom Spink
2007-10-24 18:06 ` Tom Spink
2007-10-25 4:41 ` Stephen Hemminger [this message]
2007-10-25 13:43 ` Tom Spink
2007-10-25 13:47 ` Tom Spink
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=20071024214131.50f36fee@freepuppy.rosehill \
--to=shemminger@linux-foundation.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®