On Mon, Oct 27, 2003 at 02:46:03PM -0500, Andre Guibert de Bruet
[EMAIL PROTECTED] wrote:
On Tue, 21 Oct 2003, Vallo Kallaste wrote:
I went back to last known good kernel/world combination, which is
from September 16. The next and problematic kernel/world pair is
from September 30. So
On Mon, Oct 20, 2003 at 04:38:32PM +0300, Vallo Kallaste
[EMAIL PROTECTED] wrote:
[snip all]
Ok, following up my own email..
I went back to last known good kernel/world combination, which is
from September 16. The next and problematic kernel/world pair is
from September 30. So the problem
, but sometimes non-parallel buildworld will do, only to die
later in installworld.
This is on two-processor AMD 2400+ MP system, ASUS A7M-266D mobo and
1GB ECC memory, ATA disks and CD/RW-DVD only. 4BSD scheduler if it
matters.
--
Vallo Kallaste
___
[EMAIL PROTECTED
had to drive home and reset the system. All those problematic
systems seem to be AMD based.
--
Vallo Kallaste
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
in hurry. The last kernel (4BSD) ran fine for a
month with two seti processes running.
--
Vallo Kallaste
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
and be done with it.
--
Vallo Kallaste
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
network related things etc.
which seemed to indicate such need. I've sent you personal reply.
Sorry.
--
Vallo Kallaste
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL
anyone.
--
Vallo Kallaste
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
.
--
Vallo Kallaste
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
) will show up. This is annoying. Starting up xterm
takes more time as well, but I can live with that.
--
Vallo Kallaste
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL
On Mon, Mar 24, 2003 at 11:18:59PM +0100, Julian St.
[EMAIL PROTECTED] wrote:
Am Mo, 2003-03-24 um 20.33 schrieb Vallo Kallaste:
Current isn't better. This is a long time problem and is most
noticeable when you downgrade from -current to -stable... it's
unforgettable feeling :-P
I
noticeable when you downgrade from -current to -stable... it's
unforgettable feeling :-P
I don't expect it will be fixed in the near future, because it's
been so over a year now. Current has it's weak points and this is
only one of the regressions.
--
Vallo Kallaste
To Unsubscribe: send mail to [EMAIL
is that mouse will
be unresponsive (jumping) and sound skips under X while large ftp
transfer is happening over the 100Mbit interface. Fxp driver and SMP
system if that matters. No cure in the sight.
--
Vallo Kallaste
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current
it the other way (powering off)
as well, to make sure there's no difference.
I'll try to be more clear in the future, but sometimes English feels
really difficult to elucidate the means of oneself.
--
Vallo Kallaste
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current
and restoring operation of non-hotswap disks?
I don't think so. It was more thinking aloud than anything else. As
I said above, this is the way I tested things in the first place.
Ok, I'll try to simulate the disk failure by switching off the
power, then.
Thanks
--
Vallo Kallaste
To Unsubscribe
/2001-08-28-RAIDframe-stable.diff.gz
Had to do some patching by hand, but otherwise works well.
Will it suffice to switch off power for one disk to simulate more
real-world disk failure? Are there any hidden pitfalls for failing
and restoring operation of non-hotswap disks?
--
Vallo Kallaste
.
--
Vallo Kallaste
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
for a moment, then scrolls forward again and so
on. The stopping moments are actually very short, but noticeable.
This is while the seti's are running, 2CPU PIII-500.
--
Vallo Kallaste
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Thu, Mar 06, 2003 at 10:44:21PM +0200, Vallo Kallaste
[EMAIL PROTECTED] wrote:
I'm using SCHED_ULE on my laptop now. My recent round of fixes seems to
have helped out. I'm getting good interactive performance. I'm doing the
following:
nice -5'd for (;;) {} process.
make -j4
if I remember. I've used DTLA and DPTA disk behind PIIX4
controller and have had zero problems after the initial development
did settle.
--
Vallo Kallaste
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Thu, Feb 27, 2003 at 11:53:02AM +0200, Vallo Kallaste vallo wrote:
The vinum R5 and system as a whole were stable without
softupdates. Only one problem remained after disabling softupdates,
while being online and user I/O going on, rebuilding of failed disk
corrupt the R5 volume
it was exactly. I'll need to lend 50-pin SCSI cable
and test vinum again. Will it matter on what version of FreeBSD I'll
try on? My home system runs -current of Feb 5, but if you suggest
-stable for consistent results, I'll do it.
Thanks
--
Vallo Kallaste
To Unsubscribe: send mail to [EMAIL PROTECTED
/installworld
build new kernel/install new kernel
immediately do shutdown -r now
repeat the last two steps as long as you wish or until the problem \
appears
--
Vallo Kallaste
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Wed, Feb 05, 2003 at 11:47:44AM +0200, Vallo Kallaste vallo wrote:
In the last ~three months now I've had 24 kernel crashes, all the
same, all happening in the same circumstances. Happens while cvsup
is running, everytime... except if I remove the checkouts file which
probably causes
, 9 entries at 0xc00f3d20
--
Vallo Kallaste
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
by working around the CPU bug.
Can't say anything for Paul's case, he probably had custom kernel
then? If I can remember peter did the options conditional for CPU
type, so only P4 owners get'em at boot time. Check the Feb 12 commit
logs.
--
Vallo Kallaste
To Unsubscribe: send mail to [EMAIL PROTECTED
before will work, as I
haven't had any problems after enabling them (months of time now).
--
Vallo Kallaste
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Thu, Feb 20, 2003 at 02:28:45PM -0800, Darryl Okahata
[EMAIL PROTECTED] wrote:
Vallo Kallaste [EMAIL PROTECTED] wrote:
I'll second Brad's statement about vinum and softupdates
interactions. My last experiments with vinum were more than half a
year ago, but I guess it still holds. BTW
On Wed, Feb 05, 2003 at 11:47:44AM +0200, Vallo Kallaste vallo wrote:
accumulated filesystem corruption. This is on UFS2 filesystem,
haven't tried UFS1 yet. World and kernel are from January 21, PIII
SMP system. I'll provide any info one needs to track the cause,
needless to say I'm _really_
the disk contents
(~5GB) to other disk to re-newfs the filesystem.
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
iblkno 56 dblkno 3000
cgrotor 139 fmod0 ronly 0 clean 0
flags soft-updates
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
with other work I see no justification to
not mention the brokenness of bgfsck.
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Fri, Dec 20, 2002 at 11:29:19PM +0200, Vallo Kallaste vallo wrote:
Yes, and this undefined symbols message will make no sense
from user perspective.
Then fix it. The fix is trivial:
[description of possible fix snipped]
As I've stated several times and as you most certainly
be unresolved symbols if you try to load ipl.ko w/o
PFIL_HOOKS defined in the kernel.
Yes, and this undefined symbols message will make no sense from
user perspective.
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body
are all on their
place. Somthing is completly screwed up.
Disable ChallengeResponseAuthentication, set it to no and you'll
have ssh again.
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Fri, Dec 20, 2002 at 08:30:42AM -0800, Terry Lambert
[EMAIL PROTECTED] wrote:
Vallo Kallaste wrote:
On Thu, Dec 19, 2002 at 08:46:44PM -0800, Sam Leffler
[EMAIL PROTECTED] wrote:
#ifndef PFIL_HOOKS #error You must specify PFIL_HOOKS when
using ipfilter #endif
Unfortunately
.
_
For the best comics, toys, movies, and more,
please visit http://www.tfaw.com/?qt=wmf
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED
, arg=0x0,
frame=0x0) at ../../../kern/kern_fork.c:866
(kgdb) quit
bash-2.05b# exit
exit
Script done on Thu Dec 12 10:24:41 2002
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
in fork_exit (callout=0xc022c8a0 ithread_loop, arg=0x0,
---Type return to continue, or q return to quit---
frame=0x0) at ../../../kern/kern_fork.c:866
(kgdb) quit
bash-2.05b# exit
exit
Script done on Mon Dec 9 10:25:49 2002
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail
On Fri, Dec 06, 2002 at 10:26:24PM -0500, Alexander Kabaev
[EMAIL PROTECTED] wrote:
On Fri, 6 Dec 2002 23:26:52 +0200
Vallo Kallaste [EMAIL PROTECTED] wrote:
I've built it yesterday together with a lots of other stuff. Using
other -march values than i686 is unofficially claimed
Create/update ZIP files compatible with pkzip
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
-march values than i686 is unofficially claimed to be
unsupported (kan@freebsd). As others I'll bet the -march=p4 is
causing problems, i686 works for me.
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
boot0cfg: /dev/ad0: Operation not permitted
root:vallo# disklabel -W ad0
disklabel: /dev/ad0: Operation not permitted
This is probably related to recent (re)work to protect disk labels,
but I'm not authoritative. This is not a fair way to stick me to
-current :-)
--
Vallo Kallaste
[EMAIL
but is simply missing from the start. Otherwise system is up and
running. I don't think it's coincidence, something is broken and
related to the Tyan mobos we have.
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body
fine for two and half years. Sorry about confusion.
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Mon, Dec 02, 2002 at 10:33:55AM -0800, David O'Brien
[EMAIL PROTECTED] wrote:
On Mon, Dec 02, 2002 at 04:33:27PM +0200, Vallo Kallaste wrote:
I'm not aware of any Tyan Thunder mobos which have onboard
integrated video.
They *all* do. (meaning all the Tyan dual-K7 Thunders)
Sorry
On Fri, Nov 29, 2002 at 06:45:48PM +0200, Vallo Kallaste
[EMAIL PROTECTED] wrote:
I've seen one post similar to this, but not much else. I think maybe the
UFS2 problem had to do with Kirk's recent changes, but the disklabel
issue... I'm wary to reboot my machine! What in the hell could
and the live-current
cd burnt for this purpose (JPSNAP). It's possible to go back in time
and fully restore the system as it were before.
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
nevertheless, so we can test
things out even if it's not going to 5.0-RELEASE. So this boils down
to simple question of time, necessity and willingness to do the
patch. Let's end this thread.
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd
stick with DISABLE_PSE enabled and DISABLE_PG_G disabled for
the time being.
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
freebsd.dk.freebsd.org at:
*default date=2002.11.21.13.56.00
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
to at least test and report problems (or success). Given
that enough people give it a try and report, there's possibility for
import, IMHO.
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
, IMHO.
But who will bell the cat? I vote for Snuffles.
Don't understand. Some inside joke or something based on US centric
TV? What are you trying to tell me? Remember I'm not native.
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd
:
DISABLE_PSE enabled
DISABLE_PG_Gdisabled
Are you interested of the reverse? Can it be that enabling
DISABLE_PSE incorporates DISABLE_PG_G somehow?
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
/ad0s1a on / (ufs, local, soft-updates)
devfs on /dev (devfs, local)
/dev/ad0s1d on /usr (ufs, NFS exported, local, soft-updates)
procfs on /proc (procfs, local)
myhakas:/opt/src-current/src on /usr/src (nfs)
myhakas:/opt/src-current/ports on /usr/ports (nfs, read-only)
root:vallo#
--
Vallo Kallaste
:13 test1
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
, partition c doesn't cover the whole unit!
Warning, An incorrect partition c may cause problems for standard system utilities
root:vallo#
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
the problem.
DP2 shipped with DISABLE_PSE and DISABLE_PG_G in GENERIC. I know
because I put them there.
Is it any help to know that my problems on P4 stopped after enabling
DISABLE_PSE? Initially I had both of these enabled, but seems that
one is enough. Just FYI.
--
Vallo Kallaste
[EMAIL
doesn't work (numlock is not responsive) and
which is most weird, loading acpi.ko triggers following on the
console:
swap_pager_getswapspace: failed
Is it intended behaviour or what I'm missing here?
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED
as it can be.
Thank you all for your hard work!
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
:, copied over from c:
disklabel da1s1 #all is ok
disklabel -r da1s1 #spits out 4 lines of warnings??
Why disklabel complains when using the -r switch? It didn't before.
Yes I haven't used fdisk(8) and disklabel(8) for a long time.
Possibly related to GEOM, as far as I understand.
--
Vallo
/disklabel.c,v 1.63 2002/11/18 04:58:11 julian Exp $
bash-2.05b# exit
exit
Script done on Mon Nov 18 21:49:08 2002
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
if the label is absolute of relative
and DTRT.
Ok, seems not to be over my head. It's confusing to users, that's
the only thing I have to say now. Thank you for explanation.0
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body
-SMP has 512MB and P2 has 380MB. As you
can guess, the P4 system has been given by my employer, hehe ;-)
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
needs a fix.
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
bug report,
with preprocessed source if appropriate.
See URL:http://www.gnu.org/software/gcc/bugs.html for instructions.
Are those options still needed? They are commented out in NOTES and
shouldn't be necessary, right?
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL
am)
clearly documented in handbook. Users who will not read the fine
documentation fully deserve the pain. Moreover, they probably will
not make a way as fine FreeBSD user in a long run.
Be sure you read the following line:
IMHO
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail
. Otherwise it's a sphagetti to manage.
The IMHO thing applies to this message also quite well.
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
. This darn
5.0-RELEASE is nearing way too fast considering the state of
-current today.
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Fri, Nov 15, 2002 at 09:55:52AM -0500, Wesley Morgan
[EMAIL PROTECTED] wrote:
On Fri, 15 Nov 2002, Vallo Kallaste wrote:
Just finished '-j2 buildworld' and it did well with kernel which had
the options enabled. Therefore I suppose that those options are
still absolutely necessary
pages, 64 entries
5b: Data TLB: 4KB and 4MB pages, 64 entries
66: 1st-level data cache: 8KB, 4-way set assoc, 64 byte line size
40: No 2nd-level cache, or if 2nd-level cache exists, no 3rd-level cache
70: Trace cache: 12K-micro-op, 4-way set assoc
39: unknown TLB/cache descriptor
--
Vallo Kallaste
that ata(pi) and sysinstall aren't
supported, but those times are over now I guess? From where I can
download ISO image and give it a try? I don't mean to use
5.0-20021031-SNAP, sysinstall has been reworked extensively in the
last days, that's it.
Thanks
--
Vallo Kallaste
[EMAIL PROTECTED
/kern_intr.c:535
#17 0xc0222e14 in fork_exit (callout=0xc0223d80 ithread_loop, arg=0x0,
frame=0x0) at ../../../kern/kern_fork.c:860
(kgdb) quit
bash-2.05b# exit
exit
Script done on Thu Oct 31 09:46:04 2002
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED
in fork_exit (callout=0xc028f010 sched_sync, arg=0x0,
frame=0x0) at ../../../kern/kern_fork.c:860
(kgdb) quit
bash-2.05b# exit
exit
Script done on Thu Oct 24 12:37:38 2002
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body
and trashed the return address.
Actually, there are some bugs in the mbchains code. I've just
committed a possible fix. Can you cvsup and try out revision
1.9 of subr_mchain.c and see if it works better? Thanks.
The crash is gone, thanks.
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe
that they changed size during copy operation and the target
files got zero size. In reality these are the most static files I
know on this NT server :)
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
=0xc13534e0, uap=0xd66ebd10)
at ../../../kern/sys_generic.c:329
---
You *must* be doing something that causes an SMBFS object to act as
backing store for an FFS.
You know better, sure, but nevertheless I'm not doing anything what
can cause it. Perhaps a bug somewhere.
--
Vallo Kallaste
suspected
Openoffice (xls file), but later found the real. For now
sharity-light gives me chanche to get work done.
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
() at {standard input}:141
---Can't read userspace from dump, or kernel process---
(kgdb) quit
bash-2.05b# exit
exit
Script done on Tue Oct 22 17:22:15 2002
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
-2.05b# exit
exit
Script done on Tue Oct 22 20:57:35 2002
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
share -ro from NT4 server, cd
/some/mountpoint and cp thisfile.xls /tmp. That's it.
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
/signal.h,v 1.19 2002/10/06 21:54:08 mike Exp $
The same error happens several times down the road of XFree86-4 port
compilation and all the problematic source files contain
#include signal.h surrounded by _POSIX_SOURCE. Removing this
_POSIX_SOURCE thing got the XFree86-4 port compile to me.
--
Vallo
]: *** [all-recursive] Error 1
gmake[1]: Leaving directory
`/usr/local/src/portbuild/usr/ports/audio/xmms/work/xmms-1.2.7'
gmake: *** [all-recursive-am] Error 2
*** Error code 2
Stop in /usr/ports/audio/xmms.
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED
/usr/ports/devel/imake-4/work/xc/config.
*** Error code 1
Stop in /usr/ports/devel/imake-4.
*** Error code 1
Stop in /usr/ports/x11/XFree86-4-libraries.
*** Error code 1
Stop in /usr/ports/x11/XFree86-4.
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED
. Vinum R5 is broken and
I've lost interest over the years of trying to make use of it. No
complaints to you, I do understand that paid work is what makes
living.
and is better suited for bare striping.
It is?
I'd be interested in details.
See above.
--
Vallo Kallaste
[EMAIL PROTECTED
asr(4) and 2400A. I had
no choice because hardware doesn't support spanning.
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
2
*** Error code 2
Stop in /usr/ports/x11/kdebase3.
*** Error code 1
Stop in /usr/ports/net/kdenetwork3.
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
my target for only some months and I have always thought of
{kde,gnome}-freebsd lists as developer oriented... but this seems
like the definitive call for joining :)
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body
On Mon, Sep 23, 2002 at 03:13:15PM -0700, Kris Kennaway [EMAIL PROTECTED] wrote:
On Mon, Sep 23, 2002 at 01:55:18PM +0300, Vallo Kallaste wrote:
This isn't a yesterdays problem, I've had this for a month or so.
The problem is explicit declaration of -march=p[234], use
CPUTYPE=i686
with -O2
and above. Are you _certain_ this is a compiler bug?
To put myself to the safe side, no. I'll do yet another run of
compilation on all of the CPUTYPE=p[234] levels and report how it
did tomorrow.
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED
had email discussion about it and
you claimed that Promise support for ATAPI DMA is almost missing,
but I guess you have better things to remember. The combo did work
well with PIO4. Sounds similar.
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED
/make.conf and you get further. The second way
is to not set CPUTYPE at all, logic in /usr/share/mk/bsd.cpu.mk will
set -mcpu to what appears to fit.
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Mon, Sep 23, 2002 at 01:00:24PM +0200, Hanspeter Roth
[EMAIL PROTECTED] wrote:
On Sep 23 at 13:48, Vallo Kallaste spoke:
Back to the 4.5-something I had problems with the Plextor CD-RW
drive, Promise ATA-66 and DMA. We had email discussion about it and
you claimed that Promise
this surprises me. Seems like nobody has read my
messages nor find the cause of this failure interesting. Yes this
caused bu machine type optimisation and everybody who's brave enough
to set CPUTYPE=p[234] will be trapped.
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL
reporting what I found. It's quite
unfair for non-developer to complain about development track, IMHO.
I'll see what I can do, but finding offending function is probably
beyond my knowledge.
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe
On Wed, Sep 18, 2002 at 09:59:29PM +0300, Vallo Kallaste vallo wrote:
In case someone is interested about consistent test case, here's
additional info. Now I built both world and kernel with CPUTYPE=p2
and kan's patch. I haven't changed anything except uncommenting the
aforementioned CPUTYPE
On Fri, Sep 13, 2002 at 03:35:32PM +0300, Vallo Kallaste vallo wrote:
As promised I did some further testing and found that either of the
problematic ports will build fine in case that:
1. both world and kernel are built without any CPU specific
optimisation beforehand (with kan's patch)
2
. Sorry for being harsh.
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
/xc.
*** Error code 1
Stop in /usr/local/src/portbuild/usr/ports/x11-servers/XFree86-4-Server/work/xc.
*** Error code 1
Stop in /usr/ports/x11-servers/XFree86-4-Server.
*** Error code 1
Stop in /usr/ports/x11/XFree86-4.
--
Vallo Kallaste
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL
1 - 100 of 215 matches
Mail list logo
