public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Zehetbauer <thomasz@hostmaster.org>
To: Daniel Egger <degger@fhm.edu>
Cc: Linux Mailing List Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.8 and 2.6.9 Dual Opteron glitches
Date: Tue, 02 Nov 2004 17:58:47 +0100	[thread overview]
Message-ID: <1099414727.4618.11.camel@hostmaster.org> (raw)
In-Reply-To: <5AC1EEB8-2CD7-11D9-BF00-000A958E35DC@fhm.edu>

[-- Attachment #1: Type: text/plain, Size: 1838 bytes --]

Hi,

I am using a not-so-new Tyan Thunder K8W S2885 based Dual Opteron
System.

On Die, 2004-11-02 at 14:59 +0100, Daniel Egger wrote: 
> 1) 32 bit kernel HPET calibration hang: If the kernel is compiled

Cannot tell as I am using a 64-bit kernel without HPET. Can someone
maybe tell me which applications use HPET yet?

> 2) 64 bit kernel vgettimeofday panic: The kernel panics in

Cannot confirm this, both 2.6.8.1 and 2.6.9 boot OK.

> 3) Interrupt distribution 32 bit vs. 64 bit. Below is a copy of the

Cannot confirm this, interrupts seem to be almost equally distributed
with 64-bit kernel and irqbalance running. Did you note that x86_64 does
not provide in-kernel IRQ balancing.

           CPU0       CPU1
  0:    2921345    2988327    IO-APIC-edge  timer
  1:       5767       5414    IO-APIC-edge  i8042
  3:          2        147    IO-APIC-edge  serial
  4:      23806      21183    IO-APIC-edge  serial
  8:          2         37    IO-APIC-edge  rtc
  9:          0          0   IO-APIC-level  acpi
 14:      77847      72327    IO-APIC-edge  ide0
 15:      21317      29959    IO-APIC-edge  ide1
 16:     216766     217251   IO-APIC-level  EMU10K1, mga@pci:0000:05:00.0
 17:          0          0   IO-APIC-level  AMD AMD8111
 19:     182493     182216   IO-APIC-level  ohci_hcd, ohci_hcd
 24:     317611       1085   IO-APIC-level  eth0
NMI:          0          0
LOC:    5908168    5908259
ERR:          0
MIS:          0

> 4) ACPI powermanagement (32bit and 64bit): No matter which ACPI options

AFAIK power management is almost unsupported on SMP systems.

Tom

-- 
  T h o m a s   Z e h e t b a u e r   ( TZ251 )
  PGP encrypted mail preferred - KeyID 96FFCB89
      finger thomasz@hostmaster.org for key

Quantum Mechanics is God's version of "Trust me."





[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 481 bytes --]

  reply	other threads:[~2004-11-02 17:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-02 13:59 2.6.8 and 2.6.9 Dual Opteron glitches Daniel Egger
2004-11-02 16:58 ` Thomas Zehetbauer [this message]
2004-11-02 17:55   ` Tomas Carnecky
2004-11-02 21:52     ` Thomas Zehetbauer
2004-11-02 22:37   ` Daniel Egger
2004-11-02 21:53 ` Rafael J. Wysocki
2004-11-06 23:06   ` Christopher E. Brown
2004-11-02 21:56 ` Jesse Pollard
     [not found] <5AC1EEB8-2CD7-11D9-BF00-000A958E35DC@fhm.edu.suse.lists.linux.kernel>
2004-11-03  5:06 ` Andi Kleen
2004-11-03 10:53   ` Daniel Egger
2004-11-03 11:05     ` Andi Kleen
2004-11-03 15:06       ` Jesse Pollard

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=1099414727.4618.11.camel@hostmaster.org \
    --to=thomasz@hostmaster.org \
    --cc=degger@fhm.edu \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox