Re: ahd0: Invalid Sequencer interrupt occurred.
Ricardo A. Reis wrote: Hi all, The University where i work recent acquire a new server, i install FreeBSD 6.0 and update for STABLE yestarday, in dmesg i see this messages ahd0: Invalid Sequencer interrupt occurred. I've had similar problems with Dual channel U320 adaptec controller (built in on supermicro board) and Seagate U320 drives. The solution was to force the drives to U160 speed from the BIOS, and split the drives equaly on the two channels to reduce the bottleneck. --niki ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panic with cdrecord
On Thu, 10 Nov 2005 20:13:42 +0100 Torfinn Ingolfsen [EMAIL PROTECTED] wrote: On Sat, 05 Nov 2005 18:41:05 +0100 Torfinn Ingolfsen [EMAIL PROTECTED] wrote: but anything else fails. (Ok, I have tested the vommands -toc, -msinfo, -prcap, -atip, -checkdrive, -prcap) Ok, the machine now has 6.0-release / amd64 on it, and the error seems to be gone. At least none of the commands above causes a panic anymore. i have yet to test writing a cd with cdrecord. In case anyone is unsure about it, this is still the desktop amd64 machine with the NEC ND-3540a dive in it: [EMAIL PROTECTED] uname -a FreeBSD kg-quiet.kg4.no 6.0-RELEASE FreeBSD 6.0-RELEASE #0: Wed Nov 2 19:07:38 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC amd64 [EMAIL PROTECTED] atacontrol list ATA channel 0: Master: ad0 ST3120026A/8.01 ATA/ATAPI revision 6 Slave: ad1 ST3120026A/8.54 ATA/ATAPI revision 6 ATA channel 1: Master: acd0 NEC DVD RW ND-3540A/1.01 ATA/ATAPI revision 0 Slave: no device present -- Regards, Torfinn Ingolfsen, Norway ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ahd0: Invalid Sequencer interrupt occurred.
Niki, You read this ... http://lists.freebsd.org/pipermail/freebsd-stable/2005-April/013737.html I'll try on the weekend, Ricardo A. Reis UNIFESP Unix and Network Admin Ricardo A. Reis wrote: Hi all, The University where i work recent acquire a new server, i install FreeBSD 6.0 and update for STABLE yestarday, in dmesg i see this messages ahd0: Invalid Sequencer interrupt occurred. I've had similar problems with Dual channel U320 adaptec controller (built in on supermicro board) and Seagate U320 drives. The solution was to force the drives to U160 speed from the BIOS, and split the drives equaly on the two channels to reduce the bottleneck. --niki ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: gvinum forgetting drives in 6.0R?
Marc Ramirez wrote: 7) For kicks, add the following to /etc/rc.conf like I saw in an e-mail somewhere: geom_vinum_load=YES start_cmd=gvinum start Remove that, and add this to /boot/loader.conf instead: geom_vinum_load=YES /Daniel Eriksson ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gnome-upgrade.sh
On Friday 11 November 2005 01:43, Jan Grant wrote:
Hope you don't mind me taking you up on your offer to someone else :-) -
this is more of a feature request from a portupgrade user who'd like to
migrate.
On Thu, 10 Nov 2005, Michael C. Shultz wrote:
On Thursday 10 November 2005 09:42, Paul T. Root wrote:
I moved the machine to a DSL line here, and am running
portmanager. It seems to be working.
We're going to investigate issues with this beta Cisco
ASA machine.
I am very interested at how things go with your upgrade,
please keep me informed. Just to let you know, the current
version of portmanager is 0.3.3_2 if anything goes wrong check
that first portmanager -v. If any problems arise I am more
than happy to work with you in solving them quickly.
I've been very interested in portmanager, but I'm facing a large
migration task because I've come from a portupgrade environment (and the
pain of migrating to portupgrade was bad enough :-) )
Ideally I'd like to be able to manage my portupgrade rules and derive
portmanager rules directly (at least for an interim period). There are a
couple of things which stop me shifting over (which I'd like to do,
since portupgrade still requires manual intervention too often). Note I
don't have what I'd describe as a _complex_ portupgrade configuration,
just a _large_ one.
Firstly: unfortunately I believe that the wildcard-matching facility
available in pkgtools.conf isn't available in portmanager (I can't tell
from the man page or the sample, but it looks like that's not the case).
My pkgtools.conf has hundreds(! - busy workstation) of entries along
these lines - some entries apply to several ports, and the portupgrade
toolset just basically uses the union of all matching rules:
[[[
'*/*' = 'BATCH=yes',
'*/kde*' = 'WITH_KDE_DEBUG=yes',
'databases/p5-DBI' = 'WITH_PROXY=yes',
'deskutils/kdepim3' = 'WITH_KPILOT=yes',
'devel/gnomevfs2' = 'WITH_X11=yes',
'devel/sdl12' = 'WITH_X11=yes',
'devel/subversion' = 'WITH_PYTHON=yes WITH_MOD_DAV_SVN=yes
WITHOUT_BDB=yes', ]]]
... and so on; so deskutils/kdepim3 gets built with
BATCH=yes WITH_KPILOT=yes WITH_KDE_DEBUG=yes
but more importantly, any future kde packages also get
WITH_KDE_DEBUG=yes automatically.
It'd be convenient if portmanager supported the same wildcard
ability (it'd make the script to migrate settings from pkgtools.conf to
portmanager much more straightforward).
The second issue is the AFTERINSTALL feature of pkgtools.conf; although
I make much less use of this, it's really handy to be able to specify
things like:
[[[
AFTERINSTALL = {
'www/jakarta-tomcat5' = 'chmod a-x
/usr/local/etc/rc.d/020.jakarta-tomcat*.sh', # ... etc
}
]]]
which let me encapsulate common small tweaks, post-installation.
Do you have any suggestions about either of these? Lacking CFT at the
moment or I'd dive into the source.
Port build options are covered in man portmanager(1). You didn't provide an
example where wild cards are used so I'm not sure what you mean there.
Here is how to handle this one:
AFTERINSTALL = {
'www/jakarta-tomcat5' = 'chmod a-x
/usr/local/etc/rc.d/020.jakarta-tomcat*.sh', # ... etc
}
from portmanager(1) setting up pm-020.conf
#
# STOP/START these programs if they are updated
#
# Stop command will be run after program is built, before
# old installed version is removed
#
# Start command will be run after rebuilt program is
# installed and successfully registerd
#
# note:
# must have leading / in /{category}/{port dir}
# anything after /{category}/{port dir} is run as
# a sh shell command
#
#STOP|/mail/postfix /usr/local/sbin/postfix stop|
#START|/mail/postfix /usr/local/sbin/postfix start|
In your case you would do this:
STOP| www/jakarta-tomcat5 /usr/local/etc/rc.d/020.jakarta-tomcat*.sh|
Stopping/starting is a new feature just introduced in 0.3.3_3.
-Mike
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gnome-upgrade.sh
On Fri, 11 Nov 2005, Michael C. Shultz wrote: On Friday 11 November 2005 01:43, Jan Grant wrote: My pkgtools.conf has hundreds(! - busy workstation) of entries along these lines - some entries apply to several ports, and the portupgrade toolset just basically uses the union of all matching rules: [[[ '*/*' = 'BATCH=yes', '*/kde*' = 'WITH_KDE_DEBUG=yes', 'databases/p5-DBI' = 'WITH_PROXY=yes', 'deskutils/kdepim3' = 'WITH_KPILOT=yes', 'devel/gnomevfs2' = 'WITH_X11=yes', 'devel/sdl12' = 'WITH_X11=yes', 'devel/subversion' = 'WITH_PYTHON=yes WITH_MOD_DAV_SVN=yes WITHOUT_BDB=yes', ]]] ... and so on; so deskutils/kdepim3 gets built with BATCH=yes WITH_KPILOT=yes WITH_KDE_DEBUG=yes but more importantly, any future kde packages also get WITH_KDE_DEBUG=yes automatically. It'd be convenient if portmanager supported the same wildcard ability (it'd make the script to migrate settings from pkgtools.conf to portmanager much more straightforward). Port build options are covered in man portmanager(1). You didn't provide an example where wild cards are used so I'm not sure what you mean there. The asterisks in the snippet above are wildcards. When portupgrade looks for the options to a port, it pattern-matches against all the entries. The deskutils/kdepim3 is a simple example above. Stopping/starting is a new feature just introduced in 0.3.3_3. Cheers, that's very handy. -- jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/ Tel +44 (0)117 3317661 http://ioctl.org/jan/ Goedel would be proud - I'm both inconsistent _and_ incomplete. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gnome-upgrade.sh
On Friday 11 November 2005 05:44, Jan Grant wrote: On Fri, 11 Nov 2005, Michael C. Shultz wrote: On Friday 11 November 2005 01:43, Jan Grant wrote: My pkgtools.conf has hundreds(! - busy workstation) of entries along these lines - some entries apply to several ports, and the portupgrade toolset just basically uses the union of all matching rules: [[[ '*/*' = 'BATCH=yes', '*/kde*' = 'WITH_KDE_DEBUG=yes', 'databases/p5-DBI' = 'WITH_PROXY=yes', 'deskutils/kdepim3' = 'WITH_KPILOT=yes', 'devel/gnomevfs2' = 'WITH_X11=yes', 'devel/sdl12' = 'WITH_X11=yes', 'devel/subversion' = 'WITH_PYTHON=yes WITH_MOD_DAV_SVN=yes WITHOUT_BDB=yes', ]]] ... and so on; so deskutils/kdepim3 gets built with BATCH=yes WITH_KPILOT=yes WITH_KDE_DEBUG=yes but more importantly, any future kde packages also get WITH_KDE_DEBUG=yes automatically. It'd be convenient if portmanager supported the same wildcard ability (it'd make the script to migrate settings from pkgtools.conf to portmanager much more straightforward). Port build options are covered in man portmanager(1). You didn't provide an example where wild cards are used so I'm not sure what you mean there. The asterisks in the snippet above are wildcards. When portupgrade looks for the options to a port, it pattern-matches against all the entries. The deskutils/kdepim3 is a simple example above. Silly me, I get it now. Not supported yet but I like the idea so am adding it to the things to do list. This one will be near the top. Stopping/starting is a new feature just introduced in 0.3.3_3. Cheers, that's very handy. -Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gnome-upgrade.sh
On Fri, 11 Nov 2005, Michael C. Shultz wrote: [on wildcards in portmanager rules] Silly me, I get it now. Not supported yet but I like the idea so am adding it to the things to do list. This one will be near the top. That's great! - especially since that pretty much makes it a mechanical process to take pkgtools.conf and spit out a corresponding portmanager config. Thanks Mike. -- jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/ Tel +44 (0)117 3317661 http://ioctl.org/jan/ Personal responsibility for corporate decisions: if they've nothing to hide, they've nothing to lobby against. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gnome-upgrade.sh
On Friday 11 November 2005 05:58, Jan Grant wrote: On Fri, 11 Nov 2005, Michael C. Shultz wrote: [on wildcards in portmanager rules] Silly me, I get it now. Not supported yet but I like the idea so am adding it to the things to do list. This one will be near the top. That's great! - especially since that pretty much makes it a mechanical process to take pkgtools.conf and spit out a corresponding portmanager config. Thanks Mike. I'll try to remember cc'ing you when I submit a change this. My guess is two days to a week, depends on if any new bugs are reported. -Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gnome-upgrade.sh
On Friday 11 November 2005 05:58, Michael C. Shultz wrote: On Friday 11 November 2005 05:58, Jan Grant wrote: On Fri, 11 Nov 2005, Michael C. Shultz wrote: [on wildcards in portmanager rules] Silly me, I get it now. Not supported yet but I like the idea so am adding it to the things to do list. This one will be near the top. That's great! - especially since that pretty much makes it a mechanical process to take pkgtools.conf and spit out a corresponding portmanager config. Thanks Mike. I'll try to remember cc'ing you when I submit a change this. My guess is two days to a week, depends on if any new bugs are reported. -Mike One last thing, if you make a script that does the conversion, might I have a copy? Here is how I'll set up pm-020.conf to work: textproc/docproj|JADETEX=no| java/jdk14|-DMINIMAL| textproc/libxml2|THREADS=off SCHEMA=on MEM_DEBUG=off THREAD_ALLOC=off| */kde*|WITH_KDE_DEBUG=yes| */*|BATCH=yes| ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
issues with installworld on fbsd6 libcom_err
I had no errors when building world, but it seems each time I have tried to installworld I come up with the same error. It shows up in the lib/libcom_err directory. No matter what shell I try fixes the issue. I have gone as far as to delete all the directories in /usr/src and re cvsup. I have no options in /etc/make.conf outside of the ones put there by perl and KERNCONF=KERNELNAME. Like I said it builds with no problem, but error code 1 outs each time during make installworld. === lib/libcom_err (install) install -C -o root -g wheel -m 444 libcom_err.a /usr/lib install -C -o root -g wheel -m 444 libcom_err_p.a /usr/lib install -s -o root -g wheel -m 444 libcom_err.so.3 /usr/lib ln -fs libcom_err.so.3 /usr/lib/libcom_err.so install -C -o root -g wheel -m 444 /usr/src/lib/libcom_err/../../contrib/com_err/com_err.h /usr/src/lib/libcom_err/../../contrib/com_err/com_right.h /usr/include install -o root -g wheel -m 444 com_err.3.gz /usr/share/man/man3 === lib/libcom_err/doc (install) install-info --quiet --defsection=Programming development tools. --defentry=* libcom_err: (com_err).A Common Error Description Library for UNIX. com_err.info /usr/share/info/dir install-info: /usr/share/info/dir: empty file *** Error code 1 Stop in /usr/src/lib/libcom_err/doc. *** Error code 1 Stop in /usr/src/lib/libcom_err. *** Error code 1 Stop in /usr/src/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Any suggestions on how to fix this so I can get fbsd 6 world installed so I can run portmanger to update a crap load of ports would be appreciated. Eric -- === Eric I. Ekong[EMAIL PROTECTED] FreeBSD - The Power to Serve http://www.freebsd.org K Desktop Environment on FreeBSD http://freebsd.kde.org === Laws of Serendipity: (1) In order to discover anything, you must be looking for something. (2) If you wish to make an improved product, you must already be engaged in making an inferior one. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gnome-upgrade.sh
On Fri, 11 Nov 2005, Michael C. Shultz wrote: On Friday 11 November 2005 05:58, Michael C. Shultz wrote: On Friday 11 November 2005 05:58, Jan Grant wrote: On Fri, 11 Nov 2005, Michael C. Shultz wrote: [on wildcards in portmanager rules] Silly me, I get it now. Not supported yet but I like the idea so am adding it to the things to do list. This one will be near the top. That's great! - especially since that pretty much makes it a mechanical process to take pkgtools.conf and spit out a corresponding portmanager config. Thanks Mike. I'll try to remember cc'ing you when I submit a change this. My guess is two days to a week, depends on if any new bugs are reported. -Mike One last thing, if you make a script that does the conversion, might I have a copy? Here is how I'll set up pm-020.conf to work: Surely. pkgtools.conf is actually a ruby script: I've no idea how dynamically the rules are evaluated but something that works ona prettystock bunch of settings should be close to trivial. -- jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/ Tel +44 (0)117 3317661 http://ioctl.org/jan/ ...and then three milkmaids turned up (to the delight and delactation of the crowd). ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gnome-upgrade.sh
On Friday 11 November 2005 06:26, Jan Grant wrote: On Fri, 11 Nov 2005, Michael C. Shultz wrote: On Friday 11 November 2005 05:58, Michael C. Shultz wrote: On Friday 11 November 2005 05:58, Jan Grant wrote: On Fri, 11 Nov 2005, Michael C. Shultz wrote: [on wildcards in portmanager rules] Silly me, I get it now. Not supported yet but I like the idea so am adding it to the things to do list. This one will be near the top. That's great! - especially since that pretty much makes it a mechanical process to take pkgtools.conf and spit out a corresponding portmanager config. Thanks Mike. I'll try to remember cc'ing you when I submit a change this. My guess is two days to a week, depends on if any new bugs are reported. -Mike One last thing, if you make a script that does the conversion, might I have a copy? Here is how I'll set up pm-020.conf to work: Surely. pkgtools.conf is actually a ruby script: I've no idea how dynamically the rules are evaluated but something that works ona prettystock bunch of settings should be close to trivial. Thank you. If it works well I might use it to have portmanager pick up settings from portupgrade on the fly, or at least provide some sort of conversion command. Thanks :) -Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gvinum forgetting drives in 6.0R?
On Friday 11 November 2005 07:46 am, Daniel Eriksson wrote: Marc Ramirez wrote: 7) For kicks, add the following to /etc/rc.conf like I saw in an e-mail somewhere: geom_vinum_load=YES start_cmd=gvinum start Remove that, and add this to /boot/loader.conf instead: geom_vinum_load=YES Well, that was a huge brain fart on my part! All is good. Thanks! Marc. -- Marc Ramirez Blue Circle Software Corporation 513-688-1070 (main) 513-382-1270 (direct) http://www.bluecirclesoft.com http://www.mrami.com (personal) pgp2KYYgNEDX1.pgp Description: PGP signature
Re: issues with installworld on fbsd6 libcom_err
On Fri, Nov 11, 2005 at 09:17:10AM -0500, Eric Ekong wrote: I had no errors when building world, but it seems each time I have tried to installworld I come up with the same error. It shows up in the lib/libcom_err directory. No matter what shell I try fixes the issue. I have gone as far as to delete all the directories in /usr/src and re cvsup. I have no options in /etc/make.conf outside of the ones put there by perl and KERNCONF=KERNELNAME. Like I said it builds with no problem, but error code 1 outs each time during make installworld. You're probably using -jX with installworld. If so, a fix for this has been in HEAD as of a few days: : ru 2005-11-03 08:56:39 UTC : : FreeBSD src repository : : Modified files: : .Makefile.inc1 : share/mk bsd.info.mk : Log: : Serialize access to the info/dir file; needed for parallel installs. : : Reported by:scottl : : I'm not very fond of using the non-standard lockf(1) here, but I : have no better idea at the moment. NetBSD uses ln(1) to create a : lock file, but this approach can result in a deadlock if make is : interrupted, leaving an orphaned lock file. : : Revision ChangesPath : 1.514 +1 -1 src/Makefile.inc1 : 1.72 +1 -0 src/share/mk/bsd.info.mk I'm not happy with this because it broke NFS installs. Once I find a proper fix, I will also make sure to MFC it to RELENG_6. === lib/libcom_err (install) install -C -o root -g wheel -m 444 libcom_err.a /usr/lib install -C -o root -g wheel -m 444 libcom_err_p.a /usr/lib install -s -o root -g wheel -m 444 libcom_err.so.3 /usr/lib ln -fs libcom_err.so.3 /usr/lib/libcom_err.so install -C -o root -g wheel -m 444 /usr/src/lib/libcom_err/../../contrib/com_err/com_err.h /usr/src/lib/libcom_err/../../contrib/com_err/com_right.h /usr/include install -o root -g wheel -m 444 com_err.3.gz /usr/share/man/man3 === lib/libcom_err/doc (install) install-info --quiet --defsection=Programming development tools. --defentry=* libcom_err: (com_err).A Common Error Description Library for UNIX. com_err.info /usr/share/info/dir install-info: /usr/share/info/dir: empty file *** Error code 1 Stop in /usr/src/lib/libcom_err/doc. *** Error code 1 Stop in /usr/src/lib/libcom_err. *** Error code 1 Stop in /usr/src/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Any suggestions on how to fix this so I can get fbsd 6 world installed so I can run portmanger to update a crap load of ports would be appreciated. -- Ruslan Ermilov [EMAIL PROTECTED] FreeBSD committer pgp2L0jzE4Dl7.pgp Description: PGP signature
Re: gnome-upgrade.sh
On Fri, 11 Nov 2005, Michael C. Shultz wrote: One last thing, if you make a script that does the conversion, might I have a copy? Here is how I'll set up pm-020.conf to work: Surely. pkgtools.conf is actually a ruby script: I've no idea how dynamically the rules are evaluated but something that works ona prettystock bunch of settings should be close to trivial. Thank you. If it works well I might use it to have portmanager pick up settings from portupgrade on the fly, or at least provide some sort of conversion command. Thanks :) Attached uses ruby to parse the pkgtools.conf (it relies on the portupgrade ruby package) - it'll spit out the appropriate sections (HOLD_PKGS, BEFOREBUILD, AFTERINSTALL and MAKE_ARGS) in what I think the portmanager format is (although the script is trivial, as you can see). Note that the MAKE_ARGS etc go through a hash/dictionary and consequently are unordered. A small snippet of the output I get from this: [[[ CATEGORY/PORT|OPTION=| # do not delete this line! # Ignored packages from HOLD_PKGS IGNORE|bsdpan-*| IGNORE|x11/nvidia-driver| IGNORE|editors/openoffice*| # STOP entries come from BEFOREBUILD # START entries come from AFTERINSTALL START|/databases/postgresql7 chmod a+x /usr/local/share/postgresql/502.pgsql| START|/www/jakarta-tomcat5 chmod a-x /usr/local/etc/rc.d/020.jakarta-tomcat*.sh| # Package options from MAKE_ARGS # Note: pkgtools.conf will use the UNION of all matching lines security/gnupg|WITH_SUID_GPG=yes| devel/subversion|WITH_PYTHON=yes WITH_MOD_DAV_SVN=yes WITHOUT_BDB=yes| x11/kde3|| deskutils/kdepim3|WITH_KPILOT=yes| www/gallery|| www/rt*|WITH_FASTCGI=yes WITH_APACHE2=yes DB_TYPE=Pg DB_HOST=localhost DB_DATABASE=rt3 DB_USER=rt3| www/apache2|WITH_PROXY_MODULES=yes| multimedia/kdemultimedia*|WITH_LAME=yes WITH_XINE=yes WITH_MPEGLIB=yes| */*|BATCH=yes| java/jdk14|NATIVE_BOOTSTRAP=yes JAVA_HOME=| */kde*|WITH_KDE_DEBUG=yes| mail/exim|WITH_EXIMON=yes WITH_EXISCAN_ACL=yes WITH_TCP_WRAPPERS=yes WITH_PGSQL=yes WITHOUT_PERL=yes | ]]] -- jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/ Tel +44 (0)117 3317661 http://ioctl.org/jan/ I'm the dandy information superhighwayman.#!/usr/local/bin/ruby require pkgtools puts CATEGORY/PORT|OPTION=| # do not delete this line! load_config # held packages puts puts # Ignored packages from HOLD_PKGS puts config_value(:HOLD_PKGS).each do |pkg| puts IGNORE| + pkg + | end # beforebuild becomes stop puts puts # STOP entries come from BEFOREBUILD puts config_value(:BEFOREBUILD).each do |pkg| puts STOP|/ + pkg[0] + + pkg[1] + | end # afterinstall becomes start puts puts # START entries come from AFTERINSTALL puts config_value(:AFTERINSTALL).each do |pkg| puts START|/ + pkg[0] + + pkg[1] + | end # package options. puts puts # Package options from MAKE_ARGS puts # Note: pkgtools.conf will use the UNION of all matching lines puts config_value(:MAKE_ARGS).each do |pkg| puts pkg[0] + | + pkg[1] + | end ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Filesystems 1TB not possible on 6.0-R (anymore?).
On 11/11/05, David Kirchner [EMAIL PROTECTED] wrote: On 11/10/05, Xin LI [EMAIL PROTECTED] wrote: Would you please consider to try gpt instead of bsdlabel? BTW. The dmesg meesage indicates that your array is degraded :-( Is it possible to have sysinstall use gpt instead of bsdlabel, and then to boot from a gpt based array? I haven't had luck with it, but maybe that was fixed with 6.0. I'm not quite sure, but the live system shell provided by the installation CD (disc1) might help. -- Xin LI [EMAIL PROTECTED] http://www.delphij.net ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Adaptec AIC-8130 (Marvell 88SX6041) 4-port Hercules-2 SATA Controller
I'm looking at trying out the Supermicro H8DAR-T Opteron motherboard (http://www.supermicro.com/Aplus/motherboard/Opteron/8132/H8DAR-T.cfm) but its on-board SATA controller is an Adaptec AIC-8130 (Marvell 88SX6041) Hercules-2 rev B2. Given that it is a Marvell chip, I'm concerned it might not work with any available drivers, and I haven't found any references in the FreeBSD 6.0 source code to either of the model numbers (8130 or 88SX6041). Does anyone know for sure whether it is or isn't supported? Thanks, Guy Helmer -- Guy Helmer, Ph.D. Principal System Architect Palisade Systems, Inc. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gnome-upgrade.sh
On Friday 11 November 2005 07:23, Jan Grant wrote:
On Fri, 11 Nov 2005, Michael C. Shultz wrote:
One last thing, if you make a script that does the conversion, might
I have a copy? Here is how I'll set up pm-020.conf to work:
Surely. pkgtools.conf is actually a ruby script: I've no idea how
dynamically the rules are evaluated but something that works ona
prettystock bunch of settings should be close to trivial.
Thank you. If it works well I might use it to have portmanager pick up
settings from portupgrade on the fly, or at least provide some sort
of conversion command. Thanks :)
Attached uses ruby to parse the pkgtools.conf (it relies on the
portupgrade ruby package) - it'll spit out the appropriate sections
(HOLD_PKGS, BEFOREBUILD, AFTERINSTALL and MAKE_ARGS) in what I think the
portmanager format is (although the script is trivial, as you can see).
Note that the MAKE_ARGS etc go through a hash/dictionary and
consequently are unordered. A small snippet of the output I get from
this:
[[[
CATEGORY/PORT|OPTION=| # do not delete this line!
# Ignored packages from HOLD_PKGS
IGNORE|bsdpan-*|
IGNORE|x11/nvidia-driver|
IGNORE|editors/openoffice*|
# STOP entries come from BEFOREBUILD
# START entries come from AFTERINSTALL
START|/databases/postgresql7 chmod a+x
/usr/local/share/postgresql/502.pgsql| START|/www/jakarta-tomcat5 chmod a-x
/usr/local/etc/rc.d/020.jakarta-tomcat*.sh|
# Package options from MAKE_ARGS
# Note: pkgtools.conf will use the UNION of all matching lines
security/gnupg|WITH_SUID_GPG=yes|
devel/subversion|WITH_PYTHON=yes WITH_MOD_DAV_SVN=yes WITHOUT_BDB=yes|
x11/kde3||
deskutils/kdepim3|WITH_KPILOT=yes|
www/gallery||
www/rt*|WITH_FASTCGI=yes WITH_APACHE2=yes DB_TYPE=Pg DB_HOST=localhost
DB_DATABASE=rt3 DB_USER=rt3| www/apache2|WITH_PROXY_MODULES=yes|
multimedia/kdemultimedia*|WITH_LAME=yes WITH_XINE=yes WITH_MPEGLIB=yes|
*/*|BATCH=yes|
java/jdk14|NATIVE_BOOTSTRAP=yes JAVA_HOME=|
*/kde*|WITH_KDE_DEBUG=yes|
mail/exim|WITH_EXIMON=yes WITH_EXISCAN_ACL=yes WITH_TCP_WRAPPERS=yes
WITH_PGSQL=yes WITHOUT_PERL=yes | ]]]
^^^
little glitch?
Works good, just one thing, portmanager has no dependencies, like to keep it
that way. How are you at awk? I use this awk script to do initial parsing of
the config file:
#!/bin/sh
#
# $1 = pm-020.conf $2 = output file name
#
echo keyzzNULLzzvaluezzNULLzz $2;awk 'BEGIN{ FS = | } NF == 3
$1 !~ /#/ $1 !~ /CATEGORY\/PORT/ $2 !~ /#/ {print $1 zzNULLz
I'm no scripter so getting the above to work was painful ;)
-Mike
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: issues with installworld on fbsd6 libcom_err
Just doing a regular make installworld with no -J options anywhere. Unless that is a default with sh shell or csh shell. Eric * Ruslan Ermilov [EMAIL PROTECTED] [05 10:04]: Date: Fri, 11 Nov 2005 17:04:19 +0200 From: Ruslan Ermilov [EMAIL PROTECTED] To: freebsd-questions@freebsd.org, freebsd-stable@freebsd.org Cc: Subject: Re: issues with installworld on fbsd6 libcom_err On Fri, Nov 11, 2005 at 09:17:10AM -0500, Eric Ekong wrote: I had no errors when building world, but it seems each time I have tried to installworld I come up with the same error. It shows up in the lib/libcom_err directory. No matter what shell I try fixes the issue. I have gone as far as to delete all the directories in /usr/src and re cvsup. I have no options in /etc/make.conf outside of the ones put there by perl and KERNCONF=KERNELNAME. Like I said it builds with no problem, but error code 1 outs each time during make installworld. You're probably using -jX with installworld. If so, a fix for this has been in HEAD as of a few days: : ru 2005-11-03 08:56:39 UTC : : FreeBSD src repository : : Modified files: : .Makefile.inc1 : share/mk bsd.info.mk : Log: : Serialize access to the info/dir file; needed for parallel installs. : : Reported by:scottl : : I'm not very fond of using the non-standard lockf(1) here, but I : have no better idea at the moment. NetBSD uses ln(1) to create a : lock file, but this approach can result in a deadlock if make is : interrupted, leaving an orphaned lock file. : : Revision ChangesPath : 1.514 +1 -1 src/Makefile.inc1 : 1.72 +1 -0 src/share/mk/bsd.info.mk I'm not happy with this because it broke NFS installs. Once I find a proper fix, I will also make sure to MFC it to RELENG_6. === lib/libcom_err (install) install -C -o root -g wheel -m 444 libcom_err.a /usr/lib install -C -o root -g wheel -m 444 libcom_err_p.a /usr/lib install -s -o root -g wheel -m 444 libcom_err.so.3 /usr/lib ln -fs libcom_err.so.3 /usr/lib/libcom_err.so install -C -o root -g wheel -m 444 /usr/src/lib/libcom_err/../../contrib/com_err/com_err.h /usr/src/lib/libcom_err/../../contrib/com_err/com_right.h /usr/include install -o root -g wheel -m 444 com_err.3.gz /usr/share/man/man3 === lib/libcom_err/doc (install) install-info --quiet --defsection=Programming development tools. --defentry=* libcom_err: (com_err).A Common Error Description Library for UNIX. com_err.info /usr/share/info/dir install-info: /usr/share/info/dir: empty file *** Error code 1 Stop in /usr/src/lib/libcom_err/doc. *** Error code 1 Stop in /usr/src/lib/libcom_err. *** Error code 1 Stop in /usr/src/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Any suggestions on how to fix this so I can get fbsd 6 world installed so I can run portmanger to update a crap load of ports would be appreciated. -- Ruslan Ermilov [EMAIL PROTECTED] FreeBSD committer -- === Eric I. Ekong[EMAIL PROTECTED] FreeBSD - The Power to Serve http://www.freebsd.org K Desktop Environment on FreeBSD http://freebsd.kde.org === Laws of Serendipity: (1) In order to discover anything, you must be looking for something. (2) If you wish to make an improved product, you must already be engaged in making an inferior one. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gnome-upgrade.sh
On Friday 11 November 2005 07:29, Michael C. Shultz wrote:
On Friday 11 November 2005 07:23, Jan Grant wrote:
On Fri, 11 Nov 2005, Michael C. Shultz wrote:
One last thing, if you make a script that does the conversion,
might I have a copy? Here is how I'll set up pm-020.conf to work:
Surely. pkgtools.conf is actually a ruby script: I've no idea how
dynamically the rules are evaluated but something that works ona
prettystock bunch of settings should be close to trivial.
Thank you. If it works well I might use it to have portmanager pick up
settings from portupgrade on the fly, or at least provide some sort
of conversion command. Thanks :)
Attached uses ruby to parse the pkgtools.conf (it relies on the
portupgrade ruby package) - it'll spit out the appropriate sections
(HOLD_PKGS, BEFOREBUILD, AFTERINSTALL and MAKE_ARGS) in what I think the
portmanager format is (although the script is trivial, as you can see).
Note that the MAKE_ARGS etc go through a hash/dictionary and
consequently are unordered. A small snippet of the output I get from
this:
[[[
CATEGORY/PORT|OPTION=| # do not delete this line!
# Ignored packages from HOLD_PKGS
IGNORE|bsdpan-*|
IGNORE|x11/nvidia-driver|
IGNORE|editors/openoffice*|
# STOP entries come from BEFOREBUILD
# START entries come from AFTERINSTALL
START|/databases/postgresql7 chmod a+x
/usr/local/share/postgresql/502.pgsql| START|/www/jakarta-tomcat5 chmod
a-x /usr/local/etc/rc.d/020.jakarta-tomcat*.sh|
# Package options from MAKE_ARGS
# Note: pkgtools.conf will use the UNION of all matching lines
security/gnupg|WITH_SUID_GPG=yes|
devel/subversion|WITH_PYTHON=yes WITH_MOD_DAV_SVN=yes WITHOUT_BDB=yes|
x11/kde3||
deskutils/kdepim3|WITH_KPILOT=yes|
www/gallery||
www/rt*|WITH_FASTCGI=yes WITH_APACHE2=yes DB_TYPE=Pg DB_HOST=localhost
DB_DATABASE=rt3 DB_USER=rt3| www/apache2|WITH_PROXY_MODULES=yes|
multimedia/kdemultimedia*|WITH_LAME=yes WITH_XINE=yes WITH_MPEGLIB=yes|
*/*|BATCH=yes|
java/jdk14|NATIVE_BOOTSTRAP=yes JAVA_HOME=|
*/kde*|WITH_KDE_DEBUG=yes|
mail/exim|WITH_EXIMON=yes WITH_EXISCAN_ACL=yes WITH_TCP_WRAPPERS=yes
WITH_PGSQL=yes WITHOUT_PERL=yes | ]]]
^^^
little glitch?
Works good, just one thing, portmanager has no dependencies, like to keep
it that way. How are you at awk? I use this awk script to do initial
parsing of the config file:
#!/bin/sh
#
# $1 = pm-020.conf $2 = output file name
#
echo keyzzNULLzzvaluezzNULLzz $2;awk 'BEGIN{ FS = | } NF == 3
$1 !~ /#/ $1 !~ /CATEGORY\/PORT/ $2 !~ /#/ {print $1 zzNULLz
I'm no scripter so getting the above to work was painful ;)
-Mike
Sorry I was being dumb. The ruby script is no problem, it will only run
if portupgrade is installed so a dependency won't have to be put on ruby.
-Mike
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gnome-upgrade.sh
Michael C. Shultz [EMAIL PROTECTED] writes: Works good, just one thing, portmanager has no dependencies, like to keep it that way. It's not necessary to consider that an issue: this functionality is really only useful to someone who has had portupgrade installed anyway. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gnome-upgrade.sh
On Friday 11 November 2005 08:32, Lowell Gilbert wrote: Michael C. Shultz [EMAIL PROTECTED] writes: Works good, just one thing, portmanager has no dependencies, like to keep it that way. It's not necessary to consider that an issue: this functionality is really only useful to someone who has had portupgrade installed anyway. I just thought of that, thanks for confirming :) -Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading 5.4 - 6.0 without reinstalling. safe ?
David Kirchner [EMAIL PROTECTED] wrote: On 11/10/05, Oliver Fromme [EMAIL PROTECTED] wrote: Well, I vote for /sbin/nologin as root's login shell. In single-user mode, the systems asks for the shell, with /bin/sh being the default. In multi-user mode, nobody should ever log in as root. You rather log in as normal user and then use su -m, or use sudo(8) or super(1) or whatever. It's awkward to have to reboot a machine just to log in to it from a console. I don't have to reboot to do that. Let's say you're colocated and utilize a remote hands service, or you make a mistake with your firewall. You're better off disabling root logins in sshd_config, so no one can use root from remote. You mean: No one can log in as root. You can still use root from remote, by logging in as normal user and then using one of the various methods (su, sudo, super, ...). Then you can leave a password on the root account and still have console access. Console access, root login and having a password on the root account are all different things. They're not necessarily dependant on each other. I just leave root logins enabled and use ssh keys. Leaves a very nice, easy to follow, one-line-per-login paper trail of who logged in as root from where and when. su, sudo etc. do the same. Another advantage of using su (particularly su -m) is the feature that you can use your own favourite shell, your usual aliases, keybindings etc. while being root. Otherwise, on machines where multiple admins log in as root, they tend to clutter root's profiles with their own stuff which confuses the others and might even conflict with settings of others. This is a bad thing and can cause damage. Logging in as root should be considered harmful, IMHO. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. Clear perl code is better than unclear awk code; but NOTHING comes close to unclear perl code (taken from comp.lang.awk FAQ) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gnome-upgrade.sh
On Friday 11 November 2005 09:04, Lowell Gilbert wrote: Michael C. Shultz [EMAIL PROTECTED] writes: On Friday 11 November 2005 08:32, Lowell Gilbert wrote: Michael C. Shultz [EMAIL PROTECTED] writes: Works good, just one thing, portmanager has no dependencies, like to keep it that way. It's not necessary to consider that an issue: this functionality is really only useful to someone who has had portupgrade installed anyway. I just thought of that, thanks for confirming :) Yeah, my secret of success in programming is to not fool myself into making things more complicated than I need to do. You could even leave the script out of the port completely, and just include a URL to it in the pkg-message... Simple, quick and painless :) If users want to simply convert that is the way to go. I also had in mind a knob like this: WITH_PORTUPGRADE_CONF if selected then portupgrade's settings are just added to portmanager's each time portmanager is run so if folks want to experiment with each program settings don't get lost. -Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
6-STABLE TCP nfs Linux client hangs
I have a 2x Athlon running with amd64 kernel and I can hang 2 Linux clients by attempting to write large amounts of data over TCP nfs. If I set the nfsd to be UDP only, the problem never occurs. Please let me know what I can do to help track this problem down. Cheers, Sean ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Hyperthreading issues.
Hi, Just upgraded from 5.4 to 6.0 and hyperthreading stoped working. Everything looks ok, but it doesn't use two of the logical CPU's. Is it only an error in showing the stats, or isn't it working on all 4 cpus? One other thing is when I try to switch off hyperthreading in BIOS, it will hang at bootup when it are settling the scsi drives. After awhile it will give me scsi timeouts. This only happens when I have two cpu enabled and hyperthreading off. If I disable one cpu w ht off it will boot wo problems, or two cpus w ht. But booting with ht + two cpu's gives me the other problem. The ht off issue was already present in 5.x. at least since 5.2.1. - using top I only see switching from CPU 0 and 1. $ ps aux | grep cpu root 11 92.4 0.0 0 8 ?? RL7:11PM 103:25.06 [idle: cpu3] root 12 92.4 0.0 0 8 ?? RL7:11PM 0:00.00 [idle: cpu2] root 14 31.1 0.0 0 8 ?? RL7:11PM 45:18.68 [idle: cpu0] root 13 27.3 0.0 0 8 ?? RL7:11PM 48:58.93 [idle: cpu1] $ sysctl -a | grep cpu kern.threads.virtual_cpu: 4 kern.ccpu: 1948 kern.smp.maxcpus: 16 kern.smp.cpus: 4 debug.cpufreq.lowest: 0 debug.cpufreq.verbose: 0 debug.kdb.stop_cpus: 1 debug.PMAP1changedcpu: 4 hw.ncpu: 4 hw.acpi.cpu.cx_supported: C1/0 hw.acpi.cpu.cx_lowest: C1 hw.acpi.cpu.cx_usage: 100.00% machdep.cpu_idle_hlt: 1 machdep.hlt_cpus: 0 machdep.hlt_logical_cpus: 0 machdep.logical_cpus_mask: 12 dev.cpu.0.%desc: ACPI CPU dev.cpu.0.%driver: cpu dev.cpu.0.%location: handle=\_PR_.CPU0 dev.cpu.0.%pnpinfo: _HID=none _UID=0 dev.cpu.0.%parent: acpi0 dev.cpu.1.%desc: ACPI CPU dev.cpu.1.%driver: cpu dev.cpu.1.%location: handle=\_PR_.CPU1 dev.cpu.1.%pnpinfo: _HID=none _UID=0 dev.cpu.1.%parent: acpi0 dev.cpu.2.%desc: ACPI CPU dev.cpu.2.%driver: cpu dev.cpu.2.%location: handle=\_PR_.CPU2 dev.cpu.2.%pnpinfo: _HID=none _UID=0 dev.cpu.2.%parent: acpi0 dev.cpu.3.%desc: ACPI CPU dev.cpu.3.%driver: cpu dev.cpu.3.%location: handle=\_PR_.CPU3 dev.cpu.3.%pnpinfo: _HID=none _UID=0 dev.cpu.3.%parent: acpi0 $ sysctl -a | grep hyper machdep.hyperthreading_allowed: 1 With ht off on dual cpu it ends with (scribled by hand) SCB 1 - timed out Other SCB Time out No other SBC worth waiting for... ahd0: Issued Channel A Bus Reset 13 SCB aborted dmesg.boot: Copyright (c) 1992-2005 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.0-STABLE #0: Fri Nov 11 17:31:05 CET 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/games3 ACPI APIC Table: PTLTD APIC Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 2.40GHz (2400.11-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf29 Stepping = 9 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x4400CNTX-ID,b14 Hyperthreading: 2 logical CPUs real memory = 1073741824 (1024 MB) avail memory = 1043279872 (994 MB) FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 6 cpu1 (AP): APIC ID: 0 cpu2 (AP): APIC ID: 1 cpu3 (AP): APIC ID: 7 ioapic0 Version 1.1 irqs 0-15 on motherboard ioapic1 Version 1.1 irqs 16-31 on motherboard npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: PTLTD RSDT on motherboard acpi0: Power Button (fixed) pci_link0: ACPI PCI Link LNKA on acpi0 pci_link1: ACPI PCI Link LNKB on acpi0 pci_link2: ACPI PCI Link LNKC irq 9 on acpi0 pci_link3: ACPI PCI Link LNKD irq 11 on acpi0 pci_link4: ACPI PCI Link LNKE on acpi0 pci_link5: ACPI PCI Link LNKF on acpi0 pci_link6: ACPI PCI Link LNKG on acpi0 pci_link7: ACPI PCI Link LNKH on acpi0 pci_link8: ACPI PCI Link LNKI on acpi0 pci_link9: ACPI PCI Link LNKJ on acpi0 pci_link10: ACPI PCI Link LNKK irq 10 on acpi0 pci_link11: ACPI PCI Link LNKL on acpi0 pci_link12: ACPI PCI Link LNKM on acpi0 pci_link13: ACPI PCI Link LNKN on acpi0 pci_link14: ACPI PCI Link LNKO on acpi0 pci_link15: ACPI PCI Link LNKP on acpi0 pci_link16: ACPI PCI Link LNKU on acpi0 Timecounter ACPI-safe frequency 3579545 Hz quality 1000 acpi_timer0: 32-bit timer at 3.579545MHz port 0xf008-0xf00b on acpi0 cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 cpu2: ACPI CPU on acpi0 cpu3: ACPI CPU on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge on acpi0 pci0: ACPI PCI bus on pcib0 pci0: display, VGA at device 4.0 (no driver attached) atapci0: ServerWorks CSB6 UDMA100 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1400-0x140f at device 15.1 on pci0 ata0: ATA channel 0 on atapci0 ata1: ATA channel 1 on atapci0 isab0: PCI-ISA bridge at device 15.3 on pci0 isa0: ISA bus on isab0 pcib1: ACPI Host-PCI bridge on acpi0 pci1: ACPI PCI bus on pcib1 pcib2: ACPI Host-PCI bridge on acpi0 pci2: ACPI PCI bus on pcib2 bge0: Broadcom BCM5704C Dual Gigabit Ethernet, ASIC rev. 0x2002 mem
Re: ahd0: Invalid Sequencer interrupt occurred.
Ade Lovett wrote: On Nov 10, 2005, at 05:30 , Ricardo A. Reis wrote: Reducing the problem to the relevant pieces: ahd0: Adaptec AIC7902 Ultra320 SCSI adapter port 0x2400-0x24ff,0x2000-0x20ff mem 0xdd20-0xdd201fff irq 32 at device 2.0 on pci3 ahd0: [GIANT-LOCKED] aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs ahd1: Adaptec AIC7902 Ultra320 SCSI adapter port 0x2c00-0x2cff,0x2800-0x28ff mem 0xdd202000-0xdd203fff irq 33 at device 2.1 on pci3 ahd1: [GIANT-LOCKED] aic7902: Ultra320 Wide Channel B, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs [...] da0 at ahd0 bus 0 target 0 lun 0 da0: SEAGATE ST373307LC 0006 Fixed Direct Access SCSI-3 device da0: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged Queueing Enabled da0: 70007MB (143374744 512 byte sectors: 255H 63S/T 8924C) da1 at ahd0 bus 0 target 1 lun 0 da1: SEAGATE ST373307LC 0006 Fixed Direct Access SCSI-3 device da1: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged Queueing Enabled da1: 70007MB (143374744 512 byte sectors: 255H 63S/T 8924C) Trying to mount root from ufs:/dev/da0s1a Adaptec HBAs and Seagate drives have a long and intensely painful history of not working well together. Adaptec blames Seagate. Seagate blames Adaptec. Throw in the myriad of subtly different AIC controllers that are commonplace on 1U and 2U rackmount servers, and things get even more entertaining. You essentially have 3 options 4 options. 0) Upgrade to Seagate 10K.7 drive firmware level 0008. That seems to help. One ahd sequencer error message still appears at boot, but after that it seems to work (with your fingers crossed). -Amit 1) replace the HBA -- somewhat difficult to do if it's embedded and you need the PCIX slots for something else. 2) replace the drives -- IBM/Hitachi are fine choices here. Make sure to tell whomever you purchase systems from that you'll not accept Seagate drives in the future. 3) inside the adaptec bios, drop the drives to U160 speed, making sure that *both* packetizing *and* QAS are turned OFF. You'll lose a little bit of performance (but not all that much, Seagate drives really are garbage), and get some semblance of stability. -aDe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
kernel build fails at 6.0-release!
Hi! I just can't build my kernel. I tried several changes at the config file, but I always get the same message. -- # # DEEPBLACK -- DeepBlack kernel configuration file for FreeBSD/i386 # # $FreeBSD: src/sys/i386/conf/DEEPBLACK v.1.0 $ machine i386 #cpuI486_CPU# (commented out this at v.1.0!!) #cpuI586_CPU# (commented out this at v.1.0!!) cpu I686_CPU ident DEEPBLACK # To statically compile in device wiring instead of /boot/device.hints #hints GENERIC.hints # Default places to look for devices. #makeoptionsDEBUG=-g# Build kernel with gdb(1) debug symbols #optionsSCHED_ULE # ULE scheduler options SCHED_4BSD # 4BSD scheduler options PREEMPTION # Enable kernel thread preemption options INET# InterNETworking options INET6 # IPv6 communications protocols options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories options MD_ROOT # MD is a potential root device #optionsNFSCLIENT # Network Filesystem Client (commented out this at v.1.0!!) #optionsNFSSERVER # Network Filesystem Server (commented out this at v.1.0!!) #optionsNFS_ROOT# NFS usable as /, requires NFSCLIENT (commented out this at v.1.0!!) #optionsMSDOSFS # MSDOS Filesystem (commented out this at v.1.0!!) #optionsCD9660 # ISO 9660 Filesystem (commented out this at v.1.0!!) options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS# Pseudo-filesystem framework #optionsGEOM_GPT# GUID Partition Tables. (commented out this at v.1.0!!) options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options COMPAT_FREEBSD5 # Compatible with FreeBSD5 #optionsSCSI_DELAY=5000 # Delay (in ms) before probing SCSI (commented out this at v.1.0!!) #optionsKTRACE # ktrace(1) support options SYSVSHM # SYSV-style shared memory #optionsSYSVMSG # SYSV-style message queues (commented out this at v.1.0!!) #optionsSYSVSEM # SYSV-style semaphores (commented out this at v.1.0!!) options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV# install a CDEV entry in /dev #optionsAHC_REG_PRETTY_PRINT# Print register bitfields in debug # output. Adds ~128k to driver. (commented out this at v.1.0!!) #optionsAHD_REG_PRETTY_PRINT# Print register bitfields in debug # output. Adds ~215k to driver. (commented out this at v.1.0!!) options ADAPTIVE_GIANT # Giant mutex is adaptive. device apic# I/O APIC # Bus support. device eisa device pci # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives #device ataraid # ATA RAID drives (commented out this at v.1.0!!) device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives #device atapist # ATAPI tape drives (commented out this at v.1.0!!) options ATA_STATIC_ID # Static device numbering # SCSI Controllers (commented out this at v.1.0!!) #device ahb # EISA AHA1742 family #device ahc # AHA2940 and onboard AIC7xxx devices #device ahd # AHA39320/29320 and onboard AIC79xx devices #device amd # AMD 53C974 (Tekram DC-390(T)) #device isp # Qlogic family ##deviceispfw # Firmware for QLogic HBAs- normally a module #device mpt # LSI-Logic MPT-Fusion ##devicencr # NCR/Symbios Logic #device sym # NCR/Symbios Logic (newer chipsets + those of `ncr') #device trm # Tekram DC395U/UW/F DC315U adapters #device adv # Advansys SCSI adapters #device adw # Advansys wide SCSI adapters #device aha # Adaptec 154x SCSI adapters #device aic # Adaptec 15[012]x SCSI adapters, AIC-6[23]60. #device bt # Buslogic/Mylex MultiMaster
Re: kernel build fails at 6.0-release!
On Fri, Nov 11, 2005 at 11:41:36PM +0200, Giorgos Kapetanakis wrote: Hi! I just can't build my kernel. I tried several changes at the config file, but I always get the same message. Go back to GENERIC then, or add back the differences until you find the one you incorrectly removed. Kris pgp7xXBSRAGkP.pgp Description: PGP signature
Re: kernel build fails at 6.0-release!
Giorgos Kapetanakis wrote this message on Fri, Nov 11, 2005 at 23:41 +0200: I just can't build my kernel. I tried several changes at the config file, but I always get the same message. #device ether # Ethernet support (commented out this at v.1.0!!) You need this device!! You can't compile the ethernet drivers w/o this... - linking kernel.debug if.o(.text+0x35a0): In function `if_setlladdr': /usr/src/sys/net/if.c:2152: undefined reference to `arp_ifinit' *** Error code 1 Stop in /usr/obj/usr/src/sys/DEEPBLACK. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. --- Can anyone help? Just use the GENERIC kernel next time... -- John-Mark Gurney Voice: +1 415 225 5579 All that I will do, has been done, All that I have, has not. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6-STABLE TCP nfs Linux client hangs (UPDATE)
On Fri, 2005-11-11 at 11:24 -0800, Sean McNeil wrote: I have a 2x Athlon running with amd64 kernel and I can hang 2 Linux clients by attempting to write large amounts of data over TCP nfs. If I set the nfsd to be UDP only, the problem never occurs. Please let me know what I can do to help track this problem down. It appears that the above isn't the case. I managed to get a failure of nfs in UDP mode as well. I got some messages about jumbo frames that didn't make sense coming from the NIC when that happened and some corruption of files. I believe there is an issue with mpsafe on the sk0 nic. Turning off debug.mpsafenet (i.e. setting to 0) seems to have resolved the issue for me at the moment. Sean ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
all your hopes are dashed
5.4 recent Nov 11 17:00:38 psg kernel: __ Nov 11 18:12:52 psg kernel: __ that's novel! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gnome-upgrade.sh
On Friday 11 November 2005 07:23, Jan Grant wrote: On Fri, 11 Nov 2005, Michael C. Shultz wrote: One last thing, if you make a script that does the conversion, might I have a copy? Here is how I'll set up pm-020.conf to work: Surely. pkgtools.conf is actually a ruby script: I've no idea how dynamically the rules are evaluated but something that works ona prettystock bunch of settings should be close to trivial. Thank you. If it works well I might use it to have portmanager pick up settings from portupgrade on the fly, or at least provide some sort of conversion command. Thanks :) Attached uses ruby to parse the pkgtools.conf (it relies on the portupgrade ruby package) - it'll spit out the appropriate sections (HOLD_PKGS, BEFOREBUILD, AFTERINSTALL and MAKE_ARGS) in what I think the portmanager format is (although the script is trivial, as you can see). Note that the MAKE_ARGS etc go through a hash/dictionary and consequently are unordered. A small snippet of the output I get from this: [[[ CATEGORY/PORT|OPTION=| # do not delete this line! # Ignored packages from HOLD_PKGS IGNORE|bsdpan-*| IGNORE|x11/nvidia-driver| IGNORE|editors/openoffice*| # STOP entries come from BEFOREBUILD # START entries come from AFTERINSTALL START|/databases/postgresql7 chmod a+x /usr/local/share/postgresql/502.pgsql| START|/www/jakarta-tomcat5 chmod a-x /usr/local/etc/rc.d/020.jakarta-tomcat*.sh| # Package options from MAKE_ARGS # Note: pkgtools.conf will use the UNION of all matching lines security/gnupg|WITH_SUID_GPG=yes| devel/subversion|WITH_PYTHON=yes WITH_MOD_DAV_SVN=yes WITHOUT_BDB=yes| x11/kde3|| deskutils/kdepim3|WITH_KPILOT=yes| www/gallery|| www/rt*|WITH_FASTCGI=yes WITH_APACHE2=yes DB_TYPE=Pg DB_HOST=localhost DB_DATABASE=rt3 DB_USER=rt3| www/apache2|WITH_PROXY_MODULES=yes| multimedia/kdemultimedia*|WITH_LAME=yes WITH_XINE=yes WITH_MPEGLIB=yes| */*|BATCH=yes| java/jdk14|NATIVE_BOOTSTRAP=yes JAVA_HOME=| */kde*|WITH_KDE_DEBUG=yes| mail/exim|WITH_EXIMON=yes WITH_EXISCAN_ACL=yes WITH_TCP_WRAPPERS=yes WITH_PGSQL=yes WITHOUT_PERL=yes | ]]] Hey Jan, May I have a copy of your pkgtools.conf for testing purposes? Barring no more bugs to squash I'd like to start incorporating your script into portmanager tomorrow. I've decided to make a WITH_PKGTOOLS_CONF knob so if people compile that way portmanager just loads pkgtools.conf when it starts (using your script to do the translation). There will also be a command line switch that lets people use your script to add pkgtools.conf to the end of pm-020.conf if they prefer to go that way. -Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ahd0: Invalid Sequencer interrupt occurred.
On Nov 11, 2005, at 12:51 , Amit Rao wrote: 0) Upgrade to Seagate 10K.7 drive firmware level 0008. That seems to help. One ahd sequencer error message still appears at boot, but after that it seems to work (with your fingers crossed). Of course, you then spend far too much time ensuring that any replacement drives are flashed appropriately (which, afaict, *requires* Windows to do), and also running the gauntlet of further problems down the road when you throw the drives into a new machine with a subtly different HBA bios. No thanks, I'll stick with option (2). A few more months, and Seagate drives will be a nice distant memory that I can look back on in a few years, and laugh nervously about. -aDe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ahd0: Invalid Sequencer interrupt occurred.
Ade Lovett wrote this message on Fri, Nov 11, 2005 at 22:57 -0800: On Nov 11, 2005, at 12:51 , Amit Rao wrote: 0) Upgrade to Seagate 10K.7 drive firmware level 0008. That seems to help. One ahd sequencer error message still appears at boot, but after that it seems to work (with your fingers crossed). Of course, you then spend far too much time ensuring that any replacement drives are flashed appropriately (which, afaict, *requires* Windows to do), and also running the gauntlet of further problems down the road when you throw the drives into a new machine with a subtly different HBA bios. obviously you haven't done any research or even talked with Seagate about this issue... Seagate has a Linux version of their Seagate Enterprise Utility that allows you to flash their drives... /me having had issues with the drives and successfully flashed drives w/o using Windows. -- John-Mark Gurney Voice: +1 415 225 5579 All that I will do, has been done, All that I have, has not. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ahd0: Invalid Sequencer interrupt occurred.
On Nov 11, 2005, at 23:10 , John-Mark Gurney wrote: obviously you haven't done any research or even talked with Seagate about this issue... Seagate has a Linux version of their Seagate Enterprise Utility that allows you to flash their drives... Yes, I have done plenty of research with Seagate, Adaptec, and a number of VARs. Edit your kernel config, add: options KVA_PAGES=384 (for a 2.5G/1.5G kernel/userland split, as opposed to 2G/2G) recompile, install, watch the linuxulator explode in a frenzy. I have absolutely no interest in putting Linux (or, indeed, anything *but* FreeBSD) on my production boxes. -aDe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
