On 9 July 2011 16:51, Adrian Levi wrote:
> Ok, I've had some time to sit down with this thing and check it out further.
> Found this on the screen after stopping boinc-client. I'm going to
Before I could use the machine this afternoon I had to restart it, It
responded to SysRQ RESUB
Jul 9 11:0
On 6 July 2011 08:27, William Hopkins wrote:
>
> I understand your logic but the log says setiathome was the process that
> ultimately triggered the crash. Try disabling it and doing the vt1 trick again
> (also look into the liveCD log-inspection suggestion, then you can pastebinit
> and we can re
On 07/05/11 at 10:11pm, Adrian Levi wrote:
> On 5 July 2011 21:08, Selim T. Erdogan wrote:
>
> > Just a thought: have you tried disabling setiathome? (And also, did
> > you have the same setiathome version running on the Ubuntu that didn't
> > freeze?)
>
> Seti is a recent addition to that mach
On 5 July 2011 21:08, Selim T. Erdogan wrote:
> Just a thought: have you tried disabling setiathome? (And also, did
> you have the same setiathome version running on the Ubuntu that didn't
> freeze?)
Seti is a recent addition to that machine. It was locking up before I
installed it.
Adrian
--
Adrian Levi, 5.07.2011:
> On 3 July 2011 17:43, Adrian Levi wrote:
> > My home server has been experiencing instability issues running Debian
> > stable.
>
> Ha, I turned off kdm and left the computer sitting in vt1. I got the
> following:
> (Hand typed excuse any typo's)
>
> gemini login: [2
On 3 July 2011 17:43, Adrian Levi wrote:
> My home server has been experiencing instability issues running Debian stable.
Ha, I turned off kdm and left the computer sitting in vt1. I got the following:
(Hand typed excuse any typo's)
gemini login: [24573.123365] general protection fault: [#1
On 03/07/2011 15:10, Adrian Levi wrote:
I don't see anything on the screen, Can't wake up the screen (it goes
blank) no oops, no nothing. Dosen't even respond to a num-lock,
caps-lock button press.
Adrian
OK, so you may want to use a live cd to inspect the Debian logs...?
Nicolas
--
To UNSUB
Adrian Levi wrote at 2011-07-03 01:43 -0600:
> My issue is I have no sound output and overnight the computer will
> hard lock-up so that the num-lock light won't even toggle.
If you are not getting any sound anyway, have you tried removing all the snd
modules?
signature.asc
Description: Digital
On 3 July 2011 21:27, lee wrote:
> You need to figure out what happens to trigger the freezing. Are there
> any entries in syslog that might indicate something? There's cron
> scripts running over night ... Perhaps the easiest way to approach this
> is setting the system clock 12 hours or so ah
On 3 July 2011 18:56, Nicolas Bercher wrote:
Hi Nicolas,
> So, before upgrading the kernel to 2.6.38, where you using the standard
> stable Debian kernel (2.6.32)? If not (but seems yes), maybe downgrading
> the kernel back to the stable one is a good thing to test.
The problem was also in 2.6
Adrian Levi writes:
> My home server has been experiencing instability issues running Debian stable.
>
> My issue is I have no sound output and overnight the computer will
> hard lock-up so that the num-lock light won't even toggle. I updated
> to 2.6.38 thinking it might be a kernel compatibilit
On 03/07/2011 09:43, Adrian Levi wrote:
My home server has been experiencing instability issues running Debian stable.
My issue is I have no sound output and overnight the computer will
hard lock-up so that the num-lock light won't even toggle.
I updated to 2.6.38 thinking it might be a kernel c
My home server has been experiencing instability issues running Debian stable.
My issue is I have no sound output and overnight the computer will
hard lock-up so that the num-lock light won't even toggle.
I updated to 2.6.38 thinking it might be a kernel compatibility issue
but the problem remains
13 matches
Mail list logo
