Kernel release status
The current -mm tree is 2.6.24-rc5-mm1. Recent changes to -mm include some significant device model changes; a number of subsystem trees have been dropped from this release due to patch conflicts.
The current stable 2.6 kernel is
2.6.23.10 2.6.23.11 2.6.23.12. The big patch is 2.6.23.10, released on
December 14, with several dozen fixes. The 2.6.23.11 (December 14) and
2.6.23.12 (December 18)
releases contain small fixes for problems caused by 2.6.23.10.
For older kernels: 2.6.22.15 was released on December 14 with quite a few fixes.
2.4.36-rc1 was released on
December 17 with a number of security-related fixes. The 2.4.35.5 release also contains
those fixes.
Posted Dec 20, 2007 5:22 UTC (Thu)
by ncm (guest, #165)
[Link] (2 responses)
Posted Dec 20, 2007 16:03 UTC (Thu)
by mingo (guest, #31122)
[Link] (1 responses)
Posted Dec 21, 2007 3:56 UTC (Fri)
by ncm (guest, #165)
[Link]
Oddly, the problem seems to have healed overnight, which is also
worrisome. I have had this failure before, but attributed it to
a corrupt tuxonice image; it always booted ok shortly afterward
with "noresume". This time it was booting cold, and the failure
was entirely repeatable (for a while, evidently).
On my Dell Latitude D620, with an Intel Core2 Duo dual-CPU, recent kernels (2.6.22.9, 2.6.23.10) hang during boot unless I add "nohz=off" to the boot line. (I built with CONFIG_NO_HZ and CONFIG_HIGH_RES_TIMERS on.) They stall after displaying
Boot freeze in NO_HZ
...
i2c-adapter i2c-3: unable to read EDID block
Switched to high resolution mode on CPU 1
Switched to high resolution mode on CPU 0
and (apparently) before
IP route cache hash table entries 32768 (order: 5, 131072 bytes)
please report this in bugzilla.kernel.org. (or if you have already, what is the bug#?)
Boot freeze in NO_HZ
9612.
Boot freeze in NO_HZ