Re: new FreeBSD-webpage

[Jamie Heckford]

Would just like to say I think the new site looks great, well done and 
thanks to all the people that have donated spare time to work on this.


Maybe all the moaning minnies would like to submit a URL where they have 
put hardwork into making an alternative site for us all to see, instead 
of poking at the current one.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: 5.4-RC2 freezing - ATA related?

[Jamie Heckford]

Jamie Heckford wrote:

Another one... looks completly different :-(

[GDB will not be able to debug user-mode threads: 
/usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"]

GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you 
are
welcome to change it and/or distribute copies of it under certain 
conditions.

Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-marcel-freebsd".
#0  doadump () at pcpu.h:160
160 __asm __volatile("movl %%fs:0,%0" : "=r" (td));
(kgdb) bt full
#0  doadump () at pcpu.h:160
No locals.
#1  0xc04fac8a in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:410
first_buf_printf = 1
#2  0xc04faf50 in panic (fmt=0xc06c06db 
"softdep_deallocate_dependencies: dangling deps")

at /usr/src/sys/kern/kern_shutdown.c:566
td = (struct thread *) 0xc357fd80
bootopt = 260
newpanic = 1
ap = 0xc357fd80 "\\\214\215ÃðjOÃ"
buf = "softdep_deallocate_dependencies: dangling deps", '\0' 


#3  0xc061cbfe in softdep_deallocate_dependencies (bp=0x0)
at /usr/src/sys/ufs/ffs/ffs_softdep.c:5961
No locals.
#4  0xc053c8f4 in brelse (bp=0xd77932d4) at buf.h:431
No locals.
#5  0xc054bd24 in flushbuflist (blist=0xd77932d4, flags=0, 
vp=0xc4bf9630, slpflag=0,

slptimeo=0, errorp=0x0) at /usr/src/sys/kern/vfs_subr.c:1101
bp = (struct buf *) 0xd77932d4
nbp = (struct buf *) 0xd75948f0
found = 1
#6  0xc054b987 in vinvalbuf (vp=0xc4bf9630, flags=0, cred=0x0, td=0x0, 
slpflag=0,

slptimeo=0) at /usr/src/sys/kern/vfs_subr.c:987
blist = (struct buf *) 0x0
error = 0
object = 0xc04efc79
#7  0xc054e85c in vclean (vp=0xc4bf9630, flags=8, td=0xc357fd80)
at /usr/src/sys/kern/vfs_subr.c:2479
---Type  to continue, or q  to quit---
active = 0
#8  0xc054eeb5 in vgonel (vp=0xc4bf9630, td=0xc357fd80)
at /usr/src/sys/kern/vfs_subr.c:2697
No locals.
#9  0xc054a9f2 in vlrureclaim (mp=0xc35b3c00) at pcpu.h:157
vp = (struct vnode *) 0xc4bf9630
done = 0
trigger = 10
usevnodes = 0
count = 7
#10 0xc054ac66 in vnlru_proc () at /usr/src/sys/kern/vfs_subr.c:598
mp = (struct mount *) 0xc35b3c00
nmp = (struct mount *) 0xc35b3c00
done = 5887
p = (struct proc *) 0xc38d8c5c
td = (struct thread *) 0xc357fd80
#11 0xc04e67e8 in fork_exit (callout=0xc054aa98 , arg=0x0, 
frame=0xe68aad38)

at /usr/src/sys/kern/kern_fork.c:791
p = (struct proc *) 0xc38d8c5c
td = (struct thread *) 0x0
#12 0xc066746c in fork_trampoline () at 
/usr/src/sys/i386/i386/exception.s:209

No locals.
(kgdb)

panic: softdep_deallocate_dependencies: dangling deps
Uptime: 10h26m14s
Dumping 2047 MB
 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 256 272 288 304 
320 336 352 368 384 400 416 432 448 464 480 496 512 528 544 560 576 592 
608 624 640 656 672 688 704 720 736 752 768 784 800 816 832 848 864 880 
896 912 928 944 960 976 992 1008 1024 1040 1056 1072 1088 1104 1120 1136 
1152 1168 1184 1200 1216 1232 1248 1264 1280 1296 1312 1328 1344 1360 
1376 1392 1408 1424 1440 1456 1472 1488 1504 1520 1536 1552 1568 1584 
1600 1616 1632 1648 1664 1680 1696 1712 1728 1744 1760 1776 1792 1808 
1824 1840 1856 1872 1888 1904 1920 1936 1952 1968 1984 2000 2016 2032(kgdb)


Would be really grateful if anyone could suggest anything, again it 
appears to happen around the time periodic runs (but has happened 
randomly under load, not sure if this is a red herring tho)


If anyone needs anymore info, more than happy to oblige.

Cheers



Is there anyway this could be triggered by a filesystem becoming full.?

--
Jamie Heckford
Network Manager
Trident Microsystems Ltd.

t: +44(0)1737-780790
f: +44(0)1737-771908
w: http://www.trident-uk.co.uk/
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: 5.4-RC2 freezing - ATA related?

[Jamie Heckford]

Jamie Heckford wrote:

On Wed, May 18, 2005 at 03:54:59PM -0700, Doug White wrote:


On Wed, 18 May 2005, Jamie Heckford wrote:



Hi Peter,

On Thu, May 19, 2005 at 05:53:12AM +1000, Peter Jeremy wrote:


On Wed, 2005-May-18 16:03:16 +0100, Jamie Heckford wrote:


Managed to get a dump on our system for a similar prob we are getting:


That traceback looks like a panic, not a deadlock.  What was the panic
message?


Only have remote access to the box im afraid, is there anyway I can obtain
the panic message?


"print msgbuf" should do it


Another one... looks completly different :-(

[GDB will not be able to debug user-mode threads: 
/usr/lib/libthread_db.so: Undefined symbol 
"ps_pglobal_lookup"]

GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain 
conditions.

Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-marcel-freebsd".
#0  doadump () at pcpu.h:160
160 __asm __volatile("movl %%fs:0,%0" : "=r" (td));
(kgdb) bt full
#0  doadump () at pcpu.h:160
No locals.
#1  0xc04fac8a in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:410
first_buf_printf = 1
#2  0xc04faf50 in panic (fmt=0xc06c06db 
"softdep_deallocate_dependencies: dangling deps")

at /usr/src/sys/kern/kern_shutdown.c:566
td = (struct thread *) 0xc357fd80
bootopt = 260
newpanic = 1
ap = 0xc357fd80 "\\\214\215ÃðjOÃ"
buf = "softdep_deallocate_dependencies: dangling deps", '\0' 


#3  0xc061cbfe in softdep_deallocate_dependencies (bp=0x0)
at /usr/src/sys/ufs/ffs/ffs_softdep.c:5961
No locals.
#4  0xc053c8f4 in brelse (bp=0xd77932d4) at buf.h:431
No locals.
#5  0xc054bd24 in flushbuflist (blist=0xd77932d4, flags=0, 
vp=0xc4bf9630, slpflag=0,

slptimeo=0, errorp=0x0) at /usr/src/sys/kern/vfs_subr.c:1101
bp = (struct buf *) 0xd77932d4
nbp = (struct buf *) 0xd75948f0
found = 1
#6  0xc054b987 in vinvalbuf (vp=0xc4bf9630, flags=0, cred=0x0, td=0x0, 
slpflag=0,

slptimeo=0) at /usr/src/sys/kern/vfs_subr.c:987
blist = (struct buf *) 0x0
error = 0
object = 0xc04efc79
#7  0xc054e85c in vclean (vp=0xc4bf9630, flags=8, td=0xc357fd80)
at /usr/src/sys/kern/vfs_subr.c:2479
---Type  to continue, or q  to quit---
active = 0
#8  0xc054eeb5 in vgonel (vp=0xc4bf9630, td=0xc357fd80)
at /usr/src/sys/kern/vfs_subr.c:2697
No locals.
#9  0xc054a9f2 in vlrureclaim (mp=0xc35b3c00) at pcpu.h:157
vp = (struct vnode *) 0xc4bf9630
done = 0
trigger = 10
usevnodes = 0
count = 7
#10 0xc054ac66 in vnlru_proc () at /usr/src/sys/kern/vfs_subr.c:598
mp = (struct mount *) 0xc35b3c00
nmp = (struct mount *) 0xc35b3c00
done = 5887
p = (struct proc *) 0xc38d8c5c
td = (struct thread *) 0xc357fd80
#11 0xc04e67e8 in fork_exit (callout=0xc054aa98 , arg=0x0, 
frame=0xe68aad38)

at /usr/src/sys/kern/kern_fork.c:791
p = (struct proc *) 0xc38d8c5c
td = (struct thread *) 0x0
#12 0xc066746c in fork_trampoline () at 
/usr/src/sys/i386/i386/exception.s:209

No locals.
(kgdb)

panic: softdep_deallocate_dependencies: dangling deps
Uptime: 10h26m14s
Dumping 2047 MB
 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 256 272 288 304 
320 336 352 368 384 400 416 432 448 464 480 496 512 528 544 560 576 592 
608 624 640 656 672 688 704 720 736 752 768 784 800 816 832 848 864 880 
896 912 928 944 960 976 992 1008 1024 1040 1056 1072 1088 1104 1120 1136 
1152 1168 1184 1200 1216 1232 1248 1264 1280 1296 1312 1328 1344 1360 
1376 1392 1408 1424 1440 1456 1472 1488 1504 1520 1536 1552 1568 1584 
1600 1616 1632 1648 1664 1680 1696 1712 1728 1744 1760 1776 1792 1808 
1824 1840 1856 1872 1888 1904 1920 1936 1952 1968 1984 2000 2016 2032(kgdb)


Would be really grateful if anyone could suggest anything, again it 
appears to happen around the time periodic runs (but has happened 
randomly under load, not sure if this is a red herring tho)


If anyone needs anymore info, more than happy to oblige.

Cheers

--
Jamie Heckford
Network Manager
Trident Microsystems Ltd.

t: +44(0)1737-780790
f: +44(0)1737-771908
w: http://www.trident-uk.co.uk/
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: 5.4-RC2 freezing - ATA related?

[Jamie Heckford]

On Wed, May 18, 2005 at 03:54:59PM -0700, Doug White wrote:
> On Wed, 18 May 2005, Jamie Heckford wrote:
> 
> > Hi Peter,
> >
> > On Thu, May 19, 2005 at 05:53:12AM +1000, Peter Jeremy wrote:
> > > On Wed, 2005-May-18 16:03:16 +0100, Jamie Heckford wrote:
> > > >Managed to get a dump on our system for a similar prob we are getting:
> > >
> > > That traceback looks like a panic, not a deadlock.  What was the panic
> > > message?
> >
> > Only have remote access to the box im afraid, is there anyway I can obtain
> > the panic message?
> 
> "print msgbuf" should do it

(kgdb) printf "%s", (char *)msgbufp->msg_ptr



Fatal trap 12: page fault while in kernel mode
fault virtual address   = 0x214
fault code  = supervisor write, page not present
instruction pointer = 0x8:0xc059974e
stack pointer   = 0x10:0xecb4bb74
frame pointer   = 0x10:0xecb4bb7c
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 59 (swi1: net)
trap number = 12
panic: page fault
Uptime: 2h19m27s
Dumping 2047 MB
 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 256 272 288 304 320 336 
352 368 384 400 416 432 448 464 480 496 512 528 544 560 576 592 608 624 640 656 
672 688 704 720 736 752 768 784 800 816 832 848 864 880 896 912 928 944 960 976 
992 1008 1024 1040 1056 1072 1088 1104 1120 1136 1152 1168 1184 1200 1216 1232 
1248 1264 1280 1296 1312 1328 1344 1360 1376 1392 1408 1424 1440 1456 1472 1488 
1504 1520 1536 1552 1568 1584 1600 1616 1632 1648 1664 1680 1696 1712 1728 1744 
1760 1776 1792 1808 1824 1840 1856 1872 1888 1904 1920 1936 1952 1968 1984 2000 
2016 2032(kgdb)

Thanks :)

-- 
Jamie Heckford
Network Manager
Trident Microsystems Ltd.

t: +44(0)1737-780790
f: +44(0)1737-771908
w: http://www.tridentmicrosystems.co.uk/
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: 5.4-RC2 freezing - ATA related?

[Jamie Heckford]

Hi Peter,

On Thu, May 19, 2005 at 05:53:12AM +1000, Peter Jeremy wrote:
> On Wed, 2005-May-18 16:03:16 +0100, Jamie Heckford wrote:
> >Managed to get a dump on our system for a similar prob we are getting:
> 
> That traceback looks like a panic, not a deadlock.  What was the panic
> message?

Only have remote access to the box im afraid, is there anyway I can obtain
the panic message?

> 
> >#2  0xc0513474 in panic (fmt=0xc06c3da5 "%s") at 
> >/usr/src/sys/kern/kern_shutdown.c:566
> ...
> >#7  0xc0510018 in crcopy () at /usr/src/sys/kern/kern_prot.c:1810
> >#8  0xc0598c77 in in_pcbdetach (inp=0xc0743a40) at 
> >/usr/src/sys/netinet/in_pcb.c:720
> >#9  0xc05b21a6 in tcp_close (tp=0x0) at /usr/src/sys/netinet/tcp_subr.c:783
> 
> There's something wrong here:  If tcp_close() is passed NULL it will panic
> at this point when it tries to dereference tp.

Starting to stretch my knowledge a bit now ;)

If I can provide you with further debug output would you be able to give me some
pointers?

Thanks for your help

-- 
Jamie Heckford
Network Manager
Trident Microsystems Ltd.

t: +44(0)1737-780790
f: +44(0)1737-771908
w: http://www.tridentmicrosystems.co.uk/
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: 5.4-RC2 freezing - ATA related?

[Jamie Heckford]

On Mon, May 16, 2005 at 06:40:01AM -0600, Elliot Finley wrote:
> This has been happening since 5.3-R, I've been tuning different parameters
> to no avail.  I've taken the disks off of the onboard ICH5 controller and
> put them a promise TX4 S150 controller, but still the same thing happens.
> 
> The system freezes, but isn't totally dead.  It'll still respond to pings,
> the screensaver still functions, but it won't respond to a CAD at the
> console.  But if I press 'Enter' at the console, it'll give me a 'login:'
> prompt, but after entering the username, it never comes back with the
> 'password:' prompt.
> 
> After manually resetting the system it boots and says 'Automatic file system
> check failed; help!' and drops into single user mode.  Running fsck manually
> corrects errors on all volumes.  Then it'll boot from that point.
> 
> This seems to be triggered by daily periodic as it happens at 3:02-3:03AM
> each time.  But it doesn't happen *every* morning.
> 
> I suspect a bug in FreeBSD because this mode of failure happens on 3
> different machines, all configured similarly.
> 
> ASUS P4P800
> 2G RAM (though the other affected systems only have 1G)
> 80G Seagate Barracuda SATA drives (one system now on Promise TX4 S150
> controller, others on onboard ICH5)
> 
> On my lightly loaded systems, it happens rarely.  On my mailserver (fairly
> heavy disk load), it happens quite frequently.
> 
> How can I troubleshoot this?

Managed to get a dump on our system for a similar prob we are getting:

[GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: 
Undefined symbol "ps_pglobal_lookup"]
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-marcel-freebsd".
#0  doadump () at pcpu.h:160
160 __asm __volatile("movl %%fs:0,%0" : "=r" (td));
(kgdb) bt
#0  doadump () at pcpu.h:160
#1  0xc05131ae in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:410
#2  0xc0513474 in panic (fmt=0xc06c3da5 "%s") at 
/usr/src/sys/kern/kern_shutdown.c:566
#3  0xc0691e18 in trap_fatal (frame=0xecb4bb34, eva=532) at 
/usr/src/sys/i386/i386/trap.c:817
#4  0xc0691b73 in trap_pfault (frame=0xecb4bb34, usermode=0, eva=532) at 
/usr/src/sys/i386/i386/trap.c:735
#5  0xc0691771 in trap (frame=
  {tf_fs = -1068433384, tf_es = -989790192, tf_ds = 16, tf_edi = 
-1066124736, tf_esi = -1066124736, tf_ebp = -323699844, tf_isp = -323699872, 
tf_ebx = -1007063716, tf_edx = 528, tf_ecx = -1013235680, tf_eax = 307472464, 
tf_trapno = 12, tf_err = 2, tf_eip = -1067870386, tf_cs = 8, tf_eflags = 66050, 
tf_esp = -989760240, tf_ss = -1007063716}) at /usr/src/sys/i386/i386/trap.c:425
#6  0xc068168a in calltrap () at /usr/src/sys/i386/i386/exception.s:140
#7  0xc0510018 in crcopy () at /usr/src/sys/kern/kern_prot.c:1810
#8  0xc0598c77 in in_pcbdetach (inp=0xc0743a40) at 
/usr/src/sys/netinet/in_pcb.c:720
#9  0xc05b21a6 in tcp_close (tp=0x0) at /usr/src/sys/netinet/tcp_subr.c:783
#10 0xc05ae560 in tcp_input (m=0xc3a6a300, off0=20) at 
/usr/src/sys/netinet/tcp_input.c:2308
#11 0xc05a5aed in ip_input (m=0xc3a6a300) at /usr/src/sys/netinet/ip_input.c:776
#12 0xc0582f13 in netisr_processqueue (ni=0xc0742498) at 
/usr/src/sys/net/netisr.c:233
#13 0xc058310a in swi_net (dummy=0x0) at /usr/src/sys/net/netisr.c:346
#14 0xc04ffa79 in ithread_loop (arg=0xc3481600) at 
/usr/src/sys/kern/kern_intr.c:547
#15 0xc04fed0c in fork_exit (callout=0xc04ff928 , arg=0xc3481600, 
frame=0xecb4bd38) at /usr/src/sys/kern/kern_fork.c:791
#16 0xc06816ec in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:209
(kgdb) 

Help? ;)

-- 
Jamie Heckford
Network Manager
Trident Microsystems Ltd.

t: +44(0)1737-780790
f: +44(0)1737-771908
w: http://www.tridentmicrosystems.co.uk/
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: 5.4-RC2 freezing - ATA related?

[Jamie Heckford]

On Mon, May 16, 2005 at 06:40:01AM -0600, Elliot Finley wrote:
> This has been happening since 5.3-R, I've been tuning different parameters
> to no avail.  I've taken the disks off of the onboard ICH5 controller and
> put them a promise TX4 S150 controller, but still the same thing happens.
> 
> The system freezes, but isn't totally dead.  It'll still respond to pings,
> the screensaver still functions, but it won't respond to a CAD at the
> console.  But if I press 'Enter' at the console, it'll give me a 'login:'
> prompt, but after entering the username, it never comes back with the
> 'password:' prompt.
> 
> After manually resetting the system it boots and says 'Automatic file system
> check failed; help!' and drops into single user mode.  Running fsck manually
> corrects errors on all volumes.  Then it'll boot from that point.
> 
> This seems to be triggered by daily periodic as it happens at 3:02-3:03AM
> each time.  But it doesn't happen *every* morning.
> 
> I suspect a bug in FreeBSD because this mode of failure happens on 3
> different machines, all configured similarly.
> 

We are having similar problems to this on a box, won't go into great detail at 
the moment
but will post results when we have finished testing.

-- 
Jamie Heckford
Network Manager
Trident Microsystems Ltd.

t: +44(0)1737-780790
f: +44(0)1737-771908
w: http://www.tridentmicrosystems.co.uk/
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: IPFW2 fwd rulesets not working

[Jamie Heckford]

On Mon, Apr 04, 2005 at 01:34:25PM -0400, Mike Tancsa wrote:
> This was only added to RELENG_5. I would cvsup, or wait a few days for the 
> 5.4R.  I have been using RELENG_5 on a number of production boxes and they 
> are very stable and I think 5.4R will be as well.  But as always, YMMV
> 

Ah ok, cvsup it is then I guess!

Thanks very much to all those who assisted.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: IPFW2 fwd rulesets not working

[Jamie Heckford]

On Mon, Apr 04, 2005 at 12:48:04PM -0400, Mike Tancsa wrote:
> At 12:47 PM 04/04/2005, Jamie Heckford wrote:
> >Hi,
> >
> >Has anyone else had issues with using the fwd/forward feature of IPFW2?
> >
> >As described in below PR, not working for me either since going to 5.3 :(
> >
> >http://lists.freebsd.org/pipermail/freebsd-i386/2004-November/001823.html
> >
> >Any pointers would be greatly appreciated!
> 
> Hi,
> Try adding
> 
> options IPFIREWALL_FORWARD
> options IPFIREWALL_FORWARD_EXTENDED
> 
> 

Saw this however FreeBSD 5.3-RELEASE-p6 #2: Thu Mar 31 01:50:41 BST 2005 is 
giving
unknown option "IPFIREWALL_FORWARD_EXTENDED"

Very strange!
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

IPFW2 fwd rulesets not working

[Jamie Heckford]

Hi,

Has anyone else had issues with using the fwd/forward feature of IPFW2?

As described in below PR, not working for me either since going to 5.3 :(

http://lists.freebsd.org/pipermail/freebsd-i386/2004-November/001823.html 

Any pointers would be greatly appreciated!

thanks
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

[no subject]

[Jamie Heckford]

Susbscribe [EMAIL PROTECTED]

 --
Jamie Heckford
Network Manager
Trident Microsystems Ltd.

t: +44(0)1737-780790
f: +44(0)1737-771908
w: http://www.tridentmicrosystems.co.uk/ 

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Compaq GIGA NIC

[Jamie Heckford]

 > So you ran into a driver bug, and you describe it by saying "The
> broadcom chips perform terribly!" ???  No wonder there's so much
> misinformation on the net.  Sheesh, try to remember that this stuff
> gets archived!  People read it and believe it, and nobody benefits
> when it's just not true.
>

Ok  apologies - here's my corrected version:

The last time *I* used Ethernet cards based on the broadcom chipset the driver caused 
me massive problems. It was terrible. I hated
it. I switched to intels. This solved my problem.  IMHO

Sorry for my earlier post and before something flies back yes I did understand 
your reply ;)

J


-- 

Message scanned for viruses and dangerous content by
 and believed to be clean


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message

Re: Compaq GIGA NIC

[Jamie Heckford]

Urgh - The broadcom chips perform terribly!

We put Intel cards into the riser slots on all our compaq servers.. I would 
recommend you do the same!

- Original Message - 
From: "Shagol" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, October 16, 2002 7:08 PM
Subject: Fwd: Compaq GIGA NIC


> hmmm i think this is a Broadcom Gigabit NIC but i cannot find the TYPE :-( The
> includet bge device doesn't work.
> 
> Any ideas ?
> 
> 
> - Weitergeleitete Nachricht von Shagol <[EMAIL PROTECTED]> -
> Datum: Tue, 15 Oct 2002 23:01:40 +0200
> Von: Shagol <[EMAIL PROTECTED]>
> Antwort an: Shagol <[EMAIL PROTECTED]>
>  Betreff: Compaq GIGA NIC
>   An: [EMAIL PROTECTED]
> 
> Hi there
> 
> How can i get my internal gigabit-NIC running on freebsd 4.7 RELEASE ?
> 
> Compaq Proliant ML 310 with: 
> 
> NC7760 PCI Gigabit Server Adapter (Integrated/Embedded)
> 
> 
> Thanx
> 
> Thomas
> 
> - Ende der weitergeleiteten Nachricht -
> 
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-stable" in the body of the message
> 

-- 

Message scanned for viruses and dangerous content by
 and believed to be clean


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message

Compiling a New Kernel

[Jamie Heckford]

Being one of these difficult people who like sticking to the old way of doing things, 
im still compiling my kernel the old way
(config KERNELNAME; cd ../../KERNELNAME; make depend; make ; make install) :P

I picked up a rumour on the mailing lists that this may no longer work in 
future/recent releases?

Just curious ;)

--
Jamie Heckford
[EMAIL PROTECTED]
http://www.jamiesdomain.org.uk/

FreeBSD: The Power to Serve


-- 

Message scanned for viruses and dangerous content by
<http://www.newnet.co.uk/av/> and believed to be clean


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message

Re: ATA Atapi 4.6 Release

[Jamie Heckford]

I jumped back to 4.5 earlier, installing 4.6-R with 120GB IDE drives (1x
40GB, 3x 120GB) and the system
wouldn't boot.

Came up with a page fault and fatal trap 12, i'll try grab some output and
repost.

Thanks,

Jamie

- Original Message -
From: "Matthias Andree" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, June 18, 2002 11:57 AM
Subject: Re: ATA Atapi 4.6 Release


> "David W. Chapman Jr." <[EMAIL PROTECTED]> writes:
>
> > On Mon, Jun 17, 2002 at 11:38:01AM -0500, John Prince wrote:
> >> I have to say, I am a bit disappointed in the 4.6 release, as well as
the
> >> way problems have been identified, and swept under the carpet..
> >
> > Why didn't you express these concerns for the past few months?
>
> There have been several reports of ATA and ATAPI brokenness after the
> MFC.
>
> After I brought the TCQ brokenness up again at 4.6-RC time, Søren fixed
> the boot panic I experienced, and in late May he wrote he could
> reproduce the other known TCQ-timeout-and-fall-back-to-PIO problem, but
> I've never seen anything since. But what is bringing up a known problem
> again of help? Do you want people to scream their problem list every
> week? The PRs are there, and are open, so you cannot say these concerns
> had not been expressed. They have indeed.
>
> And I agree with those who say that 4.6 should NOT have been released
> with ATA(PI) in /this/ shape.
>
> I have been told (on this list) by the RE team that the MFC cannot be
> backed out and that 5.0DP2 is close, and I understand they want to keep
> the schedule as good as possible, but all these objections do not help
> the regression or displeasing users. And the latter is a Bad Thing®.
>
> --
> Matthias Andree
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-stable" in the body of the message
>


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message

Re: NFS Problems with Quantum Snapserver 4100 (BGE Cards!)

[Jamie Heckford]

Already running the card and switch port in 100BaseTX FDX (forced) :)

Would use GigE if the switch supported it tho

Thus spake Matthew Dillon ([EMAIL PROTECTED]) :

> It should also work if you force the GigE card into 100BaseTX mode, 
> assuming the switch can deal with it.  Though of course then you are 
> not getting GigE speeds. 
> 
> Your description is very similar to a problem I had on my 2550's that
> Bill Paul finally solved.  It turned out that my 2550's (BCM5700) were
> not initializing the polynomial functions properly and this resulted
> in packet loss.  Whenever you get bit stuffing packet loss like that,
> certain bit patterns will *always* fail.  But I'm sure this issue has
> already been dealt with on the 5701 so the problem you are having is
> probably different.
> 
> The result is the appearance of hicups and delays on a TCP connection,
> and repeatable hangs when just the wrong data pattern is transmitted
> (because that packet winds up failing every time rather then just some
> of the time).
> 
> Another possibility in regards to packet loss is simply a bad cable
> (if you are running GigE over copper).  GigE is very sensitive to cable
> issues and a bad crimp will screw things up easily.
> 
> In anycase, my feeling about GigE in general is that it's a great cheap
> way to aggregate data on an uplink, or to an NFS server that needs it,
> but the incremental cost and hassle factor are still too high to
> extend the benefit to generic servers.
> 
>   -Matt

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message

Re: 4.4 will be delayed until Saturday, the 8th of September

[Jamie Heckford]

On Thu, Sep 06, 2001 at 02:57:30PM -0700, Jordan Hubbard wrote:
> Well, there does appear to be a lot of general feeling that we should
> wait, so how would people feel about a push-back to the 14th? 

would be good if you could push the release back until then, I myself
personally won't be able to test until after the weekend :(

strength in numbers ;)

-- 
====
  Jamie Heckford   |  [EMAIL PROTECTED] 
  Systems Administrator|020 7903 3015
  Clara.Net Ltd. (UK) NOC  |www.clara.net


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message

Re: another perl problem ?

[Jamie Heckford]

I had the same problem.

Defining  NOPERL=   true 
in /etc/defaults/make.conf seemed to solve it for me..


On Wed, 22 Nov 2000, you wrote:
> > Hello.
> > 
> > Well.. somebody knows how I can solve this ? (I get this error in "make
> > installworld"):
> > 
> > ...
> > 
> > ===> gnu/usr.bin/perl/library/SDBM_File
> > cd /usr/obj/usr/src/gnu/usr.bin/perl/library/SDBM_File/ext/SDBM_File ; make -B i
> > nstall  INSTALLPRIVLIB=/usr/libdata/perl/5.00503 INSTALLARCHLIB=/usr/libdata/pe
> > rl/5.00503/mach
> > cd sdbm && make all
> > rm -rf libsdbm.a
> > ar cr libsdbm.a sdbm.o  pair.o hash.o && : libsdbm.a
> > chmod 755 libsdbm.a
> > chmod:No such file or directory
> > *** Error code 1
> > 
> > Stop in
> > /usr/obj/usr/src/gnu/usr.bin/perl/library/SDBM_File/ext/SDBM_File/sdbm.
> > *** Error code 1
> > 
> > Stop in /usr/obj/usr/src/gnu/usr.bin/perl/library/SDBM_File/ext/SDBM_File.
> > 
> > ...
> > 
> > now, trying to do what "make installworld" fail:
> > 
> > # cd /usr/obj/usr/src/gnu/usr.bin/perl/library/SDBM_File/ext/SDBM_File
> > # cd sdbm && make all
> > rm -rf libsdbm.a
> > ar cr libsdbm.a sdbm.o  pair.o  hash.o && : libsdbm.a
> > chmod 755 libsdbm.a
> > /bin/sh -c true
> > #
> > 
> > (root!shaolin)(~)# uname -v
> > FreeBSD 4.2-STABLE #0: Wed Nov 22 13:51:12 EDT 2000 
> > root@shaolin:/usr/obj/usr/src/sys/shaolin
> > --
> > 
> > My source is up to date (i cvsup'ed today).
> > 
> > help :)
> > 
> > ---
> > Thiago Lucas
> > 
> > 
> > 
> > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > with "unsubscribe freebsd-stable" in the body of the message
> -- 
> Jamie Heckford
> Chief Network Engineer
> Psi-Domain - Innovative Linux Solutions. Ask Us How.
> 
> ===
> email: [EMAIL PROTECTED]
> web:   http://www.psi-domain.co.uk/
> 
> tel: +44 (0)1737 789 246
> fax: +44 (0)1737 789 245
> mobile:  +44 (0)7779 646 529
> ===
-- 
Jamie Heckford
Chief Network Engineer
Psi-Domain - Innovative Linux Solutions. Ask Us How.

===
email: [EMAIL PROTECTED]
web: http://www.psi-domain.co.uk/

tel:   +44 (0)1737 789 246
fax:   +44 (0)1737 789 245
mobile:+44 (0)7779 646 529
===


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message