Title: ¥ß§YÀ°±zºô¸ô¶}©±Àç·~°µ¥Í·N!!
dnjymxjjocxnu
¥ß§YÀ°±zºô¸ô¶}©±Àç·~°µ¥Í·N!!
2¤p®É§Ö³tºô¶»s§@¤Îקï!!
ºô¶»s§@¶W§C»ù¥unNT800¤¸.
§K¶Oºô§}!!ºô¯¸¤º®e¥i¤À:¤½¥q²¤¶.
Try disabling acpi and let me know what's what.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Hi!
I don't think that I like this behaviour:
alex@oink ~ $ ps ax | grep lpd
15328 ?? Ss 0:00.01 lpd -4
15329 ?? S 0:00.02 lpd -4
alex@oink ~ $ lpq
lpd: Host name for your address (fe80::250:baff:fed4:a512%xl0) unknown
alex@oink ~ $ ifconfig -a
rl0: flags=8843 mtu 1500
inet
Hi,
> On Sun, 30 Sep 2001 14:54:31 +0200
> Alexander Langer <[EMAIL PROTECTED]> said:
alex> I don't think that I like this behaviour:
alex> alex@oink ~ $ ps ax | grep lpd
alex> 15328 ?? Ss 0:00.01 lpd -4
alex> 15329 ?? S 0:00.02 lpd -4
alex> alex@oink ~ $ lpq
alex> lpd: Hos
With -current as of last night around 7pm PDT:
IdlePTD 4390912
initial pcb at 320920
panicstr: bremfree: bp 0xc68bf184 not locked
panic messages:
---
panic: blockable sleep lock (sx) allproc @
/usr/local/src/sys/kern/kern_proc.c:212
syncing disks... panic: bremfree: bp 0xc68bf184 not lo
On Tue, Sep 25, 2001 at 09:59:28AM -0700, Kazutaka YOKOTA wrote:
> yokota 2001/09/25 09:59:28 PDT
>
> Modified files:
> sys/isa psm.c atkbdc_isa.c
> Log:
> Yet another turn of workaround for psm/ACPI/PnP BIOS
> problems currently experienced in -CURRENT.
>
> Th
Ruslan Ermilov wrote:
> If this Yahoo! Messenger is the 4.x application, make sure to add
> COMPAT4X=TRUE to /etc/make.conf. This will remove old libc.so.4
> from /usr/lib and install proper one into /usr/lib/compat.
While this does install the appropriate libs, network apps from 4.x st
On Sun, 30 Sep 2001, Doug Barton wrote:
> With -current as of last night around 7pm PDT:
>
>
> IdlePTD 4390912
> initial pcb at 320920
> panicstr: bremfree: bp 0xc68bf184 not locked
> panic messages:
> ---
> panic: blockable sleep lock (sx) allproc @
> /usr/local/src/sys/kern/kern_proc.c:21
-current as of the last day or so- anyone else seen?
Sep 30 20:47:15 quarm ntpd[239]: kernel time discipline status change 2041
microuptime() went backwards (939.4410978 -> 938.949317)
microuptime() went backwards (1382.4391199 -> 1382.075447)
microuptime() went backwards (1382.4391190 -> 1382.2
>
> -current as of the last day or so- anyone else seen?
>
> Sep 30 20:47:15 quarm ntpd[239]: kernel time discipline status change 2041
> microuptime() went backwards (939.4410978 -> 938.949317)
Try turning off the ACPI timer:
debug.acpi.disable="timer"
in loader.conf and see if it goes away.
Cool. Yes. Will do. It also turns out that even with this being an SMP system
with IOAPIC that ACPI still shares an irq with isp0. How odd.
On Sun, 30 Sep 2001, Mike Smith wrote:
> >
> > -current as of the last day or so- anyone else seen?
> >
> > Sep 30 20:47:15 quarm ntpd[239]: kernel time
>> Modified files:
>> sys/isa psm.c atkbdc_isa.c
>> Log:
>> Yet another turn of workaround for psm/ACPI/PnP BIOS
>> problems currently experienced in -CURRENT.
>>
>> This should fix the problem that the PS/2 mouse is detected
>> twice if the acpi module is not loa
>
> Cool. Yes. Will do. It also turns out that even with this being an SMP system
> with IOAPIC that ACPI still shares an irq with isp0. How odd.
This is probably an artifact of the PCI interrupt swizzle; the ACPI
irq is typically an interrupt line out of the southbridge (where the "power
manage
Hi all,
As discussed on -arch, I've removed the UUCP utilities from the base
system, and they now live in the net/freebsd-uucp port. I have left
the cu utility behind, because it reportedly has capabilities not
supported by tip at this time. Ideally, it would be great if we can
get any missing
14 matches
Mail list logo
