6300ESB watch-dog timer/apic support?

I have a system with a Supermicro X6DAL-G main-board on which I'm running RELENG_5_4. The following are from the output of `pciconf -vl`: [EMAIL PROTECTED]:29:4:class=0x088000 card=0x668015d9 chip=0x25ab8086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '6300ESB

pthread_key_create memory leakage in pthreads?

Hi, dmesg: FreeBSD 5.4-STABLE #0: Sun Sep 25 20:08:39 EEST 2005 I am using valgrind to check my program but it always seems to come with this message: ==8210== 600 bytes in 3 blocks are definitely lost in loss record 3 of 6 ==8210==at 0x3C03619F: malloc (in

Re: Advice sought on upgrading from 4.11-R to 5.4...

Doug Barton [EMAIL PROTECTED] wrote: I disagree that ignoring comments in the files is a good idea. There is no way for mergemaster to know for sure if the comment is material or not, that's the admin's job. Furthermore, it is non-trivial to automatically detect that a change is inside a

Problem About how to use shared posix semaphore

Hi, I always get the error message:Operation not permitted When I use sem_init set pshared argument equal 1. Compiling as : gcc -o sem_test sem_test.c -lc_r. My freebsd ver is release 5.4 p6. Test code appear below: 1 #include sys/types.h 2 #include string.h 3 #include

Re: Problem About how to use shared posix semaphore

On Thu, 2005-09-29 at 20:47 +0800, Gary Li-126 wrote: Hi, I always get the error message:Operation not permitted When I use sem_init set pshared argument equal 1. Compiling as : gcc -o sem_test sem_test.c -lc_r. My freebsd ver is release 5.4 p6. From sem_init(3): A non-zero value for

Re: pthread_key_create memory leakage in pthreads?

Lefteris Tsintjelis wrote: Hi, dmesg: FreeBSD 5.4-STABLE #0: Sun Sep 25 20:08:39 EEST 2005 I am using valgrind to check my program but it always seems to come with this message: ==8210== 600 bytes in 3 blocks are definitely lost in loss record 3 of 6 ==8210==at 0x3C03619F: malloc

Re: pthread_key_create memory leakage in pthreads?

Simon Barner wrote: Can you provide a (minimal) example where this happens? Also, what is the exact command line? valgrind --trace-children=yes --leak-check=yes --show-reachable=yes ./sql-m ==12024== Memcheck, a memory error detector for x86-linux. ==12024== Copyright (C) 2002-2004, and GNU

Re: pthread_key_create memory leakage in pthreads?

In the last episode (Sep 29), Lefteris Tsintjelis said: Simon Barner wrote: Can you provide a (minimal) example where this happens? Also, what is the exact command line? valgrind --trace-children=yes --leak-check=yes --show-reachable=yes ./sql-m ==12024== 200 bytes in 1 blocks are

Re: pthread_key_create memory leakage in pthreads?

Lefteris Tsintjelis wrote: Can you provide a (minimal) example where this happens? Also, what is the exact command line? valgrind --trace-children=yes --leak-check=yes --show-reachable=yes ./sql-m Two other things you can try to determine whether it's you code or a internal error in

Re: [PATCH] option to re-enable aggressive ATA probing

Tim Howe wrote: Tim Howe [EMAIL PROTECTED] writes: ata0-master: stat=0xd0 err=0xd0 lsb=0xd0 msb=0xd0 This turned out to be the key. Version 1.51 of ata-lowlevel.c added a check for stat0/1, err, lsb, and msb being identical. If they are, it aborts the probe. The attached patch creates

Re: 5.4-STABLE changes breaks IDE boot (was Re: 5.3 - 5.4 breaks ATA (Intel ICH2))

A new kernel based on sources of 9/28/2005 still fails to boot on a Toshiba 8100 with a UDMA33 IDE onboard controller. The parameters passed to atapci0 are different from those passed by the earlier kernel, and the system locks up this point. I'm not including the dmesg, etc., since