Skip to contentSkip to conversation

Kernel 2.4.12 bug?

linux-lvm GCS 2 participants 8 messages Oct 20, 2001 – Oct 24, 2001

lore
Share & tools
lore

GCS

author
#0 lore raw

Hi!

Is there any known issues with kernel 2.4.12? My Debian Woody is complaining about lvm during startup, and drops an oops when swapp is turned off, and lvm is going to be deactivated. It is a paging error, eip seems to be trashed to 0x5a5a5a5a.

GCS

#1 lore raw
Quoted 6 lines · GCS

Hi!

Is there any known issues with kernel 2.4.12? My Debian Woody is complaining about lvm during startup, and drops an oops when swapp is turned off, and lvm is going to be deactivated. It is a paging error, eip seems to be trashed to 0x5a5a5a5a.

Not that I've seen. I'm running 2.4.12 ATM quite happily, LVM is a module rather than in the kernel though.

patrick

author
#2 lore raw

Hi,

Quoted 2 lines · Patrick Caulfield

Not that I've seen. I'm running 2.4.12 ATM quite happily, LVM is a module rather than in the kernel though.

My kernel is still complaining during vgscan, see the syslog:
lvm -- Module successfully initialized
invalidate: busy buffer
last message repeated 8 times

Also at reboot/halt I get:
printing eip:
c014c022

Oops: 0000
CPU:    0
EIP:    0010:[proc_match+18/56]    Tainted: P
EFLAGS: 00010206
eax: d9fc2609   ebx: 03   ecx: 03   edx: 5a5a5a5a
esi: d9fc2609   edi: d9fc260d   ebp: d65f7d18   esp: d65f7d10
ds: 0018   es: 0018   ss: 0018
Process vgchange (pid: 345, stackpage=d65f7000)

etc...

Eip points inside c014bf4c t meminfo_read_proc. I have even patched it to 2.4.13pre3, but I get the same result. What should I check out? With 2.4.9 everything works normaly.

Cheers, GCS

#3 lore raw
Quoted 6 lines · GCS

Hi,

Quoted 2 lines · Patrick Caulfield

Not that I've seen. I'm running 2.4.12 ATM quite happily, LVM is a module rather than in the kernel though.

My kernel is still complaining during vgscan, see the syslog:

Are you swapping onto the LV ? It seems that swapoff -a does not remove the LV from the list of swap partitions, so vgchange -an would either fail or pull the rug out from underneath the paging mechanism.

patrick

author
#4 lore raw
Quoted 3 lines · Patrick Caulfield

Are you swapping onto the LV ? It seems that swapoff -a does not remove the LV from the list of swap partitions, so vgchange -an would either fail or pull the rug out from underneath the paging mechanism.

Not at all. LVM is on a 61.5Gb IBM disk, and my swapp is on a standard
partition, on an other disk. Ok, it happens after I get 'swapp is turned off' message on the console. Thus if it is related to swapp, then it is a software bug somewhere, as my swapp is nothing to do with LVM. If you want, I can try my config without swapp. I mean remove it from fstab, reboot and see. Also, do you have an idea for the boot time problem: buffer is busy message? Thanks,
GCS

#5 lore raw
Quoted 9 lines · GCS
Quoted 3 lines · Patrick Caulfield

Are you swapping onto the LV ? It seems that swapoff -a does not remove the LV from the list of swap partitions, so vgchange -an would either fail or pull the rug out from underneath the paging mechanism.

Not at all. LVM is on a 61.5Gb IBM disk, and my swapp is on a standard
partition, on an other disk. Ok, it happens after I get 'swapp is turned off' message on the console. Thus if it is related to swapp, then it is a software bug somewhere, as my swapp is nothing to do with LVM. If you want, I can try my config without swapp. I mean remove it from fstab, reboot and see.

It was just a thought. I'd like to see more of the ksymoops output - I'm also worried by the "Tainted" flag in the extract you posted last time.

Quoted 1 line

Also, do you have an idea for the boot time problem: buffer is busy message?

I know it's harmless....

patrick

author
#6 lore raw
Quoted 2 lines · Patrick Caulfield

It was just a thought. I'd like to see more of the ksymoops output - I'm also worried by the "Tainted" flag in the extract you posted last time.

Ok, I will get a new one, as 2.4.13 is out. I cross my fingers to have this
bug fixed (if it is kernel related even). The tainted flag is set because the vfat module I think. Kernel says: no license, will taint the kernel (or similar to this).

GCS

#7 lore raw
Quoted 3 lines · GCS

The tainted flag is set because the
vfat module I think. Kernel says: no license, will taint the kernel (or similar to this).

Aha, I'd heard there were a few of those :-(

patrick