Hi, "BJörn Lindqvist" <bjourne@xxxxxxxxx> writes: > Hi, > > I have a 2.6.5-7 kernel and I sporadically get these kernel messages: > > kernel: Bad page state at free_hot_cold_page (in process 'beam', > page c1a95320) > kernel: flags:0x40020118 mapping:f401adc0 mapped:0 count:0 > private:0x00000000 > kernel: Backtrace: > kernel: Call Trace: > kernel: [<c01448ed>] bad_page+0x5d/0xa0 > kernel: [<c0144c20>] free_hot_cold_page+0x60/0xf0 > kernel: [<c014e3e2>] unmap_vmas+0x2f2/0x5c0 > kernel: [<c0150c8b>] exit_mmap+0x5b/0x180 > kernel: [<c011f115>] mmput+0x45/0x60 > kernel: [<c016909c>] flush_old_exec+0x18c/0x820 > kernel: [<c01855c7>] load_elf_binary+0x387/0x145c > kernel: [<c0141599>] generic_file_read+0x99/0xc0 > kernel: [<c011949e>] pgd_alloc+0xe/0x40 > kernel: [<c0168bd1>] search_binary_handler+0x61/0x200 > kernel: [<c016a16f>] do_execve+0x1cf/0x350 > kernel: [<c010663a>] sys_execve+0x2a/0x60 > kernel: [<c0107db9>] sysenter_past_esp+0x52/0x79 > kernel: > kernel: Trying to fix it up, but a reboot is needed > > I have googled around and it seems that the "Bad page state at > free_hot_cold_page" is quite common. But I haven't found any > satisfying explanation for it. The traceback and the flags, mapped, > count and private attributes are always the same which suggests that > this problem ought to be reproducible somehow. Could you try to reproduce this error with a more recent kernel version? The one you run is pretty old and it is not unlikely that this bug has already been fixed. Hannes -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
