Linux IA64 platform development
 help / color / mirror / Atom feed
From: "Mallick, Asit K" <asit.k.mallick@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] ACPI problems in 2.4.2-ia64-010228
Date: Tue, 06 Mar 2001 18:49:42 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590693005248@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005246@msgid-missing>

Looks like the FW is build 70 and was built on 8/15. Do you see this problem
with newer version of the FW also? We will look into this problem.

Thanks,
Asit


> -----Original Message-----
> From: Keith Owens [mailto:kaos@melbourne.sgi.com]
> Sent: Monday, March 05, 2001 5:31 PM
> To: davidm@hpl.hp.com
> Cc: Grover, Andrew; linux-ia64@linuxia64.org
> Subject: [Linux-ia64] ACPI problems in 2.4.2-ia64-010228
> 
> 
> BugSur 2 B1 cpus.  PAL 2213, BIOS W460GXBS2.86E.0070.B.200008150911.
> Kernel 2.4.2 + ia64-010228.  I am getting semi-random data in the acpi
> tables which more often than not will hang the machine during boot.
> 
> Linux version 2.4.2-ia64-010228-kdb 
> (kaos@sherman.melbourne.sgi.com) (gcc version 
> 2.96-ia64-000717 snap 001117) #17 SMP Tue Mar 6 11:28:03 EST 2001
> Warning: EFI system table major version mismatch: got 0.99, 
> expected 1.00
> EFI v0.99 by INTEL: SALsystab=0x3ff23a80 ACPI=0x3ffd9be0 
> MPS=0x3ffd0000 SMBIOS=0xf0020
> CPU 0: mapping PAL code [0x3ff40000-0x3ff7a000) into 
> [0xe000000030000000-0xe000000040000000)
> SAL v2.90: oem=INTEL   MSL     REF     SAL     , product=
> sal[0] - entry: pal_proc=0x3ff48010, sal_proc=0x3fe4bd70
> SAL: Platform features BusLock 
> sal[27] - wakeup type 0, 0xf0
> SAL: AP wakeup using external interrupt vector 0xf0
> CPU 0: 51 virtual and 44 physical address bits
> ACPI: Intel    RSDT   0.0
> Acpi cfg:bind to Boot time Acpi OSD
> Acpi cfg:initializ_subsysteme pass
> Acpi cfg:load firmware tables pass
> ACPI: install SCI 32 handler pass
> Acpi cfg:enable_subsystem pass
>       CPU 0 (0000:0000): Available.
>       CPU 1 (0000:0003): Available.
> Acpi Cfg: _PRT found. Need 336 bytes
> Acpi cfg:path=[\_SB_.PCI0]
> Acpi cfg:_BBN busnum is 0
>  Acpi cfg:no _STA: pci bus 0 exist
> KAO acpi_cf_add_to_pci_routing_tables e000000000013b88
> Acpi Cfg: _PRT found. Need 312 bytes
> Acpi cfg:path=[\_SB_.PCI1]
> Acpi cfg:_BBN busnum is 1
>  Acpi cfg:no _STA: pci bus 1 exist
> KAO acpi_cf_add_to_pci_routing_tables e000000000015d88
> Acpi Cfg: _PRT found. Need 216 bytes
> Acpi cfg:path=[\_SB_.PCI2]
> Acpi cfg:_BBN busnum is 2
>  Acpi cfg:_STA: pci bus 2 exist
> KAO acpi_cf_add_to_pci_routing_tables e000000000017488
> Acpi Cfg: _PRT found. Need 48 bytes
> Acpi cfg:path=[\_SB_.PCI3]
> Acpi cfg:_BBN busnum is 3
>  Acpi cfg:no _STA: pci bus 3 exist
> 
> On a clean boot, the first acpi table looks like this, note 
> the zero at
> 0xe000000000013cd8.
> 
> [0]kdb> md e000000000013b88
> 0xe000000000013b88 00000018 00000000 0004ffff 00000000	
> ........ÿÿ......
> 0xe000000000013b98 0000002d 00000000 00000018 00000000	
> -...............
> 0xe000000000013ba8 0005ffff 00000000 0000002c 00000000	
> ÿÿ......,.......
> 0xe000000000013bb8 00000018 00000000 0001ffff 00000000	
> ........ÿÿ......
> 0xe000000000013bc8 00000023 00000000 00000018 00000001	
> #...............
> 0xe000000000013bd8 0001ffff 00000000 00000022 00000000	
> ÿÿ......".......
> 0xe000000000013be8 00000018 00000002 0001ffff 00000000	
> ........ÿÿ......
> 0xe000000000013bf8 00000021 00000000 00000018 00000003	
> !...............
> 0xe000000000013c08 0001ffff 00000000 00000020 00000000	
> ÿÿ...... .......
> 0xe000000000013c18 00000018 00000000 0002ffff 00000000	
> ........ÿÿ......
> 0xe000000000013c28 00000027 00000000 00000018 00000001	
> '...............
> 0xe000000000013c38 0002ffff 00000000 00000026 00000000	
> ÿÿ......&.......
> 0xe000000000013c48 00000018 00000002 0002ffff 00000000	
> ........ÿÿ......
> 0xe000000000013c58 00000025 00000000 00000018 00000003	
> %...............
> 0xe000000000013c68 0002ffff 00000000 00000024 00000000	
> ÿÿ......$.......
> 0xe000000000013c78 00000018 00000000 0003ffff 00000000	
> ........ÿÿ......
> 0xe000000000013c88 0000002e 00000000 00000018 00000001	
> ................
> 0xe000000000013c98 0003ffff 00000000 0000002e 00000000	
> ÿÿ..............
> 0xe000000000013ca8 00000018 00000002 0003ffff 00000000	
> ........ÿÿ......
> 0xe000000000013cb8 0000002f 00000000 00000018 00000003	
> /...............
> 0xe000000000013cc8 0003ffff 00000000 0000002f 00000000	
> ÿÿ....../.......
> 0xe000000000013cd8 00000000 00000000 00000000 00000000	
> ................
> 0xe000000000013ce8 00000000 00000000 00000000 00000000	
> ................
> 0xe000000000013cf8 00000000 00000000 00000010 00000000	
> ................
> 
> On a failing boot, the first acpi table looks like this.  
> 0xe000000000013cd8
> contains 000000ee which sends acpi_cf_convert_prt_to_vectors 
> off to the
> wrong location, gets unaligned accesses and more often than not will
> hang the machine.
> 
> [0]kdb> md e000000000013b88
> 0xe000000000013b88 00000018 00000000 0004ffff 00000000	
> ........ÿÿ......
> 0xe000000000013b98 0000002d 00000000 00000018 00000000	
> -...............
> 0xe000000000013ba8 0005ffff 00000000 0000002c 00000000	
> ÿÿ......,.......
> 0xe000000000013bb8 00000018 00000000 0001ffff 00000000	
> ........ÿÿ......
> 0xe000000000013bc8 00000023 00000000 00000018 00000001	
> #...............
> 0xe000000000013bd8 0001ffff 00000000 00000022 00000000	
> ÿÿ......".......
> 0xe000000000013be8 00000018 00000002 0001ffff 00000000	
> ........ÿÿ......
> 0xe000000000013bf8 00000021 00000000 00000018 00000003	
> !...............
> 0xe000000000013c08 0001ffff 00000000 00000020 00000000	
> ÿÿ...... .......
> 0xe000000000013c18 00000018 00000000 0002ffff 00000000	
> ........ÿÿ......
> 0xe000000000013c28 00000027 00000000 00000018 00000001	
> '...............
> 0xe000000000013c38 0002ffff 00000000 00000026 00000000	
> ÿÿ......&.......
> 0xe000000000013c48 00000018 00000002 0002ffff 00000000	
> ........ÿÿ......
> 0xe000000000013c58 00000025 00000000 00000018 00000003	
> %...............
> 0xe000000000013c68 0002ffff 00000000 00000024 00000000	
> ÿÿ......$.......
> 0xe000000000013c78 00000018 00000000 0003ffff 00000000	
> ........ÿÿ......
> 0xe000000000013c88 0000002e 00000000 00000018 00000001	
> ................
> 0xe000000000013c98 0003ffff 00000000 0000002e 00000000	
> ÿÿ..............
> 0xe000000000013ca8 00000018 00000002 0003ffff 00000000	
> ........ÿÿ......
> 0xe000000000013cb8 0000002f 00000000 00000018 00000003	
> /...............
> 0xe000000000013cc8 0003ffff 00000000 0000002f 00000000	
> ÿÿ....../.......
> 0xe000000000013cd8 000000ee 00000000 00000000 00000000	
> î...............
> 0xe000000000013ce8 00000000 00000000 0001d1d1 00000000	
> ........ÑÑ......
> 0xe000000000013cf8 000100ee 00000000 00000010 00000000	
> î...............
> 
> Since we know the table size (Acpi Cfg: _PRT found. Need 336 bytes)
> should acpi use the table size instead of looking for a zero length?
> 
> 2.4.1-ia64-010131 with the same config and compiler works fine on this
> machine.  It may not be relevant but even when 2.4.2 boots past the
> acpi problem, /sbin/init spins in user space.  No idea why yet, it is
> very rare that I can get past acpi.
> 
> 
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64
> 



  reply	other threads:[~2001-03-06 18:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-06  1:30 [Linux-ia64] ACPI problems in 2.4.2-ia64-010228 Keith Owens
2001-03-06 18:49 ` Mallick, Asit K [this message]
2001-03-06 23:06 ` Keith Owens
2001-03-07  7:11 ` Keith Owens
2001-03-07 11:01 ` Keith Owens
2001-03-07 19:38 ` Jonathan_Kwahk

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=marc-linux-ia64-105590693005248@msgid-missing \
    --to=asit.k.mallick@intel.com \
    --cc=linux-ia64@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