Re: Core dump after RELENG_5_4 to RELENG_6_0

Core dump after RELENG_5_4 to RELENG_6_0 (kgdb) where #0 doadump () at pcpu.h:165 #1 0xc04d2f92 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:399 #2 0xc04d3228 in panic (fmt=0xc064717a "%s") at /usr/src/sys/kern/kern_shutdown.c:555 #3 0xc062a698 in trap_fatal (frame=0xc7b97c2c,

sym(4) broken on amd64 (Time to port new driver?)

Looks like it is broken for a while - "_sym_calloc2: failed to allocate HCB" is always there... And... Looks like Gerard Roudier havn't more interest in maintaining this driver - there is the second generation of the original driver into linux source three since 2001, which is newer ported to Fre

gdb konsole system crash

Hello all! Discovering troubles with kde-apps startup I've faced with interesting effect - starting of gdb konsole (as nonprivileged user) causes system crash. Here is an example: gdb konsole run In my case this method 100% rebooting system in 80 seconds (mysterious network wa

Re: Xen dom0 support

Le Tuesday 22 November 2005 23:17, Darcy Buskermolen a écrit : > Hello, > > I know Kip Macy was working on Xen support for FreeBSD. How is FreeBSD > Dom0 coming along as well as SMP support ? Hello, With the instructions on Kip's site or the patch included with the xen sources, it's possible to

getdirentries_args and other kernel syscall structures

Ok, I'va got a little question here. In the structure getdirentries_args, there seems to be duplicated fields that I'm not entirely sure what they do. Here's the definition of a structure verbatim from sys/sysproto.h: struct getdirentries_args { char fd_l_[PADL_(int)]; int fd; char fd_r

Xen dom0 support

Hello, I know Kip Macy was working on Xen support for FreeBSD. How is FreeBSD Dom0 coming along as well as SMP support ? -- Darcy Buskermolen Wavefire Technologies Corp. http://www.wavefire.com ph: 250.717.0200 fx: 250.763.1759 ___ freebsd-hackers

Re: FreeBSD Status Report Third Quarter 2005

When I initially wrote the Ports Status report I included information about a project that Edwin Groothuis created. At that time I neglected to get his approval for that text, and that was an oversight and a mistake on my part and I apologize. I did not intend for anyone to get the impression tha

Re: ATI drivers for FreeBSD - anything?

On Mon, 21 Nov 2005, Maxime Henrion wrote: Albert Vest wrote: On Sat, 19 Nov 2005 01:58:25 +0200 (EET) Vladimir Kushnir <[EMAIL PROTECTED]> wrote: Hi all, Is there any project on FreeBSD wrapper for ATI Linux drivers (like nVidia's used to be)? If so - I'd be more than happy to test (sorry

Re: Question about closeing and opening stdin

On Tuesday 22 November 2005 10:50, Michael C. Shultz wrote: > How do I close then open stdin and keep it set to the same terminal > as when it was closed? Everything I've tried so far has met with failure > accept this works sort of and I don't get why: > > signal( SIGALRM, MGPMrTimer ); > alarm(

Re: Core dump after RELENG_5_4 to RELENG_6_0

On Tue, Nov 22, 2005 at 06:09:51PM +0300, Igor wrote: > Core dump after RELENG_5_4 to RELENG_6_0 > > (kgdb) where > #0 doadump () at pcpu.h:165 > #1 0xc04d2f92 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:399 > #2 0xc04d3228 in panic (fmt=0xc064717a "%s") at > /usr/src/sys/kern/ker

Question about closeing and opening stdin

How do I close then open stdin and keep it set to the same terminal as when it was closed? Everything I've tried so far has met with failure accept this works sort of and I don't get why: signal( SIGALRM, MGPMrTimer ); alarm( 300 ); /* time out in 5 minutes */ answer = getc(stdin); the signa

Re: poll()/select()

On Tuesday 22 November 2005 04:19 am, Konstantin Prokazoff wrote: > Welcome, > > John, thanks for the answer. I'll test today bus_setup_intr() without > INTR_FAST flag, but how I remember, this cause to system heavy load for > interrupt processing ;( in my case. > My handler uses spin mutex

Re: poll()/select()

On Tuesday 22 November 2005 05:12 am, Konstantin Prokazoff wrote: > Now, have checking non-FAST handler. Have some interest moments, such as > error codes, like: > Short write: 0/15 (Programming error) > Write to 137 (fdno) failed: Programming error > Maybe server becomes overloaded? (4xE1, Xeon 3G

Core dump after RELENG_5_4 to RELENG_6_0

Core dump after RELENG_5_4 to RELENG_6_0 (kgdb) where #0 doadump () at pcpu.h:165 #1 0xc04d2f92 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:399 #2 0xc04d3228 in panic (fmt=0xc064717a "%s") at /usr/src/sys/kern/kern_shutdown.c:555 #3 0xc062a698 in trap_fatal (frame=0xc7b97c2c, ev

Re: 4.8 "Alternate system clock has died" error

On Tuesday 22 November 2005 04:35 am, Uwe Doering wrote: > Charles Sprickman wrote: > > On Tue, 22 Nov 2005, Uwe Doering wrote: > >> Charles Sprickman wrote: > >>> [...] > >>> So it certainly looks easy enough for me to change the first two > >>> sections of the diff referenced above, but I'm havin

Re: poll()/select()

Now, have checking non-FAST handler. Have some interest moments, such as error codes, like: Short write: 0/15 (Programming error) Write to 137 (fdno) failed: Programming error Maybe server becomes overloaded? (4xE1, Xeon 3G) Best regards, Konstantin Prokazoff Center Of Excellence, S_V_R Lt

Re: poll()/select()

Welcome, John, thanks for the answer. I'll test today bus_setup_intr() without INTR_FAST flag, but how I remember, this cause to system heavy load for interrupt processing ;( in my case. My handler uses spin mutexes to block inter-interrupting & sleep mutexes to block some structures now.

Re: 4.8 "Alternate system clock has died" error

Charles Sprickman wrote: On Tue, 22 Nov 2005, Uwe Doering wrote: Charles Sprickman wrote: [...] So it certainly looks easy enough for me to change the first two sections of the diff referenced above, but I'm having issues finding that last one in cpu_initclocks(). It looks like that section