Void's Forums

by **X11** » Tue Aug 31, 2004 3:53 am

I just applied the patch and everything for 2.6.9rc1 (was running 2.6.8.1) and compiled it, rebooted, all is working well.

However if i do this...
[x11@exeleven x11]$ uname -sr
Linux 2.6.8.1

Shouldnt it be 2.6.9rc1, or does it not change the reported version number with prepatches

by **Void Main** » Tue Aug 31, 2004 7:46 am

That version number comes from the Makefile in the root of the kernel source. Verify the one you used has the new VERSION, PATCHLEVEL, SUBLEVEL and EXTRAVERSION vars set properly. If it is set properly then you are probably not really booting your newly compiled kernel and are still booting your old one inadvertantly.

by **X11** » Tue Aug 31, 2004 7:46 am

Nevermind, 2.6.9rc1 kept doing this at random...
Basically I could be doing anything and the keybored would just die, couldnt do anything with it. All I could do is ssh into the system and check the logs, what I found has been pasted in below.

Should I report this? If yes, what do I do to report it?

Code: Select all: Aug 31 22:16:19 exeleven kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000000 Aug 31 22:16:19 exeleven kernel: printing eip: Aug 31 22:16:19 exeleven kernel: c013a742 Aug 31 22:16:19 exeleven kernel: *pde = 12bd6067 Aug 31 22:16:19 exeleven kernel: *pte = 00000000 Aug 31 22:16:19 exeleven kernel: Oops: 0000 [#1] Aug 31 22:16:19 exeleven kernel: Modules linked in: sd_mod ide_cd cdrom i810 nfsd exportfs lockd sunrpc ipv6 lp autofs e100 mii ohci1394 ieee1394 floppy sg scsi_mod parport_pc parport 8250 serial_core microcode ntfs nls_iso8859_1 nls_cp437 vfat fat ext3 jbd i810_audio ac97_codec soundcore thermal processor fan button battery asus_acpi ac intel_agp agpgart Aug 31 22:16:19 exeleven kernel: CPU: 0 Aug 31 22:16:19 exeleven kernel: EIP: 0060:[<c013a742>] Not tainted VLI Aug 31 22:16:19 exeleven kernel: EFLAGS: 00010002 (2.6.8.1) Aug 31 22:16:19 exeleven kernel: EIP is at kfree+0x32/0x70 Aug 31 22:16:19 exeleven kernel: eax: 003170e0 ebx: 00000000 ecx: 000000a2 edx: cbfe1e7c Aug 31 22:16:19 exeleven kernel: esi: d8b87d9a edi: 00000286 ebp: d8b5f9d0 esp: d7e87f10 Aug 31 22:16:19 exeleven kernel: ds: 007b es: 007b ss: 0068 Aug 31 22:16:19 exeleven kernel: Process events/0 (pid: 3, threadinfo=d7e86000 task=d7e80b70) Aug 31 22:16:19 exeleven kernel: Stack: c039f920 0000004a d62dd0a0 d8b73348 00000001 d8b5cbb0 d8b87d9a d62dd0a0 Aug 31 22:16:19 exeleven kernel: d8b5f963 d62dd0a0 d8b72720 00000005 00000000 d8b72884 d8b5f9db 00000212 Aug 31 22:16:19 exeleven kernel: c01277bd 00000000 d7e87f74 00000000 d7eb0818 d7e86000 d7eb0808 ffffffff Aug 31 22:16:19 exeleven kernel: Call Trace: Aug 31 22:16:19 exeleven kernel: [<d8b5cbb0>] ip_map_put+0x50/0x80 [sunrpc] Aug 31 22:16:19 exeleven kernel: [<d8b5f963>] cache_clean+0x143/0x1b0 [sunrpc] Aug 31 22:16:19 exeleven kernel: [<d8b5f9db>] do_cache_clean+0xb/0x40 [sunrpc] Aug 31 22:16:19 exeleven kernel: [<c01277bd>] worker_thread+0x1ad/0x250 Aug 31 22:16:19 exeleven kernel: [<c0117330>] default_wake_function+0x0/0x20 Aug 31 22:16:19 exeleven kernel: [<c0117330>] default_wake_function+0x0/0x20 Aug 31 22:16:19 exeleven kernel: [<c0127610>] worker_thread+0x0/0x250 Aug 31 22:16:19 exeleven kernel: [<c012b03a>] kthread+0xaa/0xb0 Aug 31 22:16:19 exeleven kernel: [<c012af90>] kthread+0x0/0xb0 Aug 31 22:16:19 exeleven kernel: [<c01042ad>] kernel_thread_helper+0x5/0x18 Aug 31 22:16:19 exeleven kernel: Code: 8b 74 24 18 89 5c 24 08 89 7c 24 10 85 f6 74 2a 9c 5f fa 8b 15 b0 cc 3a c0 8d 86 00 00 00 40 c1 e8 0c c1 e0 05 8b 54 02 18 8b 1a <8b> 03 3b 43 04 73 18 89 74 83 10 ff 03 57 9d 8b 5c 24 08 8b 74

by **X11** » Tue Aug 31, 2004 7:52 am

Code: Select all: Aug 31 22:04:26 exeleven kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000000 Aug 31 22:04:26 exeleven kernel: printing eip: Aug 31 22:04:26 exeleven kernel: c013a740 Aug 31 22:04:26 exeleven kernel: *pde = 01f9b067 Aug 31 22:04:26 exeleven kernel: *pte = 00000000 Aug 31 22:04:26 exeleven kernel: Oops: 0000 [#1] Aug 31 22:04:26 exeleven kernel: Modules linked in: nfsd exportfs lockd sunrpc sd_mod ide_cd cdrom ipv6 8250 serial_core lp autofs e100 mii ohci1394 ieee1394 floppy sg scsi_mod parport_pc parport microcode ntfs nls_iso8859_1 nls_cp437 vfat fat ext3 jbd i810_audio ac97_codec soundcore thermal processor fan button battery asus_acpi ac i810 intel_agp agpgart Aug 31 22:04:26 exeleven kernel: CPU: 0 Aug 31 22:04:26 exeleven kernel: EIP: 0060:[<c013a740>] Not tainted VLI Aug 31 22:04:26 exeleven kernel: EFLAGS: 00010002 (2.6.8.1) Aug 31 22:04:26 exeleven kernel: EIP is at kfree+0x30/0x70 Aug 31 22:04:26 exeleven kernel: eax: 00317b20 ebx: c5071aa0 ecx: 000000a2 edx: 00000000 Aug 31 22:04:26 exeleven kernel: esi: d8bd9d9a edi: 00000286 ebp: d8bb19d0 esp: d7e87f10 Aug 31 22:04:26 exeleven kernel: ds: 007b es: 007b ss: 0068 Aug 31 22:04:26 exeleven kernel: Process events/0 (pid: 3, threadinfo=d7e86000 task=d7e80b70) Aug 31 22:04:26 exeleven kernel: Stack: c039f920 0000079e c5071aa0 d8bc5348 00000001 d8baebb0 d8bd9d9a c5071aa0 Aug 31 22:04:26 exeleven kernel: d8bb1963 c5071aa0 d8bc4720 00000005 00000000 d8bc4884 d8bb19db 00000212 Aug 31 22:04:26 exeleven kernel: c01277bd 00000000 d7e87f74 00000000 d7eb0818 d7e86000 d7eb0808 ffffffff Aug 31 22:04:26 exeleven kernel: Call Trace: Aug 31 22:04:26 exeleven kernel: [<d8baebb0>] ip_map_put+0x50/0x80 [sunrpc] Aug 31 22:04:26 exeleven kernel: [<d8bb1963>] cache_clean+0x143/0x1b0 [sunrpc] Aug 31 22:04:26 exeleven kernel: [<d8bb19db>] do_cache_clean+0xb/0x40 [sunrpc] Aug 31 22:04:26 exeleven kernel: [<c01277bd>] worker_thread+0x1ad/0x250 Aug 31 22:04:26 exeleven kernel: [<c0117330>] default_wake_function+0x0/0x20 Aug 31 22:04:26 exeleven kernel: [<c0117330>] default_wake_function+0x0/0x20 Aug 31 22:04:26 exeleven kernel: [<c0127610>] worker_thread+0x0/0x250 Aug 31 22:04:26 exeleven kernel: [<c012b03a>] kthread+0xaa/0xb0 Aug 31 22:04:26 exeleven kernel: [<c012af90>] kthread+0x0/0xb0 Aug 31 22:04:26 exeleven kernel: [<c01042ad>] kernel_thread_helper+0x5/0x18 Aug 31 22:04:26 exeleven kernel: Code: 24 0c 8b 74 24 18 89 5c 24 08 89 7c 24 10 85 f6 74 2a 9c 5f fa 8b 15 b0 cc 3a c0 8d 86 00 00 00 40 c1 e8 0c c1 e0 05 8b 54 02 18 <8b> 1a 8b 03 3b 43 04 73 18 89 74 83 10 ff 03 57 9d 8b 5c 24 08 Aug 31 22:06:07 exeleven kernel: <7>atkbd.c: Keyboard on isa0060/serio0 reports too many keys pressed. Aug 31 22:06:20 exeleven kernel: [drm:i810_unlock] *ERROR* Process 2379 using kernel context 0 Aug 31 22:06:20 exeleven kernel: atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly. Aug 31 22:06:20 exeleven kernel: atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly.

Here is the first instance of the problem, and some keybored errors, I noticed the keyb died and ended up rebooting after restarting X, etc, so I just rebooted, and then it died again, so I checked /var/messeges (which is in relation the post above this one).

by **X11** » Tue Aug 31, 2004 7:56 am

I think ill just wait for 2.6.9 to come out, hehe.

by **X11** » Tue Aug 31, 2004 7:58 am

Void Main wrote:That version number comes from the Makefile in the root of the kernel source. Verify the one you used has the new VERSION, PATCHLEVEL, SUBLEVEL and EXTRAVERSION vars set properly. If it is set properly then you are probably not really booting your newly compiled kernel and are still booting your old one inadvertantly.

VERSION = 2
PATCHLEVEL = 6
SUBLEVEL = 8
EXTRAVERSION = .1

by **Void Main** » Tue Aug 31, 2004 8:30 am

X11 wrote:
Void Main wrote:That version number comes from the Makefile in the root of the kernel source. Verify the one you used has the new VERSION, PATCHLEVEL, SUBLEVEL and EXTRAVERSION vars set properly. If it is set properly then you are probably not really booting your newly compiled kernel and are still booting your old one inadvertantly.

VERSION = 2
PATCHLEVEL = 6
SUBLEVEL = 8
EXTRAVERSION = .1

You obviously didn't apply the patch properly or that would have changed to 2.6.9-rc1:

http://www.kernel.org/diff/diffview.cgi ... 1.bz2;z=16

by **X11** » Tue Aug 31, 2004 8:34 am

weird, explains a lot though... next step for me is to find out why it didnt patch, and i think ive worked that out.

by **X11** » Tue Aug 31, 2004 9:03 am

I tried patching again, still did this.

I untarred a fresh 2.6.8.1 and then patched that, and the makefile still claims its 2.6.8.1

by **Void Main** » Tue Aug 31, 2004 10:08 am

The patch is meant to be applied to 2.6.8. I just tried it on 2.6.8.1 and it rejected the Makefile change, but on 2.6.8 it patched just fine:

# cd /usr/src
# tar -xjf linux-2.6.8.tar.bz2
# cd linux-2.6.8
# bzcat ../patch-2.6.9-rc1.bz2 | patch -p1

by **X11** » Tue Aug 31, 2004 4:29 pm

Oh ok that makes sense, this time I think I will wait for 2.6.9 because by the time ive downloaded 2.6.8 so i can patch to 2.6.9rc1 a stable will be out with my luck.

by **Void Main** » Tue Aug 31, 2004 5:28 pm

It only took me about a minute to download both of them over our T3 line. :)

by **X11** » Tue Aug 31, 2004 8:09 pm

I need to hide a wireless router in my school so I can use theres.

by **Void Main** » Tue Aug 31, 2004 8:16 pm

Your school has a T3? I can't imagine why they would need such a fat pipe. Are you sure it's not a T1?

by **X11** » Tue Aug 31, 2004 8:27 pm

I dunno what they have.

I downloaded somthing from sourceforge at 400kbps once, the australian server, which was crazy.

Void's Forums

Linux Kernel 2.6.9rc1 biazzeity

Linux Kernel 2.6.9rc1 biazzeity

Who is online