Per Jessen wrote:
David C. Rankin wrote:
I will be watching because as I already posted I see the "exact" same instability problems with my:
Gigabyte GA-N700SL 2 Gig of Ram Raid1: 2 Seagate (ST3250410AS_6RY28WW1) SATA 250G drives in Raid 1 ATA: Maxtor_5T020H2_T2H34J2 as swap
I mean the *exact* same problems. Please do not forget to post any response you get from them. It also may be a kernel issue.
The last response from Gigabyte suggested I try Windows and verify if the stability also existed there. They also suggested Linux may not have the right support for the new chipset.
I replied that the only Windows license I have available is for Win2000, which is also unlikely to have support for a 2007 chipset :-) I think it's highly likely that I'll be returning this board in the next few days.
Take a look at another bug I have open regarding this instability. The fact that it has spamassassin involved may be irrelevant. A Gigabyte,kernel issue may be the root cause:
Hmm, there's not much to go on to actually suggest a kernel problem?
/Per Jessen, Zürich
Per, I don't think it is a "new" chipset problem. The GA-N700SL I have is a 2005 board. Take a look at the log snippet below and let me know if you are seeing anything similar. I also experienced another meltdown Sunday morning and I have updated bugzilla (https://bugzilla.novell.com/show_bug.cgi?id=353252) with the following: <quote> Guys, This may be a pure kernel/Gigabyte issue as opposed to a sa-learn only issue. The sa-learn problem looks like it may the the result of a larger issue concerning kernel stability/instability on the gigabyte platform. I have experienced several additional meltdowns. Some the logs are blank. Some the logs contain useful information. The latest, yesterday involved the simple routine daily mandb process. The following was collected: Feb 10 04:30:09 bonza kernel: BUG: unable to handle kernel NULL pointer dereference at virtual address 00000044 Feb 10 04:30:09 bonza kernel: printing eip: Feb 10 04:30:09 bonza kernel: c02c6157 Feb 10 04:30:09 bonza kernel: *pde = 00000000 Feb 10 04:30:09 bonza kernel: Oops: 0002 [#2] Feb 10 04:30:09 bonza kernel: SMP Feb 10 04:30:09 bonza kernel: last sysfs file: /devices/platform/i2c-adapter/i2c-9191/9191-0290/name Feb 10 04:30:09 bonza kernel: Modules linked in: af_packet it87 hwmon_vid hwmon i2c_isa iptable_filter ip_tables ip6_tables x_tables apparmor loop 8139cp 8139too mii button sr_mod cdrom shpchp i2c_nforce2 rtc_cmos pci_hotplug rtc_core nvidia_agp rtc_lib i2c_core agpgart sg dm_mirror dm_log sd_mod ehci_hcd ohci_hcd usbcore dm_snapshot dm_mod edd ext3 mbcache jbd fan sata_nv pata_amd libata scsi_mod thermal processor Feb 10 04:30:09 bonza kernel: CPU: 0 Feb 10 04:30:09 bonza kernel: EIP: 0060:[<c02c6157>] Tainted: G N VLI Feb 10 04:30:09 bonza kernel: EFLAGS: 00010286 (2.6.22.16-0.2-default #1) Feb 10 04:30:09 bonza kernel: EIP is at _spin_lock+0x1/0xf Feb 10 04:30:09 bonza kernel: eax: 00000044 ebx: d4cdf978 ecx: d4cdf888 edx: 00000001 Feb 10 04:30:09 bonza kernel: esi: 00000000 edi: 00000039 ebp: d4cdf930 esp: d56dfd84 Feb 10 04:30:09 bonza kernel: ds: 007b es: 007b fs: 00d8 gs: 0033 ss: 0068 Feb 10 04:30:09 bonza kernel: Process mandb (pid: 3975, ti=d56de000 task=f7f79570 task.ti=d56de000) Feb 10 04:30:09 bonza kernel: Stack: c018eee3 00000282 00000246 00000000 dfafba40 dfb77e00 d4cdf978 d4cdf888 Feb 10 04:30:09 bonza kernel: 00000000 00000039 00000039 c0181a80 00000080 d4cdfc68 d4ccbe94 00027fd8 Feb 10 04:30:09 bonza kernel: dfffeaa0 0000008e 000280d2 c015bdfc 00003c90 00001e48 00000000 013fec00 Feb 10 04:30:09 bonza kernel: Call Trace: Feb 10 04:30:09 bonza kernel: [<c018eee3>] remove_inode_buffers+0x3b/0xc8 Feb 10 04:30:09 bonza kernel: [<c0181a80>] shrink_icache_memory+0xc5/0x1b6 Feb 10 04:30:09 bonza kernel: [<c015bdfc>] shrink_slab+0xde/0x13b Feb 10 04:30:09 bonza kernel: [<c015c6e4>] try_to_free_pages+0x173/0x247 Feb 10 04:30:09 bonza kernel: [<c015833e>] __alloc_pages+0x1a1/0x2d6 Feb 10 04:30:09 bonza kernel: [<c0163392>] find_mergeable_anon_vma+0x5e/0xb2 Feb 10 04:30:09 bonza kernel: [<c0160646>] __handle_mm_fault+0x482/0xa83 Feb 10 04:30:09 bonza kernel: [<c0170c32>] do_sync_read+0x0/0x10a Feb 10 04:30:09 bonza kernel: [<c01632a8>] arch_get_unmapped_area_topdown+0x9b/0x127 Feb 10 04:30:09 bonza kernel: [<c0162c52>] vma_merge+0x168/0x178 Feb 10 04:30:09 bonza kernel: [<c02c78fa>] do_page_fault+0x26c/0x5a6 Feb 10 04:30:09 bonza kernel: [<c02c768e>] do_page_fault+0x0/0x5a6 Feb 10 04:30:09 bonza kernel: [<c02c6492>] error_code+0x72/0x80 Feb 10 04:30:09 bonza kernel: ======================= Feb 10 04:30:09 bonza kernel: Code: 05 90 ff 00 30 d2 89 d0 c3 89 c2 90 81 28 00 00 00 01 0f 94 c0 84 c0 b9 01 00 00 00 75 09 90 81 02 00 00 00 01 30 c9 89 c8 c3 90 <fe> 08 79 09 f3 90 80 38 00 7e f9 eb f2 c3 90 81 28 00 00 00 01 Feb 10 04:30:09 bonza kernel: EIP: [<c02c6157>] _spin_lock+0x1/0xf SS:ESP 0068:d56dfd84 Feb 10 04:30:09 bonza su: (to nobody) root on none Feb 10 04:30:35 bonza syslog-ng[2748]: last message repeated 3 times Let me know what else I can provide. I am not the only user affected by instability on Gigabyte boards. Per Jessen on the openSuSE list is likewise seeing the exact same issues. I am more than happy to provide whatever you need to see if we can solve this. This has happened regardless of the kernel version installed. Currently we have: 11:35 bonza~> uname -r 2.6.22.16-0.2-default </quote> This is just strange and a huge pain when the server just sporadically just goes whacko. I'll post any additional information I can. Since this has occurred with both mandriva and opensuse, on different power supplies and with different ram and hardrives, it is pretty much limited to being a gigabyte motherboard problem. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org