Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 4 Dec 2005 22:05:59 +0100 (CET)
From:      "Julien Gabel" <jpeg@thilelli.net>
To:        "John Baldwin" <jhb@freebsd.org>
Cc:        freebsd-acpi@freebsd.org, freebsd-usb@freebsd.org, bug-followup@freebsd.org
Subject:   Re: usb/74989: (regression) Lost USB support between 5.2.1-RELEASE  and 5.3-RELEASE on K7T266 Pro2.
Message-ID:  <56639.192.168.1.20.1133730359.squirrel@webmail.thilelli.net>
In-Reply-To: <200512031626.59048.jhb@freebsd.org>
References:  <49704.192.168.1.18.1113475314.squirrel@webmail.thilelli.net> <200512020811.33720.jhb@freebsd.org> <62227.192.168.1.20.1133563026.squirrel@webmail.thilelli.net> <200512031626.59048.jhb@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
>> Ok.  I think you finally got it this time.  Applied this patch against
>> RELENG_6 and it seems to work fine now.  I build and installed the
>> kernel, set the loader.conf directives
>>  hint.acpi.0.disabled to 0
>>  hint.apic.0.disabled to 0
>> and reboot on the system... it works well now, thank you ;)

> Ok, fix committed.  It will be in 6.1 as well.

Good news, thanks!

>>>> (*) The boot disk seems not be able to be used for the root mount,
>>>> i.e. ufs:/dev/ad0s1a in my case.

>>> If you could get a verbose dmesg for this case using a serial console
>>> I'd be interested in looking at that too.

>> Certainly!  The output can be found at:
>>  http://www.thilelli.net/~jgabel/store/pub/PR/74989/serial.dmesg.boot-v
>>
>> Note: the kernel used for this boot was the just-previously-patched one.

> Ok, what happens here is that the $PIR code ends up using IRQ 14 for a
> virgin-routed link.  You can just use a tunable to override this like so:
>
> hw.pci.link.0x1.irq=12

Yes, this setting solved the problem with both ACPI and APIC support
disabled.

> That should make the vga adapter use irq 12 rather than irq 14.  If you
> have a BIOS setting that says 'enable VGA irq' you could also try
> turning that on.  However, you'd probably much rather be running with
> ACPI + APIC enabled anyway.

Sure... ;)

Just a little question though: what can i "expect", from now on, to have
ACPI and APIC enabled in the same time, rather than ACPI support alone
(without APIC)?

-- 
-jpeg.




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