Bootloader gave me this error message:
---
BTX loader 1.00 BTX version is 1.01
Consoles: internal video/keyboard
_
int=000d err= efl=00030002 eip=2abf
eax=0300 ebx= ecx=0001 edx=009f
esi=000c edi=000
On Fri, May 25, 2007 at 12:07:10PM +0930, Shaun Branden wrote:
> uname -a
> FreeBSD sagan.cai 6.2-STABLE FreeBSD 6.2-STABLE #0: Sat May 5 23:34:08 CST
> 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SAGAN i386
>
> The results of make buildworld on this system:
>
> ide -k _crunched_chroot_stu
On Fri, May 25, 2007 at 12:28:18PM +0400, Ruslan Ermilov wrote:
> On Fri, May 25, 2007 at 12:07:10PM +0930, Shaun Branden wrote:
> IEEE80211_IS_CHAN_PASSIVE() is a macro defined in
> src/sys/net80211/_ieee80211.h. Check that you have an up-to-date
> copy of that file in /usr/src. If you have it
On 05/25/07 11:07, Volker wrote:
...
I'm using the following additional kernel options:
makeoptions DEBUG=-g
options KDB
options KDB_UNATTENDED
options KDB_TRACE
options DDB
options WITNESS
options WITNESS_SKIPSPIN
options INVARIANTS
op
Kris, Roger & all,
On 05/23/07 23:58, Kris Kennaway wrote:
On Wed, May 23, 2007 at 11:31:32PM +0100, Volker wrote:
talking to myself... ;)
On 2007-05-23 10:27, Volker wrote:
Unfortunately three hours later, the machine died completely. It has
been a hardware failure which came quietly.
Sorry
On Fri, May 25, 2007 at 07:06:38PM +0930, Shaun Branden wrote:
> On Fri, May 25, 2007 at 12:28:18PM +0400, Ruslan Ermilov wrote:
> > On Fri, May 25, 2007 at 12:07:10PM +0930, Shaun Branden wrote:
>
> > IEEE80211_IS_CHAN_PASSIVE() is a macro defined in
> > src/sys/net80211/_ieee80211.h. Check tha
JoaoBR wrote:
> same as ipfw some weeks ago :S
> lucky us that atapicam is an exotic driver and not so widely used and still
> more lucky us that it is atapicam and not ahd or aac right? Sorry dear
> clients our mail cluster is out of service and when it does not work in
> three
> weeks o
[EMAIL PROTECTED] wrote:
cvsup and built around 20.30 BST
cd /usr/src; make -f Makefile.inc1 install
===> share/info install
===> include install
creating osreldate.h from newvers.sh
touch: not found
***error code 127
Stop in /usr/src/include
***error code 1
I tried cd usr.bin/touch && make && ma
On Fri, May 25, 2007 at 01:58:51PM +0400, Ruslan Ermilov wrote:
> You have an incomplete source tree. Jan 28 corresponds to
> rev. 1.2.2.3 of that file, and the IEEE80211_IS_CHAN_PASSIVE()
> define was added in rev. 1.2.2.4. From CVS history:
>
> : revision 1.2.2.4
> : date: 2007/03/10 00:28:43
Hi all,
I know there have been some issues with the src tree , which DES fixed. I just
updated my tree, but i'm getting the following when building GENERIC:
---
sudo make buildkernel KERNCONF=GENERIC
[]
m large-function-growth=1000 -mno-align-long-strings
-mpreferred-stack-boundary=2 -mn
On Fri, May 25, 2007 at 11:44:51AM +0100, Tom Judge wrote:
> [EMAIL PROTECTED] wrote:
> > cvsup and built around 20.30 BST
> > cd /usr/src; make -f Makefile.inc1 install
> > ===> share/info install
> > ===> include install
> > creating osreldate.h from newvers.sh
> > touch: not found
> > ***error
On Friday 25 May 2007 07:21:24 Oliver Fromme wrote:
>
> First, I don't think atapicam is an "exotic" driver.
> I'm using it for several years (in fact, since it was an
> inofficial patch, before it hit the repository). It's
> working perfectly fine for me, including with today's
> RELENG_6.
>
> S
On Fri, 25 May 2007 20:24:18 +1000
Norberto Meijome <[EMAIL PROTECTED]> wrote:
> Hi all,
> I know there have been some issues with the src tree , which DES fixed. I
> just updated my tree, but i'm getting the following when building GENERIC:
>
well, thanks to my fellow Aussie Shaun Branden, i m
Using a debug kernel, the machine came up quickly with this LOR
after the reboot:
lock order reversal:
1st 0xc077078c tcp (tcp) @ /usr/src/sys/netinet/tcp_input.c:625
2nd 0xc4f18180 pf task mtx (pf task mtx) @
/usr/src/sys/modules/pf/../../contrib/pf/net/pf.c:6386
KDB: stack backtrace:
kdb_b
Hello List,
We have a network appliance that is currently based on 4.9. We are in
the process of releasing
a new version based on 6.1 stable.
In our testing using nttcp thru the appliance we see insignifant
difference in thruput between the 2
versions in a controlled environment - aproximate
We have a network appliance that is currently based on 4.9. We are in
the process of releasing
a new version based on 6.1 stable.
In our testing using nttcp thru the appliance we see insignifant
difference in thruput between the 2
versions in a controlled environment - aproximately 94mbs on a 100
I noticed after cvsup'ing the other day (6.2-stable) that /etc/rc.d
now has some issues:
# rcorder /usr/src/etc/rc.d/*
rcorder: requirement `zfs' in file `/usr/src/etc/rc.d/FILESYSTEMS'
has no providers.
(removing 'zfs' in FILESYSTEMS fixes this)
and then this later on with rcorder:
..
...
/
Stephen Clark wrote:
> Hello List,
>
> We have a network appliance that is currently based on 4.9. We are in
> the process of releasing
> a new version based on 6.1 stable.
You are going to get asked this, so I'll ask first.
Whats the reason behind not running a more recent STABLE? I understand
d
On Friday 25 May 2007 04:07, Volker wrote:
> Kris, Roger & all,
> well, we replaced the broken machine (totally different hardware),
> took one of the mirrored hard disks into this replacement machine
> and took this replacement into production.
>
> Unfortunately it took less than 16 hours for this
On Fri, 2007-05-25 at 14:51 +0100, Steven Hartland wrote:
> Why are you releasing a new product on an already unsupported version?
> 6.2 is the version you really need to be moving to not 6.1.
FreeBSD 6.1 is not unsupported - far from it. When 6.1 was released, it
was designated as an "Extended s
On Fri, May 25, 2007 at 07:42:10AM -0500, JD Bronson wrote:
> I noticed after cvsup'ing the other day (6.2-stable) that /etc/rc.d
> now has some issues:
>
> # rcorder /usr/src/etc/rc.d/*
> rcorder: requirement `zfs' in file `/usr/src/etc/rc.d/FILESYSTEMS'
> has no providers.
>
> (removing 'zfs'
Why are you releasing a new product on an already unsupported version?
6.2 is the version you really need to be moving to not 6.1.
With respect to your actual question you provide no real details so
there's no real answers. You need to provider info on hardware, configuration
and application + co
Stephen Clark wrote:
> Dominic Marks wrote:
>
>> Stephen Clark wrote:
>>
>>
>>> Hello List,
>>>
>>> We have a network appliance that is currently based on 4.9. We are in
>>> the process of releasing
>>> a new version based on 6.1 stable.
>>>
>>
>> You are going to get asked this, so I'll ask
On 05/25/07 15:01, Roger Miranda - Digital Relay Inc. wrote:
...
Volker & Kris,
Sorry for kind of hi-jacking your thread. Just hopefully we all can work
together to fix this issue (if there is one).
For me, that's ok as it may (or may not) be a similar problem.
Out machine did goto in to a
On 05/25/07 13:45, Volker wrote:
Using a debug kernel, the machine came up quickly with this LOR after
the reboot:
lock order reversal:
1st 0xc077078c tcp (tcp) @ /usr/src/sys/netinet/tcp_input.c:625
2nd 0xc4f18180 pf task mtx (pf task mtx) @
/usr/src/sys/modules/pf/../../contrib/pf/net/pf.c
I have a shiny new Sun X4100 here and it works pretty well (except
that there is a bug in the ILOM bios that refuses to let the serial
port console run at 115200!!!)
I attached an external RAID array using an LSI fibre channel card,
and now the boot disk is not found after the kernel boots.
On Fri, May 25, 2007 at 12:00:28PM +, [EMAIL PROTECTED] wrote:
>
> Today's Topics:
>
> 14. Re: atapicam cd error from freebsd-stable Digest, Vol 207,
> Issue 6 (Oliver Fromme)
> --
>
> Date: Fri, 25 May 2007 12:21:24 +0200 (CEST)
> From: Oliver Fromme <[EMA
On Fri, 25 May 2007, Stephen Clark wrote:
[..]
> >>He has been comparing the 6.1 system to 4.9 system for a couple of weeks
> >>and continues to insist the 6.1 version is much slower.
[..]
> In subjective tests R&D has done using the following setup we see "no"
> problem:
>
> freebsd+firefo
Vivek Khera wrote:
I have a shiny new Sun X4100 here and it works pretty well (except that
there is a bug in the ILOM bios that refuses to let the serial port
console run at 115200!!!)
I attached an external RAID array using an LSI fibre channel card, and
now the boot disk is not found after
- Original Message -
From: "Stephen Clark" <[EMAIL PROTECTED]>
One of our testers has the same setup but is using winblows/ie in place of
freebsd+firefox and subjectively says the 6.1 system is slower than the
4.9 system.
I was just wandering if there were any tunables that might cause
- Original Message -
From: "Gavin Atkinson" <[EMAIL PROTECTED]>
FreeBSD 6.1 is not unsupported - far from it. When 6.1 was released, it
was designated as an "Extended support" branch, and is currently
scheduled to be supported (from a security point of view) after support
for 6.2 is drop
Vivek Khera wrote:
> I have a shiny new Sun X4100 here and it works pretty well (except that
> there is a bug in the ILOM bios that refuses to let the serial port
> console run at 115200!!!)
>
> I attached an external RAID array using an LSI fibre channel card, and
> now the boot disk is not found
Dominic Marks wrote:
Stephen Clark wrote:
Hello List,
We have a network appliance that is currently based on 4.9. We are in
the process of releasing
a new version based on 6.1 stable.
You are going to get asked this, so I'll ask first.
Whats the reason behind not running a more rece
On Friday 25 May 2007 15:05, Stephen Clark wrote:
> We have a person that is testing the both system inhouse surfing out
> over the internet on our T1 link and he complains that he is consistently
seeing the 6.1 version being much slower than the
> 4.9 version (on the same hardware).
FreeBSD cann
On 5/25/07, Norberto Meijome <[EMAIL PROTECTED]> wrote:
On Fri, 25 May 2007 20:24:18 +1000
Norberto Meijome <[EMAIL PROTECTED]> wrote:
> Hi all,
> I know there have been some issues with the src tree , which DES fixed. I
just updated my tree, but i'm getting the following when building GENERIC:
Joe Altman wrote:
> You have atapicam as a kernel module; and what version of atapi-cam.c?
No, I've always compiled it statically in my kernel.
> It looks like this one is current: Revision 1.54
That's the HEAD version (in 7-current).
The version is RELENG_6 is 1.42.2.5, which is practically
JoaoBR wrote:
> Roland Smith wrote:
> > It didn't. All the drivers were in one huge package, the X server. Now
> > they are in seperate ports. But the xorg or xorgs-drivers meta-ports
> > should install all of them.
>
> ok, that is what I ment, the better way would be that portupgrade instal
On Fri, May 25, 2007 at 06:30:00PM +0200, Oliver Fromme wrote:
> Joe Altman wrote:
> > You have atapicam as a kernel module; and what version of atapi-cam.c?
>
> No, I've always compiled it statically in my kernel.
That's what I meant to say; that it was a device in the kernel:
device atapicam
Ruslan Ermilov writes:
On Fri, May 25, 2007 at 11:44:51AM +0100, Tom Judge wrote:
[EMAIL PROTECTED] wrote:
> cvsup and built around 20.30 BST
> cd /usr/src; make -f Makefile.inc1 install
> ===> share/info install
> ===> include install
> creating osreldate.h from newvers.sh
> touch: not found
Ruslan Ermilov wrote at 14:55 +0400 on May 25, 2007:
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/troubleshoot.html#TOUCH-NOT-FOUND
Someone should update that doc for the much simpler and probably more
common case of someone touching newvers.sh (e.g., cvsup) after doing a
buildworld and
Tom Judge wrote at 11:44 +0100 on May 25, 2007:
> [EMAIL PROTECTED] wrote:
> > cvsup and built around 20.30 BST
> > cd /usr/src; make -f Makefile.inc1 install
> > ===> share/info install
> > ===> include install
> > creating osreldate.h from newvers.sh
> > touch: not found
> > ***error code
Stephen Clark wrote:
> The appliance is basically a firewall/nat/vpn device. We started on 6.1
> last year and it has
> taken us a while to get things tested, plus I don't like to use a brand
> new release. If we go to
> a later release it means we have to do complete regression testing, etc
On Fri, 25 May 2007 18:30:00 +0200 (CEST)
Oliver Fromme <[EMAIL PROTECTED]> wrote:
>
>
> By the way, I am _not_ using k3b or any other krap. ;-)
>
> Best regards
>Oliver
>
What is Krap to one can be Komfort to another. ;-)
I assist a photographer fiend by maintaining her computers, networ
On Fri, May 25, 2007 at 05:17:02PM +0200, Volker wrote:
> My assumption: The LORs are somewhat pf related but are not related
> to the lockdown of the system. Am I correct?
No, they could be the cause. Make sure you have read the BUGS section
of pf.conf, and if this is not relevant to your conf
On Fri, May 25, 2007 at 03:17:40PM +0100, Gavin Atkinson wrote:
> On Fri, 2007-05-25 at 14:51 +0100, Steven Hartland wrote:
> > Why are you releasing a new product on an already unsupported version?
> > 6.2 is the version you really need to be moving to not 6.1.
>
> FreeBSD 6.1 is not unsupported
On Fri, May 25, 2007 at 09:46:35AM -1000, Robert Marella wrote:
> On Fri, 25 May 2007 18:30:00 +0200 (CEST)
> Oliver Fromme <[EMAIL PROTECTED]> wrote:
>
> >
> >
> > By the way, I am _not_ using k3b or any other krap. ;-)
> >
> > Best regards
> >Oliver
> >
> What is Krap to one can be Komfo
Roland Smith wrote:
Tools like portupgrade and portmaster and even the ports system are
great but they have their limitations. I think they are kept relatively
simple for a reason. It's much better to have a simple (maintainable)
tool that does 95% of the jobs well than to build an extremely
com
On Fri, 25 May 2007 22:02:13 +0200
Roland Smith <[EMAIL PROTECTED]> wrote:
> On Fri, May 25, 2007 at 09:46:35AM -1000, Robert Marella wrote:
> > On Fri, 25 May 2007 18:30:00 +0200 (CEST)
> > Oliver Fromme <[EMAIL PROTECTED]> wrote:
> >
> > >
> > >
> > > By the way, I am _not_ using k3b or any ot
Joe Altman wrote:
On Fri, May 25, 2007 at 06:30:00PM +0200, Oliver Fromme wrote:
Joe Altman wrote:
> You have atapicam as a kernel module; and what version of atapi-cam.c?
No, I've always compiled it statically in my kernel.
That's what I meant to say; that it was a device in the kernel:
de
On Fri, May 25, 2007 at 10:40:31AM -1000, Robert Marella wrote:
> > dirsplit (http://freshmeat.net/projects/dirsplit/) will do the trick
> > nicely.
> >
> > Roland
>
> Roland
>
> Thanks for the reply. Mea culpa, I failed to mention that the
> individual file cannot be spread over different media
On Fri, 25 May 2007, Volker wrote:
Using a debug kernel, the machine came up quickly with this LOR after the
reboot:
lock order reversal:
1st 0xc077078c tcp (tcp) @ /usr/src/sys/netinet/tcp_input.c:625
2nd 0xc4f18180 pf task mtx (pf task mtx) @
/usr/src/sys/modules/pf/../../contrib/pf/net/pf.
On Friday 25 May 2007 13:54:04 Oliver Fromme wrote:
> JoaoBR wrote:
> > Roland Smith wrote:
> > > It didn't. All the drivers were in one huge package, the X server. Now
> > > they are in seperate ports. But the xorg or xorgs-drivers meta-ports
> > > should install all of them.
> >
> > ok, tha
Tim Bishop wrote:
On Fri, May 25, 2007 at 07:42:10AM -0500, JD Bronson wrote:
I noticed after cvsup'ing the other day (6.2-stable) that /etc/rc.d
now has some issues:
# rcorder /usr/src/etc/rc.d/*
rcorder: requirement `zfs' in file `/usr/src/etc/rc.d/FILESYSTEMS'
has no providers.
(removing
Stephen Clark wrote:
> Hello List,
>
> We have a network appliance that is currently based on 4.9. We are in
> the process of releasing
> a new version based on 6.1 stable.
>
> In our testing using nttcp thru the appliance we see insignifant
> difference in thruput between the 2
> versions in a con
On 5/25/07, JoaoBR <[EMAIL PROTECTED]> wrote:
... it tells to run script xorg-upgrade but this xorg-upgrade does not exist
either
The UPDATING entry does not tell you to run a script named
xorg-upgrade, it tells you to run the script(1) command, which will
then save all output to the file xorg-
On May 25, 2007, at 11:22 AM, Scott Long wrote:
Look in /sys/conf/NOTES for a long discussion on wiring SCSI device
order.
Thanks! That looks like it should do the trick. I'm assuming those
go into /boot/loader.conf or do they go into the kernel config file
itself? They look like loade
On May 25, 2007, at 11:23 AM, Michael Proto wrote:
I believe you can use the following in your kernel config:
options ROOTDEVNAME=\"ufs:da2s1"
Or whatever the appropriate device/slice for your mpt2 controller.
That doesn't seem like it will be of much use since the device unit
na
On Fri, May 25, 2007 at 08:05:15AM -0400, Stephen Clark wrote:
> Hello List,
>
> We have a network appliance that is currently based on 4.9. We are in
> the process of releasing
> a new version based on 6.1 stable.
>
> In our testing using nttcp thru the appliance we see insignifant
> differenc
Vivek Khera wrote:
On May 25, 2007, at 11:22 AM, Scott Long wrote:
Look in /sys/conf/NOTES for a long discussion on wiring SCSI device
order.
Thanks! That looks like it should do the trick. I'm assuming those go
into /boot/loader.conf or do they go into the kernel config file
itself? The
FWIW, IMO- don't wire- use glabel instead.
On 5/25/07, Scott Long <[EMAIL PROTECTED]> wrote:
Vivek Khera wrote:
> On May 25, 2007, at 11:22 AM, Scott Long wrote:
>
>> Look in /sys/conf/NOTES for a long discussion on wiring SCSI device
>> order.
>
> Thanks! That looks like it should do the trick
On May 25, 2007, at 11:20 PM, Matthew Jacob wrote:
FWIW, IMO- don't wire- use glabel instead.
That's pretty neat, too!
I think I like this one better since I won't have to make a special
case in my system config file generator for this one host.
__
On May 25, 2007, at 11:20 PM, Matthew Jacob wrote:
FWIW, IMO- don't wire- use glabel instead.
Hmmm... minor question: how does one deal with swap partitions?
I tried as a test "glabel label -v swap1 /dev/aacd0s2b" but it
doesn't show up as a label with "glabel list", and trying to stop it
62 matches
Mail list logo
