Ubuntu
linux-restricted-modules-2.6.15 package

madwifi makes the system crash

Bug #45315 reported by Sven Herzberg on 2006-05-17

Affects		Status	Importance	Assigned to	Milestone
	Ubuntu	Invalid	Medium	Unassigned
	linux-restricted-modules-2.6.15 (Ubuntu)	Invalid	Medium	Unassigned

Bug Description

When using the ALL0281 wireless device with the madwifi driver, the computer gets unresponsive. It doesn't react to key presses and it doesn't answer ping probes (neither wireless nor over an ethernet connection). The system seems to be still running (as the syslog gets written further).

Revision history for this message

Sven Herzberg (herzi) wrote on 2006-05-17: /var/log/syslog

/var/log/syslog Edit (94.1 KiB, text/plain)

Here's my syslog for your reading

Revision history for this message

Sven Herzberg (herzi) wrote on 2006-05-17:

I think the interesting lines are these:
herzi@shaun:~$ grep ath0.\*reset syslog
Apr 10 06:15:32 shaun kernel: [ 4242.958734] ath0: stuck beacon; resetting (bmiss count 4)
Apr 10 06:15:32 shaun kernel: [ 4243.191672] ath0: ath_reset: unable to reset hardware: 'Hardware didn't respond as expected' (HAL status 3)
May 17 18:27:55 shaun kernel: [27631.123758] ath0: stuck beacon; resetting (bmiss count 4)
May 17 18:27:55 shaun kernel: [27631.356680] ath0: ath_reset: unable to reset hardware: 'Hardware didn't respond as expected' (HAL status 3)
herzi@shaun:~$

Revision history for this message

Basilio Kublik (sourcercito) wrote on 2007-09-19:

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Thanks in advance.

Changed in linux-restricted-modules-2.6.15:
assignee:	nobody → sourcercito
status:	New → Incomplete

Revision history for this message

Basilio Kublik (sourcercito) wrote on 2007-10-16:

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!