-0166: *** Error: UtAllocate: Attempt to alloc

[C. Kukulies]

...ate zero bytes

The kernel message

-0166: *** Error: UtAllocate: Attempt to allocate zero bytes
-0166: *** Error: UtAllocate: Attempt to allocate zero bytes
-0166: *** Error: UtAllocate: Attempt to allocate zero bytes
-0166: *** Error: UtAllocate: Attempt to allocate zero bytes

clobbers the screen in bursts during startup for quite some time now.
I would like to ask if there is something I can do about it.
Upgrading (cvsup)? Edit some config files with senseful info?

AFAIK it has to do something with acpi, doesn't it?

--
Chris Christoph P. U. Kukulies kuku_at_physik.rwth-aachen.de
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

g++ problem

[C. Kukulies]

I tried to compile a virus-scanner for Linux that allows for scanning
Windoze PCs in a network for all sorts of recent viruses (RPC/DCOM and such).

http://www.enyo.de/fw/software/doscan

Compilation fails with the following:

kukuboo2k# gmake
g++ -g -O2 -Wall -I/usr/local/include -I. -I. -I./lib \
-MMD -MF src/doscan.d \
-c -o src/doscan.o src/doscan.cc
In file included from src/doscan.cc:28:
/usr/local/include/getopt.h:115: error: declaration of C function `int getopt()
   ' conflicts with
/usr/include/unistd.h:377: error: previous declaration `int getopt(int, char*
   const*, const char*)' here
gmake: *** [src/doscan.o] Error 1

I wonder where /usr/local/include comes from. If I remove that it compiles
smoothly.

Sorry, if this would turn out to be not -current specific.

--
Chris Christoph P. U. Kukulies kuku_at_physik.rwth-aachen.de

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

i386_set_ldt warnings

[C. Kukulies]

Some (kde) applications now have a warning appear in xconsole:

Warning: pid 595 used static ldt allocation.
See the i386_set_ldt man page for more info
Warning: pid 596 used static ldt allocation.
See the i386_set_ldt man page for more info

Should I worry about that? Rebuild KDE?

--
Chris Christoph P. U. Kukulies kukulies (at) rwth-aachen.de

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

panic with unloading nvidia.ko

[C. Kukulies]

I just got a kernel panic after making /usr/ports/x11/nvidia-driver.
I did a make, make reinstall. Then I did a kldunload nvidia.ko
and got:

nvidia0: detached
panic: malloc(9)/free(9) confusion.
Probably freeing with wrong type, but maybe not here.
Debugger(panic)
Stopped at Debugger+0x54:  xchgl   %ebx, in_Debugger.0

trace shows:

Debugger
panic
free
os_free
__nvsym00022
__nvsym00638
__nvsym00678
__nvsym00723
rm_shutdown_rm
nvidia_modevent
driver_module_handler
module_unload
linker_file_unload
kld_unload
syscall
Xint0x80


--
Chris Christoph P. U. Kukulies kuku_at_physik.rwth-aachen.de

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

panic with -current kernel ata_timeout

[C. Kukulies]

with a -current cvsup I'm getting a kernel panic
during boot:
ata_timout
soft_clock
ithread
fork_exit
fork_trampoline

__trap 0x1

--
Chris Christoph Kukulies kuku_at_physik.rwth-aachen.de
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

ad0: WARNING - WRITE_DMA recovered from missing interrupt

[C. Kukulies]

ad0: WARNING - WRITE_DMA recovered from missing interrupt
Got this on my Dell Inspiron 8000 while dhclient was running
interactively and wi0: busy bit won't clear was happening.

At the moment with a recently cvsuped -current wi0 on my
gateway (PCI-PCMCIA adapter card) seems to be broken as well as this
everlasting wi0: busy bit won't clear thing which breaks 
WLAN on my Dell Inspiron for weeks now.



___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

wi0: tx failed, retry limit exceeded

[C. Kukulies]

I moved my server to new hardware and upgraded to 5.0-current ( 3 weeks ago)
pppoe and my ADSL link is up and running since yesterday but my
local wireless home network still refuses to work. I have a PCI pccard adapter
with an ELSA (Lucent Orinoco) WLAN PCMCIA card which worked flawlessly
under 4.4.

Now I'm getting kernel messages

wi0: tx failed, retry limit exceeded.

--
Christoph Kukulies (please cc me, I'm currently not subscribed from the
address I'm now sending from)

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

sis chipset

[C. Kukulies]

My ASUS board has a SiS 963 chip and I would like to get rid from the extra
3COM card I have presently in my system.

Is there a chance to get the built in 100MBit network adapter in the chipset
working somehow?

--
Christoph Kukulies

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message