Re: 6.1 panic after approx. 49 days uptime

2006-07-17 Thread Kostik Belousov
On Sun, Jul 16, 2006 at 12:19:25PM +0300, Kostik Belousov wrote: On Sun, Jul 16, 2006 at 09:46:49AM +0100, Mark Knight wrote: Index: mount.h === RCS file: /usr/local/arch/ncvs/src/sys/sys/mount.h,v retrieving revision 1.210

Re: 6.1 panic after approx. 49 days uptime

2006-07-17 Thread Kostik Belousov
On Sun, Jul 16, 2006 at 09:46:49AM +0100, Mark Knight wrote: In message [EMAIL PROTECTED], Kostik Belousov [EMAIL PROTECTED] writes On Sun, Jul 16, 2006 at 09:32:47AM +0100, Mark Knight wrote: Just awoke to fine my home server (6.1-RELEASE) had panicked during its daily update of /usr/ports

Re: 6.1 panic after approx. 49 days uptime

2006-07-17 Thread Kostik Belousov
On Sun, Jul 16, 2006 at 09:32:47AM +0100, Mark Knight wrote: Just awoke to fine my home server (6.1-RELEASE) had panicked during its daily update of /usr/ports with an uptime of 49 days. Stack trace is here: http://www.knigma.org.uk/scratch/crash_160706.txt Looks file system related

Re: ATA problems again ...

2006-07-17 Thread Johan Ström
On 17 jul 2006, at 00.53, Mike Tancsa wrote: At 03:02 PM 14/07/2006, Miroslav Lachman wrote: After reboot (command reboot), system boot up with both disks attached and start autosynchronization. I do not know, if this is hw or sw error, I got Install the smartmontools from

HEADS UP: BIND9's resolver and reentrant version of netdb functions are MFC'ed

2006-07-17 Thread Hajimu UMEMOTO
Hi, I've just MFC'ed the BIND9's resolver stuff and reentrant version of netdb functions. It is known that some ports are confused by existence of reentrant functions. So, I've bumped __FreeBSD_version to 601103. ---BeginMessage--- ume 2006-07-17 10:09:59 UTC FreeBSD src repository

Two panics on recent 6.1-STABLE

2006-07-17 Thread Dominic Marks
Two panics, I've just had: I had just installed a fresh world+kernel, booted and then received the first panic. Then reset, booted again and shortly received the second (although they look identical to me). At the moment everything seems fine, sending this message from the machine in question.

Re: swiN: clock sio process taking 75% CPU

2006-07-17 Thread Gareth McCaughan
I wrote: About 6 minutes after booting (on two occasions; I don't guarantee that this doesn't vary), a process that appears in the output of ps as [swi4: clock sio] begins to use about 3/4 of the machine's CPU. I think it does so more or less instantaneously. It continues to do so

Re: ATA problems again ...

2006-07-17 Thread Mike Tancsa
At 05:59 AM 17/07/2006, Johan Ström wrote: On 17 jul 2006, at 00.53, Mike Tancsa wrote: At 03:02 PM 14/07/2006, Miroslav Lachman wrote: After reboot (command reboot), system boot up with both disks attached and start autosynchronization. I do not know, if this is hw or sw error, I got

Re: ATA problems again ...

2006-07-17 Thread Johan Ström
On 17 jul 2006, at 16.51, Mike Tancsa wrote: At 05:59 AM 17/07/2006, Johan Ström wrote: On 17 jul 2006, at 00.53, Mike Tancsa wrote: At 03:02 PM 14/07/2006, Miroslav Lachman wrote: After reboot (command reboot), system boot up with both disks attached and start autosynchronization. I do

Re: ATA problems again ...

2006-07-17 Thread Mike Tancsa
At 11:02 AM 17/07/2006, Johan Ström wrote: On 17 jul 2006, at 16.51, Mike Tancsa wrote: This at least rules out the disks being bad for the most part. It still could be bad cables, but if you changed those out than its doubtful. Perhaps try updating to RELENG_6 ? If its a gmirror issue, I

Re: ATA problems again ...

2006-07-17 Thread Miroslav Lachman
Mike Tancsa wrote: [..] Install the smartmontools from /usr/ports/sysutils/smartmontools/ and post the output of smartctl -a /dev/ad8 smartmontools was previously installed and running as daemon without any bad reports. I can not run smartctl -a /dev/ad8 now, because my server housing

ath driver transmits frames only after a low watermark is filled

2006-07-17 Thread Victor Semionov
Hello list, I have a wireless card with an Atheros 5212 chipset and I'm experiencing the following behavior under FreeBSD 6.1: TCP connections that consist of small short bursts of one-way (transmission) traffic often stall until traffic is received over another TCP connection. For example,

Re: HEADS UP: BIND9's resolver and reentrant version of netdb functions are MFC'ed

2006-07-17 Thread Doug Barton
Hajimu UMEMOTO wrote: Hi, I've just MFC'ed the BIND9's resolver stuff and reentrant version of netdb functions. It is known that some ports are confused by existence of reentrant functions. So, I've bumped __FreeBSD_version to 601103. This is very exciting stuff! Thanks for your hard work