from kumar
Hai frienz, I am kumar studying MCA final year in NITWarangal. I am doing project in Device driver coding for harddisk.i want some documents related to harddisk port addresses..so that i can continue with my project.. can any one please help me in this.. -- K.V.V.S.M.B.Kumar MCA VI SEM NIT Warangal-506004. Phone : 9440584249 (M) 08856-276302(R) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: RELENG_6: serial console drops back from 115200 to 9600 baud
In message <[EMAIL PROTECTED]>, Mike Tancsa writes: >I think I am almost there, but in my case, I get some strange char >duplication after seeing the F1 prompt. The BIOS has console >redirection, so I can see it throughout the bootup process. ... >//bbtt..ccoo- ffiigg:: --DDhh// >BTX loader 1.00 BTX version is 1.01 >Consoles:ointernal >video/keyboardalserialiportoo//kkeeyybbooaarrdd That's probably expected if you enable dual console mode (-D) when the BIOS is also redirecting VGA output to the serial port. Each character goes to both the serial port and the screen, but the BIOS is also copying screen characters to the serial port so each character appears twice. Once the kernel starts it no longer uses BIOS calls to output to the screen. There might be a BIOS option to disable the redirection when booting. Alternatively you could remove the -D, but you will no longer get kernel boot messages on the VGA console. Ian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bash 3.1.10 breaks configure scripts (was Re: configure scripts ignores parameters)
On Mon, Mar 06, 2006 at 04:59:42PM -0500, Kris Kennaway wrote: > On Sun, Mar 05, 2006 at 04:01:19AM -0500, Kris Kennaway wrote: > > On Sun, Mar 05, 2006 at 09:57:54AM +0100, Nicolas Rachinsky wrote: > > > * Kris Kennaway <[EMAIL PROTECTED]> [2006-03-05 03:41 -0500]: > > > > On Sun, Mar 05, 2006 at 09:36:25AM +0100, Nicolas Rachinsky wrote: > > > > > The problem seems to depend on the installed bison version. With no > > > > > bison or bison-2.1_1 installed it works fine, with bison-1.75_2,1 it > > > > > doesn't. > > > > > > > > Installed at what point: the build time of the bash port, or runtime > > > > (which would be very odd)? > > > > > > The build time. I submitted ports/94086, which contains a > > > fix/workaround. > > > > Great, thanks for tracking this down! Can others confirm this > > solution? > > I have committed the patch, so this should go away next time you > portupgrade. Kris, thanks for taking care of this. I've been Net-dead for 3 weeks. -- -- David ([EMAIL PROTECTED]) Q: Because it reverses the logical flow of conversation. A: Why is top-posting (putting a reply at the top of the message) frowned upon? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cvs commit: www/en/releases/6.1R todo.sgml
On Tuesday 07 March 2006 04:46, Hiroki Sato wrote: > Gleb Smirnoff <[EMAIL PROTECTED]> wrote > in <[EMAIL PROTECTED]>: > > gl> Is it possible place kern/87208 into TODO list for 6.1-RELEASE? > gl> The problem appeared to be a bad regression in 6.0-RELEASE, > gl> that hurted many users. The PR contains several test cases, > gl> description and patch for the problem. > > Thanks, added just now. Will this description do? > > -- > > | Hiroki SATO Please add: 'calcru: runtime went backwards' bug for threaded program. David Xu ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Failing to understand getrusage()
On Thu, Mar 02, 2006 at 11:50:29PM +, Nick Barnes wrote:
> At 2006-03-02 22:24:17+, Nik Clayton writes:
> > I'm failing to understand how getrusage() works, which is a bit perplexing,
> > because it doesn't seem like it would be terribly complicated.
>
> ru_maxrss is the maximum resident set size, not the heap size.
> malloc(big) doesn't grow the resident set. Touching the memory you
> have allocated will grow the resident set. Try this:
>
> getrusage(RUSAGE_SELF, &ru);
> printf("%lu\n", ru.ru_maxrss);
> p = malloc(SIZE);
> assert(p)
> getrusage(RUSAGE_SELF, &ru);
> printf("%lu\n", ru.ru_maxrss);
> for (i=0; i p[i] = 0;
> }
> getrusage(RUSAGE_SELF, &ru);
> printf("%lu\n", ru.ru_maxrss);
Well, there was a call to memset() in the original Nik's program
while your code just does the same by itself.
Personally, I'd like to say a "me too". /me too fails to see why
in a quiet, idle system ru_maxrss is very unpredictable over numerous
runs of the test program, both before and after the malloc+memset.
Filling the memory with a non-zero value doesn't matter. Is it the
Heizenberg daemon at work? :-)
--
Yar
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
no ipmon output
Having upgraded from 5.4 to 6.1-PRERELEASE on two systems I find that ipmon
produces an output on one but not the other. "truss ipmon" on the non-
functioning system produces
. . .
open("/var/run/ipmon.pid",0x601,0644)= 4 (0x4)
getdtablesize() = 11095 (0x2b57)
fcntl(4,F_GETFL,0x0) = 1 (0x1)
getpid() = 88512 (0x159c0)
fstat(4,0xbfbfc900) = 0 (0x0)
write(4,0x805f000,5) = 5 (0x5)
close(4) = 0 (0x0)
sigaction(SIGHUP,{ 0x8049510
0x0|ONSTACK|RESETHAND|NOCLDSTOP|NODEFER|NOCLDWAIT|SIGINFO ss_t },{ SIG_DFL
0x0|ONSTACK|RESTART|RESETHAND|NOCLDSTOP|NODEFER|NOCLDWAIT|SIGINFO ss_t }) = 0
(0x0)
ioctl(3,FIONREAD,0xbfbfccfc) = 0 (0x0)
nanosleep({1 0}) = 0 (0x0)
ioctl(3,FIONREAD,0xbfbfccfc) = 0 (0x0)
leading to endless iterations of nanosleep, whereas the system w/ the working
ipmon begins to write packet pass/block values @ this point.
there are no relevant kernel differences (ipfilter, ipfilter log, & ipfilter
default block are compiled into both). both run 6.1-PRERELEASE on i386,
loader.conf sysctl.conf are the same on both systems, rc.conf is the same in
all relevent respects w/ the possible exception that the system w/the non-
working ipmon is natting, & both system have the same modules installed.
i'd appreciate suggestions for troubleshooting this problem.
thanks.
===
David Coder
Erstwhile Network Engineer
Washington, DC
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cvs commit: www/en/releases/6.1R todo.sgml
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 While we're at it, bin/94028 points out a fundamental problem with ifconfig(8) as it stands on 6.1-PRERELEASE, preventing MTUs from being set on vlan interfaces. - -aDe -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFEDLzBpXS8U0IvffwRAon2AJ463hVinulXQWe4f/FnRLt5lbFQRgCghQK9 tZ8ICssIVEoUzPmrOPMfUuc= =7K0L -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
rpc.lockd brokenness (2)
I'm not yet received enough information to track rpc.lockd problem.
As Kris posted before, here is a patch to backout my suspected
commit. If someone can easily reproduce this problem, please try with
this patch on both of server/client side of rpc.lockd (I'm not sure
which of server/client side this affects).
http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/80389
http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/84953
Any reports about this patch (OK or still problem) are welcome!
Index: lock_proc.c
===
RCS file: /home/ncvs/src/usr.sbin/rpc.lockd/lock_proc.c,v
retrieving revision 1.18
retrieving revision 1.17
diff -u -r1.18 -r1.17
--- lock_proc.c 3 Feb 2005 22:21:19 - 1.18
+++ lock_proc.c 9 Oct 2004 15:36:13 - 1.17
@@ -62,8 +62,6 @@
#defineCLIENT_CACHE_SIZE 64 /* No. of client sockets cached
*/
#defineCLIENT_CACHE_LIFETIME 120 /* In seconds */
-#definegetrpcaddr(rqstp) (struct sockaddr
*)(svc_getrpccaller((rqstp)->rq_xprt)->buf)
-
static voidlog_from_addr(const char *, struct svc_req *);
static voidlog_netobj(netobj *obj);
static int addrcmp(struct sockaddr *, struct sockaddr *);
@@ -196,7 +194,7 @@
{
CLIENT *client;
struct timeval retry_time, time_now;
- int error, i;
+ int i;
const char *netid;
struct netconfig *nconf;
char host[NI_MAXHOST];
@@ -243,11 +241,9 @@
* Need a host string for clnt_tp_create. Use NI_NUMERICHOST
* to avoid DNS lookups.
*/
- error = getnameinfo(host_addr, host_addr->sa_len, host, sizeof host,
- NULL, 0, NI_NUMERICHOST);
- if (error != 0) {
- syslog(LOG_ERR, "unable to get name string for caller: %s",
- gai_strerror(error));
+ if (getnameinfo(host_addr, host_addr->sa_len, host, sizeof host,
+ NULL, 0, NI_NUMERICHOST) != 0) {
+ syslog(LOG_ERR, "unable to get name string for caller");
return NULL;
}
@@ -566,7 +562,8 @@
res.cookie = arg->cookie;
res.stat.stat = getlock(&arg4, rqstp, LOCK_ASYNC | LOCK_MON);
- transmit_result(NLM_LOCK_RES, &res, getrpcaddr(rqstp));
+ transmit_result(NLM_LOCK_RES, &res,
+ (struct sockaddr *)svc_getcaller(rqstp->rq_xprt));
return (NULL);
}
@@ -620,7 +617,8 @@
* a lock to cancel, so this call always fails.
*/
res.stat.stat = unlock(&arg4, LOCK_CANCEL);
- transmit_result(NLM_CANCEL_RES, &res, getrpcaddr(rqstp));
+ transmit_result(NLM_CANCEL_RES, &res,
+ (struct sockaddr *)svc_getcaller(rqstp->rq_xprt));
return (NULL);
}
@@ -667,7 +665,8 @@
res.stat.stat = unlock(&arg4, 0);
res.cookie = arg->cookie;
- transmit_result(NLM_UNLOCK_RES, &res, getrpcaddr(rqstp));
+ transmit_result(NLM_UNLOCK_RES, &res,
+ (struct sockaddr *)svc_getcaller(rqstp->rq_xprt));
return (NULL);
}
@@ -724,7 +723,8 @@
nlm_granted, NULL, NLM_VERS) == 0 ?
nlm_granted : nlm_denied;
- transmit_result(NLM_GRANTED_RES, &res, getrpcaddr(rqstp));
+ transmit_result(NLM_GRANTED_RES, &res,
+ (struct sockaddr *)svc_getcaller(rqstp->rq_xprt));
return (NULL);
}
@@ -1067,7 +1067,8 @@
res.cookie = arg->cookie;
res.stat.stat = getlock(arg, rqstp, LOCK_MON | LOCK_ASYNC | LOCK_V4);
- transmit4_result(NLM4_LOCK_RES, &res, getrpcaddr(rqstp));
+ transmit4_result(NLM4_LOCK_RES, &res,
+ (struct sockaddr *)svc_getcaller(rqstp->rq_xprt));
return (NULL);
}
@@ -1115,7 +1116,8 @@
* a lock to cancel, so this call always fails.
*/
res.stat.stat = unlock(&arg->alock, LOCK_CANCEL | LOCK_V4);
- transmit4_result(NLM4_CANCEL_RES, &res, getrpcaddr(rqstp));
+ transmit4_result(NLM4_CANCEL_RES, &res,
+ (struct sockaddr *)svc_getcaller(rqstp->rq_xprt));
return (NULL);
}
@@ -1156,7 +1158,8 @@
res.stat.stat = unlock(&arg->alock, LOCK_V4);
res.cookie = arg->cookie;
- transmit4_result(NLM4_UNLOCK_RES, &res, getrpcaddr(rqstp));
+ transmit4_result(NLM4_UNLOCK_RES, &res,
+ (struct sockaddr *)svc_getcaller(rqstp->rq_xprt));
return (NULL);
}
@@ -1212,7 +1215,8 @@
res.stat.stat = lock_answer(arg->alock.svid, &arg->cookie,
nlm4_granted, NULL, NLM_VERS4) == 0 ?
nlm4_granted : nlm4_denied;
- transmit4_result(NLM4_GRANTED_RES, &res, getrpcaddr(rqstp));
+ transmit4_result(NLM4_GRANTED_RES, &res,
+ (struct sockaddr *)svc_getrpccaller(rqstp->rq_xprt)->buf);
return (NULL);
}
--
Jun Kuriyama <[EMAIL PROTECTED]> // IMG SRC, Inc.
<[EMAIL PROTECTED]> // FreeBSD Project
___
freebsd-
Re: wpa_supplicant with NDIS-wrapped wireless card and WPA-PSK reboots 6.1-pre
Fabian Keil wrote: Does it make a difference if you additionally put the bssid in /etc/wpa_supplicant.conf? No, it doesn't, but thanks for suggestion. I only use wep encryption and don't know if a failed attempt to associate with wpa_supplicant can cause a reboot, but it's worth a try. You should also check if you can associate to the (unencrypted) network with ifconfig by hand. Works just fine, it is a wpa_supplicant problem. Carlos ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
gmirror(8) and graid3(8) changes.
Hi. Here you can find patches with changes to gmirror(8) and graid3(8): http://people.freebsd.org/~pjd/patches/gmirror.7.patch http://people.freebsd.org/~pjd/patches/graid3.patch The patches does the following: - Significant synchronization speed improvement. Now many parallel synchronization I/O requests can be used instead of only one before. Many people requested this. - Close race between regular and synchronization requests (I wasn't able to trigger it with one sync request, but with many parallel requests it's real). - Reimplement locking. I moved softc synchronization from the topology lock to per-device sx lock. I'd like to ask gmirror/graid3 users to test those patches as much as possible, because I want to commit them to the HEAD and RELENG_6 branches. Because of locking changes it will be really good if you can turn on INVARIANTS, INVARIANT_SUPPORT options and eventually DIAGNOSTIC in your kernel. Thanks in advance! -- Pawel Jakub Dawidek http://www.wheel.pl [EMAIL PROTECTED] http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! pgpY3M9ZCC7Fw.pgp Description: PGP signature
Re: cvs commit: www/en/releases/6.1R todo.sgml
On Tue, Mar 07, 2006 at 05:46:54AM +0900, Hiroki Sato wrote: H> gl> Is it possible place kern/87208 into TODO list for 6.1-RELEASE? H> gl> The problem appeared to be a bad regression in 6.0-RELEASE, H> gl> that hurted many users. The PR contains several test cases, H> gl> description and patch for the problem. H> H> Thanks, added just now. Will this description do? Looks fine, thanks. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bash 3.1.10 breaks configure scripts (was Re: configure scripts ignores parameters)
On Sun, Mar 05, 2006 at 04:01:19AM -0500, Kris Kennaway wrote: > On Sun, Mar 05, 2006 at 09:57:54AM +0100, Nicolas Rachinsky wrote: > > * Kris Kennaway <[EMAIL PROTECTED]> [2006-03-05 03:41 -0500]: > > > On Sun, Mar 05, 2006 at 09:36:25AM +0100, Nicolas Rachinsky wrote: > > > > The problem seems to depend on the installed bison version. With no > > > > bison or bison-2.1_1 installed it works fine, with bison-1.75_2,1 it > > > > doesn't. > > > > > > Installed at what point: the build time of the bash port, or runtime > > > (which would be very odd)? > > > > The build time. I submitted ports/94086, which contains a > > fix/workaround. > > Great, thanks for tracking this down! Can others confirm this > solution? I have committed the patch, so this should go away next time you portupgrade. Kris pgp2rzAmJZ8b1.pgp Description: PGP signature
Re: RELENG_6: serial console drops back from 115200 to 9600 baud
At 04:19 PM 06/03/2006, Ian Dowse wrote: Presumably the boot loader (boot1/2) drops you at the prompt because it is old and does not understand the "-S115200". Once you update the boot blocks with disklabel, that /boot.config should work. I think I am almost there, but in my case, I get some strange char duplication after seeing the F1 prompt. The BIOS has console redirection, so I can see it throughout the bootup process. F1 FreeBSD Default: F1 //bbtt..ccoo- ffiigg:: --DDhh// BTX loader 1.00 BTX version is 1.01 Consoles:ointernal video/keyboardalserialiportoo//kkeeyybbooaarrdd sseerriiaaBIOSpdrivetA: is disk0 BIOSOdrivedC:risvdisk1AA:: iiss ddiisskk00 BIOSO638kB/504704kBeavailableimemoryiisskk11 BBIIOOSS 663388kkBB//550044770044kkBB aavvaaiillaabbllee mmeemmoorryy FreeBSD/i386 bootstrap loader, Revision 1.1 ([EMAIL PROTECTED],tSataMar 4l04:44:56rEST 2006)vviissiioonn LLoadingi/boot/defaults/loader.confauullttss//llooaaddeerr..ccoonnff a,, SSaat//boot/kernel/kerneletext=0x2e7378ddata=0x37d14+0x2ecf8ssyms=[0x4+0x3f8f0+0x4+0x513d4]dd44\\ \\\ If for some reason, boot.config is bogus, I can actually type in /boot/loader and it will load, just what I type is duplicated. I have # cat /boot/loader.conf #debug.acpi.disabled="sysresource" beastie_disable="YES" # Turn the beastie boot menu on and off comconsole_speed="19200" and # cat /boot.config -Dh -S19200 After hitting enter as I normally do, the rest of the boot process is normal looking and works fine /boot/kernel/acpi.koetext=0x42e34ddata=0x2280+0x10f0ssyms=[0x4+0x7ad0+0x4+0xa709]//a77009 Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.1-PRERELEASE #0: Sat Mar 4 07:20:49 EST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/gas Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: VIA C3 Nehemiah+RNG+ACE (796.77-MHz 686-class CPU) Origin = "CentaurHauls" Id = 0x698 Stepping = 8 Features=0x381b03f real memory = 517865472 (493 MB) avail memory = 497393664 (474 MB) ---Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: RELENG_6: serial console drops back from 115200 to 9600 baud
On Mar 6, 2006, at 4:19 PM, Ian Dowse wrote: There are a lot of steps to the boot process so it can be confusing - the command you wanted was disklabel, not boot0cfg. The boot0cfg program installs boot0, which is a 512-byte boot manager that you Yow. Thanks for the clarification. I guess 10 years of experience with running these boxes is just not enough :-( Perhaps UPDATING needs clarification as to which command to use to update boot blocks, because I'm *sure* it will bite others too. Thanks again. This was a very helpful post for me. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: RELENG_6: serial console drops back from 115200 to 9600 baud
In message <[EMAIL PROTECTED]>, Vivek Khera writes : > >On Feb 27, 2006, at 12:29 PM, Ed Maste wrote: >I'm not having any luck getting my 115200 baud serial console back. >The machine was upgraded from 5.4-STABLE to 6.1-PRE last week, and >again over the weekend. I did the following: > >make buildworld and buildkernel with BOOT_COMCONSOLE_SPEED=115200 in / >etc/make.conf, options CONSPEED=115200 in the kernel config. > >make installkernel, reboot, yada yada yada, installworld,.. then >boot0cfg -B aacd0 to update the boot blocks. > >Now, at this point I expected to have a 115200 console on the next >boot. Nope. Got 9600 baud again. There are a lot of steps to the boot process so it can be confusing - the command you wanted was disklabel, not boot0cfg. The boot0cfg program installs boot0, which is a 512-byte boot manager that you can optionally install in the MBR to give a menu of slices to boot from - it has nothing to do with reading /boot.config and doesn't set up the serial port. If the slice you boot from is aacd0s2 then you can use `disklabel -B aacd0s2' to install the new boot blocks (boot1 and boot2) into that slice. >The other side-effect is now I get this stupid "Boot F1 for DOS and >F2 for FreeBSD" menu which defaults to DOS (which is the Dell utility >partition). How do I get back to the original boot style where it >just boots freebsd without any menu? That's boot0. `fdisk -B /dev/aacd0' should put back the basic MBR. >So I updated my /boot.config to read: > > -Dh -S115200 > >now on boot, the boot0 drops to the prompt and makes me type in "/ >boot/loader" to continue the process. It is as if it forgot what >file to load, and ignores the -S option anyhow, because I still end >up with a 9600 baud console. Presumably the boot loader (boot1/2) drops you at the prompt because it is old and does not understand the "-S115200". Once you update the boot blocks with disklabel, that /boot.config should work. Ian ___ 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 nfs root troubles
On Mon, Mar 06, 2006 at 04:55:11PM +0600, sergey akifiev wrote: > On Mon, Mar 06, 2006 at 04:27:43AM -0500, Kris Kennaway wrote: > > After you have rebuilt your kernel, please post the panic (which may > > be different now), and do 'wh' at the prompt. > > i've added INVARIANTS* options to kernel, but trap looks exactly as before > (only IP register changed). > and i can't enter `where' command via serial cable attached, so i'll write it > by hands :-) > here we go: > db>wh > Tracing pid 1 tid 17 td 0xc0e2c480 > mountnfs(c0624b10,c0ecbc00,c0eb6c90,c315b8cc) at 0xc0533559 = mountnfs+0x139 > nfs_mountdiskless(c315b8f4,1,c0624bac,c0624b10,c0e2c480,c315b8cc,c0ecbc00,c05ddebc,c315b8f4) > at 0xc0532db9 = nfs_mountdiskless+0x39 > nfs_mountroot(c0ecbc00,c0e2c480,c05bc8b0,c315b9c4,0) at 0xc0532d1d = > nfs_mountroot+0x1cd > nfs_mount(c0ecbc00,c0e2c480,0,0,c0f57000) at 0xc053327b = nfs_mount+0x3b > vfs_domount(c0e2c480,c0ec9200,c0ec91f0,4001,c0ec9230) at 0xc04df4bc = > vfs_domount+0x5bc > vfs_donmount(c0e2c480,4001,c315bc24,c0ec1e80,6) at 0xc04ded4f = > vfs_donmount+0x2ef > kernel_mount(c0ec9240,4001,c315bc90,c315bcbc,c04e06c7) at 0xc04e11af = > kernel_mount+0x6f > kernel_vmount(4001,c05d7d49,c0ec9260,c05d7d50,c05ce4e1) at 0xc04e120b = > kernel_vmount+0x3b > vfs_mountroot_try(c05dd58e) at 0xc04e06c7 = vfs_mountroor_try+0xbf > vfs_mountroot(c0e3,c0e2c480,0,c315bd04,c315bcf8) at 0xc04e05bd = > vfs_mountroot+0xcd > start_init(0,c315bd38,0,c0467a60,0) at 0xc0467aab = start_init+0xa8 > fork_exit(c0467a60,0,c351bd38) at 0xc047c138 = fork_exit+0xa8 > fork_trampoline() at 0xc059bc3c = fork_trampoline+0x8 > --- trap 0x1, eip = 0, esp = 0xc315bd6c, ebp = 0 --- > db> > > uff, that was hell alot of typing :-) Thanks :) I netboot many machines on 6.1 and don't see this, so perhaps it it due to your use of the BOOTP* options: options BOOTP # Use BOOTP to obtain IP address/hostname # Requires NFSCLIENT and NFS_ROOT options BOOTP_NFSROOT # NFS mount root filesystem using BOOTP info options BOOTP_NFSV3 # Use NFS v3 to NFS mount root options BOOTP_COMPAT# Workaround for broken bootp daemons. Perhaps [EMAIL PROTECTED] is able to help (CC'ing). Kris pgpN711ga3QPA.pgp Description: PGP signature
Re: cvs commit: www/en/releases/6.1R todo.sgml
Gleb Smirnoff <[EMAIL PROTECTED]> wrote in <[EMAIL PROTECTED]>: gl> Is it possible place kern/87208 into TODO list for 6.1-RELEASE? gl> The problem appeared to be a bad regression in 6.0-RELEASE, gl> that hurted many users. The PR contains several test cases, gl> description and patch for the problem. Thanks, added just now. Will this description do? -- | Hiroki SATO pgp93rSswL0gH.pgp Description: PGP signature
Re: cvs commit: www/en/releases/6.1R todo.sgml
On Mon, Mar 06, 2006 at 06:59:07PM +, Hiroki Sato wrote: H> H> Modified files: H> en/releases/6.1R todo.sgml H> Log: H> Add new items: H> exec_map depletion, H> NFS data corruption between two 7.0 machines, H> panic in fxp driver, H> deadlock in vn_start_write() consumers, H> panic in bpf, H> devfs locking problem, H> pty leak, H> trap in cpu_ipi_selected() on sparc64, and H> rpc.lockd interoperability problems. Is it possible place kern/87208 into TODO list for 6.1-RELEASE? The problem appeared to be a bad regression in 6.0-RELEASE, that hurted many users. The PR contains several test cases, description and patch for the problem. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
vm_page_free: pindex(0), busy(0), PG_BUSY(0), hold(0) panic: vm_page_free: freeing free page
Got the attached panic + trace on a build server today when doing a parallel
buildworld.
Unread portion of the kernel message buffer:
vm_page_free: pindex(0), busy(0), PG_BUSY(0), hold(0)
panic: vm_page_free: freeing free page
Uptime: 2d20h44m8s
Dumping 1022 MB (2 chunks)
chunk 0: 1MB (159 pages) ... ok
chunk 1: 1022MB (261616 pages) 1006 990 974 958 942 926 910 894 878 862 846
830 814 798 782 766 750 734 718 702 686 670 654 638 622 606 590 574 558 542
526 510 494 478 462 446 430 414 398 382 366 350 334 318 302 286 270 254 238
222 206 190 174 158 142 126 110 94 78 62 46 30 14
#0 doadump () at pcpu.h:165
165 pcpu.h: No such file or directory.
in pcpu.h
(kgdb) bt
#0 doadump () at pcpu.h:165
#1 0xc064a012 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:399
#2 0xc064a2a8 in panic (fmt=0xc08aa63a "vm_page_free: freeing free page")
at /usr/src/sys/kern/kern_shutdown.c:555
#3 0xc07c7c2b in vm_page_free_toq (m=0xc1b6f330)
at /usr/src/sys/vm/vm_page.c:1023
#4 0xc07c7295 in vm_page_free (m=0xc1b6f330) at /usr/src/sys/vm/vm_page.c:403
#5 0xc07c4cd1 in vm_object_terminate (object=0xc57de630)
at /usr/src/sys/vm/vm_object.c:631
#6 0xc07c4bab in vm_object_deallocate (object=0xc57de630)
at /usr/src/sys/vm/vm_object.c:564
#7 0xc07c174e in vm_map_entry_delete (map=0xc518dce4, entry=0xc5110aa0)
at /usr/src/sys/vm/vm_map.c:2207
#8 0xc07c191b in vm_map_delete (map=0xc518dce4, start=3328910128,
end=3217031168) at /usr/src/sys/vm/vm_map.c:2300
#9 0xc07c197c in vm_map_remove (map=0xc518dce4, start=0, end=3217031168)
at /usr/src/sys/vm/vm_map.c:2319
#10 0xc0631fe3 in exit1 (td=0xc554d900, rv=0) at vm_map.h:211
#11 0xc06319ac in sys_exit (td=0xc554d900, uap=0x0)
at /usr/src/sys/kern/kern_exit.c:97
#12 0xc0825edb in syscall (frame=
{tf_fs = 59, tf_es = 59, tf_ds = 59, tf_edi = 0, tf_esi = 1, tf_ebp =
-1077944200, tf_isp = -278880924, tf_ebx = -1077941067, tf_edx = 134626912,
tf_ecx = 6, tf_eax = 1, tf_trapno = 12, tf_err = 2, tf_eip = 672758583, tf_cs
= 51, tf_eflags = 658, tf_esp = -1077944324, tf_ss = 59})
at /usr/src/sys/i386/i386/trap.c:981
#13 0xc0814d5f in Xint0x80_syscall () at
/usr/src/sys/i386/i386/exception.s:200
#14 0x0033 in ?? ()
Previous frame inner to this frame (corrupt stack?)
(kgdb) up
#1 0xc064a012 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:399
399 doadump();
(kgdb) up
#2 0xc064a2a8 in panic (fmt=0xc08aa63a "vm_page_free: freeing free page")
at /usr/src/sys/kern/kern_shutdown.c:555
555 boot(bootopt);
(kgdb) up
#3 0xc07c7c2b in vm_page_free_toq (m=0xc1b6f330)
at /usr/src/sys/vm/vm_page.c:1023
1023panic("vm_page_free: freeing free page");
(kgdb) inspect *m
$1 = {pageq = {tqe_next = 0xc1b4b330, tqe_prev = 0xc0966a60}, listq = {
tqe_next = 0xc1276878, tqe_prev = 0xc87de668}, left = 0x0,
right = 0xc210be98, object = 0x0, pindex = 0, phys_addr = 663449600, md = {
pv_list_count = 0, pv_list = {tqh_first = 0x0, tqh_last = 0xc1b6f35c}},
queue = 24, flags = 128, pc = 23, wire_count = 0, cow = 0, hold_count = 0,
act_count = 5 '\005', busy = 0 '\0', valid = 0 '\0', dirty = 0 '\0'}
(kgdb) up
#4 0xc07c7295 in vm_page_free (m=0xc1b6f330) at /usr/src/sys/vm/vm_page.c:403
403 vm_page_free_toq(m);
(kgdb) up
#5 0xc07c4cd1 in vm_object_terminate (object=0xc57de630)
at /usr/src/sys/vm/vm_object.c:631
631 vm_page_free(p);
(kgdb) inspect *p
Cannot access memory at address 0x0
(kgdb) inspect *object
$2 = {mtx = {mtx_object = {lo_class = 0xc08f26e4,
lo_name = 0xc08a966d "vm object",
lo_type = 0xc08aa45e "standard object", lo_flags = 4390912, lo_list = {
tqe_next = 0x0, tqe_prev = 0x0}, lo_witness = 0x0},
mtx_lock = 3310672128, mtx_recurse = 0}, object_list = {
tqe_next = 0xc63cd18c, tqe_prev = 0xc62d62b8}, shadow_head = {
lh_first = 0x0}, shadow_list = {le_next = 0x0, le_prev = 0xc82815d8},
memq = {tqh_first = 0xc1b6f330, tqh_last = 0xc1fb94e8}, root = 0xc210be98,
size = 8, generation = 13, ref_count = 0, shadow_count = 0, type = 0 '\0',
flags = 8584, pg_color = 27, paging_in_progress = 0,
resident_page_count = 6, backing_object = 0x0,
backing_object_offset = 20480, pager_object_list = {tqe_next = 0x0,
tqe_prev = 0x0}, handle = 0x0, un_pager = {vnp = {vnp_size = 512}, devp =
{
devp_pglist = {tqh_first = 0x200, tqh_last = 0x0}}, swp = {
swp_bcount = 512}}}
(kgdb) up
#6 0xc07c4bab in vm_object_deallocate (object=0xc57de630)
at /usr/src/sys/vm/vm_object.c:564
564 vm_object_terminate(object);
(kgdb) up
#7 0xc07c174e in vm_map_entry_delete (map=0xc518dce4, entry=0xc5110aa0)
at /usr/src/sys/vm/vm_map.c:2207
2207vm_object_deallocate(object);
(kgdb) up
#8 0xc07c191b in vm_map_delete (map=0xc518dce4, start=3328910128,
end=3217031168) at /usr/src/sys/vm/vm_map.c:2300
2300
Problems with AVM B1 PCMCIA card / card detection
Hi all, after upgrading my FreeBSD 6 gateway from 6-BETA2 to 6-RELEASE-p5, my AVM B1 PCMCIA active ISDN card stopped to work. When plugging the card in, all I see are these lines in dmesg: pccard0: Card has no functions! cbb0: PC Card card activation failed Additionaly, reading out the card's CIS information fails: <0>ianus[1001]:~# pccardc dumpcisfile /dev/pccard0.cis pccardc: CIS code read: Inappropriate ioctl for device Configuration data for file /dev/pccard0.cis I want to span the C4B driver over this card, but in order for that driver to hijack the card, it's necessary that it can detect it. This obviously does not work ... Any ideas? -- .''`. Martin Loschwitz Debian GNU/Linux developer : :' : [EMAIL PROTECTED][EMAIL PROTECTED] `. `'` http://www.madkiss.org/people.debian.org/~madkiss/ `- Use Debian GNU/Linux 3.1! See http://www.debian.org/ pgpIBpiTk92g0.pgp Description: PGP signature
Great job to all who work on FreeBSD!
[ sorry for the cross-post, but both "camps" deserve this message ] A hearty "thank you" to all FreeBSD developers and a job well done! I've been "out of the loop" on FreeBSD due to utter busy-ness on the job and at home (along with general apathy for being in front of a computer outside work) for about 2.5 years now. I decided to finally upgrade one of my boxes from 5.1-CURRENT to 6.2-BETA2 over the weekend. Everything went flawlessly and a few knobs set within rc.conf and make.conf and my box was totally functional, and fast! My hat's off to all developers, testers, etc. for the sacrifices you give to bring such great software to all of us! -Jr -- John Reynolds[EMAIL PROTECTED] DEG/SG Storage Components Division MS: CH6-332 Phone: 480-554-9092 Structural / Physical Design Engineering swec.ch.intel.com/~jreynold/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: RELENG_6: serial console drops back from 115200 to 9600 baud
On Feb 27, 2006, at 12:29 PM, Ed Maste wrote: Probably the "best" way is now -S in boot.config, since it means that you don't have to recompile and you only have to change it in one place. I'm not having any luck getting my 115200 baud serial console back. The machine was upgraded from 5.4-STABLE to 6.1-PRE last week, and again over the weekend. I did the following: make buildworld and buildkernel with BOOT_COMCONSOLE_SPEED=115200 in / etc/make.conf, options CONSPEED=115200 in the kernel config. make installkernel, reboot, yada yada yada, installworld,.. then boot0cfg -B aacd0 to update the boot blocks. Now, at this point I expected to have a 115200 console on the next boot. Nope. Got 9600 baud again. The other side-effect is now I get this stupid "Boot F1 for DOS and F2 for FreeBSD" menu which defaults to DOS (which is the Dell utility partition). How do I get back to the original boot style where it just boots freebsd without any menu? So I updated my /boot.config to read: -Dh -S115200 now on boot, the boot0 drops to the prompt and makes me type in "/ boot/loader" to continue the process. It is as if it forgot what file to load, and ignores the -S option anyhow, because I still end up with a 9600 baud console. I ran out of time to try setting the speed in /boot/loader.conf but I'm not expecting any miracles. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fresh install on gmirror'ed disks?
On Monday 06 March 2006 10:34, Patrick M. Hausen wrote: > Hi! > > On Mon, Mar 06, 2006 at 10:26:53AM -0300, JoaoBR wrote: > > > I did configure quite a few servers with soft-updates on all > > > partitions, when soft-updates were rather new and I was > > > excited about the performance gain and didn't know about > > > the possible problems with / - as I said, I never had a > > > single problem with that setup. > > > > softupdate except for / is the default I guess so you do not need to > > enable it > > It is the default _now_. I started using soft-updates when > you still needed to change some kernel files and recompile > to activate it at all. > > FreeBSD since 1.0 ;-) > well well, better to say nothing but this is freebsd-stable in 2006 ... :S João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fresh install on gmirror'ed disks?
On Sunday 05 March 2006 01:22, Mark Kirkwood wrote: > JoaoBR wrote: > > geom changed this complications definitely, using gmirror or gstripe > > commands is easy as copying a file. > > > > (Chuckles) - While I see your point, I see that Ralf E's article > discussing this very issue weighs in at about a page worth of > instructions for *each* of the two methods discussed. Now, sure, he's > being pedantically careful so no-one will misunderstand and murder their > systems - but ISTM that this is the sort of task that ideally an > installer could/should handle. > > The argument of 'its only a few commands...' does not really stand up - > as (for instance) it could be equally applied to that installer > providing package installation - and it seems to have that facility > (thankfully!). > good point, probably it is much easier as thought to integrate as script into the installer where one can chose the disks/partitions to gmirror/gstripe them and put it beside other options in "Startup Options" I never felt the need and probably would not use the option either and will configure my config manually later as I do with named or others > > So in comparism > > the easy use of geom is great and the people which developed geom did a > > really fantastic job. > > I agree, as the geom based applications are maturing, we are starting to > see that benefit of the geom infrastructure. > for me this happened already. I use gmirror for almost a year now and I changed all vinum setups and I never had a serious problem with it. I have to say that I never tried IDE or SATA, only SCSI with Adaptec. João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fresh install on gmirror'ed disks?
Hi! On Mon, Mar 06, 2006 at 10:26:53AM -0300, JoaoBR wrote: > > I did configure quite a few servers with soft-updates on all > > partitions, when soft-updates were rather new and I was > > excited about the performance gain and didn't know about > > the possible problems with / - as I said, I never had a > > single problem with that setup. > > softupdate except for / is the default I guess so you do not need to enable it It is the default _now_. I started using soft-updates when you still needed to change some kernel files and recompile to activate it at all. FreeBSD since 1.0 ;-) Regards, Patrick -- punkt.de GmbH Internet - Dienstleistungen - Beratung Vorholzstr. 25Tel. 0721 9109 -0 Fax: -100 76137 Karlsruhe http://punkt.de ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fresh install on gmirror'ed disks?
On Monday 06 March 2006 08:41, Patrick M. Hausen wrote: > AFAIK soft-updates don't put your root partition at risk _directly_. > You might run into problems, _if_ your root partition is rather > small, during installworld/installkernel. This is due to the > delayed freeing of data blocks when files are erased. > So your root partition might fill up even if there should be > plenty of space. > I believe that softupdates is usefull only for partitions where writing ocurres what normally is not the case on the root partition > This has _never_ happened to me, though. My root partitions are all > at least 128 M in size and /var is _always_ separate and /tmp is > a symlink to /var/tmp. > this is a good idea but not default, standard install suggest a small /tmp partition I guess what probably is even better if you expect lots of r/w on it > I did configure quite a few servers with soft-updates on all > partitions, when soft-updates were rather new and I was > excited about the performance gain and didn't know about > the possible problems with / - as I said, I never had a > single problem with that setup. softupdate except for / is the default I guess so you do not need to enable it João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fresh install on gmirror'ed disks?
Hello! On Fri, Mar 03, 2006 at 06:58:50PM -0800, George Hartzell wrote: > > http://ezine.daemonnews.org/200502/diskmirror.html > > > > When the mirror is up and running, cvsup, buildworld, buildkernel, > > installkernel, installworld, mergemaster, reboot, enjoy ;-) > > I think that the instructions in the above mentioned article mildly > incorrect in that they enable soft-updates when they newfs the root > partition. AFAIK soft-updates don't put your root partition at risk _directly_. You might run into problems, _if_ your root partition is rather small, during installworld/installkernel. This is due to the delayed freeing of data blocks when files are erased. So your root partition might fill up even if there should be plenty of space. This has _never_ happened to me, though. My root partitions are all at least 128 M in size and /var is _always_ separate and /tmp is a symlink to /var/tmp. I didn't notice that in Ralf's script, because I didn't copy it verbatim ;-) Just used it as a guid through the process. I did configure quite a few servers with soft-updates on all partitions, when soft-updates were rather new and I was excited about the performance gain and didn't know about the possible problems with / - as I said, I never had a single problem with that setup. Regards, Patrick -- punkt.de GmbH Internet - Dienstleistungen - Beratung Vorholzstr. 25Tel. 0721 9109 -0 Fax: -100 76137 Karlsruhe http://punkt.de ___ 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 nfs root troubles
On Mon, Mar 06, 2006 at 04:27:43AM -0500, Kris Kennaway wrote: > After you have rebuilt your kernel, please post the panic (which may > be different now), and do 'wh' at the prompt. i've added INVARIANTS* options to kernel, but trap looks exactly as before (only IP register changed). and i can't enter `where' command via serial cable attached, so i'll write it by hands :-) here we go: db>wh Tracing pid 1 tid 17 td 0xc0e2c480 mountnfs(c0624b10,c0ecbc00,c0eb6c90,c315b8cc) at 0xc0533559 = mountnfs+0x139 nfs_mountdiskless(c315b8f4,1,c0624bac,c0624b10,c0e2c480,c315b8cc,c0ecbc00,c05ddebc,c315b8f4) at 0xc0532db9 = nfs_mountdiskless+0x39 nfs_mountroot(c0ecbc00,c0e2c480,c05bc8b0,c315b9c4,0) at 0xc0532d1d = nfs_mountroot+0x1cd nfs_mount(c0ecbc00,c0e2c480,0,0,c0f57000) at 0xc053327b = nfs_mount+0x3b vfs_domount(c0e2c480,c0ec9200,c0ec91f0,4001,c0ec9230) at 0xc04df4bc = vfs_domount+0x5bc vfs_donmount(c0e2c480,4001,c315bc24,c0ec1e80,6) at 0xc04ded4f = vfs_donmount+0x2ef kernel_mount(c0ec9240,4001,c315bc90,c315bcbc,c04e06c7) at 0xc04e11af = kernel_mount+0x6f kernel_vmount(4001,c05d7d49,c0ec9260,c05d7d50,c05ce4e1) at 0xc04e120b = kernel_vmount+0x3b vfs_mountroot_try(c05dd58e) at 0xc04e06c7 = vfs_mountroor_try+0xbf vfs_mountroot(c0e3,c0e2c480,0,c315bd04,c315bcf8) at 0xc04e05bd = vfs_mountroot+0xcd start_init(0,c315bd38,0,c0467a60,0) at 0xc0467aab = start_init+0xa8 fork_exit(c0467a60,0,c351bd38) at 0xc047c138 = fork_exit+0xa8 fork_trampoline() at 0xc059bc3c = fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xc315bd6c, ebp = 0 --- db> uff, that was hell alot of typing :-) -- WBFH: -error IL2: =SB=error SGA16-RIPE ___ 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 nfs root troubles
On Mon, Mar 06, 2006 at 02:42:22PM +0600, sergey akifiev wrote: > currently i'm trying to setup diskless client, which netboots 6.1-PRERELEASE > kernel with help of etherboot. > i've built custom kernel with `sudo make -j4 buildkernel KERNCONF=DISKLESS > CPUTYPE=pentium-mmx -DNO_MODULES' and attached config. > kernell loads off tftp server fine, detecting devices, but traps, when trying > to mount root fs from nfs server. > i've managed to get copy of console messages, which i attach to this message. > any help appreciated. and... pls forgive my bad english :-) Try adding to your kernel options INVARIANTS options INVARIANT_SUPPORT > Trying to mount root from nfs: > NFS ROOT: 94.1.0.85:/usr/diskless > > > Fatal trap 18: integer divide fault while in kernel mode > instruction pointer = 0x20:0xc0542ca9 > stack pointer = 0x28:0xc315b7e0 > frame pointer = 0x28:0xc315b880 > code segment = base 0x0, limit 0xf, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 1 (swapper) > [thread pid 1 tid 17 ] > Stopped at 0xc0542ca9 = mountnfs+0x139:idivl %ecx,%eax > db> ~ After you have rebuilt your kernel, please post the panic (which may be different now), and do 'wh' at the prompt. Kris pgpFKAnDLtVjy.pgp Description: PGP signature
Re: "page fault" panices after upgrading 5.4-RELEASE to 6.0-RELEASE/6.1-PRERELEASE
Hello! On Mon, 6 Mar 2006, Pavel Gubin wrote: I've got some machine which is almost idle and works now almost only as dialup server. The problem was that this machine was very stable under 5.4-RELEASE, but after upgrading (via buildworld/installworld) to 6.0-RELEASE-p4 and then to 6.1-PRERELEASE (4 days ago) the machine panices (uptime from an hour to a day or two). I have one idea about this. You've said that machine acts as a dialup server. What kind of ppp do you use: kernel (devices ppp + process pppd) or user (devices tun + process ppp)? It seems to me that kernel ppp is seriously broken in RELENG_6, but I've never succeeded in getting a crashdump (my otherwise stable home machine just reboots from time to time when I use kernel ppp), so for now I've just switched to user ppp. Sincerely, Dmitry -- Atlantis ISP, System Administrator e-mail: [EMAIL PROTECTED] nic-hdl: LYNX-RIPE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
6.1-PRERELEASE nfs root troubles
currently i'm trying to setup diskless client, which netboots 6.1-PRERELEASE kernel with help of etherboot. i've built custom kernel with `sudo make -j4 buildkernel KERNCONF=DISKLESS CPUTYPE=pentium-mmx -DNO_MODULES' and attached config. kernell loads off tftp server fine, detecting devices, but traps, when trying to mount root fs from nfs server. i've managed to get copy of console messages, which i attach to this message. any help appreciated. and... pls forgive my bad english :-) -- WBFH: -error IL2: =SB=error SGA16-RIPE machine i386 cpu I486_CPU cpu I586_CPU cpu I686_CPU ident SERGEY hints "DISKLESS.hints"# Default places to look for devices. makeoptions DEBUG=-g# Build kernel with gdb(1) debug symbols options KDB options KDB_TRACE options DDB options DDB_NUMSYM options GDB options BOOTP # Use BOOTP to obtain IP address/hostname # Requires NFSCLIENT and NFS_ROOT options BOOTP_NFSROOT # NFS mount root filesystem using BOOTP info options BOOTP_NFSV3 # Use NFS v3 to NFS mount root options BOOTP_COMPAT# Workaround for broken bootp daemons. options HZ=1000 options SCHED_4BSD # 4BSD scheduler options INET# InterNETworking options FFS # Berkeley Fast Filesystem options MD_ROOT # MD is a potential root device options NFSCLIENT # Network Filesystem Client options NFS_ROOT# NFS usable as /, requires NFSCLIENT options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS# Pseudo-filesystem framework options GEOM_GPT# GUID Partition Tables. options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options COMPAT_FREEBSD5 # Compatible with FreeBSD5 options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV# install a CDEV entry in /dev options ADAPTIVE_GIANT # Giant mutex is adaptive. device isa device pci device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device vga # VGA video card driver device splash # Splash screen and screen saver support device sc device agp # support several AGP chipsets device npx device pmtimer device sio # 8250, 16[45]50 based serial ports device ppc device ppbus # Parallel port bus (required) device lpt # Printer device miibus # MII bus support device ed # NE[12]000, SMC Ultra, 3c503, DS8390 cards device loop# Network loopback device mem # Memory and kernel memory devices device io # I/O device device random # Entropy device device ether # Ethernet support device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" device bpf # Berkeley packet filter options DEVICE_POLLING Connected GDB: no debug ports present KDB: debugger backends: ddb KDB: current backend: ddb Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.1-PRERELEASE #15: Mon Mar 6 14:11:56 OMST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/DISKLESS Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Pentium/P54C (133.27-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping = 12 Features=0x1bf real memory = 16777216 (16 MB) avail memory = 11325440 (10 MB) Intel Pentium detected, installing workaround for F00F bug npx0: [FAST] npx0: on motherboard npx0: INT 16 interface cpu0 on motherboard pcib0: pcibus 0 on motherboard pci0: on pcib0 isab0: at device 7.0 on pci0 isa0: on isab0 pci0: at device 7.1 (no driver attached) pci0: at device 7.2 (no driver attached) pmtimer0 on isa0 orm0: at iomem 0xc-0xc7fff on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles,
