Help after kernel recompile
 

Hello, I am using kernel 2.6.28-ARCH and I recompiled from the ABS repositories using directions in the wiki and a few posts found on the forums there. I added CONFIG_XEN=y because it is on an XEN vps and it would not boot at all before it would just give an elf error. Now it gets passed that and i get a screen full of ...well i cant read it so if someoen could tell me what i did wrong please that would be cool Not sure what i should even google out of this.

close blk: backend at /local/domain/0/backend/vbd/432/51712
close blk: backend at /local/domain/0/backend/vbd/432/51776
Linux version 2.6.28-ARCH (root@centos_pristine) (gcc version 4.3.3 (GCC) ) #1 SMP PREEMPT Fri Feb 20 10:26:01 UTC 2009
Command line: root=/dev/sda3 ro
KERNEL supported cpus:
Intel GenuineIntel
AMD AuthenticAMD
Centaur CentaurHauls
ACPI in unprivileged domain disabled
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 00000000000a0000 (usable)
Xen: 00000000000a0000 - 0000000000100000 (reserved)
Xen: 0000000000100000 - 0000000001644000 (usable)
Xen: 0000000001644000 - 0000000001747000 (reserved)
Xen: 0000000001747000 - 0000000020000000 (usable)
DMI not present or invalid.
last_pfn = 0x20000 max_arch_pfn = 0x3ffffffff
Scanning 2 areas for low memory corruption
modified physical RAM map:
modified: 0000000000000000 - 0000000000001000 (usable)
modified: 0000000000001000 - 0000000000006000 (reserved)
modified: 0000000000006000 - 0000000000008000 (usable)
modified: 0000000000008000 - 0000000000010000 (reserved)
modified: 0000000000010000 - 0000000000093000 (usable)
modified: 00000000000a0000 - 0000000000100000 (reserved)
modified: 0000000000100000 - 0000000001644000 (usable)
modified: 0000000001644000 - 0000000001747000 (reserved)
modified: 0000000001747000 - 0000000020000000 (usable)
init_memory_mapping: 0000000000000000-0000000020000000
last_map_addr: 20000000 end: 20000000
RAMDISK: 007aa000 - 01644000
(6 early reservations) ==> bootmem [0000000000 - 0020000000]
#0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
#1 [0000006000 - 0000008000] TRAMPOLINE ==> [0000006000 - 0000008000]
#2 [0001747000 - 0001756000] XEN PAGETABLES ==> [0001747000 - 0001756000]
#3 [0000200000 - 00007a998c] TEXT DATA BSS ==> [0000200000 - 00007a998c]
#4 [00007aa000 - 0001644000] RAMDISK ==> [00007aa000 - 0001644000]
#5 [0001756000 - 0001846000] PGTABLE ==> [0001756000 - 0001846000]
Zone PFN ranges:
DMA 0x00000000 -> 0x00001000
DMA32 0x00001000 -> 0x00100000
Normal 0x00100000 -> 0x00100000
Movable zoDentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
Scanning for low memory corruption every 60 seconds
Checking aperture...
No AGP bridge found
Memory: 492284k/524288k available (2702k kernel code, 1524k absent, 29884k reserved, 1227k data, 388k init)
SLUB: Genslabs=12, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
installing Xen timer for CPU 0
Calibrating delay loop (skipped), value calculated using timer frequency.. 3821.72 BogoMIPS (lpj=6365956)
Security Framework initialized
Mount-cache hash table entries: 256
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
CPU: Physical Processor ID: 1
CPU: Processor Core ID: 0
SMP alternatives: switching to UP code
Freeing SMP alternatives: 19k freed
BUG: scheduling while atomic: kthreadd/2/0x00000002
Modules linked in:
Pid: 2, comm: kthreadd Not tainted 2.6.28-ARCH #1
Call Trace:
BUG: unable to handle kernel paging request at ffff880801813780
IP: [<ffffffff8023c96b>] put_prev_task_fair+0x2b/0xf0
PGD 202067 PUD 0
Oops: 0000 [#1] PREEMPT SMP
last sysfs file:
CPU 0
Modules linked in:
Pid: 2, comm: kthreadd Not tainted 2.6.28-ARCH #1
RIP: e030:[<ffffffff8023c96b>] [<ffffffff8023c96b>] put_prev_task_fair+0x2b/0xf0
RSP: e02b:ffff88001f87df60 EFLAGS: 00010082
RAX: ffff88000184f780 RBX: ffffffff80696480 RCX: 0000000000000001
RDX: 00000000ffff8800 RSI: ffff88001f874630 RDI: ffff88000185b480
RBP: ffff88001f87df70 R08: ffff8800811c5000 R09: ffffffff80549a97
R10: 0000000000000000 R11: ffffffff8036d210 R12: ffff88001f874630
R13: ffff88000185b480 R14: 0000000000000001 R15: 0000000000000001
FS: 0000000000000000(0000) GS:ffffffff806cb000(0000) knlGS:0000000000000000
CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: ffff880801813780 CR3: 0000000000201000 CR4: 0000000000000660
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process kthreadd (pid: 2, threadinfo ffff88001f87e000, task ffff88001f874630)
Stack:
ffff88000185b480 ffff88001f874630 ffff88001f87e030 ffffffff8049cdd5
0000000000000000 0000000000000000 ffffffff80696480 ffff88001f874630
0000000000000000 ffff88001f874898 0000000000000000 0000000000000000
Call Trace:
Code: 55 48 89 f0 48 83 c0 38 48 89 e5 41 54 49 89 f4 53 74 2f 48 8b 40 d0 8b 4e 70 48 c7 c3 80 64 69 80 8b 50 1c 48 8b 05 55 c5 3c 00 <48> 8b 04 d0 48 03 58 08 85 c9 75 19 48 c7 83 c0 00 00 00 00 00
RIP [<ffffffff8023c96b>] put_prev_task_fair+0x2b/0xf0
RSP <ffff88001f87df60>
CR2: ffff880801813780
---[ end trace 4eaa2a86a8e2da22 ]---
note: kthreadd[2] exited with preempt_count 3

it's the line

BUG: scheduling while atomic: kthreadd/2/0x00000002

Scheduling while atomic tends to lead to race conditions or bad locks -- this also appears to be a fairly recent thing in the kernel (people only started reporting this in the last few versions). 2.6.24 is the earliest I've seen it -- can you jump back a few versions & try again?

I'm not a skilled kernel hacker, but someone mentioned they suspected it was in the slub allocator -- are you using slub or slab?