Re: HELP! core dumps: install, mtree, et cetera all of the sudden after portmaster security/cyrus-sasl2
On 08/16/12 17:44, Glen Barber wrote: > On Thu, Aug 16, 2012 at 05:33:20PM +0200, Hartmann, O. wrote: >> >> I ran into a very delicate and nasty situation. >> >> On several boxes, FreeBSD 9.1-PRE and FreeBSD 10-CURRENT (build of >> CURRENT sources from yesterday, r239295 Wed August 15 17:04:51 CEST 2012 >> amd64, I had to recompile all requirements of port Apache22, since after >> the port update it core dumped. >> >> On FreeBSD 9.1-PRE, with pkg(ng), things went well. Recompilation and >> installation of all "portmaster -f apache-2.2" requirements went perfect. >> >> On both FreeBSD 10-CURRENT boxes it ended up in a mess, all of a >> sudden(!), while reinstalling port security/cyrus-sasl2, things started >> to fail in a dramatik way! >> >> On both FBSD 10 boxes, the installation of the port security/cyrus-sasl2 >> got corrupted by "install" and/or "mtree" dumping core and signalling >> SIGNAL 11. Booting into multiuser mode is impossible, login core dumps >> SIGNAL 11, many other daemons, too. The only way is to boot into single >> user mode. >> >> An installation failed due to pkg(ng) was missing libarchive.so via > > There is pkg-static for recovering in this type of situation. Oh ... I'm new to pkg(ng). > >> portmaster or via core dumping install(1). By installing on one box, my >> home box, port security/cyrus-sasl2 manually, luckily install(1) and >> mtree(1) didn't coredump and it worked - and this precedure rescued me. >> But on my lab's development box, it doesn't work! >> >> On this specific box, where this nasty problem also occured the same way >> by simply recompiling everything for port www/apache22, including the >> reinstallation of port security/cyrus-sasl2. Nearly every binary is >> suddenly coredumping (as on the home box). login, vi, install, devfs, >> syslogd, mtree, id, find ... a whole lot of binaries seem to be >> compromised by something I do not see (libsasl2.so perhaps?). >> >> I tried to help myself via copying /rescue/vi to /usr/bin/vi to have at >> least a working vi. But in /rescue, I can not find install or mtree. I'm >> not familiar with the sophisticated ways of /rescue. Where are >> install(1) and mtree(1)? >> >> Trying to reinstall security/cyrus-sasl2 from single-user fails due >> install coredumps. pkg(ng) fails due to missing libpkg.so.5 and even >> rejects being reinstalled. But /usr/local/lib/libpkg.so.0 is even there! >> Disabling the use of pkg with commenting out WITH_PKGNG=yes in >> /etc/make.conf leads to the above issues with mtree and install. >> Disabling this pkgng tag leads to reinstallation of missing packages, >> which are store in the pkgng sqlite format and not as ASCII anymore, but >> then I get >> /var/runld-elf.so.hints: No such file or directory > > Is this a typo, or literal transcription? (The missing "/" between > 'run' and 'ld-elf.so.hints', that is.) A typo, sorry. I had to type it from the screen of the broken box to the laptop. > >> Error: shared library "iconv.3" does not exist. >> >> But most of the libs have never been touch! So what is the loader >> complaining about? >> >> Well, I'm floating like a dead man in the water and I'm glad that one >> box survided although suffering from the same symptomes. >> >> I tried to find rescue images and a rescue DVD of a snap shot server, >> but there is no way to crawl through the informations on the web pages >> towards a snapshot. All folders end up in 2011 and highly outdated >> (www.freebsd.org, I didn't look at mirrors since I thought the main >> server carries the most recent stuff). This isn't funny. No lead, no >> hint, even in the download section. >> > > Yes, I have been complaining about this for a while now... This is a so unneccessary issue. Why are people bothering themselfs with hiding a bit of information? If one isn't a cold-blood developer aware of all the neat knobs of FBSD and where to ask and where to look, a novice or not-so-well-informed guy like me run into frustration. The main page should have a hint present, where to find the newest stuff. Leaving the officiela page the way it is at the moment in this specific issue, it looks a bit "unmaintained" ... > >> If someone has some hints how to recompile the sources with an emergency >> booted disk, I highly appreciate some desater advice. Maybe the release >> of FreeBSD-10-CURRENT sources I compiled do have accidentally a nasty >> bug, so it would be nice to update the sources and have a complete >> recompilation done. >> > > If you can get booted into a recovery medium, you can mount /usr/src and > /usr/obj from the hosed system, and should be able to > installworld/installkernel into the hosed system with DESTDIR set. > > Glen > I do this the very moment with the RELEASE CD I found at allbsd.org for the most recent FBSD 10.0-CURRENT as from 16.08.2012. I try to build the sources and install them into the mounted DESTDIR. Oliver ___ freebsd-questions@freebsd.org
Re: HELP! core dumps: install, mtree, et cetera all of the sudden after portmaster security/cyrus-sasl2
On Fri, Aug 17, 2012 at 09:44:40AM +0200, Hartmann, O. wrote: > >> An installation failed due to pkg(ng) was missing libarchive.so via > > > > There is pkg-static for recovering in this type of situation. > > Oh ... I'm new to pkg(ng). > No worries. It is a nice thing to know about, since after a big shlib bump during an upgrade, if all else is broken, you can still at least get /rescue stuff and pkg-static to upgrade third party software. > >> If someone has some hints how to recompile the sources with an emergency > >> booted disk, I highly appreciate some desater advice. Maybe the release > >> of FreeBSD-10-CURRENT sources I compiled do have accidentally a nasty > >> bug, so it would be nice to update the sources and have a complete > >> recompilation done. > >> > > > > If you can get booted into a recovery medium, you can mount /usr/src and > > /usr/obj from the hosed system, and should be able to > > installworld/installkernel into the hosed system with DESTDIR set. > > > > I do this the very moment with the RELEASE CD I found at allbsd.org for > the most recent FBSD 10.0-CURRENT as from 16.08.2012. I try to build the > sources and install them into the mounted DESTDIR. > I have lately been creating memstick images for this exact type of thing. On -CURRENT and 9-STABLE, you can do: # make -C /usr/src buildworld buildkernel # make -C /usr/src/release NOSRC=yes NODOCS=yes NOPORTS=yes memstick Then take the resulting memory stick image to use for recovery. Glen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Fwd: docs
--- Пересылаемое сообщение --- От: "кузнецов иван" Кому: freebsd-questions@freebsd.org Копия: Тема: docs Дата: Tue, 14 Aug 2012 10:45:13 +0400 how to open RU_FREEBSD_DOC_20111014.TBZ under windows? several program cant,i was attempt.7zip cant. -- Написано в почтовом клиенте браузера Opera: http://www.opera.com/mail/___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
docs
how to open RU_FREEBSD_DOC_20111014.TBZ under windows? several program cant,i was attempt.7zip cant. -- Написано в почтовом клиенте браузера Opera: http://www.opera.com/mail/___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
doc
how to open RU_FREEBSD_DOC_20111014.TBZ under windows? several program cant,i was attempt.7zip cant. why i not able read documentation BEFORE install? where it after install? second,you installer is not well, not very undersandingable for newbis.i mean user must hit tab in some dialogs,but he press enter - attempt please.it is not MISTAKE but look mysteriously,and user worry.you shoud do only one small step in order to do freebsd more frendly - publish full international docs on install dvd -- user only put dvd and see docs in browser.its simpler than rewriting os in order to div it more frendly.is it true flash work badly or after complex work? i cant write on my writemaster dvd drive with freebsd9 - brasero dont see drive.what you can say about it? with best regards,ivan,Russia,Moscow. иван кузнецов. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: docs
2012/8/17 кузнецов иван > > > > --- Пересылаемое сообщение --- > От: "кузнецов иван" > Кому: freebsd-questions@freebsd.org > Копия: > Тема: docs > Дата: Tue, 14 Aug 2012 10:45:13 +0400 > > > > how to open RU_FREEBSD_DOC_20111014.TBZ under windows? several program > cant,i was attempt.7zip cant. > > Please try powerarchiver > > -- > Написано в почтовом клиенте браузера Opera: http://www.opera.com/mail/ > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" -- with kind regards ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Firefox 14.0.1 won't build under 8.3 on amd64
== John Levine wrote on Mon 13.Aug'12 at 5:41:52 - == > Oops, it's 14.0.1 I'm trying to build. 13.0.0.1 is what I have installed now. > > In article <20120813053621.24629.qm...@joyce.lan> you write: did you select the option to use optimised CFLAGS when you run make config in the port directory? I remember I had this problem on 8.2 earlier this year/last year and deselecting that option made it build. I don't know if that has been fixed/changed since I built that port and it was for an earlier version of firefox. I recall the same was true for Thunderbird at that time. You try that first? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: freebsd-update and csup - I'm going around in circles.
On Fri, 17 Aug 2012 01:48:18 +0200, Polytropon wrote: < snip problem and comprehensive answer > That's really helpful. Very many thanks, Polytropon. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
ToS marking in pf
Hi list! Could you please point me how can I set DSCP/TOS bits for outgoing packets using pf ? I would like to mark all packets going to the specific port marked with DSCP CS3. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 9.0 release hang in quiescent X
On 08/16/12 00:04, Matthew Seaman wrote: > On 16/08/2012 05:45, Gary Aitken wrote: ... >> Running 9.0 release on an amd 64 box, standard kernel, 16GB, SSD (/, >> /usr, /var, /tmp) + HDDs, visiontek 900331 graphics card (ati radeon >> hd5550). >> >> As long as I am using the system, things seem to be fine. However, >> when I leave the system idle for an extended period of time (e.g. >> overnight, out for the day, etc.), it often refuses to return from >> whatever state it is in. The screen is blank and in standby for >> power saving, and Fn won't get me a console prompt. The >> only way I know to recover is to power off and reboot. ... >> Can someone suggest a good way to proceed to figure out what's going >> on? > > Can you get network access to the machine when it gets into this state? I enabled remote logins and when the system hangs, I can neither log in nor ping it. I can do both of those prior to a hang. > If you can't, that suggests the OS is hanging or crashing, possibly in > response to going into some sort of power-saving mode. > > As to working out what the underlying cause of the problem is: that's > harder. I'd try experimenting with the power saving settings for your > graphics display. If you can turn them off as a test, and the machine > then survives for an extended period of idleness, you'll have gone a > long way towards isolating the problem. My display, a NEC multisync LCD 1970NX, has a menu item for "Off Timer" but it is set to "off" As far as I can tell there are no other power saving options on the display itself. Could this be related to the sync rates? I'm using whatever X.org and the drivers decided to come up with, which is 63.9kHz H, 59.9Hz V. I have the following in rc.conf: powerd_enable="YES" # Run powerd to lower our power usage. powerd_flags="-a hiadaptive -n hiadaptive -p 250" I presume screen blanking is independent of cpu frequency rates, but it's not clear to me how the screen blanking is controlled. How does screen blanking interact with BIOS? My screen blanks, but it's not clear to me if it's BIOS or the os that's doing it. man acpi indicates acpi should not be disabled: "Disabling all or part of ACPI on non-i386 platforms (i.e., platforms where ACPI support is mandatory) may result in a non-functional system." On 08/16/12 00:06, Steve O'Hara-Smith wrote: > Are you running any kind of screensaver ? > Sometimes the OpenGL screen saver modules crash without proper > hardware support. If you're running a screensaver try disabling it and just > using display blanking. I'm not running a screensaver, just blanking the screen. Gary ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
fsck recoveries, configuration
When my system hangs and I have to force it to power cycle, I sometimes have some fsck issues. So some questions: 1. It appears to me that the file system (ufs) is not writing stuff out when things are idle. If I do a sync manually and leave the machine idle and it crashes later, it comes up clean. If I don't do a sync manually and it crashes later, it often comes up needing fsck. Is there a way to configure the filesystem to cache but still write cached stuff at low priority? 2. When my machine hung (could not rlogin or ping), I powered off and rebooted. Reboot did a deferred fsck. After it booted I logged in, and also logged in on another system. On the remote system I could do a ping but rlogin returned "connection reset by peer", even though I could log in locally. I presume that is because the background fscks were not complete? I then did a ps ax | grep fsck and saw only the "logger" process for the deferred fsck's. I did a man logger which appeared to hang -- no output. I'm guessing because it needed the filesystems which hadn't yet fsck'd. I then attempted to switch consoles using fn but could not. I then attempted to kill the man logger process using ^C with no success. Can someone shed light on the above sequence of events? It's highly likely some of them occurred before the 60 second delay for fsck timed out, but I'd like to understand what the heck is going on. Thanks, Gary ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 9.0 release hang in quiescent X
On Fri, 17 Aug 2012, Gary Aitken wrote: On 08/16/12 00:04, Matthew Seaman wrote: On 16/08/2012 05:45, Gary Aitken wrote: ... Running 9.0 release on an amd 64 box, standard kernel, 16GB, SSD (/, /usr, /var, /tmp) + HDDs, visiontek 900331 graphics card (ati radeon hd5550). As long as I am using the system, things seem to be fine. However, when I leave the system idle for an extended period of time (e.g. overnight, out for the day, etc.), it often refuses to return from whatever state it is in. The screen is blank and in standby for power saving, and Fn won't get me a console prompt. The only way I know to recover is to power off and reboot. ... Can someone suggest a good way to proceed to figure out what's going on? Can you get network access to the machine when it gets into this state? I enabled remote logins and when the system hangs, I can neither log in nor ping it. I can do both of those prior to a hang. If you can't, that suggests the OS is hanging or crashing, possibly in response to going into some sort of power-saving mode. As to working out what the underlying cause of the problem is: that's harder. I'd try experimenting with the power saving settings for your graphics display. If you can turn them off as a test, and the machine then survives for an extended period of idleness, you'll have gone a long way towards isolating the problem. My display, a NEC multisync LCD 1970NX, has a menu item for "Off Timer" but it is set to "off" As far as I can tell there are no other power saving options on the display itself. Could this be related to the sync rates? I'm using whatever X.org and the drivers decided to come up with, which is 63.9kHz H, 59.9Hz V. I have the following in rc.conf: powerd_enable="YES" # Run powerd to lower our power usage. powerd_flags="-a hiadaptive -n hiadaptive -p 250" I presume screen blanking is independent of cpu frequency rates, but it's not clear to me how the screen blanking is controlled. How does screen blanking interact with BIOS? My screen blanks, but it's not clear to me if it's BIOS or the os that's doing it. Yes, screen blanking is unrelated to current CPU speed. powerd is probably not responsible. The first test would be just to disable screen blanking in X: In xorg.conf, ServerLayout section: Option "BlankTime" "0" Option "StandbyTime" "0" Option "SuspendTime" "0" Option "OffTime" "0" If that stops the lockups, then you could try setting each in turn to a non-zero value (minutes). Leave everything at zero except for the one being tested. But these also seem unlikely, as it's a hardware signal from the video board to the monitor. The suggestion of an X screensaver causing the lockup was excellent. Even if you have no screensavers, there are other things that could be triggered, like xlock. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
handbook pkg name
What is the pkg name of the English version of 9.0 handbook? Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: handbook pkg name
On Fri, 17 Aug 2012 16:48:24 -0400, Fbsd8 wrote: > What is the pkg name of the English version of 9.0 handbook? It should be "en-freebsd-doc" or "freebsd-doc-en". -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 9.0 release hang in quiescent X
On 08/17/12 14:44, Warren Block wrote: > If that stops the lockups, then you could try setting each in turn to a > non-zero value (minutes). Leave everything at zero except for the one being > tested. But these also seem unlikely, as it's a hardware signal from the > video board to the monitor. The suggestion of an X screensaver causing the > lockup was excellent. Even if you have no screensavers, there are other > things that could be triggered, like xlock. Not sure I understand what you're getting at. By "other things that could be triggered" what do you mean? e.g. xclock obviously gets "triggered" at least once per minute; you're suggesting that event could be causinging an update request while blanked out that is causing trouble? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: fsck recoveries, configuration
On Fri, 17 Aug 2012 14:19:07 -0600, Gary Aitken wrote: > 1. It appears to me that the file system (ufs) is not writing > stuff out when things are idle. If I do a sync manually and > leave the machine idle and it crashes later, it comes up clean. > If I don't do a sync manually and it crashes later, it often > comes up needing fsck. Is there a way to configure the filesystem > to cache but still write cached stuff at low priority? Note that even if the OS orders a data write, it's up to the disk driver to actually tell the disk to do it. And the disk then _has_ to do it. There is no real "connection" (in time) for those components of the "task line", even though one would assume that they happen immediately. On a somewhat idle system, you could keep a process (e. g. top -S) running to check system processes that could be responsible for writes (or missing writes). > 2. When my machine hung (could not rlogin or ping), I powered > off and rebooted. Does the machine have a "soft power button" and it is configured to issue a "shutdown -p now" (which is quite common)? When you have access to the machine, try that. Even if the machine does not accept network logins, this mechanism might still work. > Reboot did a deferred fsck. Is this intended? Personally, I'd rather wait some time to boot in a fully checked file system environment then dealing with the uncertain situation of snapshots and background FS check activity. In worst case, I want to be prompted by fsck if a major defect has been found that requires administrator attention. Put background_fsck="NO" into /etc/rc.conf to get this behaviour. Note that as long as fsck is running, you can't enter any interactive commands, and it will happen _prior_ to allowing any network connections. Also note that this is in single user mode, so you can't switch VTs. > After it booted I logged in, and also logged in on another system. > On the remote system I could do a ping but rlogin returned > "connection reset by peer", even though I could log in locally. Does rlogin work when you "give the system some time to recover"? > I presume that is because the background fscks were not complete? Possible. Background fsck is uncertain per se, so for diagnostics better leave it aside and use the maybe "less comfortable" method. This is easy when you have local access to the machine in question. > I then did a > ps ax | grep fsck > and saw only the "logger" process for the deferred fsck's. > I did a > man logger > which appeared to hang -- no output. I'm guessing because it needed > the filesystems which hadn't yet fsck'd. Just a guess: Maybe you're experiencing a file system defect and fsck, even though running in background, needs an input? I'm not really sure about this, because I'm _intendedly_ not using fsck that way. > I then attempted to switch consoles using > fn > but could not. That would imply you're still stuck in SUM. A strange constellation given that it appears that you have fsck running in background. > I then attempted to kill the man logger process using ^C with no success. Waiting / hanging process? > Can someone shed light on the above sequence of events? It's highly > likely some of them occurred before the 60 second delay for fsck > timed out, but I'd like to understand what the heck is going on. Try to construct a more _defined_ situation for further diagnostics. Also you could boot the system up in SUM (use "boot -s") and then perform fsck manually, just to make sure your disks are fine. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: doc
On Fri, 17 Aug 2012 13:17:42 +0400, иван кузнецов wrote: > how to open RU_FREEBSD_DOC_20111014.TBZ under windows? The file is a tar archive compressed with BZip2. It's no real surprise that "Windows" cannot natively handle it, as with many established standard formats. :-) > several program cant,i was attempt.7zip cant. It's not a 7zip archive; still the 7zip page on http://7-zip.org/ mentions that the BZip2 format is supported. However, there's BZip2 available for "Windows", maybe this can help you: http://gnuwin32.sourceforge.net/packages/bzip2.htm There are also claims that "WinRAR" is able to extract BZip2 files. > why i not able read documentation BEFORE install? I'd refer to the documentation presented on FreeBSD's web page. You can easily create a local copy of the HTML subtree using wget (and yes, there's WGET.EXE even for "Windows"). The most important pages are: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ http://www.freebsd.org/doc/faq/ Check out FreeBSD's main web page for language selection. Here you can find a russian translation of all those documents: http://www.freebsd.org/ru/docs.html Again, it's possible to make a local copy of them which you could carry on a USB stick or CD for further reference. > where it after install? It will be installed into /usr/doc, containing the language variants and formats. > second,you installer is not well, not very undersandingable for newbis. I don't think so. It's very precise in wording and easy to use. You just have to read what's on the screen and answer accordingly. A help function is also included. > i mean user must hit tab in some dialogs,but he press enter - > attempt please. The keyboard support is explained in the first help pages. It's also mentioned in the Handbook which one should read before or even while performing the install (if one is unsure about how the interface works). > it is not MISTAKE but look mysteriously,and user worry. That's quite possible. :-) Users feeling unhappy with the FreeBSD installer often tend to prefer PC-BSD with its GUI installer and a more lengthly "step by step" guide through the installation with much more interactivity and user attention. As this interface can be used with a mouse, the distinction between TAB and ENTER is not that important anymore. > you shoud do only one small step in order to do freebsd more > frendly - publish full international docs on install dvd -- > user only put dvd and see docs in browser. How is a user supposed to have a browser available when putting the CD into a system he wants to install it on, with _nothing_ on the hard disk? I agree that the documentation could be accessible via a web browser from the install media when used in a _different_ computer, and maybe it should also be accessible in text form during an early stage of the installer. However, the purpose of an installation medium is to install something. The installer does exactly that. > its simpler than rewriting os in order to div it more frendly. The OS has basically nothing to do with its installer or the way help is presented to the user. This is done by programs, _those_ could be extended or changed. > is it true flash work badly or after complex work? No. Outdated stuff like "Flash" can be quickly and easily installed, and it works reliably and stable. > i cant write on my writemaster dvd drive with freebsd9 - brasero > dont see drive. Can you provide more information, e. g. what model, how connected, output of dmesg and so on? Please check the Handbook regarding the use of optical media. Start with "low level diagnostics" (i. e. use OS tools to first check if the drive is detected and attached to the correct driver), in a next step maybe check your Gnome and Brasero configuration. If it fails, try a command line tool. Those are typically easier to use and more comfortable. > what you can say about it? with best regards,ivan,Russia,Moscow. MHOrO YCnEXOB! ;-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 9.0 release hang in quiescent X
On Fri, 17 Aug 2012, Gary Aitken wrote: On 08/17/12 14:44, Warren Block wrote: If that stops the lockups, then you could try setting each in turn to a non-zero value (minutes). Leave everything at zero except for the one being tested. But these also seem unlikely, as it's a hardware signal from the video board to the monitor. The suggestion of an X screensaver causing the lockup was excellent. Even if you have no screensavers, there are other things that could be triggered, like xlock. Not sure I understand what you're getting at. By "other things that could be triggered" what do you mean? e.g. xclock obviously gets "triggered" at least once per minute; you're suggesting that event could be causinging an update request while blanked out that is causing trouble? Other long-term events that happen might be to blame, not related to screen blanking at all. For example, a cron job. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 9.0 release hang in quiescent X
On Aug 17, 2012, at 7:00 PM, Warren Block wrote: > On Fri, 17 Aug 2012, Gary Aitken wrote: > >> On 08/17/12 14:44, Warren Block wrote: >> >>> If that stops the lockups, then you could try setting each in turn to a >>> non-zero value (minutes). Leave everything at zero except for the one >>> being tested. But these also seem unlikely, as it's a hardware signal from >>> the video board to the monitor. The suggestion of an X screensaver causing >>> the lockup was excellent. Even if you have no screensavers, there are >>> other things that could be triggered, like xlock. >> >> Not sure I understand what you're getting at. By "other things that could >> be triggered" what do you mean? e.g. xclock obviously gets "triggered" at >> least once per minute; you're suggesting that event could be causinging an >> update request while blanked out that is causing trouble? > > Other long-term events that happen might be to blame, not related to screen > blanking at all. For example, a cron job. Just as a data point, I had the same thing happen on PC-BSD 9.0. The system would hang after just a couple minutes of inactivity, but would wake up again on keyboard input. Top showed X.org taking 100% of CPU and load averages got up to some seriously ridiculous levels. The workaround I found was to turn off the "Dim Screen" option in KDE. Never filed a bug report, since I didn't know if it was FreeBSD, PC-BSD or X.org. OK, MCN___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: fsck recoveries, configuration
On 08/17/12 19:05, Polytropon wrote: >> 2. When my machine hung (could not rlogin or ping), I powered >> off and rebooted. > > Does the machine have a "soft power button" and it is configured > to issue a "shutdown -p now" (which is quite common)? When you > have access to the machine, try that. Even if the machine does > not accept network logins, this mechanism might still work. Hmmm. It has a "soft" power button; have to hold it down 5 sec or so to power off. Those things can be configured to issue a command that will actually get executed without a login? I assume you're talking about a bios option? How does that work? sounds like magic of some sort... Or is this a whole login sequence with the shutdown at the end? >> Reboot did a deferred fsck. > > Is this intended? Personally, I'd rather wait some time to boot > in a fully checked file system environment then dealing with the > uncertain situation of snapshots and background FS check activity. > In worst case, I want to be prompted by fsck if a major defect has > been found that requires administrator attention. > > Put > > background_fsck="NO" > > into /etc/rc.conf to get this behaviour. Yeah, I came to that conclusion... Thanks. >> After it booted I logged in, and also logged in on another system. >> On the remote system I could do a ping but rlogin returned >> "connection reset by peer", even though I could log in locally. > > Does rlogin work when you "give the system some time to recover"? yes, if it's not hung -- i.e. done with fsck, I think. I verified that by monitoring the delayed fsck process and as soon as it was done the rlogin worked. >> I then attempted to switch consoles using >>fn >> but could not. > > That would imply you're still stuck in SUM. A strange constellation > given that it appears that you have fsck running in background. > It seems to me this is always the case -- delayed fsck waits 60 seconds by default to start. During that time the system has come up multi-user, so it's trivial to be logged in under multi-user mode with fsck running. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 9.0 release hang in quiescent X
On 08/17/12 20:29, Matthew Navarre wrote: > > > On Aug 17, 2012, at 7:00 PM, Warren Block wrote: > >> On Fri, 17 Aug 2012, Gary Aitken wrote: >> >>> On 08/17/12 14:44, Warren Block wrote: >>> If that stops the lockups, then you could try setting each in turn to a non-zero value (minutes). Leave everything at zero except for the one being tested. But these also seem unlikely, as it's a hardware signal from the video board to the monitor. The suggestion of an X screensaver causing the lockup was excellent. Even if you have no screensavers, there are other things that could be triggered, like xlock. >>> >>> Not sure I understand what you're getting at. By "other things that could >>> be triggered" what do you mean? e.g. xclock obviously gets "triggered" at >>> least once per minute; you're suggesting that event could be causinging an >>> update request while blanked out that is causing trouble? >> >> Other long-term events that happen might be to blame, not related to screen >> blanking at all. For example, a cron job. > > Just as a data point, I had the same thing happen on PC-BSD 9.0. The system > would hang after just a couple minutes of inactivity, but would wake up again > on keyboard input. Top showed X.org taking 100% of CPU and load averages got > up to some seriously ridiculous levels. The workaround I found was to turn > off the "Dim Screen" option in KDE. Never filed a bug report, since I didn't > know if it was FreeBSD, PC-BSD or X.org. That's not my issue; what I'm seeing is a screen that never wakes up; or, more accurately, a system which appears to have crashed completely, since I can't rlogin either. I would guess the high load averages you saw may be related to everything in the world woken up at the same time for repaints. I would expect x.org to take 100% of cpu when woken up. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: fsck recoveries, configuration
On Fri, 17 Aug 2012 20:44:10 -0600, Gary Aitken wrote: > On 08/17/12 19:05, Polytropon wrote: > >> 2. When my machine hung (could not rlogin or ping), I powered > >> off and rebooted. > > > > Does the machine have a "soft power button" and it is configured > > to issue a "shutdown -p now" (which is quite common)? When you > > have access to the machine, try that. Even if the machine does > > not accept network logins, this mechanism might still work. > > Hmmm. It has a "soft" power button; have to hold it down 5 sec > or so to power off. That's the "override time" for a "hard power off". If you only press it once, it should issue "shutdown -p now", but of course this only works if the system is still responding. Even if the keyboard input and screen output, as well as networking services stopped to work, this _might_ still be effective. > Those things can be configured to issue a command that will actually > get executed without a login? Sure, it has been working for many years. Check the BIOS setup, some machines can be configured to what the button does. The default setup of FreeBSD should perform the correct action via ACPI. In the past, it also worked with APM. In that case, /etc/apmd.conf would contain the command executed when the button was pressed. On APM-capable machines, the PSU would be switched off, just like today's ACPI-based systems. Of course that only works with ATX power supplies, the AT ones usually had a mechanical switch. > I assume you're talking about a bios option? How does that work? I've seen BIOS setups allowing different actions for the button, from "go to sleep" to "soft power off" or "hard power off". That action (hard power off) is taken when pressing the button for about 5 seconds. The OS can NOT deal with that case. > sounds like magic of some sort... Or is this a whole login > sequence with the shutdown at the end? No, it's a system action using ACPI. No magic involved. :-) > >> Reboot did a deferred fsck. > > > > Is this intended? Personally, I'd rather wait some time to boot > > in a fully checked file system environment then dealing with the > > uncertain situation of snapshots and background FS check activity. > > In worst case, I want to be prompted by fsck if a major defect has > > been found that requires administrator attention. > > > > Put > > > > background_fsck="NO" > > > > into /etc/rc.conf to get this behaviour. > > Yeah, I came to that conclusion... Thanks. I _know_ booting a system may take time when the file system needs repair, but you have to set your priorities: I prefer waiting 20 minutes instead of running stuff on a damaged file system. > >> After it booted I logged in, and also logged in on another system. > >> On the remote system I could do a ping but rlogin returned > >> "connection reset by peer", even though I could log in locally. > > > > Does rlogin work when you "give the system some time to recover"? > > yes, if it's not hung -- i.e. done with fsck, I think. I verified > that by monitoring the delayed fsck process and as soon as it was > done the rlogin worked. It seems that background fsck stops certain services from working... interesting; another reason for me to avoid it when possible. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: fsck recoveries, configuration
On 08/17/12 21:17, Polytropon wrote: > On Fri, 17 Aug 2012 20:44:10 -0600, Gary Aitken wrote: >> On 08/17/12 19:05, Polytropon wrote: 2. When my machine hung (could not rlogin or ping), I powered off and rebooted. >>> >>> Does the machine have a "soft power button" and it is configured >>> to issue a "shutdown -p now" (which is quite common)? When you >>> have access to the machine, try that. Even if the machine does >>> not accept network logins, this mechanism might still work. >> >> Hmmm. It has a "soft" power button; have to hold it down 5 sec >> or so to power off. > > That's the "override time" for a "hard power off". If you only > press it once, it should issue "shutdown -p now", but of course > this only works if the system is still responding. Even if the > keyboard input and screen output, as well as networking services > stopped to work, this _might_ still be effective. >> Those things can be configured to issue a command that will actually >> get executed without a login? > > Sure, it has been working for many years. Check the BIOS setup, > some machines can be configured to what the button does. The > default setup of FreeBSD should perform the correct action via > ACPI. > > In the past, it also worked with APM. In that case, /etc/apmd.conf > would contain the command executed when the button was pressed. > On APM-capable machines, the PSU would be switched off, just like > today's ACPI-based systems. Of course that only works with ATX > power supplies, the AT ones usually had a mechanical switch. Ah, I see. The driver raises a signal the system can respond to. >> I assume you're talking about a bios option? How does that work? > > I've seen BIOS setups allowing different actions for the button, > from "go to sleep" to "soft power off" or "hard power off". That > action (hard power off) is taken when pressing the button for > about 5 seconds. The OS can NOT deal with that case. > >> sounds like magic of some sort... Or is this a whole login >> sequence with the shutdown at the end? > > No, it's a system action using ACPI. No magic involved. :-) I'll look at it next time I reboot. Reading the bios manual, it looks like acpi 2.0 support is disabled by default, which may be where it is; otherwise I don't see anything obvious. Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: fsck recoveries, configuration
On Fri, 17 Aug 2012 22:14:47 -0600, Gary Aitken wrote: > On 08/17/12 21:17, Polytropon wrote: > > On Fri, 17 Aug 2012 20:44:10 -0600, Gary Aitken wrote: > >> On 08/17/12 19:05, Polytropon wrote: > 2. When my machine hung (could not rlogin or ping), I powered > off and rebooted. > >>> > >>> Does the machine have a "soft power button" and it is configured > >>> to issue a "shutdown -p now" (which is quite common)? When you > >>> have access to the machine, try that. Even if the machine does > >>> not accept network logins, this mechanism might still work. > >> > >> Hmmm. It has a "soft" power button; have to hold it down 5 sec > >> or so to power off. > > > > That's the "override time" for a "hard power off". If you only > > press it once, it should issue "shutdown -p now", but of course > > this only works if the system is still responding. Even if the > > keyboard input and screen output, as well as networking services > > stopped to work, this _might_ still be effective. > > >> Those things can be configured to issue a command that will actually > >> get executed without a login? > > > > Sure, it has been working for many years. Check the BIOS setup, > > some machines can be configured to what the button does. The > > default setup of FreeBSD should perform the correct action via > > ACPI. > > > > In the past, it also worked with APM. In that case, /etc/apmd.conf > > would contain the command executed when the button was pressed. > > On APM-capable machines, the PSU would be switched off, just like > > today's ACPI-based systems. Of course that only works with ATX > > power supplies, the AT ones usually had a mechanical switch. > > Ah, I see. The driver raises a signal the system can respond to. Yes, it's typically done in the kernel (or by a kernel module). > >> I assume you're talking about a bios option? How does that work? > > > > I've seen BIOS setups allowing different actions for the button, > > from "go to sleep" to "soft power off" or "hard power off". That > > action (hard power off) is taken when pressing the button for > > about 5 seconds. The OS can NOT deal with that case. > > > >> sounds like magic of some sort... Or is this a whole login > >> sequence with the shutdown at the end? > > > > No, it's a system action using ACPI. No magic involved. :-) > > I'll look at it next time I reboot. Reading the bios manual, it > looks like acpi 2.0 support is disabled by default, which may be > where it is; otherwise I don't see anything obvious. Thanks. Also check the BIOS setup. In most cases, the default configuration will assign the button press to a "soft power down", raising the proper signal via ACPI. You can also check dmesg's output: acpi_button0: on acpi0 acpi_button1: on acpi1 I don't know where this 2nd button is on my system, it only has one which - when being pressed - lets the system shut down and then power off properly. You can find even more elaborate data in sysctl's output: hw.acpi.power_button_state: S5 hw.acpi.sleep_button_state: S3 dev.acpi_button.0.%desc: Power Button dev.acpi_button.0.%driver: acpi_button dev.acpi_button.0.%location: handle=\_SB_.PWRB dev.acpi_button.0.%pnpinfo: _HID=PNP0C0C _UID=0 dev.acpi_button.0.%parent: acpi0 dev.acpi_button.1.%desc: Sleep Button dev.acpi_button.1.%driver: acpi_button dev.acpi_button.1.%location: handle=\_SB_.SLPB dev.acpi_button.1.%pnpinfo: _HID=PNP0C0E _UID=0 dev.acpi_button.1.%parent: acpi0 dev.acpi_button.1.wake: 1 As I said, my system doesn't have that 2nd "sleep" button anywhere, but addressing the power button is correct, the S3 state explained as "Commonly referred to as Standby, Sleep, or Suspend to RAM. RAM remains powered" is then used as a signal to perform the system shutdown as intended. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: fsck recoveries, configuration
On 08/17/12 22:23, Polytropon wrote: > Also check the BIOS setup. In most cases, the default configuration > will assign the button press to a "soft power down", raising the > proper signal via ACPI. You can also check dmesg's output: > > acpi_button0: on acpi0 > acpi_button1: on acpi1 > > I don't know where this 2nd button is on my system, it only has > one which - when being pressed - lets the system shut down and > then power off properly. > > You can find even more elaborate data in sysctl's output: > > hw.acpi.power_button_state: S5 > hw.acpi.sleep_button_state: S3 > dev.acpi_button.0.%desc: Power Button > dev.acpi_button.0.%driver: acpi_button > dev.acpi_button.0.%location: handle=\_SB_.PWRB > dev.acpi_button.0.%pnpinfo: _HID=PNP0C0C _UID=0 > dev.acpi_button.0.%parent: acpi0 > dev.acpi_button.1.%desc: Sleep Button > dev.acpi_button.1.%driver: acpi_button > dev.acpi_button.1.%location: handle=\_SB_.SLPB > dev.acpi_button.1.%pnpinfo: _HID=PNP0C0E _UID=0 > dev.acpi_button.1.%parent: acpi0 > dev.acpi_button.1.wake: 1 > > As I said, my system doesn't have that 2nd "sleep" button anywhere, > but addressing the power button is correct, the S3 state explained > as "Commonly referred to as Standby, Sleep, or Suspend to RAM. RAM > remains powered" is then used as a signal to perform the system > shutdown as intended. Hmmm: acpi0: <030811 XSDT1017> on motherboard acpi0: Power Button (fixed) acpi0: reservation of fec0, 1000 (3) failed acpi0: reservation of fee0, 1000 (3) failed acpi0: reservation of ffb8, 8 (3) failed acpi0: reservation of fec1, 20 (3) failed acpi0: reservation of fed8, 1000 (3) failed acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, c7e0 (3) failed acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 acpi_ec0: port 0x62,0x66 on acpi0 pcib0: port 0xcf8-0xcff on acpi0 acpi_button0: on acpi0 attimer0: port 0x40-0x43 irq 0 on acpi0 atrtc0: port 0x70-0x71 irq 8 on acpi0 uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 hpet0: iomem 0xfed0-0xfed003ff on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 acpi_throttle0: on cpu0 Do all those reservation failed indicate the interrupt is not going to actually be seen? What does (fixed) mean? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: fsck recoveries, configuration
On Fri, 17 Aug 2012 23:53:55 -0600, Gary Aitken wrote: > Hmmm: > > acpi0: <030811 XSDT1017> on motherboard > acpi0: Power Button (fixed) > acpi0: reservation of fec0, 1000 (3) failed > acpi0: reservation of fee0, 1000 (3) failed > acpi0: reservation of ffb8, 8 (3) failed > acpi0: reservation of fec1, 20 (3) failed > acpi0: reservation of fed8, 1000 (3) failed > acpi0: reservation of 0, a (3) failed > acpi0: reservation of 10, c7e0 (3) failed > acpi_button0: on acpi0 > Do all those reservation failed indicate the interrupt is not > going to actually be seen? Seems to be messages related to an improperly implemented ACPI BIOS I'd assume. Look: acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, 7fde (3) failed I also have two of such messages here. In my case, it's a really cheap home PC (from a discounter). > What does (fixed) mean? A can only guess: It probably means that the button is fixed (mounted) in the machine, e. g. at the front panel. You could also check in sysctl's output on what state the button will initiate when pressed (usually S3). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
