mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* SMP + Hyperthreading / Asus PCDL Deluxe / Kernel 2.4.x 2.6.x / Crash/Freeze
@ 2004-03-10 12:27 Richard Browning
  2004-03-10 16:10 ` Zwane Mwaikambo
  0 siblings, 1 reply; 15+ messages in thread
From: Richard Browning @ 2004-03-10 12:27 UTC (permalink / raw)
  To: linux-kernel

**** SUMMARY
Enabling hyperthreading on Asus PCDL Deluxe motherboard w/ 2xP4Xeon causes 
system freeze in short order.

**** DESCRIPTION
I have an Asus PCDL Deluxe P4Xeon motherboard which has a north/southbridge 
combination allowing system memory to run at 533MHz . The motherboard has the 
usual Asus onboard gigabit ethernet, AD1985 audio, Intel and Promise SATA 
controllers, firewire. All are enabled and operate. I am running dual 2.8GHz 
P4 Xeons.

When hyperthreading is disabled the system is perfectly stable and usable. No 
operating artefacts seem to occur and SMP appears to workcorrectly.

However when hyperthreading is enabled, the system operates for a brief period 
(enough for KDE to boot, for example) before halting. When operating from the 
command line it is usual to see a Machine Check Exception error immediately 
prior to system failure.

**** KEYWORDS
SMP Hyperthreading Asus Xeon Freeze Crash

**** KERNELS
2.4.2x 2.6.x

**** OOPS
Not available

**** CATALYST
Enable hyperthreading

**** ENVIRONMENT
Asus PCDL Deluxe motherboard
(http://usa.asus.com/products/server/srv-mb/pc-dl/overview.HTM)

**** SOFTWARE
Gnu C                  3.3.2
Gnu make               3.80
util-linux             2.12
mount                  2.12
module-init-tools      0.9.15-pre4
e2fsprogs              1.34
Linux C Library        2.3.2
Dynamic linker (ldd)   2.3.2
Procps                 3.1.15
Net-tools              1.60
Kbd                    1.08
Sh-utils               5.0.91
Modules Loaded         fglrx eeprom i2c_isa lm75 i2c_i801 i2c_algo_bit i2c_dev 
i2c_sensor i2c_core

**** PROCESSOR
NOTE Hyperthreading disabled
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 15
model           : 2
model name      : Intel(R) Xeon(TM) CPU 2.80GHz
stepping        : 7
cpu MHz         : 2807.537
cache size      : 512 KB
physical id     : 0
siblings        : 1
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe cid
bogomips        : 5537.79

processor       : 1
vendor_id       : GenuineIntel
cpu family      : 15
model           : 2
model name      : Intel(R) Xeon(TM) CPU 2.80GHz
stepping        : 7
cpu MHz         : 2807.537
cache size      : 512 KB
physical id     : 0
siblings        : 1
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe cid
bogomips        : 5603.32

**** MODULES
fglrx 208932 7 - Live 0xe09d5000
eeprom 11656 0 - Live 0xe08c9000
i2c_isa 6144 0 - Live 0xe08b3000
lm75 11908 0 - Live 0xe08c0000
i2c_i801 12176 0 - Live 0xe089f000
i2c_algo_bit 13832 0 - Live 0xe08bb000
i2c_dev 14976 0 - Live 0xe08b6000
i2c_sensor 7168 2 eeprom,lm75, Live 0xe08a3000
i2c_core 27524 7 eeprom,i2c_isa,lm75,i2c_i801,i2c_algo_bit,i2c_dev,i2c_sensor, 
Live 0xe08a8000

**** DRIVER AND HARDWARE
(IOPORTS)
0000-001f : dma1
0020-0021 : pic1
0040-005f : timer
0060-006f : keyboard
0070-0077 : rtc
0080-008f : dma page reg
00a0-00a1 : pic2
00c0-00df : dma2
00f0-00ff : fpu
0170-0177 : libata
01f0-01f7 : ide0
0378-037a : parport0
03c0-03df : vga+
03f6-03f6 : ide0
0500-051f : 0000:00:1f.3
  0500-050f : i801-smbus
0cf8-0cff : PCI conf1
9000-9fff : PCI Bus #01
  9000-90ff : 0000:01:00.0
a000-afff : PCI Bus #02
  a000-a01f : 0000:02:01.0
    a000-a01f : e1000
b000-b01f : 0000:00:1d.0
  b000-b01f : uhci_hcd
b400-b41f : 0000:00:1d.1
  b400-b41f : uhci_hcd
b800-b81f : 0000:00:1d.2
  b800-b81f : uhci_hcd
bc00-bc1f : 0000:00:1d.3
  bc00-bc1f : uhci_hcd
d800-d8ff : 0000:00:1f.5
dc00-dc3f : 0000:00:1f.5
f000-f00f : 0000:00:1f.2
  f000-f00f : libata

(IOMEM)
00000000-0009f7ff : System RAM
0009f800-0009ffff : reserved
000a0000-000bffff : Video RAM area
000d0000-000d0fff : Extension ROM
000f0000-000fffff : System ROM
00100000-1ffeffff : System RAM
  00100000-0036a323 : Kernel code
  0036a324-00492e7f : Kernel data
1fff0000-1fff2fff : ACPI Non-volatile Storage
1fff3000-1fffffff : ACPI Tables
e0000000-e7ffffff : 0000:00:00.0
e8000000-f7ffffff : PCI Bus #01
  e8000000-efffffff : 0000:01:00.0
  f0000000-f7ffffff : 0000:01:00.1
f8000000-f9ffffff : PCI Bus #01
  f9000000-f900ffff : 0000:01:00.0
  f9010000-f901ffff : 0000:01:00.1
fa000000-fa0fffff : PCI Bus #02
  fa000000-fa01ffff : 0000:02:01.0
    fa000000-fa01ffff : e1000
fa100000-fa103fff : 0000:03:03.0
fa104000-fa1047ff : 0000:03:03.0
  fa104000-fa1047ff : ohci1394
fa200000-fa2003ff : 0000:00:1d.7
  fa200000-fa2003ff : ehci_hcd
fa201000-fa2011ff : 0000:00:1f.5
  fa201000-fa2011ff : Intel ICH5 - AC'97
fa202000-fa2020ff : 0000:00:1f.5
  fa202000-fa2020ff : Intel ICH5 - Controller
fec00000-ffffffff : reserved

**** PCI
(lspci not available; here output of cat /proc/bus/pci/devices)
0000    80862578        0       e0000008        00000000        00000000        
00000000        00000000        00000000        00000000     08000000        
00000000        00000000        00000000        00000000        00000000        
00000000        agpgart-intel
0008    80862579        0       00000000        00000000        00000000        
00000000        00000000        00000000        00000000     00000000        
00000000        00000000        00000000        00000000        00000000        
00000000
0018    8086257b        0       00000000        00000000        00000000        
00000000        00000000        00000000        00000000     00000000        
00000000        00000000        00000000        00000000        00000000        
00000000
00e8    808624d2        10      00000000        00000000        00000000        
00000000        0000b001        00000000        00000000     00000000        
00000000        00000000        00000000        00000020        00000000        
00000000        uhci_hcd
00e9    808624d4        13      00000000        00000000        00000000        
00000000        0000b401        00000000        00000000     00000000        
00000000        00000000        00000000        00000020        00000000        
00000000        uhci_hcd
00ea    808624d7        12      00000000        00000000        00000000        
00000000        0000b801        00000000        00000000     00000000        
00000000        00000000        00000000        00000020        00000000        
00000000        uhci_hcd
00eb    808624de        10      00000000        00000000        00000000        
00000000        0000bc01        00000000        00000000     00000000        
00000000        00000000        00000000        00000020        00000000        
00000000        uhci_hcd
00ef    808624dd        17      fa200000        00000000        00000000        
00000000        00000000        00000000        00000000     00000400        
00000000        00000000        00000000        00000000        00000000        
00000000        ehci_hcd
00f0    8086244e        0       00000000        00000000        00000000        
00000000        00000000        00000000        00000000     00000000        
00000000        00000000        00000000        00000000        00000000        
00000000
00f8    808624d0        0       00000000        00000000        00000000        
00000000        00000000        00000000        00000000     00000000        
00000000        00000000        00000000        00000000        00000000        
00000000
00fa    808624d1        12      00000000        00000000        00000000        
00000000        0000f001        00000000        00000000     00000000        
00000000        00000000        00000000        00000010        00000000        
00000000        ata_piix
00fb    808624d3        11      00000000        00000000        00000000        
00000000        00000501        00000000        00000000     00000000        
00000000        00000000        00000000        00000020        00000000        
00000000        i801 smbus
00fd    808624d5        11      0000d801        0000dc01        fa201000        
fa202000        00000000        00000000        00000000     00000100        
00000040        00000200        00000100        00000000        00000000        
00000000        Intel ICH
0100    10024e48        10      e8000008        00009001        f9000000        
00000000        00000000        00000000        00000000     08000000        
00000100        00010000        00000000        00000000        00000000        
00020000
0101    10024e68        0       f0000008        f9010000        00000000        
00000000        00000000        00000000        00000000     08000000        
00010000        00000000        00000000        00000000        00000000        
00000000
0208    80861019        12      fa000000        00000000        0000a001        
00000000        00000000        00000000        00000000     00020000        
00000000        00000020        00000000        00000000        00000000        
00000000        e1000
0318    104c8023        14      fa104000        fa100000        00000000        
00000000        00000000        00000000        00000000     00000800        
00004000        00000000        00000000        00000000        00000000        
00000000        ohci1394

**** SCSI
/proc/scsi/scsi not available

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: SMP + Hyperthreading / Asus PCDL Deluxe / Kernel 2.4.x 2.6.x / Crash/Freeze
  2004-03-10 12:27 SMP + Hyperthreading / Asus PCDL Deluxe / Kernel 2.4.x 2.6.x / Crash/Freeze Richard Browning
@ 2004-03-10 16:10 ` Zwane Mwaikambo
  2004-03-11 13:04   ` Richard Browning
  0 siblings, 1 reply; 15+ messages in thread
From: Zwane Mwaikambo @ 2004-03-10 16:10 UTC (permalink / raw)
  To: Richard Browning; +Cc: linux-kernel

On Wed, 10 Mar 2004, Richard Browning wrote:

> **** SUMMARY
> Enabling hyperthreading on Asus PCDL Deluxe motherboard w/ 2xP4Xeon causes
> system freeze in short order.
>
> **** DESCRIPTION
> I have an Asus PCDL Deluxe P4Xeon motherboard which has a north/southbridge
> combination allowing system memory to run at 533MHz . The motherboard has the
> usual Asus onboard gigabit ethernet, AD1985 audio, Intel and Promise SATA
> controllers, firewire. All are enabled and operate. I am running dual 2.8GHz
> P4 Xeons.
>
> When hyperthreading is disabled the system is perfectly stable and usable. No
> operating artefacts seem to occur and SMP appears to workcorrectly.
>
> However when hyperthreading is enabled, the system operates for a brief period
> (enough for KDE to boot, for example) before halting. When operating from the
> command line it is usual to see a Machine Check Exception error immediately
> prior to system failure.
>
> **** ENVIRONMENT
> Asus PCDL Deluxe motherboard
> (http://usa.asus.com/products/server/srv-mb/pc-dl/overview.HTM)

Just to make sure, have you tried a bios upgrade?

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: SMP + Hyperthreading / Asus PCDL Deluxe / Kernel 2.4.x 2.6.x / Crash/Freeze
  2004-03-10 16:10 ` Zwane Mwaikambo
@ 2004-03-11 13:04   ` Richard Browning
  0 siblings, 0 replies; 15+ messages in thread
From: Richard Browning @ 2004-03-11 13:04 UTC (permalink / raw)
  To: Zwane Mwaikambo; +Cc: linux-kernel

On Wednesday 10 March 2004 16:10, Zwane Mwaikambo wrote:
> Just to make sure, have you tried a bios upgrade?

No, because the two BIOS upgrades available are minor boot-up UI 
modifications. I can do it though (<fx>purchases floppy drive</fx>) and I'll 
get back to you.

R

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: SMP + Hyperthreading / Asus PCDL Deluxe / Kernel 2.4.x 2.6.x / Crash/Freeze
  2004-03-12  7:07               ` Len Brown
  2004-03-12  8:24                 ` Richard Browning
@ 2004-03-18  3:01                 ` Richard Browning
  1 sibling, 0 replies; 15+ messages in thread
From: Richard Browning @ 2004-03-18  3:01 UTC (permalink / raw)
  To: Len Brown; +Cc: Zwane Mwaikambo, linux-kernel, Venkatesh Pallipadi

On Friday 12 March 2004 07:07, Len Brown wrote:
> Hmm, read that note too fast...
> Since the failure did not follow the package to the BSP socket
> (CPU0/CPU1), but instead stayed with the AP (CPU2/CPU3) socket, that
> suggests an issue with the MB rather than the processor itself.

Right then. I've just 'borrowed' the same motherboard (Asus PC-DL Deluxe) and 
CPUs from the local friendly computer place. I simply connected the hard 
drive to their combo and booted. SAME RESULT.

To confirm these (SEVERE) issues, I installed (deep breath, apologies, etc,) 
Windows XP Pro. Regrettably, the Micro$oft beast worked perfectly. Four 
processors in task manager, no hangs after several hours of 'doing stuff'.

I don't know what's going on with Linux and this motherboard. Is it the 
strangeness of Asus putting a Canterwood and Intel ICH5 chipset together to 
get the 533 FSB out of the Xeon?

The symptoms only show up if I'm doing 'dev'. In other words, I can boot into 
KDE, play music, watch DVDs and even play Enemy Territory - all with HT 
enabled. However AS SOON as I begin the configure/make/install cycle the 
system will hang. It's almost like an interrupt is gumming up the works 
somehow, but I lack the expertise to pinpoint it. For the record, I'm running 
a Radeon9800Pro graphics card.

I dunno why there haven't been more issues like this. Then again, most of the 
folk I hear on the Asus forums are using these mobos with Windoze.

What can I do to help you chaps get to the bottom of this? (Interestingly I 
note that turning off ACPI - not APIC - with HT enabled causes the kernel to 
not realise that HT is in fact enabled. I though the kernel used CPUIDs to 
work out whether HT was enabled?)

R

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: SMP + Hyperthreading / Asus PCDL Deluxe / Kernel 2.4.x 2.6.x / Crash/Freeze
  2004-03-12  7:07               ` Len Brown
@ 2004-03-12  8:24                 ` Richard Browning
  2004-03-18  3:01                 ` Richard Browning
  1 sibling, 0 replies; 15+ messages in thread
From: Richard Browning @ 2004-03-12  8:24 UTC (permalink / raw)
  To: Len Brown; +Cc: Zwane Mwaikambo, linux-kernel, Venkatesh Pallipadi

On Friday 12 March 2004 07:07, Len Brown wrote:
> Hmm, read that note too fast...
> Since the failure did not follow the package to the BSP socket
> (CPU0/CPU1), but instead stayed with the AP (CPU2/CPU3) socket, that
> suggests an issue with the MB rather than the processor itself.

But how is it possible that simply activating HT could cause this error? Is it 
not the BIOS/processor that determines HT support ... it operates correctly 
in SMP mode. Hm.

R

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: SMP + Hyperthreading / Asus PCDL Deluxe / Kernel 2.4.x 2.6.x / Crash/Freeze
  2004-03-12  6:27             ` Len Brown
@ 2004-03-12  7:07               ` Len Brown
  2004-03-12  8:24                 ` Richard Browning
  2004-03-18  3:01                 ` Richard Browning
  0 siblings, 2 replies; 15+ messages in thread
From: Len Brown @ 2004-03-12  7:07 UTC (permalink / raw)
  To: Richard Browning; +Cc: Zwane Mwaikambo, linux-kernel, Venkatesh Pallipadi

Hmm, read that note too fast...
Since the failure did not follow the package to the BSP socket
(CPU0/CPU1), but instead stayed with the AP (CPU2/CPU3) socket, that
suggests an issue with the MB rather than the processor itself.

-Len

On Fri, 2004-03-12 at 01:27, Len Brown wrote:
> On Thu, 2004-03-11 at 19:42, Richard Browning wrote:
> > On Friday 12 March 2004 00:36, Zwane Mwaikambo wrote:
> > > On Fri, 12 Mar 2004, Richard Browning wrote:
> > > > > For my own curiosity, does switching the processors around do anything?
> > > > > Those MCEs look confined to the non bootstrap processor package.
> > > >
> > > > Switched CPUs. This time I get the following:
> > > >
> > > > CPU3: Machine Check Exception: 000.0004
> > > > CPU2: Machine Check Exception: 000.0004
> > > > Bank 0: a20000008c010400
> > > > Kernel Panic: CPU context corrupt
> > > > In idle task - not syncing
> > > >
> > > > Note that the CPU# designations are swapped and that there's only one
> > > > Bank 0: message. Is this significant?
> > >
> > > Ok, but that's still on the same package so it's not moving with the
> > > processor, thanks. Could you also supply processor info from
> > > /proc/cpuinfo.
> > 
> > I suppose that's good (for me); indicates no hardware error?
> 
> MCE == hardware error.
> In this case un-recoverable.
> 
> I'll take a swing at decoding this, call the Coast Guard if I don't
> return in 30 minutes;-)
> 
> http://developer.intel.com/design/pentium4/manuals/25366813.pdf
> 
> > Machine Check Exception: 000.0004
> 
> fig 14-4 says this means that indeed, you have a valid MCE.
> 
> > Bank 0: a20000008c010400
> 
> fig 14-6 says:
> 63: valid register contents
> 61: UC -- processor did not correct the error
> 57: PCC -- Processor context corrupt (you're dead)
> 
> 0400 is the MCA error code
> 
> fig E2 says
> 10 - internal watchdog timeout.
> 26,27 -- TT -- Thread timeout indicator -- both threads timed out
> 
> > /proc/cpuinfo of course:
> > 
> > processor       : 0
> > vendor_id       : GenuineIntel
> > cpu family      : 15
> > model           : 2
> 
> I have no idea what causes this error, but it sure sounds specific to
> the processor, and specific to HT -- which matches your experiments. 
> I'd imagine that after you verify that you've got the latest BIOS for
> the board and the error persists that you should look into getting that
> specific processor replaced.
> 
> cheers,
> -Len
> 
> 


^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: SMP + Hyperthreading / Asus PCDL Deluxe / Kernel 2.4.x 2.6.x / Crash/Freeze
  2004-03-12  0:42           ` Richard Browning
@ 2004-03-12  6:27             ` Len Brown
  2004-03-12  7:07               ` Len Brown
  0 siblings, 1 reply; 15+ messages in thread
From: Len Brown @ 2004-03-12  6:27 UTC (permalink / raw)
  To: Richard Browning; +Cc: Zwane Mwaikambo, linux-kernel, Venkatesh Pallipadi

On Thu, 2004-03-11 at 19:42, Richard Browning wrote:
> On Friday 12 March 2004 00:36, Zwane Mwaikambo wrote:
> > On Fri, 12 Mar 2004, Richard Browning wrote:
> > > > For my own curiosity, does switching the processors around do anything?
> > > > Those MCEs look confined to the non bootstrap processor package.
> > >
> > > Switched CPUs. This time I get the following:
> > >
> > > CPU3: Machine Check Exception: 000.0004
> > > CPU2: Machine Check Exception: 000.0004
> > > Bank 0: a20000008c010400
> > > Kernel Panic: CPU context corrupt
> > > In idle task - not syncing
> > >
> > > Note that the CPU# designations are swapped and that there's only one
> > > Bank 0: message. Is this significant?
> >
> > Ok, but that's still on the same package so it's not moving with the
> > processor, thanks. Could you also supply processor info from
> > /proc/cpuinfo.
> 
> I suppose that's good (for me); indicates no hardware error?

MCE == hardware error.
In this case un-recoverable.

I'll take a swing at decoding this, call the Coast Guard if I don't
return in 30 minutes;-)

http://developer.intel.com/design/pentium4/manuals/25366813.pdf

> Machine Check Exception: 000.0004

fig 14-4 says this means that indeed, you have a valid MCE.

> Bank 0: a20000008c010400

fig 14-6 says:
63: valid register contents
61: UC -- processor did not correct the error
57: PCC -- Processor context corrupt (you're dead)

0400 is the MCA error code

fig E2 says
10 - internal watchdog timeout.
26,27 -- TT -- Thread timeout indicator -- both threads timed out

> /proc/cpuinfo of course:
> 
> processor       : 0
> vendor_id       : GenuineIntel
> cpu family      : 15
> model           : 2

I have no idea what causes this error, but it sure sounds specific to
the processor, and specific to HT -- which matches your experiments. 
I'd imagine that after you verify that you've got the latest BIOS for
the board and the error persists that you should look into getting that
specific processor replaced.

cheers,
-Len




^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: SMP + Hyperthreading / Asus PCDL Deluxe / Kernel 2.4.x 2.6.x / Crash/Freeze
  2004-03-12  0:36         ` Zwane Mwaikambo
  2004-03-12  0:42           ` Richard Browning
@ 2004-03-12  1:16           ` Richard Browning
  1 sibling, 0 replies; 15+ messages in thread
From: Richard Browning @ 2004-03-12  1:16 UTC (permalink / raw)
  To: Zwane Mwaikambo; +Cc: Len Brown, linux-kernel

Maybe it's worthwhile pointing out that this Asus mobo achieves the unusual 
Xeon 533MHz front side bus speed by combining the Intel875 Northbridge with 
the Canterwood chipset. Dunno if that's significant.

R

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: SMP + Hyperthreading / Asus PCDL Deluxe / Kernel 2.4.x 2.6.x / Crash/Freeze
  2004-03-12  0:36         ` Zwane Mwaikambo
@ 2004-03-12  0:42           ` Richard Browning
  2004-03-12  6:27             ` Len Brown
  2004-03-12  1:16           ` Richard Browning
  1 sibling, 1 reply; 15+ messages in thread
From: Richard Browning @ 2004-03-12  0:42 UTC (permalink / raw)
  To: Zwane Mwaikambo; +Cc: Len Brown, linux-kernel

On Friday 12 March 2004 00:36, Zwane Mwaikambo wrote:
> On Fri, 12 Mar 2004, Richard Browning wrote:
> > > For my own curiosity, does switching the processors around do anything?
> > > Those MCEs look confined to the non bootstrap processor package.
> >
> > Switched CPUs. This time I get the following:
> >
> > CPU3: Machine Check Exception: 000.0004
> > CPU2: Machine Check Exception: 000.0004
> > Bank 0: a20000008c010400
> > Kernel Panic: CPU context corrupt
> > In idle task - not syncing
> >
> > Note that the CPU# designations are swapped and that there's only one
> > Bank 0: message. Is this significant?
>
> Ok, but that's still on the same package so it's not moving with the
> processor, thanks. Could you also supply processor info from
> /proc/cpuinfo.

I suppose that's good (for me); indicates no hardware error?

/proc/cpuinfo of course:

processor       : 0
vendor_id       : GenuineIntel
cpu family      : 15
model           : 2
model name      : Intel(R) Xeon(TM) CPU 2.80GHz
stepping        : 7
cpu MHz         : 2807.537
cache size      : 512 KB
physical id     : 0
siblings        : 1
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe cid
bogomips        : 5537.79

processor       : 1
vendor_id       : GenuineIntel
cpu family      : 15
model           : 2
model name      : Intel(R) Xeon(TM) CPU 2.80GHz
stepping        : 7
cpu MHz         : 2807.537
cache size      : 512 KB
physical id     : 0
siblings        : 1
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe cid
bogomips        : 5603.32

R

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: SMP + Hyperthreading / Asus PCDL Deluxe / Kernel 2.4.x 2.6.x / Crash/Freeze
  2004-03-12  0:22       ` Richard Browning
@ 2004-03-12  0:36         ` Zwane Mwaikambo
  2004-03-12  0:42           ` Richard Browning
  2004-03-12  1:16           ` Richard Browning
  0 siblings, 2 replies; 15+ messages in thread
From: Zwane Mwaikambo @ 2004-03-12  0:36 UTC (permalink / raw)
  To: Richard Browning; +Cc: Len Brown, linux-kernel

On Fri, 12 Mar 2004, Richard Browning wrote:

> > For my own curiosity, does switching the processors around do anything?
> > Those MCEs look confined to the non bootstrap processor package.
>
> Switched CPUs. This time I get the following:
>
> CPU3: Machine Check Exception: 000.0004
> CPU2: Machine Check Exception: 000.0004
> Bank 0: a20000008c010400
> Kernel Panic: CPU context corrupt
> In idle task - not syncing
>
> Note that the CPU# designations are swapped and that there's only one Bank 0:
> message. Is this significant?

Ok, but that's still on the same package so it's not moving with the
processor, thanks. Could you also supply processor info from
/proc/cpuinfo.

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: SMP + Hyperthreading / Asus PCDL Deluxe / Kernel 2.4.x 2.6.x / Crash/Freeze
  2004-03-11 22:17     ` Zwane Mwaikambo
@ 2004-03-12  0:22       ` Richard Browning
  2004-03-12  0:36         ` Zwane Mwaikambo
  0 siblings, 1 reply; 15+ messages in thread
From: Richard Browning @ 2004-03-12  0:22 UTC (permalink / raw)
  To: Zwane Mwaikambo; +Cc: Len Brown, linux-kernel

On Thursday 11 March 2004 22:17, Zwane Mwaikambo wrote:
> On Thu, 11 Mar 2004, Richard Browning wrote:
> > I've now updated the BIOS to the latest version available on Asus' site.
> > The crash occurs even earlier - during bootup this time. Exactly:
> >
> > CPU2: Machine Check Exception: 000.0004
> > CPU3: Machine Check Exception: 000.0004
> > Bank 0: a20000008c010400Bank0: a20000008c010400
> > Kernel Panic: CPU context corrupt
> > In idle task - not syncing
> >
> > Again, disabling hyperthreading allows the system to operate normally.
>
> For my own curiosity, does switching the processors around do anything?
> Those MCEs look confined to the non bootstrap processor package.

Switched CPUs. This time I get the following:

CPU3: Machine Check Exception: 000.0004
CPU2: Machine Check Exception: 000.0004
Bank 0: a20000008c010400
Kernel Panic: CPU context corrupt
In idle task - not syncing

Note that the CPU# designations are swapped and that there's only one Bank 0: 
message. Is this significant?

R

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: SMP + Hyperthreading / Asus PCDL Deluxe / Kernel 2.4.x 2.6.x / Crash/Freeze
  2004-03-11 18:19   ` Richard Browning
@ 2004-03-11 22:17     ` Zwane Mwaikambo
  2004-03-12  0:22       ` Richard Browning
  0 siblings, 1 reply; 15+ messages in thread
From: Zwane Mwaikambo @ 2004-03-11 22:17 UTC (permalink / raw)
  To: Richard Browning; +Cc: Len Brown, linux-kernel

On Thu, 11 Mar 2004, Richard Browning wrote:

> I've now updated the BIOS to the latest version available on Asus' site. The
> crash occurs even earlier - during bootup this time. Exactly:
>
> CPU2: Machine Check Exception: 000.0004
> CPU3: Machine Check Exception: 000.0004
> Bank 0: a20000008c010400Bank0: a20000008c010400
> Kernel Panic: CPU context corrupt
> In idle task - not syncing
>
> Again, disabling hyperthreading allows the system to operate normally.

For my own curiosity, does switching the processors around do anything?
Those MCEs look confined to the non bootstrap processor package.

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: SMP + Hyperthreading / Asus PCDL Deluxe / Kernel 2.4.x 2.6.x / Crash/Freeze
  2004-03-11  6:50 ` Len Brown
  2004-03-11 13:38   ` Richard Browning
@ 2004-03-11 18:19   ` Richard Browning
  2004-03-11 22:17     ` Zwane Mwaikambo
  1 sibling, 1 reply; 15+ messages in thread
From: Richard Browning @ 2004-03-11 18:19 UTC (permalink / raw)
  To: Len Brown; +Cc: linux-kernel, Zwane Mwaikambo

On Thursday 11 March 2004 06:50, Len Brown wrote:
> On Wed, 2004-03-10 at 07:27, Richard Browning wrote:
> > When operating from the
> > command line it is usual to see a Machine Check Exception error
> > immediately prior to system failure.
>
> details?

I've now updated the BIOS to the latest version available on Asus' site. The 
crash occurs even earlier - during bootup this time. Exactly:

CPU2: Machine Check Exception: 000.0004
CPU3: Machine Check Exception: 000.0004
Bank 0: a20000008c010400Bank0: a20000008c010400
Kernel Panic: CPU context corrupt
In idle task - not syncing

Again, disabling hyperthreading allows the system to operate normally.

R

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: SMP + Hyperthreading / Asus PCDL Deluxe / Kernel 2.4.x 2.6.x / Crash/Freeze
  2004-03-11  6:50 ` Len Brown
@ 2004-03-11 13:38   ` Richard Browning
  2004-03-11 18:19   ` Richard Browning
  1 sibling, 0 replies; 15+ messages in thread
From: Richard Browning @ 2004-03-11 13:38 UTC (permalink / raw)
  To: Len Brown; +Cc: linux-kernel

On Thursday 11 March 2004 06:50, Len Brown wrote:
> On Wed, 2004-03-10 at 07:27, Richard Browning wrote:
> > When operating from the
> > command line it is usual to see a Machine Check Exception error
> > immediately prior to system failure.
>
> details?

CPU 2: Machine Check Exception: 000...0004
CPU 3: Machine Check Exception: 000...0004

Is what I get now. Previously I also got "Kernel Context Corrupt" in addition 
to the above.

The MCE error can be made to appear when, for example, I'm running a 
configure/compile cycle. I thought it might be a SATA issue so installed 
Mandrake on an IDE drive but I got the same error.

As an aside, I'm running Gentoo with CFLAGS=-O2 -march=pentium4 -pipe ... I 
was running CFLAGS=-O3 -march=pentium3 -mcpu=pentium4 -mmmx -ssse2 (and so 
on) with no difference whatsoever (probably shouldn't be a surprise bearing 
in mind the kernel is compiled with its own flags).

I've run MEMTEST with no errors reported. It's a very interesting problem, 
since with SMP only everything works okay. But SMP+Hyperthreading and, sooner 
rather than later, the thing will bomb.

R

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: SMP + Hyperthreading / Asus PCDL Deluxe / Kernel 2.4.x 2.6.x / Crash/Freeze
       [not found] <A6974D8E5F98D511BB910002A50A6647615F4B99@hdsmsx402.hd.intel.com>
@ 2004-03-11  6:50 ` Len Brown
  2004-03-11 13:38   ` Richard Browning
  2004-03-11 18:19   ` Richard Browning
  0 siblings, 2 replies; 15+ messages in thread
From: Len Brown @ 2004-03-11  6:50 UTC (permalink / raw)
  To: Richard Browning; +Cc: linux-kernel

On Wed, 2004-03-10 at 07:27, Richard Browning wrote:

> When operating from the 
> command line it is usual to see a Machine Check Exception error
> immediately prior to system failure.

details?



^ permalink raw reply	[flat|nested] 15+ messages in thread

end of thread, other threads:[~2004-03-18  3:02 UTC | newest]

Thread overview: 15+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-03-10 12:27 SMP + Hyperthreading / Asus PCDL Deluxe / Kernel 2.4.x 2.6.x / Crash/Freeze Richard Browning
2004-03-10 16:10 ` Zwane Mwaikambo
2004-03-11 13:04   ` Richard Browning
     [not found] <A6974D8E5F98D511BB910002A50A6647615F4B99@hdsmsx402.hd.intel.com>
2004-03-11  6:50 ` Len Brown
2004-03-11 13:38   ` Richard Browning
2004-03-11 18:19   ` Richard Browning
2004-03-11 22:17     ` Zwane Mwaikambo
2004-03-12  0:22       ` Richard Browning
2004-03-12  0:36         ` Zwane Mwaikambo
2004-03-12  0:42           ` Richard Browning
2004-03-12  6:27             ` Len Brown
2004-03-12  7:07               ` Len Brown
2004-03-12  8:24                 ` Richard Browning
2004-03-18  3:01                 ` Richard Browning
2004-03-12  1:16           ` Richard Browning

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®