From: Stephen Hemminger <shemminger@osdl.org>
To: "David Arnold" <david@mantara.com>
Cc: netdev@vger.kernel.org
Subject: Re: skge driver oops
Date: Tue, 16 May 2006 14:17:50 -0700 [thread overview]
Message-ID: <20060516141750.5c773955@localhost.localdomain> (raw)
In-Reply-To: <861.1147397784@d.0x1.org>
On Fri, 12 May 2006 11:36:24 +1000
"David Arnold" <david@mantara.com> wrote:
> i've been getting semi-regular lockups on my machine over 2.6.16
> series. I recently attached a serial console in an attempt to capture
> an OOPS.
>
> i got one yesterday. it's copied manually from the console, but
> hopefully the values are all accurate. there was more that had scrolled
> off screen above this too (sorry).
>
> oops, lspci, uname -a, .config and dmesg below.
>
> any suggestions for further debugging would be great,
>
> thanks,
I tried reproducing this and can't seem to cause it.
Are you running anything special that could influence this?
bridging, VLAN's, bonding, netfilter, queueing disciplines,
tc filters, ...
What is the output of /proc/interrupts, perhaps the devices don't like
sharing IRQ?
next prev parent reply other threads:[~2006-05-16 21:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060511150952.4c2cde2e@localhost.localdomain>
2006-05-12 1:36 ` skge driver oops David Arnold
2006-05-12 15:53 ` Stephen Hemminger
2006-05-15 21:55 ` David Arnold
2006-05-16 21:42 ` David Arnold
2006-05-16 21:17 ` Stephen Hemminger [this message]
2006-05-17 9:32 Beschorner Daniel
2006-05-17 10:17 ` Krzysztof Oledzki
-- strict thread matches above, loose matches on Subject: below --
2006-05-22 18:38 Beschorner Daniel
2006-05-26 15:17 ` Stephen Hemminger
2006-07-22 22:28 ` Krzysztof Oledzki
2006-07-30 13:33 ` Krzysztof Oledzki
2006-05-29 17:54 Beschorner Daniel
2006-05-30 18:25 ` Stephen Hemminger
2006-05-31 11:05 Beschorner Daniel
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=20060516141750.5c773955@localhost.localdomain \
--to=shemminger@osdl.org \
--cc=david@mantara.com \
--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).