[solved] Update kernel26-2.6.22.4-2 with kernel26-2.6.22.5-1

Theoden · 2007-08-22 04:53:43

Doesn't solve all the problems. Mine boots to login - won't run entranced. When I log in - it sits at prompt for a few seconds - then kicks me back out to log in.

I can't reboot it at all - the system locks up. This kernel is completelt fubar.

--Theoden

STiAT · 2007-08-22 07:34:00

Heh, my systems also won't boot. But i don't have any proper arch install cd here either to repair.

Shot the bird for me the morning, at work and all 3 computers with this error.

shining · 2007-08-22 10:20:52

AndyRTR wrote:

this crc-problem had exist only for i686 in kernel26-2.6.22.4-2. it's fixed in kernel26-2.6.22.4-2.1! if your system cannot boot kernel26-2.6.22.4-2 - use another installed (suspend2-,ck-,mm-,custom-)kernel to boot or follow the shown way above with the install cd to rescue your system.

Yes, I suppose it's always a good idea to have two kernels installed. I'm glad I just recently switched to -mm and that it stopped hardlocking (I had to switch from ipw3945 to iwl3945), that saved me some time

In other distribs I like (mostly debian and ubuntu), this is not a problem though : each new kernel version is a new package, so the old ones always stay.
IIRC, one kernel package can also get upgraded with a minor revision, but with this system, it's easier to ensure there is always at least 2 kernel versions installed. No need to use a different branch.

STiAT · 2007-08-22 11:01:55

For everyone experiencing problems with the kernel version 2.6.22-3 and 2.6.22-4 (system not booting, kernel panics), the following can be done:

Use a arch install CD (in example, i used the arch Don't Panic base CD), and boot up your system. You can choose your favorite keyboard layout using the command "km" after booting.

Afterwards, mount your filesystems

mkdir /mnt/arch
mount /dev/sda5 /mnt/arch
mount /dev/sda1 /mnt/arch/boot

Note: Choose the devices according to your local filesystem setup.
If this is done, we need to use chroot, to make it our "current" system, but with the installer kernel.

cd /mnt/arch
chroot . /mnt/arch

Afterwards, if you do have any network connection (in example using the FTP install iso), you can update the kernel directly, using

pacman -Syu

Otherwhise, you'll have to install an old kernel version.

cd /var/cache/pacman/pkg
pacman -U ./kernel26-2.6.21.4-1.pkg.tar.gz

This will install the old kernel on your system. I've personally used the (also broken) 2.6.22.3-1 kernel, and used the fallback image to boot my system, which worked properly.

Afterwards, immediately update your system, to receive kernel26-2.6.22.4-2.1, which is the fixed version.
NOTE: Installing an old kernel version can, and will cause problems with sudo (due to libpam). Plase ensure your root password is not locked, so you can su to root when you rebooted.

Yours,
STiAT

Last edited by STiAT (2007-08-22 11:05:55)

lumiwa · 2007-08-22 11:20:38

If is crc well known problem on 686 system why are than so in rush to put kernel in the current? As I wrote before the kernel is not the same as Doom.

test1000 · 2007-08-22 16:58:35

This shows that atleast for important packages like the kernel, glibc, etcetc there SHOULD exist ABSOLUTE testing procedures and not just be up to maintainers who are "absolutely sure" they don't need to test the new packages since their "change didn't matter".

I think I heard Linus say something like this once... he ought to know.

Theoden · 2007-08-22 18:47:39

test1000 wrote:

This shows that atleast for important packages like the kernel, glibc, etcetc there SHOULD exist ABSOLUTE testing procedures and not just be up to maintainers who are "absolutely sure" they don't need to test the new packages since their "change didn't matter".
I think I heard Linus say something like this once... he ought to know.

I couldn't agree more! You know that the pkg released to current was absolutely NOT tested or they would have found it immediately. Someone just compiled it and released it to current.

That's the worst kind of Q&A. Hope they make some improvements in this.

--Theoden

kishd · 2007-08-22 20:38:49

I know that there is a problem with the new kernel for some users. However, for the time that I have been using ARCH it has been very rare for such strong criticism to come through. Criticism has generally been constructive and with a view to find solutions. Many arch users have more than one kernel installed and in this case it would have been trivial to boot up with another kernel and re-install the working kernel while waiting for a fix.(which usually comes quite quickly as opposed to many other distro's). Perhaps you should use this as a lesson to install another kernel to boot your machine in case of problems before upgrading the kernel.

braincenter · 2007-08-23 00:19:09

After using the Arch CD to re-install the kernel from /var/lib/cache pacman, I was able to boot the system.

Now I am having the following error:

sudo pacman -Syu
:: Synchronizing package databases...
 current is up to date
 extra is up to date
:: Starting full system upgrade...
error: could not open file /var/lib/pacman/extra//3ddesktop-0.2.9-2/desc: No such file or directory

Now what? Do I have to rebuild the pacman database? If yes, how to rebuild?

chilebiker · 2007-08-23 01:24:51

@braincenter
I had the same error, but tonight i was able to upgrade the system as usual without problems!

@all
These kind of errors happen every now and then (maybe every three to four months), but as they usually take only a couple of minutes to fix, I don't panic! Checking the logs, see what packages got updated the night before and downgrade the ones being most likely responsable for the error. In my opinion this is a very small price to pay for such a wonderful, bleeding edge distro!

nirvanix · 2007-08-23 04:46:41

Sorry kishd, but I disagree with you. ALL packages should be tested before being released to current, and one of this magnitude (the kernel!!!) should be thoroughly tested. As far as I'm concerned - current means it's tested. If it hasn't been tested, don't release it to current - put it in test where it belongs.
Just because Arch users are fairly savvy linux folks, doesn't mean they should have to experience this.
This does not mean that I don't appreciate the excellent work that the Arch devs have done in the past - I do, I do. But a thing like this can really give the Arch community a bad rep. Hopefully not too many people grabbed the bad kernel. Unfortunately I did.

Leigh · 2007-08-23 05:41:34

Well, I always assumed all the packages in "current" were tested packages. I seldom run into major problems that render my system unbootable, even so, I keep keep a backup just incase, which from time to time come in very handy! I'm kind of wondering just how many packages " not so critical ones" enter current ? was this just a fluke that an un-tested kernel went into current? If not, I would say, yikes, this sounds like a major breach of no-brainer stuff.

AndyRTR · 2007-08-23 05:51:22

just to let you know: the kernel pkg was tested and known to work on the maintainer's system. the corruption happened on our master server when uplaoding/copying it into the repo. we are not sure what exactly the reason is. first time this happened. we fixed it as soon as possible but some mirrors had the bad pkg already synced.

you can all be sure we try to test each pkg as best as we can do. especially the important ones. on the other side time is always limited and ArchLinux is known for fast updates. so we often push in minor updates without deep testing. sometimes we have to maintain software we personally do not use at all. so it might happen we run into upstream bugs being the first distribution to have the new version of a pkg. That's part of the Arch way.

Leigh · 2007-08-23 06:06:43

Thanks AndyRTR, I back read a number of times thinking I missed the actual cause of the bad kernel. It's reasurring it was a fluke kind of thing which makes sense. If importantant packages weren't tested, I'm sure my system wouldn't be as stable as it is, and has been, for some time now. I didn't mean to critisize in my previous post. I just found it odd to think the kernel might intentionally not have been tested.

Umfortunately, sometimes sh*t happens no matter how well prepared we are. *sigh*

I have a 2nd arch64 backup on a usb drive that I had intended to use to help test packages, but unfortunately I'm working 70 hours a week these days. *sigh*

shining · 2007-08-23 06:53:11

Hmm, what happened with md5sum stuff ?
I see that the corruption in kernel26-2.6.22.4-1 was detected by pacman (see first report of this thread).
But so what happened with kernel26-2.6.22.4-2 ?
Or is kernel26-2.6.22.4-2 exactly the same as the corrupted kernel26-2.6.22.4-1 , but with the md5sum updated ?

AndyRTR · 2007-08-23 07:12:16

-1 and -2 are different; 2.1 is only a rebuild to fix the broken upload: http://cvs.archlinux.org/cgi-bin/viewcv … ot=Current

shining · 2007-08-23 07:18:27

AndyRTR wrote:

-1 and -2 are different; 2.1 is only a rebuild to fix the broken upload: http://cvs.archlinux.org/cgi-bin/viewcv … ot=Current

Oh, indeed.
But I'm still wondering why pacman caught the corrupted -1 package, but not the -2 one.

nirvanix · 2007-08-23 16:57:33

Thanks for the update AndyRTR, that makes me feel more confident in Arch.

JaDa · 2007-08-23 19:37:52

I just updated
kernel26 2.6.22.5-1

it works fine

Theoden · 2007-08-24 03:03:00

JaDa wrote:

I just updated
kernel26 2.6.22.5-1
it works fine

Just updated - no fix here. My system still boots to a login - then when I log in - it kicks me back out to to the login - over and over again.

Enranced won't run - and when I try to reboot - CTRL-ALT-DEL - the system locks up - requiring a hard reset. NONE of this happened before the recent bad kernel upgrade.

I went back and reinstalled 2.6.22.3-1 - but now it won't work either. Something got so hosed no kernel will run but my ck kernel. This truly sux!

--Theoden

JaDa · 2007-08-24 03:12:13

@Theoden

it looks like you don't have a kernel problem, maybe a xserver problem.

log in to the terminal (command line mode)

then "startx"

if it doesn't start up

follow the wiki
http://wiki.archlinux.org/index.php/Xorg7#Introduction

Last edited by JaDa (2007-08-24 03:13:05)

Theoden · 2007-08-24 03:19:18

JaDa wrote:

@Theoden
it looks like you don't have a kernel problem, maybe a xserver problem.
log in to the terminal (command line mode)
then "startx"
if it doesn't start up
follow the wiki
http://wiki.archlinux.org/index.php/Xorg7#Introduction

Can't do it - when I log in - it kicks me back out - at the command console.

And why would everything work fine with my ck kernel? No - it's definately kernel related.

--Theoden

Last edited by Theoden (2007-08-24 03:22:55)

Theoden · 2007-08-24 04:14:05

Theoden wrote:

JaDa wrote:
@Theoden
it looks like you don't have a kernel problem, maybe a xserver problem.
log in to the terminal (command line mode)
then "startx"
if it doesn't start up
follow the wiki
http://wiki.archlinux.org/index.php/Xorg7#Introduction
Can't do it - when I log in - it kicks me back out - at the command console.
And why would everything work fine with my ck kernel? No - it's definately kernel related.
--Theoden

Flyspray bug report: FS#7886

--Theoden

AndyRTR · 2007-08-24 04:38:35

probably not a kernel issue. see comment in flyspray.

Theoden · 2007-08-27 17:16:12

AndyRTR wrote:

probably not a kernel issue. see comment in flyspray.

Yes it is a kernel issue:

http://bugs.archlinux.org/task/7886

1. The system is exactly the same regardless of which kernel I use - ck or default.
2. X is still exactly the same regardless of which kernel I use - ck or default.
3. Entranced is still exactly the same regardless of which kernel I use - ck or default.
4. acpid is still exactly the same regardless of which kernel I use - ck or default.
5. The login and initscripts are still exactly the same regardless of which kernel I use - ck or default.
6. The hardware is still exactly the same regardless of which kernel I use - ck or default.
7. NOTHING is different EXCEPT the kernel and of course the modules it includes.

In troubleshooting - I learned to always determine what is different - what changed - and then narrow down to the problem. When I do that - the kernel keeps coming up as the only thing. When I use the ck kernel everything works. When I use the default kernel - it doesn't. When I break the attempt to start entranced (it is itself loging in as root I believe), it fails with the default - but when I break the attempt to startup entranced - log in - and then run entranced - it works correctly with the default kernel.

I simply don't think the problem is X. It HAS to be kernel related!

Since most users seem to be alright now - this appears to have been dropped. But my system is still broken with the default kernel and nothing 'appears' to be happening. Initially, there were attempts after I filed the bug report - then they seem to have stopped.

Could someone 'please' try and fix this?

--Theoden

Last edited by Theoden (2007-08-27 17:17:14)

Arch Linux

#26 2007-08-22 04:53:43

Re: [solved] Update kernel26-2.6.22.4-2 with kernel26-2.6.22.5-1

#27 2007-08-22 07:34:00

Re: [solved] Update kernel26-2.6.22.4-2 with kernel26-2.6.22.5-1

#28 2007-08-22 10:20:52

Re: [solved] Update kernel26-2.6.22.4-2 with kernel26-2.6.22.5-1

#29 2007-08-22 11:01:55

Re: [solved] Update kernel26-2.6.22.4-2 with kernel26-2.6.22.5-1

#30 2007-08-22 11:20:38

Re: [solved] Update kernel26-2.6.22.4-2 with kernel26-2.6.22.5-1

#31 2007-08-22 16:58:35

Re: [solved] Update kernel26-2.6.22.4-2 with kernel26-2.6.22.5-1

#32 2007-08-22 18:47:39

Re: [solved] Update kernel26-2.6.22.4-2 with kernel26-2.6.22.5-1

#33 2007-08-22 20:38:49

Re: [solved] Update kernel26-2.6.22.4-2 with kernel26-2.6.22.5-1

#34 2007-08-23 00:19:09

Re: [solved] Update kernel26-2.6.22.4-2 with kernel26-2.6.22.5-1

#35 2007-08-23 01:24:51

Re: [solved] Update kernel26-2.6.22.4-2 with kernel26-2.6.22.5-1

#36 2007-08-23 04:46:41

Re: [solved] Update kernel26-2.6.22.4-2 with kernel26-2.6.22.5-1

#37 2007-08-23 05:41:34

Re: [solved] Update kernel26-2.6.22.4-2 with kernel26-2.6.22.5-1

#38 2007-08-23 05:51:22

Re: [solved] Update kernel26-2.6.22.4-2 with kernel26-2.6.22.5-1

#39 2007-08-23 06:06:43

Re: [solved] Update kernel26-2.6.22.4-2 with kernel26-2.6.22.5-1

#40 2007-08-23 06:53:11

Re: [solved] Update kernel26-2.6.22.4-2 with kernel26-2.6.22.5-1

#41 2007-08-23 07:12:16

Re: [solved] Update kernel26-2.6.22.4-2 with kernel26-2.6.22.5-1

#42 2007-08-23 07:18:27

Re: [solved] Update kernel26-2.6.22.4-2 with kernel26-2.6.22.5-1

#43 2007-08-23 16:57:33

Re: [solved] Update kernel26-2.6.22.4-2 with kernel26-2.6.22.5-1

#44 2007-08-23 19:37:52

Re: [solved] Update kernel26-2.6.22.4-2 with kernel26-2.6.22.5-1

#45 2007-08-24 03:03:00

Re: [solved] Update kernel26-2.6.22.4-2 with kernel26-2.6.22.5-1

#46 2007-08-24 03:12:13

Re: [solved] Update kernel26-2.6.22.4-2 with kernel26-2.6.22.5-1

#47 2007-08-24 03:19:18

Re: [solved] Update kernel26-2.6.22.4-2 with kernel26-2.6.22.5-1

#48 2007-08-24 04:14:05

Re: [solved] Update kernel26-2.6.22.4-2 with kernel26-2.6.22.5-1

#49 2007-08-24 04:38:35

Re: [solved] Update kernel26-2.6.22.4-2 with kernel26-2.6.22.5-1

#50 2007-08-27 17:16:12

Re: [solved] Update kernel26-2.6.22.4-2 with kernel26-2.6.22.5-1

Board footer