From: Pavol Cvengros <pavol.cvengros@primeinteractive.net>
To: Zid Null <zidsoft@gmail.com>
Cc: "Olivér Pintér" <oliver.pntr@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: ICH9 & Core2 Duo - kernel crash
Date: Tue, 04 Dec 2007 18:41:05 +0100 [thread overview]
Message-ID: <47559131.4070800@primeinteractive.net> (raw)
In-Reply-To: <328e43f00712040901i6ef853eanee3e43fceacc447e@mail.gmail.com>
I have one P35 machine too. And it's running ok (my workstation). The
problem is with this board and chipset Intel G33 Express.
I am going to test vanilla 2.6.22 kernels and latest devel kernel too
next few days.
Zid Null wrote:
> I'm using ICH9 on this machine currently, works fine. (p35 chipset though)
>
> On 04/12/2007, *Pavol Cvengros* < pavol.cvengros@primeinteractive.net
> <mailto:pavol.cvengros@primeinteractive.net>> wrote:
>
> On Tuesday 04 December 2007 16:10:40 Olivér Pintér wrote:
> > On 12/4/07, Pavol Cvengros <pavol.cvengros@primeinteractive.net
> <mailto:pavol.cvengros@primeinteractive.net>> 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..
> > >
> > > lspci:
> > > 00:00.0 Host bridge: Intel Corporation DRAM Controller (rev 02)
> > > 00:02.0 VGA compatible controller: Intel Corporation
> Integrated Graphics
> > > Controller (rev 02)
> > > 00:03.0 Communication controller: Intel Corporation MEI
> Controller (rev
> > > 02) 00: 1a.0 USB Controller: Intel Corporation USB UHCI
> Controller #4 (rev
> > > 02) 00:1a.1 USB Controller: Intel Corporation USB UHCI
> Controller #5 (rev
> > > 02) 00:1a.2 USB Controller: Intel Corporation USB UHCI
> Controller #6 (rev
> > > 02) 00:1a.7 USB Controller: Intel Corporation USB2 EHCI
> Controller #2
> > > (rev 02) 00:1c.0 PCI bridge: Intel Corporation PCI Express
> Port 1 (rev
> > > 02) 00:1c.1 PCI bridge: Intel Corporation PCI Express Port 2
> (rev 02)
> > > 00:1c.2 PCI bridge: Intel Corporation PCI Express Port 3 (rev
> 02) 00:1c.3
> > > PCI bridge: Intel Corporation PCI Express Port 4 (rev 02)
> 00:1c.4 PCI
> > > bridge: Intel Corporation PCI Express Port 5 (rev 02) 00: 1d.0 USB
> > > Controller: Intel Corporation USB UHCI Controller #1 (rev 02)
> 00:1d.1 USB
> > > Controller: Intel Corporation USB UHCI Controller #2 (rev 02)
> 00:1d.2 USB
> > > Controller: Intel Corporation USB UHCI Controller #3 (rev 02)
> 00: 1d.7 USB
> > > Controller: Intel Corporation USB2 EHCI Controller #1 (rev 02)
> 00:1e.0
> > > PCI bridge: Intel Corporation 82801 PCI Bridge (rev 92)
> > > 00:1f.0 ISA bridge: Intel Corporation LPC Interface Controller
> (rev 02)
> > > 00:1f.2 IDE interface: Intel Corporation 4 port SATA IDE
> Controller (rev
> > > 02) 00:1f.3 SMBus: Intel Corporation SMBus Controller (rev 02)
> > > 00:1f.5 IDE interface: Intel Corporation 2 port SATA IDE
> Controller (rev
> > > 02) 02:00.0 IDE interface: Marvell Technology Group Ltd. 88SE6101
> > > single-port PATA133 interface (rev b1)
> > > 06:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
> > > RTL-8139/8139C/8139C+ (rev 10)
> > >
> > > Thanks for any kind of help...
> >
> > kernel version?
>
> tested with:
> vanila 2.6.23.9 <http://2.6.23.9>
> gentoo-2.6.23-r2
>
>
> --
> -----------[ Signature ]---------
> Name: Pavol Cvengros
> Company: Prime Interactive, Ltd.
> E-mail: pavol.cvengros@primeinteractive.net
> <mailto:pavol.cvengros@primeinteractive.net>
> Web: http://www.primeinteractive.net <http://www.primeinteractive.net>
> Personal web: http://orpheus.grass.sk
> --
> To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> <mailto:majordomo@vger.kernel.org>
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
> <http://www.tux.org/lkml/>
>
>
next prev parent reply other threads:[~2007-12-04 17:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-04 12:31 ICH9 & Core2 Duo - kernel crash Pavol Cvengros
2007-12-04 14:52 ` Arjan van de Ven
2007-12-04 15:03 ` Pavol Cvengros
2007-12-04 15:10 ` Olivér Pintér
2007-12-04 15:31 ` Pavol Cvengros
[not found] ` <328e43f00712040901i6ef853eanee3e43fceacc447e@mail.gmail.com>
2007-12-04 17:41 ` Pavol Cvengros [this message]
2007-12-06 20:15 ` Bill Davidsen
2007-12-07 6:01 ` Pavol Cvengros
2007-12-07 18:16 ` Bill Davidsen
2007-12-07 18:55 ` Pavol Cvengros
2007-12-08 16:32 ` Bill Davidsen
2007-12-08 21:38 ` Pavol Cvengros
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47559131.4070800@primeinteractive.net \
--to=pavol.cvengros@primeinteractive.net \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver.pntr@gmail.com \
--cc=zidsoft@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.