RE: ZFS panic in zfs_fuid_create

2009-05-29 Thread Lawrence Farr


> -Original Message-
> From: owner-freebsd-sta...@freebsd.org [mailto:owner-freebsd-
> sta...@freebsd.org] On Behalf Of Andriy Gapon
> Sent: 28 May 2009 18:11
> To: Lawrence Farr
> Cc: freebsd-stable@freebsd.org
> Subject: Re: ZFS panic in zfs_fuid_create
> 
> on 27/05/2009 19:25 Lawrence Farr said the following:
> > I updated my backup boxes to the latest and greatest ZFS code,
> > and started getting the following panic on them all (3 machines):
> >
> > panic: zfs_fuid_create
> > cpuid = 1
> > Uptime: 1h28m48s
> > Cannot dump. No dump device defined.
> > Automatic reboot in 15 seconds - press a key on the console to abort
> >
> > A quick google found kern/133020 with a patch from PJD that has fixed
> > it for me. Should it be in stable or does it break something else?
> 
> Hmm I wonder if you really do have UIDs or GIDs greater than 2147483647
> defined on
> your system?
> 

Not that I could see. It's rsyncing from an EXT3 volume on a Linux server,
that runs as an OSX fileserver. All the permissions/owners are mapped to
Linux users. There are a lot of odd characters used in the filenames, but
that's all I could see that was potentially an issue. Hasn't had a problem
since I put that patch in, and I was getting a few minutes into the backup
before it paniced previously.

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


ZFS panic in zfs_fuid_create

2009-05-27 Thread Lawrence Farr
I updated my backup boxes to the latest and greatest ZFS code,
and started getting the following panic on them all (3 machines):

panic: zfs_fuid_create
cpuid = 1
Uptime: 1h28m48s
Cannot dump. No dump device defined.
Automatic reboot in 15 seconds - press a key on the console to abort

A quick google found kern/133020 with a patch from PJD that has fixed
it for me. Should it be in stable or does it break something else?

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


Cannot see disks attached to Marvell controller

2008-11-12 Thread Lawrence Farr
I've got an Asus P5E3WSPro with 8 SATA ports and 8 disks attached. 6 disks
are on
one controller (and work perfectly) and 2 are on a second Marvell
controller.
FreeBSD sees the controller, but not the disks. If I move a working disk to
the
Marvell controller I can boot off it up to the stage of mounting root where
it
fails to see the disk. 

atacontrol shows:

ATA channel 2:
Master:  no device present
Slave:   no device present
ATA channel 3:
Master:  no device present
Slave:   no device present
ATA channel 4:
Master:  ad8  Serial ATA II
Slave:   no device present
ATA channel 5:
Master: ad10  Serial ATA II
Slave:   no device present
ATA channel 6:
Master: ad12  Serial ATA II
Slave:   no device present
ATA channel 7:
Master: ad14  Serial ATA II
Slave:   no device present
ATA channel 8:
Master: ad16  Serial ATA II
Slave:   no device present
ATA channel 9:
Master: ad18  Serial ATA II
Slave:   no device present

Here's the pciconf listing:

[EMAIL PROTECTED]:0:31:2:class=0x010601 card=0x82771043 chip=0x29228086
rev=0x02 hdr=0x00
vendor = 'Intel Corporation'
device = '82801IB/IR/IH (ICH9 Family) 6 port SATA AHCI Controller'
class  = mass storage
--
[EMAIL PROTECTED]:1:0:0: class=0x01048f card=0x82201043 chip=0x614511ab
rev=0xa1 hdr=0x00
vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)'
device = '? Add-on IC to provide 4x SATA Ports, attached to ICH7
(SthBridge?) via PCI-Express.'
class  = mass storage

Anyone got any ideas why they don't show up? I've tried every BIOS option
with the controller,
Ie raid mode etc.



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


Anyone else seeing make release failing?

2008-09-01 Thread Lawrence Farr
I build releases nightly, and have been getting

(snip)

+ shift
+ FSLABEL=minimum3
+ shift
+ [ 4320 -eq 0 -a minimum3 = auto ]
+ rm -f /R/stage/mfsroot/mfsroot
+ dd of=/R/stage/mfsroot/mfsroot if=/dev/zero count=4320 bs=1k uname -r 
+ [ -f /R/stage/trees/base/boot/boot ] BOOT=-B -b 
+ /R/stage/trees/base/boot/boot dofs_md [ x != x ] mdconfig -a -t vnode 
+ -f /R/stage/mfsroot/mfsroot
mdconfig: failed to load geom_md module: No such file or directory
+ MDDEVICE=
+ umount /dev

For a few days now. The module exists, but refuses to load, as I guess
it's already in Generic?

kldload: can't load geom_md: File exists

Do I just need a newer -STABLE than FreeBSD 7.0-STABLE #1: Mon Mar 17
13:20:41 GMT 2008?

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


RE: bin/121684: dump frequently hangs

2008-03-17 Thread Lawrence Farr
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:owner-freebsd-
> [EMAIL PROTECTED] On Behalf Of John Baldwin
> Sent: 14 March 2008 19:46
> To: freebsd-stable@freebsd.org
> Cc: Greg Rivers
> Subject: Re: bin/121684: dump frequently hangs
> 
> On Friday 14 March 2008 12:53:22 am Greg Rivers wrote:
> > I'm seeing dump hang frequently on RELENG_7 i386.  Details and a
> ktrace in
> > PR bin/121684.  Is anyone else experiencing this?
> 
> jeff@ just fixed this in HEAD with the latest patch to
> sys/kern/subr_sleepqueue.c.  The patch should apply directly to
> RELENG_7.


I couldn't get this to apply cleanly against 7, is it safe to use rev 1.48
on 7?
I have 3 machines here that hang whilst dumping and I'd like to test the
patch.

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


RE: Anyone else seeing this on a make release of 7?

2007-12-05 Thread Lawrence Farr

> -Original Message-
> From: [EMAIL PROTECTED] [mailto:owner-freebsd-
> [EMAIL PROTECTED] On Behalf Of Claus Guttesen
> Sent: 05 December 2007 10:47
> To: Lawrence Farr
> Cc: freebsd-stable@freebsd.org
> Subject: Re: Anyone else seeing this on a make release of 7?
> 
> > cc -Os -pipe -Wsystem-headers -Werror -Wall -Wno-format-y2k -W
> 
> What happens if you revert to default optimization to -O2?
> 
> --
> regards
> Claus


I have no optimization settings in make.conf.

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


RE: Anyone else seeing this on a make release of 7?

2007-12-05 Thread Lawrence Farr


> -Original Message-
> From: Yuri Pankov [mailto:[EMAIL PROTECTED]
> Sent: 05 December 2007 10:37
> To: Lawrence Farr
> Cc: freebsd-stable@freebsd.org
> Subject: Re: Anyone else seeing this on a make release of 7?
> 
> On 12/5/2007 12:55 PM, Lawrence Farr wrote:
> > cc -Os -pipe -Wsystem-headers -Werror -Wall -Wno-format-y2k -W
> > -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes
> > -Wpointer-arith -W
> > return-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-
> align
> > -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -
> Wredundan
> > t-decls -Wno-pointer-sign -c /usr/src/bin/ed/main.c
> > *** Error code 1
> >
> > Stop in /usr/src/bin/ed.
> > *** Error code 1
> >
> > Stop in /usr/obj/usr/src/release/fixit_crunch.
> > *** Error code 1
> >
> > Stop in /usr/src/release.
> > *** Error code 1
> >
> > Stop in /usr/src/release.
> > in.c:106: warning: argument 'argv' might be clobbered by 'longjmp' or
> > 'vfork'
> > + umount /dev
> >
> > Been getting it for a week or so now, it's being built on:
> >
> > 7.0-BETA3 FreeBSD 7.0-BETA3 #0: Mon Nov 26 01:04:55 GMT 2007
> 
> Are you sure that you are building from RELENG_7 source? It doesn't
> have
> -Werror defined, IIRC. And HEAD should be fixed by this commit:
> http://lists.freebsd.org/pipermail/cvs-src/2007-December/084624.html
> 
> 
> HTH,
> Yuri

Got it, was using 7 source, and the release script had "RELEASETAG=."
defined later in it.

Thanks for the clue!

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


Anyone else seeing this on a make release of 7?

2007-12-05 Thread Lawrence Farr
cc -Os -pipe -Wsystem-headers -Werror -Wall -Wno-format-y2k -W
-Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes
-Wpointer-arith -W
return-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align
-Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundan
t-decls -Wno-pointer-sign -c /usr/src/bin/ed/main.c
*** Error code 1

Stop in /usr/src/bin/ed.
*** Error code 1

Stop in /usr/obj/usr/src/release/fixit_crunch.
*** Error code 1

Stop in /usr/src/release.
*** Error code 1

Stop in /usr/src/release.
in.c:106: warning: argument 'argv' might be clobbered by 'longjmp' or
'vfork'
+ umount /dev

Been getting it for a week or so now, it's being built on:

7.0-BETA3 FreeBSD 7.0-BETA3 #0: Mon Nov 26 01:04:55 GMT 2007

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


RE: ufs_dirbad: bad dir panic (Was Areca Weirdness)

2006-11-29 Thread Lawrence Farr
 

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of Kris Kennaway
> Sent: 21 November 2006 21:07
> To: Lawrence Farr
> Cc: freebsd-stable@freebsd.org; 'Tom Samplonius'; 'Kris Kennaway'
> Subject: Re: ufs_dirbad: bad dir panic (Was Areca Weirdness)
> 
> On Tue, Nov 21, 2006 at 10:27:18AM -, Lawrence Farr wrote:
> >  
> > 
> > > -Original Message-
> > > From: Kris Kennaway [mailto:[EMAIL PROTECTED] 
> > > Sent: 21 November 2006 00:44
> > > To: Tom Samplonius
> > > Cc: Kris Kennaway; freebsd-stable@freebsd.org; Lawrence Farr
> > > Subject: Re: ufs_dirbad: bad dir panic (Was Areca Weirdness)
> > > 
> > > On Mon, Nov 20, 2006 at 04:29:17PM -0800, Tom Samplonius wrote:
> > > > 
> > > > - Kris Kennaway <[EMAIL PROTECTED]> wrote:
> > > > > > > > > >> If I newfs it, and copy data to it, I have 
> no problem
> > > > > > > initially.
> > > > > > I can repeat this 100% now, by copying data onto 
> the drive then
> > > > > unmounting
> > > > > > and remounting it. I have a core dump if anyone can 
> tell me what
> > > > > info to
> > > > > > get from it:
> > > > > > 
> > > > > >   Version String: FreeBSD 6.2-PRERELEASE #0: Wed Nov 15 
> > > 19:57:01 GMT
> > > > > 2006
> > > > > > 
> > > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/P6NOUSB
> > > > > >   Panic String: ufs_dirbad: bad dir
> > > > > 
> > > > > Run fsck -fy on the filesystem, this is a common symptom of a
> > > > > corrupted filesystem.
> > > > 
> > > >   I think the OP knows the filesystem is corrupted.  The 
> > > problem is why does the filesystem get corrupted?  The OP 
> > > says he can corrupt the filesystem on demand after a newfs.  
> > > So it could be the Areca driver, or even bad hardware.
> > > 
> > > My point is that this panic can happen when your 
> filesystem becomes
> > > corrupted, and the panic keeps happening during "normal" 
> filesystem
> > > operations until you forcibly fsck it, at which point the 
> panic goes
> > > away.
> > > 
> > > Kris
> > > 
> > 
> > I have been newfs'ing it and starting again, and it will 
> work once, but 
> > once unmounted and re-mounted it will panic with ufs_dirbad.
> 
> OK, that's a different matter then.  One thing you could try would be
> to write known data directly to the device and then read it back or
> verify the md5 sum and try to identify the failure mode.  I'd try to
> rule out hardware problems too.
> 
> Kris
> 

I made a volume that was under 2Tb and installed directly onto the
Areca rather than the ATA drive. This has now run without issue for 
a week. Strangely, I did the same test on the ATA drive prior to this
and it worked without issue for a week. Quite why it doesn't work with
the ATA as the boot device and the Areca as storage is beyond me.

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


RE: Areca Weirdness - UFS2 larger than 2Tb problem?

2006-11-18 Thread Lawrence Farr

> > 
> > 
> > > Re-posting to -STABLE as it also does it on i386.
> > >
> > > I reinstalled i386 stable as of yesterday, and newfs'd all 
> > the partitions
> > > "just in case". I got it to crash while doing a mkdir on the areca
> > > partition, so set up crash dumps on the boot drive (it 
> > boots off a single
> > > ATA disk, the Areca is additional storage) and it died 
> again running
> > > the periodic scripts last night. The info file from the 
> dump shows:
> > >
> > > Dump header from device /dev/ad0s1b
> > >  Architecture: i386
> > >  Architecture Version: 2
> > >  Dump Length: 2145452032B (2046 MB)
> > >  Blocksize: 512
> > >  Dumptime: Thu Nov 16 03:01:09 2006
> > >  Hostname: nas-2.shorewood-epc.co.uk
> > >  Magic: FreeBSD Kernel Dump
> > >  Version String: FreeBSD 6.1-20061115 #0: Wed Nov 15 
> > 04:18:11 UTC 2006
> > >[EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP
> > >  Panic String: ufs_dirbad: bad dir
> > >  Dump Parity: 632980830
> > >  Bounds: 0
> > >  Dump Status: good
> > >
> > > Am I expecting too much with partitions over 2Tb? I've 
> > never gone over
> > > 2Tb before, so havent come across any issues like this.
> > >
> > >> -Original Message-
> > >> From: [EMAIL PROTECTED]
> > >> [mailto:[EMAIL PROTECTED] On Behalf Of 
> Lawrence Farr
> > >> Sent: 10 November 2006 11:39
> > >> To: [EMAIL PROTECTED]
> > >> Subject: Areca Weirdness
> > >>
> > >> I've got an Areca 12 port card running a 6Tb array which 
> is divided
> > >> into 2.1Tb chunks at the moment, as it was doing the same with a
> > >> single 6Tb partition.
> > >>
> > >> ad0: 58644MB  at ata0-master UDMA100
> > >> da0 at arcmsr0 bus 0 target 0 lun 0
> > >> da0:  Fixed Direct Access SCSI-3 device
> > >> da0: 166.666MB/s transfers (83.333MHz, offset 32, 16bit),
> > >> Tagged Queueing
> > >> Enabled
> > >> da0: 2224922MB (4556640256 512 byte sectors: 255H 63S/T 283637C)
> > >>
> > >> If I newfs it, and copy data to it, I have no problem initially.
> > >> If I then try and copy the data on the disk already to a new
> > >> folder, the machine reboots (it's a remote host with no serial
> > >> attached currently). When it comes back to life, it mounts, and
> > >> shows as:
> > >>
> > >> /dev/da0   2.1T343G1.6T18%/usr/home/areca1
> > >>
> > >> But is completely empty. Unmounting it and trying to fsck it
> > >> errors, as does mounting it by hand.
> > >>
> > >> [EMAIL PROTECTED] /home]# fsck -y /dev/da0
> > >> ** /dev/da0
> > >> Cannot find file system superblock
> > >> ioctl (GCINFO): Inappropriate ioctl for device
> > >> fsck_ufs: /dev/da0: can't read disk label
> > >> [EMAIL PROTECTED] /home]# mount /dev/da0
> > >> mount: /dev/da0 on /usr/home/areca1: incorrect super block
> > >>
> > >> Are there any known issues with the driver on AMD64? I had
> > >> major issues with it on Linux/386 with large memory support
> > >> (it would behave equally strangely) that went away when I
> > >> took large memory support out, maybe there are some non 64
> > >> bit safe parts common to both?
> > 
> > I have the Areca 8 port PCI-X card. 2 arrays of 1.25T each 
> > and no issues 
> > yet. I've been using it on 5.x for a year and now on 6.x it's 
> > perfect too.
> > Have you updated the card to the latest firmware ?
> > 
> > I've just done a test copy from the one volume to the other 
> > of 10 gigs. It 
> > ran at over 80M/s and tok under 2 minutes with no errors.
> > 
> > Did you follow the instructions provided with the Areca card 
> > for creating 
> > volumes over 2TB ? There are some things you have to do so 
> > that the OS works 
> > correctly with it.
> > 
> > -Clay
> 
> I'm not convinced it's an Areca problem anymore, as I've copied 
> 300 or so Gb on now, but it will randomly corrupt the fs and
> reboot itself. Background fsck will not fix it, but a manual one
> does. I'm going to drop the partitions below 2Tb and try the test
> again to try and eliminate any hardware/driver issues.


This has now paniced while idle, and with only a 1.8Tb fs mounted.
Didn't get a core, but got this:

Nov 17 19:43:39 nas-2 savecore: reboot after panic: ffs_valloc: dup alloc
Nov 17 19:43:39 nas-2 savecore: no dump, not enough free space on device
(661322 available, need 2095170)
Nov 17 19:43:39 nas-2 savecore: unsaved dumps found but not saved

Anyone got any ideas where to start looking?

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


RE: Areca Weirdness - UFS2 larger than 2Tb problem?

2006-11-17 Thread Lawrence Farr
 

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of Clayton Milos
> Sent: 17 November 2006 11:10
> To: Lawrence Farr; freebsd-stable@freebsd.org
> Subject: Re: Areca Weirdness 
> 
> 
> - Original Message ----- 
> From: "Lawrence Farr" <[EMAIL PROTECTED]>
> To: 
> Sent: Thursday, November 16, 2006 4:51 PM
> Subject: RE: Areca Weirdness
> 
> 
> > Re-posting to -STABLE as it also does it on i386.
> >
> > I reinstalled i386 stable as of yesterday, and newfs'd all 
> the partitions
> > "just in case". I got it to crash while doing a mkdir on the areca
> > partition, so set up crash dumps on the boot drive (it 
> boots off a single
> > ATA disk, the Areca is additional storage) and it died again running
> > the periodic scripts last night. The info file from the dump shows:
> >
> > Dump header from device /dev/ad0s1b
> >  Architecture: i386
> >  Architecture Version: 2
> >  Dump Length: 2145452032B (2046 MB)
> >  Blocksize: 512
> >  Dumptime: Thu Nov 16 03:01:09 2006
> >  Hostname: nas-2.shorewood-epc.co.uk
> >  Magic: FreeBSD Kernel Dump
> >  Version String: FreeBSD 6.1-20061115 #0: Wed Nov 15 
> 04:18:11 UTC 2006
> >[EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP
> >  Panic String: ufs_dirbad: bad dir
> >  Dump Parity: 632980830
> >  Bounds: 0
> >  Dump Status: good
> >
> > Am I expecting too much with partitions over 2Tb? I've 
> never gone over
> > 2Tb before, so havent come across any issues like this.
> >
> >> -Original Message-
> >> From: [EMAIL PROTECTED]
> >> [mailto:[EMAIL PROTECTED] On Behalf Of Lawrence Farr
> >> Sent: 10 November 2006 11:39
> >> To: [EMAIL PROTECTED]
> >> Subject: Areca Weirdness
> >>
> >> I've got an Areca 12 port card running a 6Tb array which is divided
> >> into 2.1Tb chunks at the moment, as it was doing the same with a
> >> single 6Tb partition.
> >>
> >> ad0: 58644MB  at ata0-master UDMA100
> >> da0 at arcmsr0 bus 0 target 0 lun 0
> >> da0:  Fixed Direct Access SCSI-3 device
> >> da0: 166.666MB/s transfers (83.333MHz, offset 32, 16bit),
> >> Tagged Queueing
> >> Enabled
> >> da0: 2224922MB (4556640256 512 byte sectors: 255H 63S/T 283637C)
> >>
> >> If I newfs it, and copy data to it, I have no problem initially.
> >> If I then try and copy the data on the disk already to a new
> >> folder, the machine reboots (it's a remote host with no serial
> >> attached currently). When it comes back to life, it mounts, and
> >> shows as:
> >>
> >> /dev/da0   2.1T343G1.6T18%/usr/home/areca1
> >>
> >> But is completely empty. Unmounting it and trying to fsck it
> >> errors, as does mounting it by hand.
> >>
> >> [EMAIL PROTECTED] /home]# fsck -y /dev/da0
> >> ** /dev/da0
> >> Cannot find file system superblock
> >> ioctl (GCINFO): Inappropriate ioctl for device
> >> fsck_ufs: /dev/da0: can't read disk label
> >> [EMAIL PROTECTED] /home]# mount /dev/da0
> >> mount: /dev/da0 on /usr/home/areca1: incorrect super block
> >>
> >> Are there any known issues with the driver on AMD64? I had
> >> major issues with it on Linux/386 with large memory support
> >> (it would behave equally strangely) that went away when I
> >> took large memory support out, maybe there are some non 64
> >> bit safe parts common to both?
> 
> I have the Areca 8 port PCI-X card. 2 arrays of 1.25T each 
> and no issues 
> yet. I've been using it on 5.x for a year and now on 6.x it's 
> perfect too.
> Have you updated the card to the latest firmware ?
> 
> I've just done a test copy from the one volume to the other 
> of 10 gigs. It 
> ran at over 80M/s and tok under 2 minutes with no errors.
> 
> Did you follow the instructions provided with the Areca card 
> for creating 
> volumes over 2TB ? There are some things you have to do so 
> that the OS works 
> correctly with it.
> 
> -Clay

I'm not convinced it's an Areca problem anymore, as I've copied 
300 or so Gb on now, but it will randomly corrupt the fs and
reboot itself. Background fsck will not fix it, but a manual one
does. I'm going to drop the partitions below 2Tb and try the test
again to try and eliminate any hardware/driver issues.

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


RE: Areca Weirdness

2006-11-16 Thread Lawrence Farr
Re-posting to -STABLE as it also does it on i386.

I reinstalled i386 stable as of yesterday, and newfs'd all the partitions
"just in case". I got it to crash while doing a mkdir on the areca
partition, so set up crash dumps on the boot drive (it boots off a single
ATA disk, the Areca is additional storage) and it died again running
the periodic scripts last night. The info file from the dump shows:

Dump header from device /dev/ad0s1b
  Architecture: i386
  Architecture Version: 2
  Dump Length: 2145452032B (2046 MB)
  Blocksize: 512
  Dumptime: Thu Nov 16 03:01:09 2006
  Hostname: nas-2.shorewood-epc.co.uk
  Magic: FreeBSD Kernel Dump
  Version String: FreeBSD 6.1-20061115 #0: Wed Nov 15 04:18:11 UTC 2006
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP
  Panic String: ufs_dirbad: bad dir
  Dump Parity: 632980830
  Bounds: 0
  Dump Status: good

Am I expecting too much with partitions over 2Tb? I've never gone over
2Tb before, so havent come across any issues like this.

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of Lawrence Farr
> Sent: 10 November 2006 11:39
> To: [EMAIL PROTECTED]
> Subject: Areca Weirdness 
> 
> I've got an Areca 12 port card running a 6Tb array which is divided
> into 2.1Tb chunks at the moment, as it was doing the same with a
> single 6Tb partition.
> 
> ad0: 58644MB  at ata0-master UDMA100
> da0 at arcmsr0 bus 0 target 0 lun 0
> da0:  Fixed Direct Access SCSI-3 device
> da0: 166.666MB/s transfers (83.333MHz, offset 32, 16bit), 
> Tagged Queueing
> Enabled
> da0: 2224922MB (4556640256 512 byte sectors: 255H 63S/T 283637C)
> 
> If I newfs it, and copy data to it, I have no problem initially.
> If I then try and copy the data on the disk already to a new
> folder, the machine reboots (it's a remote host with no serial
> attached currently). When it comes back to life, it mounts, and
> shows as:
> 
> /dev/da0   2.1T343G1.6T18%/usr/home/areca1
> 
> But is completely empty. Unmounting it and trying to fsck it
> errors, as does mounting it by hand.
> 
> [EMAIL PROTECTED] /home]# fsck -y /dev/da0
> ** /dev/da0
> Cannot find file system superblock
> ioctl (GCINFO): Inappropriate ioctl for device
> fsck_ufs: /dev/da0: can't read disk label
> [EMAIL PROTECTED] /home]# mount /dev/da0
> mount: /dev/da0 on /usr/home/areca1: incorrect super block
> 
> Are there any known issues with the driver on AMD64? I had
> major issues with it on Linux/386 with large memory support
> (it would behave equally strangely) that went away when I
> took large memory support out, maybe there are some non 64
> bit safe parts common to both?
> 
> ___
> [EMAIL PROTECTED] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-amd64
> To unsubscribe, send any mail to 
> "[EMAIL PROTECTED]"
> 

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


Install onto 6Tb array

2006-10-25 Thread Lawrence Farr
I'd like to install stable directly onto a 6Tb Areca array, and
have run out of clues how to do it. In the past I've always
used a separate boot volume that was small enough for sysinstall
to work with, but I have no space to fit more drives in this
chassis. I've tried putting a small partition on the start,
which boots fine, but screws up the disk sizing as the geometry
is wrong I guess? tried diskprep, but that gets the gemometry
wrong as well. Is the only option to use gpt and restore to
it from another boot device and hope that the bios can boot it? 

Lawrence Farr
EPC Direct Limited 

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


RE: Stable Build Error

2006-04-25 Thread Lawrence Farr
> -Original Message-
> From: Brooks Davis [mailto:[EMAIL PROTECTED] 

> My telepathy powers aren't working.  What's the error? :)

See the second message I sent where I didn't accidentally hit 
ctrl-s instead of ctrl-v when pasting the error in. Doh.

Here it is again:

I've been seeing the following for a week or so, and have 
deleted /usr/obj , re-cvsupped and run 

cd /usr/src && make cleandir && make cleandir

make.conf is empty. Anyone got any ideas? 

===> kerberos5/tools/make-roken (all)
===> kerberos5/tools/asn1_compile (all)
cd /usr/src/kerberos5/tools/asn1_compile/../make-roken && make
cc -O2 -fno-strict-aliasing -pipe
-I/usr/src/kerberos5/tools/asn1_compile/../../../crypto/heimdal/lib/roken
-I/usr/src/kerberos5/tools/asn1_compile/../../../crypto/heimdal/lib/asn1 -I.
-DHAVE_CONFIG_H -I/usr/src/kerberos5/tools/asn1_comp
ile/../../include -DINET6  -I/usr/obj/usr/src/tmp/legacy/usr/include -c
/usr/src/kerberos5/tools/asn1_compile/../../../crypto/heimdal/lib/asn1/gen.c
In file included from ./roken.h:61,
 from
/usr/src/kerberos5/tools/asn1_compile/../../../crypto/heimdal/lib/asn1/gen_l
ocl.h:51,
 from
/usr/src/kerberos5/tools/asn1_compile/../../../crypto/heimdal/lib/asn1/gen.c
:34:
/usr/include/resolv.h:320: error: syntax error before "ns_tsig_key"
*** Error code 1

Stop in /usr/src/kerberos5/tools/asn1_compile.
*** Error code 1

Stop in /usr/src/kerberos5/tools.
*** Error code 1

Stop in /usr/src.
*** Error code 1 

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


Stable Build Error

2006-04-24 Thread Lawrence Farr
I've been seeing the following for a week or so, and have 
deleted /usr/obj , re-cvsupped and run 

cd /usr/src && make cleandir && make cleandir

make.conf is empty. Anyone got any ideas? 

===> kerberos5/tools/make-roken (all)
===> kerberos5/tools/asn1_compile (all)
cd /usr/src/kerberos5/tools/asn1_compile/../make-roken && make
cc -O2 -fno-strict-aliasing -pipe
-I/usr/src/kerberos5/tools/asn1_compile/../../../crypto/heimdal/lib/roken
-I/usr/src/kerberos5/tools/asn1_compile/../../../crypto/heimdal/lib/asn1 -I.
-DHAVE_CONFIG_H -I/usr/src/kerberos5/tools/asn1_comp
ile/../../include -DINET6  -I/usr/obj/usr/src/tmp/legacy/usr/include -c
/usr/src/kerberos5/tools/asn1_compile/../../../crypto/heimdal/lib/asn1/gen.c
In file included from ./roken.h:61,
 from
/usr/src/kerberos5/tools/asn1_compile/../../../crypto/heimdal/lib/asn1/gen_l
ocl.h:51,
 from
/usr/src/kerberos5/tools/asn1_compile/../../../crypto/heimdal/lib/asn1/gen.c
:34:
/usr/include/resolv.h:320: error: syntax error before "ns_tsig_key"
*** Error code 1

Stop in /usr/src/kerberos5/tools/asn1_compile.
*** Error code 1

Stop in /usr/src/kerberos5/tools.
*** Error code 1

Stop in /usr/src.
*** Error code 1

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


Stable Build Error

2006-04-24 Thread Lawrence Farr
I've been seeing this for a week or so, and have deleted
/usr/obj and run make


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


RE: Promise TX4300 boot problems

2005-11-16 Thread Lawrence Farr

> 
> > I've stuck a Promise TX4300 controller in to replace
> > the marvell onboard SATA that I can't boot off on a
> > Supermicro server. If I set 2 discs up as Raid 0
> > or Raid 1 it's fine, But 4 discs as Raid 0+1 is detected,
> > installs without any problems, but hangs at the boot
> > loader with elf32_loadimage: read failed. I'm guesssing
> > the boot loader thinks it's a mirror, not a stripe and
> > fails to read past the first stripe on the disk?
> 
> If this is the case then its a bug in the controller 
> firmware; loader is
> just doing BIOS I/O calls. Check for a firmware update for your
> controller.


It's the latest version of the firmware. I'll go back to using
a mirror.

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


Promise TX4300 boot problems

2005-11-15 Thread Lawrence Farr
I've stuck a Promise TX4300 controller in to replace
the marvell onboard SATA that I can't boot off on a
Supermicro server. If I set 2 discs up as Raid 0
or Raid 1 it's fine, But 4 discs as Raid 0+1 is detected, 
installs without any problems, but hangs at the boot 
loader with elf32_loadimage: read failed. I'm guesssing 
the boot loader thinks it's a mirror, not a stripe and
fails to read past the first stripe on the disk?

Anyone come across this or have an idea?  


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


RE: CONSPEED=19200 broken/changed on 5.4?

2005-06-08 Thread Lawrence Farr
I use:

BOOT_COMCONSOLE_SPEED=  115200

In my make.conf and that does the trick for me. 

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of 
> Michael W. Lucas
> Sent: 08 June 2005 15:03
> To: [EMAIL PROTECTED]
> Subject: CONSPEED=19200 broken/changed on 5.4?
> 
> Hi,
> 
> I'm building a nanobsd image on i386 5.4-stable for a Soekris net4801.
> My kernel includes
> 
> options   CONSPEED=19200
> 
> so that the serial console "just works".  (Soekris hardware defaults
> to 19200; having the BIOS at 19200 and the OS at 9600 is just
> annoying.)
> 
> When I boot, however, the console speed remains unchanged.  I've
> confirmed that the Soekris is running on my custom kernel.
> 
> I know this worked with 4.mumble; has something changed?
> 
> Thanks,
> ==ml
> 
> -- 
> Michael W. Lucas  [EMAIL PROTECTED], 
> [EMAIL PROTECTED]
>   http://www.BlackHelicopters.org/~mwlucas/
> 
> "The cloak of anonymity protects me from the nuisance of 
> caring." -Non Sequitur
> ___
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to 
> "[EMAIL PROTECTED]"
> 

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


RE: Netgear MA301 PCI->PCMCIA bridge in 4.6.2/4.7?

2002-09-19 Thread Lawrence Farr

Yep.  They work fine:

wi0:  port 0xdf00-0xdf3f,0xd880-0xd8ff mem
0xdfffe000-0xdfffefff irq 10 at device 9.0 on pci0
wi0: 802.11 address: 00:30:ab:09:5e:ed
wi0: using RF:PRISM2 MAC:HFA3841 CARD:HWB3163 rev.B
wi0: Intersil Firmware: Primary 0.03.00, Station 0.08.03



Lawrence Farr
EPC Direct Limited 

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED]] On Behalf Of Matt Sealey
> Sent: 19 September 2002 16:52
> To: [EMAIL PROTECTED]
> Subject: Netgear MA301 PCI->PCMCIA bridge in 4.6.2/4.7?
> 
> 
> 
> Hewwo,
> 
> Anyone know the precise status of support for the Netgear 
> MA301 PCI card in
> STABLE or
> the last release?
> 
> I think I can get one dirt cheap with the MA401 PCMCIA card 
> bundled, but
> dirt cheap is still
> £50, and £50 is more than I want to spend on hardware my server won't
> support properly.
> 
> If there is support, but it's not enabled/compiled in to if_wi (??) by
> default, anyone know a
> URL with instructions/commands/code to enable it? I see there 
> is decent
> support for the
> PCMCIA part anyway, so it's just a matter of making the 
> system use the PCI
> bridge, I
> assume.
> 
> Thanks a lot in advance..
> 
> --
> Matt <[EMAIL PROTECTED]>
> 
> 
> 
> 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: Bigger Harddisk

2002-01-10 Thread Lawrence Farr

And there's Dan O'Connor's excellent info on 
http://www.mostgraveconcern.com/freebsd/

See the "Moving to a Larger Hard Drive" section.

Lawrence Farr
EPC Direct Limited 

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED]] On Behalf Of 
> Christopher Schulte
> Sent: 10 January 2002 07:46
> To: Erich Zigler; [EMAIL PROTECTED]
> Subject: Re: Bigger Harddisk
> 
> 
> At 12:20 AM 1/10/2002 -0600, Erich Zigler wrote:
> >I have recently freed up a couple partitions on my hard 
> drive. I would like
> >to expand the FreeBSD partition. Is this possible?
> 
> If you're running FreeBSD 4.4 or later, growfs(8) may be able 
> to help you.
> 
> >--
> >I like work. I can sit here and watch it for hours.
> 
> --chris
> 
> 
> 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: mmap busted in 4.3?

2001-12-05 Thread Lawrence Farr

Will this patch sort out problems with audio extraction on my
A7V-E or A7M266? I get read timeouts in FreeBSD, but it's happy
in Win2K. If it's worth a try, can someone mail me with it?

Cheers!

Lawrence Farr
EPC Direct Limited 

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED]] On Behalf Of Steve 
> O'Hara-Smith
> Sent: 05 December 2001 18:06
> To: Steve O'Hara-Smith
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; 
> [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: mmap busted in 4.3?
> 
> 
> On Wed, 5 Dec 2001 07:05:28 +0100
> "Steve O'Hara-Smith" <[EMAIL PROTECTED]> wrote:
> 
> SOS> On Wed, 05 Dec 2001 11:21:47 +1030 (CST)
> SOS> "Daniel O'Connor" <[EMAIL PROTECTED]> wrote:
> SOS> 
> SOS> DO> pressed to get 2 copies correct in a row). However 
> the patch appears to make
> SOS> DO> the machine rather unstable :(
> SOS> 
> SOS>  Hmm, mine seems solid as a rock - I've just started a
> SOS> make -j2 buildworld loop as a stress test. I'll let you 
> know in about 12
> SOS> hours.
> 
>   Still running fine - I'm hitting ^C.
> 
> -- 
> C:>WIN  | 
> Directable Mirrors
> The computer obeys and wins.|A Better Way 
> To Focus The Sun
> You lose and Bill collects. |  licenses 
> available - see:
> |   
http://www.sohara.org/

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: 4.4-STABLE crashes - suspects new ata-driver over wd-driver

2001-11-29 Thread Lawrence Farr

As in powers off? How bigs the PSU?

Lawrence Farr
EPC Direct Limited 

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED]] On Behalf Of Morsal Roudbay
> Sent: 29 November 2001 10:45
> To: Kristian K. Nielsen
> Cc: [EMAIL PROTECTED]
> Subject: Re: 4.4-STABLE crashes - suspects new ata-driver 
> over wd-driver
> 
> 
> I seem to have the same problem... when my IDE drive is under 
> heavy use the
> whole computer goes down. :( It's my server so it's very 
> serious. My root
> partition is a SCSI drive.. the IDE drive is only used for 
> ports... and the
> computer often shuts down when I run the command "portsdb 
> -uU"... (heavy
> disk usage)
> 
> 
> On Sat, Oct 13, 2001 at 03:06:56PM +0200, Kristian K. Nielsen wrote:
> > Hey,
> > 
> > Motherboard hardware:  ASUS P2B with ASUS latest BIOS update 1012
> > 
> > Recently I upgraded my good FreeBSD server from 3.5-STABLE 
> to 4.4-STABLE and
> > after
> > that the kernel has constantly being panicing.
> > Before upgrading I never have had unexpected kernel panics 
> - now the box
> > goes down
> > with a day.
> > I suspects the new ata-driver since the panics seem to 
> happened when there
> > is most disk
> > activity like seeks or copying lots of data from one place 
> to another.
> > 
> > The panic could look like this - here stangely in an 
> inactive RealServer
> > (but seem to happen in any running process not nesserily 
> the one causing the
> > diskactivity):
> > 
> > IdlePTD 3276800
> > initial pcb at 2966c0
> > panicstr: page fault
> > panic messages:
> > ---
> > Fatal trap 12: page fault while in kernel mode
> > fault virtual address   = 0x7145cfb0
> > fault code  = supervisor read, page not present
> > instruction pointer = 0x8:0xc01496d2
> > stack pointer   = 0x10:0xd720ef20
> > frame pointer   = 0x10:0xd720ef38
> > 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 = 364 (rmserver)
> > interrupt mask  = none
> > trap number = 12
> > panic: page fault
> > 
> > syncing disks... 104 13 10 9 8
> > done
> > Uptime: 18h53m51s
> > 
> > 
> > 
> > dmesg returns:
> > Copyright (c) 1992-2001 The FreeBSD Project.
> > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 
> 1992, 1993, 1994
> > The Regents of the University of California. All 
> rights reserved.
> > FreeBSD 4.4-STABLE #0: Wed Oct 10 23:33:25 CEST 2001
> > [EMAIL PROTECTED]:/usr/src/sys/compile/JKKN_KRNL
> > Timecounter "i8254"  frequency 1193182 Hz
> > Timecounter "TSC"  frequency 300683475 Hz
> > CPU: Pentium II/Pentium II Xeon/Celeron (300.68-MHz 686-class CPU)
> >   Origin = "GenuineIntel"  Id = 0x634  Stepping = 4
> > 
> > 
> Features=0x80f9ff PGE,MCA,CMOV,M
> > MX>
> > real memory  = 402640896 (393204K bytes)
> > avail memory = 387919872 (378828K bytes)
> > Preloaded elf kernel "kernel" at 0xc0301000.
> > Pentium Pro MTRR support enabled
> > Using $PIR table, 6 entries at 0xc00f0d10
> > npx0:  on motherboard
> > npx0: INT 16 interface
> > pcib0:  on motherboard
> > pci0:  on pcib0
> > pcib1:  at 
> device 1.0 on pci0
> > pci1:  on pcib1
> > isab0:  at device 4.0 on pci0
> > isa0:  on isab0
> > atapci0:  port 0xd800-0xd80f 
> at device 4.1 on
> > pci0
> > ata0: at 0x1f0 irq 14 on atapci0
> > ata1: at 0x170 irq 15 on atapci0
> > pci0:  at 4.2
> > chip1:  port 
> 0xe800-0xe80f at
> > device 4.3 on pci0
> > rl0:  port 0xd000-0xd0ff mem
> > 0xe300-0xe3ff irq 10 at device 10.0 on pci0
> > rl0: Ethernet address: 00:40:95:30:2e:5e
> > miibus0:  on rl0
> > rlphy0:  on miibus0
> > rlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> > pci0:  at 12.0 irq 11
> > orm0:  at iomem 0xc-0xc7fff on isa0
> > fdc0:  at port 0x3f0-0x3f5,0x3f7 irq 6 
> drq 2 on isa0
> > fdc0: FIFO enabled, 8 bytes threshold
> > fd0: <1440-KB 3.5" drive> on fdc0 drive 0
> > atkbdc0:  at port 0x60,0x64 on isa0
> > vga0:  at port 0x3c0-0x3df iomem 
> 0xa-0xb on isa0
> > sc0:  at flags 0x100 on isa0
> > sc0: VGA <16 virtual consoles, flags=0x300>
> > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0

RE: end of 3ware IDE

2001-10-04 Thread Lawrence Farr

More importantly, do they work? They used to be next to useless.

>-Original Message-
>From: [EMAIL PROTECTED] 
>[mailto:[EMAIL PROTECTED]] On Behalf Of Len Conrad
>Sent: 04 October 2001 12:48
>To: [EMAIL PROTECTED]
>Subject: Re: end of 3ware IDE
>
>
>
>>>www.highpoint-tech.com
>>
>>How does it work in RAID mode ?  Is there a way to detect 
>raid sets gone bad?
>
>Are there any boards available?
>
>Len
>
>
>http://MenAndMice.com/DNS-training
>http://BIND8NT.MEIway.com : ISC BIND 8.2.4 for NT4 & W2K
>http://IMGate.MEIway.com  : Build free, hi-perf, anti-abuse 
>mail gateways
>
>
>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: Spontanous reboot on SMP system FBSD 4.4-RC

2001-09-05 Thread Lawrence Farr

>weeks. The reason why the machine
>gets so often rebooted is because we do very often cvsupdates, 
>almost every day. 

Why do you do this to a production machine, and then get surprised when
it doesn't work???


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



RE: Kernel Compile failure

2001-08-08 Thread Lawrence Farr

Ive had odd errors when using full stops and hyphens in kernel names,
that
have been fixed by changing the filename.

-Original Message-
From: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED]] On Behalf Of Odhiambo 
Washington
Sent: 08 August 2001 12:57
To: FBSD-STABLE
Subject: Kernel Compile failure


CVSUP yesterday (07-08-2001)
FreeBSD-4.3-STABLE

While compiling a new kernel after buildworld/installworld:

##
fformat-extensions -ansi -c setdef0.c
cc -nostdinc -O -pipe   -DIPV6FIREWALL  -D_KERNEL -Wall 
-Wredundant-decls
-Wnest
ed-externs -Wstrict-prototypes  -Wmissing-prototypes 
-Wpointer-arith -Winline -W cast-qual  -fformat-extensions 
-ansi -DKLD_MODULE -nostdinc -I-  -I. -I@ -I@/../ include  
-mpreferred-stack-boundary=2 -Wall -Wredundant-decls 
-Wnested-externs - Wstrict-prototypes  -Wmissing-prototypes 
-Wpointer-arith -Winline -Wcast-qual  - fformat-extensions 
-ansi -c setdef1.c ld -Bshareable  -o ip6fw.ko setdef0.o 
ip6fw.kld setdef1.o ===> ipfilter
*** Error code 2
Stop in /usr/src/sys/modules.
*** Error code 1
Stop in /usr/obj/usr/src/sys/Kern4.x.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.

##

Someone can point me to a soln. I don't know what to search for 
on the archives. A body search in my -stable mailbox yielded nothing.


TIA

-Wash

--
Odhiambo Washington
Wananchi Online Ltd.,
[EMAIL PROTECTED] 1st Flr Loita Hse.
Tel: 254 2 313985 Loita Street.,
Fax: 254 2 313922 PO Box 10286,00100-NAIROBI,KE.

Any philosophy that can be put "in a nutshell" belongs there. 
-Sydney J. Harris 


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



RE: Athlon and 4.2 Release

2001-01-16 Thread Lawrence Farr

I also have a 950 Athlon on an A7v with cheap PC133 ram, and a seagate
Barracuda IDE drive on the UDMA66 channel at home. Rock stable, does a
buildworld
in 45 minutes!.

Sat next to me is an A7v with cheap PC133 ram, a Quantum drive on the
UDMA100
channel that also is rock stable. Both the 1004 BIOS, set to optimal, and
running
4-STABLE. Only time I had problems was when I left the squidgy pink thermal
paste
on the heatsink that made it overheat. Cleaning it off resulted in a stable
system.

Oh and as to load, it ran 10 consecutive buildworlds with -j4 as a test with
no
problems.

Lawrence Farr
EPC Direct Limited mailto:[EMAIL PROTECTED]
T:01179666123 F:01179666111 M:07970780901



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