From: Pekka Pietikainen <pp@netppl.fi>
To: linux-kernel@vger.kernel.org
Subject: Re: REQ: BCM4400 network driver for 2.4.22
Date: Fri, 11 Jul 2003 23:04:30 +0300 [thread overview]
Message-ID: <20030711200430.GA13284@netppl.fi> (raw)
In-Reply-To: <20030711163345.GA23076@netppl.fi>
On Fri, Jul 11, 2003 at 07:33:45PM +0300, Pekka Pietikainen wrote:
> Here's a patch against the driver version in 2.5.73 for testing/comments,
> which fixes all the issues I know of in the driver. I'm writing this mail
> through the driver running on 2.4.x, so obviously at least basic
> functionality is working.
>
> I'm not too sure about the pointer tricks I do with skb->data
> in b44_rx(), but they seem to do the trick just fine ;)
Two kinds of oopses uncovered in a bit heavier
testing, one doesn't mention b44 anywhere but it's very likely caused by
something in the driver:
kernel BUG at slab.c:1228!
invalid operand: 0000
b44 ipt_TCPMSS ipt_tcpmss ipt_MASQUERADE iptable_nat ip_conntrack
parport_pc lp
parport iptable_filter ip_tables
autofs ppp_synctty ppp_async ppp_generic slhc
CPU: 0
EIP: 0060:[<c0137eb4>] Not tainted
EFLAGS: 00010046
EIP is at kmem_extra_free_checks [kernel] 0x64 (2.4.20-20.1.2013.nptl)
eax: 00000000 ebx: 00000000 ecx: 00000800 edx: 00000000
esi: dbe3f14c edi: dbe3e000 ebp: dbe3e000 esp: d9811dac
ds: 0068 es: 0068 ss: 0068
Process pppoe (pid: 6437, stackpage=d9811000)
Stack: dbe3e000 dbe3e000 dbe3e800 dbe3f14c c0138913 dffc56f0
dbe3f14c dbe3e000
0053aba0 dbe3e000 00000286 dbeb47c0 c013803b dffc56f0
dbe3e000 dbeef7e8
c01e9150 d9811ec8 c01ea263 dbe3e000 dbeef7e8 dbeef7e8
c01ea3ed dbeef7e8
Call Trace: [<c0138913>] kmem_cache_free_one [kernel] 0xf3 (0xd9811dbc)
[<c013803b>] kfree [kernel] 0x5b (0xd9811ddc)
[<c01e9150>] sock_rfree [kernel] 0x0 (0xd9811dec)
[<c01ea263>] kfree_skbmem [kernel] 0x13 (0xd9811df4)
[<c01ea3ed>] __kfree_skb [kernel] 0x12d (0xd9811e04)
[<c0243507>] packet_recvmsg [kernel] 0x127 (0xd9811e1c)
[<c01e6a08>] sock_recvmsg [kernel] 0x58 (0xd9811e4c)
[<c01e678c>] sockfd_lookup [kernel] 0x1c (0xd9811e80)
[<c01e7af4>] sys_recvfrom [kernel] 0xb4 (0xd9811e94)
[<c0182046>] normal_poll [kernel] 0x106 (0xd9811ee8)
[<c015197a>] poll_freewait [kernel] 0x3a (0xd9811f10)
[<c0138913>] kmem_cache_free_one [kernel] 0xf3 (0xd9811f24)
[<c01e7b97>] sys_recv [kernel] 0x37 (0xd9811f64)
[<c01e831a>] sys_socketcall [kernel] 0x15a (0xd9811f80)
[<c01097ff>] system_call [kernel] 0x33 (0xd9811fc0)
and also something that looked like an assertion failure in skb handling
in b44_rx, but couldn't see fully due to having a 80x25 terminal and
scrolling not working either...
That and 2.5.75 complains that irq are disabled in local_bh_enable(),
looks like the locking in b44_poll will need to be adjusted a bit.
Oh well, we're getting there ;)
--
Pekka Pietikainen
next prev parent reply other threads:[~2003-07-11 19:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-09 21:34 REQ: BCM4400 network driver for 2.4.22 Bas Mevissen
2003-07-09 22:05 ` Jeff Garzik
2003-07-11 16:33 ` Pekka Pietikainen
2003-07-11 16:58 ` Jeff Garzik
2003-07-11 20:04 ` Pekka Pietikainen [this message]
2003-07-12 3:24 ` David S. Miller
2003-07-14 20:12 ` Pekka Pietikainen
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=20030711200430.GA13284@netppl.fi \
--to=pp@netppl.fi \
--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;
as well as URLs for NNTP newsgroup(s).