From: Guenther Thomsen <gthomsen@bluearc.com>
To: shemminger@osdl.org, "John W. Linville" <linville@redhat.com>
Cc: netdev@vger.kernel.org
Subject: kernel panic (on DHCP discover?) in sky2 driver of 2.6.17-rc1
Date: Wed, 12 Apr 2006 14:42:56 -0700 [thread overview]
Message-ID: <200604121442.56750.gthomsen@bluearc.com> (raw)
I'm happy to report, that the version of the sky2 driver in 2.6.17-rc1
yields line rate at low CPU utilization (as determined using ttcp).
Unfortunately, it's not quite bug-free yet ;-}
When enabling the second interface (of the same network controller) the
kernel panics (perhaps during DHCP discovery?):
--8<--
[root@penguin1 ~]# ifup eth1
Determining IP information for eth1...Unable to handle kernel paging
request at ffffc20000014000 RIP:
<ffffffff811a3329>{sky2_mac_init+522}
PGD 13fc49067 PUD 13fc4a067 PMD 13fc4b067 PTE 0
Oops: 0000 [1] SMP
CPU 3os linked in: autofs4 sr_mod cdrom dm_mod button usb_storage
uhci_hcd 11BladeRunner_sk98lin #1
RIP: 0010:[<ffffffff811a3329>] <ffffffff811a68 RCX: 000000000000001e
RDX: 0000000000004008 RSI: ffffc20000010000 11 0000000000000fe0 R12:
0000000000001000
R13: ffff81013fae61a8 R14:
S: 010 DS: 0000 ES: 0000 CR0:
000000008005003b
CR2: ffffc20000014000fe40)
Stack: 0000000000001000 ffff81013fae6000 ffff81013fae6500
00000f1013fae6000
Call Trace: <ffffffff811a3e0c>{sky2_up+334} <ffffffff81
<ffffffff81144cf4>{sprintf+144}
<ffffffff8123b616>{inet_ioctl{s_ioctl+44}
<ffffffff81085703>{sys_ioctl+107}
<ffffffff81009a2ac_init+522} RSP <ffff81013487fd28>
CR2: ffffc20000014000
<0>Kerne
-->8--
or (2nd try):
--8<--
[root@penguin1 ~]# Unable to handle kernel paging request at
ffffc20000014000 RIP:
<ffffffff811a3329>{sky2_mac_init+522}
PGD 13fc49067 PUD 13fc4a067 PMD 13fc4b067 PTE 0
Oops: 0000 [1] SMP
CPU 2
Modules linked in: autofs4 sr_mod cdrom dm_mod button usb_storage
uhci_hcd ehci_hcd e752x_edac edac_mc shpcR: 00:[<ffffffff811a3329>]
<ffffffff811a3329>{sky2_mac_init+522}
RDX: 0000000000004008 RSI: ffffc20000010000 RDI: 0000000000000000
R1 0000000001000
R13: ffff81013f0511a8 R14: 0000000000000001 R15: 0000S0000 CR0:
000000008005003b
CR2: ffffc20000014000 CR3: 000000013425b000000000001000 ffff81013f051000
ffff81013f051500 0000000000000000
Call Trace: <ffffffff811a3e0c>{sky2_up+334}
<ffffffff811fea04>{dev_op844cf4>{sprintf+144}
<ffffffff8123b616>{inet_ioctl+74}
<fffffffff81085703>{ys_ioctl+107}
<ffffffff81009ac8>{tracesys+209}
+} RSP <ffff81013534fd28>
CR2: ffffc20000014000
<0>Kernel panic - n
-->8--
The kernel is vanilla 2.6.17-rc1, the sky2 driver was compiled into the
kernel. OS is RedHat Fedora Core 4. The kernel was compiled using
gcc32.
The system is a Blade of a BladeRunner 4130 of Penguincomputing, it
contains two Xeon CPU (+ HT enabled) and an on-board 8062 network
controller of Marvell (88E8062 is stamped on the chip).
The hardware seems to work fine using 2.6.15(.7) with the sk98lin driver
version 8.31 of Syskonnect (skd.de).
Please let me know, if I can provide further information or assist in
any other way.
best regards
Guenther
next reply other threads:[~2006-04-12 21:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-12 21:42 Guenther Thomsen [this message]
2006-04-12 21:48 ` kernel panic (on DHCP discover?) in sky2 driver of 2.6.17-rc1 Stephen Hemminger
2006-04-12 22:26 ` Guenther Thomsen
2006-04-17 18:18 ` Stephen Hemminger
2006-04-26 0:06 ` sky2 driver problems in 2.6.17-rc2-git6 (was: Re: kernel panic (on DHCP discover?) in sky2 driver of 2.6.17-rc1) Guenther Thomsen
2006-04-26 16:44 ` Stephen Hemminger
2006-04-26 17:41 ` Guenther Thomsen
2006-05-16 19:11 ` kernel panic (on DHCP discover?) in sky2 driver of 2.6.17-rc1 Stephen Hemminger
-- strict thread matches above, loose matches on Subject: below --
2006-05-16 20:15 Guenther Thomsen
2006-06-04 4:05 Guenther Thomsen
2006-06-07 19:33 Guenther Thomsen
2006-06-07 19:44 ` Stephen Hemminger
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=200604121442.56750.gthomsen@bluearc.com \
--to=gthomsen@bluearc.com \
--cc=linville@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@osdl.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).