Hi,
I found this in logs of 6.1 box that I admin this morning. The machine
keeps running after that.
--
wilx
+malloc(M_WAITOK) of "g_bio", forcing M_NOWAIT with the following non-sleepable
locks held:
+exclusive sleep mutex inp (tcpinp) r = 0 (0xc50c5d38) locked @
/usr/src/sys/netinet/tcp_usrreq
It may be a bit early but I switched to RELENG_6 fot that reason.
After I switched, it seems the number of interrupts increased a lot. When I do
'dump -0 -f - -L /somewhere | restore -r -f', I see hight interrupt rates which
I don't remember seeing in 6.1-RELEASE.
Is it too early to report inc
Pyun YongHyeon wrote:
On Wed, Aug 30, 2006 at 12:52:49PM +0400, Gleb Smirnoff wrote:
> On Wed, Aug 30, 2006 at 05:22:23PM +0900, Ganbold wrote:
> G> >On Wed, Aug 30, 2006 at 12:23:20PM +0900, Ganbold wrote:
> G> >G> Thanks a lot for your patch. Your patch fixes panic, however I still
see
> G
Just got this panic on my amd64 smp system running stable:
kernel trap 12 with interrupts disabled
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0x20
fault code = supervisor read, page not present
instruction pointer = 0x8:0x
On 8/30/06, Danny Braniss <[EMAIL PROTECTED]> wrote:
ever since 6.1 I've seen fluctuations in the performance of
the em (Intel(R) PRO/1000 Gigabit Ethernet).
motherboard OBN (On Board NIC)
--
1- Intel SE
Hi,
1) Have you made sure there are no NFS rexmits reported by nfsstat -c ?
2) I haven't run thruput tests lately, but when I tested NFS/UDP thruput a
few months ago, I routinely got over 70MB/s sequential read thruput
and over 80MB/s sequential write thruput (against filers). I use
Bryan Fullerton wrote:
> So... the releng web page indicates that RELENG_6 is frozen as of
> August 25th pending a 6.2R release on October 9th.
>
> I'm guessing, since there seem to still be lots of commits and there's
> no /releases/6.2R/ doc tree on the FreeBSD site, that these dates are
> no lo
So... the releng web page indicates that RELENG_6 is frozen as of
August 25th pending a 6.2R release on October 9th.
I'm guessing, since there seem to still be lots of commits and there's
no /releases/6.2R/ doc tree on the FreeBSD site, that these dates are
no longer accurate.
What is a valid ET
On Wed, Aug 30, 2006 at 11:50:12AM +0400, Gleb Smirnoff wrote:
> Pyun,
>
> On Wed, Aug 30, 2006 at 04:30:25PM +0900, Pyun YongHyeon wrote:
> P> ===
> P> RCS file: /home/ncvs/src/sys/dev/bge/if_bge.c,v
> P> retrieving revision
On Wed, Aug 30, 2006 at 12:52:49PM +0400, Gleb Smirnoff wrote:
> On Wed, Aug 30, 2006 at 05:22:23PM +0900, Ganbold wrote:
> G> >On Wed, Aug 30, 2006 at 12:23:20PM +0900, Ganbold wrote:
> G> >G> Thanks a lot for your patch. Your patch fixes panic, however I still
> see
> G> >G> bge0: firmware
test 1: writing to a NetApp filer via NFS/UDP
FreeBSD Linux
MegaBytes/sec
1- Average: 18.48 32.61
2- Average: 15.69 35.72
3- Average: 16.61 29.69
(interstingly, doing NFS/TCP instead of NFS/UDP shows an increas
Gleb Smirnoff wrote:
On Wed, Aug 30, 2006 at 05:26:07PM +0900, Ganbold wrote:
G> Gleb, Pyun,
G>
G> I'm a kind of bit confused here whose patch to choose.
G> Can you guys enlighten me in this regard?
Can you please merge them? You should take all the stuff that
prepares the dma_rw_ctl variable
ever since 6.1 I've seen fluctuations in the performance of
the em (Intel(R) PRO/1000 Gigabit Ethernet).
motherboard OBN (On Board NIC)
--
1- Intel SE7501WV2S Intel 82546EB::2.1
2- Inte
On Wed, Aug 30, 2006 at 05:26:07PM +0900, Ganbold wrote:
G> Gleb, Pyun,
G>
G> I'm a kind of bit confused here whose patch to choose.
G> Can you guys enlighten me in this regard?
Can you please merge them? You should take all the stuff that
prepares the dma_rw_ctl variable from my patch, and all t
On Wed, Aug 30, 2006 at 05:22:23PM +0900, Ganbold wrote:
G> >On Wed, Aug 30, 2006 at 12:23:20PM +0900, Ganbold wrote:
G> >G> Thanks a lot for your patch. Your patch fixes panic, however I still see
G> >G> bge0: firmware handshake timed out
G> >G> bge0: link state changed to DOWN
G> >G> messages.
G>
Gleb, Pyun,
I'm a kind of bit confused here whose patch to choose.
Can you guys enlighten me in this regard?
thanks,
Ganbold
Gleb Smirnoff wrote:
Pyun,
On Wed, Aug 30, 2006 at 04:30:25PM +0900, Pyun YongHyeon wrote:
P> ===
P>
Gleb, Pyun,
Gleb Smirnoff wrote:
Ganbold,
On Wed, Aug 30, 2006 at 12:23:20PM +0900, Ganbold wrote:
G> Thanks a lot for your patch. Your patch fixes panic, however I still see
G> bge0: firmware handshake timed out
G> bge0: link state changed to DOWN
G> messages.
And yesterday delphij@ have se
Ganbold,
On Wed, Aug 30, 2006 at 12:23:20PM +0900, Ganbold wrote:
G> Thanks a lot for your patch. Your patch fixes panic, however I still see
G> bge0: firmware handshake timed out
G> bge0: link state changed to DOWN
G> messages.
And yesterday delphij@ have sent me patch against "firmware handsh
Pyun,
On Wed, Aug 30, 2006 at 04:30:25PM +0900, Pyun YongHyeon wrote:
P> ===
P> RCS file: /home/ncvs/src/sys/dev/bge/if_bge.c,v
P> retrieving revision 1.91.2.16
P> diff -u -r1.91.2.16 if_bge.c
P> --- if_bge.c 10 Aug 2006 11:02:14 -0
Pyun YongHyeon wrote:
On Wed, Aug 30, 2006 at 12:23:20PM +0900, Ganbold wrote:
> Hi,
>
> Thanks a lot for your patch. Your patch fixes panic, however I still see
> bge0: firmware handshake timed out
> bge0: link state changed to DOWN
> messages.
>
> When I tried to use Oleg's if_bge.c,
On Wed, Aug 30, 2006 at 12:23:20PM +0900, Ganbold wrote:
> Hi,
>
> Thanks a lot for your patch. Your patch fixes panic, however I still see
> bge0: firmware handshake timed out
> bge0: link state changed to DOWN
> messages.
>
> When I tried to use Oleg's if_bge.c, rev. 1.140 in STABLE bui
21 matches
Mail list logo
