From owner-acpi-jp@jp.freebsd.org  Thu Oct  4 02:50:17 2001
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id CAA44843;
	Thu, 4 Oct 2001 02:50:17 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from mass.dis.org (mass.dis.org [216.240.45.41])
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id CAA44838
	for <acpi-jp@jp.freebsd.org>; Thu, 4 Oct 2001 02:50:16 +0900 (JST)
	(envelope-from msmith@mass.dis.org)
Received: from mass.dis.org (localhost [127.0.0.1])
	by mass.dis.org (8.11.6/8.11.3) with ESMTP id f93I0DI01518
	for <acpi-jp@jp.freebsd.org>; Wed, 3 Oct 2001 11:00:13 -0700 (PDT)
	(envelope-from msmith@mass.dis.org)
Message-Id: <200110031800.f93I0DI01518@mass.dis.org>
X-Mailer: exmh version 2.1.1 10/15/1999
To: acpi-jp@jp.freebsd.org
In-reply-to: Your message of "Wed, 03 Oct 2001 11:57:06 EDT."
             <20011003115705.B1533@kanpc.gte.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 03 Oct 2001 11:00:12 -0700
From: Mike Smith <msmith@freebsd.org>
Reply-To: acpi-jp@jp.freebsd.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+010328
X-Sequence: acpi-jp 1328
Subject: [acpi-jp 1328] Re: CURRENT crashes in acpi on IBM ThnkPad 77ED 
Errors-To: owner-acpi-jp@jp.freebsd.org
Sender: owner-acpi-jp@jp.freebsd.org
X-Originator: msmith@freebsd.org


Is this with the 'oldcard' or 'newcard' drivers?

The fact that you were running into Fatal()s has me concerned that you 
might still have something going wrong under the hood, although there 
aren't any Fatal()s in the PCI interrupt link device methods.

> I replaced panic with print in OsdDebug.c and now notebook is
> able to boot and both cardbus and pcccard _appear_ to work.
> Unfortunately, is does look like interrupts are not being delivered
> to the PCMCIA cards divers, i.e when I insert my 3Com Megahertz Cardbus
> ethernet card, is is correctly recognized and initialized, but then
> immetiately starts to complain about watchdog timeouts. The same
> happens with an older 16bit 3Com Etherlink III card with both
> newcard and oldcard kernels.
> 
> For some weird reason ACPI decided to route interrupts for PCCARD to
> irq 3, not IRQ 10 and 11 as it happens under Windows 2000. I understand
> this happens because ACPI does not have an equivalent for a PCI $PIR
> table and just selects first IRQ from the list of available ones.
> I hacked kernel to prefer IRQs 10 and 11 for pccard and dmesg message
> did actually confirm, that IRQs were routed correctly, but that did
> not change the behavious I was seeing. Any idea what to try next?

-- 
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also.  But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view.  [Dr. Fritz Todt]
           V I C T O R Y   N O T   V E N G E A N C E


