acpi: bad write to port
Danny Braniss
danny at cs.huji.ac.il
Sun Jun 18 15:25:03 UTC 2006
> --nextPart1464934.38S1oUu9Sa
> Content-Type: text/plain;
> charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
> Content-Disposition: inline
>
> On Sunday 18 June 2006 11:02, Danny Braniss wrote:
> > hi,
> > some recent acpi changes seem to have provoked this:
> >
> > Copyright (c) 1992-2006 The FreeBSD Project.
> > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993,
> > 1994 The Regents of the University of California. All rights
> > reserved. FreeBSD 6.1-STABLE #7: Fri Jun 16 14:09:18 IDT 2006
> > danny at bsd:/r+d/obj/bsd/i386/r+d/6.1/src/sys/HUJI
> > Timecounter "i8254" frequency 1193182 Hz quality 0
> > CPU: Intel Pentium III (730.97-MHz 686-class CPU)
> > Origin =3D "GenuineIntel" Id =3D 0x686 Stepping =3D 6
> > =20
> > Features=3D0x383f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,
> >MCA,CMOV,P AT,PSE36,MMX,FXSR,SSE>
> > real memory =3D 266493952 (254 MB)
> > avail memory =3D 251117568 (239 MB)
> > kbd1 at kbdmux0
> > acpi0: <DELL GX115 > on motherboard
> > acpi: bad write to port 0x070 (8), val 0x55
> > acpi: bad read from port 0x071 (8)
> Unless you're seeing any functional changes it shouldn't be a problem. =20
> ACPI is just being more verbose about the BIOS doing bad things. If=20
> you have Windows installed you should see a similar error message in=20
> the system log.
no windows :-), but it seems to be working ok.
thanks,
danny
More information about the freebsd-stable
mailing list