Re: nmbclusters
On Tue, 28 Mar 2006 20:34:18 +0100 Chris [EMAIL PROTECTED] wrote: Using 6.0 release latest security branch. netstat -m 69/576/645 mbufs in use (current/cache/total) 65/261/326/33792 mbuf clusters in use (current/cache/total/max) 0/38/8704 sfbufs in use (current/peak/max) 147K/666K/813K bytes allocated to network (current/cache/total) 0 requests for sfbufs denied 0 requests for sfbufs delayed 29780 requests for I/O initiated by sendfile 633 calls to protocol drain routines sysctl kern.ipc.nmbclusters kern.ipc.nmbclusters: 65536 sysctl kern.ipc.nmbclusters=25000 kern.ipc.nmbclusters: 65536 - 25000 70/575/645 mbufs in use (current/cache/total) 64/262/326/33792 mbuf clusters in use (current/cache/total/max) 0/38/8704 sfbufs in use (current/peak/max) 145K/667K/813K bytes allocated to network (current/cache/total) 0 requests for sfbufs denied 0 requests for sfbufs delayed 29780 requests for I/O initiated by sendfile 633 calls to protocol drain routines so the sysctl variable has no affect, has this become a read only tunable again only settable in loader.conf? To the best of my knowledge, this has *always* been a loader tunable, not configurable on-the-fly. Myself, ever since the introduction quite some time ago of the friendly setting of 0 (for unlimited mbufs), I've always used that in my /boot/loader.conf, i.e., kern.ipc.nmbclusters=0. Can't really comment on your other questions, I'm afraid. :-) if yes then their is a bug where it shows no error on sysctl command, or is it suppoedbly settable then their is a bug where it doesnt work or netstat -m shows inccorect info. Or is this setting been depreciated? Also if the machine stops responding, and no kernel panic logged does it mean a livelock/deadlock? Have been seeing issues on 3 diff 6.0 release servers which simply go dead. 2 were rolled back to 5.4 and immediatly became stable and I left this one on 6.0 to try and resolve problems but diffilcult with no log entries. Thanks Chris -- Conrad J. Sabatier [EMAIL PROTECTED] -- In Unix veritas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kern/93381: kern/93381 : reboot(8) works but 'reboot -n' hangs
Hi! The same problem occures if 6.1-PRERELEASE kernel panic occures while configuration partition of NanoBSD is being updated (so, mounted read-write). This problem has occured now, I've got kernel panic while find(1) walked file system and the system become frozen after panic, it did not reboot. Please take a look at http://www.FreeBSD.org/cgi/query-pr.cgi?pr=kern/93381 Eugene Grosbein ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: new sk driver [was: nve timeout (and down) regression?]
On Tue, Mar 28, 2006 at 04:22:15PM +0200, Wilko Bulte wrote: On Mon, Mar 27, 2006 at 07:48:46PM -0800, Clint Olsen wrote.. On Mar 28, Pyun YongHyeon wrote: and sparc64(SMP) and I never see above errors. The only issue known to me is occasional watchdog timeout error which I really want to fix. But the watchdog timeout error is hard to reproduce and I couldn't reproduce the error on my system. I'm still seeing the watchdog timeout on 5.5-PRERELEASE (uni-processor): Mar 22 14:47:04 belle kernel: sk0: watchdog timeout Mar 24 08:37:19 belle kernel: sk0: watchdog timeout Mar 27 04:09:15 belle kernel: sk0: watchdog timeout But at least the driver doesn't wedge the interface now. Yes, same here on 6.1-PRERELEASE: ch0: 10 slots, 1 drive, 1 picker, 0 portals sk0: watchdog timeout sk0: watchdog timeout Ok, here is a new patch that try to fix the watchdog timeout error. I don't know it will eradicate the bug as I don't see the watchdog error on my system. The patch borrowed Yukon specific register definition from Linux driver and adopted Yukon FIFO related operations from Linux. I don't know exact meaning of the registers(it's just guessing) but it seems it doesn't hurt on my system. You may have to download 4 files to build the driver. http://people.freebsd.org/~yongari/sk/sk_test2/if_sk.c http://people.freebsd.org/~yongari/sk/sk_test2/if_skreg.h http://people.freebsd.org/~yongari/sk/sk_test2/xmaciireg.h http://people.freebsd.org/~yongari/sk/sk_test2/yukonreg.h -- Regards, Pyun YongHyeon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
gvinum help
Profuse apologies for any wrong list, missed faqs, etc. But I am looking for help with using gvinum to set up a raid volume. I have read the handbook, and I sort of understand how it works, I just cannot seem to figure out how to do it. My setup is a box running 6.0-RELEASE, I have 1 200G wd drive that I have set up as the os and I have 6 200G wd drives that I want to combine in a raid (hopefully 5, but just knowing how to do any would be great). Any pointers to howto docs ins the form of first do this, then do thiis, etc. would be helpful mostly I don't understand ow to prepare the drives in the array to be used by gvinum. I could probably figure out he rest on my own given enough time and monkeys. Thanks, Brad - Brad Miele [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gvinum help
brad miele wrote: Profuse apologies for any wrong list, missed faqs, etc. But I am looking for help with using gvinum to set up a raid volume. I have read the handbook, and I sort of understand how it works, I just cannot seem to figure out how to do it. My setup is a box running 6.0-RELEASE, I have 1 200G wd drive that I have set up as the os and I have 6 200G wd drives that I want to combine in a raid (hopefully 5, but just knowing how to do any would be great). Any pointers to howto docs ins the form of first do this, then do thiis, etc. would be helpful mostly I don't understand ow to prepare the drives in the array to be used by gvinum. I could probably figure out he rest on my own given enough time and monkeys. There is an article on the O'Reilly BSD Devcenter about setting up software RAID 1 with FreeBSD as a step by step tutorial. Here is the link: http://www.onlamp.com/pub/a/bsd/2005/11/10/FreeBSD_Basics.html I hope it helps. Cheers, Emil ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nmbclusters
Conrad J. Sabatier [EMAIL PROTECTED] writes: Chris [EMAIL PROTECTED] wrote: so [kern.ipc.nmbclusters] has no affect, has this become a read only tunable again only settable in loader.conf? To the best of my knowledge, this has *always* been a loader tunable, not configurable on-the-fly. kern.ipc.nmbclusters is normally computed at boot time. A compile- time option to override it was introduced in 2.0-CURRENT. At that time, it was defined in param.c. A read-only sysctl was introduced in 3.0-CURRENT. It moved from param.c to uipc_mbuf.c in 4.0-CURRENT, then to subr_mbuf.c when mballoc was introduced in 5.0-CURRENT; became a tunable at some point after that; then moved again to kern_mbuf.c when mballoc was replaced with mbuma in 6.0-CURRENT. That is the point where it became read-write, for no good reason that I can see; setting it at runtime has no effect, because the size of the mbuf zone is determined at boot time. Perhaps Bosko (who wrote both mballoc and mbuma, IIRC) knows. DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nmbclusters
It's always only been boot-time tunable (well, always is of course relative to my time with FreeBSD -- Dag-Erling has been around longer and therefore recounts its more comprehensive history). In 6.0-CURRENT there was an intention to make it sysctl (runtime) tunable, as it finally became at least theoretically possible to do so. I have recently seen a patch floating around from Paul Saab (ps@) who has finally made it runtime tunable -- at least enough so that it can be _increased_. Not sure if he has committed it, yet. Note that _decreasing_ nmbclusters at run-time will probably never be possible -- implementing is too difficult for what it would be worth. Cheers, Bosko On 3/29/06, Dag-Erling Smørgrav [EMAIL PROTECTED] wrote: Conrad J. Sabatier [EMAIL PROTECTED] writes: Chris [EMAIL PROTECTED] wrote: so [kern.ipc.nmbclusters] has no affect, has this become a read only tunable again only settable in loader.conf? To the best of my knowledge, this has *always* been a loader tunable, not configurable on-the-fly. kern.ipc.nmbclusters is normally computed at boot time. A compile- time option to override it was introduced in 2.0-CURRENT. At that time, it was defined in param.c. A read-only sysctl was introduced in 3.0-CURRENT. It moved from param.c to uipc_mbuf.c in 4.0-CURRENT, then to subr_mbuf.c when mballoc was introduced in 5.0-CURRENT; became a tunable at some point after that; then moved again to kern_mbuf.c when mballoc was replaced with mbuma in 6.0-CURRENT. That is the point where it became read-write, for no good reason that I can see; setting it at runtime has no effect, because the size of the mbuf zone is determined at boot time. Perhaps Bosko (who wrote both mballoc and mbuma, IIRC) knows. DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] -- Bosko Milekic [EMAIL PROTECTED] To see all the content I generate on the web, check out my Peoplefeeds profile at: http://peoplefeeds.com/bosko ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Installing FreeBSD 6.0 on IBM BladeCenter HS20 - IT WORKS!
On Mar 28, 2006, at 4:38 PM, Tom Samplonius wrote: 1. Disabling acpi. What happens for you if acpi is not disabled? I never tried this, and I'm not sure if this fixes anything or not. What did it do for you? Try disabling just the ACPI timer. At boot, break to the loader prompt and enter debug.acpi.disabled=timer boot then see if it works. I have one machine for which I must do this on FreeBSD = 6.0, and others have reported this as well. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
GRUB does not boot FreeBSD after installworld ...
HI, i have updatete to 6.1-PRERELEASE and after the installworld step GRUB is unable to boot FreeBSD. After i did the installworld and rebooted the GRUB error was: 23 : Error while parsing number I have reinstalled the standard FreeBSD loader for now. Booting with a GRUB boot-floppy i am able to start either XP or Linux but trying to start FreeBSD the system just reboots, no errormessage. I have already tried to install GRUB to MBR again, but no go, the system just reboots if i try to start FreeBSD. Any ideas? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
cannot type in GDM after installworld ...
Hi, additionally to my GRUB problem, GDM does not accept any keystroke at all, nada nothing, after updating to 6.1-PRERELEASE. I am using XDM for now. Any ideas here? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Data transfer from one HD to another
Quoting Matt Smith [EMAIL PROTECTED]: Will this also transfer the filesystem structure? Indeed. The man pages for these commands will provide variations of their usage. So as to obtain different results. Dependant upon your needs. --Chris Matt -Original Message- From: Joseph Olatt [mailto:[EMAIL PROTECTED] Sent: Sunday, March 26, 2006 8:45 AM To: Matt Smith Cc: freebsd-stable@freebsd.org Subject: Re: Data transfer from one HD to another On Sun, Mar 26, 2006 at 08:27:27AM -0500, Matt Smith wrote: Hi, Is there an EASY method to transfer the partitions from an old hard disk to a new one? I presume you want to trasfer all the files from one (or more) partition(s) in the old hard drive to a new hard drive. If so, try the command dd. man dd(1). There are examples at the bottom of the man page. Other commands that may be used are: tar cpio (man tar man cpio for more info). regards, joseph Matt Smith ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- Microsoft: Disc space -- the final frontier! - FreeBSD 5.4-RELEASE-p12 (SMP - 900x2) Tue Mar 7 19:37:23 PST 2006 / ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nmbclusters
On Wed, 29 Mar 2006, Dag-Erling Smørgrav wrote: Conrad J. Sabatier [EMAIL PROTECTED] writes: Chris [EMAIL PROTECTED] wrote: so [kern.ipc.nmbclusters] has no affect, has this become a read only tunable again only settable in loader.conf? To the best of my knowledge, this has *always* been a loader tunable, not configurable on-the-fly. kern.ipc.nmbclusters is normally computed at boot time. A compile- time option to override it was introduced in 2.0-CURRENT. At that time, it was defined in param.c. A read-only sysctl was introduced in 3.0-CURRENT. It moved from param.c to uipc_mbuf.c in 4.0-CURRENT, then to subr_mbuf.c when mballoc was introduced in 5.0-CURRENT; became a tunable at some point after that; then moved again to kern_mbuf.c when mballoc was replaced with mbuma in 6.0-CURRENT. That is the point where it became read-write, for no good reason that I can see; setting it at runtime has no effect, because the size of the mbuf zone is determined at boot time. Perhaps Bosko (who wrote both mballoc and mbuma, IIRC) knows. Paul Saab from Yahoo! has a set of patches that allow run-time nmbclusters changes to be implemented -- while it won't cause the freeing of clusters referenced, it goes through and recalculates dependent variables, propagates them into UMA, etc. I believe they're running with this patch on 6.x, and I expect that they will be merged to -CURRENT and -STABLE in the relatively near future. Not before 6.1, however. If the nmbclusters setting really has no effect right now, we should mark the sysctl as read-only to make it more clear it doesn't, since allowing it to be set without taking effect is counter-intuitive. Robert N M Watson___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cannot type in GDM after installworld ...
From [EMAIL PROTECTED] Wed Mar 29 16:42:48 2006 From: Norbert Augenstein [EMAIL PROTECTED] To: freebsd-stable@freebsd.org Date: Wed, 29 Mar 2006 17:42:07 +0200 Subject: cannot type in GDM after installworld ... Hi, additionally to my GRUB problem, GDM does not accept any keystroke at all, nada nothing, after updating to 6.1-PRERELEASE. I am using XDM for now. Any ideas here? Yes, I had a similar problem. Perhaps the same. GDM's allocation of a VT may conflict with getty. In the configuration file, there's a parameter which is FirstVT with default value 9. He'll try to use, by default, ttyv8 as its VT. Sometimes, he'll get it before getty does. Then it works. Sometimes, he get's it afterwards and you get that strange conflict. I used to have all VTs until ttva enabled in /etc/ttys, so this would conflict with GDM's default configuration file. If this is your case, try these two solutions: 1- change FirstVT to a diferent (higher) value 2- disable all VTs below 9 in /etc/ttys I chose the second solution, because GDM can use more than one VT, enabling several users of the same console to be logged in graphically and simultaneously. -- Miguel Ramos GnuPG ID 0xA006A14C ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cannot type in GDM after installworld ...
From [EMAIL PROTECTED] Wed Mar 29 16:42:48 2006 From: Norbert Augenstein [EMAIL PROTECTED] To: freebsd-stable@freebsd.org Date: Wed, 29 Mar 2006 17:42:07 +0200 Subject: cannot type in GDM after installworld ... Hi, additionally to my GRUB problem, GDM does not accept any keystroke at all, nada nothing, after updating to 6.1-PRERELEASE. I am using XDM for now. Any ideas here? Yes, I had a similar problem. Perhaps the same. GDM's allocation of a VT may conflict with getty. In the configuration file, there's a parameter which is FirstVT with default value 9. He'll try to use, by default, ttyv8 as its VT. Sometimes, he'll get it before getty does. Then it works. Sometimes, he get's it afterwards and you get that strange conflict. I used to have all VTs until ttva enabled in /etc/ttys, so this would conflict with GDM's default configuration file. If this is your case, try these two solutions: 1- change FirstVT to a diferent (higher) value 2- disable all VTs below 9 in /etc/ttys I chose the second solution, because GDM can use more than one VT, enabling several users of the same console to be logged in graphically and simultaneously. -- Miguel Ramos GnuPG ID 0xA006A14C ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GRUB does not boot FreeBSD after installworld ...
From: Norbert Augenstein [EMAIL PROTECTED] Subject: GRUB does not boot FreeBSD after installworld ... HI, i have updatete to 6.1-PRERELEASE and after the installworld step GRUB is unable to boot FreeBSD. Perhaps it wasn't the installworld step that caused this... The boot record isn't touched... After i did the installworld and rebooted the GRUB error was: 23 : Error while parsing number I have reinstalled the standard FreeBSD loader for now. Booting with a GRUB boot-floppy i am able to start either XP or Linux but trying to start FreeBSD the system just reboots, no errormessage. I have already tried to install GRUB to MBR again, but no go, the system just reboots if i try to start FreeBSD. Any ideas? How are you installing grub? From floppy? What are your configuration files? -- Miguel ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nmbclusters
Chris [EMAIL PROTECTED] writes: thanks for everyones responses. My 5.4 servers seem to accept the tunable been changed at runtime although this could be a bug and it isnt really changing? You can change it, but it has no effect. DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Strange Panic During Reboot
I'm getting the following panic during shutdown of a 6.1-PRERELEASE system cvsupped yesterday. Strangely enabling DDB in the kernel fixes the problem. The computer is an old P120 (which I should probably replace). It occurs every time when DDB is disabled but when DDB is enabled, it does not panic. All buffers synced. Uptime: 19m16s (da0:ahc0:0:0:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 (da0:ahc0:0:0:0): Sense Error Code 0xe0 at block no. -1073741792 (decimal) kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode fault virtual address = 0x1c fault code = supervisor write, page not present instruction pointer = 0x20:0xc0539553 stack pointer = 0x28:0xc6da2a68 frame pointer = 0x28:0xc6da2ab4 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= resume, IOPL = 0 current process = 1728 (reboot) trap number = 12 panic: page fault Uptime: 19m16s I suspect that memory is mapped a tiny bit differently with DDB enabled and thus we don't tickle a bug somewhere. Thoughts? -- Regards, Phone: (250)387-8437 Cy SchubertFax: (250)387-5231 Team Leader, Solaris TeamEmail: [EMAIL PROTECTED] Open Systems Group, CITS Ministry of Labour and Citizens' Services Province of BC FreeBSD UNIX: [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GRUB does not boot FreeBSD after installworld ...
On Wed, 2006-03-29 at 20:07 +0100, [EMAIL PROTECTED] wrote: From: Norbert Augenstein [EMAIL PROTECTED] Subject: GRUB does not boot FreeBSD after installworld ... HI, i have updatete to 6.1-PRERELEASE and after the installworld step GRUB is unable to boot FreeBSD. Perhaps it wasn't the installworld step that caused this... The boot record isn't touched... I did a reboot after installkernel so i know the 6.1-PRE kernel was able to boot, and GRUB did not complain too. So whatelse could have changed? After i did the installworld and rebooted the GRUB error was: 23 : Error while parsing number I have reinstalled the standard FreeBSD loader for now. Booting with a GRUB boot-floppy i am able to start either XP or Linux but trying to start FreeBSD the system just reboots, no errormessage. I have already tried to install GRUB to MBR again, but no go, the system just reboots if i try to start FreeBSD. Any ideas? How are you installing grub? From floppy? yes, booting from grub-floppy root (hd0,1,a) kernel /boot/loader setup (hd0) no error up to here! but typing boot does not boot, it reboots the system without errormessage. Booting XP or Linux works with the grub-floppy by just typing the root and kernel line from menu.lst and boot [EMAIL PROTECTED] ~]% cat /boot/grub/menu.lst default 0 timeout 2 title FreeBSD -- The Power to Serve root (hd0,1,a) kernel /boot/loader title Gentoo Linux root (hd0,2) kernel /kernel root=/dev/hda3 title Windoof -- The eXPerience root (hd0,0) chainloader +1 What are your configuration files? menu.lst what else? Thanks, -- auge ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: news good
D B ear Home O y wner , Your cred K it doesn't matter to us ! If you O G WN real e X st W at 2 e and want IMM G EDIA n TE cas y h to spe L nd ANY way you like, or simply wish to LO P WER your monthly p g ayments by a third or more, here are the deal G s we have T 4 ODA y Y : $48 D 8,000.00 at a 3.6 Q 7% fixe i d-ra s te $37 B 2,000.00 at a 3 k .90% variab h le-ra p te $49 I 2,000.00 at a 3.2 0 1% i u ntere M st-only $24 d 8,000.00 at a 3. 4 36% fix r ed-ra o te $1 1 98,000.00 at a 3.5 p 5% v e ariable-ra A te Hur t ry, when these dea F Is are gone, they are gone ! Don't worry about a y pproval, your cre D dit will not di e squalify you ! Vis K it our sit 1 e http://geocities.com/DieNysbornRoman/ Sincerely, Xiang Maddocks App Y roval Manager ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GRUB does not boot FreeBSD after installworld ...
On Wed, 2006-03-29 at 23:33 +0200, Michel Talon wrote: Maybe you have an old Grub which doesn't grok UFS2? No, Grub 0.97 works fine with UFS2 I will cvsup again and rebuild everything, without CPUTYPE=athlon-xp in make.conf I can remember some bootproblems on my laptop with CPUTYPE?=pentium3m It is the case on my machine so i use chainloader to boot freebsd, like that: title FreeBSD root(hd0,3) savedefault makeactive chainloader +1 boot Linux i can boot directly: title Debian GNU/Linux, kernel 2.6.8-2-k7 root(hd0,5) kernel /boot/vmlinuz-2.6.8-2-k7 root=/dev/hda6 ro acpi=force initrd /boot/initrd.img-2.6.8-2-k7 savedefault boot WindowsXP i also chainload. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Data transfer from one HD to another
Posted this to OP but omitted to post to the list. Here's my 2p worth Chris Matt Smith wrote: Hi, Is there an EASY method to transfer the partitions from an old hard disk to a new one? Matt Smith ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] I regularly do this cloning desktops. I am usually using the same size / /var /tmp and swap and whatever is remaining as /usr Install new disk as primary master. Boot from CD and install minimal system (you can even abort once it has created the file system, the only purpose of this step is to create the slices and newfs. I think this is quicker than doing it with sysinstall or fdisk/bsdlabel. When it's me doing it it is certainly more error free.) Next install your source disk as primary master and new disk as anything else. (ad1 in example below) Boot to single user. Now do: mount -u / mount /dev/ad1s1a /mnt cd /mnt rm -rf /mnt/* /mnt/.* dump 0afL - / | restore xf - cd umount /mnt fsck -y /dev/ad1s1a Do the same sequence of steps for /tmp, mounting /tmp read/write and using L switch in dump. You don't need to do the mount -u / again. [Can anybody tell me if it is really necessary to clone /tmp? Not that it takes much time.] Do the same sequence of steps for /var and /usr but mounting them ro and not using the L switch in dump My /usr takes some time like 1 - 2 hours, the rest you can do as you sit at the machine. Sometimes the rm fails to remove a directory called empty - you have to chflags it. I've done this quite a few times and had no problems. I've tried various variations and this one is the only one that didn't come to some sort of sticky end for me. Cleverer people would probably have found a way through. I did try putting my commands in a script but the result was b0rked somehow and I never found time to investigate why. Chris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.1-PRERELEASE: freezing
On Mon, 27 Mar 2006 13:03:30 -0800 Sam Leffler wrote:
László Károly wrote:
Boris Samorodov wrote:
I've had 6.0-STABLE as of jan-2006. Yesterday it was upgraded to
current 6.1-PRERELEASE (tag=RELENG_6). The hardware is HP/Compaq
nx6110 notebook.
After upgrading mashine is freezing under load. After booting the
OS without any actions it's OK for two hours. But after starting of
make buildkernel the mashine freezes.
It's freezing (actually it's an IRQ storm) when the cooler temperature
is increased and the speed of the fan should be increased.
I have the same box and I too made an upgrade yesterday (from a
two-week-old 6.1-PRERELEASE). The same experience: the system became
unusably slow, no problem without ACPI.
What type of debugging should I do to find up what's up?
Good question ;-): how to debug a system which practically does not
react but runs?
Are you running powerd? I've got an nx6125 (amd cpu) that has
numerous acpi issues and also would lockup when idle. I found turning
off powerd stopped the latter. Unfortunately there are still many
other unresolved issues (and no time to pursue them).
I found when things went broken. It is the patch(es) as of
2006-01-13. The patch is at attachment. After applying (reversed)
patch acpi is working as well as management of the cooler speed.
Sam, should I do some other testing?
László, can you apply the patch (cd /usr/src; patch -R -p0
_the_patch_), make kernel and tell us if the problem go out?
As for me the reversed patch worked for current 6.1-PRERELEASE
(cvsupped some hours ago).
WBR
--
Boris B. Samorodov, Research Engineer
InPharmTech Co, http://www.ipt.ru
Telephone Internet Service Provider
diff -ruN src.03.14/sys/dev/acpica/Osd/OsdSchedule.c src.03.15/sys/dev/acpica/Osd/OsdSchedule.c
--- sys/dev/acpica/Osd/OsdSchedule.c.orig Wed Mar 29 17:46:29 2006
+++ sys/dev/acpica/Osd/OsdSchedule.c Wed Mar 29 18:02:22 2006
@@ -30,7 +30,7 @@
*/
#include sys/cdefs.h
-__FBSDID($FreeBSD: src/sys/dev/acpica/Osd/OsdSchedule.c,v 1.32.2.2 2005/11/07 09:53:23 obrien Exp $);
+__FBSDID($FreeBSD: src/sys/dev/acpica/Osd/OsdSchedule.c,v 1.32.2.3 2006/03/14 23:28:30 sam Exp $);
#include opt_acpi.h
#include sys/param.h
@@ -65,31 +65,8 @@
void *at_context;
};
-/*
- * Private task queue definition for ACPI
- */
-static struct proc *
-acpi_task_start_threads(struct taskqueue **tqp)
-{
-struct proc *acpi_kthread_proc;
-int err, i;
-
-KASSERT(*tqp != NULL, (acpi taskqueue not created before threads));
-
-/* Start one or more threads to service our taskqueue. */
-for (i = 0; i acpi_max_threads; i++) {
- err = kthread_create(taskqueue_thread_loop, tqp, acpi_kthread_proc,
- 0, 0, acpi_task%d, i);
- if (err) {
- printf(%s: kthread_create failed (%d)\n, __func__, err);
- break;
- }
-}
-return (acpi_kthread_proc);
-}
-
TASKQUEUE_DEFINE(acpi, taskqueue_thread_enqueue, taskqueue_acpi,
-taskqueue_acpi_proc = acpi_task_start_threads(taskqueue_acpi));
+taskqueue_start_threads(taskqueue_acpi, 3, PWAIT, acpi_task));
/*
* Bounce through this wrapper function since ACPI-CA doesn't understand
diff -ruN src.03.14/sys/kern/kern_synch.c src.03.15/sys/kern/kern_synch.c
--- sys/kern/kern_synch.c.orig Wed Mar 29 17:46:44 2006
+++ sys/kern/kern_synch.c Wed Mar 29 18:02:38 2006
@@ -35,7 +35,7 @@
*/
#include sys/cdefs.h
-__FBSDID($FreeBSD: src/sys/kern/kern_synch.c,v 1.270.2.2 2006/02/27 00:19:40 davidxu Exp $);
+__FBSDID($FreeBSD: src/sys/kern/kern_synch.c,v 1.270.2.3 2006/03/14 23:28:30 sam Exp $);
#include opt_ktrace.h
@@ -218,6 +218,88 @@
mtx_lock(mtx);
WITNESS_RESTORE(mtx-mtx_object, mtx);
}
+ return (rval);
+}
+
+int
+msleep_spin(ident, mtx, wmesg, timo)
+ void *ident;
+ struct mtx *mtx;
+ const char *wmesg;
+ int timo;
+{
+ struct thread *td;
+ struct proc *p;
+ int rval;
+ WITNESS_SAVE_DECL(mtx);
+
+ td = curthread;
+ p = td-td_proc;
+ KASSERT(mtx != NULL, (sleeping without a mutex));
+ KASSERT(p != NULL, (msleep1));
+ KASSERT(ident != NULL TD_IS_RUNNING(td), (msleep));
+
+ if (cold) {
+ /*
+ * During autoconfiguration, just return;
+ * don't run any other threads or panic below,
+ * in case this is the idle thread and already asleep.
+ * XXX: this used to do s = splhigh(); splx(safepri);
+ * splx(s); to give interrupts a chance, but there is
+ * no way to give interrupts a chance now.
+ */
+ return (0);
+ }
+
+ sleepq_lock(ident);
+ CTR5(KTR_PROC, msleep_spin: thread %p (pid %ld, %s) on %s (%p),
+ (void *)td, (long)p-p_pid, p-p_comm, wmesg, ident);
+
+ DROP_GIANT();
+ mtx_assert(mtx, MA_OWNED | MA_NOTRECURSED);
+ WITNESS_SAVE(mtx-mtx_object, mtx);
+ mtx_unlock_spin(mtx);
+
+ /*
+ * We put ourselves on the sleep queue and start our timeout.
+ */
+ sleepq_add(ident, mtx, wmesg, SLEEPQ_MSLEEP);
+ if (timo)
+ sleepq_set_timeout(ident, timo);
+
+ /*
+ * Can't call ktrace with any spin locks held so it can lock the
+ * ktrace_mtx lock, and
Re: 6.1-PRERELEASE: freezing
On Thu, 30 Mar 2006 02:27:50 +0400 Boris Samorodov wrote: On Mon, 27 Mar 2006 13:03:30 -0800 Sam Leffler wrote: László Károly wrote: Boris Samorodov wrote: I've had 6.0-STABLE as of jan-2006. Yesterday it was upgraded to current 6.1-PRERELEASE (tag=RELENG_6). The hardware is HP/Compaq nx6110 notebook. After upgrading mashine is freezing under load. After booting the OS without any actions it's OK for two hours. But after starting of make buildkernel the mashine freezes. It's freezing (actually it's an IRQ storm) when the cooler temperature is increased and the speed of the fan should be increased. I have the same box and I too made an upgrade yesterday (from a two-week-old 6.1-PRERELEASE). The same experience: the system became unusably slow, no problem without ACPI. What type of debugging should I do to find up what's up? Good question ;-): how to debug a system which practically does not react but runs? Are you running powerd? I've got an nx6125 (amd cpu) that has numerous acpi issues and also would lockup when idle. I found turning off powerd stopped the latter. Unfortunately there are still many other unresolved issues (and no time to pursue them). I found when things went broken. It is the patch(es) as of 2006-01-13. The patch is at attachment. After applying (reversed) Sorry, the date should be 2006-03-14. patch acpi is working as well as management of the cooler speed. Sam, should I do some other testing? László, can you apply the patch (cd /usr/src; patch -R -p0 _the_patch_), make kernel and tell us if the problem go out? As for me the reversed patch worked for current 6.1-PRERELEASE (cvsupped some hours ago). WBR -- Boris B. Samorodov, Research Engineer InPharmTech Co, http://www.ipt.ru Telephone Internet Service Provider ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] WBR -- bsam Boris B. Samorodov, Research Engineer InPharmTech Co, http://www.ipt.ru Telephone Internet Service Provider ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GRUB does not boot FreeBSD after installworld ...
On Wednesday 29 March 2006 14:07, Norbert Augenstein wrote: On Wed, 2006-03-29 at 23:33 +0200, Michel Talon wrote: Maybe you have an old Grub which doesn't grok UFS2? No, Grub 0.97 works fine with UFS2 I will cvsup again and rebuild everything, without CPUTYPE=athlon-xp in make.conf I can remember some bootproblems on my laptop with CPUTYPE?=pentium3m I had a problem with 6.1-pre not booting. In my case, I had an old version of boot1 being used by ntldr. When I updated boot1, I didn't have any problem booting. Kent It is the case on my machine so i use chainloader to boot freebsd, like that: title FreeBSD root(hd0,3) savedefault makeactive chainloader +1 boot Linux i can boot directly: title Debian GNU/Linux, kernel 2.6.8-2-k7 root(hd0,5) kernel /boot/vmlinuz-2.6.8-2-k7 root=/dev/hda6 ro acpi=force initrd /boot/initrd.img-2.6.8-2-k7 savedefault boot WindowsXP i also chainload. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- Kent Stewart Richland, WA http://www.soyandina.com/ I am Andean project. http://users.owt.com/kstewart/index.html ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nmbclusters
On 29/03/06, Robert Watson [EMAIL PROTECTED] wrote: On Wed, 29 Mar 2006, Dag-Erling Smørgrav wrote: Conrad J. Sabatier [EMAIL PROTECTED] writes: Chris [EMAIL PROTECTED] wrote: so [kern.ipc.nmbclusters] has no affect, has this become a read only tunable again only settable in loader.conf? To the best of my knowledge, this has *always* been a loader tunable, not configurable on-the-fly. kern.ipc.nmbclusters is normally computed at boot time. A compile- time option to override it was introduced in 2.0-CURRENT. At that time, it was defined in param.c. A read-only sysctl was introduced in 3.0-CURRENT. It moved from param.c to uipc_mbuf.c in 4.0-CURRENT, then to subr_mbuf.c when mballoc was introduced in 5.0-CURRENT; became a tunable at some point after that; then moved again to kern_mbuf.c when mballoc was replaced with mbuma in 6.0-CURRENT. That is the point where it became read-write, for no good reason that I can see; setting it at runtime has no effect, because the size of the mbuf zone is determined at boot time. Perhaps Bosko (who wrote both mballoc and mbuma, IIRC) knows. Paul Saab from Yahoo! has a set of patches that allow run-time nmbclusters changes to be implemented -- while it won't cause the freeing of clusters referenced, it goes through and recalculates dependent variables, propagates them into UMA, etc. I believe they're running with this patch on 6.x, and I expect that they will be merged to -CURRENT and -STABLE in the relatively near future. Not before 6.1, however. If the nmbclusters setting really has no effect right now, we should mark the sysctl as read-only to make it more clear it doesn't, since allowing it to be set without taking effect is counter-intuitive. Robert N M Watson thanks for everyones responses. My 5.4 servers seem to accept the tunable been changed at runtime although this could be a bug and it isnt really changing? 4.x I know was a boot only tunable. I have tested this now in loader.conf and it works so it seems its a minor bug where the error message is replaced by a false success output. Chris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
4.9 network not freeing memory
Hi, I realize this is a very old release but we have over a 1000 systems deployed so it is hard to upgrade. Anyway we are using gre/vpn/gif. If I stress test the system with netperf or nttcp I eventually run into the situation where netperf is in sbwait state and it stays there forever. I can't log into the machine with ssh but I can go in thru the console. If I try to ping localhost I get ping: sendto: No buffer space available. The only recourse to get things going again is reboot. If I do and netstat -m it shows I have mbufs available. The system is a Duron 1.6ghz with 256 mb of memory. What I am looking for is some direction on how to further diagnose the problem. this is before the problem $ netstat -m 2/736/131072 mbufs in use (current/peak/max): 2 mbufs allocated to data 0/672/32768 mbuf clusters in use (current/peak/max) 1528 Kbytes allocated to network (1% of mb_map in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines this is after the problem: 965/1376/131072 mbufs in use (current/peak/max): 965 mbufs allocated to data 872/876/32768 mbuf clusters in use (current/peak/max) 2096 Kbytes allocated to network (2% of mb_map in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines Any ideas would be greatly appreciated. Steve ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[SOLVED]Re: GRUB does not boot FreeBSD after installworld ...
On Wed, 2006-03-29 at 14:44 -0800, Kent Stewart wrote: On Wednesday 29 March 2006 14:07, Norbert Augenstein wrote: On Wed, 2006-03-29 at 23:33 +0200, Michel Talon wrote: Maybe you have an old Grub which doesn't grok UFS2? No, Grub 0.97 works fine with UFS2 I will cvsup again and rebuild everything, without CPUTYPE=athlon-xp in make.conf I can remember some bootproblems on my laptop with CPUTYPE?=pentium3m I had a problem with 6.1-pre not booting. In my case, I had an old version of boot1 being used by ntldr. When I updated boot1, I didn't have any problem booting. I commented out #CPUTYPE?=athlon-xp #CFLAGS= -O2 -pipe in make.conf and did a buildworld again, GRUB installs and works fine again. Thanks and sorry for the noise, -- auge ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Call for FreeBSD Status Reports
Hi All, It is time for the quarterly Status Reports. As always, reports are encouraged for anything that relates to FreeBSD development, documentation, independent projects, or anything else that might be interesting to the community as a whole. Reports should be one to two paragraphs in length. The template for submissions is here: http://www.freebsd.org/news/status/report-sample.xml Submissions should be submitted to monthly at FreeBSD.org by April 7th. Regards, Brad Davis ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.1-BETA4-i386-disc2.iso - only usr/share/doc, no usr/src?
in message [EMAIL PROTECTED], wrote Scot Hetzel thusly... On 3/27/06, Parv [EMAIL PROTECTED] wrote: Does the 6.1-BETA4-i386-disc2.iso contain only usr/share/doc, or for some reason i am unable to see anything else? I was looking for usr/src (and for a odd chance to have usr/ports); i suppose those two trees would be available somewhere on some disc for RELENG_6_1. Have you checked if they are on the disc1 ISO? Oh, yes both (src ports) were there on disc1 under 6.1-BETA* directory. For some reason, that directory just did not register. Sorry for the noise. - Parv -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Your message to hlcoders awaits moderator approval
Your mail to 'hlcoders' with the subject Delivery failed Is being held until the list moderator can review it for approval. The reason it is being held: Post by non-member to a members-only list Either the message will get posted to the list, or you will receive notification of the moderator's decision. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GRUB does not boot FreeBSD after installworld ...
Norbert Augenstein wrote:
On Wed, 2006-03-29 at 23:33 +0200, Michel Talon wrote:
Maybe you have an old Grub which doesn't grok UFS2?
No, Grub 0.97 works fine with UFS2
I will cvsup again and rebuild everything, without CPUTYPE=athlon-xp
in make.conf
I can remember some bootproblems on my laptop with CPUTYPE?=pentium3m
It is the case on my machine so i use chainloader to boot freebsd, like that:
title FreeBSD
root(hd0,3)
savedefault
makeactive
chainloader +1
boot
Linux i can boot directly:
title Debian GNU/Linux, kernel 2.6.8-2-k7
root(hd0,5)
kernel /boot/vmlinuz-2.6.8-2-k7 root=/dev/hda6 ro acpi=force
initrd /boot/initrd.img-2.6.8-2-k7
savedefault
boot
WindowsXP i also chainload.
I had similar problems, the following entry in my /etc/make.conf fixed
this for me:
# /boot/loader crashs with pentium-m
.if ${.CURDIR:M*/src/sys/boot/i386/loader*}
.undef CPUTYPE
CPUTYPE?= pentium3
CFLAGS= -O2 -pipe
.endif
Just replace pentium3 with something that works on your system.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
