kernel 2.6.24-23-generic crash when loading module atl1e

Bug #323572 reported by kaiszy
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Hi!

After updating the kernel from 2.6.24-19-generic to 2.6.24-23-generic i have to recompile the atl1e-Driver (Version 1.0.0.4). The i load the module with the command "modprobe atl1e". After enter the command the kernel crash with a kernel panic.

Best regards,
  Kai.

Revision history for this message
kaiszy (kai-szymanski) wrote :

Hello,

i made a screenshot from the crash while the system is booting with kernekl 2.6.24-23-generic with installed atl1e-Module. If i rename the module the system boots (but without nic). When i copy the module back and make a "modprobe atl1e" i get also the kernel panic.

CU,
   Kai.

Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you 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.
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://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks in advance!

Revision history for this message
kaiszy (kai-szymanski) wrote :

Hi!

Attached you will find the missing information. I can only give you a "dmesg" with not loaded module (otherwise the system crash as you can see in the screenshot ;).

Revision history for this message
kaiszy (kai-szymanski) wrote :
Revision history for this message
kaiszy (kai-szymanski) wrote :
Revision history for this message
kaiszy (kai-szymanski) wrote :

If you need further informations, please feel free to ask !

Best regards and thanks for your afford,

Kai.

Revision history for this message
kaiszy (kai-szymanski) wrote :

Ups...here the full lspci ;)

Changed in linux:
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

kaiszy, thank you for reporting this and helping make Ubuntu better. Hardy desktop reached EOL on May 12, 2011.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue on a supported release? If so, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in a supported release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

tags: added: hardy needs-upstream-testing
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.