On Wed, Mar 28, 2012 at 22:22, Chris.H wrote:
> Greetings,
> Over the past year, in an effort to convert my server farm to wireless, I've
> purchased some half a dozen USB wireless dongles, at a total cost of ~150.00.
> Unfortunately, none of them are (yet) supported — I know, I know, I've
> a
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 chang
On Wed, Mar 28, 2012 at 04:33:17PM -0400, Brandon Falk wrote:
> Reverse engineering a whole driver could take a very long time, even with the
> proper tools. If it's possible, return the adapter, and buy a new one and
> verify
> that the chipset is supported before you buy it. Last time I bought a
Thanks a lot for replying!
Ok I've tried this to push arguments onto stack.
Is it right?
I get an error at this line:
die_perror("ptrace(PT_WRITE,%d,0x%.8x,INT 0x80) failed while
dasfallocating memory",exec_pid,temp_regs.r_eip);
Please tell me what to do.
void map_memory(unsigned long ad
On Wed, 28 Mar 2012 18:31:38 -0500, Adrian Chadd
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
months later hit th
On Thu, 29 Mar 2012 02:36:49 -0500, Doug Barton 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 then.
The sad part
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 Thursday, March 29, 2012 9:15:43 am Maninya M wrote:
> Thanks a lot for replying!
> Ok I've tried this to push arguments onto stack.
> Is it right?
> I get an error at this line:
>
>die_perror("ptrace(PT_WRITE,%d,0x%.8x,INT 0x80) failed while
> dasfallocating memory",exec_pid,temp_regs.r_ei
> 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
> int
On Thursday 29 March 2012 15:42:42 Joe Greco wrote:
> > Hi,
Do both 32- and 64-bit versions of FreeBSD crash?
--HPS
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "
> 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 thing
On Thu, 29 Mar 2012 09:58:16 -0500, Hans Petter Selasky
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-hackers@freebsd.org mailing list
http://lists.freebsd.o
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/
Don't
> 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 t
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
On Thu, 29 Mar 2012 10:31:24 -0500, Eduardo Morras
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 looking
to see
On 28 Mar 2012 21:23, "Chris.H" wrote:
>
> Greetings,
> Over the past year, in an effort to convert my server farm to wireless,
I've purchased some half a dozen USB wireless dongles, at a total cost of
~150.00. Unfortunately, none of them are (yet) supported — I know, I know,
I've already had thi
On Thu, 29 Mar 2012 10:55:36 -0500, Hans Petter Selasky
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 for a crash any
On Thu, 29 Mar 2012 10:49:30 -0500, Joe Greco 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. We've rebuilt them fr
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, a
On Thu, Mar 29, 2012 at 11:27 AM, Mark Felder wrote:
> On Thu, 29 Mar 2012 10:55:36 -0500, Hans Petter Selasky
> 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?
>>
>
On Thursday 29 March 2012 18:15:59 Chris Rees wrote:
> On 28 Mar 2012 21:23, "Chris.H" wrote:
> > Greetings,
> >
> > I can unpack the setup file to extract the .sys files. While I _could_
>
> utilize the ndisulator to load them, that's not my goal. Should I unpack
> the .sys file, and attempt t
-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
I am currently working on coredump and then restarting the process in FreeBSD 9.
I have created the coredump file for a process using gcore of gdb.
I am not able restart the process from the coredump file.
Is there any ways to restart the process using gdb itself or any other ways to
implement
On Thu, 29 Mar 2012 12:05:30 -0500, Mark Atkinson
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
diagnose this and we wi
Which part of the source code in FreeBSD 9 is responsible for making context
switching i.e. storing and restoring the process state.
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, s
On Thu, 29 Mar 2012 12:24:30 -0500, 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 that would virtualiz
On Thu, 29 Mar 2012 11:53:02 -0500, Alan Cox 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:
http://static.usenix.org/events/atc11/tech
mlock(2) says:
> A single process can mlock() the minimum of a system-wide
> ``wired pages'' limit and the per-process RLIMIT_MEMLOCK
> resource limit.
Shouldn't this say maximum rather than minimum?
> [EAGAIN] Locking the indicated range would exceed either the
> system or per-process limit for
> 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 mu
> FreeBSD ?? - 7.4 never crash
> FreeBSD 8.0 - 8.2 crashes
Obvious short term workaround is to run production on 7.4 (assuming you can)
until you figure out what is wrong with 8.x.
What filesystem(s) are you running? UFS? ZFS? other?
> started randomly disconnecting people every morning
Due to
On Thu, 29 Mar 2012 12:53:49 -0500, Dieter BSD
wrote:
FreeBSD ?? - 7.4 never crash
FreeBSD 8.0 - 8.2 crashes
Obvious short term workaround is to run production on 7.4 (assuming you
can)
until you figure out what is wrong with 8.x.
We're moving our most critical servers to 7.4 this week
On Thu, Mar 29, 2012 at 1:22 PM, Mark Felder 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 not VMWare'
On Fri, 2012-03-30 at 01:10 +0800, Mahesh Babu wrote:
> I am currently working on coredump and then restarting the process in FreeBSD
> 9.
>
>
> I have created the coredump file for a process using gcore of gdb.
>
> I am not able restart the process from the coredump file.
>
> Is there any way
On Thu, 29 Mar 2012 15:53:52 -0500, Adam Vande More
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 Paravirtual (not applicable
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.
> > 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 emu
On Thu, 29 Mar 2012 19:27:31 -0500, Joe Greco 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, whether you're us
On Thu, Mar 29, 2012 at 3:17 PM, Dieter BSD wrote:
> mlock(2) says:
>
>> A single process can mlock() the minimum of a system-wide
>> ``wired pages'' limit and the per-process RLIMIT_MEMLOCK
>> resource limit.
>
> Shouldn't this say maximum rather than minimum?
I don't think so. The minimum of t
Hello Community,
I am interested in participating in Google Summer of Code 2012 with
the FreeBSD Project. From the IdeasPage
(http://wiki.freebsd.org/IdeasPage) I found the project "Automated
kernel crash reporting system". After reading its description I
decided to work on it because I t
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
On Thu, Mar 29, 2012 at 09:20:27AM +0100, Anton Shterenlikht wrote:
> On Wed, Mar 28, 2012 at 04:33:17PM -0400, Brandon Falk wrote:
> > Reverse engineering a whole driver could take a very long time, even with
> > the
> > proper tools. If it's possible, return the adapter, and buy a new one and
42 matches
Mail list logo
