Re: Intel SE7500WV2 not working with ACPI

2003-12-03 Thread John Baldwin

On 02-Dec-2003 Brooks Davis wrote:
 On Tue, Dec 02, 2003 at 05:50:27PM -0500, John Baldwin wrote:
 
 On 25-Nov-2003 Brooks Davis wrote:
  Since the interrupt changes, my dual Xeons based on the SE7500WV2 board
  don't work with ACPI.  Specificly, the onboard nics (em0 and em1)
  appear to not be recieving interupts.  Instead, they continiously get
  watchdog timeouts.  In a stock current, this is an instant panic.  With
  a minor fix to the watchdog function, the system sees to be more or less
  funcitonal other then not having a network.  Disabling ACPI makes the
  nics work.  I have updated the BIOS to the latest version[0].
  
  I've included ACPI and non-ACPI dmesg output below.  What else is needed
  to diagnose this problem?  Any patches I should try?
 
 Since acpi0 failed to probe, ACPI isn't used to route interrupts.  However,
 the apic code expects ACPI to do that since it enumerated CPUs and I/O
 APICs.  You are just going to have to disable ACPI for now.
 
  acpi0: INTEL  SWV20on motherboard
  ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.SBRG.EC0_._REG] 
  (Node
  0xc29b4660),
  AE_NOT_EXIST
  acpi0: Could not initialise SystemIO handler: AE_NOT_EXIST
  device_probe_and_attach: acpi0 attach returned 6
 
 If you can get this fixed, then you can re-enable ACPI again.
 
 What I can't figure out is why this is failing since acpi was at least
 partialy working before.  For instance, soft power was definalty
 working.  Doesn't that depend on acpi attaching?

Yes.  What does a dmesg from a UP kernel or a kernel w/o 'device apic'
show?

-- 

John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/
Power Users Use the Power to Serve!  -  http://www.FreeBSD.org/


pgp0.pgp
Description: PGP signature


Re: Intel SE7500WV2 not working with ACPI

2003-12-03 Thread Nate Lawson
Brooks Davis wrote:
 Since acpi0 failed to probe, ACPI isn't used to route interrupts.  However,
 the apic code expects ACPI to do that since it enumerated CPUs and I/O
 APICs.  You are just going to have to disable ACPI for now.

  acpi0: INTEL  SWV20on motherboard
  ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.SBRG.EC0_._REG] 
  (Node 0xc29b4660), AE_NOT_EXIST
  acpi0: Could not initialise SystemIO handler: AE_NOT_EXIST
  device_probe_and_attach: acpi0 attach returned 6

 If you can get this fixed, then you can re-enable ACPI again.

 What I can't figure out is why this is failing since acpi was at least
 partialy working before.  For instance, soft power was definalty
 working.  Doesn't that depend on acpi attaching?

I plan on updating our ACPI-CA to the 20031202 dist after the code freeze
is over.  It has some important fixes, including this one:

---
Changed the initialization of Operation Regions during subsystem init to
perform two entire walks of the ACPI namespace; The first to initialize
the regions themselves, the second to execute the _REG methods.  This
fixed some interdependencies across _REG methods found on some machines.
---

You might be able to work around this problem by setting:
  debug.acpi.disable=ec
or
  debug.acpi.avoid=\_SB_.PCI0.SBRG

-Nate
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


RE: Intel SE7500WV2 not working with ACPI

2003-12-02 Thread John Baldwin

On 25-Nov-2003 Brooks Davis wrote:
 Since the interrupt changes, my dual Xeons based on the SE7500WV2 board
 don't work with ACPI.  Specificly, the onboard nics (em0 and em1)
 appear to not be recieving interupts.  Instead, they continiously get
 watchdog timeouts.  In a stock current, this is an instant panic.  With
 a minor fix to the watchdog function, the system sees to be more or less
 funcitonal other then not having a network.  Disabling ACPI makes the
 nics work.  I have updated the BIOS to the latest version[0].
 
 I've included ACPI and non-ACPI dmesg output below.  What else is needed
 to diagnose this problem?  Any patches I should try?

Since acpi0 failed to probe, ACPI isn't used to route interrupts.  However,
the apic code expects ACPI to do that since it enumerated CPUs and I/O
APICs.  You are just going to have to disable ACPI for now.

 acpi0: INTEL  SWV20on motherboard
 ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.SBRG.EC0_._REG] (Node 
 0xc29b4660),
 AE_NOT_EXIST
 acpi0: Could not initialise SystemIO handler: AE_NOT_EXIST
 device_probe_and_attach: acpi0 attach returned 6

If you can get this fixed, then you can re-enable ACPI again.

-- 

John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/
Power Users Use the Power to Serve!  -  http://www.FreeBSD.org/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Intel SE7500WV2 not working with ACPI

2003-12-02 Thread Brooks Davis
On Tue, Dec 02, 2003 at 05:50:27PM -0500, John Baldwin wrote:
 
 On 25-Nov-2003 Brooks Davis wrote:
  Since the interrupt changes, my dual Xeons based on the SE7500WV2 board
  don't work with ACPI.  Specificly, the onboard nics (em0 and em1)
  appear to not be recieving interupts.  Instead, they continiously get
  watchdog timeouts.  In a stock current, this is an instant panic.  With
  a minor fix to the watchdog function, the system sees to be more or less
  funcitonal other then not having a network.  Disabling ACPI makes the
  nics work.  I have updated the BIOS to the latest version[0].
  
  I've included ACPI and non-ACPI dmesg output below.  What else is needed
  to diagnose this problem?  Any patches I should try?
 
 Since acpi0 failed to probe, ACPI isn't used to route interrupts.  However,
 the apic code expects ACPI to do that since it enumerated CPUs and I/O
 APICs.  You are just going to have to disable ACPI for now.
 
  acpi0: INTEL  SWV20on motherboard
  ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.SBRG.EC0_._REG] 
  (Node 0xc29b4660),
  AE_NOT_EXIST
  acpi0: Could not initialise SystemIO handler: AE_NOT_EXIST
  device_probe_and_attach: acpi0 attach returned 6
 
 If you can get this fixed, then you can re-enable ACPI again.

What I can't figure out is why this is failing since acpi was at least
partialy working before.  For instance, soft power was definalty
working.  Doesn't that depend on acpi attaching?

-- Brooks

-- 
Any statement of the form X is the one, true Y is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529  9BF0 5D8E 8BE9 F238 1AD4


pgp0.pgp
Description: PGP signature


Intel SE7500WV2 not working with ACPI

2003-11-25 Thread Brooks Davis
Since the interrupt changes, my dual Xeons based on the SE7500WV2 board
don't work with ACPI.  Specificly, the onboard nics (em0 and em1)
appear to not be recieving interupts.  Instead, they continiously get
watchdog timeouts.  In a stock current, this is an instant panic.  With
a minor fix to the watchdog function, the system sees to be more or less
funcitonal other then not having a network.  Disabling ACPI makes the
nics work.  I have updated the BIOS to the latest version[0].

I've included ACPI and non-ACPI dmesg output below.  What else is needed
to diagnose this problem?  Any patches I should try?

-- Brooks

[0] In a way, I'm glad the BIOS update didn't fix the problem because
that would probably mean I'd have to flash another 70 machines.

Copyright (c) 1992-2003 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 5.1-CURRENT #1: Tue Nov 11 14:45:00 PST 2003
[EMAIL 
PROTECTED]:/usr/home/brooks/working/freebsd/p4/xname/sys/i386/compile/GENERIC
Preloaded elf kernel /boot/kernel/kernel at 0xc0a75000.
ACPI APIC Table: INTEL  SWV20   
Timecounter i8254 frequency 1193182 Hz quality 0
CPU: Intel(R) XEON(TM) CPU 2.20GHz (2193.54-MHz 686-class CPU)
  Origin = GenuineIntel  Id = 0xf24  Stepping = 4
  
Features=0x3febfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM
  Hyperthreading: 2 logical CPUs
real memory  = 1073676288 (1023 MB)
avail memory = 1033482240 (985 MB)
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
 cpu2 (AP): APIC ID:  6
 cpu3 (AP): APIC ID:  7
ioapic0 Version 2.0 irqs 0-23 on motherboard
ioapic1 Version 2.0 irqs 24-47 on motherboard
ioapic2 Version 2.0 irqs 48-71 on motherboard
lapic0: Forcing LINT1 to edge trigger
Pentium Pro MTRR support enabled
ACPI-0660: *** Warning: Type override - [DEB_] had invalid type (Integer) for 
Scope operator, changed to (Scope)
ACPI-0660: *** Warning: Type override - [MLIB] had invalid type (Integer) for 
Scope operator, changed to (Scope)
ACPI-0660: *** Warning: Type override - [DATA] had invalid type (String) for Scope 
operator, changed to (Scope)
ACPI-0660: *** Warning: Type override - [SIO_] had invalid type (String) for Scope 
operator, changed to (Scope)
ACPI-0660: *** Warning: Type override - [LEDP] had invalid type (String) for Scope 
operator, changed to (Scope)
ACPI-0660: *** Warning: Type override - [GPEN] had invalid type (String) for Scope 
operator, changed to (Scope)
ACPI-0660: *** Warning: Type override - [GPST] had invalid type (String) for Scope 
operator, changed to (Scope)
ACPI-0660: *** Warning: Type override - [WUES] had invalid type (String) for Scope 
operator, changed to (Scope)
ACPI-0660: *** Warning: Type override - [WUSE] had invalid type (String) for Scope 
operator, changed to (Scope)
ACPI-0660: *** Warning: Type override - [SBID] had invalid type (String) for Scope 
operator, changed to (Scope)
ACPI-0660: *** Warning: Type override - [SWCE] had invalid type (String) for Scope 
operator, changed to (Scope)
acpi0: INTEL  SWV20on motherboard
ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.SBRG.EC0_._REG] (Node 
0xc29b4660), AE_NOT_EXIST
acpi0: Could not initialise SystemIO handler: AE_NOT_EXIST
device_probe_and_attach: acpi0 attach returned 6
npx0: [FAST]
npx0: math processor on motherboard
npx0: INT 16 interface
pcibios: BIOS version 2.10
Using $PIR table, 19 entries at 0xc00f3060
pcib0: Host to PCI bridge at pcibus 0 on motherboard
pci0: PCI bus on pcib0
pci_cfgintr: 0:29 INTA BIOS irq 5
pci_cfgintr: 0:29 INTB BIOS irq 10
pci0: unknown at device 0.1 (no driver attached)
pcib1: PCIBIOS PCI-PCI bridge at device 3.0 on pci0
pci2: PCI bus on pcib1
pci2: base peripheral, interrupt controller at device 28.0 (no driver attached)
pcib2: PCIBIOS PCI-PCI bridge at device 29.0 on pci2
pci4: PCI bus on pcib2
pci2: base peripheral, interrupt controller at device 30.0 (no driver attached)
pcib3: PCIBIOS PCI-PCI bridge at device 31.0 on pci2
pci3: PCI bus on pcib3
pci_cfgintr: 3:7 INTA BIOS irq 5
pci_cfgintr: 3:7 INTB BIOS irq 5
em0: Intel(R) PRO/1000 Network Connection, Version - 1.7.16 port 0x2040-0x207f mem 
0xfeac-0xfead irq 5 at device 7.0 on pci3
em0:  Speed:N/A  Duplex:N/A
em1: Intel(R) PRO/1000 Network Connection, Version - 1.7.16 port 0x2000-0x203f mem 
0xfeae-0xfeaf irq 5 at device 7.1 on pci3
em1:  Speed:N/A  Duplex:N/A
pci0: unknown at device 3.1 (no driver attached)
uhci0: Intel 82801CA/CAM (ICH3) USB controller USB-A port 0x3020-0x303f irq 5 at 
device 29.0 on pci0
usb0: Intel 82801CA/CAM (ICH3) USB controller USB-A on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1: Intel 82801CA/CAM (ICH3) USB controller 

Re: Intel SE7500WV2 not working with ACPI

2003-11-25 Thread Nate Lawson
 acpi0: INTEL  SWV20on motherboard
 ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.SBRG.EC0_._REG] (Node 
 0xc29b4660), AE_NOT_EXIST
 acpi0: Could not initialise SystemIO handler: AE_NOT_EXIST
 device_probe_and_attach: acpi0 attach returned 6

This is the source of the problems.  When acpi0 fails to attach,
everything else is done through the legacy PCI code.  The question is, why
is it failing?  The above-mentioned EC method could indicate the problem
is in walking the namespace but we'll have to look at the ASL to be sure.

Please send a url to the output of:
 acpidump -t -d  brooks-Intel.asl

Also, build with options ACPI_DEBUG and set these in your loader.conf:

debug.acpi.layer=ACPI_ALL_COMPONENTS
debug.acpi.level=ACPI_LV_OPREGION

-Nate
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Intel SE7500WV2 not working with ACPI

2003-11-25 Thread Brooks Davis
On Tue, Nov 25, 2003 at 12:12:16PM -0800, Nate Lawson wrote:
  acpi0: INTEL  SWV20on motherboard
  ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.SBRG.EC0_._REG] 
  (Node 0xc29b4660), AE_NOT_EXIST
  acpi0: Could not initialise SystemIO handler: AE_NOT_EXIST
  device_probe_and_attach: acpi0 attach returned 6
 
 This is the source of the problems.  When acpi0 fails to attach,
 everything else is done through the legacy PCI code.  The question is, why
 is it failing?  The above-mentioned EC method could indicate the problem
 is in walking the namespace but we'll have to look at the ASL to be sure.
 
 Please send a url to the output of:
  acpidump -t -d  brooks-Intel.asl

http://people.freebsd.org/~brooks/debug/brooks-Intel.asl

 Also, build with options ACPI_DEBUG and set these in your loader.conf:
 
 debug.acpi.layer=ACPI_ALL_COMPONENTS
 debug.acpi.level=ACPI_LV_OPREGION

There's a new dmesg with this done at:

http://people.freebsd.org/~brooks/debug/dmesg-brooks-Intel

Thanks,
Brooks

-- 
Any statement of the form X is the one, true Y is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529  9BF0 5D8E 8BE9 F238 1AD4


pgp0.pgp
Description: PGP signature