Re: gemor mirror and priority

2009-03-22 Thread Ulrich Spörlein 
On Sat, 21.03.2009 at 08:44:42 -1000, Clifton Royston wrote:
>   Even if you don't, I think it's quite useful to make the *default*
> priority set when creating a mirror be some value which allows both
> higher and lower values to be specified.  I hadn't known about that
> issue until I read the original thread here a while back.If the default
> were set to some mid-range value, or even to 2, for example, then at
> least creating a new mirror and adding drives without setting a
> priority would continue to behave as usual, while it would be possible
> to explicitly insert new components with a lower priority.  (I see why
> one wouldn't want to change the default interpretation of existing
> priority values for POLA reasons.)
> 
>   There are lots of reasons one could want to control priorities of
> mirrored drives in various ways.  One is to use gmirror as a long-term
> backup approach: mirror with three drives, periodically disconnecting
> one from the mirror to swap it with a fresh drive from a pool of backup
> drives.  I haven't tried this, but it's been on my mind to mess around
> with soon.

I did this for 2-3 years and it has worked very well. Of course I took
care of using the right priorities from the start. This setup has now
been replaced by a ZFS mirror. The resilver time is just so much better :)

>   In this case, I would want the designated backup drive to always be
> lowest-priority, to ensure the mirror never accidentally started
> rebuilding from a newly reinserted backup.  (This probably wouldn't
> happen anyway, but it would be nice to be sure...)

This will not happen. Besides, I would strongly encourage you to disable
automatic rebuilding for this type of setup.

Cheers,
Ulrich Spörlein
-- 
None are more hopelessly enslaved than those who falsely believe they are free
-- Johann Wolfgang von Goethe
___
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: Is some combination of gmirror, md file systems, snapshots and, maybe, quotas considered harmful?

2009-03-22 Thread Scott Lambert 
On Fri, Mar 20, 2009 at 02:41:57PM -0500, Scott Lambert wrote:
> I have a previously stable machine, other than a one time panic in
> soft-updates which I could never reproduce, running RELENG_7 from July
> 23, 2008.
> 
> Starting update: Wed Jul 23 01:29:47 CDT 2008
> Finished update: Wed Jul 23 01:31:13 CDT 2008
> 
> I had the userquota option in the fstab for /home, but I did not yet
> have anything in /etc/rc.conf to enable them.  I have been running an
> unmodified GENERIC kernel config.
> 
> /dev/mirror/gm0s1g on /home (ufs, local, soft-updates)
> 
> It runs a few jails, using ezjails.  Two of them were image based jails,
> 1GB and 2GB.  There is also one non-image file jail.  The jails live in
> /home/ezjails.
> 
> I added another image based jail, 3GB image, on March 12th.
> 
> I added this machine to our AMANDA setup on March 13, 2009.  
> 
> Things seemed to be okay until the 19th.  On the 19th, during the dump
> of /home, things gradually started to hang.  Nagios paged me about
> services not responding.  
> 
> I did not find any explanation for it.  The disks were idle according to
> systat -vm.  I was able to grep the log files on /var for a while, and
> then I could no longer do anything with it.
> 
> I eventually had to go to the office and power cycle it.  I tried C-A-D
> first, but shutdown timed out after 30 seconds.
> 
> Just to make sure it wasn't something that had since been fixed, I
> updated to RELENG_7 as of Mar 19th.
> 
> Starting update: Thu Mar 19 03:40:41 CDT 2009
> Finished update: Thu Mar 19 03:48:45 CDT 2009
> 
> I rebooted to the new kernel and installed the world just after midnight
> on the 20th.  I started getting paged by Nagios again at 3:40am.  
> 
> I noticed that mksnap_ffs was running on /home, cpu time used: 0:00.77,
> as things began to circle the drain.  That was about 30 minutes after
> the dump attempt had been started by AMANDA.  There were many processes
> waiting in state D.  This time I did a reboot -n -q and the box rebooted
> but was still fscking when I got to the office.
> 
> # ls -l /home/.snap
> -r   1 root  operator  117285093376 Mar 20 03:18 dump_snapshot
> 
> # df /home
> FilesystemSizeUsed   Avail Capacity  Mounted on
> /dev/mirror/gm0s1g106G 11G 86G11%/home
> 
> I removed userquota from the fstab entry for /home and rebooted, just
> to be sure.  The last danger combination I remember for snapshots was
> in combination with quotas.  Am I even in the danger zone for quotas
> without having them compiled into the kernel?
> 
> It looks like removing the .snap directory should be enough to prevent
> any future snapshots during the backup process.  Does that sound like a
> reasonable workaround?  It would at least remove one variable from the
> trouble shooting process.
> 
> Any other suggestions?
> 
> Thank you for any help you may be able to provide,

Did it to me again tonight.  I was unable to get in to look at anything.
Just pushed the power button.  It did give me the same "shutdown timed
out after 30 seconds."

So, I tuned the /home fs to disable softupdates.  I also removed the
.snap directory.

I would appreciate any suggestions...
 
-- 
Scott LambertKC5MLE   Unix SysAdmin
lamb...@lambertfam.org

___
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"

7.2-PRERELEASE/sunx2200/bge/msi broken

2009-03-22 Thread Danny Braniss 
Hi,
between March 16 and now, bge on a Sun X2200 stopped working,
turning off msi (via hw..pci.enable_msi=0) got it working again.
I tried first replacing bge with an older version but that did not help.

please advice :-)

Danny

___
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: KDB+DDB make interrupt storm on MSI motherboards go away it seems

2009-03-22 Thread Marat N.Afanasyev 

Pete French wrote:

I admit I was scepticle of this suggestion - but it actually seems to
have worked. COmpiling a straight GENERIC kernel with KDB and DDB
included do seem to have made my irq22 interrupt storms go away.
Certainly I have spent some time trying to provoke the problem and not
managed to make it read it's ugly head again.

The thing is though, this doen't make me particularly happy - as I am
sure that KDB and DDB are not supposed to make any major changes to
how the kernel functions are they ?

-pete.
___
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"

no major changes, indeed, but a couple of small changes, e.g. implicit 
turning off all optimizations.


--
SY, Marat
___
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: 7.2-PRERELEASE/sunx2200/bge/msi broken

2009-03-22 Thread Mikolaj Golub 

On Sun, 22 Mar 2009 12:55:02 +0200 Danny Braniss wrote:

 DB> Hi,
 DB> between March 16 and now, bge on a Sun X2200 stopped working,
 DB> turning off msi (via hw..pci.enable_msi=0) got it working again.
 DB> I tried first replacing bge with an older version but that did not help.

It looks like related to this report:

http://www.freebsd.org/cgi/getmsg.cgi?fetch=1253844+1263253+/usr/local/www/db/text/2009/freebsd-bugs/20090322.freebsd-bugs

-- 
Mikolaj Golub
___
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: 7.2-PRERELEASE/sunx2200/bge/msi broken

2009-03-22 Thread Marius Strobl 
On Sun, Mar 22, 2009 at 03:10:07PM +0200, Mikolaj Golub wrote:
> 
> On Sun, 22 Mar 2009 12:55:02 +0200 Danny Braniss wrote:
> 
>  DB> Hi,
>  DB> between March 16 and now, bge on a Sun X2200 stopped working,
>  DB> turning off msi (via hw..pci.enable_msi=0) got it working again.
>  DB> I tried first replacing bge with an older version but that did not help.
> 
> It looks like related to this report:
> 
> http://www.freebsd.org/cgi/getmsg.cgi?fetch=1253844+1263253+/usr/local/www/db/text/2009/freebsd-bugs/20090322.freebsd-bugs
> 

Could you please give the following patch a try?
http://people.freebsd.org/~marius/bge_intx.diff

Marius

___
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: gemor mirror and priority

2009-03-22 Thread Pete French 
> I did this for 2-3 years and it has worked very well. Of course I took
> care of using the right priorities from the start. This setup has now
> been replaced by a ZFS mirror. The resilver time is just so much better :)

How do you find ZFS performance in an asymetric mirror, and does it
seem to cope OK if the remote disc fails ? One of the reaons I have stuck
with gmirror is that it seems extremely tolerant to having one of the
drives vanish from underneath it (as sometimes happens with a remote disc).
When I experimented doing this with ZFS I found that it did not work well
at all (lock ups until the disc I had taken away came back).

-pete.
___
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: 7.2-PRERELEASE/sunx2200/bge/msi broken

2009-03-22 Thread Danny Braniss 
> On Sun, Mar 22, 2009 at 03:10:07PM +0200, Mikolaj Golub wrote:
> > 
> > On Sun, 22 Mar 2009 12:55:02 +0200 Danny Braniss wrote:
> > 
> >  DB> Hi,
> >  DB> between March 16 and now, bge on a Sun X2200 stopped working,
> >  DB> turning off msi (via hw..pci.enable_msi=0) got it working again.
> >  DB> I tried first replacing bge with an older version but that did not 
> > help.
> > 
> > It looks like related to this report:
> > 
> > http://www.freebsd.org/cgi/getmsg.cgi?fetch=1253844+1263253+/usr/local/www/db/text/2009/freebsd-bugs/20090322.freebsd-bugs
> > 
> 
> Could you please give the following patch a try?
> http://people.freebsd.org/~marius/bge_intx.diff
> 
> Marius
> 
it works!
thanks,
danny


___
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: Is some combination of gmirror, md file systems, snapshots and, maybe, quotas considered harmful?

2009-03-22 Thread Kris Kennaway 

Scott Lambert wrote:

On Fri, Mar 20, 2009 at 02:41:57PM -0500, Scott Lambert wrote:

I have a previously stable machine, other than a one time panic in
soft-updates which I could never reproduce, running RELENG_7 from July
23, 2008.

Starting update: Wed Jul 23 01:29:47 CDT 2008
Finished update: Wed Jul 23 01:31:13 CDT 2008

I had the userquota option in the fstab for /home, but I did not yet
have anything in /etc/rc.conf to enable them.  I have been running an
unmodified GENERIC kernel config.

/dev/mirror/gm0s1g on /home (ufs, local, soft-updates)

It runs a few jails, using ezjails.  Two of them were image based jails,
1GB and 2GB.  There is also one non-image file jail.  The jails live in
/home/ezjails.

I added another image based jail, 3GB image, on March 12th.

I added this machine to our AMANDA setup on March 13, 2009.  


Things seemed to be okay until the 19th.  On the 19th, during the dump
of /home, things gradually started to hang.  Nagios paged me about
services not responding.  


I did not find any explanation for it.  The disks were idle according to
systat -vm.  I was able to grep the log files on /var for a while, and
then I could no longer do anything with it.

I eventually had to go to the office and power cycle it.  I tried C-A-D
first, but shutdown timed out after 30 seconds.

Just to make sure it wasn't something that had since been fixed, I
updated to RELENG_7 as of Mar 19th.

Starting update: Thu Mar 19 03:40:41 CDT 2009
Finished update: Thu Mar 19 03:48:45 CDT 2009

I rebooted to the new kernel and installed the world just after midnight
on the 20th.  I started getting paged by Nagios again at 3:40am.  


I noticed that mksnap_ffs was running on /home, cpu time used: 0:00.77,
as things began to circle the drain.  That was about 30 minutes after
the dump attempt had been started by AMANDA.  There were many processes
waiting in state D.  This time I did a reboot -n -q and the box rebooted
but was still fscking when I got to the office.

# ls -l /home/.snap
-r   1 root  operator  117285093376 Mar 20 03:18 dump_snapshot

# df /home
FilesystemSizeUsed   Avail Capacity  Mounted on
/dev/mirror/gm0s1g106G 11G 86G11%/home

I removed userquota from the fstab entry for /home and rebooted, just
to be sure.  The last danger combination I remember for snapshots was
in combination with quotas.  Am I even in the danger zone for quotas
without having them compiled into the kernel?

It looks like removing the .snap directory should be enough to prevent
any future snapshots during the backup process.  Does that sound like a
reasonable workaround?  It would at least remove one variable from the
trouble shooting process.

Any other suggestions?

Thank you for any help you may be able to provide,


Did it to me again tonight.  I was unable to get in to look at anything.
Just pushed the power button.  It did give me the same "shutdown timed
out after 30 seconds."

So, I tuned the /home fs to disable softupdates.  I also removed the
.snap directory.

I would appreciate any suggestions...
 


http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html

Kris
___
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"

Lock enabling onboard lan (Attansic L1 GbE) on 7.1-PRERELEASE

2009-03-22 Thread barbara 

Any news about that?

http://lists.freebsd.org/pipermail/freebsd-stable/2009-January/047527.html


___
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: Crazy "interrupt storm detected" on atapci0

2009-03-22 Thread Nicolais 


Marat N.Afanasyev wrote:
> 
> Nicolais wrote:
>> Also - this was extracted from kenv:
>> 
>> smbios.system.maker="MICRO-STAR INTERANTIONAL CO.,LTD"
>> smbios.system.product="MS-7368"
> 
> as I supposed in previous message your MB is MicroStar product. So I 
> insist that you read thread [1] in freebsd-stable named 'Interrupt 
> storm' started by Dan Langille
> 
> [1] 
> http://lists.freebsd.org/pipermail/freebsd-stable/2009-January/047645.html
> 

Hi Marat,

Thank you for pointing this out. After posting I looked in more archives and
found the same threads are you listed.

I have now run with DDB and KDB more than 5 days, and the interrupt storms
have ceased it seems.

This is truly wonderful news, even though I don't really like the solution.

I will leave the options on for now, but will continue to monitor the lists
for better solutions. I would lie if I said I had not hoped a driver update
would have solved the situation, but I guess that is coming sooner or later.

Thanks again

Best regards

 - Nicolai
-- 
View this message in context: 
http://www.nabble.com/Crazy-%22interrupt-storm-detected%22-on-atapic0-tp22560101p22651491.html
Sent from the freebsd-stable mailing list archive at Nabble.com.

___
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"

istgt now supports command queuing in disk type

2009-03-22 Thread Daisuke Aoyama 

Hello.

New release was uploaded in my blog.
The command queuing improves especially sequential read
by MCS(multiple connections per session) round robin.
In my post, I uploaded the screen shots using CrystalDiskMark
which is one of popular benchmark in Japan.

You can download CrystalDiskMark(multilingual) from:
http://crystalmark.info/?lang=en

I got the result about 1.5x-3x faster than previous 20090314.
If test data was cached, it reached over 200MB/s.

Known Issue and Limitations:
o queuing is only supported in single initiator environment.
o LUN thread might have deadlock when an error has occurred.
o write command is still slow.
o timeout may occur when using MCS.
o single connection may be slower than without queuing.

Here is release 20090323:
http://shell.peach.ne.jp/aoyama/archives/376

The screen shots show difference between QueueDepth 16 and 0
(disabled queuing).

The command queuing is disabled by default.
If you want to use it, please add QueueDepth key in the LogicalUnit
section of your configuration. for example:

[LogicalUnit1]
 # Queuing 0=disabled, 1-255=enabled with specified depth.
 QueueDepth 16

Thanks.
--
Daisuke Aoyama

___
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"

ANNOUNCE: [FreeBSD-Announce] FreeBSD Errata Notice FreeBSD-EN-09:01.kenv

2009-03-22 Thread FreeBSD Errata Notices 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

=
FreeBSD-EN-09:01.kenv   Errata Notice
  The FreeBSD Project

Topic:  Kernel panic when dumping environment

Category:   core
Module: kern
Announced:  2009-03-23
Affects:FreeBSD 7.x
Corrected:  2009-03-23 00:00:50 UTC (RELENG_7, 7.2-PRERELEASE)
2009-03-23 00:00:50 UTC (RELENG_7_1, 7.1-RELEASE-p4)
2009-03-23 00:00:50 UTC (RELENG_7_0, 7.0-RELEASE-p11)

For general information regarding FreeBSD Security Advisories,
including descriptions of the fields above, security branches, and the
following sections, please visit http://security.FreeBSD.org/>.

I.   Background

The kenv(2) system call allows userland processes to get, set, and unset
kernel environment variables, as well as to dump all of the entries in
the kernel environment.

II.  Problem Description

When dumping all of the entries in the kernel environment, the kernel
does not adequately bounds-check the size of the buffer into which the
environment should be written.

III. Impact

An unprivileged process can cause the FreeBSD kernel to attempt to
allocate a very large amount of memory, thereby causing the FreeBSD
kernel to panic.

IV.  Workaround

No workaround is available, but systems without untrusted local users
are not vulnerable.

V.   Solution

Perform one of the following:

1) Upgrade your vulnerable system to 7-STABLE, or to the RELENG_7_1
or  RELENG_7_0 security branch dated after the correction date.

2) To patch your present system:

The following patch has been verified to apply to FreeBSD 7.0 and 7.1
systems.

a) Download the patch from the location below, and verify the
detached PGP signature using your PGP utility.

# fetch http://security.FreeBSD.org/patches/EN-09:01/kenv.patch
# fetch http://security.FreeBSD.org/patches/EN-09:01/kenv.patch.asc

b) Apply the patch.

# cd /usr/src
# patch < /path/to/patch

c) Recompile your kernel as described in
http://www.FreeBSD.org/handbook/kernelconfig.html> and reboot the
system.

VI.  Correction details

The following list contains the revision numbers of each file that was
corrected in FreeBSD.

CVS:

Branch   Revision
  Path
- -
RELENG_7
  src/sys/kern/kern_environment.c1.47.2.1
RELENG_7_1
  src/UPDATING 1.507.2.13.2.7
  src/sys/conf/newvers.sh1.72.2.9.2.8
  src/sys/kern/kern_environment.c1.47.6.2
RELENG_7_0
  src/UPDATING 1.507.2.3.2.15
  src/sys/conf/newvers.sh   1.72.2.5.2.15
  src/sys/kern/kern_environment.c1.47.4.1
- -

Subversion:

Branch/path  Revision
- -
stable/7/ r190301
releng/7.1/   r190301
releng/7.0/   r190301
- -

VII. References

The latest revision of this advisory is available at
http://security.FreeBSD.org/advisories/FreeBSD-EN-09:01.kenv.asc
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (FreeBSD)

iEUEARECAAYFAknG0gwACgkQFdaIBMps37ILlwCfcbVKW5FlPK+GtATY34wfkDWr
5tAAmMteIrkXAeBgp3QNI6pFiHzgunE=
=wJeF
-END PGP SIGNATURE-

Re: Lock enabling onboard lan (Attansic L1 GbE) on 7.1-PRERELEASE

2009-03-22 Thread Pyun YongHyeon 
On Sun, Mar 22, 2009 at 08:29:57PM +0100, barbara wrote:
> 
> Any news about that?
> 
> http://lists.freebsd.org/pipermail/freebsd-stable/2009-January/047527.html
> 

I'm sorry, I forgot this issue which was caused by my disk crash
happened in the end of Jan, 2009.
I've updated age(4) patch in the following URL.
http://people.freebsd.org/~yongari/age/age.diff

Please test the with
1. shutdown your box
2. remove power cable and wait 5 min.
3. unplug UTP cabble
4. boot and see whether age(4) does not lockup your box
5. plug UTP cable and see whether age(4) can send/receive traffics

And please do
1. reboot your box with UTP cable plugged in
2. check whether age(4) works

Please also see whether ethernet MAC address is correctly detected
in both cases.

Thanks for reminder.
___
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: [PREVIEW] Nouveau on FreeBSD (Take 2)

2009-03-22 Thread wsk 
>Ok, this patch should work on NV50 chips also.

>What you get is EXA and Xv.

>You still need:

>A recent -CURRENT or -STABLE.

>git master of libdrm and xf86-video-nouveau.

>This patch.

>Things I've figured out since the last patch...

>On NV50 class hardware you need to have a compositing manager running
>for Xv to work.  That means xcompmgr, metacity with composite enabled,
>xfce (rumored to work as well, haven't tried).  If your running Gnome
>with metacity, open gconf-editor and go to apps->metacity->general and
>check the composite box.

>On NV40 class hardware, you don't need the composite manager.  In fact
>(at least with Xserver 1.6 which I'm running now), if a composite
>manager is enabled, I'm seeing high cpu utilization from Xorg under some
>circumstances.  I don't think this is a drm issue, but still an issue.
>For me, if I start a video using mplayer in an xterm, cpu is fine as
>long as that xterm is the foreground window.  If it is not the
>foreground window, even if it isn't obscured I see the cpu utilization.
>Disabling the composite manager makes everything fine.

>http://people.freebsd.org/~rnoland/drm-nouveau-032109.patch 
>

>robert.

get the following errors and exitThis is a pre-release version of the X server 
from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.

X.Org X Server 1.5.99.902 (1.6.0 RC 2)
Release Date: 2009-1-30
X Protocol Version 11, Revision 0
Build Operating System: FreeBSD 7.1-STABLE amd64
Current Operating System: FreeBSD lp.gddsn.org.cn 7.2-PRERELEASE FreeBSD 7.2-PRE
RELEASE #2: Sun Mar 22 19:44:23 CST 2009 
w...@lp.gddsn.org.cn:/usr/obj/usr/sr
c/sys/WSK amd64
Build Date: 06 February 2009  04:22:44PM

Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Mar 23 09:14:03 2009
ing config file: "xorg.conf1"
error: [drm:pid30722:drm_alloc_resource] *ERROR* Couldn't find resource 0x2
error: [drm:pid30722:drm_alloc_resource] *ERROR* Couldn't find resource 0x2
error: [drm:pid30722:drm_alloc_resource] *ERROR* Couldn't find resource 0x2
vgapci0: 0x1000 bytes of rid 0x14 res 3 failed (0, 0x).
error: [drm:pid30722:drm_alloc_resource] *ERROR* Couldn't find resource 0x1
vgapci0: 0x1000 bytes of rid 0x14 res 3 failed (0, 0x).
error: [drm:pid30722:drm_alloc_resource] *ERROR* Couldn't find resource 0x1
drm0: [ITHREAD]
info: [drm] Allocating FIFO number 1
info: [drm] nouveau_fifo_alloc: initialised FIFO 1
info: [drm] PFIFO_DMA_PUSHER - Ch 1
(EE) NOUVEAU(0): 1296: No valid FB address in PCI config space
(EE) Screen(s) found, but none have a usable configuration.

Fatal server error:
no screens found

Please consult the The X.Org Foundation support
 at http://wiki.x.org
 for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional informati
on.

info: [drm] nouveau_fifo_free: freeing fifo 1
error: [drm:pid30722:nouveau_fifo_free] *ERROR* Failed to idle channel 1 before
destroy.Prepare for strangeness..
vgapci0: 0x1000 bytes of rid 0x14 res 3 failed (0, 0x).
error: [drm:pid30722:drm_alloc_resource] *ERROR* Couldn't find resource 0x1

what can i do ?





This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.

X.Org X Server 1.5.99.902 (1.6.0 RC 2)
Release Date: 2009-1-30
X Protocol Version 11, Revision 0
Build Operating System: FreeBSD 7.1-STABLE amd64 
Current Operating System: FreeBSD lp.gddsn.org.cn 7.2-PRERELEASE FreeBSD 
7.2-PRERELEASE #2: Sun Mar 22 19:44:23 CST 2009 
w...@lp.gddsn.org.cn:/usr/obj/usr/src/sys/WSK amd64
Build Date: 06 February 2009  04:22:44PM
 
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Mar 23 09:14:03 2009
(++) Using co

Re: Is some combination of gmirror, md file systems, snapshots and, maybe, quotas considered harmful?

2009-03-22 Thread Scott Lambert 
On Sun, Mar 22, 2009 at 06:03:54PM +, Kris Kennaway wrote:
> http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html

I guess that means, "We are not aware of issues with any combinations
of the features in the Subject: at this time.  Please recompile your
kernel with debugging options so you can figure out what is going on
next time."

I'm going to guess the Debugging Deadlocks section is what you mostly
want since the kernel does not panic.  

I think I better remove the /home disk from AMANDA's list while I try
to figure out how to accomplish what I think you want on a production
server.

-- 
Scott LambertKC5MLE   Unix SysAdmin
lamb...@lambertfam.org

___
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"

filesystem corruption freebsd 7.1 release guest on virtualpc 2007/windowsXP host system

2009-03-22 Thread security 
I'm writing this more as a heads up to those using freebsd as a guest
under virtualpc 2007 on Win XP sp3 host.

I created a fixed size virtual disk (8gig). Just to be sure, I ran the
XP disk check on the underlying disk before hand.  I then installed
freebsd 7.1 from cd image.  Next I csup'ed to get the latest updates.  I
then did a make buildworld and a make kernel.  I ran into trouble when
it rebooted and went to run make installworld.  Part way through, I
started getting a bunch of FS errors and then a kernel panic.  I
rebooted and manually fsck'ed /usr.  It did recover, but was unusable. 
I tried the same thing again (fresh install), but I used dd and fsck to
read /usr first to see if I could generate errors. It was clean but died
again while it was writing lots of files to /usr during installworld.

I had my suspicions that freebsd and the XP filesystems we getting out
of sync under a large number of updates.  I rebuilt a third time, but
for this round, I set hw.ata.wc="0" in loader.conf.  I haven't seen any
other corruption since turning off write caching and the installworld
runs clean now (multiple passes).  I'm not sure who maintains the
virtualization pages, but they may want to add that as a suggestion for
virtualpc or other VM's that run into disk corruption problems.

jim
___
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"