2.6.12.1 problems I meet (please CC: me)

[Wang Jian <larkwang@gmail.com>]

Hi,

I use a customized kernel to do packets analysis. The analysis code is
linked into kernel. It will vmalloc() nearly 128M (a little less) when
initialized.

The original code runs on 2.6.10 and works fine. The platform is a
general P4 with 100M ethernet. The user space system is a 8M compressed
ramdisk image which is a 32M filesystem.

Now I want to make it work on 2.6.12+ and on Athlon64 platform, for
better driver and better CPU/NIC performance.

I have a P4 box (compilation bed, CB), a 2-way Athlon64 box (test bed,
TB).

The problems are:

1. I port the code directly to 2.6.12.1 on CB, and it compiles ok. But
during boot, the kernel boot with error "unknown bus type 0" and freeze.
Especially, it can't detect harddisk's partition table. I use "quiet" to
strip non-error message and hand copy error messages

unknown bus type 0.
...
<repeat for several times>
...
unknown bus type 0.
irq 15: nobody cared!
handlers:
[<c0252927>]  (ide_intr+0x0/0x146)
Disabling IRQ #15
irq 1: nobody cared!
handlers:
[<c021a79a>]  (i8042_interrupt+0x0/0x256)
Disabling IRQ #1

But the same configuration works fine for 2.6.10.


2. I compile kernel 2.6.12.1 for K7 on CB. Boot it on TB, the system
boot up execept that the analysis code can't vmalloc() the needed memory.

"allocation failed: out of vmalloc space - use vmalloc=<size> to increase size."

If I use vmalloc=256m in boot command line, then

initrd extends beyond end of memory (0x37fef716 > 0x30000000)
initrd extends beyond end of memory (0x37fef716 > 0x30000000)
Kernel panic - unsyncing: VFS: Unable to mount root fs on unknown-block
(1,0)

BTW: Is there any way that a 512M memory chunk can be alloc? The system
has a lot of memory (1G+) and can't be used. It's better to provide a
mechanism to alloc big chunk of memory for special purpose (they will
never be freed and will be used as a single big chunk)


-- 
Wang Jian

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/