From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: Mark v Wolher <trilight@ns666.com>
Cc: Lee Revell <rlrevell@joe-job.com>,
Folkert van Heusden <folkert@vanheusden.com>,
Jesper Juhl <jesper.juhl@gmail.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: system keeps freezing once every 24 hours / random apps crashing
Date: Fri, 30 Dec 2005 23:56:59 +0000 [thread overview]
Message-ID: <200512302356.59749.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <43B5C5F6.5070500@ns666.com>
On Friday 30 December 2005 23:42, Mark v Wolher wrote:
> Alistair John Strachan wrote:
> > On Friday 30 December 2005 22:16, Mark v Wolher wrote:
> > [snip]
> >
> >>>Basically you are asking for help with an unsupported configuration. In
> >>>general people on LKML will be more helpful if you take the time to find
> >>>out what the bug reporting guidelines are before posting.
> >>>
> >>>Lee
> >>
> >>Thank you for your input, but sometimes thinking out of the box gives a
> >>solution instead of hiding behind "guidelines".
> >
> > I'm surprised Lee fed you this long, but the cold hard fact of the matter
> > is that you are posting to the Linux kernel mailing lists, and you will
> > comply with these guidelines if you expect help.
> >
> > I'm sure the problem might not be with VMWare, but there is absolutely
> > nothing stopping you from switching nvidia with nv, not loading
> > nvidia/vmware modules, then running the TV card doing *something else*
> > for a few hours. If you do not detect lockups, contact VMWare. They will
> > probably do the exact opposite of what Lee has done and suggest
> > non-VMWare parts of the system are at fault.
> >
> > However, unlike VMWare or NVIDIA, we can actually debug problems if you
> > use source-available modules. Thinking outside of the box here is
> > irrelevant -- a problem requires logical procedure to gain a solution.
> > Any engineer will tell you the same thing. Ordinarily, this is test,
> > observe, retest, and all Lee is suggesting is that you do *not* load the
> > proprietary modules.
> >
> > Try it before responding to this email, so you do not have to write
> > another.
>
> I already switched nvidia for the nv driver in the kernel. Also disabled
> by unloading all modules.
As Lee already explained, "unloading" is insufficient. If you continue to
argue that it is sufficient, then you are only exposing your own ignorance of
the issues at hand. Please physically delete the modules so that they cannot
ever be loaded by the kernel during or after bootup, then reboot the machine
before testing.
> You're saying i should then see what happens after doing the above ...
> This is exactly what i'm now doing, tvcard is active (tv) and i'm doing
> some work as usual. I get the feeling some people consider everyone who
> is a bit different in approach as either some newbie or an idiot, well
> wake up, sometimes by looking from a different view at a problem it can
> be solved. This doesn't mean i don't appreciate the advise of Lee or
> yours, i only ask for some patience. It's not like the world is going
> under if we don't solve this in an hour with traditional logic. :)
Feel free to try any method you like, but the method myself and Lee have
stated is the only one acceptable on this list.
> And at this point the system is still working, i'm increasing the load
> by making it crush numbers, doing a full virusscan and so on.
This is good news -- you stand a better chance of achieving the stability you
require by eliminating variables. VMWare and NVIDIA are useful softwares, and
I would not deny that, but they are closed source and thus any conflicts
resulting from their use are not necessary LKML material (however, if the
interaction is generic and is as a result of a kernel bug, then the
maintainer would very much like to hear it).
--
Cheers,
Alistair.
'No sense being pessimistic, it probably wouldn't work anyway.'
Third year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
next prev parent reply other threads:[~2005-12-30 23:56 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-30 14:05 system keeps freezing once every 24 hours / random apps crashing Trilight
2005-12-30 14:11 ` Ochal Christophe
2005-12-30 14:27 ` Jesper Juhl
2005-12-30 15:52 ` Mark v Wolher
2005-12-30 16:37 ` Mark v Wolher
2005-12-30 16:47 ` Folkert van Heusden
2005-12-30 17:14 ` Mark v Wolher
2005-12-30 18:30 ` Folkert van Heusden
2005-12-30 19:22 ` Mark v Wolher
2005-12-30 20:24 ` Folkert van Heusden
2005-12-30 20:58 ` Mark v Wolher
2005-12-30 21:15 ` Mark v Wolher
2005-12-30 21:30 ` Mark v Wolher
2005-12-30 21:35 ` Lee Revell
2005-12-30 21:47 ` Mark v Wolher
2005-12-30 21:51 ` Lee Revell
2005-12-30 21:57 ` Mark v Wolher
2005-12-30 22:00 ` Lee Revell
2005-12-30 22:05 ` Mark v Wolher
2005-12-30 22:11 ` Lee Revell
2005-12-30 22:16 ` Mark v Wolher
2005-12-30 23:11 ` Alistair John Strachan
2005-12-30 23:42 ` Mark v Wolher
2005-12-30 23:56 ` Alistair John Strachan [this message]
2005-12-31 0:20 ` Mark v Wolher
2005-12-31 0:27 ` Alistair John Strachan
2005-12-31 0:42 ` Mark v Wolher
2005-12-31 0:51 ` Alistair John Strachan
2005-12-31 0:54 ` Mark v Wolher
2005-12-31 10:31 ` Mark v Wolher
2005-12-31 11:08 ` Jesper Juhl
2005-12-31 11:40 ` Mark v Wolher
2005-12-31 11:49 ` Jesper Juhl
2005-12-31 12:46 ` Mark v Wolher
2005-12-31 15:18 ` Mark v Wolher
2005-12-31 15:22 ` Arjan van de Ven
2005-12-31 15:34 ` Mark v Wolher
2005-12-31 15:51 ` Mark v Wolher
2005-12-31 16:34 ` Sami Farin
2005-12-31 16:48 ` Mark v Wolher
2005-12-31 17:02 ` Sami Farin
2005-12-31 17:26 ` Mark v Wolher
2005-12-31 22:01 ` Sami Farin
2006-01-01 2:26 ` Mark v Wolher
2006-01-01 13:06 ` Mark v Wolher
2006-01-01 14:47 ` Mark v Wolher
2006-01-01 17:47 ` Mark v Wolher
2006-01-01 18:38 ` Jiri Slaby
2006-01-01 18:49 ` Mark v Wolher
2006-01-01 19:01 ` Mauro Carvalho Chehab
2006-01-01 19:12 ` Jiri Slaby
2006-01-01 19:37 ` Mark v Wolher
2006-01-01 23:20 ` Re; system keeps freezing once every 24 hours / random apps crashing Peter Missel
2006-01-02 22:29 ` Alan Cox
2006-01-03 0:19 ` Mauro Carvalho Chehab
2006-01-01 18:49 ` Folkert van Heusden
2006-01-01 18:54 ` Mark v Wolher
2006-01-01 20:49 ` Folkert van Heusden
2006-01-01 21:38 ` Mark v Wolher
2006-01-01 21:41 ` Lee Revell
2006-01-01 22:01 ` Mark v Wolher
2006-01-25 12:46 ` Jiri Slaby
2006-01-01 15:14 ` Sami Farin
2005-12-31 11:23 ` Jesper Juhl
2005-12-31 11:31 ` Jesper Juhl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200512302356.59749.s0348365@sms.ed.ac.uk \
--to=s0348365@sms.ed.ac.uk \
--cc=folkert@vanheusden.com \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
--cc=trilight@ns666.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.