Bug #226593 reported by balmy_fool on 2008-05-04
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Nominated for Hardy by Adam Porter
linux-firmware (Ubuntu)
Nominated for Hardy by Adam Porter
linux-meta (Ubuntu)
Nominated for Hardy by Adam Porter

Bug Description

Binary package hint: linux-backports-modules

Using Ubuntu Hardy.

The iwl4965 module does not respond to 'options iwl4965 debug=0x43fff' in /etc/modprobe.d/options. After getting a microcode error, nothing extra was reported in dmesg. Insmod is getting called correctly, so it would seem that debugging has somehow been disabled.

Debugging info is essential for this module, given the number of microcode errors this module has.

balmy_fool (balmy-fool) wrote :

/sys/module/iwl4965/parameters/debug has the correct value, so I can confirm that the module is getting called correctly. Something is wrong with the module itself, then.

balmy_fool (balmy-fool) wrote :

Debugging of the iwl* modules is still not enabled in the kernel. The various microcode errors that happen in these modules are nigh impossible to debug without the information reported with debugging enabled.

CONFIG_IWL3945_DEBUG and CONFIG_IWLWIFI_DEBUG should be enabled in the kernel.

balmy_fool (balmy-fool) wrote :

All right, what does it take to get a bug even looked at. I've pointed out the two relevant config options. Is there some reason why this issue is getting entirely ignored? Is there active opposition to being able to debug a flaky module? Do you all like having broken iwlwifi modules?

Please, enable CONFIG_IWL3945_DEBUG and CONFIG_IWLWIFI_DEBUG. I'm tired of having my computer crash daily and being stuck filing useless bug reports.

Wow, sorry for such a delayed response. I'll try to bring this to the attention of the kernel team for them to consider. Also, I'm going to close the "linux-firmware (Ubuntu)" and "linux-meta (Ubuntu) " tasks as this is correctly already open against the "linux (Ubuntu)" task. Thanks.

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
Changed in linux-firmware (Ubuntu):
status: New → Invalid
Changed in linux-meta (Ubuntu):
status: New → Invalid
tags: added: kconfig
summary: - iwl4965 does not report debug information
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Triaged a while ago but has not had any updated comments for quite some time. Please let us know if this issue remains in the current Ubuntu release, . If the issue remains, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-triage
Changed in linux (Ubuntu):
status: Triaged → Incomplete
Adam Porter (alphapapa) wrote :

Unless a developer has fixed this bug, it ought to remain. Please do not ask those who have already put time and effort into reporting and documenting this bug to waste their time re-testing code unless someone has actively attempted to fix it.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Jeremy Foshee (jeremyfoshee) wrote :

     updated fixes are applied daily in the kernel, so asking you to test an issue that you reported is not superfluous. It is in fact a major help to those who are actively trying to get fixes for a vast amount of hardware included in the kernel. It is also the method I am forced to use to determine if there has been a regression in code that may have been included in a previous update. I am sorry if this request impacts you, but the request was for the bug reporter.



Changed in linux (Ubuntu):
status: Confirmed → Incomplete
balmy_fool (balmy-fool) on 2010-03-14
Changed in linux (Ubuntu):
status: Incomplete → New
balmy_fool (balmy-fool) wrote :

I filed this bug two years ago. It took you guys a year to respond to it with promises of corrective action. It's taken you a year again to realize that you still haven't even checked it out yet.

I quit using Ubuntu because of this bug.

I have no intentions to check whether or not this bug is fixed. It's so trivial for a developer to check, that I don't see why a user has to do your work for you. Look at the kernel config. Is CONFIG_IWL3945_DEBUG set? Is CONFIG_IWLWIFI_DEBUG set? Done. Are you guys lazy, or merely incompetent?

Chase Douglas (chasedouglas) wrote :

We discussed this issue in a kernel team meeting and decided to leave the configuration as is. Turning on CONFIG_IWLWIFI_DEBUG adds size and lots of branching to the driver, which we don't want to do for the official kernel. I will be writing documentation soon on how to compile a special version of a driver for debugging purposes. It will be listed in the ubuntu kernel wiki page when it's done ( You would then be able to build your own module with debugging support. I hope this resolution is sufficient for you.

I'm assigning myself to the bug to handle the documentation.

Changed in linux (Ubuntu):
importance: Medium → Wishlist
assignee: nobody → Chase Douglas (chasedouglas)
status: New → Triaged
Changed in linux (Ubuntu):
assignee: Chase Douglas (chasedouglas) → nobody

> On Mon, Mar 15, 2010 at 12:38 PM, Chase Douglas <email address hidden> wrote:
>> I'm assigning myself to the bug to handle the documentation.

On Thu, Jun 7, 2012 at 5:59 PM, Chase Douglas <email address hidden> wrote:
> ** Changed in: linux (Ubuntu)
>     Assignee: Chase Douglas (chasedouglas) => (unassigned)

Does this mean documentation on building a debug enabled version of driver will not be provided or does it already exist somewhere?

Won't Fix as per As per , for debug technical support send email to <email address hidden> and cc <email address hidden> . If you have a bug in Ubuntu then you would want to file a new report via a terminal:
ubuntu-bug linux

Thank you for your understanding.

Helpful bug reporting tips:

Changed in linux (Ubuntu):
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers