[arch-general] [signoff] kernel 2.6.32.4-1
Hi guys, bump to latest bugfix version. Please signoff both arches, greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa@archlinux.org
On 01/19/2010 12:42 AM, Tobias Powalowski wrote:
Hi guys, bump to latest bugfix version. Please signoff both arches,
greetings tpowa
After grub the first message i get is: Error binding control socket, seems udevd is already running. Everything else seems to work ok x86_64 Ignacio
Am 19.01.2010 17:17, schrieb Ignacio Galmarino:
On 01/19/2010 12:42 AM, Tobias Powalowski wrote:
Hi guys, bump to latest bugfix version. Please signoff both arches,
greetings tpowa
After grub the first message i get is:
Error binding control socket, seems udevd is already running.
Everything else seems to work ok
That is a (temporary) bug in mkinitcpio, which won't be solved until the next major mkinitcpio version, expected "soon". It doesn't harm anyone, just prints this message.
That is a (temporary) bug in mkinitcpio, which won't be solved until the next major mkinitcpio version, expected "soon". It doesn't harm anyone, just prints this message.
Sorry to hijack, but I cannot resist... I've been having great problems recently with any custom-built kernel, both vanilla and from abs. Kernels build fine, boot fine, but then I get something about control sockets at the udev stage and the system hangs failing to find my root partition. I have an older kernel+image(done with older version of mkinitcpio) with exact same .config which works fine though. Could you please elaborate on this 'bug' in mkinitcpio!? Maybe you know something that mighty fix this for me?! Tom
2010/1/20 Tom <uebershark@googlemail.com>:
That is a (temporary) bug in mkinitcpio, which won't be solved until the next major mkinitcpio version, expected "soon". It doesn't harm anyone, just prints this message.
Sorry to hijack, but I cannot resist... I've been having great problems recently with any custom-built kernel, both vanilla and from abs. Kernels build fine, boot fine, but then I get something about control sockets at the udev stage and the system hangs failing to find my root partition. I have an older kernel+image(done with older version of mkinitcpio) with exact same .config which works fine though.
Could you please elaborate on this 'bug' in mkinitcpio!? Maybe you know something that mighty fix this for me?!
Tom
http://bbs.archlinux.org/viewtopic.php?pid=689656#p689656 -- GPG/PGP ID: B42DDCAD
On 01/19/2010 08:42 AM, Tobias Powalowski wrote:
Hi guys, bump to latest bugfix version. Please signoff both arches,
greetings tpowa
signoff x86_64 -- Ionut
On 01/19/2010 12:42 AM, Tobias Powalowski wrote:
Hi guys, bump to latest bugfix version. Please signoff both arches,
greetings tpowa
Can't 'sign off', but kernel26 2.6.32.4-1 seems to be working fine on x86_64 with nvidia. I'll load it on my laptop and report back as well after testing the radeon setup. That should be the real test. Is the recommendation no early config for the radeon module?? -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On 01/19/2010 04:43 PM, David C. Rankin wrote:
On 01/19/2010 12:42 AM, Tobias Powalowski wrote:
Hi guys, bump to latest bugfix version. Please signoff both arches,
greetings tpowa
Can't 'sign off', but kernel26 2.6.32.4-1 seems to be working fine on x86_64 with nvidia. I'll load it on my laptop and report back as well after testing the radeon setup. That should be the real test.
Is the recommendation no early config for the radeon module??
Tobias, all, After further testing with kernel 2.6.32.4-1, I have found two bugs: (1) the kernel upgrade kills WindowMaker (2) the kernel upgrade kills VirtualBox It was ironic, because I was using WindowMaker when I installed the kernel and then on reboot, WindowMaker attempted to start and then crashed back to the login screen. After the upgrade I successfully rebuilt the kernel module for vb with vbox_build_module, then started vbox and it hung with a small dialog "spawning session". Let me know what information you want to see and I'll be happy to provide it or file a bug report. Thanks. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On Wed, 2010-01-20 at 10:51 -0600, David C. Rankin wrote:
On 01/19/2010 04:43 PM, David C. Rankin wrote:
On 01/19/2010 12:42 AM, Tobias Powalowski wrote:
Hi guys, bump to latest bugfix version. Please signoff both arches,
greetings tpowa
Can't 'sign off', but kernel26 2.6.32.4-1 seems to be working fine on x86_64 with nvidia. I'll load it on my laptop and report back as well after testing the radeon setup. That should be the real test.
Is the recommendation no early config for the radeon module??
Tobias, all,
After further testing with kernel 2.6.32.4-1, I have found two bugs:
(1) the kernel upgrade kills WindowMaker (2) the kernel upgrade kills VirtualBox
It was ironic, because I was using WindowMaker when I installed the kernel and then on reboot, WindowMaker attempted to start and then crashed back to the login screen. After the upgrade I successfully rebuilt the kernel module for vb with vbox_build_module, then started vbox and it hung with a small dialog "spawning session". Let me know what information you want to see and I'll be happy to provide it or file a bug report. Thanks.
I'm using kernel26-2.6.32-ice currently (its up to 2.6.32-4) and Virtualbox PUEL worked fine just moments ago. Its 1 am here, tomorrow I'll try with the stock kernel and see whether it doesn't work.
On 01/20/2010 11:51 AM, David C. Rankin wrote:
It was ironic, because I was using WindowMaker when I installed the kernel
Just a suggestion: I usually drop down to single user ("sudo telinit s") before I install major packages like a kernel. DR
On Wednesday 20 January 2010 22:21:19 David C. Rankin wrote:
On 01/19/2010 04:43 PM, David C. Rankin wrote: After further testing with kernel 2.6.32.4-1, I have found two bugs:
(1) the kernel upgrade kills WindowMaker (2) the kernel upgrade kills VirtualBox
even with 2.6.32.3, I had to recomile virtualbox module. I tried to start a VM and system froze solid and had to do hard reset. With a recompile, its working though. -- Shridhar
On 01/20/2010 11:28 AM, Shridhar Daithankar wrote:
On Wednesday 20 January 2010 22:21:19 David C. Rankin wrote:
On 01/19/2010 04:43 PM, David C. Rankin wrote: After further testing with kernel 2.6.32.4-1, I have found two bugs:
(1) the kernel upgrade kills WindowMaker (2) the kernel upgrade kills VirtualBox
even with 2.6.32.3, I had to recomile virtualbox module. I tried to start a VM and system froze solid and had to do hard reset. With a recompile, its working though.
Are you talking about recompile of the vbox module, that I just did, or are you talking about a kernel recompile? -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On Thursday 21 January 2010 00:50:22 David C. Rankin wrote:
On 01/20/2010 11:28 AM, Shridhar Daithankar wrote:
On Wednesday 20 January 2010 22:21:19 David C. Rankin wrote:
On 01/19/2010 04:43 PM, David C. Rankin wrote: After further testing with kernel 2.6.32.4-1, I have found two bugs:
(1) the kernel upgrade kills WindowMaker (2) the kernel upgrade kills VirtualBox
even with 2.6.32.3, I had to recomile virtualbox module. I tried to start a VM and system froze solid and had to do hard reset. With a recompile, its working though.
Are you talking about recompile of the vbox module, that I just did, or are you talking about a kernel recompile?
vbox module recompile. It fixed the issue on 2.6.32-3 but from your post it seems, it is not sufficient for 2.6.32-4. -- Shridhar
After further testing with kernel 2.6.32.4-1, I have found two bugs:
(1) the kernel upgrade kills WindowMaker (2) the kernel upgrade kills VirtualBox
even with 2.6.32.3, I had to recomile virtualbox module. I tried to start a VM and system froze solid and had to do hard reset. With a recompile, its working though.
Are you talking about recompile of the vbox module, that I just did, or are you talking about a kernel recompile?
vbox module recompile.
It fixed the issue on 2.6.32-3 but from your post it seems, it is not sufficient for 2.6.32-4.
It is working here with x86_64. I have updated _only_ the kernel, headers and firmware, after that I've rebuilt the vbox module and reboot. Everything is working as it should. It is clearly stated when you install virtualbox that you need to rebuild the vbox module after every kernel update, if before it was only needed after a kernel version change it was just luck. And I guess just rebuilding the module doesn't cut it, if it is already inserted you may have to rmmod it and modprobe it again, but to be safe I think it is better to reboot the machine.
On 20/01/10 16:51, David C. Rankin wrote:
Tobias, all,
After further testing with kernel 2.6.32.4-1, I have found two bugs:
(1) the kernel upgrade kills WindowMaker (2) the kernel upgrade kills VirtualBox
It was ironic, because I was using WindowMaker when I installed the kernel and then on reboot, WindowMaker attempted to start and then crashed back to the login screen. After the upgrade I successfully rebuilt the kernel module for vb with vbox_build_module, then started vbox and it hung with a small dialog "spawning session". Let me know what information you want to see and I'll be happy to provide it or file a bug report. Thanks.
I can't comment on the WindowMaker issue but the VirtualBox, at least the OSE version(virtualbox-ose 3.1.2-3) released today is fixed.
On 01/20/2010 11:28 AM, Nathan Wayde wrote:
On 20/01/10 16:51, David C. Rankin wrote:
Tobias, all,
After further testing with kernel 2.6.32.4-1, I have found two bugs:
(1) the kernel upgrade kills WindowMaker (2) the kernel upgrade kills VirtualBox
It was ironic, because I was using WindowMaker when I installed the kernel and then on reboot, WindowMaker attempted to start and then crashed back to the login screen. After the upgrade I successfully rebuilt the kernel module for vb with vbox_build_module, then started vbox and it hung with a small dialog "spawning session". Let me know what information you want to see and I'll be happy to provide it or file a bug report. Thanks.
I can't comment on the WindowMaker issue but the VirtualBox, at least the OSE version(virtualbox-ose 3.1.2-3) released today is fixed.
I'll check and report back. Thanks! -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On 01/20/2010 09:21 PM, David C. Rankin wrote:
On 01/20/2010 11:28 AM, Nathan Wayde wrote:
On 20/01/10 16:51, David C. Rankin wrote:
Tobias, all,
After further testing with kernel 2.6.32.4-1, I have found two bugs:
(1) the kernel upgrade kills WindowMaker (2) the kernel upgrade kills VirtualBox
It was ironic, because I was using WindowMaker when I installed the kernel and then on reboot, WindowMaker attempted to start and then crashed back to the login screen. After the upgrade I successfully rebuilt the kernel module for vb with vbox_build_module, then started vbox and it hung with a small dialog "spawning session". Let me know what information you want to see and I'll be happy to provide it or file a bug report. Thanks.
I can't comment on the WindowMaker issue but the VirtualBox, at least the OSE version(virtualbox-ose 3.1.2-3) released today is fixed.
I'll check and report back. Thanks!
windowmaker still wasn't rebuilt. eventually it will, maybe i'll do it later. -- Ionut
On 01/20/2010 10:51 AM, David C. Rankin wrote:
Tobias, all,
After further testing with kernel 2.6.32.4-1, I have found two bugs:
(1) the kernel upgrade kills WindowMaker (2) the kernel upgrade kills VirtualBox
It was ironic, because I was using WindowMaker when I installed the kernel and then on reboot, WindowMaker attempted to start and then crashed back to the login screen. After the upgrade I successfully rebuilt the kernel module for vb with vbox_build_module, then started vbox and it hung with a small dialog "spawning session". Let me know what information you want to see and I'll be happy to provide it or file a bug report. Thanks.
Add to the list of broken desktop/window managers: (3) Enlightenment (E17) broken with latest kernel The problem seems to be libpng and libjpg. The xsession-errors from windowmaker were: [13:26 alchemy:~] # cat /home/david/.xsession-errors wmaker: error while loading shared libraries: libpng12.so.0: cannot open shared object file: No such file or directory I created the link to libpng like: ln -s /usr/lib/libpng14.so.14.0.0 /usr/lib/libpng12.so.0 then on next wm start [13:32 alchemy:~] # cat /home/david/.xsession-errors wmaker: error while loading shared libraries: libjpeg.so.7: cannot open shared object file: No such file or directory I didn't catch the E17 .xsession-errors, but I suspect it is related. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On 01/20/2010 09:41 PM, David C. Rankin wrote:
On 01/20/2010 10:51 AM, David C. Rankin wrote:
Tobias, all,
After further testing with kernel 2.6.32.4-1, I have found two bugs:
(1) the kernel upgrade kills WindowMaker (2) the kernel upgrade kills VirtualBox
It was ironic, because I was using WindowMaker when I installed the kernel and then on reboot, WindowMaker attempted to start and then crashed back to the login screen. After the upgrade I successfully rebuilt the kernel module for vb with vbox_build_module, then started vbox and it hung with a small dialog "spawning session". Let me know what information you want to see and I'll be happy to provide it or file a bug report. Thanks.
Add to the list of broken desktop/window managers:
(3) Enlightenment (E17) broken with latest kernel
The problem seems to be libpng and libjpg. The xsession-errors from windowmaker were:
[13:26 alchemy:~] # cat /home/david/.xsession-errors wmaker: error while loading shared libraries: libpng12.so.0: cannot open shared object file: No such file or directory
I created the link to libpng like:
ln -s /usr/lib/libpng14.so.14.0.0 /usr/lib/libpng12.so.0
then on next wm start
[13:32 alchemy:~] # cat /home/david/.xsession-errors wmaker: error while loading shared libraries: libjpeg.so.7: cannot open shared object file: No such file or directory
I didn't catch the E17 .xsession-errors, but I suspect it is related.
packages for e17 wasn't rebuild. have patience or downgrade to extra/community and don't flood the email with useless problems. The rebuilding process is NOT FINISHED. -- Ionut
On 01/20/2010 01:44 PM, Ionut Biru wrote:
packages for e17 wasn't rebuild. have patience or downgrade to extra/community and don't flood the email with useless problems.
The rebuilding process is NOT FINISHED.
Sorry, those weren't complaints... Since I have blackbox, e16, e17, fluxbox, fvwm2 gnome, (the old) kdemod3, kde4, openbox, sawfish, xfce, and WindowMaker on the box, I was just checking to see which worked after the kernel update and providing feeback. Note to self: Premise responses following new kernel install with "These just may not have been rebuilt yet but ..." :p -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On Thu, Jan 21, 2010 at 01:19:44PM -0600, David C. Rankin wrote:
On 01/20/2010 01:44 PM, Ionut Biru wrote:
packages for e17 wasn't rebuild. have patience or downgrade to extra/community and don't flood the email with useless problems.
The rebuilding process is NOT FINISHED.
Sorry, those weren't complaints... Since I have blackbox, e16, e17, fluxbox, fvwm2 gnome, (the old) kdemod3, kde4, openbox, sawfish, xfce, and WindowMaker on the box, I was just checking to see which worked after the kernel update and providing feeback.
I'm guessing that none of those were broken because of the kernel update, but because of the unfinished libpng rebuild in testing. -- Byron Clark
On 01/21/2010 01:31 PM, Byron Clark wrote:
I'm guessing that none of those were broken because of the kernel update, but because of the unfinished libpng rebuild in testing.
100% Correct. The issues were libpng12 to libpng14 and libjpg. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On Tue, 2010-01-19 at 07:42 +0100, Tobias Powalowski wrote:
Hi guys, bump to latest bugfix version. Please signoff both arches,
greetings tpowa
Everything working perfectly as usual. 32bit kernel with nvidia kernel module.
Processes are still being randomly killed by oom-killer here even tho there's lots of free swap available, most of the time ksmserver which kills the kde session. It's been happening since updating to 2.6.32 series. The issue is discussed here (with patch): http://marc.info/?l=linux-kernel&m=126169821317492&w=4 Tobias Powalowski wrote:
Hi guys, bump to latest bugfix version. Please signoff both arches,
greetings tpowa
participants (15)
-
A Rojas
-
Byron Clark
-
David C. Rankin
-
David Rosenstrauch
-
Hussam Al-Tayeb
-
Ignacio Galmarino
-
Ionut Biru
-
Mauro Santos
-
Nathan Wayde
-
Ng Oon-Ee
-
Ray Rashif
-
Shridhar Daithankar
-
Thomas Bächler
-
Tobias Powalowski
-
Tom