Re: panic: umass1: Unknown state 1
Hans Petter Selasky wrote: > On Thursday 13 October 2011 20:06:34 Oliver Fromme wrote: > > I just got this panic on a recent stable/8 amd/64 system: > > panic: umass1: Unknown state 1 > > > > Here's a screen shot from the KVM console: > > > > http://www.secnetix.de/olli/tmp/umass-panic.jpg > > > > Unfortunately, the crash dump that was written seems to be > > lost. A quick search on the PRs doesn't reveal anything > > either ... has anyone seen this type of panic before? > > > > It happened when I was switching virtual remote drives in > > the management application of an IBM blade center, i.e. > > the USB drive is actually a virtual drive emulated by the > > blade management system. I did similar things a few times > > before without a panic, so this isn't 100% reproducable. > > Also, I'm reluctant to try again because this is a quite > > important production server. > > > > Hi, > > ehci_softintr() is not part of the USB stack in 8-stable and 9-stable. Must > be > 7-stable you are running. You are right! I'm sorry for the confusion. The disk contains a dual-boot setup with both 7-stable and 8-stable. Indeed, at the time the panic occured, 7-stable was booted. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd In my experience the term "transparent proxy" is an oxymoron (like jumbo shrimp). "Transparent" proxies seem to vary from the distortions of a funhouse mirror to barely translucent. I really, really dislike them when trying to figure out the corrective lenses needed with each of them. -- R. Kevin Oberman, Network Engineer ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: /usr/bin/script eating 100% cpu with portupgrade and xargs
On Wed, Oct 12, 2011 at 11:25:35PM +0100, Adrian Wontroba wrote: > On Sat, Oct 08, 2011 at 01:27:07AM +0100, Adrian Wontroba wrote: > > I won't be in a position to create a simpler test case, raise a PR or > > try patches till Tuesday evening (UK) at the earliest. > So far I have been unable to reproduce the problem with portupgrade (and > will probably move to portmaster). > I have however found a different but possibly related problem with the > new version of script in RELENG_8, for which I have raised this PR: > misc/161526: script outputs corrupt if input is not from a terminal > Blast, should of course been bin/ The extra ^D\b\b are the EOF character being echoed. These EOF characters are being generated by the new script(1) to pass through the EOF condition on stdin. One fix would be to change the termios settings temporarily to disable the echoing but this may cause problems if the application is changing termios settings concurrently and generally feels bad. It may be best to remove writing EOF characters, perhaps adding an option to enable it again if there is a concrete use case for it. -- Jilles Tjoelker ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: /usr/bin/script eating 100% cpu with portupgrade and xargs
Am 14.10.2011 um 14:03 schrieb Jilles Tjoelker: > On Wed, Oct 12, 2011 at 11:25:35PM +0100, Adrian Wontroba wrote: >> On Sat, Oct 08, 2011 at 01:27:07AM +0100, Adrian Wontroba wrote: >>> I won't be in a position to create a simpler test case, raise a PR or >>> try patches till Tuesday evening (UK) at the earliest. > >> So far I have been unable to reproduce the problem with portupgrade (and >> will probably move to portmaster). > >> I have however found a different but possibly related problem with the >> new version of script in RELENG_8, for which I have raised this PR: > >> misc/161526: script outputs corrupt if input is not from a terminal > >> Blast, should of course been bin/ > > The extra ^D\b\b are the EOF character being echoed. These EOF > characters are being generated by the new script(1) to pass through the > EOF condition on stdin. > > One fix would be to change the termios settings temporarily to disable > the echoing but this may cause problems if the application is changing > termios settings concurrently and generally feels bad. > > It may be best to remove writing EOF characters, perhaps adding an > option to enable it again if there is a concrete use case for it. I finally figured out why my ports aren't updating anymore: when running portupgrade -a --batch from cron, stdin is /dev/null, and that produces the gobs of ^D in the output, as well as the script file that portupgrade creates. What's worse is that the upgrade never completes. You can easily see this for yourself: # portupgrade -a --batchFon +49 151 14070811 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
backup for /var/db/ports
Hi
With /etc/periodic/daily/220.backup-pkgdb I would also suggest backing up
/var/db/ports dir
Maybe it's better to combine into one script.
diff -ruN etc.bak/defaults/periodic.conf etc/defaults/periodic.conf
--- etc.bak/defaults/periodic.conf 2011-10-15 04:37:28.879673119 +0400
+++ etc/defaults/periodic.conf 2011-10-15 04:30:48.599677268 +0400
@@ -78,6 +78,10 @@
daily_backup_pkgdb_enable="YES"# Backup
/var/db/pkg
daily_backup_pkgdb_dir="/var/backups"
+# 230.backup-portdb
+daily_backup_portdb_enable="YES" # Backup
/var/db/ports
+daily_backup_portdb_dir="/var/backups"
+
# 300.calendar
daily_calendar_enable="NO" # Run calendar -a
diff -ruN etc.bak/periodic/daily/230.backup-portdb
etc/periodic/daily/230.backup-portdb
--- etc.bak/periodic/daily/230.backup-portdb1970-01-01 03:00:00.0
+0300
+++ etc/periodic/daily/230.backup-portdb2011-10-15 04:29:31.149682366
+0400
@@ -0,0 +1,51 @@
+#!/bin/sh
+#
+# $FreeBSD: src/etc/periodic/daily/220.backup-portdb,v 1.2 2011/05/05
02:35:11 dougb Exp $
+#
+
+# If there is a global system configuration file, suck it in.
+#
+if [ -r /etc/defaults/periodic.conf ]
+then
+. /etc/defaults/periodic.conf
+source_periodic_confs
+fi
+
+rc=0
+
+case "$daily_backup_portdb_enable" in
+[Yy][Ee][Ss])
+ bak="${daily_backup_portdb_dir:-/var/backups}"
+ bak_file="${bak}/portdb.bak.tbz"
+
+ port_dbdir=`make -f/usr/share/mk/bsd.port.mk -V PORT_DBDIR
2>/dev/null` ||
+ port_dbdir=/var/db/ports
+
+ if [ ! -d "$bak" ]
+ then
+ install -d -o root -g wheel -m 750 $bak || {
+ echo '$daily_backup_portdb_enable is enabled but' \
+ "$daily_backup_portdb_dbdir doesn't exist" ;
+ exit 2 ; }
+ fi
+
+ echo ''
+ echo 'Backing up package db directory:'
+
+ new_bak_file=`mktemp ${bak_file}-X`
+
+ if tar -cjHf "${new_bak_file}" "$port_dbdir" 2>/dev/null; then
+ chmod 644 "${new_bak_file}"
+
+ if [ -e "${bak_file}.2" -a -e "${bak_file}" ]; then
+ unlink "${bak_file}.2"
+ mv "${bak_file}" "${bak_file}.2"
+ fi
+ [ -e "${bak_file}" ] && mv "${bak_file}" "${bak_file}.2"
+ mv "${new_bak_file}" "${bak_file}"
+ else
+ rc=3
+ fi ;;
+esac
+
+exit $rc
--
С уважением, With respect,
Олег Гинзбург Oleg Ginzburg
=
E-mail: mailto: olev...@olevole.ru
Skype: olegginzburg
XMPP/Jabber: olev...@jabber.ru
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
