lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <47585879.7010305@tmr.com>
Date:	Thu, 06 Dec 2007 15:15:53 -0500
From:	Bill Davidsen <davidsen@....com>
To:	Pavol Cvengros <pavol.cvengros@...meinteractive.net>
CC:	linux-kernel@...r.kernel.org
Subject: Re: ICH9 & Core2 Duo - kernel crash

Pavol Cvengros wrote:
> Hello,
> 
> I am trying LKML to get some help on one linux kernel related problem.
> Lately we got a machine with new HW from Intel. CPU is Intel Core2 Duo E6850 
> 3GHz with 2GB of RAM. Motherboard is Intel DG33BU with G33 chipset.
> 
> After long fight with kernel crashes on different things, we figured out that 
> if the multicore is disabled in bios, everything is ok and machine is running 
> good. No kernel crashes no problems, but with one core only.
> 
> This small table will maybe explain:
> 
> Cores   -     kernel   -   state
>    2  -   nonsmp or smp  - crash
>    1  -  smp or nonsmp  - ok
> 
> All crashes have been different (swaper, rcu, irq, init.....) or we just got 
> internal gcc compiler error while compiling kernel/glibc/.... and the machine 
> was frozen.
> 
> Please can somebody advise what to do to identify that problem more precisely.
> (debug kernel options?)
> 
> Our immpresion - ICH9 & ICH9R support in kernel is bad... sorry to say..
> 
I have seen unusual memory behavior under heavy load, in the cases I saw 
it was heavy DMA load from multiple SCSI controllers, and one case with 
FFT on the CPU and heavy network load with gigE. Have you run memtest on 
this hardware? Just a thought, but I see people running Linux on that 
chipset, if not that particular board.

A cheap test even if it shows nothing. Of course it could be a CPU cache 
issue in that one CPU, although that's unlikely.

-- 
Bill Davidsen <davidsen@....com>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ