Hi,
you guys were right, I was wrong.
It is the hardware.
I increased ram voltage by 0.15V on the 22nd and hadn't any oopses since then.
And I did torture the system.
I am deeply sorry that I wasted your time (but still puzzled that the oopses
started after kernel update - maybe I should buy
On Freitag, 21. Dezember 2007, Mike Galbraith wrote:
> On Thu, 2007-12-20 at 19:14 +0100, Hemmann, Volker Armin wrote:
> > It is just.. I could be the hardware - but I should have seen the
> > same 'problem' with earlier kernels - and the 'almost daily oops' only
> > started with 2.6.23.
>
> Noneth
* Hemmann, Volker Armin <[EMAIL PROTECTED]> wrote:
> Ok, so after the holidays I will do the following:
>
> let memtest86+ run several hours. do a full backup&restore to switch
> to r3 and build an unpatched kernel. see if I can reproduce the oops
> with .21 and .22 (because AFAIR no oops with
On Thu, 2007-12-20 at 19:14 +0100, Hemmann, Volker Armin wrote:
> It is just.. I could be the hardware - but I should have seen the
> same 'problem' with earlier kernels - and the 'almost daily oops' only
> started with 2.6.23.
Nonetheless, the oopsen _suggest_ hardware. If it were my box, I'
Ok, so after the holidays I will do the following:
let memtest86+ run several hours.
do a full backup&restore to switch to r3 and build an unpatched kernel.
see if I can reproduce the oops with .21 and .22 (because AFAIR no oops with
21.. but I might be wrong).
Not exactly in that order.
Glück
* Pekka Enberg <[EMAIL PROTECTED]> wrote:
> Nah, it's just that vma->anon_vma is probably supposed to be NULL
> here. And if you look at all the oopses, they do suggest one
> particular byte lane is dodgy (the corruption is in bits 41-43 and
> 45).
>
> The whole thing reminds me of another bu
Hi,
On Dec 20, 2007 4:38 PM, David Newall <[EMAIL PROTECTED]> wrote:
> >>> and another one, this time tainted with the nvidia module:
> >>> 5194.130985] Unable to handle kernel paging request at 0300
> >>> RIP:
>
> Numbers like that don't suggest hardware faults. All those zeros: It's
On Donnerstag, 20. Dezember 2007, Ingo Molnar wrote:
> * Hemmann, Volker Armin <[EMAIL PROTECTED]> wrote:
> > On Donnerstag, 20. Dezember 2007, you wrote:
> > > Hemmann, Volker Armin wrote:
> > > > [ 5194.131014] Pid: 22490, comm: sleep Tainted: P
> > > > 2.6.23.11reiser4 #4
> > >
> > > The
Hemmann, Volker Armin wrote:
> On Donnerstag, 20. Dezember 2007, you wrote:
>> The subject line is wrong.
>> You apparently run Linux, but not Linux 2.6.23.y.
>
> first of all, apart from this oops all other oopses I reported were with a
> not-tainted kernel. You might want to read the other mail
* Hemmann, Volker Armin <[EMAIL PROTECTED]> wrote:
> On Donnerstag, 20. Dezember 2007, you wrote:
> > Hemmann, Volker Armin wrote:
> > > [ 5194.131014] Pid: 22490, comm: sleep Tainted: P2.6.23.11reiser4
> > > #4
> >
> > The subject line is wrong.
> > You apparently run Linux, but not Linu
On Donnerstag, 20. Dezember 2007, David Newall wrote:
> >>> On Montag, 17. Dezember 2007, you wrote:
> >>>
> >>> and another one, this time tainted with the nvidia module:
> >>> 5194.130985] Unable to handle kernel paging request at 0300
> >>> RIP:
>
> Numbers like that don't suggest ha
On Donnerstag, 20. Dezember 2007, you wrote:
> On Thu, 2007-12-20 at 06:53 +0100, Hemmann, Volker Armin wrote:
> > On Donnerstag, 20. Dezember 2007, you wrote:
> > > On Thu, 2007-12-20 at 03:13 +0100, Hemmann, Volker Armin wrote:
> > > > On Montag, 17. Dezember 2007, you wrote:
> > > >
> > > > and
On Donnerstag, 20. Dezember 2007, you wrote:
> Hemmann, Volker Armin wrote:
> > [ 5194.131014] Pid: 22490, comm: sleep Tainted: P2.6.23.11reiser4
> > #4
>
> The subject line is wrong.
> You apparently run Linux, but not Linux 2.6.23.y.
first of all, apart from this oops all other oopses I
Hemmann, Volker Armin wrote:
> [ 5194.131014] Pid: 22490, comm: sleep Tainted: P2.6.23.11reiser4 #4
The subject line is wrong.
You apparently run Linux, but not Linux 2.6.23.y.
--
Stefan Richter
-=-=-=== ==-- =-=--
http://arcgraph.de/sr/
--
To unsubscribe from this list: send the line
On Montag, 17. Dezember 2007, you wrote:
and another one, this time tainted with the nvidia module:
5194.130985] Unable to handle kernel paging request at 0300
RIP:
Numbers like that don't suggest hardware faults. All those zeros: It's
far too round. Sounds very like software.
On Donnerstag, 20. Dezember 2007, you wrote:
> On Thu, 2007-12-20 at 03:13 +0100, Hemmann, Volker Armin wrote:
> > On Montag, 17. Dezember 2007, you wrote:
> >
> > and another one, this time tainted with the nvidia module:
> > 5194.130985] Unable to handle kernel paging request at 0300
On Thu, 2007-12-20 at 03:13 +0100, Hemmann, Volker Armin wrote:
> On Montag, 17. Dezember 2007, you wrote:
>
> and another one, this time tainted with the nvidia module:
> 5194.130985] Unable to handle kernel paging request at 0300 RIP:
This really sounds like bad hardware. Either me
On Montag, 17. Dezember 2007, you wrote:
and another one, this time tainted with the nvidia module:
5194.130985] Unable to handle kernel paging request at 0300 RIP:
[ 5194.130988] [] _spin_lock+0x0/0xf
[ 5194.130993] PGD 0
[ 5194.130994] Oops: 0002 [1] SMP
[ 5194.130996] CPU 1
[ 5194.
On Montag, 17. Dezember 2007, you wrote:
> On Mon, 17 Dec 2007, Hemmann, Volker Armin wrote:
> > I got another crash, now with 2.6.23.11 on logout from KDE (two
> > differences, new kernel, 4gb ram instead of 2gb):
> > also I got some strange message yesterday before increasing ramsize:
> > [19546
On Mon, 17 Dec 2007, Hemmann, Volker Armin wrote:
>
> I got another crash, now with 2.6.23.11 on logout from KDE (two differences,
> new kernel, 4gb ram instead of 2gb):
>
> [ 1771.063731] Unable to handle kernel paging request at 0400 RIP:
> also I got some strange message yesterday
Hi.
I got another crash, now with 2.6.23.11 on logout from KDE (two differences,
new kernel, 4gb ram instead of 2gb):
[ 1771.063731] Unable to handle kernel paging request at 0400 RIP:
[ 1771.063735] [] _spin_lock+0x0/0xf
[ 1771.063740] PGD 0
[ 1771.063741] Oops: 0002 [1] SMP
[ 1771
21 matches
Mail list logo
