[Nexus S Q&A, Help & Troubleshooting] htj:
I've been running CM dailies for a while. A few weeks ago, i started getting tons of random reboots. I grabbed quite a few debugs, and if i'm reading it right, it seems like i have some memory errors that cause the reboots to happen. I tried a few formats and things, nothing seemed to help. I finally went back to stock, and have had no reboots for over a week.

So the questions are:

1) is there anything i can do to avoid the problem?

2) at boot, it says the kernel has option errors=panic. Can i easily turn that off w/o a recompile? Is that a good idea?

here's part of the last-kmsg that may be interesting:

[ 3868.222239] mmc0: error -110 during resume (card was removed?)

[ 3868.222769] fsa9480 7-0025: dev1: 0x0, dev2: 0x0

[ 3868.223166] wakeup wake lock: event2-364

[ 3868.223266] s3c-rtc s3c2410-rtc: rtc disabled, re-enabling

[ 3868.223467] [ wm8994_samsung.c (wm8994_resume,3113) ] ------WM8994 Revision = [3]-------

[ 3868.223773] PM: resume of devices complete after 1596.380 msecs

[ 3868.224134] Restarting tasks ... done.

Slept 56s418ms

Slept 56s418ms

[ 3868.236828] suspend: exit suspend, ret = 0 (2013-03-05 02:53:11.013550710 UTC)

[ 3868.238030] dai_active 0, IISMOD d0001c00, IISCON 8030c638

[ 3869.158603] mmcblk0: error -110 sending status command, retrying

[ 3869.159351] mmcblk0: error -110 sending status command, retrying

[ 3869.160035] mmcblk0: error -110 sending status command, aborting

[ 3869.160162] end_request: I/O error, dev mmcblk0, sector 2681264

[ 3869.160235] Buffer I/O error on device mmcblk0p2, logical block 203830

[ 3869.160354] lost page write due to I/O error on mmcblk0p2

[ 3869.163046] mmcblk0: error -110 sending status command, retrying

[ 3869.163779] mmcblk0: error -110 sending status command, retrying

[ 3869.164453] mmcblk0: error -110 sending status command, aborting

[ 3869.164575] end_request: I/O error, dev mmcblk0, sector 1071928

[ 3869.164705] end_request: I/O error, dev mmcblk0, sector 1071936

[ 3869.164774] end_request: I/O error, dev mmcblk0, sector 1071944

[ 3869.164893] end_request: I/O error, dev mmcblk0, sector 1071952

[ 3869.164961] end_request: I/O error, dev mmcblk0, sector 1071960

[ 3869.165081] end_request: I/O error, dev mmcblk0, sector 1071968

[ 3869.165148] end_request: I/O error, dev mmcblk0, sector 1071976

[ 3869.165267] end_request: I/O error, dev mmcblk0, sector 1071984

[ 3869.165372] Aborting journal on device mmcblk0p2-8.

[ 3869.166731] mmcblk0: error -110 sending status command, retrying

[ 3869.167414] mmcblk0: error -110 sending status command, retrying

[ 3869.168159] mmcblk0: error -110 sending status command, aborting

[ 3869.168230] end_request: I/O error, dev mmcblk0, sector 1055256

[ 3869.168353] Buffer I/O error on device mmcblk0p2, logical block 579

[ 3869.168420] lost page write due to I/O error on mmcblk0p2

[ 3869.168560] JBD2: I/O error detected when updating journal superblock for mmcblk0p2-8.

[ 3869.170927] journal commit I/O error

[ 3869.172122] mmcblk0: error -110 sending status command, retrying

[ 3869.172794] mmcblk0: error -110 sending status command, retrying

[ 3869.173514] mmcblk0: error -110 sending status command, aborting

[ 3869.173589] end_request: I/O error, dev mmcblk0, sector 1050624

[ 3869.173710] Buffer I/O error on device mmcblk0p2, logical block 0

[ 3869.173777] lost page write due to I/O error on mmcblk0p2

[ 3869.180609] EXT4-fs error (device mmcblk0p2): ext4_journal_start_sb:296: Detected aborted journal

[ 3869.182200] EXT4-fs (mmcblk0p2): Remounting filesystem read-only

[ 3869.182717] EXT4-fs (mmcblk0p2): previous I/O error to superblock detected

[ 3869.184561] mmcblk0: error -110 sending status command, retrying

[ 3869.185227] mmcblk0: error -110 sending status command, retrying

[ 3869.185950] mmcblk0: error -110 sending status command, aborting

[ 3869.186020] end_request: I/O error, dev mmcblk0, sector 1050624

[ 3869.186141] Buffer I/O error on device mmcblk0p2, logical block 0

[ 3869.186258] lost page write due to I/O error on mmcblk0p2

[ 3869.196306] Kernel panic - not syncing: EXT4-fs panic from previous error

[ 3869.196319]

[ 3869.196503] Backtrace:

[ 3869.196654] [<c003e3b8>] (dump_backtrace+0x0/0x10c) from [<c0611280>] (dump_stack+0x18/0x1c)

[ 3869.196775] r6:c08527e0 r5:00000000 r4:c0897a08 r3:00000000

[ 3869.197086] [<c0611268>] (dump_stack+0x0/0x1c) from [<c06113e0>] (panic+0x80/0x198)

[ 3869.197219] [<c0611360>] (panic+0x0/0x198) from [<c0185320>] (__ext4_abort+0xd8/0xec)

[ 3869.197339] r3:88020840 r2:db367cb8 r1:db367cac r0:c077df58

[ 3869.197640] r7:db366000

[ 3869.197768] [<c018524c>] (__ext4_abort+0x4/0xec) from [<c01853b8>] (ext4_journal_start_sb+0x84/0x128)

[ 3869.197888] r6:0000002a r5:e713a000 r4:e70c5800

[ 3869.198143] [<c0185334>] (ext4_journal_start_sb+0x0/0x128) from [<c0178be8>] (ext4_create+0x4c/0x118)

[ 3869.198210] r8:e76fbe80 r7:c062ce80 r6:e7529800 r5:e7568288 r4:e7529800

[ 3869.198636] [<c0178b9c>] (ext4_create+0x0/0x118) from [<c010f0f8>] (vfs_create+0x90/0xbc)

[ 3869.198802] [<c010f068>] (vfs_create+0x0/0xbc) from [<c011111c>] (do_last.isra.37+0x5ec/0x6a0)

[ 3869.198871] r6:db367e90 r5:00020241 r4:db367ed8

[ 3869.199172] [<c0110b30>] (do_last.isra.37+0x0/0x6a0) from [<c0111414>] (path_openat+0xc0/0x3b0)

[ 3869.199298] [<c0111354>] (path_openat+0x0/0x3b0) from [<c01117f8>] (do_filp_open+0x34/0x88)

[ 3869.199375] [<c01117c4>] (do_filp_open+0x0/0x88) from [<c01027e8>] (do_sys_open+0xf0/0x188)

[ 3869.199495] r7:00000001 r6:0000002e r5:00020241 r4:d49d0000

[ 3869.199856] [<c01026f8>] (do_sys_open+0x0/0x188) from [<c01028a8>] (sys_open+0x28/0x2c)

[ 3869.199930] [<c0102880>] (sys_open+0x0/0x2c) from [<c003a980>] (ret_fast_syscall+0x0/0x30)

[ 3869.200055] Rebooting in 5 seconds..

[ 3874.199803] Restarting Linux version 3.0.50-Cyanogenmod-g2a11ce9 (inky-ghost@cyanogenmod) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 PREEMPT Sun Mar 3 20:47:31 PST 2013

[ 3874.199814]

[ 3874.203399] arch_reset: attempting watchdog reset

Thanks for any help or ideas people have!