[Prism54-devel] [Bug 51] New: Erratic behaviour after working properly

[bugzilla-daemon@mcgrof.com]

http://prism54.org/cgi-bin/bugzilla/show_bug.cgi?id=51

           Summary: Erratic behaviour after working properly
           Product: prim54
           Version: 1.0.2.2
          Platform: ia32
        OS/Version: Linux 2.6
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Device Driver
        AssignedTo: prism54-devel@prism54.org
        ReportedBy: jelte.werkhoven@itfy.com


I've had my SMC cardbus card working happily under kernel 2.6.0, however, since 
upgrading to 2.6.1 and using the newest cvs patch (29/01/04) of the prism54 
module, I've had some strange stuff happening. First of all, the card tends to 
work at first startup; I can happily ad-hoc connect to my gateway ( this runs a 
rt2400 based card in ad-hoc mode ), and the connection is fine. However, after 
a while, the connection gets lost, and can't get restored in any way. After 
doing ifdown eth1; ifup eth1 the link light on the card lights up at first, and 
it looks like a connection has been made; the card in the gateway reports 
having successfully received a few packets. However after a few seconds the 
link light starts blinking and the connection is lost. If I do iwlist eth1 
scanning it does show the ad-hoc network my gateway is transmitting. It seems 
to me the card is sending but not receiving; in one situation today, just after 
I'd had a good connection all morning, I lost ping to my gateway but the link 
light was still burning. I checked what was happening on both machines with 
tcpdump and started both machines pinging each other. The laptop with the SMC 
card reported only its own outgoing ARP request, the gateway with the rt2400 
card was reporting its own outgoing ARP request and was receiving the request 
from the laptop, and sending a reply which, alas, didn't get received by the 
SMC card. 
 
Also I've had one or two hangs caused by the module; this is the message log 
for one: 
 
Jan 29 13:33:17 plankje kernel: eth1: islpci_open() 
Jan 29 13:33:17 plankje kernel: eth1: resetting device... 
Jan 29 13:33:17 plankje kernel: eth1: uploading firmware... 
Jan 29 13:33:17 plankje kernel: eth1: firmware uploaded done, now triggering 
reset... 
Jan 29 13:33:18 plankje kernel: eth1: firmware version 1.0.4.3 
Jan 29 13:33:19 plankje kernel: eth1: done with prism54_mib_init()! -- Client, 
Managed, Master mode 
Jan 29 13:33:21 plankje kernel: TRAP: oid 0x1, device 3, flags 0x0 length 4 
Jan 29 13:33:30 plankje kernel: eth1: no IPv6 routers present 
Jan 29 13:34:02 plankje kernel: _mgt_get_request(): data length (64!=1452) 
mismatch for oid=0x1c000043 
Jan 29 13:34:16 plankje kernel: _mgt_get_request(): data length (64!=1452) 
mismatch for oid=0x1c000043 
Jan 29 13:52:08 plankje -- MARK -- 
Jan 29 13:59:00 plankje /USR/SBIN/CRON[2144]: (root) CMD ( rm -f /var/spool/
cron/lastrun/cron.hourly)  
Jan 29 14:12:09 plankje -- MARK -- 
Jan 29 14:24:45 plankje kernel: _mgt_get_request(): data length (64!=1452) 
mismatch for oid=0x1c000043 
Jan 29 14:25:46 plankje kernel: eth1: islpci_close () 
Jan 29 14:26:00 plankje kernel: eth1: islpci_open() 
Jan 29 14:26:00 plankje kernel: eth1: resetting device... 
Jan 29 14:26:00 plankje kernel: eth1: uploading firmware... 
Jan 29 14:26:00 plankje kernel: eth1: firmware uploaded done, now triggering 
reset... 
Jan 29 14:26:01 plankje kernel: eth1: firmware version 1.0.4.3 
Jan 29 14:26:02 plankje kernel: eth1: done with prism54_mib_init()! -- Client, 
Managed, Master mode 
Jan 29 14:26:04 plankje kernel: TRAP: oid 0x1, device 3, flags 0x0 length 4 
Jan 29 14:26:13 plankje kernel: eth1: no IPv6 routers present 
Jan 29 14:52:09 plankje -- MARK -- 
Jan 29 14:59:00 plankje /USR/SBIN/CRON[2403]: (root) CMD ( rm -f /var/spool/
cron/lastrun/cron.hourly)  
Jan 29 15:05:59 plankje kernel: eth1: Out of memory, cannot handle oid 
0xe0070015 
Jan 29 15:05:59 plankje kernel: eth1: timeout waiting for mgmt response 1000, 
trigging device 
Jan 29 15:06:00 plankje kernel: eth1: timeout waiting for mgmt response 
Jan 29 15:06:05 plankje kernel: eth1: islpci_close () 
Jan 29 15:11:00 plankje syslogd 1.4.1: restart. 
 
 
The machine is a dell c600 running SuSE9.0 with a homemade 2.6.1 kernel. It has 
a second 3com NIC which is not wireless.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.