Ubuntu hangs when MAC restrictions enabled on router

Bug #122774 reported by Marcin Gałązka on 2007-06-28
Affects Status Importance Assigned to Milestone
linux-source-2.6.20 (Ubuntu)

Bug Description

After enabling MAC Access Control on my home router (Gigabyte GN-BR01G) Ubuntu hangs while booting with message:

BUG: soft lockup detected on CPU#0!

It doesn't matter if MAC of my wireless card (GN-WP01GS) is present on access control list. Disabling MAC restrictions allows Ubuntu to boot successfully.

Ubuntu Feisty.

Paul Dufresne (paulduf) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

I believe that the message 'soft lockup detected on CPU#0!' means that one of your core have crashed, but because you have a dual core CPU, computer can
continue to work, but not exactly very well (may have others problems linked to this one).

Unfortunately we can't fix it, because your description doesn't yet have enough information.

Please include 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 "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 [WWW] http://wiki.ubuntu.com/KernelTeamBugPolicies. Thanks in advance!

Paul Dufresne (paulduf) wrote :

For uname and lspci it does not matter when you do it.
But for dmesg, you must wait after the 'soft lockup detected'.

Paul Dufresne (paulduf) wrote :

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!

Changed in linux-source-2.6.20:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers