After a testing phase kernel 2.6.24.1 has been moved to Core where it replaces version 2.6.23.14.
Some of the most visible changes for users include: * more mac80211-based wireless drivers added * tickless support for x86_64 * uvesafb; support for ATI Xpress 200M and Mac framebuffers * ACPI usage in libata * SATA port multipliers support * NCQ support on MCP51/MCP55/MCP61 chipsets (add 'swncq=1' to the kernel boot commandline) * SDIO support * ability to use any kernel version to resume a hibernated system * read-only --bind mounts * tons of bugfixes and improvements
A detailed human-readable changelog is available at KernelNewbies Wiki: http://kernelnewbies.org/Linux_2_6_24
Attention! The kernel26-2.6.24.1-2 package includes an important security fix (local user privilege escalation). Everyone is encouraged to upgrade, especially on a system with ssh accounts.
söndag 10 februari 2008 skrev Roman Kyrylych:
After a testing phase kernel 2.6.24.1 has been moved to Core where it replaces version 2.6.23.14.
It still crashes at boot. I have investigated a little bit further.
Init comes to "Loading udev uevents" Then it crashes, with a register printout and stack trace, from process "udevtrigger" and says that it cannot find the /boot partition (on /dev/hda1), and comes into a kind of crippled single-user mode. Crippled, since the disk devices /hda1-3 are not populated in /dev
I have written down the stack trace, and every symbol is a kernel symbol, and not from udevtrigger, so it is a kind of partial kernel panic, but without panic, even though the system becomes unusable. EIP=sysfs_open_file+0x33/0x1a0
Under some conditions it does not crash, but then I find that my sound device is somehow not existing. It does not exist even in lspci anymore, which is strange, since should not every device, even unsupported, be listed by lspci? The device that does not exist anymore is: (from lspci) 00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60) I don't know if that means that everyone with that VIA chip will get the same problem.
So for me it is back to kernel 2.6.23.14
2008/2/11, Karolina Lindqvist karolina.lindqvist@kramnet.se:
söndag 10 februari 2008 skrev Roman Kyrylych:
After a testing phase kernel 2.6.24.1 has been moved to Core where it replaces version 2.6.23.14.
It still crashes at boot. I have investigated a little bit further.
I cannot remember bugreport number. Was it created already? I suggest to keep the progress on bugtracker because it's more convenient than ML. And also check bugzilla.kernel.org
On Feb 10, 2008 4:23 PM, Karolina Lindqvist karolina.lindqvist@kramnet.se wrote:
It still crashes at boot. I have investigated a little bit further.
Init comes to "Loading udev uevents" Then it crashes, with a register printout and stack trace,
This has nothing to do with the kernel. It is module related. Your best bet is to get a list of all your modules and slowly blacklist/whitelist them until you figure out which module is causing the issue.
måndag 11 februari 2008 skrev Aaron Griffin:
This has nothing to do with the kernel. It is module related. Your best bet is to get a list of all your modules and slowly blacklist/whitelist them until you figure out which module is causing the issue.
I throught the device driver modules were part of the kernel. Are they not?
On Feb 11, 2008 7:40 AM, Karolina Lindqvist karolina.lindqvist@kramnet.se wrote:
måndag 11 februari 2008 skrev Aaron Griffin:
This has nothing to do with the kernel. It is module related. Your best bet is to get a list of all your modules and slowly blacklist/whitelist them until you figure out which module is causing the issue.
I throught the device driver modules were part of the kernel. Are they not?
True, but we're splitting hairs. Put it this way - the bug wouldn't be reported to Linus, it would be reported to some guy who maintains the module that is failing. This is important info
arch-general@lists.archlinux.org