I received that message from syslogd. Something about hot_cold_page. Try to fix the bug but a reboot is needed.

I rebooted and got the same message. Do you know what is it?

(Since I'm afraid that my lappy became too hot so I shutdown. )

I copy the last few lines of the syslog file here.

Feb 7 08:46:19 darkstar kernel: Bad page state at free_hot_cold_page (in process 'artsd', page c16d65e0)
Feb 7 08:46:19 darkstar kernel: flags:0x80000414 mapping:00000000 mapcount:0 count:0
Feb 7 08:46:19 darkstar kernel: Backtrace:
Feb 7 08:46:19 darkstar kernel: [<c0135e76>] bad_page+0x5c/0x92
Feb 7 08:46:19 darkstar kernel: [<c013653e>] free_hot_cold_page+0x5a/0xeb
Feb 7 08:46:19 darkstar kernel: [<c013e555>] zap_pte_range+0x164/0x1ea
Feb 7 08:46:19 darkstar kernel: [<c013e66c>] unmap_page_range+0x91/0xdf
Feb 7 08:46:19 darkstar kernel: [<c013e784>] unmap_vmas+0xca/0x187
Feb 7 08:46:19 darkstar kernel: [<c0141ce1>] unmap_region+0x7d/0xed
Feb 7 08:46:19 darkstar kernel: [<c0141f61>] do_munmap+0xd5/0xeb
Feb 7 08:46:19 darkstar kernel: [<c0141fb1>] sys_munmap+0x3a/0x55
Feb 7 08:46:19 darkstar kernel: [<c0102be1>] syscall_call+0x7/0xb
Feb 7 08:46:19 darkstar kernel: Trying to fix it up, but a reboot is needed


Do you guys know what is wrong and what should I do to fix it?

Thanks.

your problem seems to be described here:

http://lkml.org/lkml/2005/12/9/124

did you upgrade kernel or alsa recently?

I also read that someone fixed it by upgrading alsa to the development release of alsa 1.0.11rc3

perhaps posting your problem on the alsa mailing list would be another option...

tobyl

That's it. I've just install alsa and that's probably the case.
Thanks a lot, tobyl.