Re: 5.2.1-RC1 and RC2
On Monday 16 February 2004 3:16 am, Kent Stewart wrote: On Sunday 15 February 2004 07:04 pm, Chris wrote: On Sunday 15 February 2004 09:00 pm, Thomas T. Veldhouse wrote: Chris wrote: Is is me? Or has something changed in 5.2 that tends to make systems freeze up during portupgrade? Mainly - KDE-3.2.0 That being said, I seem to be seeing this more often on other upgrades. Strange thing is, I considered it to be my PC however, I never seem to run into the total freeze when doing a buildworld. No trouble here upgrading 5.2 to current on my desktop and no trouble upgrading my 5.2p1 to 5.2RC2 on my server. I suspect your problem is hardware or driver related. Tom Veldhouse Tom, My upgrades (5.2.1 - 5.2.1-RC1 - 5.2.1-RC2) went flawless. The issues I'm having is during portupgrade. Kent, Interesting - I did as you advised. I am typically running between 113 and 125 degrees (F) My AMD did come with a fan. Perchance I ought to look into alternative cooling? Mine ran like that for 53 weeks. The warranty was for 52. When it died, it litterally blew one of the voltage regulator ICs on the motherboard. All I saw was a flash of light at the same time as a loud bang and the top right corner of the IC disappeared. Out was towards me but I didn't feel it hit nor could I find it. Much as I love AMD, I would have to agree about the fans. I bought boxed CPUs with fans as I expected that this would provide the right level of cooling (and reliability). IIRC the warranty was 2 years. When the first one went wobbly I replaced the lot. It's just not worth taking the chance. To the OP, re temperatures. I wouldn't rely too much on what other peoples systems report. The actual temperature of the CPU is going to depend on the speed and CPU core architecture (and maybe the BIOS) vs the ambient temp/cooling. This is as opposed to the temperature reported. The accuracy is going vary with method (chip) which means, which M/B. I somehow doubt the sensors are individually calibrated against a lab standard. If you can find somone with the same CPU/Motherboard, those numbers would be slightly more useful. As a counter example my 2100+/Gigabyte GA-VTXE+ (BIOS F6a) sits at 54C idle and around 60C when busy. It's perfectly stable (on stable, not current). [With fvcool idle temp = 30C] If I forget to clean the filters, the temperature will rise, and the system becomes increasingly unstable. A few degrees increase is enough. My advice is to clean any filters, fans and heatsinks and check the fans spin correctly. If the box runs cooler, note the temperature for future reference. The current fans look like the Antec fans you can see in a Circuit City or Best Buy. You can mail order them but I think I would buy one sooner than that :). You have been having problems for quite a while now and that may be what is going on. Kent -- ian j hart http://ars.userfriendly.org/cartoons/?id=20031016 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: diskless swap filename
Re: http://docs.freebsd.org/cgi/mid.cgi?200311291436.37674.ianjhart
On Saturday 29 November 2003 2:36 pm, ian j hart wrote:
Does anyone have a patch to use the mac address instead of the ip
address for the swapfile name?
Feeling lazy this week :)
Cheers
No takers then :(
For the archive, here's a patch. It's probably bogus and it certainly breaks style,
but it seems to work okay.
--- sys/nfs/bootp_subr.c.orig Thu Dec 11 00:06:28 2003
+++ sys/nfs/bootp_subr.cThu Dec 11 00:14:10 2003
@@ -57,6 +57,7 @@
#include sys/sysctl.h
#include sys/uio.h
+#include net/ethernet.h
#include net/if.h
#include net/route.h
@@ -1845,9 +1846,31 @@
gctx-lookup_path,
nd-swap_fh, nd-swap_fhsize,
nd-swap_args, procp);
- if (error != 0)
- panic(nfs_boot: lookup swap, error=%d,
- error);
+ if (error != 0) {
+ if (gctx-interfaces-sdl-sdl_type == IFT_ETHER
+ gctx-interfaces-sdl-sdl_alen == ETHER_ADDR_LEN)
{
+ snprintf(gctx-lookup_path,
+ sizeof(gctx-lookup_path),
+ swap.%02x:%02x:%02x:%02x:%02x:%02x,
+ ((struct ether_addr
*)LLADDR(gctx-interfaces-sdl))-octet[0],
+ ((struct ether_addr
*)LLADDR(gctx-interfaces-sdl))-octet[1],
+ ((struct ether_addr
*)LLADDR(gctx-interfaces-sdl))-octet[2],
+ ((struct ether_addr
*)LLADDR(gctx-interfaces-sdl))-octet[3],
+ ((struct ether_addr
*)LLADDR(gctx-interfaces-sdl))-octet[4],
+ ((struct ether_addr
*)LLADDR(gctx-interfaces-sdl))-octet[5]
+ );
+ error = md_lookup_swap(nd-swap_saddr,
+ gctx-lookup_path,
+ nd-swap_fh,
nd-swap_fhsize,
+ nd-swap_args, procp);
+ if (error != 0)
+ panic(nfs_boot: lookup swap name=%s,
error=%d,
+ gctx-lookup_path, error);
+ }
+ else
+ panic(nfs_boot: lookup swap, error=%d,
+ error);
+ }
}
nfs_diskless_valid = 3;
}
--
ian j hart
http://ars.userfriendly.org/cartoons/?id=20031016
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
diskless swap filename
Does anyone have a patch to use the mac address instead of the ip address for the swapfile name? Feeling lazy this week :) Cheers -- ian j hart http://ars.userfriendly.org/cartoons/?id=20031016 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
how to kernel debug
[Please CC] I have a growing collection of core dumps so I guess it's time to learn how to do this. Are there any docs I can read? I already found CH10 of the developers handbook and read the man pages for gdb and ddb. While I'm here, the handbook suggests that call boot(0) is a suitable method of leaving ddb. I just get a page fault. Is this normal? Thanks -- ian j hart http://ars.userfriendly.org/cartoons/?id=20031016 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
