From owner-freebsd-current Tue Jul 24 10:15: 7 2001 Delivered-To: freebsd-current@freebsd.org Received: from mass.dis.org (sat.dis.org [216.240.44.14]) by hub.freebsd.org (Postfix) with ESMTP id C5F6F37B407 for ; Tue, 24 Jul 2001 10:14:40 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.4/8.11.3) with ESMTP id f6NKbx201647; Mon, 23 Jul 2001 13:37:59 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200107232037.f6NKbx201647@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: "neckpain@nettaxi.com" Cc: current@freebsd.org Subject: Re: acpica malfunctions In-reply-to: Your message of "Mon, 23 Jul 2001 05:31:07 PDT." <200107231231.FAA09442@mail21.bigmailbox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Jul 2001 13:37:59 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > > 1. Acpica modules hangs in > > > AcpiRsCalculateByteStreamLength() called from > > > AcpiRsCreateByteStream() called from > > > AcpiRsSetSrsMethodData() called from > > > AcpiSetCurrentResources() from somewhere in acpi_pcib.c . > > > > > > The hang itself occurs at LinkedList->Id == 9 and LinkedList->Length > == 0 > > > . > > > > Can you replace &crsbuf with crsbuf in acpi_pcib.c at line 484? > > I think I should be passing a pointer to the buffer, not a pointer to a > > pointer. > > There's no &crsbuf in line 484 (not in rev 1.10, nor 1.11). > > Assuming you're talking about the one in line 478, it doesn't compile if you > change it to crsbuf from &crsbuf, since crsbuf is an ACPI_BUFFER, not > an (ACPI_BUFFER *). Um. Sorry about the line numbers, and yes, sorry about the confusion there; I just looked at it and it seemed wrong. I'd still like to know the allocation length for that buffer though; my last suspicion is that it doesn't contain any resources at all, and so we're overrunning it when we go to try to stuff an interrupt resource into it. If that's the case, it's easy to fix. If not, then we will have to go hunting snarks. Thanks. Mike -- ... 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message