Date: Tue, 05 Dec 2006 19:11:43 +0900 (JST) From: Hiroki Sato <hrs@FreeBSD.org> To: jhb@FreeBSD.org Cc: lydianconcepts@gmail.com, stable@FreeBSD.org Subject: Re: strange behavior of ioapic on PDSME motherboard Message-ID: <20061205.191143.90827582.hrs@allbsd.org> In-Reply-To: <200612041200.27861.jhb@freebsd.org> References: <4571BE11.4030009@samsco.org> <20061204.125553.133857290.hrs@allbsd.org> <200612041200.27861.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
----Security_Multipart(Tue_Dec__5_19_11_43_2006_917)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit John Baldwin <jhb@freebsd.org> wrote in <200612041200.27861.jhb@freebsd.org>: jh> On Sunday 03 December 2006 22:55, Hiroki Sato wrote: jh> > Hiroki Sato <hrs@freebsd.org> wrote jh> > in <20061202.201139.35852412.hrs@allbsd.org>: jh> > John, are there any big changes of ioapic support between RELENG_6 jh> > and CURRENT? I would like your comments to narrow down the cause. jh> > The 7.0-CURRENT November snapshot could probe the mpt (as a very slow jh> > device, though), and both em and mpt worked with acpi/ioapic enabled. jh> > I had a look at the changes in sys/i386/i386, but I am not sure jh> > if which is likely (or not)... jh> jh> There aren't any non-cosmetic changes in the apic code between 6.x and HEAD. Okay, thanks. So these symptoms are not directly related to mpt(4) and apic code at least. I will continue to investigate what is the cause, anyway. -- | Hiroki SATO ----Security_Multipart(Tue_Dec__5_19_11_43_2006_917)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBFdUXhTyzT2CeTzy0RAhjPAJkBNcrhRJLKkhM/6IvabQVHLMO+zwCdHCXS A5h8nEahOuIaEFUTpE268RM= =9RuQ -----END PGP SIGNATURE----- ----Security_Multipart(Tue_Dec__5_19_11_43_2006_917)----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061205.191143.90827582.hrs>