From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: Jeff Garzik <jgarzik@pobox.com>,
netdev@oss.sgi.com,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: [BUG] 2.6.3 + hp100 -> Oops
Date: Wed, 18 Feb 2004 12:15:59 -0800 [thread overview]
Message-ID: <20040218201559.GA31872@bougret.hpl.hp.com> (raw)
Hi,
Maybe it would be a good idea to fix or revert the hp100 patch
that went into 2.6.3 :
----------------------------------------------------------
# modprobe hp100
FATAL: Error inserting hp100 (/lib/modules/2.6.3/kernel/drivers/net/hp100.ko): No such device
# dmesg
[...]
hp100: Busmaster mode enabled.
hp100: at 0xf400, IRQ 16, PCI bus, 32k SRAM (rx/tx 75%).
hp100: Adapter is attached to 100Mb/s Voice Grade AnyLAN network.
# cat /proc/net/dev
Segmentation fault
# dmesg
[...]
hp100: Busmaster mode enabled.
hp100: at 0xf400, IRQ 16, PCI bus, 32k SRAM (rx/tx 75%).
hp100: Adapter is attached to 100Mb/s Voice Grade AnyLAN network.
Unable to handle kernel paging request at virtual address d086648c
printing eip:
d086648c
*pde = 0fda1067
*pte = 00000000
Oops: 0000 [#1]
CPU: 1
EIP: 0060:[<d086648c>] Not tainted
EFLAGS: 00010282
EIP is at 0xd086648c
eax: d086648c ebx: ccf6b000 ecx: fffffffd edx: cfb99000
esi: c139cca0 edi: ccf6b000 ebp: 000001be esp: c90b5f20
ds: 007b es: 007b ss: 0068
Process cat (pid: 511, threadinfo=c90b4000 task=c9080670)
Stack: c01ee394 ccf6b000 c139cca0 00000000 c01ee46d c139cca0 ccf6b000 c139cca0
00000000 ccf6b000 c0167d60 c139cca0 ccf6b000 00000000 c55888e0 c5588900
00000400 c139ccb8 00000000 00000003 00000000 00000002 00000000 c014cf1c
Call Trace:
[<c01ee394>] dev_seq_printf_stats+0x14/0x94
[<c01ee46d>] dev_seq_show+0x59/0x64
[<c0167d60>] seq_read+0x1bc/0x2fc
[<c014cf1c>] vfs_read+0x9c/0xcc
[<c014d0fd>] sys_read+0x31/0x4c
[<c0108c33>] syscall_call+0x7/0xb
Code: Bad EIP value.
---------------------------------------------------------------
After that, the whole system is mostly unusable and doesn't
reboot cleanly.
This is with a PCI card. Looking at the changes, they would
also require testing with a ISA card (which I don't have in my box at
the moment).
2.6.2 works perfectly. This is what 2.6.2 looks like :
---------------------------------------------
hp100: eth1: Busmaster mode enabled.
hp100: eth1: HP J2585B at 0xf400, IRQ 16, PCI bus, 32k SRAM (rx/tx 75%).
hp100: eth1: Adapter is attached to 100Mb/s Voice Grade AnyLAN network.
---------------------------------------------
Also :
-----------------------------------
00:12.0 Ethernet controller: Hewlett-Packard Company J2585B
Subsystem: Hewlett-Packard Company J2585B DeskDirect 10/100VG NIC
Flags: bus master, medium devsel, latency 64, IRQ 16
I/O ports at f400 [size=256]
Memory at fedfc000 (32-bit, non-prefetchable) [disabled] [size=8K]
-----------------------------------
Have fun...
Jean
next reply other threads:[~2004-02-18 20:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-18 20:15 Jean Tourrilhes [this message]
2004-02-18 20:26 ` [BUG] 2.6.3 + hp100 -> Oops Stephen Hemminger
2004-02-18 20:40 ` Stephen Hemminger
2004-02-18 22:16 ` Jean Tourrilhes
2004-02-18 22:40 ` 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=20040218201559.GA31872@bougret.hpl.hp.com \
--to=jt@bougret.hpl.hp.com \
--cc=jgarzik@pobox.com \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
/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).