Fedora Linux Support Community & Resources Center
  #1  
Old 18th March 2007, 11:22 PM
dbixler Offline
Registered User
 
Join Date: Mar 2007
Posts: 4
FC5: Spurious General Protection Fault

Guys,
Recently, a server that I run (which has been running flawlessly for the last several months) started dying spontaneously. Also, after downloading a bunch of updates (via yum), it won't even boot the new kernel. I've had to fall back to using the previous kernel that is dying. Below is the message in the /var/log/messages file. I could really use some help on this one, please. One thing that seems to change is the process where it dies. Sometimes it's cleanup, sometimes smbd, sometimes master, it's completely random (or so it seems).

Mar 18 00:22:45 lothlorien kernel: general protection fault: 0000 [1] SMP
Mar 18 00:22:45 lothlorien kernel: last sysfs file: /block/hdb/size
Mar 18 00:22:45 lothlorien kernel: CPU 1
Mar 18 00:22:45 lothlorien kernel: Modules linked in: ipv6 autofs4 it87 hwmon_vid hwmon i2c_isa hidp rfcomm l2cap bluetooth sunrpc ip_conntrack_netbios_ns ipt_REJECT xt_state ip_conntrack nfnetlink xt_tcpudp iptable_filter ip_tables x_tables raid456 xor video sbs i2c_ec button battery asus_acpi ac lp parport_pc parport floppy snd_hda_intel snd_hda_codec snd_seq_dummy snd_ice1724 snd_ice17xx_ak4xxx snd_ac97_codec snd_ac97_bus snd_ak4114 snd_ak4xxx_adda snd_seq_oss snd_mpu401_uart snd_seq_midi_event nvidia(U) sg snd_rawmidi snd_seq snd_pcm_oss serio_raw tulip i2c_core snd_seq_device snd_mixer_oss ide_cd snd_pcm snd_timer snd ehci_hcd cdrom ohci_hcd soundcore snd_page_alloc shpchp pcspkr dm_snapshot dm_zero dm_mirror dm_mod ext3 jbd ahci libata sd_mod scsi_mod
Mar 18 00:22:45 lothlorien kernel: Pid: 14640, comm: cleanup Tainted: P 2.6.18-1.2257.fc5 #1
Mar 18 00:22:45 lothlorien kernel: RIP: 0010:[<ffffffff8021a50d>] [<ffffffff8021a50d>] remove_vma+0x2f/0x75
Mar 18 00:22:45 lothlorien kernel: RSP: 0018:ffff81000e8b1ea8 EFLAGS: 00010282
Mar 18 00:22:45 lothlorien kernel: RAX: dfffffff80550ce0 RBX: ffff810036f79818 RCX: 0000000000000006
Mar 18 00:22:45 lothlorien kernel: RDX: 0000000000000001 RSI: 00000000000000e3 RDI: ffffffff8047cb6e
Mar 18 00:22:45 lothlorien kernel: RBP: ffff810035a278c8 R08: 0000000000000002 R09: ffff810010309980
Mar 18 00:22:45 lothlorien kernel: R10: ffff810008b22348 R11: 0000000000000002 R12: ffff810035a0f800
Mar 18 00:22:45 lothlorien kernel: R13: 0000000000000001 R14: 0000000000000000 R15: 0000000000000000
Mar 18 00:22:45 lothlorien kernel: FS: 0000000000000000(0000) GS:ffff81003df049c0(0000) knlGS:0000000000000000
Mar 18 00:22:45 lothlorien kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Mar 18 00:22:45 lothlorien kernel: CR2: 00002aaaac149560 CR3: 0000000000201000 CR4: 00000000000006e0
Mar 18 00:22:45 lothlorien kernel: Process cleanup (pid: 14640, threadinfo ffff81000e8b0000, task ffff81002b2d5040)
Mar 18 00:22:45 lothlorien kernel: Stack: 0000000000000001 ffff810002018400 ffff810036f79818 ffffffff80239f2a
Mar 18 00:22:45 lothlorien kernel: 00000000000000e7 ffff810002018400 ffff810035a0f800 ffff810035a0f8b0
Mar 18 00:22:45 lothlorien kernel: 00002aaaabc62888 ffffffff8023c058 ffff81002b2d5040 00002aaaabc62888
Mar 18 00:22:45 lothlorien kernel: Call Trace:
Mar 18 00:22:45 lothlorien kernel: [<ffffffff80239f2a>] exit_mmap+0xca/0xee
Mar 18 00:22:45 lothlorien kernel: [<ffffffff8023c058>] mmput+0x41/0x96
Mar 18 00:22:45 lothlorien kernel: [<ffffffff802150f4>] do_exit+0x293/0x928
Mar 18 00:22:45 lothlorien kernel: [<ffffffff8024816e>] cpuset_exit+0x0/0x6c
Mar 18 00:22:45 lothlorien kernel: [<00002aaaabc62888>]
Mar 18 00:22:45 lothlorien kernel:
Mar 18 00:22:45 lothlorien kernel:
Mar 18 00:22:45 lothlorien kernel: Code: 48 8b 40 08 48 85 c0 74 05 48 89 df ff d0 48 8b bb 90 00 00
Mar 18 00:22:45 lothlorien kernel: RIP [<ffffffff8021a50d>] remove_vma+0x2f/0x75
Mar 18 00:22:45 lothlorien kernel: RSP <ffff81000e8b1ea8>
Mar 18 00:22:45 lothlorien kernel: <1>Fixing recursive fault but reboot is needed!
M
Reply With Quote
  #2  
Old 21st March 2007, 03:22 AM
sonicbuddha Offline
Registered User
 
Join Date: Aug 2004
Posts: 24
I have a nearly identical problem. I just upgraded my machine with a new AMD 4200+ 65W and received a similar crash in the middle of the night (log below). Thinking that m'be the processor was bad, I spent 24 hours throwing everything I had at it: cpuburn, nbench, sprime, super-pi, even the stress tests from the linux test project, making sure to exercise both cores. It didn't even blink. The next day, another crash.

This is with the most recent kernel, 2.6.20-1.2300, X86_64 on FC5. I do notice that, on both times, its soon after either starting or stopping a raid.

I've googled this and found a lot of people with similar errors but no answers.

Mar 18 23:10:23 phoenix kernel: md: md1 stopped.
Mar 18 23:10:23 phoenix kernel: md: unbind<sdc1>
Mar 18 23:10:23 phoenix kernel: md: export_rdev(sdc1)
Mar 18 23:10:23 phoenix kernel: md: unbind<sdb1>
Mar 18 23:10:23 phoenix kernel: md: export_rdev(sdb1)
Mar 18 23:10:45 phoenix ainit:
Mar 18 23:14:07 phoenix last message repeated 2 times
Mar 18 23:14:07 phoenix ainit:
Mar 19 00:15:47 phoenix kernel: general protection fault: 0000 [1] SMP
Mar 19 00:15:47 phoenix kernel: last sysfs file: /devices/pci0000:00/0000:00:0a.1/i2c-0/name
Mar 19 00:15:47 phoenix kernel: CPU 0
Mar 19 00:15:47 phoenix kernel: Modules linked in: eeprom i2c_dev nfsd exportfs lockd nfs_acl ipv6 it87 hwmon_vid i2c_isa sunrpc xf
s dm_mirror dm_mod raid0 video sbs i2c_ec dock button battery asus_acpi backlight ac lp parport_pc parport ehci_hcd ohci1394 floppy
ohci_hcd sg ieee1394 k8_edac edac_mc serio_raw ide_cd shpchp k8temp hwmon i2c_nforce2 i2c_core pcspkr cdrom forcedeth ext3 jbd sat
a_nv libata sd_mod scsi_mod
Mar 19 00:15:47 phoenix kernel: Pid: 3157, comm: bittorrent-curs Not tainted 2.6.20-1.2300.fc5 #1
Mar 19 00:15:47 phoenix kernel: RIP: 0010:[<ffffffff8022ea59>] [<ffffffff8022ea59>] do_sys_poll+0x1f4/0x35f
Mar 19 00:15:47 phoenix kernel: RSP: 0018:ffff81004b0dbb98 EFLAGS: 00010246
Mar 19 00:15:47 phoenix kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000002
Mar 19 00:15:47 phoenix kernel: RDX: 0000000000000104 RSI: 0000000000000104 RDI: ffff81007328e340
Mar 19 00:15:47 phoenix kernel: RBP: ffff81004b0dbedc R08: 0000000000000000 R09: 00000000000007c9
Mar 19 00:15:47 phoenix kernel: R10: 0000000000000000 R11: ffff810033c41300 R12: ffff81007328e340
Mar 19 00:15:47 phoenix kernel: R13: fbbf81004b0dbe18 R14: ffff81004b0dbf78 R15: ffff81004b0dbbc8
Mar 19 00:15:47 phoenix kernel: FS: 00002aaaaaab7e90(0000) GS:ffffffff80582000(0000) knlGS:0000000000000000
Mar 19 00:15:47 phoenix kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Mar 19 00:15:47 phoenix kernel: CR2: 00002aaab0476000 CR3: 00000000619c4000 CR4: 00000000000006e0
Mar 19 00:15:47 phoenix kernel: Process bittorrent-curs (pid: 3157, threadinfo ffff81004b0da000, task ffff81002bb78820)
Mar 19 00:15:47 phoenix kernel: Stack: 000000000098a830 000000000098a8e8 0000000000000000 ffff81004b0dbe18
Mar 19 00:15:47 phoenix kernel: ffff81004b0dbe18 ffff81004b0dbedc ffffffff8021e48a ffff810020098000
Mar 19 00:15:47 phoenix kernel: 0000000a00000000 ffff810033c41d00 ffff810000000000 ffff81002bb78820
Mar 19 00:15:47 phoenix kernel: Call Trace:
Mar 19 00:15:47 phoenix kernel: [<ffffffff8021e48a>] __pollwait+0x0/0xe1
Mar 19 00:15:47 phoenix kernel: [<ffffffff80285931>] default_wake_function+0x0/0xe
Mar 19 00:15:47 phoenix last message repeated 9 times
Mar 19 00:15:47 phoenix kernel: [<ffffffff802b0069>] audit_syscall_entry+0x141/0x174
Mar 19 00:15:47 phoenix kernel: [<ffffffff8024982e>] sys_poll+0x2c/0x33
Mar 19 00:15:47 phoenix kernel: [<ffffffff8025a29c>] tracesys+0xdc/0xe1
Mar 19 00:15:47 phoenix kernel:
Mar 19 00:15:47 phoenix kernel:
Mar 19 00:15:47 phoenix kernel: Code: 4d 8b 6d 00 4d 85 ed 0f 85 61 ff ff ff 44 8b 44 24 14 45 85
Mar 19 00:15:47 phoenix kernel: RIP [<ffffffff8022ea59>] do_sys_poll+0x1f4/0x35f
Mar 19 00:15:47 phoenix kernel: RSP <ffff81004b0dbb98>


Mar 20 13:39:21 phoenix kernel: XFS mounting filesystem md1
Mar 20 13:39:21 phoenix kernel: SELinux: initialized (dev md1, type xfs), uses xattr
Mar 20 13:50:50 phoenix kernel: general protection fault: 0000 [1] SMP
Mar 20 13:50:50 phoenix kernel: last sysfs file: /block/sdb/size
Mar 20 13:50:50 phoenix kernel: CPU 0
Mar 20 13:50:50 phoenix kernel: Modules linked in: nfsd exportfs lockd nfs_acl ipv6 sunrpc xfs dm_mirror dm_mod raid0 video sbs i2c
_ec dock button battery asus_acpi backlight ac lp parport_pc parport ohci1394 ohci_hcd ieee1394 floppy ehci_hcd sg serio_raw ide_cd
k8temp hwmon k8_edac edac_mc i2c_nforce2 i2c_core shpchp pcspkr cdrom forcedeth ext3 jbd sata_nv libata sd_mod scsi_mod
Mar 20 13:50:50 phoenix kernel: Pid: 3236, comm: bonnie++ Not tainted 2.6.20-1.2300.fc5 #1
Mar 20 13:50:50 phoenix kernel: RIP: 0010:[<ffffffff8025f72f>] [<ffffffff8025f72f>] io_schedule+0x33/0x67
Mar 20 13:50:50 phoenix kernel: RSP: 0018:ffff81000aecdb48 EFLAGS: 00010206
Mar 20 13:50:50 phoenix kernel: RAX: 0000000000000000 RBX: ffbf81000301c860 RCX: 0000000000008d3c
Mar 20 13:50:50 phoenix kernel: RDX: 00000000001f7005 RSI: 0000000000004d7f RDI: ffff81007e42a788
Mar 20 13:50:50 phoenix kernel: RBP: ffff81000aecdb58 R08: ffff8100030037f0 R09: ffff81007e683a28
Mar 20 13:50:50 phoenix kernel: R10: 0000000000029aae R11: ffff8100030037d8 R12: ffff8100829eef00
Mar 20 13:50:50 phoenix kernel: R13: 0000000000000002 R14: ffffffff8022890c R15: ffff81007136e398
Mar 20 13:50:50 phoenix kernel: FS: 00002aaaaaab84a0(0000) GS:ffffffff80582000(0000) knlGS:00000000f7fcd6c0
Mar 20 13:50:50 phoenix kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Mar 20 13:50:50 phoenix kernel: CR2: 000000000050f30f CR3: 000000002acd6000 CR4: 00000000000006e0
Mar 20 13:50:50 phoenix kernel: Process bonnie++ (pid: 3236, threadinfo ffff81000aecc000, task ffff8100033a4080)
Mar 20 13:50:50 phoenix kernel: Stack: ffff8100022e99c0 ffff8100030037d8 ffff81000aecdba8 ffffffff8022894d
Mar 20 13:50:50 phoenix kernel: ffff8100022e99c0 ffffffff8025f87f ffff8100022e99c0 ffff81000aecdee8
Mar 20 13:50:50 phoenix kernel: 0000000000029aae 0000000000008bf3 0000000000000000 ffffffff8023ec2d
Mar 20 13:50:50 phoenix kernel: Call Trace:
Mar 20 13:50:50 phoenix kernel: [<ffffffff8022894d>] sync_page+0x41/0x45
Mar 20 13:50:50 phoenix kernel: [<ffffffff8025f87f>] __wait_on_bit_lock+0x36/0x66
Mar 20 13:50:50 phoenix kernel: [<ffffffff8023ec2d>] __lock_page+0x5e/0x64
Mar 20 13:50:50 phoenix kernel: [<ffffffff80297f1e>] wake_bit_function+0x0/0x23
Mar 20 13:50:50 phoenix kernel: [<ffffffff8020c03c>] do_generic_mapping_read+0x1d9/0x40b
Mar 20 13:50:50 phoenix kernel: [<ffffffff8020ccbd>] file_read_actor+0x0/0x166
Mar 20 13:50:50 phoenix kernel: [<ffffffff802168d8>] generic_file_aio_read+0x15b/0x19d
Mar 20 13:50:50 phoenix kernel: [<ffffffff8827e771>] :xfs:xfs_read+0x26a/0x2df
Mar 20 13:50:50 phoenix kernel: [<ffffffff8827b326>] :xfs:xfs_file_aio_read+0x58/0x5e
Mar 20 13:50:50 phoenix kernel: [<ffffffff8020c9f1>] do_sync_read+0xc9/0x10c
Mar 20 13:50:50 phoenix kernel: [<ffffffff8031602d>] file_has_perm+0x94/0xa3
Mar 20 13:50:50 phoenix kernel: [<ffffffff80297ef0>] autoremove_wake_function+0x0/0x2e
Mar 20 13:50:50 phoenix kernel: [<ffffffff8020b14e>] vfs_read+0xcb/0x173
Mar 20 13:50:50 phoenix kernel: [<ffffffff802117e3>] sys_read+0x45/0x6e
Mar 20 13:50:50 phoenix kernel: [<ffffffff8025a29c>] tracesys+0xdc/0xe1
Mar 20 13:50:50 phoenix kernel:
Mar 20 13:50:50 phoenix kernel:
Mar 20 13:50:50 phoenix kernel: Code: f0 ff 83 54 12 00 00 e8 b5 ec ff ff f0 ff 8b 54 12 00 00 65
Mar 20 13:50:50 phoenix kernel: RIP [<ffffffff8025f72f>] io_schedule+0x33/0x67
Mar 20 13:50:50 phoenix kernel: RSP <ffff81000aecdb48>
Reply With Quote
  #3  
Old 21st March 2007, 03:26 AM
dbixler Offline
Registered User
 
Join Date: Mar 2007
Posts: 4
Upgraded to FC6. Took about 3 or 4 hours. Running flawlessly now for like 2 or 3 days. Problem solved :P.
Reply With Quote
  #4  
Old 21st March 2007, 03:34 AM
sonicbuddha Offline
Registered User
 
Join Date: Aug 2004
Posts: 24
Huh. I remain unconvinced since both FC5 and FC6 are running the same kernel, although you were running 2.6.18-1.2257 and I was running 2.6.20-1.2300. Although both of us were doing filesystem related processes, mine either a bonnie++ test or bittorrrent, yours comm.

I am curious, what is your processor?
Reply With Quote
  #5  
Old 21st March 2007, 03:41 AM
dbixler Offline
Registered User
 
Join Date: Mar 2007
Posts: 4
Unconvinced? Well, it has been running flawlessly now for 1 day and 22 hours (so I spoke somewhat incorrectly above), and prior to this it did not always fault on comm. That was just one example. It faulted on smb sometimes, master, and other processes. As for the CPU, it's a Pentium D 2.66Ghz. Anyhow, almost 2 days now when before it wouldn't get past 24 hours.
Reply With Quote
  #6  
Old 21st March 2007, 03:49 AM
sonicbuddha Offline
Registered User
 
Join Date: Aug 2004
Posts: 24
For me, I'll easily make it past 24 hours, think I am in the clear and then *BAM* crash.

What kernel are you running now?
Reply With Quote
  #7  
Old 21st March 2007, 09:17 PM
dbixler Offline
Registered User
 
Join Date: Mar 2007
Posts: 4
Linux lothlorien.wbs-wireless.com 2.6.18-1.2798.fc6 #1 SMP Mon Oct 16 14:39:22 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux
Reply With Quote
  #8  
Old 21st March 2007, 09:34 PM
sonicbuddha Offline
Registered User
 
Join Date: Aug 2004
Posts: 24
And you're still stable? Congrats. That makes at least 48 hours, right?

Curious that, even after your upgrade, you're not running the most recent kernel, 2.6.20-1.2300. Any particular reason? What kernel were you running on FC5 when you experienced your crashes?

Oh, and to clarify, by "unconvinced" I meant I was unconvinced that upgrading to FC6 would solve at least my problem, considering it seems kernel based, not that I didn't believe you that you were able to resolve your problem.
Reply With Quote
  #9  
Old 21st March 2007, 09:52 PM
sonicbuddha Offline
Registered User
 
Join Date: Aug 2004
Posts: 24
Oh, and, BTW, I'm not convinced that my problem isn't hardware based, either. I've switched out my CPU for another dual core I happened to have. If it can stay up for at least 24 hours, I'll believe its the CPU.

Thanks!
Reply With Quote
Reply

Tags
fault, fc5, general, protection, spurious

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
2.6.27.9-159.fc10.x86_64 & general protection fault LinuxTom Using Fedora 2 29th December 2008 01:37 AM
HSF Modem Driver causes a general fault protection fedora6userSVT Using Fedora 1 20th November 2007 11:58 AM
General protection fault (SMP) on quad core system andygrove Using Fedora 0 11th August 2007 09:20 PM


Current GMT-time: 23:16 (Friday, 18-04-2014)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat