You are not logged in.
hi,
I just updated to "kernel26 2.6.30.1-1". So I rebooted my system. After "grub", some lines of words showed up and the system rebooted itself again. Then "some lines of words"->reboot->"some lines of words"->reboot->"some lines of words"->reboot->"some lines of words"->reboot->..............
Could someone tell me why this took place and what i should do?
thx
Offline
Do you have the same problem with the fallback image?
Offline
Try to choose in grub loading menu the second line - fallback and when it will boot check your load log file
Offline
the same situation occured with the fallback as well. sorry for forgetting to mention that
Offline
It's pretty hard to diagnose without the content of the "some lines of words" you mention.
But my best bet atm is to boot with a livecd, mount and chroot your system. When chroot'ed check your /var/log/dmesg.log for any hints on what may be causing the error. Errors like this can sometimes be corrected by fiddling with mkinitcpio (adding modules/hooks) and rerunning mkinitcpio, other times it is better to simply downgrade kernel for the time being. But report back here with your findings before attempting this.
Follow the instructions for mounting a system after booting with a liveCD:
http://wiki.archlinux.org/index.php/Rei … stallation
You're not supposed to reinstall grub.
NB: If you just want to check your logs you can skip the chroot part and simply mount the partition containing the /var dir and look there.
Offline
same problem here, spontaneous reboots with 2.6.30.1, both regular and fallback image. i don't see any text scrolling by though, no log entries either, just an instant reboot after grub timeouts.
chrooting and reinstalling .30 was the only solution for me.
ᶘ ᵒᴥᵒᶅ
Offline
I think the problem is something to do with the update process. When I went from 2.6.29... to 2.6.30 I had lots of problems, mainly being pacman gone missing. Then I reinstalled Arch with 2.6.30 with no problems then now that I've updated to 2.6.30.1 I cant boot!
Offline
same problem here, spontaneous reboots with 2.6.30.1, both regular and fallback image. i don't see any text scrolling by though, no log entries either, just an instant reboot after grub timeouts.
chrooting and reinstalling .30 was the only solution for me.
And when this problem had appeared? Immediately after updating kernel to newer version or later?
As it was told above - booting from livecd is the only variant you can do
Offline
I have the same problem here - the computer wouldn't even start to boot with either the "default" or fallback image. The problem appeared after I upgraded the kernel. I now downgraded to the previous version and everything works again ...
Offline
I could confirm this on my x86_64 AMD Athlon X2 Dual Core. Other kernel update on i686 works.
i removed all framebuffer(vga) and quiet setting from bootparameter - i see nothing as output, the PC reboots immidiately.
Building a new initrd won't solve this. Downgrade to 2.6.30 works.
Have you the problem on a specific CARCH (here x86_64)?
And maybe on a special CPU Vendor (here AMD)
Offline
I can confirm this problem with the newest kernel package (2.6.30.1). The last message I see before the system reboots itself is "Decompressing Linux ...". My guess is that it somehow fails to decompress the kernel image. I copied back an older kernel image (vmlinuz26) to /boot and it works when I use that one. Rebuilding the ramdisk with mkinitcpio didn't solve the problem.
Offline
Please wrote something about your CARCH (i686, x86_64) and your CPU (Vendor, uname -a)
Offline
Please wrote something about your CARCH (i686, x86_64) and your CPU (Vendor, uname -a)
intel x86_64 here
ᶘ ᵒᴥᵒᶅ
Offline
That's the one causing the problem for me:
i686 Intel(R) Pentium(R) 4 CPU 3.40GHz GenuineIntel GNU/Linux
Offline
Ok, it's so nothing special for ex. AMD-CPUs or x86_64....
Myself have also other reports where 2.6.30.1 have no problems...
Offline
OK, I think I found it. The problem is not in the kernel package, but in the new version of xz-utils. The new "beta4" package seems to be defect. I downgraded to beta3, ran mkinitcpio again and now I have a perfectly booting kernel.
I didn't notice this before because I upgraded both xz-utils and the kernel at the same time.
Btw, this is on i686.
Offline
Ok, it's so nothing special for ex. AMD-CPUs or x86_64....
Myself have also other reports where 2.6.30.1 have no problems...
Yep, no problems to report with new kernel here (running x86_64).
oz
Offline
OK, I think I found it. The problem is not in the kernel package, but in the new version of xz-utils. The new "beta4" package seems to be defect. I downgraded to beta3, ran mkinitcpio again and now I have a perfectly booting kernel.
I didn't notice this before because I upgraded both xz-utils and the kernel at the same time.
i regenerated .30 with xz-utils beta4 and that works fine, haven't tried .30.1 with beta3 though..
ᶘ ᵒᴥᵒᶅ
Offline
OK, I think I found it. The problem is not in the kernel package, but in the new version of xz-utils. The new "beta4" package seems to be defect. I downgraded to beta3, ran mkinitcpio again and now I have a perfectly booting kernel.
Tested it here on x86_64, doesn't solve it.
I will rebuild the kernel26 package from abs-Tree myself (with xz-utils "beta3" installed) to see if i got
a difference.....
I will write a bugreport now, i think it's time for that.... although we have not many details for the report...
I post the Bugreport Number when finished...
Last edited by GerBra (2009-07-06 19:58:23)
Offline
Offline
These people with problems: could you please write your system details into the bugreport?
uname -a
RAM
Motherboard
GPU/Graphiccard
//edit: and probably the filesystem you use for / and /boot
Thanks
Last edited by GerBra (2009-07-06 21:33:33)
Offline
I had been having this "insta-reboot" problem with my custom Zen (2.6.31) kernel, and again, when I upgraded my custom vanilla kernel to 2.6.30.1. The first solution was to clear my compiler cache and module folders and compile the kernels again. That got me booting up.
The second solution was to move away from the JFS file system. Apparently, there must some kind of bug. I probably ought to report that. A mess of segfaulting would happen at boot. I moved over to Ext4.
Now, both of my custom kernels work great, and everything is behaving like it is supposed to.
Last edited by DevoidOfWindows (2009-07-06 21:28:31)
Offline
The second solution was to move away from the JFS file system. Apparently, there must some kind of bug. I probably ought to report that. A mess of segfaulting would happen at boot. I moved over to Ext4.
And the same on my PC. Using a free partition as seperate /boot (ext2) i could boot 2.6.30.1 without problems.
To the other with same problem: To help figure this mysteroius bug out: please post your system infs and your FS (where your /boot lives) into the bugreport. I bet, that not all of you have jfs....
Offline
thanks
"Decompressing Linux ..."
this is what i saw
Please wrote something about your CARCH (i686, x86_64) and your CPU (Vendor, uname -a)
i686 celeron 1.4G HP laptop
OK, I think I found it. The problem is not in the kernel package, but in the new version of xz-utils. The new "beta4" package seems to be defect. I downgraded to beta3, ran mkinitcpio again and now I have a perfectly booting kernel.
but i only upgraded the kernel, i think
Last edited by yjcong (2009-07-06 23:28:47)
Offline
Hmmm would this have anything to do with these messages I'm getting after a system update (I assume from mkinitcpio)
Mostly a whole lot of this:
Unrecognized file format '/lib/modules/2.6.30-ARCH/kernel/fs/quota/quota_v2.ko /lib/modules/2.6.30-ARCH/kernel/fs/quota/quota_v2.ko 644 0 0' line 433
Unrecognized file format '/lib/modules/2.6.30-ARCH/kernel/fs/reiserfs/reiserfs.ko /lib/modules/2.6.30-ARCH/kernel/fs/reiserfs/reiserfs.ko 644 0 0' line 435
Unrecognized file format '/lib/modules/2.6.30-ARCH/kernel/fs/smbfs/smbfs.ko /lib/modules/2.6.30-ARCH/kernel/fs/smbfs/smbfs.ko 644 0 0' line 437
Unrecognized file format '/lib/modules/2.6.30-ARCH/kernel/fs/squashfs/squashfs.ko /lib/modules/2.6.30-ARCH/kernel/fs/squashfs/squashfs.ko 644 0 0' line 439
Unrecognized file format '/lib/modules/2.6.30-ARCH/kernel/fs/udf/udf.ko /lib/modules/2.6.30-ARCH/kernel/fs/udf/udf.ko 644 0 0' line 441
Offline