Stuart Henderson wrote:
> I've had faulty hardware that was somewhat stable with earlier
> releases but crashed more often with code from sometime in april; the
> key point is that the hardware _was_ faulty. memtest86 did not find
> any RAM errors. 'make build' whilst running stress (from ports) d
> >I'm not sure what to do at this point. I'll run memtest86 tonight, but
> >I'm very skeptical that it will reveal any hardware problems. This
> >machine started acting strange the next day after I upgraded it to 4.0,
> >and I can't recall a single crash during the 3.7 - 3.9 releases.
I've had
From: "Stephen Takacs" <[EMAIL PROTECTED]>
Sent: Friday, November 24, 2006 9:35 AM
---snip---
I'm not sure what to do at this point. I'll run memtest86 tonight, but
I'm very skeptical that it will reveal any hardware problems. This
machine started acting strange the next day after I upgraded i
This machine has been locking up randomly once or twice a day on
average, but always when X is running. So I've been leaving it in
console mode at night, hoping it crashes into ddb...
Last night it crashed, but unfortunately, it didn't go into ddb on its
own, and the ddb.console Ctl-Alt-Esc key s
Stephen Takacs wrote:
Alexander Hall wrote:
Or try typing "boot crash" or so, and see if anything happens, but you
maybe tried that earlier.
Haven't tried that yet, but that's because I'm waiting for the machine
to crash into ddb. :-) I can invoke ddb at the console with
Ctrl-Alt-Esc, and t
On 2006/11/13 11:30, Stephen Takacs wrote:
> Alexander Hall wrote:
> > Try a serial console, if possible. I have not been able to view the ddb
> > output if the machine crashed while running X. Not sure if the caps lock
> > etc was unresponsive, though. I am on a Dell Inspiron 4100.
>
> This lapto
Alexander Hall wrote:
> Try a serial console, if possible. I have not been able to view the ddb
> output if the machine crashed while running X. Not sure if the caps lock
> etc was unresponsive, though. I am on a Dell Inspiron 4100.
This laptop doesn't have any serial ports, but maybe one of those
Stephen Takacs wrote:
On Sun, Nov 05, 2006 at 05:27:05PM -0500, Kyle George wrote:
Actually, what I should have said was uncomment the ddb.console=1 line in
sysctl.conf. That's where it should go. It will work in either place
though.
Yeah that's what I did. :-) Unfortunately the machine cra
On Sun, Nov 05, 2006 at 05:27:05PM -0500, Kyle George wrote:
> Actually, what I should have said was uncomment the ddb.console=1 line in
> sysctl.conf. That's where it should go. It will work in either place
> though.
Yeah that's what I did. :-) Unfortunately the machine crashed again
tonight
On Sun, 5 Nov 2006, Stephen Takacs wrote:
On Sun, Nov 05, 2006 at 03:12:33PM -0500, Kyle George wrote:
Maybe add sysctl ddb.console=1 to rc.securelevel so if it happens again
you can try breaking into ddb with ctrl-alt-esc.
Thanks! I'll add that, reboot, and we shall see...
Actually, what
On Sun, Nov 05, 2006 at 03:12:33PM -0500, Kyle George wrote:
> Maybe add sysctl ddb.console=1 to rc.securelevel so if it happens again
> you can try breaking into ddb with ctrl-alt-esc.
Thanks! I'll add that, reboot, and we shall see...
On Sun, 5 Nov 2006, Stephen Takacs wrote:
I upgraded my laptop yesterday, and this afternoon I returned to find an
interesting surprise: the screen was blank, and the keyboard completely
unresponsive (even the CapsLock key LED didn't toggle). Unfortunately
the logs don't say much. I hard-rese
I upgraded my laptop yesterday, and this afternoon I returned to find an
interesting surprise: the screen was blank, and the keyboard completely
unresponsive (even the CapsLock key LED didn't toggle). Unfortunately
the logs don't say much. I hard-reset the machine at 13:25. Here are
the only lo
13 matches
Mail list logo
