kern/111743: [ath] if_ath occasionally hangs system with certain broadcom AP chipsets

Bob Frazier bobf at mrp3.com
Mon Apr 23 17:10:14 UTC 2007


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

From: Bob Frazier <bobf at mrp3.com>
To: bug-followup at FreeBSD.org
Cc:  
Subject: Re: kern/111743: [ath] if_ath occasionally hangs system with certain
 broadcom AP chipsets
Date: Mon, 23 Apr 2007 09:42:41 -0700

 additional information:
 
 when in console mode (X11 not running) the following differences in bug behavior were noted:
 
 a) keyboard input would not work for login screens nor for 'logged in' shell; however, 
 the ALT+F# keys would still work to switch virtual screens, as well as caps lock and num 
 lock.
 
 b) when X11 is running, the mouse and keyboard do not function at all (including 
 CTRL+ALT+F# keys and CTRL+ALT+BACKSPACE)
 
 c) after removing the cardbus card for the atheros card, in either case the system truly 
 does 'hang'.
 
 
 This test was conducted using a new kernel build from source (6-STABLE), obtained via 
 cvsup on 4/21/2007
 
 
 Tests were also conducted while a USB serial device (uplcom driver) was loaded.  Here is 
 a typical 'kldstat' for this system, which should have been included in the original bug 
 report:
 
 Id Refs Address    Size     Name
   1   23 0xc0400000 71cd88   kernel
   2    1 0xc0b1d000 32e4     splash_bmp.ko
   3    1 0xc0b21000 4228     vesa.ko
   4    3 0xc0be6000 1c550    linux.ko
   5    1 0xc0c03000 6170     snd_via8233.ko
   6    2 0xc0c0a000 22c48    sound.ko
   7    1 0xc0c2d000 5ae18    acpi.ko
   8    1 0xc50ee000 6000     linprocfs.ko
   9    1 0xc5520000 2000     rtc.ko
 10    1 0xc5641000 4000     uplcom.ko
 11    1 0xc5645000 3000     ucom.ko
 12    1 0xc5d3c000 1b000    smbfs.ko
 13    2 0xc55de000 3000     libiconv.ko
 14    2 0xc55e4000 3000     libmchain.ko
 
 The bug was repeated with a 300N device functioning correctly at close range (3 feet 
 from the client).  It appeared in console mode after several successful scans, after 
 which the keyboard stopped responding.
 
 
 


More information about the freebsd-bugs mailing list