Arch Linux

saleem

Member

Registered: 2011-09-21

Posts: 101

Re: Kernel Panic

If it solved from your POV go ahead. Just be aware that you are essentially running a partial upgrade now, and you should keep an eye on that bug, and reupdate glibc once this is considered fixed.

Thank you for the tip. Are such threads followed by the developers to fix reported bugs/problems? Indeed it's a partial fix since everytime I run pacman -Syu command I am being warned that glibc package is being held from upgrade and at some stage I have to remove the restriction imposed upon this package to upgrade to a new fixed version

seth

Member

Registered: 2012-09-03

Posts: 50,970

Re: Kernel Panic

You should follow https://bugs.archlinux.org/task/54240, BUT i686 support is being phased out and ends this fall. Realistically this won't fix anymore ever.

OOC: the bug speculates about a bug in SSE 4.2 code - what's the output of "lscpu" for you?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

saleem

Member

Registered: 2011-09-21

Posts: 101

Re: Kernel Panic

You should follow https://bugs.archlinux.org/task/54240, BUT i686 support is being phased out and ends this fall. Realistically this won't fix anymore ever.

OOC: the bug speculates about a bug in SSE 4.2 code - what's the output of "lscpu" for you?

Yes i686 support is dying but archlinux32.org is a hope that might let i686 survive. here is paste for my lscpu https://pastebin.com/cV89N5hZ

seth

Member

Registered: 2012-09-03

Posts: 50,970

Re: Kernel Panic

You do have sse 4.2 support (both, announced and "in theory" as this is a sandy bridge chip)

The bug description is a bit convoluted, but if this is a problem when running a 32bit virtual client on a 64bit host, this remains a problem for archlinux even across the drop of i686 support - let alone the multilib question (ie. if this is also a problem with 32bit process on a 64bit system)

btw, are you aware that the CPU is fully x86_64 capable?
https://wiki.archlinux.org/index.php/Mi … hitectures

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

saleem

Member

Registered: 2011-09-21

Posts: 101

Re: Kernel Panic

You do have sse 4.2 support (both, announced and "in theory" as this is a sandy bridge chip)

The bug description is a bit convoluted, but if this is a problem when running a 32bit virtual client on a 64bit host, this remains a problem for archlinux even across the drop of i686 support - let alone the multilib question (ie. if this is also a problem with 32bit process on a 64bit system)

btw, are you aware that the CPU is fully x86_64 capable?
https://wiki.archlinux.org/index.php/Mi … hitectures

Yes seth , I knew that but was too lazy to switch over to 64 . With little motivation I did migrated to 64 bit and also converted ext3 to ext4 file format for my root partition today, so my 2011 installation lives on with these new changes

Slacka

Member

Registered: 2017-03-13

Posts: 1

Re: Kernel Panic

I used a live iso and

# arch-chroot /mnt /bin/bash

to update my glibc to 2.25-3. This resolved my issue.

I have a Intel Duo Processor T2400, so don't really have the option of switching to x86-64. Hopefully ArchLinux32 will pan out.

saleem

Member

Registered: 2011-09-21

Posts: 101

Re: Kernel Panic

I used a live iso and

# arch-chroot /mnt /bin/bash

to update my glibc to 2.25-3. This resolved my issue.

I have a Intel Duo Processor T2400, so don't really have the option of switching to x86-64. Hopefully ArchLinux32 will pan out.

I have glibc locked up at 2.25-1 , so as you say glibc upgrade to 2.25-3 resolved your issue, I wonder if I should dare to upgrade mine as well?

saleem

Member

Registered: 2011-09-21

Posts: 101

Re: Kernel Panic

I used a live iso and

# arch-chroot /mnt /bin/bash

to update my glibc to 2.25-3. This resolved my issue.

I have a Intel Duo Processor T2400, so don't really have the option of switching to x86-64. Hopefully ArchLinux32 will pan out.

I have glibc locked up at 2.25-1 , so as you say glibc upgrade to 2.25-3 resolved your issue, I wonder if I should dare to upgrade mine as well?

Just checked now it`s core/glibc   2.25-1    --->   2.25-4 

wondering if I should upgrade?