Subject: wi0: record read mismatch, rid=fd42, got=fd41
To: None <current-users@netbsd.org>
From: Kurt Schreiner <ks@ub.uni-mainz.de>
List: current-users
Date: 09/27/2004 15:48:44
Hi,

just got this panic from wi0: again using my (i386-)notebook running
NetBSD-current (cvs-upped some hours ago) as WLAN client where the 
"access-point" is an oldish alpha (multia) w/ a Lucent Orinoco-Gold Card
running NetBSD 1.6L. 

>From /var/log/messages on the failing notebook:

Sep 27 15:13:59 imega-bsd syslogd: restart
Sep 27 15:13:59 imega-bsd /netbsd: wi0: record read mismatch, rid=fd42, got=fd41
Sep 27 15:13:59 imega-bsd /netbsd: wi0: record read mismatch, rid=fdc1, got=fd42
Sep 27 15:13:59 imega-bsd /netbsd: panic: wi0: invalid channel 49170
Sep 27 15:14:00 imega-bsd /netbsd: 
Sep 27 15:14:00 imega-bsd /netbsd: syncing disks... wi0: record read mismatch, rid=fd42, got=fdc1
Sep 27 15:14:00 imega-bsd /netbsd: wi0: record read mismatch, rid=fdc1, got=fd42
Sep 27 15:14:00 imega-bsd /netbsd: panic: wi0: invalid channel 0
Sep 27 15:14:00 imega-bsd /netbsd: 
Sep 27 15:14:00 imega-bsd /netbsd: 
Sep 27 15:14:00 imega-bsd /netbsd: dumping to dev 0,1 offset 3575
Sep 27 15:14:00 imega-bsd /netbsd: dump 1022 1021 1020 1019 1018 1017 1016 1015 1014 1013 1012 1011

Does that ring any bells on what could be going wrong?

Here's the relevant part of dmesg and ifconfig from my notebook:

wi0 at pcmcia0 function 0: <TOSHIBA, Wireless LAN Card, Version 01.01, >
wi0: 802.11 address 00:02:2d:33:44:6a
wi0: using Lucent Embedded WaveLAN/IEEE
wi0: Lucent Firmware: Station (6.14.1)
wi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps

ifconfig wi0
wi0: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        ssid KEKS_at_Home-NetBSD nwkey *****
        powersave off
        bssid 00:02:2d:0e:cc:ec chan 10
        address: 00:02:2d:33:44:6a
        media: IEEE802.11 autoselect adhoc (DS2 adhoc)
        status: active
        inet 10.7.177.224 netmask 0xffffff00 broadcast 10.7.177.255

As there's a coredump (and kernel compiled w/ -g) I'm happy to provide further
information as needed to help debugging this problem...

-kurt