Dell Inspiron 2600 locks completely with Hardy and Ibex kernels
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
I am reporting a bug on my girlfriend's laptop that I'm currently borrowing to try to squash this bug. The problem is that on Gutsy, the machine worked great. After upgrading to Hardy, the machine started locking up at random. After a period of use, the machine will freeze. Reverting to the Gutsy kernel (2.6.22), the lockups are avoided completely. This problem has existed in every kernel I have tested since the Hardy release version of 2.6.24.
Recently, I had her try 2.6.27 from Ibex. The problem still exists, with a freeze at random. Now that I have this machine, I'd like to know what information to post or what types of things to try. This is a very serious bug, and the fact that a release is planned in a month that appears to still have this problem is pretty grave to me.
The only items of particular interest I think is a LinkSys wireless card that is using the TNET1130 driver via ndiswrapper. I haven't tried the machine without the wireless card in, but I believe that she has in the past.
Let me know what information I might want to provide. It appears as if nothing is written to any of the logfiles I've looked at after a crash, so I don't know how we're going to get to the bottom of this. I'm also not really convinced this is a bug with the Ubuntu kernel, and suspect it might be upstream. I don't know the best way to test that.
Hi Ryan,
Thanks for the bug report, lets see if we can try to get this resolved. You mention testing the latest kernel available for Intrepid. I suspect as you do that this might be a bug in the upstream kernel as well since we just rebased the Ubuntu kernel with upstream. If you would be intersted in testing the upstream kernel just to verify, try taking a look at the following:
https:/ /wiki.ubuntu. com/KernelTeam/ GitKernelBuild
Building the upstream kernel is obviously not something we expect you to know how to do so proceeding with doing this is completely voluntary and at your own comfort level. We appreciate all the help you can give. If you do happen to test the upstream kernel and can verify this is an issue upstream, it's likely we'll want to escalate this in an upstream bug report at bugzilla. kernel. org. The next step after that would likely be to perform a git bisect to try and narrow down the patch which is causing the regression. Again, this is competely at your own comfort level if you want to do this but will be extremely helpful to both us and upstream to narrow down this bug. Information regarding performing a git bisect can be found at:
http:// www.kernel. org/doc/ local/git- quick.html# bisect
You can perform the git bisect using the upstream kernel git tree or the Ubuntu kernel git tree. If you want to use the Ubuntu kernel git tree I'd suggest looking at the following:
https:/ /help.ubuntu. com/community/ Kernel/ Compile => discussing building the Ubuntu kernel /wiki.ubuntu. com/KernelGitGu ide => information regarding where to get the Ubuntu kernel git tree - You'll likely want to grab the Hardy git tree to reduce the number of bisections you'd need to perform.
https:/
Definitely let us know if you have any questions. I realize this might be a bit overwhelming with all this information I just gave you. But again, we really appreciate all the help you can provide. Thanks.