Hello Brian:
Although the system won't boot with the device plugged
in, the system doesn't initially lock up when I just
plug the USB NIC into the system.  It seems I have to
perform an action (e.g. launching a web browser) that
will ask the system to access the network.

It usually takes about 30 seconds to a minute for the
system to lock up in full GUI mode (i.e. run level 5)
after I plug in the USB NIC if I attempt to access the
network (by launching a web browser, attempting to
access the update manager, etc).

In the virtual terminal, I captured this log file
immediately after plugging in the USB device, but the
last two entries only displayed on the console vs.
getting captured in the txt file.  Here's what I
captured:

Apr 27 17:02:44 localhost gconfd (tdorris-5192):
Resolved address
"xml:readonly:/etc/gconf/gconf.xml.mandatory" to a
read-only configuration source at position 0
Apr 27 17:02:44 localhost gconfd (tdorris-5192):
Resolved address "xml:readwrite:/home/tdorris/.gconf"
to a writable configuration source at position 1
Apr 27 17:02:44 localhost gconfd (tdorris-5192):
Resolved address
"xml:readonly:/etc/gconf/gconf.xml.defaults" to a
read-only configuration source at position 2
Apr 27 17:02:44 localhost gconfd (tdorris-5192):
Resolved address
"xml:readonly:/var/lib/gconf/debian.defaults" to a
read-only configuration source at position 3
Apr 27 17:02:44 localhost gconfd (tdorris-5192):
Resolved address
"xml:readonly:/var/lib/gconf/defaults" to a read-only
configuration source at position 4
Apr 27 17:02:48 localhost kernel: [   86.216000] NET:
Registered protocol family 10
Apr 27 17:02:48 localhost kernel: [   86.216000] lo:
Disabled Privacy Extensions
Apr 27 17:02:48 localhost kernel: [   86.216000]
ADDRCONF(NETDEV_UP): eth0: link is not ready
Apr 27 17:02:56 localhost kernel: [   93.628000]
ondemand governor failed to load due to too long
transition latency
Apr 27 17:03:01 localhost gconfd (tdorris-5192):
Resolved address "xml:readwrite:/home/tdorris/.gconf"
to a writable configuration source at position 0
Apr 27 17:04:44 localhost kernel: [  199.360000] usb
1-1: new full speed USB device using uhci_hcd and
address 2
Apr 27 17:04:44 localhost kernel: [  199.512000] usb
1-1: configuration #1 chosen from 1 choice
Apr 27 17:04:45 localhost kernel: [  200.264000]
ubuntu/wireless/at76/at76c503.c: Atmel at76c50x USB
Wireless LAN Driver 0.14beta1 loading
Apr 27 17:04:45 localhost kernel: [  200.344000]
usbcore: registered new interface driver at76_usb
Apr 27 17:04:48 localhost kernel: [  202.624000] usb
1-1: reset full speed USB device using uhci_hcd and
address 2
Apr 27 17:04:48 localhost kernel: [  202.772000] usb
1-1: device firmware changed
Apr 27 17:04:48 localhost kernel: [  202.772000] usb
1-1: USB disconnect, address 2
Apr 27 17:04:48 localhost kernel: [  202.772000]
ubuntu/wireless/at76/at76c503.c: wlan0 disconnecting
Apr 27 17:04:48 localhost kernel: [  202.772000]
ubuntu/wireless/at76/at76c503.c: at76_usb disconnected
Apr 27 17:04:48 localhost kernel: [  202.884000] usb
1-1: new full speed USB device using uhci_hcd and
address 3
Apr 27 17:04:48 localhost kernel: [  203.036000] usb
1-1: configuration #1 chosen from 1 choice
Apr 27 17:04:48 localhost kernel: [  203.204000]
ubuntu/wireless/at76/at76c503.c: firmware version
1.101.4 #84 (fcs_len 4)
Apr 27 17:04:48 localhost kernel: [  203.204000]
ubuntu/wireless/at76/at76c503.c: device's MAC
00:0c:41:09:8c:84, regulatory domain FCC (U.S) (id 16)
Apr 27 17:04:48 localhost kernel: [  203.204000]
ubuntu/wireless/at76/at76c503.c: registered wlan0

Now, here's what was left out of the file I captured,
but was displayed on the console of the virtual
terminal:

[ 205.956000]ubuntu/wireless/at76/at76c503.c: 2522:
assertion dev->istate == INIT failed
[ 207.436000]ubuntu/wireless/at76/at76c503.c: 1784:
assertion dev->curr_bss == NULL failed

I went back to full GUI mode and started another tail
session of /var/log/messages and attempted to capture
another file.  I launched update manager, and about
10seconds later, the system locked up.  Here's what I
got:

Apr 27 17:09:35 localhost kernel: [  554.052000] USB
Mass Storage support registered.
Apr 27 17:09:40 localhost kernel: [  559.056000] scsi
2:0:0:0: Direct-Access     SanDisk  Cruzer Micro    
0.4  PQ: 0 ANSI: 2
Apr 27 17:09:40 localhost kernel: [  559.060000] SCSI
device sdb: 2001888 512-byte hdwr sectors (1025 MB)
Apr 27 17:09:40 localhost kernel: [  559.064000] sdb:
Write Protect is off
Apr 27 17:09:40 localhost kernel: [  559.076000] SCSI
device sdb: 2001888 512-byte hdwr sectors (1025 MB)
Apr 27 17:09:40 localhost kernel: [  559.076000] sdb:
Write Protect is off
Apr 27 17:09:40 localhost kernel: [  559.076000]  sdb:
sdb1
Apr 27 17:09:40 localhost kernel: [  559.084000] sd
2:0:0:0: Attached scsi removable disk sdb
Apr 27 17:09:40 localhost kernel: [  559.084000] sd
2:0:0:0: Attached scsi generic sg2 type 0
Apr 27 17:10:58 localhost kernel: [  637.180000] usb
1-2: USB disconnect, address 4
Apr 27 17:11:45 localhost kernel: [  684.024000] usb
1-1: new full speed USB device using uhci_hcd and
address 5
Apr 27 17:11:45 localhost kernel: [  684.176000] usb
1-1: configuration #1 chosen from 1 choice
Apr 27 17:11:48 localhost kernel: [  686.584000] usb
1-1: reset full speed USB device using uhci_hcd and
address 5
Apr 27 17:11:48 localhost kernel: [  686.732000] usb
1-1: device firmware changed
Apr 27 17:11:48 localhost kernel: [  686.732000] usb
1-1: USB disconnect, address 5
Apr 27 17:11:48 localhost kernel: [  686.732000]
ubuntu/wireless/at76/at76c503.c: wlan0 disconnecting
Apr 27 17:11:48 localhost kernel: [  686.732000]
ubuntu/wireless/at76/at76c503.c: at76_usb disconnected
Apr 27 17:11:48 localhost kernel: [  686.844000] usb
1-1: new full speed USB device using uhci_hcd and
address 6
Apr 27 17:11:48 localhost kernel: [  686.996000] usb
1-1: configuration #1 chosen from 1 choice
Apr 27 17:11:48 localhost kernel: [  687.188000]
ubuntu/wireless/at76/at76c503.c: firmware version
1.101.4 #84 (fcs_len 4)
Apr 27 17:11:48 localhost kernel: [  687.188000]
ubuntu/wireless/at76/at76c503.c: device's MAC
00:0c:41:09:8c:84, regulatory domain FCC (U.S) (id 16)
Apr 27 17:11:48 localhost kernel: [  687.188000]
ubuntu/wireless/at76/at76c503.c: registered wlan0


Then immediately the system locked up.

Anyway, I hope what I captured here can get you
pointed in the right direction.

Thanks in advance,

T. Dorris

--- Brian Murray <[EMAIL PROTECTED]> wrote:

> Thanks for taking the time to report this bug and
> helping to make Ubuntu
> better.  How quickly does the system lock up?  One
> way to get more
> information may be to log into a virtual terminal
> (Ctrl+Alt+F2) execute
> 'tail -f /var/log/messages' and then plug in the
> adapter.  If you can
> capture what is causing the crash a picture of the
> crash may be helpful.
> Thanks in advance.
> 
> ** Changed in: Ubuntu
>      Assignee: (unassigned) => Brian Murray
>        Status: Unconfirmed => Needs Info
> 
> -- 
> Linksys USB NIC prevents boot-up or locks system
> after plugging in after boot on Fiesty Fawn
> https://bugs.launchpad.net/bugs/109836
> You received this bug notification because you are a
> direct subscriber
> of the bug.
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam
protection around 
http://mail.yahoo.com 

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam
protection around 
http://mail.yahoo.com 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam
protection around 
http://mail.yahoo.com 

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com

-- 
Linksys USB NIC prevents boot-up or locks system after plugging in after boot 
on Fiesty Fawn
https://bugs.launchpad.net/bugs/109836
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to