Re: [acpi-jp 2704] Re: Odd ACPI behavior

From: Nate Lawson (nate_at_root.org)
Date: 09/29/03

  • Next message: Kevin Oberman: "Re: [acpi-jp 2704] Re: Odd ACPI behavior" 
    Date: Mon, 29 Sep 2003 13:33:06 -0700 (PDT)
To: acpi-jp@jp.FreeBSD.org

    On Mon, 29 Sep 2003, Kevin Oberman wrote:
    > > Date: Mon, 29 Sep 2003 16:04:25 -0400 (EDT)
    > > From: John Baldwin <jhb@FreeBSD.org>
    > >
    > > On 29-Sep-2003 Kevin Oberman wrote:
    > > > I recently noticed that, when I boot with ACPI on my IBM T30, I get
    > > > errors trying to probe the BIOS disabled sio1. This does not happen
    > > > under apm and happens twice(?) when booting with ACPI and happens even
    > > > though I have the line 'hint.sio.1.disabled="1"' in /boot/device.hints.
    > > >>From my dmesg:
    > > > sio0: type 16550A
    > > > sio1: configured irq 3 not in bitmap of probed irqs 0
    > > > sio1: port may not be enabled
    > > > acpi_cmbat0: <Control method Battery> on acpi0
    > > > acpi_cmbat1: <Control method Battery> on acpi0
    > > > acpi_acad0: <AC adapter> on acpi0
    > > > sio1: configured irq 3 not in bitmap of probed irqs 0
    > > > sio1: port may not be enabled
    > >
    > > Do you kldload a module at some point during your boot? If so, that
    > > would explain the double probe.
    >
    > Yes, it would, but I am not loading any kernel modules except the
    > slightly automatic loads of ACPI, itself and a few others which should
    > not cause a probe: ntfs, linux, linprocfs, and daemon_saver.

    ACPI attaches the bus twice. See sys/dev/acpica/acpi.c:

        /*
         * Scan all of the child devices we have created and let them probe/attach.
         */
        ACPI_DEBUG_PRINT((ACPI_DB_OBJECTS, "first bus_generic_attach\n"));
        bus_generic_attach(bus);

        /*
         * Some of these children may have attached others as part of their attach
         * process (eg. the root PCI bus driver), so rescan.
         */
        ACPI_DEBUG_PRINT((ACPI_DB_OBJECTS, "second bus_generic_attach\n"));
        bus_generic_attach(bus);

    -Nate
    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"

  • Next message: Kevin Oberman: "Re: [acpi-jp 2704] Re: Odd ACPI behavior"

    Relevant Pages

    • Re: Linux / BSD kernel module compatibility
      ... FreeBSD modules can be loaded after boot. ... See man kldload. ... Errr.you misunderstood. ...
      (comp.unix.bsd.freebsd.misc)
    • Re: ACPI autoload failed: no such file or directory
      ... is not include in the logs) ... >>after the boot process, i logged in and try this command ... yes, i know, but kldload doesn't found the file if i don't specify the ... i got the message in the log: "kernel: The ACPI ...
      (freebsd-current)
    • Re: ACPI autoload failed: no such file or directory
      ... is not include in the logs) ... >after the boot process, i logged in and try this command ... You cannot load acpi.ko from userland. ... >- kldload works with other modules in this directory. ...
      (freebsd-current)
    • Re: kernel panic on boot with compiled in fwip(4)
      ... > P.S. i have been using this kernel conf for quite a while without problems. ... but it prints early in the boot that module if_fwip ... then after the machine boots, i don't have fwip0 interface, nor if_fwip ... kldload: can't load if_fwip: File exists. ...
      (freebsd-current)
    • Re: 5.3 crash on boot
      ... On Thu, 2005-03-10 at 16:33 -0800, Kevin Oberman wrote: ... > Exactly where does it stop in the boot? ... Does the kernel load? ... > upgrade or a new install? ...
      (freebsd-stable)