this is from his log:
Code:
<4>[ 4707.484356] notifier_call_chain 5 call=-5 tegra_dvfs_pm_notify+0x0/0x40 val=4
<4>[ 4707.484799] ------------[ cut here ]------------
<4>[ 4707.484830] WARNING: at include/linux/gfp.h:152 __alloc_pages_nodemask+0x58/0x658()
<4>[ 4707.484840] Modules linked in: bcm4329 texfat(P) tntfs(P) battery_rvsd(P)
<4>[ 4707.484897] [<c0048a04>] (unwind_backtrace+0x0/0xf0) from [<c007c4ec>] (warn_slowpath_common+0x4c/0x64)
<4>[ 4707.484919] [<c007c4ec>] (warn_slowpath_common+0x4c/0x64) from [<c007c51c>] (warn_slowpath_null+0x18/0x1c)
<4>[ 4707.484940] [<c007c51c>] (warn_slowpath_null+0x18/0x1c) from [<c00d27d8>] (__alloc_pages_nodemask+0x58/0x658)
<4>[ 4707.484961] [<c00d27d8>] (__alloc_pages_nodemask+0x58/0x658) from [<c007add0>] (copy_process+0xb8/0xdc0)
<4>[ 4707.484980] [<c007add0>] (copy_process+0xb8/0xdc0) from [<c007bbd8>] (do_fork+0x100/0x270)
<4>[ 4707.485004] [<c007bbd8>] (do_fork+0x100/0x270) from [<c0043898>] (kernel_thread+0x70/0x80)
<4>[ 4707.485023] [<c0043898>] (kernel_thread+0x70/0x80) from [<c0094890>] (kthreadd+0xac/0xf8)
<4>[ 4707.485040] [<c0094890>] (kthreadd+0xac/0xf8) from [<c0043698>] (kernel_thread_exit+0x0/0x8)
<4>[ 4707.485052] ---[ end trace 896a0ed708458bf6 ]---
<1>[ 4707.485137] Unable to handle kernel paging request at virtual address 08bd8054
<1>[ 4707.485148] pgd = c0004000
<1>[ 4707.485155] [08bd8054] *pgd=00000000
<0>[ 4707.485167] Internal error: Oops: 5 [#1] PREEMPT SMP
<0>[ 4707.485175] last sysfs file: /sys/devices/system/cpu/cpufreq/conservative/down_threshold
<4>[ 4707.485186] Modules linked in: bcm4329 texfat(P) tntfs(P) battery_rvsd(P)
<4>[ 4707.485206] CPU: 0 Tainted: P W (2.6.39.4 #1)
<4>[ 4707.485222] PC is at clk_disable_locked+0x14/0xa4
<4>[ 4707.485231] LR is at clk_disable+0x38/0x60
tegra_dvfs_pm_notify is a notifier routine of the Nvidia's SoC driver in the file dvfs.c. value=4 means POST_SUSPEND, i.e. waking up from sleep.
The warning was from the kernel because the memory allocation request (from the nvidia driver???) has bad parameters.
The kernel panic was triggered by a bad address presumably caused by memory trampling...