public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Traby <stefan@hello-penguin.com>
To: Yaroslav Rastrigin <yarick@relex.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ACPI && vortex still broken in latest 2.4 and 2.6.0-test9
Date: Wed, 29 Oct 2003 19:47:58 +0100	[thread overview]
Message-ID: <20031029184758.GA1201@hello-penguin.com> (raw)
In-Reply-To: <200310291832.22650.yarick@relex.ru>

On Wed, Oct 29, 2003 at 06:32:22PM +0300, Yaroslav Rastrigin wrote:
> On Wednesday 29 October 2003 17:03, Matthias Andree wrote:
> > > Affected are at least
> > > IBM Thinkpad T21  http://lkml.org/lkml/2003/6/15/111
> > > IBM Thinkpad A21p (3c556B Laptop Hurricane)
> >
> > Might the problems you observe be related to the IBM BIOS?
> Yes. With IBM's DSDT, to be more specific. I've filed a bug in the bugzilla, 

Well, I could try a Dell BIOS on my A21p if buying a SCO-Linux license
doesn't fix the problem. :)

http://www.hello-penguin.com/thinkpad/
contains more info including a dump of /proc/acpi/dsdt
if somebody cares (to acpi_blacklist it).

Maybe this is interesting: It's a diff of lspci -vvvvvvvvv
without and with acpi enabled...

--- lspci-noacpi	2003-10-29 19:20:00.000000000 +0100
+++ lspci-acpi	2003-10-29 19:21:42.000000000 +0100
@@ -49,13 +49,13 @@
 
 00:03.0 Ethernet controller: 3Com Corporation 3c556B Hurricane CardBus (rev 20)
 	Subsystem: 3Com Corporation: Unknown device 6356
-	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B-
+	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
 	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
-	Latency: 80 (2500ns min, 2500ns max), Cache Line Size: 0x08 (32 bytes)
+	Latency: 64 (2500ns min, 2500ns max)
 	Interrupt: pin A routed to IRQ 9
 	Region 0: I/O ports at 1800 [size=256]
-	Region 1: Memory at f0101400 (32-bit, non-prefetchable) [size=128]
-	Region 2: Memory at f0101000 (32-bit, non-prefetchable) [size=128]
+	Region 1: [virtual] Memory at f0101400 (32-bit, non-prefetchable) [size=128]
+	Region 2: [virtual] Memory at f0101000 (32-bit, non-prefetchable) [size=128]
 	Expansion ROM at <unassigned> [disabled] [size=128K]
 	Capabilities: [50] Power Management version 2
 		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)

-- 

  ciao - 
    Stefan

  reply	other threads:[~2003-10-29 18:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-29 13:48 ACPI && vortex still broken in latest 2.4 and 2.6.0-test9 Stefan Traby
2003-10-29 14:03 ` Matthias Andree
2003-10-29 15:32   ` Yaroslav Rastrigin
2003-10-29 18:47     ` Stefan Traby [this message]
2003-10-29 20:14       ` Yaroslav Rastrigin

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=20031029184758.GA1201@hello-penguin.com \
    --to=stefan@hello-penguin.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yarick@relex.ru \
    /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