| Author |
Message |
|
|
Post subject:
 Posted: Oct 05, 2008 - 04:55 PM
|
|
Joined: Dec 02, 2006
Posts: 1904
Status: Offline
|
|
|
slh wrote:
I'm sorry, but I had to revert that patch in 5.slh.10 again, as it was a serious regression on nforce3 and nforce4 chipsets.
Yes, my system's an nForce4 Ultra chipset, so that's where the bug got triggered. Thanks for the fast fix and will grab the latest kernel |
|
|
| |
|
|
|
 |
|
|
|
Post subject:
Posted: Oct 11, 2008 - 06:24 PM
|
|
Joined: Dec 09, 2006
Posts: 66
Status: Offline
|
|
first kernel upgrade on a thinkpad t60 since 2.6.25-series and i have the same problem when on ac no problem but when on battery no kernel of the 2.6.26-series boots ,screen just stays black and no harddisk activity .
i have now tried several 2.6.26-kernels up to 2.6.26-6.slh.1-sidux-686 all with problem the same problem . |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Nov 03, 2008 - 07:28 PM
|
|
Joined: Apr 30, 2008
Posts: 9
Status: Offline
|
|
Problems back with all 2.6.27 kernels, in other distros too (Mepis) both 64 bit and 32 bit.
Oh well, it still works after hitting the power button again, and sidux it still the best distro. The rest of my hardware works fine. |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Nov 03, 2008 - 09:56 PM
|
|
Joined: Nov 30, 2006
Posts: 3434
Location: Budapest
Status: Offline
|
|
The boot hang I had with some 2.6.27 kernels, not with this one now: 2.6.27-4.slh.2-sidux-686. I still have to upgrade to the newest kernel.
But some time ago I found something in the Ubuntu bugtracker (which is more a forum somehow, the thread is hilariously long). Initially I did Google searches for iwl3945 and 2.6.27, so I thought, the hangs had something to do with the wireless chip, and I also read that in the kernel start sequences are changing atm.
But now I found this message in the same thread. It reads
Quote:
Marking this fixed by:
linux (2.6.27-7.12) intrepid; urgency=low
[...]
* disable CONFIG_DYNAMIC_FTRACE due to possible memory corruption on
module unload
All Ubuntu bugtracker users report: no hang anymore after this config change.
Now: /boot/config-2.6.27-4.slh.2-sidux-686 reads in line 4026:
/boot/config-2.6.27-4.slh.2-sidux-686 wrote:
CONFIG_HAVE_DYNAMIC_FTRACE=y
This is the end of my knowledge, someone who really knows the kernel might explain if there can be/is a connection to the. hangs and the Ubuntu solution.
At least it is the only hint which came close to a reasoning what might cause that random hang on boot time with 2.6.27.
hubi |
_________________
Bonitas stultitiaque sodales sunt.
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Nov 03, 2008 - 10:57 PM
|
|
Joined: Nov 25, 2006
Posts: 2555
Status: Offline
|
|
| CONFIG_HAVE_DYNAMIC_FTRACE != CONFIG_DYNAMIC_FTRACE |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Nov 03, 2008 - 11:13 PM
|
|
Joined: Nov 30, 2006
Posts: 3434
Location: Budapest
Status: Offline
|
|
slh, I thought so but was not sure.
The funny thing is, I had that behaviour with early 2.6.27 kernels but at some stage this behaviour just disappeared. It might be confusing if one has only one kernel on the box after a fresh installation.
But it might also have been a bug which is/was not kernel related. I just cannot remember if I had boot hangs with 2.6.25 as well (I did not care to track it because the second boot always worked). It might have been solved by something else which was updated. And since the hang was so early there is no log entry anywhere.
Or maybe it is after suspend/resume. I had (maybe still have) problems to reboot or shutdown after suspend/resume. The box does not reboot and it does not shut down, so a 4 sec pressing of the powerbutton is the only way out. Maybe after such an action I had the boot hangs. But I am not in the mood to test it out, I don't think the HD likes it 
Module/driver issue I suppose, and I still think that iwl3945 might be the cause. But ... it's just a wild guess.
hubi |
_________________
Bonitas stultitiaque sodales sunt.
|
| |
|
|
|
|
|
|
