Article View: ch.comp.os.linux
Article #720Kernel Error
From: Chrigi Hartmann
Date: Mon, 09 Jul 2007 07:46
Date: Mon, 09 Jul 2007 07:46
90 lines
5774 bytes
5774 bytes
Hallo Zusammen Ich habe 8 identische Intel Server unter Fedora 6 am laufen. Die haben ein Intel Xeon Dual Core 2.13 Ghz, 2 x 512 MB PC533 CL4 Ram, 2 x 160 GB S-ATA im Raid und ein Intel Server Board S3000AH verbaut. Die Kisten laufen alle stabil, bis auf eine. Diese ist heute Morgen zum zweiten mal abgeschmiert. Im /var/log/messages finde ich folgendes: Jul 9 07:21:02 dc kernel: kernel BUG at mm/rmap.c:588! Jul 9 07:21:02 dc kernel: invalid opcode: 0000 [#1] Jul 9 07:21:02 dc kernel: SMP Jul 9 07:21:02 dc kernel: last sysfs file: /devices/system/cpu/cpu0/cpufreq/scaling_setspeed Jul 9 07:21:02 dc kernel: Modules linked in: autofs4 hidp rfcomm l2cap bluetooth sunrpc ipv6 acpi_cpufreq freq_table dm_multipath video sbs i2c_ec dock button battery ac parport_pc lp parport floppy i2c_i801 i2c_core iTCO_wdt iTCO_vendor_support ide_cd serio_raw e1000 cdrom sg pcspkr usb_storage dm_snapshot dm_zero dm_mirror dm_mod ata_piix libata sd_mod scsi_mod ext3 jbd ehci_hcd ohci_hcd uhci_hcd Jul 9 07:21:02 dc kernel: CPU: 0 Jul 9 07:21:02 dc kernel: EIP: 0060:[<c0462103>] Not tainted VLI Jul 9 07:21:02 dc kernel: EFLAGS: 00210292 (2.6.20-1.2962.fc6 #1) Jul 9 07:21:02 dc kernel: EIP is at page_remove_rmap+0xd4/0xf1 Jul 9 07:21:02 dc kernel: eax: 0000003b ebx: c1000000 ecx: ffffffff edx: 00200046 Jul 9 07:21:02 dc kernel: esi: d4af01d0 edi: 00000000 ebp: fffab9a4 esp: c881deb0 Jul 9 07:21:02 dc kernel: ds: 007b es: 007b ss: 0068 Jul 9 07:21:02 dc kernel: Process php (pid: 1306, ti=c881d000 task=c25e2930 task.ti=c881d000) Jul 9 07:21:02 dc kernel: Stack: c06a76a5 00000000 c1000000 03a69000 c045c9aa 00000000 d4af01d0 c881df28 Jul 9 07:21:02 dc kernel: 00000000 00000001 03a87000 e691b038 f7273a80 c2414f80 00000000 fffffffb Jul 9 07:21:02 dc kernel: c1d27dac e691b038 001883e5 03a87000 00000000 c881df28 d949fb54 f7273a80 Jul 9 07:21:02 dc kernel: Call Trace: Jul 9 07:21:02 dc kernel: [<c045c9aa>] unmap_vmas+0x294/0x4fd Jul 9 07:21:02 dc kernel: [<c045f4df>] exit_mmap+0x73/0xe9 Jul 9 07:21:02 dc kernel: [<c0420fb0>] mmput+0x34/0x7a Jul 9 07:21:02 dc kernel: [<c04258da>] do_exit+0x1e1/0x6db Jul 9 07:21:02 dc kernel: [<c0423918>] printk+0x1f/0x96 Jul 9 07:21:02 dc kernel: [<c0619f0e>] do_page_fault+0x47e/0x506 Jul 9 07:21:02 dc kernel: [<c0619a90>] do_page_fault+0x0/0x506 Jul 9 07:21:02 dc kernel: [<c06186dc>] error_code+0x7c/0x90 Jul 9 07:21:02 dc kernel: [<c0610033>] unix_sock_destructor+0xa/0xd5 Jul 9 07:21:02 dc kernel: ======================= Jul 9 07:21:02 dc kernel: Code: c0 74 0d 8b 50 08 b8 d5 76 6a c0 e8 7c bd fd ff 8b 46 48 85 c0 74 14 8b 40 10 85 c0 74 0d 8b 50 2c b8 f4 76 6a c0 e8 61 bd fd ff <0f> 0b eb fe 8b 53 10 89 d8 59 5b 5b 5e 83 f2 01 83 e2 01 e9 2a Jul 9 07:21:03 dc kernel: EIP: [<c0462103>] page_remove_rmap+0xd4/0xf1 SS:ESP 0068:c881deb0 Jul 9 07:21:03 dc kernel: <1>Fixing recursive fault but reboot is needed! Jul 9 07:21:03 dc kernel: BUG: scheduling while atomic: php/0x00000001/1306 Jul 9 07:21:03 dc kernel: [<c061658e>] __sched_text_start+0x56/0xa23 Jul 9 07:21:03 dc kernel: [<c042005d>] scheduler_tick+0x7c/0xdc Jul 9 07:21:03 dc kernel: [<c0423918>] printk+0x1f/0x96 Jul 9 07:21:03 dc kernel: [<c04257f7>] do_exit+0xfe/0x6db Jul 9 07:21:03 dc kernel: [<c0405bad>] die+0x216/0x23b Jul 9 07:21:03 dc kernel: [<c0405fb8>] do_invalid_op+0x0/0xab Jul 9 07:21:03 dc kernel: [<c040605a>] do_invalid_op+0xa2/0xab Jul 9 07:21:03 dc kernel: [<c0462103>] page_remove_rmap+0xd4/0xf1 Jul 9 07:21:03 dc kernel: [<c042328d>] release_console_sem+0x183/0x1c2 Jul 9 07:21:03 dc kernel: [<c041cab0>] task_running_tick+0x2d/0x237 Jul 9 07:21:03 dc kernel: [<c0456235>] __pagevec_free+0x14/0x1a Jul 9 07:21:03 dc kernel: [<c06186dc>] error_code+0x7c/0x90 Jul 9 07:21:03 dc kernel: [<c0462103>] page_remove_rmap+0xd4/0xf1 Jul 9 07:21:03 dc kernel: [<c045c9aa>] unmap_vmas+0x294/0x4fd Jul 9 07:21:03 dc kernel: [<c045f4df>] exit_mmap+0x73/0xe9 Jul 9 07:21:03 dc kernel: [<c0420fb0>] mmput+0x34/0x7a Jul 9 07:21:03 dc kernel: [<c04258da>] do_exit+0x1e1/0x6db Jul 9 07:21:03 dc kernel: [<c0423918>] printk+0x1f/0x96 Jul 9 07:21:03 dc kernel: [<c0619f0e>] do_page_fault+0x47e/0x506 Jul 9 07:21:03 dc kernel: [<c0619a90>] do_page_fault+0x0/0x506 Jul 9 07:21:03 dc kernel: [<c06186dc>] error_code+0x7c/0x90 Jul 9 07:21:03 dc kernel: [<c0610033>] unix_sock_destructor+0xa/0xd5 Jul 9 07:21:03 dc kernel: ======================= Kann hier jemand etwas mit diesen Meldungen anfange? WO muss ich ansetzen um das Problem zu finden und zu l�sen? W�re um ein paar Tips dankbar. Gr�assli us em P�ntnerland Chrigi Hartmann
Technical Details
Message-ID:
<d0568$4691e7e7$d947f8ac$24314@news.hispeed.ch>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news3.google.com!feeder1-2.proxad.net!proxad.net!feeder1-1.proxad.net!feeder.news-service.com!txtfeed1.tudelft.nl!tudelft.nl!txtfeed2.tudelft.nl!amsnews11.chello.com!newsfeed01.chello.at!newsfeed02.chello.at!news.hispeed.ch.POSTED!not-for-mailShow Full Headers
Complete Article Headers
X-Google-Thread: f4b73,9bdcaa0896a7ba5e,start X-Google-Attributes: gidf4b73,public,usenet X-Google-Language: GERMAN,ASCII Path: arc1-ca.pugleaf.net!g2news1.google.com!news3.google.com!feeder1-2.proxad.net!proxad.net!feeder1-1.proxad.net!feeder.news-service.com!txtfeed1.tudelft.nl!tudelft.nl!txtfeed2.tudelft.nl!amsnews11.chello.com!newsfeed01.chello.at!newsfeed02.chello.at!news.hispeed.ch.POSTED!not-for-mail Date: Mon, 09 Jul 2007 09:46:42 +0200 From: Chrigi Hartmann <chrigi.hartmann@gmx.net> User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 Newsgroups: ch.comp.os.linux Subject: Kernel Error Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Message-ID: <d0568$4691e7e7$d947f8ac$24314@news.hispeed.ch> X-Complaints-To: abuse@hispeed.ch Organization: hispeed.ch Lines: 90 NNTP-Posting-Host: 217.71.248.172 (217.71.248.172) NNTP-Posting-Date: Mon, 09 Jul 2007 09:46:47 +0200 X-Trace: d05684691e7e77ce25d0924314