Fwd: [Prism54-devel] [patch 0/6] [prism54 svn trunk] various fixes for prism54 svn

[Bob Beers]

---------- Forwarded message ----------
From: Bob Beers <bob.beers at gmail.com>
Date: May 22, 2005 12:34 PM
Subject: Re: [Prism54-devel] [patch 0/6] [prism54 svn trunk] various
fixes for prism54 svn
To: Jean-Baptiste Note <jean-baptiste.note at wanadoo.fr>


On 5/22/05, Jean-Baptiste Note <jean-baptiste.note at wanadoo.fr> wrote:
>
> Hello Bob,
>
> > Hello Jean-Baptiste!
> >  Before I got this latest change in place, I was running another test and I got
> >  the BUG in a trace!  Here it is, I hope it is useful.  This is the XG-601 with
> >  no shared IRQ.
> >
> > ------------[ cut here ]------------
> > kernel BUG at /home/bbeers/download/prism54/prism54-svn=20050516/ksrc/isl_38xx.c
> > :248!
> > invalid operand: 0000 [#1]
> > PREEMPT
> > Modules linked in: vhub wd1100 ip_nat_irc ip_nat_ftp ip_conntrack_irc ip_conntra
> > ck_ftp iptable_nat ip_conntrack iptable_filter ip_tables prism54 eepro100
> > CPU:    0
> > EIP:    0060:[<c4825f6c>]    Tainted: P      VLI
> > EFLAGS: 00010202   (2.6.10)
> > EIP is at isl38xx_in_queue+0x8c/0xc0 [prism54]
> > eax: 000000a6   ebx: c11cd000   ecx: 00000004   edx: 000000a6
> > esi: c11cd220   edi: 00000009   ebp: c3b7935c   esp: c0947bcc
> > ds: 007b   es: 007b   ss: 0068
> > Process ping (pid: 12772, threadinfo=c0946000 task=c0acb020)
> > Stack: c4829b87 c1640000 00000004 c11cd220 c1640000 00000000 c03baac8 c01188b4
> >        c11cd220 00000001 c0118663 c03baac8 00000046 00000040 c0a99580 c01186a5
> >        c3ce7b60 c012d025 c0103c6f c010265a c3ce7b60 c0ee69e0 00000000 00000040
> > Call Trace:
> >  [<c4829b87>] update_queues+0x27/0x110 [prism54]
> >  [<c01188b4>] tasklet_action+0x44/0x70
> >  [<c0118663>] __do_softirq+0x83/0x90
> >  [<c01186a5>] do_softirq+0x35/0x40
> >  [<c012d025>] irq_exit+0x35/0x40
> >  [<c0103c6f>] do_IRQ+0x1f/0x30
> >  [<c010265a>] common_interrupt+0x1a/0x20
> >  [<c02ab4ee>] ip_push_pending_frames+0x33e/0x440
> >  [<c02a0060>] netlink_broadcast+0x90/0x380
> >  [<c02c5631>] raw_sendmsg+0x321/0x470
> >  [<c02ce1fb>] inet_sendmsg+0x3b/0x50
> >  [<c02824f3>] sock_sendmsg+0xd3/0x100
> >  [<c0110b36>] __wake_up_common+0x36/0x70
> >  [<c0110b91>] __wake_up+0x21/0x50
> >  [<c01dfadd>] n_tty_receive_buf+0x17d/0xf40
> >  [<c01bc5ee>] copy_from_user+0x2e/0x60
> >  [<c01bc5ee>] copy_from_user+0x2e/0x60
> >  [<c0126be0>] autoremove_wake_function+0x0/0x40
> >  [<c0287c01>] verify_iovec+0x31/0x90
> >  [<c0283ce3>] sys_sendmsg+0x153/0x1b0
> > [<c01df1ec>] opost_block+0x9c/0x150
> >  [<c02ebc60>] schedule+0x1d0/0x530
> >  [<c01daf56>] tty_ldisc_deref+0x66/0x90
> >  [<c01dbefa>] tty_write+0x1ea/0x250
> >  [<c01e13b0>] write_chan+0x0/0x210
> >  [<c01bc5ee>] copy_from_user+0x2e/0x60
> >  [<c02840b2>] sys_socketcall+0x1a2/0x1c0
> >  [<c0102437>] syscall_call+0x7/0xb
> > Code: fa 08 7f 08 b8 08 00 00 00 29 d0 c3 0f 0b fe 00 80 d7 82 c4 eb ee 89 f6 8d
> >  bc 27 00 00 00 00 83 fa 04 7f 07 b8 04 00 00 00 eb de <0f> 0b f8 00 80 d7 82 c4
> >  eb ef 8d 76 00 8d bc 27 00 00 00 00 0f
> >  <7>CB drv Qs: [32032][31753][0][0][166][124]
> > CB dev Qs: [62][32028][31753][0][0][162]
> > Kernel panic - not syncing: Fatal exception in interrupt
> >  <7>CB drv Qs: [32032][31753][0][0][166][124]
> > CB dev Qs: [62][32029][31753][0][0][162]
> > CB drv Qs: [32032][31753][0][0][166][124]
> > CB dev Qs: [62][32030][31753][0][0][162]
> > CB drv Qs: [32032][31753][0][0][166][124]
> > CB dev Qs: [62][32031][31753][0][0][162]
> > CB drv Qs: [32032][31753][0][0][166][124]
> > CB dev Qs: [62][32032][31753][0][0][162]
> >
> > Then it rebooted.  I was pushing it pretty hard: ping flood on eth1,
> >  voip call on eth0, and downloading from the web to a wireless
> >  NAT'ed 802.11g station.
>
> It's really interesting ! -- device bug it seems to me, or very subtle
> hardware bug somewhere : what firmware version were you using ?

1.0.4.3

>
> Also, maybe others could be interested : can you forward this to the
> list, or do you give me authorization to reply on-list with this
> information ?

As you request, this reply is also sent to the list for all curious eyes.  I was
 replying only to the list earlier in this thread, but after a couple of times
 getting your replies off list, I thought I was perhaps breaking protocol, so
 I began replying only to you.  I am happy to continue the thread either
 way, I just want to help improve the driver.  I have a few different SBCs
 and 3 prism54 devices to test with.

-Bob
--