Re: Scheduler changes?
On Mon, 29 May 2000, Bruce Evans wrote:
> Scheduling was broken in -current on 2004/04/30 11:33:44 PDT. "nice -20" in
> -current does essentially the same thing as "nice -10" in 4.0 (not enough
> even in 4.0).
hmmm... so there's a few years to wait before we have to worry.. :-)
>
> Bruce
>
>
--
:{ [EMAIL PROTECTED]
Andy Farkas
System Administrator
Speednet Communications
http://www.speednet.com.au/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Internal compiler error: program ld got fatal signal 10
In message <[EMAIL PROTECTED]> "David O'Brien" writes: : On Sun, May 28, 2000 at 08:32:30PM -0600, Warner Losh wrote: : > If it works, then I think it should be committed in the usual way : > for this stuff: Filtered through David O'Brien... : : Give me a few days if you can. (if people think that is unacceptable, : please let me know) I've forwarded the patch to the Binutils : maintainers. Binutils 2.10 should be released any day now, so I'll have : to do another Buntils import anyway, so I'll get it then. I think a few days is cool. There's a known work around for the problem, and it doesn't seem to cause any problems. People that are really worried can apply the patch. Yes, it is a breakage, and it was frustrating to find out what broke, but now that we know the parameters, I'd rate it as a minor annoyance that one can read about in UPDATING (which I updated with the first workaround, don't use J). It certainly isn't worth creating headaches for you over. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Internal compiler error: program ld got fatal signal 10
On Sun, May 28, 2000 at 08:32:30PM -0600, Warner Losh wrote: > If it works, then I think it should be committed in the usual way > for this stuff: Filtered through David O'Brien... Give me a few days if you can. (if people think that is unacceptable, please let me know) I've forwarded the patch to the Binutils maintainers. Binutils 2.10 should be released any day now, so I'll have to do another Buntils import anyway, so I'll get it then. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Internal compiler error: program ld got fatal signal 10
On Mon, May 29, 2000 at 05:05:29AM +, Anatoly Vorobey wrote: > You need to apply the patch and remake /usr/src/gnu/usr.bin/binutils/libbfd > and then /usr/src/gnu/usr.bin/binutils/ld . I'll pass this onto the Binutils people. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Internal compiler error: program ld got fatal signal 10
The patch works for me! Yippie! I have my AJ back again. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Internal compiler error: program ld got fatal signal 10
Warner Losh wrote: > David, > I'm fairly certain that there are malloc related bugs in the new > binutils. If I have malloc.conf pointing at AJ, then we die in ld all > the time. If I remove that file, then we don't and things appear to > work. That's why some people succeeded in their upgrade, and why some > fail. > Bingo. I have AJ set. > P.S. One more beer to phk for putting this functionality into malloc :-) We're going to have one happy phk. Mark me down for one beer. -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Internal compiler error: program ld got fatal signal 10
In message <[EMAIL PROTECTED]> Anatoly Vorobey writes: : Can you test this patch? I think I tracked down the problem. At some : point, someone added a new field into a hash table struct and didn't : add initialization for it into the general hash table struct init func. : This patch cures the problem for me. Yes, I know, vendor branch and : all :( If it works, then I think it should be committed in the usual way for this stuff: Filtered through David O'Brien... I've just started a build and will let people know if this works. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: have a couple of problems.
:Hi, : :ok so I am having a couple of problems. : :The first is that I get tons of "sio0: x more silo overflows" messages when I :boot an SMP enabled kernel under the latest 5.0 source. Well as of friday I :re'cvs-upped. : :I can get rid of these by not booting an SMP kernel but then I get really :freaky :X stuff happening. My screen gets all wavy when there is a bunch of stuff :being sent out of the video card. Which is really annoying and causes :headaches. : :Anyone else having the X problem? I have seen mention and potential fixes for :the :silo overflow problems but it hasnt made it into the current source yet. : :thanks : :steve : :Steve Heistand :[EMAIL PROTECTED] Steve, please try the patch that Bruce posted a few days ago and tell us if that fixes your problem too. The patch will almost certainly go in in some form, it hasn't yet only because I wanted a little time to be able to trace out the interrupt path to make sure the patch was ok. -Matt Matthew Dillon <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Internal compiler error: program ld got fatal signal 10
On Sun, May 28, 2000 at 05:12:05PM -0600, Warner Losh wrote:
> I get these failures on hello world:
>
> int main() { printf("hello world\n"); }
>
> cc -c xxx.c
> cc -o xxx xxx.o
>
Can you test this patch? I think I tracked down the problem. At some
point, someone added a new field into a hash table struct and didn't
add initialization for it into the general hash table struct init func.
This patch cures the problem for me. Yes, I know, vendor branch and
all :(
You need to apply the patch and remake /usr/src/gnu/usr.bin/binutils/libbfd
and then /usr/src/gnu/usr.bin/binutils/ld .
Index: elf.c
===
RCS file: /freebsd/cvs/src/contrib/binutils/bfd/elf.c,v
retrieving revision 1.6
diff -u -r1.6 elf.c
--- elf.c 2000/05/13 16:44:19 1.6
+++ elf.c 2000/05/29 04:58:34
@@ -979,6 +979,7 @@
table->needed = NULL;
table->hgot = NULL;
table->stab_info = NULL;
+ table->dynlocal = NULL;
return _bfd_link_hash_table_init (&table->root, abfd, newfunc);
}
--
Anatoly Vorobey,
[EMAIL PROTECTED] http://pobox.com/~mellon/
"Angels can fly because they take themselves lightly" - G.K.Chesterton
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: unknown:
> IF and ONLY IF the PNPBIOS code is causing your machine to fail, do the > following: > > - Send me FULL DETAILS; this will need to include the trap messages and, >if the trap is in the kernel, a DDB traceback. > The described situation actually occured to me tonight (5-28-2000) while trying to install. Rather than check the list for a solution, I went back to the 4.0 boot disks (which worked really well) and changed them to setup a snapshot (5.0-2528-CURRENT). If you so desire (which presumably is the case), I can just boot up the current floppies and try to send you the information you request. I apologize for being currently un-helpful, but I will try to help if you still need so. Dan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ftp(1) breakage w/ passive mode?
On Sun, May 28, 2000 at 05:53:38PM -0700, Cy Schubert - ITSD Open Systems Group wrote: > According to the ftp(1) man page: > > Please note that if you are connecting to IPv6 ftp server, > the program will use EPSV/EPRT pair and LPSV/LPRT pair, in- > stead of PASV and PORT. The meaning is the same.) Ok.. I have no IPv6 network except for my localnet. The outside network is completely IPv4. > What would make ftp(1) think it has an IPv6 connection? I have no idea.. > If you have no requirement for IPv6 you may wish to create a custom > kernel w/o IPv6 options. Well, it has purely experimental purposes.. I'd rather leave it in and get ftp(1) properly fixed, since everything else works just fine. :-) -- Will Andrews <[EMAIL PROTECTED]> GCS/E/S @d- s+:+>+:- a--->+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++> DI+++ D+ G++>+++ e-> h! r-->+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Internal compiler error: program ld got fatal signal 10
On Sun, May 28, 2000 at 05:12:05PM -0600, Warner Losh wrote: > I think that this is strong evidence that there are bugs in the new > binutils that AJ is finding. I think it may be that it incorrectly > expects memory to be zero'd when it gets it or something. I've further verified that: - it's J that's causing the problem, even without A present. - the assembler generates identical .o files with or without the J option of malloc, so it's really an ld problem. I think you're right, and it expects a zeroed-out malloced memory somewhere. I'll try to hunt for it in spare time. -- Anatoly Vorobey, [EMAIL PROTECTED] http://pobox.com/~mellon/ "Angels can fly because they take themselves lightly" - G.K.Chesterton To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ftp(1) breakage w/ passive mode?
In message <[EMAIL PROTECTED]>, Will Andrews writes: > [ i'm not on -stable, but am on -current ] > > Hi all, > > I'm having trouble with ftp(1) in passive mode on 4-STABLE and 5-CURRENT: > FreeBSD 4.0-STABLE #0: Sat May 27 10:26:43 EDT 2000 > FreeBSD 5.0-CURRENT #1: Fri May 26 04:52:03 EDT 2000 > > <2 5002-0> (18:46:17) [will@radon ~]% ftp ftp://ftp.FreeBSD.org/pub/ > Connected to ftp.freesoftware.com. > [..] > 230 Guest login ok, access restrictions apply. > Remote system type is UNIX. > Using binary mode to transfer files. > 200 Type set to I. > 250 CWD command successful. > 250 CWD command successful. > ftp> ls > 500 'EPSV': command not understood. > 500 'LPSV': command not understood. > Passive mode refused. > ftp> > > However, it works on some servers: > <2 5007-0> (18:49:16) [will@radon /usr/src/usr.bin/ftp]% ftp ftp://ftp.cs.ubc > .ca/ > Connected to ftp.cs.ubc.ca. > [..] > 200 Type set to I. > 250 CWD command successful. > ftp> ls > 227 Entering Passive Mode (142,103,6,49,233,148) > 150 Opening ASCII mode data connection for /bin/ls. > total 28 > drwxrwxr-x 10 root other512 Jan 17 1996 . > drwxrwxr-x 10 root other512 Jan 17 1996 .. > lrwxrwxrwx 1 root other 7 Dec 27 1995 bin -> usr/bin > lrwxrwxrwx 1 root other 1 Dec 27 1995 cs -> . > [..] > ftp> quit > > So it seems there's something quite broken in the code. My suspect is > rev 1.25 of ftp.c and associated commits. According to the ftp(1) man page: Please note that if you are connecting to IPv6 ftp server, the program will use EPSV/EPRT pair and LPSV/LPRT pair, in- stead of PASV and PORT. The meaning is the same.) I've removed all IPv6 options from my kernel at home (to circumvent a Kerberos V through pipsecd through NAT problem) and I have no problems with ftp(1). What would make ftp(1) think it has an IPv6 connection? If you have no requirement for IPv6 you may wish to create a custom kernel w/o IPv6 options. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/DEC Team Internet: [EMAIL PROTECTED] Open Systems Group, ITSD, ISTA Province of BC To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FW: GDB 5.0 is released!
On Fri, 26 May 2000, David O'Brien wrote: > > > > GDB 5.0 is released! > > Do you have any forecasts as to when we will see this baby in the -current? > > Its priority is behind GCC 2.96 I haven't had a chance to examine this yet ... do you know if it includes support for our new hardware debug register support on IA32? -Brian -- Brian Dean [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Internal compiler error: program ld got fatal signal 10
David,
looks like I found the problem. Or at least how to trivially
recreate the problem and how to work around it for those people that
need to do so. I've cc'd current since I've been talking there with
people about it.
I'm fairly certain that there are malloc related bugs in the new
binutils. If I have malloc.conf pointing at AJ, then we die in ld all
the time. If I remove that file, then we don't and things appear to
work. That's why some people succeeded in their upgrade, and why some
fail.
I get these failures on hello world:
int main() { printf("hello world\n"); }
cc -c xxx.c
cc -o xxx xxx.o
I think that this is strong evidence that there are bugs in the new
binutils that AJ is finding. I think it may be that it incorrectly
expects memory to be zero'd when it gets it or something.
So if you have to update your system, don't have /etc/malloc.conf
pointing at AJ:
A All warnings (except for the warning about unknown flags being
set), and failure to allocate memory become fatal. The process
will call abort(3) in these cases.
J Each byte of new memory allocated by malloc(), realloc() or
reallocf() as well as all memory returned by free(), realloc() or
reallocf() will be initialized to 0xd0. This options also sets
the ``R'' option. This is intended for debugging and will impact
performance negatively.
R Causes the realloc() and reallocf() functions to always reallo-
cate memory even if the initial allocation was sufficiently
large. This can substantially aid in compacting memory.
Warner
P.S. One more beer to phk for putting this functionality into malloc :-)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ftp(1) breakage w/ passive mode?
[ i'm not on -stable, but am on -current ] Hi all, I'm having trouble with ftp(1) in passive mode on 4-STABLE and 5-CURRENT: FreeBSD 4.0-STABLE #0: Sat May 27 10:26:43 EDT 2000 FreeBSD 5.0-CURRENT #1: Fri May 26 04:52:03 EDT 2000 <2 5002-0> (18:46:17) [will@radon ~]% ftp ftp://ftp.FreeBSD.org/pub/ Connected to ftp.freesoftware.com. [..] 230 Guest login ok, access restrictions apply. Remote system type is UNIX. Using binary mode to transfer files. 200 Type set to I. 250 CWD command successful. 250 CWD command successful. ftp> ls 500 'EPSV': command not understood. 500 'LPSV': command not understood. Passive mode refused. ftp> However, it works on some servers: <2 5007-0> (18:49:16) [will@radon /usr/src/usr.bin/ftp]% ftp ftp://ftp.cs.ubc.ca/ Connected to ftp.cs.ubc.ca. [..] 200 Type set to I. 250 CWD command successful. ftp> ls 227 Entering Passive Mode (142,103,6,49,233,148) 150 Opening ASCII mode data connection for /bin/ls. total 28 drwxrwxr-x 10 root other512 Jan 17 1996 . drwxrwxr-x 10 root other512 Jan 17 1996 .. lrwxrwxrwx 1 root other 7 Dec 27 1995 bin -> usr/bin lrwxrwxrwx 1 root other 1 Dec 27 1995 cs -> . [..] ftp> quit So it seems there's something quite broken in the code. My suspect is rev 1.25 of ftp.c and associated commits. -- Will Andrews <[EMAIL PROTECTED]> GCS/E/S @d- s+:+>+:- a--->+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++> DI+++ D+ G++>+++ e-> h! r-->+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: have a couple of problems.
On Sun, May 28, 2000 at 02:30:59PM -0600, Steve Heistand wrote: > Hi, > > ok so I am having a couple of problems. > > The first is that I get tons of "sio0: x more silo overflows" messages when I > boot an SMP enabled kernel under the latest 5.0 source. Well as of friday I > re'cvs-upped. Same for me. During download of images from a digital camera using gphoto. Device: /dev/cuaa0 Speed: 115000 [...] sio0: 1 more silo overflow (total 23) sio0: 1 more silo overflow (total 24) sio0: 1 more silo overflow (total 25) sio0: 2 more silo overflows (total 27) sio0: 2 more silo overflows (total 29) sio0: 1 more silo overflow (total 30) sio0: 1 more silo overflow (total 31) sio0: 1 more silo overflow (total 32) sio0: 1 more silo overflow (total 33) sio0: 1 more silo overflow (total 34) sio0: 1 more silo overflow (total 35) sio0: 1 more silo overflow (total 36) sio0: 1 more silo overflow (total 37) sio0: 1 more silo overflow (total 38) sio0: 1 more silo overflow (total 39) sio0: 1 more silo overflow (total 40) sio0: 1 more silo overflow (total 41) sio0: 1 more silo overflow (total 42) sio0: 1 more silo overflow (total 43) sio0: 1 more silo overflow (total 44) sio0: 1 more silo overflow (total 45) sio0: 1 more silo overflow (total 46) sio0: 1 more silo overflow (total 47) sio0: 1 more silo overflow (total 48) sio0: 1 more silo overflow (total 49) sio0: 1 more silo overflow (total 50) sio0: 1 more silo overflow (total 51) sio0: 636 more interrupt-level buffer overflows (total 636) sio0: 1 more silo overflow (total 52) sio0: 1 more silo overflow (total 53) sio0: 1 more silo overflow (total 54) sio0: 1 more silo overflow (total 55) sio0: 1 more silo overflow (total 56) sio0: 1 more silo overflow (total 57) sio0: 1 more silo overflow (total 58) sio0: 66 more interrupt-level buffer overflows (total 702) sio0: 71 more interrupt-level buffer overflows (total 773) sio0: 2 more silo overflows (total 60) sio0: 1 more silo overflow (total 61) sio0: 1 more silo overflow (total 62) sio0: 1 more silo overflow (total 63) sio0: 1 more silo overflow (total 64) sio0: 1 more silo overflow (total 65) sio0: 664 more interrupt-level buffer overflows (total 1437) sio0: 1 more silo overflow (total 66) sio0: 1 more silo overflow (total 67) sio0: 2 more silo overflows (total 69) sio0: 1 more silo overflow (total 70) sio0: 1 more silo overflow (total 71) sio0: 1 more silo overflow (total 72) sio0: 1 more silo overflow (total 73) sio0: 1 more silo overflow (total 74) sio0: 1 more silo overflow (total 75) sio0: 1 more silo overflow (total 76) sio0: 1 more silo overflow (total 77) sio0: 1 more silo overflow (total 78) sio0: 1 more silo overflow (total 79) sio0: 1 more silo overflow (total 80) sio0: 1 more silo overflow (total 81) sio0: 1 more silo overflow (total 82) sio0: 1 more silo overflow (total 83) sio0: 1 more silo overflow (total 84) sio0: 1 more silo overflow (total 85) sio0: 1 more silo overflow (total 86) sio0: 1 more silo overflow (total 87) sio0: 1 more silo overflow (total 88) sio0: 1 more silo overflow (total 89) sio0: 1 more silo overflow (total 90) sio0: 1 more silo overflow (total 91) sio0: 2 more silo overflows (total 93) sio0: 1 more silo overflow (total 94) sio0: 2 more silo overflows (total 96) sio0: 2 more silo overflows (total 98) sio0: 2 more silo overflows (total 100) sio0: 1 more silo overflow (total 101) sio0: 1 more silo overflow (total 102) sio0: 2 more silo overflows (total 104) sio0: 1 more silo overflow (total 105) sio0: 2 more silo overflows (total 107) sio0: 1 more silo overflow (total 108) sio0: 1 more silo overflow (total 109) sio0: 1 more silo overflow (total 110) sio0: 1 more silo overflow (total 111) sio0: 1 more silo overflow (total 112) sio0: 1 more silo overflow (total 113) sio0: 1 more silo overflow (total 114) sio0: 2 more silo overflows (total 116) sio0: 1 more silo overflow (total 117) sio0: 1 more silo overflow (total 118) sio0: 1 more silo overflow (total 119) sio0: 1 more silo overflow (total 120) sio0: 1 more silo overflow (total 121) sio0: 1 more silo overflow (total 122) sio0: 2 more silo overflows (total 124) sio0: 2 more silo overflows (total 126) sio0: 1 more silo overflow (total 127) sio0: 1 more silo overflow (total 128) sio0: 1 more silo overflow (total 129) sio0: 1 more silo overflow (total 130) sio0: 1 more silo overflow (total 131) sio0: 1 more silo overflow (total 132) sio0: 1 more silo overflow (total 133) sio0: 1 more silo overflow (total 134) sio0: 1 more silo overflow (total 135) sio0: 1 more silo overflow (total 136) sio0: 1 more silo overflow (total 137) sio0: 2 more silo overflows (total 139) sio0: 1 more silo overflow (total 140) sio0: 1 more silo overflow (total 141) sio0: 1 more silo overflow (total 142) sio0: 1 more silo overflow (total 143) sio0: 1 more silo overflow (total 144) sio0: 1 more silo overflow (total 145) sio0: 1 more silo overflow (total 146) sio0: 1 more silo overflow (total 147) sio0: 1 more silo overflow (total 148) sio0: 1 more silo overflow (total
Re: Internal compiler error: program ld got fatal signal 10
Did install of new binutils. now ld dumps core ALL the time. Further testing impossible. DO NOT TRY TO UPGRADE JUST BINUTILS IF YOU ARE GETTING THE SIGNAL 10 ERROR. YOU WON'T BE ABLE TO BUILD ANYTHING ELSE ON THE SYSTEM. Now, I'm grumpy... Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Unknown Devices in Dmesg
In message <[EMAIL PROTECTED]> "Thomas D. Dean" writes: : and have devices listed as 'unknown' in dmesg. Everything appears to : function OK. They are ok. : The serial ports, sio0 and sio1 appear both as sio and unknown. Yes. This is expected. The PnP BIOS code which should execute before all the other devices are probed actually executes after, so you get things like that. It is safe to ignore for now. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Internal compiler error: program ld got fatal signal 10
In message <[EMAIL PROTECTED]> Warner Losh writes: : OK. I'm trying on my bouncer box now. It is over NFS so it is slow. : Also it is a PPro 180, so that is slow too :-(. : : FreeBSD billy-club.village.org 5.0-CURRENT FreeBSD 5.0-CURRENT #33: : Sun Apr 30 22:57:58 MDT 2000 : [EMAIL PROTECTED]:/home/imp/FreeBSD/src/sys/compile/BILLY-CLUB : i386 : : I'll let people know how this works out. Got the same exact results with the PPro 180 as I did on my PIII 500. Definitely not hardware at this point. I think I'm safe in saying that. I'm going to try to upgrade my binutils by hand and see if that helps any. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
have a couple of problems.
Hi, ok so I am having a couple of problems. The first is that I get tons of "sio0: x more silo overflows" messages when I boot an SMP enabled kernel under the latest 5.0 source. Well as of friday I re'cvs-upped. I can get rid of these by not booting an SMP kernel but then I get really freaky X stuff happening. My screen gets all wavy when there is a bunch of stuff being sent out of the video card. Which is really annoying and causes headaches. Anyone else having the X problem? I have seen mention and potential fixes for the silo overflow problems but it hasnt made it into the current source yet. thanks steve Steve Heistand [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Dual-booting: FreeBSD, NetBSD and OpenBSD
At 10:34 AM -0600 5/28/00, Warner Losh wrote: >I need to setup a machine that will boot FreeBSD, NetBSD and >OpenBSD. Assume I have an insane amount of disk space. What's >the best way to accomplish this? Last time I tried it, the >partition ID numbers were all the same, making this difficult >if not impossible. FreeBSD and OpenBSD work fine (I've set it up, no problem). I haven't tried NetBSD yet, as my available disk space is not yet at the "insane" level (but I hope to be at that level within a week or two). If there is a conflict with NetBSD, you could use a boot manager to solve the problem. I have used PowerBoot from http://www.blueskyinnovations.com/pboot.html (about $30, IIRC), but I'm sure there are plenty of other options. You can have the boot-manager change the partition ID for one set of partitions when booting from some other partition, effectively hiding the partition. Once I do hit insane disk-levels, I'm more inclined to try for a vmware solution, as that means I can have multiple OS's active simultaneously. This would not be adequate for low- level (eg: drivers) or SMP development, but it should work fine for many of the things I do. --- Garance Alistair Drosehn = [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Institute To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Internal compiler error: program ld got fatal signal 10
In message <[EMAIL PROTECTED]> "Thomas D. Dean" writes: : make world : reboot : rebuild+install kernel : reboot OK. I'm trying on my bouncer box now. It is over NFS so it is slow. Also it is a PPro 180, so that is slow too :-(. FreeBSD billy-club.village.org 5.0-CURRENT FreeBSD 5.0-CURRENT #33: Sun Apr 30 22:57:58 MDT 2000 [EMAIL PROTECTED]:/home/imp/FreeBSD/src/sys/compile/BILLY-CLUB i386 I'll let people know how this works out. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Internal compiler error: program ld got fatal signal 10
Sorry for two replies: I did: make world reboot rebuild+install kernel reboot tomdean To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Internal compiler error: program ld got fatal signal 10
Before upgrade: FreeBSD celebris 5.0-CURRENT FreeBSD 5.0-CURRENT #0: \ Tue Apr 4 11:47:34 PDT 2000 \ [EMAIL PROTECTED]:/usr/src/sys/compile/CELEBRIS-SMP i386 After upgrade: FreeBSD celebris 5.0-CURRENT FreeBSD 5.0-CURRENT #1: \ Sun May 28 11:07:09 PDT 2000 \ root@celebris:/usr/src/sys/compile/CELEBRIS-SMP i386 tomdean To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Internal compiler error: program ld got fatal signal 10
In message <[EMAIL PROTECTED]> John Baldwin writes: : I built a new world fine with the new binutils right after all my commits : in /sys/boot. Also, I built world again with today's sources: OK. I have the old binutils installed on my system. : -- : build started at 10:20:27 on 05/28/00 : build finished at 14:39:14 on 05/28/00 : -- : > ld -v : GNU ld version 2.10-anoncvs-2512 (with BFD 2.10-anoncvs-2512) : > as -v : GNU assembler version 2.10-anoncvs-2512 (i386-unknown-freebsdelf5.0) using BFD :version : 2.10-anoncvs-2512 : : In all my tests, I used a normal make buildworld, I never manually : built or installed binutils. Odd. that means that you must have done at least one buildworld with the old binutils. Hmmm. Time to play with the bouncer box to see what I can do with it. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Internal compiler error: program ld got fatal signal 10
On 28-May-00 Warner Losh wrote: > In message <[EMAIL PROTECTED]> "Thomas D. Dean" writes: >: I just completed a 'make world' on a -current cvsup'ed yesterday and saw >: no errors. > > When was the previous time that you did this? And did you update the > binutils first? It sure would be a MAJOR BUMMER if one needed to > update binutils first... I built a new world fine with the new binutils right after all my commits in /sys/boot. Also, I built world again with today's sources: -- build started at 10:20:27 on 05/28/00 build finished at 14:39:14 on 05/28/00 -- > ld -v GNU ld version 2.10-anoncvs-2512 (with BFD 2.10-anoncvs-2512) > as -v GNU assembler version 2.10-anoncvs-2512 (i386-unknown-freebsdelf5.0) using BFD version 2.10-anoncvs-2512 In all my tests, I used a normal make buildworld, I never manually built or installed binutils. > Warner -- John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Internal compiler error: program ld got fatal signal 10
On Sun, May 28, 2000 at 01:10:20PM -0600, Warner Losh wrote: > In message <[EMAIL PROTECTED]> "Thomas D. Dean" writes: > : I just completed a 'make world' on a -current cvsup'ed yesterday and saw > : no errors. > > When was the previous time that you did this? And did you update the > binutils first? It sure would be a MAJOR BUMMER if one needed to > update binutils first... > > Warner I have been updating this box by 'make worlds' in 1-2 day intervals recently (for example I did it yesterday but not today) and it worked every time apart from the queue macro bustages, which were easy to fix though. Will try again tomorrow. (esp because I had one report that the SB 64 AWE doesn't work on a kernel from today. I need to verify this.) I got the binutils on the day they were added to the tree but 'make world' was as easy as ever on that day too. (Although I was foolish enough to try to compile a kernel before making an installworld... but it was my fault, I never do this normally I was just not paying attention. It bombed as expected:-) But then I made installworld and everything was fine afterwards.) Just a datapoint...(PII 233 UP here, LX 440 mobo, 64M RAM) -- Regards: Szilveszter ADAM Szeged University Szeged Hungary To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Internal compiler error: program ld got fatal signal 10
In message <[EMAIL PROTECTED]> Steve Kargl writes: : I've got 500MB of swap. It is never touched during : the build. The machine is very lightly loaded (i.e., : only "make buildworld" running). Ditto. I just tried it with root and all the limits set to unlimited. I had the same problem. : I was surprise that no one else had reported this problem : when I sent my original e-mail. It must be restricted to : a specific hardware combination. Must be something specific to our environments. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Internal compiler error: program ld got fatal signal 10
Warner Losh wrote: > In message <[EMAIL PROTECTED]> Marcel Moolenaar writes: > : The ability to do cross builds rules out the need to update binutils > : first. I haven't done any cross-builds since, well, februari, so I'm not > : at all up to date on that front; things may have been broken by then... > > I did a complete buildworld in early May w/o a hitch that worked when > I installed it on my bouncer box. > > Maybe I just need more swap than I have on my machine, or higher > limits for the process building things. Then again, I do have 1/2G of > swap that isn't being used at all during the builds... > Warner, I've got 500MB of swap. It is never touched during the build. The machine is very lightly loaded (i.e., only "make buildworld" running). I was surprise that no one else had reported this problem when I sent my original e-mail. It must be restricted to a specific hardware combination. -- Steve Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Fri May 26 09:39:34 PDT 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/TROUTMASK Timecounter "i8254" frequency 1193182 Hz CPU: Pentium Pro (199.31-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping = 9 Features=0xfbff real memory = 268435456 (262144K bytes) avail memory = 257748992 (251708K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 Preloaded elf kernel "kernel" at 0xc0346000. VESA: v1.2, 4096k memory, flags:0x0, mode table:0xc00c1bdf (c0001bdf) VESA: S3 Incorporated. 86C325 Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 isab0: at device 7.0 on pci0 isa0: on isab0 pci0: at 7.1 pci0: at 15.0 irq 19 ahc0: port 0xf400-0xf4ff mem 0xf0dff000-0xf0df irq 18 at device 16.0 on pci0 ahc0: aic7880 Single Channel A, SCSI Id=7, 16/255 SCBs xl0: <3Com 3c905-TX Fast Etherlink XL> port 0xf0c0-0xf0ff irq 17 at device 17.0 on pci0 xl0: Ethernet address: 00:60:97:98:38:65 miibus0: on xl0 nsphy0: on miibus0 nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto 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 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: on isa0 sc0: VGA <8 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: This ppc chipset does not support the extended I/O port range...no problem ppc0: at port 0x378-0x37b irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode pps0: on ppbus0 ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port unknown0: at port 0xcf8-0xcff on isa0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown1: at port 0x80,0x10-0x1f,0x22-0x2f,0x30-0x3f,0x50-0x5f,0x90-0x9f,0xa2-0xaf,0xb0-0xbf,0xe0-0xef iomem 0xfff8-0x on isa0 unknown2: at iomem 0-0x9,0xe-0xf,0x10-0xfff on isa0 unknown3: at port 0-0xf,0x81-0x8f,0xc0-0xdf drq 4 on isa0 unknown4: at port 0x20-0x21,0xa0-0xa1 irq 2 on isa0 unknown5: at port 0x40-0x43 irq 0 on isa0 unknown6: at port 0x70-0x71 irq 8 on isa0 unknown: can't assign resources npxisa0: at port 0xf0-0xff irq 13 on isa0 unknown7: at port 0x61 on isa0 unknown: can't assign resources unknown8: at port 0x4d0-0x4d1 on isa0 unknown9: at iomem 0xfec0-0xfec0,0xfee0-0xfee00fff on isa0 unknown10: at port 0x620-0x623 on isa0 sbc0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 sbc0: setting card to irq 5, drq 1, 5 pcm0: on sbc0 unknown11: at port 0x200-0x207 on isa0 APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 Waiting 10 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! sa0 at ahc0 bus 0 target 1 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 5.000MB/s transfers (5.000MHz, offset 15) cd0 at ahc0 bus 0 target 6 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 15) cd0: cd present [312700 x 2048 byte records] da1 at ahc0 bus 0 target 3 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 5.000MB/s transfers (5.000MHz, offset 8) da1: 699MB (1431760 512 byte sectors: 64H 32S/T 699C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled d
Re: Internal compiler error: program ld got fatal signal 10
In message <[EMAIL PROTECTED]> Marcel Moolenaar writes: : The ability to do cross builds rules out the need to update binutils : first. I haven't done any cross-builds since, well, februari, so I'm not : at all up to date on that front; things may have been broken by then... I did a complete buildworld in early May w/o a hitch that worked when I installed it on my bouncer box. Maybe I just need more swap than I have on my machine, or higher limits for the process building things. Then again, I do have 1/2G of swap that isn't being used at all during the builds... Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Internal compiler error: program ld got fatal signal 10
Warner Losh wrote: > > In message <[EMAIL PROTECTED]> "Thomas D. Dean" writes: > : I just completed a 'make world' on a -current cvsup'ed yesterday and saw > : no errors. > > When was the previous time that you did this? And did you update the > binutils first? It sure would be a MAJOR BUMMER if one needed to > update binutils first... The ability to do cross builds rules out the need to update binutils first. I haven't done any cross-builds since, well, februari, so I'm not at all up to date on that front; things may have been broken by then... -- Marcel Moolenaar mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] tel: (408) 447-4222 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Internal compiler error: program ld got fatal signal 10
In message <[EMAIL PROTECTED]> "Thomas D. Dean" writes: : I just completed a 'make world' on a -current cvsup'ed yesterday and saw : no errors. When was the previous time that you did this? And did you update the binutils first? It sure would be a MAJOR BUMMER if one needed to update binutils first... Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Internal compiler error: program ld got fatal signal 10
I just completed a 'make world' on a -current cvsup'ed yesterday and saw no errors. tomdean To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Unknown Devices in Dmesg
I cvsup'ed, make world, rebuild+install kernel, reboot, without problem. Good work. I upgraded from Apr 4 -current to May 28 -current and have devices listed as 'unknown' in dmesg. Everything appears to function OK. The serial ports, sio0 and sio1 appear both as sio and unknown. tomdean === dmesg Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #1: Sun May 28 11:07:09 PDT 2000 tomdean@celebris:/usr/src/sys/compile/CELEBRIS-SMP Timecounter "i8254" frequency 1193182 Hz CPU: Pentium/P54C (109.34-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping = 5 Features=0x3bf real memory = 100663296 (98304K bytes) avail memory = 94887936 (92664K bytes) Programming 16 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00030010, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00030010, at 0xfee0 io0 (APIC): apic id: 2, version: 0x000f0011, at 0xfec0 Preloaded elf kernel "kernel" at 0xc02f2000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc02f209c. Intel Pentium detected, installing workaround for F00F bug npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 ncr0: port 0xec00-0xecff mem 0xfedfbf00-0xfedfbfff irq 11 at device 1.0 on pci0 isab0: at device 2.0 on pci0 isa0: on isab0 pci0: at 6.0 irq 9 de0: port 0xe880-0xe8ff mem 0xfedfbe80-0xfedfbeff irq 10 at device 8.0 on pci0 de0: DEC DE450-CA 21041 [10Mb/s] pass 1.1 de0: address 00:00:f8:02:76:db 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 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: This ppc chipset does not support the extended I/O port range...no problem ppc0: at port 0x378-0x37b irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode lpt0: on ppbus0 lpt0: Interrupt-driven port unknown0: at port 0x4d0-0x4d1,0xcf8,0xcfa on isa0 unknown1: at port 0x26,0x26e-0x26f on isa0 unknown2: at port 0x61 on isa0 unknown3: at iomem 0-0x9,0xe-0xf,0xfec0-0xfec3,0xfee0-0xfee3 on isa0 unknown: can't assign resources npxisa0: at port 0xf0-0xff irq 13 on isa0 unknown: can't assign resources unknown: <16550 compatible COM device> can't assign resources unknown: <16550 compatible COM device> can't assign resources unknown: can't assign resources unknown4: at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0 unknown: can't assign resources unknown5: at port 0-0xf,0x81-0x8f,0xc0-0xdf drq 4 on isa0 unknown6: at port 0x20-0x21,0xa0-0xa1 irq 2 on isa0 unknown7: at port 0x40-0x43 irq 0 on isa0 unknown8: at port 0x70-0x71 irq 8 on isa0 APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 Waiting 10 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! cd0 at ncr0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 4.237MB/s transfers (4.237MHz, offset 8) cd0: cd present [295811 x 2048 byte records] da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 8) da0: 1042MB (2134305 512 byte sectors: 255H 63S/T 132C) da2 at ncr0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da2: 1029MB (2109376 512 byte sectors: 255H 63S/T 131C) Mounting root from ufs:/dev/da1s1a da1 at ncr0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da1: 8748MB (17916240 512 byte sectors: 255H 63S/T 1115C) de0: enabling BNC port To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Internal compiler error: program ld got fatal signal 10
Here's the full list. I think something very bad is going on here. Here's the list from my last build: i386/usr/lib/libc.so: file not recognized: File truncated i386/usr/lib/libcalendar.so: file not recognized: File truncated i386/usr/lib/libcrypt.so: file not recognized: File truncated i386/usr/lib/libcrypto.so: file not recognized: File truncated i386/usr/lib/libcurses.so: file not recognized: File truncated i386/usr/lib/libftpio.so: file not recognized: File truncated i386/usr/lib/libgnuregex.so: file not recognized: File truncated i386/usr/lib/libipsec.so: file not recognized: File truncated i386/usr/lib/libipx.so: file not recognized: File truncated i386/usr/lib/libkvm.so: file not recognized: File truncated i386/usr/lib/libm.so: file not recognized: File truncated i386/usr/lib/libmd.so: file not recognized: File truncated i386/usr/lib/libmp.so: file not recognized: File truncated i386/usr/lib/libncp.so: file not recognized: File truncated i386/usr/lib/libncurses.so: file not recognized: File truncated i386/usr/lib/libnetgraph.so: file not recognized: File truncated i386/usr/lib/libpam.so: file not recognized: File truncated i386/usr/lib/libpcap.so: file not recognized: File truncated i386/usr/lib/librpcsvc.so: file not recognized: File truncated i386/usr/lib/libssl.so: file not recognized: File truncated i386/usr/lib/libtermcap.so: file not recognized: File truncated i386/usr/lib/libutil.so: file not recognized: File truncated i386/usr/lib/libwrap.so: file not recognized: File truncated i386/usr/lib/libz.so: file not recognized: File truncated lib/libcom_err/libcom_err.so: file not recognized: File truncated secure/lib/libcrypto/libcrypto.so: file not recognized: File truncated secure/lib/libcipher/libcipher.so: file not recognized: File truncated Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Internal compiler error: program ld got fatal signal 10
In message <[EMAIL PROTECTED]> Martin Cracauer writes: : I know that it is supposed to do so, I suspect that might not be the : case here. I don't think so. It is already using the new ld when it coredumps. I don't think that having it on the system would change things much. BTW, if I do a make buildworld -k -DNOCLEAN, I get lots of files that are truncated due to this: /usr/obj/home/imp/FreeBSD/src/i386/usr/lib/libcrypto.so: file not recognized: File truncated /usr/obj/home/imp/FreeBSD/src/i386/usr/lib/libssl.so: file not recognized: File truncated /usr/obj/home/imp/FreeBSD/src/i386/usr/lib/libtermcap.so: file not recognized: File truncated etc. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Internal compiler error: program ld got fatal signal 10
Warner Losh wrote: > In message <[EMAIL PROTECTED]> Bob Martin writes: > : If you are using an older K6 with more than 32mb of ram, this will > : happen from time to time of it's own accord. I have never taken the time > : to find out why, but if you search the archives, you will find that it > : happens quite a bit. > > I'm using a PIII-500 and it is happening to me. This system would > always build world great, but now fails all the time (20 builds) at > exactly the same spot. I don't think this is hardware. > It definitely isn't hardware. This, I believe, is a result of the new binutils. I've narrowed the window to *default date=2000.05.22.00.00.00 <-- build completes. *default date=2000.05.22.12.00.00 <-- ld gets a signal 10. -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Dual-booting: FreeBSD, NetBSD and OpenBSD
On Mon, May 29, 2000 at 01:52:24 +0900, [EMAIL PROTECTED] wrote: > > >I need to setup a machine that will boot FreeBSD, NetBSD and OpenBSD. > >Assume I have an insane amount of disk space. What's the best way to > >accomplish this? Last time I tried it, the partition ID numbers were > >all the same, making this difficult if not impossible. > > just a starter: NetBSD 1.4 and recent use different FDISK partition > ID, so it is easy to share FreeBSD and NetBSD on a same disk using > separate FDISK partition. > OpenBSD uses 0xa6 and NetBSD 0xa9. With OpenBSD I had no problems, but the NetBSD-disklabel is also interpreted by FreeBSD resulting in some boot-messages: May 28 17:52:10 diehard /kernel: da1s1: rejecting partition in BSD label: it isn 't entirely within the slice May 28 17:52:10 diehard /kernel: da1s1: start 63, end 12048749, size 12048687 May 28 17:52:10 diehard /kernel: da1s1d: start 0, end 35843669, size 35843670 This is due to the "d" slice of NetBSD, which contains the entire disk (not only the entire NetBSD partiton which is - like in FreeBSD the "c" slice). Anyway: apart from this I have a working multi-boot-system (FreeBSD-stable, FreeBSD-current, OpenBSD, NetBSD, Linux, W*s) on multiple disks. Regards -- Udo Schweigert, Siemens AG | Voice : +49 89 636 42170 ZT IK 3, Siemens CERT| Fax: +49 89 636 41166 D-81730 Muenchen / Germany | email : [EMAIL PROTECTED] PGP-2/5 fingerprint | D8 A5 DF 34 EC 87 E8 C6 E2 26 C4 D0 EE 80 36 B2 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Internal compiler error: program ld got fatal signal 10
In <[EMAIL PROTECTED]>, Warner Losh wrote: > In message <[EMAIL PROTECTED]> Martin Cracauer writes: > : Have you tried building and installing the new binutils before > : compiling the rest of the world? > > This shouldn't be required for buildworld. If it is, then it is a bug > in the buildworld process. Buildworld makes all the stuff it needs to > build things, unlike the kernel. I know that it is supposed to do so, I suspect that might not be the case here. Martin -- % Martin Cracauer <[EMAIL PROTECTED]> http://www.cons.org/cracauer/ BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Dual-booting: FreeBSD, NetBSD and OpenBSD
>I need to setup a machine that will boot FreeBSD, NetBSD and OpenBSD. >Assume I have an insane amount of disk space. What's the best way to >accomplish this? Last time I tried it, the partition ID numbers were >all the same, making this difficult if not impossible. just a starter: NetBSD 1.4 and recent use different FDISK partition ID, so it is easy to share FreeBSD and NetBSD on a same disk using separate FDISK partition. itojun To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Dual-booting: FreeBSD, NetBSD and OpenBSD
I need to setup a machine that will boot FreeBSD, NetBSD and OpenBSD. Assume I have an insane amount of disk space. What's the best way to accomplish this? Last time I tried it, the partition ID numbers were all the same, making this difficult if not impossible. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Internal compiler error: program ld got fatal signal 10
In message <[EMAIL PROTECTED]> Martin Cracauer writes: : Have you tried building and installing the new binutils before : compiling the rest of the world? This shouldn't be required for buildworld. If it is, then it is a bug in the buildworld process. Buildworld makes all the stuff it needs to build things, unlike the kernel. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP - minor API change in -current's old ISA drivers.
In message <[EMAIL PROTECTED]> Peter Wemm writes: : I've made old-style ISA drivers self identifying and got rid of the dreaded : isa_compat.h table. As a consequence, the 'struct isa_driver' stuff has : changed slightly to store the additional data that was in the compat tables : and a new line is required (COMPAT_ISA_DRIVER()) so the driver registers : itself with the device subsystem. This works essentially the same way as : the COMPAT_PCI_DRIVER() stuff works. : : There shouldn't be any noticable changes except for the slight tweaks : to the individual drivers. Now that the drivers are self contained (not self identifying, right?), I guess that means that I need to finish the hints driver so that one can set hints for drivers one kld's. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Internal compiler error: program ld got fatal signal 10
In message <[EMAIL PROTECTED]> Bob Martin writes: : If you are using an older K6 with more than 32mb of ram, this will : happen from time to time of it's own accord. I have never taken the time : to find out why, but if you search the archives, you will find that it : happens quite a bit. I'm using a PIII-500 and it is happening to me. This system would always build world great, but now fails all the time (20 builds) at exactly the same spot. I don't think this is hardware. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Internal compiler error: program ld got fatal signal 10
In message <[EMAIL PROTECTED]> Steve Kargl writes: : cc: Internal compiler error: program ld got fatal signal 10 : : *default date=2000.05.23.00.00.00 : : as specified in my cvsup supfile. The system builds fine : for all earlier dates that I've tried. I have used the : following three CFLAGS as set in /etc/make.conf : : CFLAGS= : CFLAGS=-O -pipe : CFLAGS=-O2 -pipe : : and the above error occurs. : : Any and all suggestions are welcomed, but it appears to be : a problem with the new binutils. I've seen this as well, and have reported it to the binutils maintainer. I've done the above, plus get rid of -pipe, raise my resource limits to insanely high levels, try it on a fresh tree w/o any of my local hacks, etc. This is building from a 4.0-stable system. I do this because my -stable system is my fileserver/build server and is 3x faster than my bouncer boxes are at building -current and 2x faster than my laptop. It needs to be -stable since it is expected to have long uptimes and I don't want to upgrade all the time. I also need -stable for SO work. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Internal compiler error: program ld got fatal signal 10
In <[EMAIL PROTECTED]>, Steve Kargl wrote: > First, the error message: > > cc -fpic -DPIC -I/usr/src/lib/libmd -DSHA1_ASM -DELF -DRMD160_ASM -DELF >-I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libmd/i386/rmd160.S -o rmd160.So > building shared library libmd.so.2 > cc: Internal compiler error: program ld got fatal signal 10 > *** Error code 1 > > Stop in /usr/src/lib/libmd. > *** Error code 1 > > > Now, the details. I started on Monday trying to update > a 15 March 00 -current to current -current. I get the > above error message with a source tree after > > *default date=2000.05.23.00.00.00 Have you tried building and installing the new binutils before compiling the rest of the world? Some assembler files are not compatible with the old binutils. Martin -- % Martin Cracauer <[EMAIL PROTECTED]> http://www.cons.org/cracauer/ BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SB AWE64 not recognised anymore
On Sun, May 28, 2000 at 04:34:57PM +0200, Jose M. Alcaide wrote: > Ollivier Robert wrote: > > > > I just upgraded my home machine from 4.0-R to 5.0-CURRENT and have found > > something odd. I have an ISA PnP SB AWE64 in the machine and it is not seen by > > the system at all. > > > > -CURRENT kernel built last Thursday recognizes my AWE64 PnP: Cool:-) Mine is from yesterday: FreeBSD fonix.hos.u-szeged.hu 5.0-CURRENT FreeBSD 5.0-CURRENT #2: Sat May 27 22: 38:40 CEST 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/FONIX i386 and works. I am now checking the commit logs to see what might have happened because last week's stuff just arrived into the archive section at www.freebsd.org. -- Regards: Szilveszter ADAM Szeged University Szeged Hungary To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
HEADS UP - minor API change in -current's old ISA drivers.
I've made old-style ISA drivers self identifying and got rid of the dreaded isa_compat.h table. As a consequence, the 'struct isa_driver' stuff has changed slightly to store the additional data that was in the compat tables and a new line is required (COMPAT_ISA_DRIVER()) so the driver registers itself with the device subsystem. This works essentially the same way as the COMPAT_PCI_DRIVER() stuff works. There shouldn't be any noticable changes except for the slight tweaks to the individual drivers. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SB AWE64 not recognised anymore
Ollivier Robert wrote: > > I just upgraded my home machine from 4.0-R to 5.0-CURRENT and have found > something odd. I have an ISA PnP SB AWE64 in the machine and it is not seen by > the system at all. > -CURRENT kernel built last Thursday recognizes my AWE64 PnP: $ uname -a FreeBSD defiant.we.lc.ehu.es 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Thu May 25 11:43:13 CEST 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/DEFIANT i386 $ /sbin/dmesg | fgrep sbc sbc0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 sbc0: setting card to irq 5, drq 1, 5 pcm0: on sbc0 -- JMA --- José Mª Alcaide | mailto:[EMAIL PROTECTED] Universidad del País Vasco | mailto:[EMAIL PROTECTED] Dpto. de Electricidad y Electrónica | http://www.we.lc.ehu.es/~jose Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-946013071 --- "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Scheduler changes?
On Sun, 28 May 2000, Jacob A. Hart wrote: > I remember the scheduler bug you're talking about. My system feels much > the same as it did during 4.0-CURRENT when that bug was active. I had a Scheduling was broken in -current on 2004/04/30 11:33:44 PDT. "nice -20" in -current does essentially the same thing as "nice -10" in 4.0 (not enough even in 4.0). Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SB AWE64 not recognised anymore
On Sun, May 28, 2000 at 10:12:57AM +0200, Ollivier Robert wrote: > > What does 'cat /dev/sndstat' say on your system? > > Device non configured of course :-( Hmmm I think I'll have to give up on this one... apart from "it should work" I cannot think of any more insight just now. Maybe testing if the card works in another machine/config/OS? -- Regards: Szilveszter ADAM Szeged University Szeged Hungary To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SB AWE64 not recognised anymore
According to Szilveszter Adam: > The only remaining issue this far has been that when the Linux RealPlayer > starts playing a clip, it will always start-stop-start in the beginning and Last time I started the RealPlayer7, it went fine but I'll have to test it again as soon as I get my card back. > So you are using pcm then... Well I only have > > device pcm > device sbc Same. I have been using that even in 4.0 for a long time. > in my kernel config and no PNPBIOS option. (PnP OS set to "no" in the BIOS) Same. > Despite this, yesterday's kernel prints all sorts of "unknownX > " lines which I only saw this far with people who had "options PNPBIOS" in > their kernels. But it doesn't bother me much... I know that the SB 64 PnP PNPBIOS is now a standard option :) > (I have no other PnP devices so I am easy here.) Same. > The lines that matter come after that:-) Mine used to generate the same lines. > What does 'cat /dev/sndstat' say on your system? Device non configured of course :-( -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED] FreeBSD keltia.freenix.fr 5.0-CURRENT #79: Sun May 28 01:27:10 CEST 2000 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
