Why Do I Get a Kernel Panic When Shutting Down Linux? Primary Software: Driver Software>>NI-488.2Primary Software Version: N/A Primary Software Fixed Version: N/A Secondary Software: Driver Software>>NI-FGEN, Driver Software>>NI-SCOPE, Driver Software>>NI-DMM, Driver Software>>NI-VISA, Driver Software>>NI-DAQmx Base, Driver Software>>NI-DAQmx
Problem: Why do I get a kernel panic similar to below when shutting down my machine running Linux? Kernel panic output: Unable to handle kernel NULL pointer dereference at virtual address 0000000c printing eip: f90f0f01 *pde = 2fe30001 Oops: 0000 [#1] SMP Modules linked in: nipxirmk(U) nidimk(U) niorbk(U) gpibprtk(U) nipalk(U) nikal(U) parport_pc lp parport autofs4 i2c_dev i2c_core sunrpc dm_mirror dm_multipath dm_mod button battery ac md5 ipv6 joydev uhci_hcd ehci_hcd hw_random e1000 ext3 jbd raid1 ata_piix libata mptscsih mptsas mptspi mptscsi mptbase sd_mod scsi_mod CPU: 2 EIP: 0060:[<f90f0f01>] Tainted: PF VLI EFLAGS: 00210246 (2.6.9-55.0.2.ELsmp) EIP is at nipalk-unversioned0002360+0x3d/0x50 [nipalk] eax: 00000000 ebx: 00038010 ecx: 00000001 edx: 00000000 esi: f07aee64 edi: f07aef00 ebp: f07aedfc esp: f07aedf8 ds: 007b es: 007b ss: 0068 Process nipalsm (pid: 6233, threadinfo=f07ae000 task=f03c8230) Stack: f07aee40 f07aee28 f90bd4a8 00000001 00038010 00000002 00000000 00000002 00038010 00000001 f07aee44 00000010 f07aeeb0 f90b3758 f07aee64 f07aee44 f07aee40 f07aee84 00000000 f07aee84 f07aee8c 00000010 00000000 00000008 Call Trace: [<f90bd4a8>] nipalk-unversioned0001190+0x68/0x94 [nipalk] [<f90b3758>] nipalk-unversioned0000984+0xcc/0x194 [nipalk] [<c014e79e>] do_no_page+0x2da/0x2f9 [<f90f0363>] _Z15ioControlHelperPvmS_m+0xcb/0xd0 [nipalk] [<f90f043a>] nipalk-unversioned0002349+0xd2/0x1a4 [nipalk] [<f90f0502>] nipalk-unversioned0002349+0x19a/0x1a4 [nipalk] [<c010d501>] intel_machine_check+0x19/0x174 [<c010d501>] intel_machine_check+0x19/0x174 [<f89e17a0>] nNIKAL100_ioctl+0x21/0x33 [nikal] [<c010d501>] intel_machine_check+0x19/0x174 [<c016b292>] sys_ioctl+0x227/0x269 [<c02d6093>] syscall_call+0x7/0xb [<c010d501>] intel_machine_check+0x19/0x174 Code: 8f 1d f9 8b 54 c8 04 8b 42 08 c7 42 08 00 00 00 00 89 45 10 89 5d 0c 89 55 08 8b 1c 24 c9 e9 df 04 00 00 8d 76 00 a1 20 8f 1d f9 <8b> 54 c8 04 c7 04 8d 60 cf 1d f9 00 00 00 00 eb cb 89 f6 55 89 <0>Fatal exception: panic in 5 seconds Kernel panic - not syncing: Fatal exception Solution: This could be caused because your distribution has a script that removes old files in the /tmp directory that are actually still needed for NI drivers. To avoid this kernel panic, exclude the /tmp/nipal directory from any script that cleans the /tmp directory. For example in Red Hat Enterprise Linux, you can do this by editing the /etc/cron.daily/tmpwatch file. One of the first lines in tmpwatch should include -x arguments. Add "-x /tmp/nipal" to that line to exclude NI driver software from the removal list. An example tmpwatch file is displayed and attached below. The bold and underlined text is the addition described above. /usr/sbin/tmpwatch -x /tmp/.X11-unix -x /tmp/.XIM-unix -x /tmp/.font-unix -x /tmp/.ICE-unix -x /tmp/.Test-unix -x /tmp/nipal 240 /tmp /usr/sbin/tmpwatch 720 /var/tmp for d in /var/{cache/man,catman}/{cat?,X11R6/cat?,local/cat?}; do if [ -d "$d" ]; then /usr/sbin/tmpwatch -f 720 $d fi done Related Links: Attachments:  tmpwatch
Report Date: 07/24/2007 Last Updated: 07/26/2007 Document ID: 4BNASUQA |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
