<[EMAIL PROTECTED]> wrote:
Hi,
After the update of em to 6.6.6 last, I experience watchdog timeouts on a
server running 6-STABLE.
I have two identical servers with Intel D915GAV boards. Both have Intel
PRO/1000 PCI-Express network cards.
Server balder:
em0: port
0xac00-0xac1f mem 0xff60-
On Sat, Oct 20, 2007 at 12:10:30AM -0400, Josh Carroll wrote:
> > There's another thread on this issue, although that thread seems to
> > apply to a specific version (of em(4) code, or of NIC PROM revision -- I
> > don't know, the dmesg output is somewhat ambiguous).
>
> Ah sorry, I did see that t
> There's another thread on this issue, although that thread seems to
> apply to a specific version (of em(4) code, or of NIC PROM revision -- I
> don't know, the dmesg output is somewhat ambiguous).
Ah sorry, I did see that thread, but did notice the em version was
different, and that it didn't a
On 20/10/2007, at 5:03 PM, Jeremy Chadwick wrote:
On Sat, Oct 20, 2007 at 11:21:10AM +1300, Philip Murray wrote:
"me too" on a Supermicro 5015MT+, although I notice my em0 is also
sharing
an interrupt with USB (uhci3)... not sure if that's the culprit.
I'm not aware of a 5015MT+ model. Ma
On Fri, Oct 19, 2007 at 11:24:44PM -0400, Josh Carroll wrote:
> Sorry, I should have also included dmesg output. The "not properly
> dismounted" errors are obviously from the last crash :)
There's another thread on this issue, although that thread seems to
apply to a specific version (of em(4) cod
On Sat, Oct 20, 2007 at 11:21:10AM +1300, Philip Murray wrote:
> "me too" on a Supermicro 5015MT+, although I notice my em0 is also sharing
> an interrupt with USB (uhci3)... not sure if that's the culprit.
I'm not aware of a 5015MT+ model. Maybe you mean 5015M-MT+ or
5015M-T+?
We have two 5015
Sorry, I should have also included dmesg output. The "not properly
dismounted" errors are obviously from the last crash :)
Here is /var/run/dmesg.boot:
Copyright (c) 1992-2007 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the
Hello,
I have managed to lock my (amd64, RELENG_7) machine up twice today. In
both cases, I was transferring a file to my laptop (in one case over
SMB, the other over FTP). Both resulted in a hard lock (no panic). One
of the lockups had an "em1: watchdog timeout" message on the console,
the other
OK, I will look into this as soon as I can.
Jack
On 10/19/07, Philip Murray <[EMAIL PROTECTED]> wrote:
>
> On 20/10/2007, at 1:06 AM, Goran Lowkrantz wrote:
>
> > Hi,
> >
> > After the update of em to 6.6.6 last, I experience watchdog timeouts
> > on a server running 6-STABLE.
> >
>
> "me too" o
Hey guys, I have LOCK_PROFILING done for a product based on FreeBSD-6,
this means I can relatively easily backport LOCK_PROFILING from
FreeBSD-7 to FreeBSD-6.
Do we want this?
I'd like to do it if people want it.
--
- Alfred Perlstein
___
freebsd-sta
On 20/10/2007, at 1:06 AM, Goran Lowkrantz wrote:
Hi,
After the update of em to 6.6.6 last, I experience watchdog timeouts
on a server running 6-STABLE.
"me too" on a Supermicro 5015MT+, although I notice my em0 is also
sharing an interrupt with USB (uhci3)... not sure if that's the cu
* Oleg Derevenetz <[EMAIL PROTECTED]> [071019 08:17] wrote:
> Hi all,
>
> Can anyone take a look on PR kern/104406 ? I got repeatable hang situation,
> but I can't obtain a kernel dump to get result of all show commands from
> here:
>
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/developer
On Thu, Oct 18, 2007 at 12:07:02PM -0700, Christopher Chen wrote:
> Is there a simple and easy reason why rpc.statd would mmap 1G? I've
> read the FAQ and understand why it would allocate 256M, but this one
> shows 1G--file.c in /usr/src/usr.sbin/rpc.statd is still set to
> allocate 256M, btw.
>
>
On 19 Oct 2007, at 8:04, Chris Chou wrote:
I saw the same message when upgrading from RELENG_6 to RELENG_7,
and it
disappeared when I re-installed the RELENG_7 kernel.
Was your user land already upgraded to RELENG_7 ? if concerned, find
the version 7 kldxref from /usr/obj and rerun it. ap
Hi all,
Can anyone take a look on PR kern/104406 ? I got repeatable hang situation, but I can't obtain a kernel dump to get result of all
show commands from here:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-deadlocks.html
After my break to debugger using C
Ruslan Ermilov wrote:
On Thu, Oct 18, 2007 at 09:06:55PM +0200, Philipp Ost wrote:
Vlad GALU wrote:
On 10/18/07, Philipp Ost <[EMAIL PROTECTED]> wrote:
Hi list,
I'm currently upgrading from 6.2-STABLE (13 Oct. 2007) to RELENG_7. I
did the following after csup'ing my sources:
# make kernel-
On Tuesday 23 January 2007 01:17:57 pm Guy Helmer wrote:
> Jack Vogel wrote:
> > On 1/23/07, Guy Helmer <[EMAIL PROTECTED]> wrote:
> >> Using FreeBSD 6.2, I'm having trouble with the Supermicro X7DBR-8+
> >> motherboard (dual Xeon 5130 CPUs on the Blackford chipset -
> >> http://www.supermicro.com/
On Thu, Oct 18, 2007 at 09:06:55PM +0200, Philipp Ost wrote:
> Vlad GALU wrote:
>> On 10/18/07, Philipp Ost <[EMAIL PROTECTED]> wrote:
>>> Hi list,
>>>
>>> I'm currently upgrading from 6.2-STABLE (13 Oct. 2007) to RELENG_7. I
>>> did the following after csup'ing my sources:
>>> # make kernel-toolc
<[EMAIL PROTECTED]> wrote:
Hi,
snip
When running netstat between servers balder and midgard, server balder
get watchdog timeouts and resets the connection for a few seconds.
Oct 19 13:12:47 balder kernel: em0: watchdog timeout -- resetting
s/netstat/netperf/
...
On 2007-10-19 10:48, Max Laier <[EMAIL PROTECTED]> wrote:
> Okay. libpcap 0.9.8 and tcpdump 3.9.8 are now imported into HEAD and
> RELENG_7. Is anyone eager to pull it down to RELENG_6 as well,
> because I don't have the resources available at the moment. The
> update was crucial to me in HEAD a
Hi,
After the update of em to 6.6.6 last, I experience watchdog timeouts on a
server running 6-STABLE.
I have two identical servers with Intel D915GAV boards. Both have Intel
PRO/1000 PCI-Express network cards.
Server balder:
em0: port
0xac00-0xac1f mem 0xff60-0xff61,0xff62-0x
Hi,
Looks like I found the problem and it was a local patch - ouch. Some
casts that worked in i386 didn't work on amd64 ... sigh.
Sorry for the noise.
--
Martin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/fre
A kdump output shows always the same output. The file descriptor '108/0x6c'
doesn't look very valid
--
36626 mimedefang RET kse_release 0
36626 mimedefang RET kse_release 0
36626 mime
Josh Carroll wrote:
I have noticed some performance discrepancies with ULE and 4BSD in
RELENG_7, specifically with ffmpeg. I have all the kernel debugging
options disabled, and as I understand it, the userland debugging is
all off by default in RELENG_7.
Here are a couple of additional benchmar
on 18/10/2007 17:29 Ivan Voras said the following:
> Krassimir Slavchev wrote:
>> Hi,
>>
>> Ivan Voras wrote:
>
>
>>> The same command works under root, and the appropriate klds are loaded:
>> Only superuser can load modules. If you try to load module by regular
>> user you will get: kldload: can
Hi Max,
On Fri, Oct 19, 2007 at 10:48:52AM +0200, Max Laier wrote:
> Okay. libpcap 0.9.8 and tcpdump 3.9.8 are now imported into HEAD and
> RELENG_7.
Thank you for updating these two components!
Regards,
Brix
--
Henrik Brix Andersen <[EMAIL PROTECTED]>
pgp2pFfzwjHEk.pgp
Description: PGP sig
Okay. libpcap 0.9.8 and tcpdump 3.9.8 are now imported into HEAD and
RELENG_7. Is anyone eager to pull it down to RELENG_6 as well, because I
don't have the resources available at the moment. The update was crucial
to me in HEAD and RELENG_7 to get a working pflog tcpdump, but RELENG_6
isn't
Quoting Kris Kennaway <[EMAIL PROTECTED]>:
Clifton Royston wrote:
On Tue, Oct 16, 2007 at 01:01:46PM -0700, Chris H. wrote:
excerpt from this list titled: NFS == lock && reboot, that I posted
follows:
--8<---SNIP---8<-SNIP-8<---
# uname -a
FreeBSD host.domain.tld 6.2-RELEASE
Hi everybody,
I'm trying to get mimedefang running on amd64. But unfortunatly the threaded
milter part ('mimedefang') does segfault after some time, normally 1-2 minutes.
pid 2331 (mimedefang), uid 1001: exited on signal 11 (core dumped)
gdb /idms/bin/mimedefang mimedefang-2331.core
#0 0x
29 matches
Mail list logo
