12.2 messed up with latest kernel update

with yast I just updated all packages for which a newer version existed.
I asked for a reboot due to kernel update.

after that it doesn’t boot any longer.
I can select the system with grub, but this immediately results in a screen with the following message (numers omitted):

WARNING: at /home/abuild/rpmbuild/BUILD/kernel-desktop-3-4-63/linux-3.4/arch/x86/kernel/smp.c:120 trigger_load_balane+0x1d3/0x280()
Hardware name: 1000H
Modules linked in:
Pid: 1, comm: swapper/0 Not tainted 3.4.63-2.44-desktop #1
Call Trace:
… try_stack_unwind…
… dump_trace_log_lvl…

a different try lead to a different screen:

kernel panic - not syncing: VFS: Unable to mount root fs on unknown block(0,0)
Pid:1, comm… (as above)

the rescue system on the disk can be booted and the partition can be mounted and accessed.
fsck says the partition is ok.
a parallell Win on the disk can be booted.

-> can that be repaired (how?), or do I have to perform a new install?

correction: the recovery mode on the disk as well leads to the kernel panic.

the disk can be accessed from recovery mode on the installation dvd

The rescue system on what “disk”?

Does your rescue system offer a facility to repair the installed system i.e. replace packages, or even run a system upgrade depending on whether “disk” refers to DVD installation media?

I made the kernel update this morning on my 12.2 system (using Apper) with no issue, except I had to run “update-bootloader --refresh” from my 12.3 system before it would reboot with Grub2. That’s only because I multiboot several openSUSE releases, and it shouldn’t affect your situation. If I hadn’t used Apper, I would have used YaST Online Update (YOU) to make the kernel update. Did you use YOU, if not then perhaps you should (next time)?

PS. Just seen your correction post after writing, so take that into account when reading this.

On 2013-11-01 15:06, suse paul wrote:
>
> correction: the recovery mode on the disk as well leads to the kernel
> panic.

In advanced option you should be able to boot the previous kernel.


Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

same behaviour for the previous kernel

On 2013-11-01 18:46, suse paul wrote:
>
> same behaviour for the previous kernel

Then you might do a “same version distribution upgrade”.
Boot from the 12.2 DVD, and choose “upgrade”.

Offline upgrade
method

After that, do careful updates. Verify that your repo list doesn’t
contain any factory or other version repositories.


Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)