Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 6 Dec 2005 02:22:57 +0700
From:      Eugene Grosbein <eugen@kuzbass.ru>
To:        John Baldwin <jhb@freebsd.org>
Cc:        freebsd-acpi@freebsd.org
Subject:   Re: 5.4: pci_link problem on 440BX
Message-ID:  <20051205192257.GC75425@svzserv.kemerovo.su>
In-Reply-To: <200512021732.15866.jhb@freebsd.org>
References:  <20050513140240.GA25774@svzserv.kemerovo.su> <200512021732.15866.jhb@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
> > 6.0's GENERIC does not boot to single user with
> > debug.acpi.disabled="pci_link", fatal trap 12 occures: page fault while in
> > kernel mode,
> > fault virtual address 0x0, supervisor read, page not present
> > in acpi_pci_link_lookup+0x26.
> 
> I think I know what this is and this patch probably fixes the panic in the
> case that you use 'debug.acpi.disabled="pci_link"'
> 
> --- //depot/vendor/freebsd/src/sys/dev/acpica/acpi_pci_link.c   2005/11/23 16:40:40
> +++ //depot/user/jhb/acpipci/dev/acpica/acpi_pci_link.c 2005/12/02 22:28:08
> @@ -1011,6 +1011,9 @@
>  {
>         struct link *link;
> 
> +       if (acpi_disabled("pci_link"))
> +               return (PCI_INVALID_IRQ);
> +
>         ACPI_SERIAL_BEGIN(pci_link);
>         link = acpi_pci_link_lookup(dev, index);
>         if (link == NULL)
> 

6.0-RELEASE boots with this patch, ACPI enabled
and debug.acpi.disabled="pci_link", make buildworld started
but several minutes later kernel started to write to console:

ad4: req=0xc223d7d0 SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !!
ad4: req=0xc223d7d0 SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !!
ad4: req=0xc223d7d0 SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !!

Every 4 seconds another line is appears.

Ctrl-T now shows:

load: 0.07  cmd: sh 16681 [ufs] 0.00u 0.00s 0% 284k

I cannot login using another vty, getty hangs too:

login: root
load: 0.08  cmd: getty 549 [ufs] 0.00u 0.00s 0% 928k

6.0-RELEASE is installed on ad6, and ad4 holds /usr/obj mounted
from 4.11 installation. ad4 is partitioned to hold
4.11-STABLE, Windows 98SE and Windows XP, all three OSes boot
and run from ad4 without a problem. 6.0-RELEASE with GENERIC kernel
behaves not so well.

However, previously established outgoing ssh session works
and I'm writting this letter using this session and pasting messages
with mouse :-)

Eugene Grosbein



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051205192257.GC75425>