On 3/28/2012 1:59 PM, Mark Felder wrote:
FreeBSD 8-STABLE, 8.3, and 9.0 are untested
As much as I'm sensitive to your production requirements, realistically
it's not likely that you'll get a helpful result without testing a newer
version. 8.2 came out over a year ago, many many things have
Mark Felder wrote:
Alright guys, I'm at the end of my rope here. For those that haven't seen
my previous emails here's the (not so) quick breakdown:
Overview:
FreeBSD ?? - 7.4 never crash
FreeBSD 8.0 - 8.2 crashes
FreeBSD 8-STABLE, 8.3, and 9.0 are untested (Sorry, not possible in our
Mark Felder wrote:
My second suggestion is to please never ever ever mess with CFLAGS on
FreeBSD. You can get away with it on some Linux distros, but FreeBSD
strongly discourages it.
Not true.
eg I've set various CFLAGS for years.
What FreeBSD requires is if one sets either CFLAGS or
My system has root login via sshd disabled, and it is going to stay disabled.
I don't care if the whole of the entire internet tries to login as root,
because:
Root login is disabled.
However, syslog likes to print little warnings on my console, and in my
auth.log, everytime some bot tries.
I
On Wed, 28 Mar 2012 18:31:38 -0500, Adrian Chadd adr...@freebsd.org
wrote:
* have you filed a PR?
No
* is the crash easily reproducable?
Unfortunately not. It's totally random. Some servers will get the bug
and crash daily, some will crash weekly, some might seem to be fine but 3
On Thu, 29 Mar 2012 02:36:49 -0500, Doug Barton do...@freebsd.org wrote:
As much as I'm sensitive to your production requirements, realistically
it's not likely that you'll get a helpful result without testing a newer
version. 8.2 came out over a year ago, many many things have changed
since
Thank you for the suggestion. We'll put it in our toolbox and see if it
helps!
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
Alright, new data. It happened to crash about 10 minutes after I came in
this morning and I ran some stuff in the DDB. I have no idea what
information is useful, but perhaps someone will see something out of the
ordinary?
http://feld.me/freebsd/esx_crash/
Thanks...
On Wed, 28 Mar 2012 16:24:51 -0700, Gary Kline wrote:
i dont have a clue what a chording keybd is;
This kind of keyboard uses key combination of its FEWER keys
to generate characters (or even syllables or words). The
name chorded is used synonymously with instruments like
the guitar where
Hi,
* have you filed a PR?
* is the crash easily reproducable?
* are you able to boot some ramdisk-only FreeBSD-8.2 images (eg create
a ramdisk image using nanobsd?) and do some stress testing inside
that?
It sounds like you've established it's a storage issue, or at least
interrupt
On Thursday 29 March 2012 15:42:42 Joe Greco wrote:
Hi,
Do both 32- and 64-bit versions of FreeBSD crash?
--HPS
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail
On 3/28/2012 1:59 PM, Mark Felder wrote:
FreeBSD 8-STABLE, 8.3, and 9.0 are untested
As much as I'm sensitive to your production requirements, realistically
it's not likely that you'll get a helpful result without testing a newer
version. 8.2 came out over a year ago, many many things have
On Thu, 29 Mar 2012 09:58:16 -0500, Hans Petter Selasky hsela...@c2i.net
wrote:
Do both 32- and 64-bit versions of FreeBSD crash?
Correct, we see both i386 and amd64 flavors crash in the same way.
___
freebsd-questions@freebsd.org mailing list
At 16:03 29/03/2012, you wrote:
Alright, new data. It happened to crash about 10 minutes after I came in
this morning and I ran some stuff in the DDB. I have no idea what
information is useful, but perhaps someone will see something out of the
ordinary?
http://feld.me/freebsd/esx_crash/
On Thursday 29 March 2012 15:42:42 Joe Greco wrote:
Hi,
Do both 32- and 64-bit versions of FreeBSD crash?
We've only seen it happen on one virtual machine. That was a 32-bit
version. And it's not so much a crash as it is a disk I/O hang.
The fact that it was happening regularly to that
On Thursday 29 March 2012 17:49:30 Joe Greco wrote:
On Thursday 29 March 2012 15:42:42 Joe Greco wrote:
Hi,
Do both 32- and 64-bit versions of FreeBSD crash?
We've only seen it happen on one virtual machine. That was a 32-bit
version. And it's not so much a crash as it is a disk
Hi,
Any one know where I can get a FreeBSD-9.0-STABLE ISO/IMG image?
ftp.freebsd.org/pub/FreeBSD/FreeBSD-stable/
That path does not seem to have it.
--
Mike
Of course, you might discount this possibility, but remember that one in a
million chances happen 99% of the time.
On Thu, 29 Mar 2012 10:31:24 -0500, Eduardo Morras nec...@retena.com
wrote:
Don't know about ESXi but on others VM Managers i can change the chipset
emulation from ICH10 to ICH4. Can you change it to an older chipset too?
Unfortunately there's no setting in the GUI for that but I'll keep
On 29/03/2012 17:10, Mike Barnard wrote:
Hi,
Any one know where I can get a FreeBSD-9.0-STABLE ISO/IMG image?
ftp.freebsd.org/pub/FreeBSD/FreeBSD-stable/
That path does not seem to have it.
ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/ISO-IMAGES/9.0/
Cheers,
/amd64/ISO-IMAGES/9.0/
Errr... except of course that is -RELEASE and you asked for -STABLE. I
don't believe there's a 9.0-STABLE snapshot available at freebsd.org
right now. Instead, try one from here:
ftp://ftp.allbsd.org/pub/FreeBSD-snapshots/amd64-amd64/9.0-RELENG_9-20120329-JPSNAP/
There's a new
On Thu, 29 Mar 2012 10:55:36 -0500, Hans Petter Selasky hsela...@c2i.net
wrote:
It almost sounds like the lost interrupt issue I've seen with USB EHCI
devices, though disk I/O should have a retry timeout?
What does wmstat -i output?
--HPS
Here's a server that has a week uptime and is due
On Thu, 29 Mar 2012 10:49:30 -0500, Joe Greco jgr...@ns.sol.net wrote:
I explained it at the time to one of my VMware friends:
This is 100% identical to what we see, Joe! And we're so unlucky that we
have this happen on probably a dozen servers, but a handful are the really
bad ones.
Hi, folks. I want to diagnose which programs trigger disk writes,
so I'm wondering if there's a way to determine which processes write
to which files on what disks with what speed?
I know there are gstat(8) and iostat(8) which show how busy each
disk is, but they do not show which files are being
This sounds just like a race condition that happens under Windows 7 on
this laptop. The race condition, as far as I can tell involves heavy
disk access and heavy network access, and usually leaves the drive light
on, while all activity monitors (alldisk, allcpu, allnetwork) are still
active,
On Thu, Mar 29, 2012 at 11:27 AM, Mark Felder f...@feld.me wrote:
On Thu, 29 Mar 2012 10:55:36 -0500, Hans Petter Selasky hsela...@c2i.net
wrote:
It almost sounds like the lost interrupt issue I've seen with USB EHCI
devices, though disk I/O should have a retry timeout?
What does wmstat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/29/2012 07:03, Mark Felder wrote:
Alright, new data. It happened to crash about 10 minutes after I
came in this morning and I ran some stuff in the DDB. I have no
idea what information is useful, but perhaps someone will see
something out of
On Thu, 29 Mar 2012 11:43:45 -0500
Jim Bryant articulated:
Mark Felder wrote:
Alright guys, I'm at the end of my rope here. For those that
haven't seen my previous emails here's the (not so) quick breakdown:
Overview:
FreeBSD ?? - 7.4 never crash
FreeBSD 8.0 - 8.2 crashes
FreeBSD
On Thu, 29 Mar 2012 12:05:30 -0500, Mark Atkinson atkin...@gmail.com
wrote:
If this is an interrupt problem with disk i/o, then you might want to
look into (DDB(4))
show intr
show intrcount
maybe
show allrman
Thank you! I really don't know what things we should be running in DDB to
On Thu, 29 Mar 2012 12:24:30 -0500, je...@seibercom.net wrote:
I just started reading this tread, but I am wondering if I missed
something here. What does this have to do with Windows 7?
I emailed him off-list but I'm guessing he thought this was on VMWare
Workstation or another product
On Thu, 29 Mar 2012 11:53:02 -0500, Alan Cox alan.l@gmail.com wrote:
Not so long ago, VMware implemented a clever scheme for reducing the
overhead of virtualized interrupts that must be delivered by at least
some
(if not all) of their emulated storage controllers:
On Thursday 29 March 2012 17:49:30 Joe Greco wrote:
On Thursday 29 March 2012 15:42:42 Joe Greco wrote:
Hi,
Do both 32- and 64-bit versions of FreeBSD crash?
We've only seen it happen on one virtual machine. That was a 32-bit
version. And it's not so much a crash as it is
On Thu, Mar 29, 2012 at 1:22 PM, Mark Felder f...@feld.me wrote:
If we assume mpt is the culprit
Doesn't VMWare offer different types of emulated disk controllers? If so,
that might be the easiest way to narrow the field. Another thing maybe to
try would be to backport the mpt
Also, it's
On Thu, 29 Mar 2012 15:53:52 -0500, Adam Vande More
amvandem...@gmail.com wrote:
Doesn't VMWare offer different types of emulated disk controllers? If
so,
that might be the easiest way to narrow the field. Another thing maybe
to
try would be to backport the mpt
Yes, they offer
On 3/29/2012 7:01 AM, Joe Greco wrote:
On 3/28/2012 1:59 PM, Mark Felder wrote:
FreeBSD 8-STABLE, 8.3, and 9.0 are untested
As much as I'm sensitive to your production requirements, realistically
it's not likely that you'll get a helpful result without testing a newer
version. 8.2 came out
And then there is this one with similar symptoms and a workaround:
http://forums.freebsd.org/showthread.php?t=3D27899
I'm now investigating those loader.conf options. I have my crashy machine
set to use them on next boot so we'll see if it crashes now that I'm using
LSI SAS emulated
On Thu, 29 Mar 2012 19:27:31 -0500, Joe Greco jgr...@ns.sol.net wrote:
It also doesn't explain the experience here, where one VM basically
crapped out but only after a migration - and then stayed crapped out.
It would be interesting to hear about your datastore, how busy it is,
what technology,
On 28/03/2012 22:59, Mark Felder wrote:
Alright guys, I'm at the end of my rope here. For those that haven't
seen my previous emails here's the (not so) quick breakdown:
Overview:
FreeBSD ?? - 7.4 never crash
FreeBSD 8.0 - 8.2 crashes
FreeBSD 8-STABLE, 8.3, and 9.0 are untested (Sorry, not
Many thanks to everyone who contacted me, either directly or through the list.
I now have
plenty of places and ideas to check out to help get my stepfather online. At
the moment,
I'm leaning towards getting him a Mac (since it has a real operating system
under the
hood) and a suite of
Again, it's starting to sound like an interrupt handling issue which
may or may not be limited to the storage device.
You'll have to engage someone who knows those device drivers and
likely have them add some debugging to the driver which can be easily
flipped on (via binaries in a ramdisk - very
39 matches
Mail list logo