[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <9a8748490801101505y7b163f9ev8fdc3102281003fb@mail.gmail.com>
Date: Fri, 11 Jan 2008 00:05:41 +0100
From: "Jesper Juhl" <jesper.juhl@...il.com>
To: "Stoyan Gaydarov" <stoyboyker@...il.com>
Cc: "Alan Cox" <alan@...rguk.ukuu.org.uk>, linux-kernel@...r.kernel.org
Subject: Re: Kernel Oops?
On 09/01/2008, Stoyan Gaydarov <stoyboyker@...il.com> wrote:
> On Jan 8, 2008 9:02 PM, Alan Cox <alan@...rguk.ukuu.org.uk> wrote:
> > > Except this time when rebooting the machine i got a kernel oops
> > > message and it didn't boot completely. I could not copy it but I did
> > > take a picture and now I have re-written the screen here(sorry about
> >
> > That is interesting - that sort of error usually points at memory
> > corruption and early on tends to point at hardware (but not always). What
> > hard is in this system and does it have over 4GB of RAM ?
> >
> >
>
> There are 2GB of RAM and the motherboard is DFI and it has a duel core
> intel cpu. If you need to specifics I could look them up.
cat /proc/cpuinfo
cat /proc/scsi/scsi
cat /proc/interrupts
lspci -vvx
should give you most of the details :)
--
Jesper Juhl <jesper.juhl@...il.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists