Re: "Shutdown -p now" not working in 5.4 STABLE
Hi Mike! If you still manage this puzzle, is there something in your bios that affects 5.4 and not 5.1? Must be "power" menue with apm and other stuff. Acpi is on and should take the whole process for you. Best regards Zoran ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 6.0-BETA2 Available
On Fri, 5 Aug 2005, Kevin Oberman wrote: Date: Fri, 5 Aug 2005 21:08:50 -0300 (ADT) From: "Marc G. Fournier" <[EMAIL PROTECTED]> Sender: [EMAIL PROTECTED] How/where should we be reporting such bugs? I reported a *very* easy to reproduce hang situation with unionfs in BETA1 (and have updated/retested as I see commits going through) over a week ago, and the biggest 'interest' I got out of it was from Robert Watson giving me suggestions on other stuff to provide :( I would suggest that it would have been better to post to current as 6.0 is not yet stable and most of the people who deal with problems are much more likely to see problems reported there. You also might open a PR. I did that, actually, even posted a followup to the PR after I found the vfs.uniondebug sysctl option and got a trace of that too ... even posted to -fs, just in case anyone over there wanted to look at it ... hadn't thought of -current, but will repost to there too ... Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 6.0-BETA2 Available
> Date: Fri, 5 Aug 2005 21:08:50 -0300 (ADT) > From: "Marc G. Fournier" <[EMAIL PROTECTED]> > Sender: [EMAIL PROTECTED] > > > How/where should we be reporting such bugs? I reported a *very* easy to > reproduce hang situation with unionfs in BETA1 (and have updated/retested > as I see commits going through) over a week ago, and the biggest > 'interest' I got out of it was from Robert Watson giving me suggestions on > other stuff to provide :( I would suggest that it would have been better to post to current as 6.0 is not yet stable and most of the people who deal with problems are much more likely to see problems reported there. You also might open a PR. -- 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 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 6.0-BETA2 Available
How/where should we be reporting such bugs? I reported a *very* easy to reproduce hang situation with unionfs in BETA1 (and have updated/retested as I see commits going through) over a week ago, and the biggest 'interest' I got out of it was from Robert Watson giving me suggestions on other stuff to provide :( On Fri, 5 Aug 2005, Ken Smith wrote: Announcement The FreeBSD Release Engineering Team is pleased to announce the availability of FreeBSD 6.0-BETA2. Because suitable pre-build packages are not widely available (see the Known Issues section below) BETA2 only has disc1 and bootonly ISOs available, and there are no FTP install trees. We encourage people to help with testing so any final bugs can be identified and worked out. Availability of ISO images is given below. If you have an older system you want to update using the normal CVS/cvsup source based upgrade the branch tag to use is RELENG_6 (though that will change for the Release Candidates later). Problem reports can be submitted using the send-pr(1) command. The list of open issues and things still being worked on are on the todo list: http://www.freebsd.org/releases/6.0R/todo.html Since this is the first release of a new branch we only have a rough idea for some of the dates. The current rough schedule is available but most dates are still listed as "TBD - To Be Determined": http://www.freebsd.org/releases/6.0R/schedule.html Known Issues Prebuilt packages are not available at this time due to the recent bump of shared library version numbers. The installation procedure will fail to install things normally present as packages (e.g. perl). There is a full ports tree available so you can build anything you want to use from that. Availability The BETA2 ISOs are available on most of the FreeBSD Mirror sites. A list of the mirror sites is available here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html The MD5s are: MD5 (6.0-BETA2-alpha-bootonly.iso) = 800d6bf84642ade264fce2594b783136 MD5 (6.0-BETA2-alpha-disc1.iso) = 12cbc4fbf616a8a6c70184aaa3e389a4 MD5 (6.0-BETA2-amd64-bootonly.iso) = 4e027ebc30157677464e8a4766d6f924 MD5 (6.0-BETA2-amd64-disc1.iso) = 2e54efd31dc63dadf5b68b4345233611 MD5 (6.0-BETA2-i386-bootonly.iso) = 70129bbc9e490836de7544230b6bc6fb MD5 (6.0-BETA2-i386-disc1.iso) = 3b1917c8143cbc99b22fc50e405c710f MD5 (6.0-BETA2-ia64-bootonly.iso) = 60a277555ae190b30113cd2fab9a3d64 MD5 (6.0-BETA2-ia64-disc1.iso) = a89acc0a1493b8c4d3786ddef33bdf42 MD5 (6.0-BETA2-ia64-livefs.iso) = 85d0f5d14d0e8b1697aa2c4dcdf73f68 MD5 (6.0-BETA2-pc98-disc1.iso) = bfca0ea211c1f977204b9677720289db MD5 (6.0-BETA2-sparc64-bootonly.iso) = a79dae4b17b14dda908b84ac388a411b MD5 (6.0-BETA2-sparc64-disc1.iso) = 6aaefe58e249057d4b7d2418ec1c52c5 -ken Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.4 Installer + Promise FT100TX2 = Loader crash
Daniel O'Connor wrote: > Hi, > I am updating an old 4.x system to 5.4 here and it has a Promise FT100TX2 > RAID > controller (in mirror). > > The problem is that when I boot the CD the loader crashes (does a reg dump) > but only if the card is present and an array is defined. I can't record what > the dump is because it continually sprays the dump down the screen which > makes it unreadable :( > > I have seen this on an AMD64 system (I used the same RAID card in it) and got > the same problem. To work around it on that system I installed via the > motherboard IDE controller and then moved the disk over to the RAID > controller. > > It only seems to affect booting the installer - once the system is installed > it boots from the RAID card just fine (!) > > I just tried booting from floppy and that works (?!) although that method > doesn't probe my PS/2 keyboard for some reason :-/ > > Does anyone have any suggestions for fixing the RAID + CD boot problem? > > Thanks. > I've exactly the same issue: on a PIII866, only one IDE CD, Floppy and a RAID1 array on the FT100TX2, no way to boot on the CD... It works with there are no array on the card. (No array defined, Ctrl-F for bios or to continue). -> I just installed on 'ad4'(prim. master from raid card) disk, edited fstab to mount ar0 instead of ad4, then build (on the card's bios) a raid1 with ad6(long time copying...), then it boots from the raid. Still not from a FreeBSD5.4 RELEASE CD, nor a FreeSBIE 1.1 (based on 5.3). I can do some tests if needed, even if I'm don't really understand more than 'hello world', I know how to apply patches ;) -- --- / Geoffroy DESVERNAY| \ /`Service info` | Tel: (+33|0)4 91 05 45 24 \ \ Ecole Généraliste d'Ingénieurs| Fax: (+33|0)4 91 05 45 98 / \ ...de MARSEILLE | dgeo _AT_ egim-mrs.fr/ --- smime.p7s Description: S/MIME Cryptographic Signature
5.4-STABLE panic in propagate_priority() and a tentative patch
Hi,
We saw several panics of the same kind on different systems running
5.4-STABLE. The panic was in propagate_priority() and was ultimately
traced to vget() call in pfs_vncache_alloc(). vget() is called under
global pfs mutex. When vget() sleeps,
propagate_priority() in a different thread comes across a sleeping
thread that owns a blocked mutex, and that causes a panic.
a tentative patch for 5.4-STABLE is below. In addition to a fix for
panic, it includes
changes to switch to LIST_*() macros instead of directly manipulating
queue pointers.
I'd be most interested to hear opinion of people experienced with vfs
whether this patch is suitable or what problems they see with it.
In order to apply it to 6.0, I think it might be sufficient to
uncomment XXX-- comments, but I hadn't checked that: the patch also
includes some 6.0 fixes from Isilon backported to 5.4, and some of those
depend on other 6.0 vfs changes and will fail on 5.4 so they are
partially commented out to make it work on 5.4.
Best,
Garry
--- pseudofs_internal.h 23 Dec 2004 00:36:09 - 1.1
+++ pseudofs_internal.h 5 Aug 2005 20:50:42 - 1.2
@@ -43,8 +43,9 @@
struct pfs_node *pvd_pn;
pid_tpvd_pid;
struct vnode*pvd_vnode;
- struct pfs_vdata*pvd_prev, *pvd_next;
+LIST_ENTRY(pfs_vdata) pvd_link;
};
+
/*
* Vnode cache
--- pseudofs_vncache.c 23 Dec 2004 00:36:09 - 1.1
+++ pseudofs_vncache.c 5 Aug 2005 20:50:42 - 1.2
@@ -38,6 +38,7 @@
#include
#include
#include
+#include
#include
#include
@@ -45,7 +46,8 @@
static MALLOC_DEFINE(M_PFSVNCACHE, "pfs_vncache", "pseudofs vnode cache");
static struct mtx pfs_vncache_mutex;
-static struct pfs_vdata *pfs_vncache;
+static LIST_HEAD(, pfs_vdata) pfs_vncache_list =
+LIST_HEAD_INITIALIZER(&pfs_vncache_list);
static eventhandler_tag pfs_exit_tag;
static void pfs_exit(void *arg, struct proc *p);
@@ -106,6 +108,7 @@
struct pfs_node *pn, pid_t pid)
{
struct pfs_vdata *pvd;
+struct vnode *vnp;
int error;
/*
@@ -113,10 +116,10 @@
* XXX linear search is not very efficient.
*/
mtx_lock(&pfs_vncache_mutex);
- for (pvd = pfs_vncache; pvd; pvd = pvd->pvd_next) {
+LIST_FOREACH(pvd, &pfs_vncache_list, pvd_link) {
if (pvd->pvd_pn == pn && pvd->pvd_pid == pid &&
pvd->pvd_vnode->v_mount == mp) {
- if (vget(pvd->pvd_vnode, 0, curthread) == 0) {
+ if (vget(pvd->pvd_vnode, LK_NOWAIT, curthread)
== 0) {
++pfs_vncache_hits;
*vpp = pvd->pvd_vnode;
mtx_unlock(&pfs_vncache_mutex);
@@ -127,6 +130,20 @@
return (0);
}
/* XXX if this can happen, we're in trouble */
+/* the vnode is being cleaned.
+ * need to wait until it's gone
+ */
+ vnp = pvd->pvd_vnode;
+vhold(vnp);
+ mtx_unlock(&pfs_vncache_mutex);
+/*XXX-- VOP_LOCK(vnp, LK_EXCLUSIVE, curthread); */
+if (vget(vnp, 0, curthread) == 0) {
+/* XXX shouldn't happen. */
+vrele(vnp);
+}
+/*XXX-- VOP_UNLOCK(vnp, 0, curthread); */
+vdrop(vnp);
+ mtx_lock(&pfs_vncache_mutex);
break;
}
}
@@ -135,8 +152,6 @@
/* nope, get a new one */
MALLOC(pvd, struct pfs_vdata *, sizeof *pvd, M_PFSVNCACHE,
M_WAITOK);
- if (++pfs_vncache_entries > pfs_vncache_maxentries)
- pfs_vncache_maxentries = pfs_vncache_entries;
error = getnewvnode("pseudofs", mp, pfs_vnodeop_p, vpp);
if (error) {
FREE(pvd, M_PFSVNCACHE);
@@ -176,12 +191,13 @@
if ((pn->pn_flags & PFS_PROCDEP) != 0)
(*vpp)->v_vflag |= VV_PROCDEP;
pvd->pvd_vnode = *vpp;
+
mtx_lock(&pfs_vncache_mutex);
- pvd->pvd_prev = NULL;
- pvd->pvd_next = pfs_vncache;
- if (pvd->pvd_next)
- pvd->pvd_next->pvd_prev = pvd;
- pfs_vncache = pvd;
+
+LIST_INSERT_HEAD(&pfs_vncache_list, pvd, pvd_link);
+ if (++pfs_vncache_entries > pfs_vncache_maxentries)
+ pfs_vncache_maxentries = pfs_vncache_entries;
+
mtx_unlock(&pfs_vncache_mutex);
(*vpp)->v_vnlock->lk_flags |= LK_CANRECURSE;
vn_lock(*vpp, LK_RETRY | LK_EXCLUSIVE, curthread);
@@ -199,15 +215,10 @@
mtx_lock(&pfs_vncache_mutex);
pvd = (struct pfs_vdata *)vp->v_data;
KASSERT(pvd != NULL, ("pfs_vncache_free(): no vnode data\n"));
- if (
Re: ``shutdown -p now'' not working in 5.4 STABLE
On Fri, 2005-08-05 at 16:03 -0400, Garance A Drosihn wrote: > At 8:43 PM -0700 8/4/05, Mike Eubanks wrote: > >On Thu, 2005-08-04 at 19:14 -0400, Garance A Drosihn wrote: > > > > >> Hmm. The more I think about this, the more I think I tripped > >> across something similar once. I think it was something like > >> I turned on 'APM' somewhere, or I added it to my kernel, or > > > something. For power-down, you need to be using ACPI, not APM. > >> But from your dmesg output, it looks like you are using ACPI, > > > so I am probably not helping much with that guess either. > > > >Ok, I built APM into the kernel and gave it a few tries, fiddling > >with different things. > > Sorry, my comments were not as clear as they should have been. > What I meant is that my problem was *caused* by adding APM into > the mix, when it should not have been there. That's what I > meant by: For power-down, you need to be using ACPI, not APM. > > But all of this is just vague memory anyway. I haven't had any > problems with my machines powering down for quite awhile now. > (through many different system builds...) > Garance, That's ok. I figured it wouldn't hurt to give it a try anyway. I am currently rebuilding it. I've never had a problem quite like this one. Evidence for problem seems to be inconsistent in the fact that it works fully on one version, and sometimes on the other. In the end, I fear my install is the only thing questionable at this point when considering the other dual-Athlon 5.4 system operates without a problem. Thanks again -- Mike Eubanks <[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: ``shutdown -p now'' not working in 5.4 STABLE
On Fri, 2005-08-05 at 12:29 +0200, Owe Jørgensen wrote: > Mike Eubanks wrote: > > >On Thu, 2005-08-04 at 14:21 -0700, J. Nyhuis wrote: > > > > > >>Wouldn't you want a -h for "halt" to prevent it from powering back > >>up? > >> > >>Thanks, > >> > >>John H. Nyhuis > >>Sr. Computer Specialist > >>Dept. of Pediatrics > >>HS RR349B, Box 356320 > >>University of Washington > >>Desk: (206)-685-3884 > >>[EMAIL PROTECTED] > >> > >>On Thu, 4 Aug 2005, Garance A Drosihn wrote: > >> > >> > >> > >>>At 1:32 PM -0700 8/4/05, Mike Eubanks wrote: > >>> > >>> > I have finished migrating my system from 5.1-RELEASE to 5.4-STABLE. > The system no longer powers down using either the `shutdown -p now' > or `acpiconf -s 5' commands. Instead it always restarts. > > > >>>This won't help much, but I have a system running 5.4-STABLE as of > >>>Thu Jul 28, and `shutdown -p now' works on that. Dual-athlon. > >>> > >>>-- > >>>Garance Alistair Drosehn= [EMAIL PROTECTED] > >>>Senior Systems Programmer or [EMAIL PROTECTED] > >>>Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] > >>> > >>> > > > > > >Yeah, the `-h' option does halt the system. The system does not power > >down though as it should with `-p' (halt and power down). > > > > > > > > > I guess it would be more healthy for the system and your fitness if you > reached down and turned it off manually after a shutdown -h :-) Right you are. Once the machine is being used, though, I will need one arm that is at least 240 miles in length and rippling back muscles to carry the weight of my arm. :-) -- Mike Eubanks <[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: ``shutdown -p now'' not working in 5.4 STABLE
At 8:43 PM -0700 8/4/05, Mike Eubanks wrote: On Thu, 2005-08-04 at 19:14 -0400, Garance A Drosihn wrote: > Hmm. The more I think about this, the more I think I tripped across something similar once. I think it was something like I turned on 'APM' somewhere, or I added it to my kernel, or > something. For power-down, you need to be using ACPI, not APM. But from your dmesg output, it looks like you are using ACPI, > so I am probably not helping much with that guess either. Ok, I built APM into the kernel and gave it a few tries, fiddling with different things. Sorry, my comments were not as clear as they should have been. What I meant is that my problem was *caused* by adding APM into the mix, when it should not have been there. That's what I meant by: For power-down, you need to be using ACPI, not APM. But all of this is just vague memory anyway. I haven't had any problems with my machines powering down for quite awhile now. (through many different system builds...) -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
error when trying to log into gnome
Hi Everyone, This is my first time ever asking a question on here so bare with me if I make any mistakes. I have a 5.4 system that was working great with gnome and I was trying to install word perfect from linux from the cd and I rebooted and now I am not able to log into a gnome session. When I try to log in xdm restarts and I am back at the login prompt. I looked at my .xsession-errors file and noticed the following: here is my .xsession file by the way also: #!/bin/sh /usr/X11R6/bin/gnome-session $ /usr/X11R6/bin/gnome-session My .xsession-errors states the following: /libexec/ld-elf.so.1: /usr/lib/libSM.so.6: Undefined symbol "_IO_stderr_" Any suggestions on how I might remedy the problem? Thanks Chris Arthur ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD 6.0-BETA2 Available
Announcement The FreeBSD Release Engineering Team is pleased to announce the availability of FreeBSD 6.0-BETA2. Because suitable pre-build packages are not widely available (see the Known Issues section below) BETA2 only has disc1 and bootonly ISOs available, and there are no FTP install trees. We encourage people to help with testing so any final bugs can be identified and worked out. Availability of ISO images is given below. If you have an older system you want to update using the normal CVS/cvsup source based upgrade the branch tag to use is RELENG_6 (though that will change for the Release Candidates later). Problem reports can be submitted using the send-pr(1) command. The list of open issues and things still being worked on are on the todo list: http://www.freebsd.org/releases/6.0R/todo.html Since this is the first release of a new branch we only have a rough idea for some of the dates. The current rough schedule is available but most dates are still listed as "TBD - To Be Determined": http://www.freebsd.org/releases/6.0R/schedule.html Known Issues Prebuilt packages are not available at this time due to the recent bump of shared library version numbers. The installation procedure will fail to install things normally present as packages (e.g. perl). There is a full ports tree available so you can build anything you want to use from that. Availability The BETA2 ISOs are available on most of the FreeBSD Mirror sites. A list of the mirror sites is available here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html The MD5s are: MD5 (6.0-BETA2-alpha-bootonly.iso) = 800d6bf84642ade264fce2594b783136 MD5 (6.0-BETA2-alpha-disc1.iso) = 12cbc4fbf616a8a6c70184aaa3e389a4 MD5 (6.0-BETA2-amd64-bootonly.iso) = 4e027ebc30157677464e8a4766d6f924 MD5 (6.0-BETA2-amd64-disc1.iso) = 2e54efd31dc63dadf5b68b4345233611 MD5 (6.0-BETA2-i386-bootonly.iso) = 70129bbc9e490836de7544230b6bc6fb MD5 (6.0-BETA2-i386-disc1.iso) = 3b1917c8143cbc99b22fc50e405c710f MD5 (6.0-BETA2-ia64-bootonly.iso) = 60a277555ae190b30113cd2fab9a3d64 MD5 (6.0-BETA2-ia64-disc1.iso) = a89acc0a1493b8c4d3786ddef33bdf42 MD5 (6.0-BETA2-ia64-livefs.iso) = 85d0f5d14d0e8b1697aa2c4dcdf73f68 MD5 (6.0-BETA2-pc98-disc1.iso) = bfca0ea211c1f977204b9677720289db MD5 (6.0-BETA2-sparc64-bootonly.iso) = a79dae4b17b14dda908b84ac388a411b MD5 (6.0-BETA2-sparc64-disc1.iso) = 6aaefe58e249057d4b7d2418ec1c52c5 -ken pgpUzxbjCJNAX.pgp Description: PGP signature
ggatec+gmirror
Hi, all!
I can't use in my script this variant:
ggate=`sbin/ggatec ${ggatec_flags}`
/sbin/gmirror insert ${mirror} ${ggate}
I have to use:
/sbin/ggatec ${ggatec_flags} > /dev/null
ggate=`/sbin/ggatec list`
/sbin/gmirror insert ${mirror} ${ggate}
Think in $ggate I get father-process STDOUT, but device name return child
STDOUT.
Is it correct behaviour?
$ uname -rs
FreeBSD 5.4-RELEASE-p5
By.
Dmitriy
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
AntiVir ALERT [your mail: "DELIVERY REPORTS ABOUT YOUR E-MAIL"]
* * * * * * * * * * * * * * * AntiVir ALERT * * * * * * * * * * * * * * * This version of AntiVir is licensed and full featured. AntiVir has detected the following in a mail from your address: Worm/Mydoom.M The mail was not delivered. Please remove any potential malicious software from your computer before sending a new mail with attachments. Mail-Info: --8<-- From: freebsd-stable@freebsd.org To: [EMAIL PROTECTED] Date: Fri, 5 Aug 2005 14:32:31 +0200 Subject: DELIVERY REPORTS ABOUT YOUR E-MAIL --8<-- -- AntiVir for UNIX Copyright (C) 1994-2003 by H+BEDV Datentechnik GmbH. All rights reserved. For more information see http://www.antivir.de/ or http://www.hbedv.com/ ___ 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 has problems with booting
I still experience hangs with RELENG_6. Today I though I give it another try. I used a fresh cvsup of RELENG_6. After rm -rf /usr/obj* && make clean && make cleandir && make buildworld && make buildkernel && make install kernel I rebooted into single user mode in order to install the world and execute mergemaster. Even in single user mode the machine will hang after some minutes. I have no problems with RELENG_5. See my other mails in this thread for a verbose dmesg. Any hints on that? Greets, Jonathan -- Jonathan Weiss http://blog.innerewut.de ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
