Re: help! 5.1 doesn't do the rc thing?
On Thu, Aug 07, 2003 at 07:26:28PM -0700, Charlie Schluting wrote: Ok, I found that /etc/rc.d/netif was missing. I moved the one from /usr/src/etc/rc.d into place, and I'm thinking that will fix it. I don't remember telling it NOT to move this file in mergemaster... Thanks to everyone who responded. --Charlie I had the problem a few days ago with exactly the same file. I solution was to cd /usr/src/etc/rc.d make install -- Without the userland, the kernel is useless. --inspired by The Tao of Programming ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: D-Link DGE-500T support
On Tue, Aug 05, 2003 at 08:49:50AM -0500, Nick H. - Network Operations wrote: I attempted to use a D-Link DGE-500T card this weekend on 5.1-RELEASE (and -CURRENT) with no success. It is unable to probe the device and find a proper driver for it. My question is: are there any plans currently to provide support for this card? If there is already support for it (which may be the case) then which driver is it using? I tried a GENERIC kernel with all the default drivers, but it diddnt work with them. I can eventually get dmesg output again, but I'd need to bring the server down to put the card back in. Any help is more than welcome. Thank you! This card's chipset is the NatSemi gigE chipset, which is supported by the nge(4) driver. However, as nge(4) cards are relatively uncommon, support is not enabled by default in the GENERIC kernel. You can load the if_nge module, however. kldload if_nge In fact, the only gigE chipset common enough to make it into GENERIC is the Broadcom, supported by bge(4). Regards, -- wca ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
[resolved] Re: help! 5.1 doesn't want to start my nic :)
Anyone know what's up with that? Can anyone give me the rundown on how/what FreeBSD does at boot time to start the network interface? Maybe something is supposed to be running that script, but isn't? Another missing script? Upon boot up, FreeBSD runs the /etc/rc script. Check that you have the latest rc script by comparing it with the one in /usr/src/etc. diff -u /etc/rc /usr/src/etc/rc There should be no differences between these files. You should also have the following rc* files in the /etc directory: # ls /etc/rc* /etc/rc /etc/rc.firewall6 /etc/rc.sendmail /etc/rc.subr /etc/rc.conf/etc/rc.firewall/etc/rc.resume /etc/rc.shutdown/etc/rc.suspend Also the /etc/rc.d directory should contain 145 scripts. Scot :-) Ah, yes. Thank you so much! It was the /etc/rc file. evilness. I told it not to move the new one in because it looked like it was just deleting my old one. Mergemaster is great, but if you don't know certian files need to change, it doesn't help much. I knew to be careful when I saw it wanted to give me a default passwd file, but I suppose I was too careful. Oh, btw, my /etc/rc.d/ has 115 files, but everything works. Strange. Thanks to everyone! --Charlie ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntop broken?
On Wed, 2003-08-06 at 22:39, Charlie Schluting wrote:
5BOn Wed, 6 Aug 2003, Kris Kennaway wrote:
On Wed, Aug 06, 2003 at 08:57:53AM -0700, Charlie Schluting wrote:
Howdy,
Running 5.0.
cvsup to 5.1 and retry. The package currently builds on a clean 5.1 system.
Kris
Interesting. So, I tried, and it deleted all my ports. I was using this:
*default host=cvsup10.FreeBSD.org
*default base=/usr
*default prefix=/usr
*default release=cvs
*default tag=RELENG_5_1
*default delete use-rel-suffix
*default compress
ports-base
ports-all
Any ideas? Thanks a bunch :)
Yes. Your tag for ports should be '.', so:
*default tag=.
not
*default tag=RELENG_5_1
There is no such animal and that is why it deleted all of your ports
instead of updating them. In addition, specifying 'ports-all' is
sufficient ('ports-base' is not needed unless you are only cvsup'ing
individual collections).
-Scott
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: busdma/scsi trm(4) related panic
Jon Kuster wrote:
On Wed, 2003-08-06 at 06:42, Scott Long wrote:
I know what the problem is and I'm working on a patch right now.
Scott
Excellent. I'll be happy to test it if needed.
Jon
Attached is an untested patch. Please let me know if it solves the
problem
Scott
Index: trm.c
===
RCS file: /home/ncvs/src/sys/dev/trm/trm.c,v
retrieving revision 1.12
diff -u -r1.12 trm.c
--- trm.c 1 Jul 2003 15:52:02 - 1.12
+++ trm.c 9 Aug 2003 06:45:05 -
@@ -2999,6 +2999,7 @@
{
u_int16_ti;
PSRBpSRB;
+ int error;
for (i = 0; i TRM_MAX_SRB_CNT; i++) {
pSRB = (PSRB)pACB-pFreeSRB[i];
@@ -3040,6 +3041,17 @@
pSRB-pNextSRB = NULL;
}
pSRB-TagNumber = i;
+
+ /*
+* Create the dmamap. This is no longer optional!
+*
+* XXX This is not freed on unload! None of the other
+* allocations in this function are either!
+*/
+ if ((error = bus_dmamap_create(pACB-buffer_dmat, 0,
+ pSRB-dmamap)) != 0)
+ return (error);
+
}
return (0);
}
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GEOM/vinum compatibility (was: vinum lock panic at startup-current)
In message [EMAIL PROTECTED], Greg 'groggy' Lehey writes: and it seems that vinum does not respect the D_NOGIANT flag which GEOM recently started setting. Probably because it didn't know about it. As I've said before, it would be nice to be informed about the changes you're making, particularly given your stated intention of doing no work on Vinum. I had the choice between supporting sos@ effort to de-Giantize ATA or wait for the non-maintainer of vinum to possibly react to his email so I chose the former as being more beneficial to the project. Could you please give details (privately if you want, but I think this could be of interest to other people too). See sys/fs/specfs/specfs_vnops.c, that is probably faster. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACPI battery state and resume not working on Inspiron 5150
On Thu, 2003-08-07 at 10:31, Kevin Oberman wrote: From: Joe Marcus Clarke [EMAIL PROTECTED] Date: Wed, 06 Aug 2003 16:01:37 -0400 Sender: [EMAIL PROTECTED] --=-MHp9eSkqmbnyoWl+2a1w Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Wed, 2003-08-06 at 15:56, Barney Wolff wrote: On Wed, Aug 06, 2003 at 03:31:01PM -0400, Joe Marcus Clarke wrote: ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.LPCB.BAT1._STA] (Node 0xc6137640), AE_NOT_EXIST =20 I would not expect BAT1 to exist unless you have 2 batteries installed. Ah, good point. However, I don't see any battery sysctls, and I do have at least one battery installed. As to resume, on my I5000 it takes almost a minute to come back from S3, but does eventually come back on a -current from 7/30. Thanks for the suggestion. I'll wait a bit longer. Well, I did some experimenting yesterday with the ACPI code on my IBM T30 and learned one thing...if you plan on suspending, you need to set a sleep delay. Before I set the delay I had some nasty problems because power went away immediately and the disk cache did not have a chance to flush (ouch!) and left the display where it should not be. I noticed that Windows XP has a delay of about 5 seconds. I set the sysctl and tried again and things went MUCH better. The suspend didn't leave the disk corrupt (whew!) and the display dropped to low resolution before the graphics was shut down and switched back on resume! My Radeon M7 even retained sync. Of course, the USB driver simply does not recover from a suspend on ACPI and this should be fixed before too long. Also, the backlight stays on making the suspend NVU (not very useful). But it is a huge improvement and adding a delay MAY help a lot of other laptop suspend/resume areas. Whether this will help th I5000 problems, I can't say, but it seems like suspend/resume is the most common show-stopper for ACPI on laptops, so it's worth a shot. If there is a trend that indicates that a short delay in suspending fixes a number of problems, the default delay should probably be modified from 0 to 4 or 5. I tried your suggestion, but this just prolonged the inevitable for 5 seconds. The laptop still remained dead to all input and no video after resume. Joe -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
RE: Best Known Methods for dual booting WinXP + -current
I use Grub to multi-boot XPpro, Linux FreeBSD. Had to use FFS filesystem since Grub doesn't support UFS. -Original Message- From: John Reynolds [mailto:[EMAIL PROTECTED] Sent: Thursday, August 07, 2003 3:10 PM To: [EMAIL PROTECTED] Subject: Best Known Methods for dual booting WinXP + -current hello all, Having had a positive experience thus far with 5.1-RELEASE and -current beyond that on one of the new boxes I recently built, it is now time to build up the dual-boot system (BSD for me, WinXP for the wife ;). I've read different reports (some from laptop users) about using the WinXP loader to boot FreeBSD and I've also read reports that people used the standard boot-easy to boot both (while even others using GRUB). Are there currently any issues with dual-booting 5.1-RELEASE and/or -current along with Windows XP (probably SP1)? This would be on the same physical disk. What do you other -current users who are faced with dual booting XP do for the most part? Thanks, -Jr -- John Jennifer Reynolds johnjen at reynoldsnet.org www.reynoldsnet.org Sr. Physical Design Engineer - WCCG/CCE PDE jreynold at sedona.ch.intel.com Running FreeBSD since 2.1.5-RELEASE. FreeBSD: The Power to Serve! Unix is user friendly, it's just particular about the friends it chooses. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Mozilla V1.3.1 crashing on FreeBSD 5.1-C (older cvsup level)
I deinstalled and reinstalled gtk12. That appears to have fixed this problem. Joe Marcus Clarke wrote: (mozilla-bin:62160): Gtk-WARNING **: A floating object was finalized. This means that someone called g_object_unref() on an object that had only a floating reference; the initial floating reference is not owned by anyone and must be removed with gtk_object_sink() after a normal reference is obtained with g_object_ref(). $ Could be a problem with your gtk12 port. You might try rebuilding it. I removed flashplugin-mozilla and installed flashpluginwrapper. The screen painted but when I put the mouse pointer in the flash window, it indicates the movie was not loaded. However, I'm not getting error messages/crashes, per se. I would remove the flashplugin-mozilla-0.4.10_2 package, and install www/flashpluginwrapper instead. I've picked up a different problem... When I try to click on links off of the historychannel web site (either javascript or to another html page) I get the following: mozilla-bin in free(): error: page is already free I cannot identify any pattern to this message but once it is issued, I have to control-C out of mozilla-gtk2 in the window I started it from. I have not found any other way to get out of the problem. Put another way, when I get this error, Mozilla is dead but control-C will get rid of the hung application. Cheers... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ath0 driver
In message: [EMAIL PROTECTED] David Gilbert [EMAIL PROTECTED] writes: : M == M Warner Losh [EMAIL PROTECTED] writes: : : M The ath driver doesn't work with broadcom hardware. You will need : M to write your own driver, or find someone else that can write a : M broadcom one for you. : : OK ... so slap me down... Geez. It certainly has been discussed that : the PCI vendor doesn't necessarily have anything to do with the : chipset. Simple question ... so many snarky answers. It is a frequently asked question, so maybe I've gotten a little snarky about it. Please accept my appoligies. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: LOR (vm_fault.c:286 and vm_kern.c:323)
On Thu, Aug 07, 2003 at 11:08:06PM -0500, Alan L. Cox wrote: Kris Kennaway wrote: I don't think I've seen this i386 traceback before. Is it harmless as well? Yes. In general, any LOR involving a system map mutex and a vm object mutex that has a stack trace looking like _mtx_lock_flags() _vm_map_lock() kmem_malloc() page_alloc() slab_zalloc() uma_zone_slab() uma_zalloc_internal() uma_zfree_arg() ... is not a problem. Thanks, I'll keep that in mind. Kris pgp0.pgp Description: PGP signature
Re: ipfw - default to accept + bootp = confusion.
On Thursday, August 7, 2003, at 12:22 AM, Juli Mallett wrote: Does someone have any idea what approach to take for the following scenario? I'm leaning towards a compile time failure, or an informative panic at the beginning of bootp... You have IPFIREWALL, but not the default to accept option, and you have BOOTP. The BOOTP stuff will fail in sosend with EACCESS (informatively printed as 13), because of IPFW, and this may be slightly non-obvious to people who haven't dealt with early ipfw interference before. If not compile time failure / panic, I'd say probably we want some way to notify a user in general of ipfw stopping pre-init operation, but I don't want to add the concept of runlevels, and don't know if there's anything there currently to do detection of if we've hit that point yet. If the default rule controlled by IPFIREWALL_DEFAULT_TO_ACCEPT, default_rule.cmd[0].opcode, were made accessible via a sysctl. then bootp could check it and produce an informative message. Or, if possible try to insert a rule into the kernel restrictive enough to be safe. On the one hand it's a firewall, and you don't want to be making assumptions about trust on behalf of the user. On the other hand, we just accepted a kernel from someone, and now want to get some data for a root partition, so if we cannot trust the host we're booting from, what's the point? Given the above, would it be possible, to embed a small function taking just a pair of addresses and masks, and use that to add a rule so that this process could continue? After using sysctl to verify the predicament, you could then try installing one (or a few) rules to trust the machines that are booting us. Trust the server running bootpd, trust the dchp and nfs server, or just trust the network+submask in a single rule. the following is just a rough guess from looking at ip_fw.c. I don't know how far off it is to being valid. s = socket(AF_INET, SOCK_RAW, IPPROTO_RAW); if (s 0) err(EX_UNAVAILABLE, socket); memset(rule, 0, sizeof rule); rule.fw_flg |= IP_FW_F_ACCEPT; rule.fw_prot = IPPROTO_IP; rule.fw_src = /* the bootp servers address rule.fw_smsk = ~0; /* Does all 1s mean just from that host? */ rule.fw_dst = /* Is our addr known yet? */ rule.fw_dmsk = ??; rule.fw_flg |= (IP_FW_F_OUT|IP_FW_F_IN); /* you could do both directions */ i = sizeof(rule); if (getsockopt(s, IPPROTO_IP, IP_FW_ADD, rule, i) == -1) err(EX_UNAVAILABLE, getsockopt(%s), IP_FW_ADD); Is any of this reasonable or I am just being naive? (I'm new here.) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mdconfig feature request
Tobias Roth wrote: You could do the vnode. Doing the path is hard. the vnode is good enough for me. would someone be so kind to implement that? Depends; what are you going to do, with only the address of a kernel structure? What's having that going to buy you? or will this still cause problems because the vnode file can actually be deleted (as stated below)? Again, it really depends on what the heck you are wanting to do with it once you have it. If you only want to print it out as a hex number on a little square of paper and carry it around as a good luck charm, won't any random hex number work for that? A better idea might be telling the list what problem is it that you are trying to solve, since we may already have a way of solving it. -- Terry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient problem with xl0
On Sat, 9 Aug 2003, Matthew N. Dodd wrote: Try this (cut paste): The patch I posted was incorrect as I forgot to do a register window select before reading media status. ftp://ftp.jurai.net/users/winter/patches/xl_media.patch -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: LOR in pcm
/-- Kris Kennaway wrote: | | LORs in the pcm system are reported quite regularly, but I haven't | seen anyone working on the problem. Is there anyone who can look at | the locking code used in this system and fix the problems? Perhaps | this should be added to the 5.2 TODO list. | =20 I'm unaware of anybody chasing this though I'm not very closely involved with [EMAIL PROTECTED] these days. Last I knew cg was focusing his energies on a new freebsd sound architecture to better cater for modern audio h/w. If somebody was interested in taking this issue on, it would be of immediate benefit to the project. Regards - Orion ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mdconfig feature request
In message [EMAIL PROTECTED], Tobias Roth writes: would it be possible to add the currently attached vnode (or the complete path to it) to the output of mdconfig -l -u devicenumber that would simplify some things for me. That is actually somewhat tricky because the file might have been renamed or have multiple names. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient problem with xl0
On Sat, Aug 09, 2003 at 12:28:45PM +0200, Martin Blapp wrote: Hi, Here is the output of dhclient -v -d xl0 I I checked. Dhclient still initializes the interface and brings it up itself. So there is only one possibility: You don't have a working link. Maybe it helps if you add a interface define in /etc/dhclient.conf wit the possible media. Hmmm, I am not sure about this, since if I use the old dhclient binary, it works fine without problems. Here is the output if 'ifconfig xl0': xl0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=8VLAN_MTU inet6 fe80::260:97ff:fe72:adf0%xl0 prefixlen 64 scopeid 0x2 inet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255 ether 00:60:97:72:ad:f0 media: Ethernet 10baseT/UTP (10baseT/UTP half-duplex) -- Craig Rodrigues http://crodrigues.org [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntop broken?
On Thu, 2003-08-07 at 00:39, Charlie Schluting wrote: Any ideas? Thanks a bunch :) try this instead: *default host=cvsup.no.freebsd.org *default base=/usr *default prefix=/usr *default tag=RELENG_5_1 *default release=cvs delete use-rel-suffix compress ports-all tag=. src-all doc-all -- Med Vennlig Hilsen / Best regards Christer Gundersen / dizzy tun3Z http://dtz.cjb.net - http://carebears.mine.nu Early to rise and early to bed makes a male healthy and wealthy and dead. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Invalid partition table error when creating more than one sliceduring install?
I'm trying to get 5.1-R installed, but I've run into a problem I don't understand. The disk layout I want should look like this: s1: 20gb, FreeBSD s2: 10gb, Windows s3: ~83gb (the rest of the disk), data The partition, label, and install process all seems to work fine. However, when I reboot, rather than beginning the bootstrap, the machine halts with the error Invalid partition table. If I install with just s1, it works fine. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACPI battery state and resume not working on Inspiron 5150
From: David Gilbert [EMAIL PROTECTED] Date: Sat, 9 Aug 2003 20:53:54 -0400 What does a hibernation partition look like? My dell has a 31 meg partition that I havn't touched and my FreeBSD partition. Most laptops have the capability of sleeping in two modes. 1. suspend where most of the system is powered off, but the memory is kept on so that the system can pick up right where it left off (except for drivers re-initing hardware) when the system is resumed. 2. Hibernate where the contents of memory and some system registers are written ti a pore-allocated space on disk, usually a dedicated partition. The boot is then tagged that the hibernation partition is active and the systems is power completely off. On powering up, the BIOS will detect that i=the system was in hibernation and reload the memory and registers and resuming where the system left off. Hardware must still be re-initialized and it's up to the drivers to handle this. Suspend is faster, but continues limited battery drain. Hibernation takes a while to stop and start and requires a dedicated partition (slice), but the system is totally off while in hibernation. I don't know if all laptops support both, but every one I have used does. IBM has a stand-alone tool on it's web site that creates a hibernation partition on ThinkPads (which I use). You probably need to check with the manufacturer of your system to see what is available. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
dhclient problem with xl0
Hi, I just did a cvsup of -CURRENT and rebuilt the world. dhclient doesn't seem to work for me any more. It looks like a problem with dhclient, and not the kernel, because an older version of dhclient works fine. Here is the output of dhclient -v -d xl0 == Script started on Sat Aug 9 03:11:38 2003 Internet Software Consortium DHCP Client V3.0.1rc11 Copyright 1995-2002 Internet Software Consortium. All rights reserved. For info, please visit http://www.isc.org/products/DHCP Listening on BPF/xl0/00:60:97:72:ad:f0 Sending on BPF/xl0/00:60:97:72:ad:f0 Sending on Socket/fallback xl0: Polling interface state xl0: client state of 2 xl0: link = 0 xl0: No Link on interface xl0: Polling interface state xl0: client state of 2 xl0: link = 0 xl0: No Link on interface xl0: Polling interface state xl0: client state of 2 xl0: link = 0 xl0: No Link on interface xl0: Polling interface state xl0: client state of 2 xl0: link = 0 xl0: No Link on interface xl0: Polling interface state xl0: client state of 2 xl0: link = 0 xl0: No Link on interface Script done on Sat Aug 9 03:12:04 2003 == -- Craig Rodrigues http://crodrigues.org [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: another buildworld -j4 panic
On Thu, 2003-08-07 at 22:36, Mike Silbersack wrote: ok, here goes: duplicate free from zone FFS1 dinode traceback: Debugger panic uma_dbg_free uma_zfree_arg ffs_ifree ufs_reclaim ufs_vnoperate vclean gdonel getnewvnode ffs_vget ufs_lookup ufs_vnoperate vfs_cache_lookup ufs_vnoperate lookup namei stat syscall Xint0x80_syscall Whee! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] IS it possible for you to duplicate without the -j4? like a simple make buildworld? Your I/O controller maybe not able to keep up. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
