Comment 34 for bug 1181777
Revision history for this message
| Pierre Schweitzer (pierre-jean-schweitzer) wrote | #34 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
This workaround unfortunately appear to totally break the network card in the VM making it unusable. TG3 driver (which is supposed to handle it) cannot properly communicate with it.
The kernel outputs the following lines:
Jul 30 13:32:03 carrier-commander kernel: [ 0.981658] tg3 0000:00:05.0: PCI INT B -> Link[LNKB] -> GSI 10 (level, high) -> IRQ 10
Jul 30 13:32:03 carrier-commander kernel: [ 0.981722] tg3 0000:00:05.0: setting latency timer to 64
Jul 30 13:32:03 carrier-commander kernel: [ 0.988207] tg3 0000:00:05.0: phy probe failed, err -19
Jul 30 13:32:03 carrier-commander kernel: [ 0.993954] tg3 0000:00:05.0: Problem fetching invariants of chip, aborting
Jul 30 13:32:03 carrier-commander kernel: [ 1.047883] tg3 0000:00:05.0: Refused to change power state, currently in D0
Jul 30 13:32:03 carrier-commander kernel: [ 1.047916] tg3 0000:00:05.0: PCI INT B disabled
The weird thing being this "-19" error, ie, -ENODEV.