Originally Posted by freemangordon

Me too, even with the latest (buffer overrun) patch included.

@colin.stephane - it is your ramzswap module patch that is causing reboots, here is the backtrace

Code:

[  333.989776] CPU: 0    Not tainted  (2.6.28.10-power48 #1)
[  333.989807] PC is at reset_device+0x7c/0x1d8 [ramzswap]
[  333.989837] LR is at 0x0
[  333.989837] pc : [<bf33c238>]    lr : [<00000000>]    psr: 80000153
[  333.989837] sp : c9713d78  ip : 00000000  fp : c9713d9c
[  333.989868] r10: 00000000  r9 : 00000000  r8 : 00008000
[  333.989868] r7 : 00000000  r6 : c953aa00  r5 : c953aa00  r4 : 0e7c0000
[  333.989868] r3 : 00000000  r2 : 00000000  r1 : 00000000  r0 : c953aa00
[  333.989898] Flags: Nzcv  IRQs on  FIQs off  Mode SVC_32  ISA ARM  Segment user
[  333.989898] Control: 10c5387d  Table: 831bc018  DAC: 00000015
[  333.989898] Process insmod (pid: 1901, stack limit = 0xc97122e8)
[  333.989929] Stack: (0xc9713d78 to 0xc9714000)

[  333.990631] Backtrace: 
[  333.990631] [<bf33c1bc>] (reset_device+0x0/0x1d8 [ramzswap]) from [<bf33d6cc>] (ramzswap_ioctl_init_device+0x4e4/0x55c [ramzswap])
[  333.990661] [<bf33d1e8>] (ramzswap_ioctl_init_device+0x0/0x55c [ramzswap]) from [<bf3431fc>] (ramzswap_init+0x1fc/0x29c [ramzswap])
[  333.990692] [<bf343000>] (ramzswap_init+0x0/0x29c [ramzswap]) from [<c002c334>] (__exception_text_end+0x64/0x198)

stack trace removed by me.

@colin.stephane - Will you please test the kernel at least once before uploading a link here. It is not only to put some patches and to leave others with reflashing and reboot loops.

And BTW where is this patch? I mean .diff file.

Here is the kernel with leafpad crash fixed an working ramzswap module.