NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: kern/52526: Panic on "ifconfig athn0 down"



The following reply was made to PR kern/52526; it has been noted by GNATS.

From: Andreas Gustafsson <gson%gson.org@localhost>
To: Masanobu SAITOH <msaitoh%execsw.org@localhost>
Cc: gnats-bugs%netbsd.org@localhost
Subject: Re: kern/52526: Panic on "ifconfig athn0 down"
Date: Fri, 14 Jun 2019 19:17:42 +0300

 Masanobu SAITOH wrote:
 >  Do you still have this problem?
 >  Some changes have been added to athn(4) since September 2017, so this problem might be fixed now.
 
 I'm not sure if it's still the same problem, but the driver is still
 causing panics.
 
 I re-tested with the same adapter but on a different system (amd64
 with ehci), using -current built from CVS source date
 2019.06.14.01.00.52.  The first time I ran my test script, the system
 rebooted.  If there were any messages on the console, they went by too
 fast to see them, and there was no kernel core dump, but I managed to
 fish out the console messages from dmesg after the reboot:
 
 [   751.004900] athn0 at uhub3 port 2
 [   752.483823] : Atheros AR9271
 [   752.483823] athn0: rev 1 (1T1R), ROM rev 15, address 48:5d:60:57:7d:4f
 [   752.879769] athn0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
 [   752.879769] athn0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
 [  2551.452330] panic: kernel diagnostic assertion "xfer->ux_status == USBD_CANCELLED || xfer->ux_status == USBD_TIMEOUT" failed: file "/tmp/bracket/build/2019.06.14.01.00.52-amd64-debug-baremetal/src/sys/dev/usb/ehci.c", line 1054 
 [  2551.452330] cpu0: Begin traceback...
 [  2551.452330] vpanic() at netbsd:vpanic+0x160
 [  2551.452330] stge_eeprom_wait.isra.4() at netbsd:stge_eeprom_wait.isra.4
 [  2551.452330] ehci_softintr() at netbsd:ehci_softintr+0x28b
 [  2551.452330] usb_soft_intr() at netbsd:usb_soft_intr+0x38
 [  2551.452330] softint_dispatch() at netbsd:softint_dispatch+0xf4
 [  2551.452330] DDB lost frame for netbsd:Xsoftintr+0x4f, trying 0xffffbb0050ea30f0
 [  2551.452330] Xsoftintr() at netbsd:Xsoftintr+0x4f
 [  2551.452330] --- interrupt ---
 [  2551.452330] ffffffffffffffff:
 [  2551.452330] cpu0: End traceback...
 
 [  2551.452330] dumping to dev 0,1 (offset=61361456, size=718638):
 [  2551.452330] dump [   1.0000000] Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
 [     1.000000] 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017,
 [     1.000000] 2018, 2019 The NetBSD Foundation, Inc.  All rights reserved.
 [     1.000000] Copyright (c) 1982, 1986, 1989, 1991, 1993
 [     1.000000] The Regents of the University of California.  All rights reserved.
 
 After the reboot, I ran the script several times more without a panic.
 I then ran some manual tests that included configuring the interface
 and starting dhcpcd on it, ran the script again, and it paniced again.
 
 The test script is as follows.  /etc/wpa_supplicant.conf contains
 a single "network" block with my WPA2 network's ssid and psk.
 
 iface=athn0
 wpa_supplicant -i $iface -c /etc/wpa_supplicant.conf >wpa_supplicant.log &
 wpa_supplicant_pid=$!
 echo pid $wpa_supplicant_pid
 #wpa_cli status
 # dhcpcd $iface
 ifconfig $iface 10.0.1.42 netmask 255.255.255.0
 #wpa_cli status
 ifconfig $iface
 ifconfig $iface up
 ifconfig $iface
 #wpa_cli status
 ping -n -c 20 10.0.1.1
 kill $wpa_supplicant_pid
 sleep 5
 ifconfig $iface
 ifconfig $iface down
 
 -- 
 Andreas Gustafsson, gson%gson.org@localhost
 


Home | Main Index | Thread Index | Old Index