[feisty] lockups - "ipw2200: Firmware error detected. Restarting."
Bug #116456 reported by
Elias K Gardner
This bug report is a duplicate of:
Bug #352150: ipw2200: Firmware error detected. Restarting // randomly disconnecting.
Edit
Remove
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
linux-restricted-modules-2.6.20 (Ubuntu) |
Won't Fix
|
Medium
|
Unassigned | ||
linux-ubuntu-modules-2.6.24 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I am now running a fresh install of ubuntu 7.04 I reinstalled after have an increasing number of lockups. I am experiencing two different kinds.
first a complete freeze where the mouse will not move and the system is completely unresponsive and requires a hard shutdown
second exactly the same except the mouse can move around the screen but not interact with anything
There is a thread http://
My most recent freeze occurred with the only applications I had manually started being firefox, terminal, and nautilus.
What must be done to discover the cause of these freezes?
Changed in linux-ubuntu-modules-2.6.24: | |
status: | New → Invalid |
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
To post a comment you must log in.
Thanks for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information. /wiki.ubuntu. com/KernelTeamB ugPolicies . Thanks in advance!
Please include as attachments the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command 'uname -a' in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' and attach the resulting file 'dmesg.log' to this bug report.
3. Please run the command 'sudo lspci -vvnn > lspci-vvnn.log' and attach the resulting file 'lspci-vvnn.log' to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at https:/