On Thu, Apr 8, 2010 at 4:45 PM, Anoop Kumar Narayanan
wrote:
> On Sat, Apr 3, 2010 at 6:21 PM, Masoom Shaikh wrote:
>> On Sun, Mar 28, 2010 at 5:38 PM, Ivan Voras wrote:
>>> On 28 March 2010 16:42, Masoom Shaikh wrote:
>>>
lets assume if this is h/w problem, then how can other OSes overcom
On Sat, Apr 3, 2010 at 6:21 PM, Masoom Shaikh wrote:
> On Sun, Mar 28, 2010 at 5:38 PM, Ivan Voras wrote:
>> On 28 March 2010 16:42, Masoom Shaikh wrote:
>>
>>> lets assume if this is h/w problem, then how can other OSes overcome
>>> this ? is there a way to make FreeBSD ignore this as well, let
On Sat, 3 Apr 2010 12:51:46 +
Masoom Shaikh wrote:
> On Sun, Mar 28, 2010 at 5:38 PM, Ivan Voras wrote:
> > On 28 March 2010 16:42, Masoom Shaikh wrote:
> >
> >> lets assume if this is h/w problem, then how can other OSes overcome
> >> this ? is there a way to make FreeBSD ignore this as we
On Sun, Mar 28, 2010 at 5:38 PM, Ivan Voras wrote:
> On 28 March 2010 16:42, Masoom Shaikh wrote:
>
>> lets assume if this is h/w problem, then how can other OSes overcome
>> this ? is there a way to make FreeBSD ignore this as well, let it
>> result in reasonable performance penalty.
>
> Very pr
On Mon, Mar 29, 2010 at 02:27:34PM -0400, John Baldwin wrote:
> On Monday 29 March 2010 1:30:38 pm Jeremy Chadwick wrote:
> > On Mon, Mar 29, 2010 at 05:01:02PM +, Masoom Shaikh wrote:
> > > On Sun, Mar 28, 2010 at 5:38 PM, Ivan Voras wrote:
> > > > On 28 March 2010 16:42, Masoom Shaikh wrote
On Mon, Mar 29, 2010 at 8:27 PM, John Baldwin wrote:
>> To developers: what incentives would help get this issue well-needed
>> attention? This problem makes kernel debugging, panic analysis, and
>> other console-oriented viewing basically impossible.
>
> I was recently going to look at it. The
On Monday 29 March 2010 1:30:38 pm Jeremy Chadwick wrote:
> On Mon, Mar 29, 2010 at 05:01:02PM +, Masoom Shaikh wrote:
> > On Sun, Mar 28, 2010 at 5:38 PM, Ivan Voras wrote:
> > > On 28 March 2010 16:42, Masoom Shaikh wrote:
> > >
> > >> lets assume if this is h/w problem, then how can other
On Mon, Mar 29, 2010 at 05:01:02PM +, Masoom Shaikh wrote:
> On Sun, Mar 28, 2010 at 5:38 PM, Ivan Voras wrote:
> > On 28 March 2010 16:42, Masoom Shaikh wrote:
> >
> >> lets assume if this is h/w problem, then how can other OSes overcome
> >> this ? is there a way to make FreeBSD ignore this
On Sun, Mar 28, 2010 at 5:38 PM, Ivan Voras wrote:
> On 28 March 2010 16:42, Masoom Shaikh wrote:
>
>> lets assume if this is h/w problem, then how can other OSes overcome
>> this ? is there a way to make FreeBSD ignore this as well, let it
>> result in reasonable performance penalty.
>
> Very pr
On 28 March 2010 16:42, Masoom Shaikh wrote:
> lets assume if this is h/w problem, then how can other OSes overcome
> this ? is there a way to make FreeBSD ignore this as well, let it
> result in reasonable performance penalty.
Very probably, if only we could detect where the problem is.
Try add
On Sun, Mar 28, 2010 at 8:42 AM, Masoom Shaikh wrote:
> nopes, this didn't help too, machine freezed again after using for 30
> minutes or so
> all it was doing is playing amarok, fetching sources from svn repos,
> and using firefox
>
> lets assume if this is h/w problem, then how can other OSes o
On Sun, Mar 28, 2010 at 12:03 PM, Ivan Voras wrote:
> On 28 March 2010 13:18, Masoom Shaikh wrote:
>> On Sun, Mar 28, 2010 at 10:32 AM, Ivan Voras wrote:
>>> Masoom Shaikh wrote:
Hello List,
I was a happy FreeBSD user, just before I installed FreeBSD8.0-RC1. Since
then,
-- Forwarded message --
From: Masoom Shaikh
Date: Sun, Mar 28, 2010 at 8:28 AM
Subject: random FreeBSD panics
To: freebsd-hack...@freebsd.org, freebsd-questions
Hello List,
I was a happy FreeBSD user, just before I installed FreeBSD8.0-RC1.
Since then, system randomly just
13 matches
Mail list logo
