Hello
Few days ago I've bought new processor Athlon XP 1800+ to my computer
(MSI K7D Master with 256 MB PC2100 DDR).Before that I've got Athlon ThunderBird
900 processor and everything had been working well till I change to the new one.
Now for every few minutes I've got segmetation fault or immediate system reboot.
Could anyone tell me what's goin' on?
thanks
Karol Olechowski
Kernels log:
Unable to handle kernel paging request at virtual address 087fde40
Jul 21 11:26:01 alpha kernel: printing eip:
Jul 21 11:26:01 alpha kernel: c01a2942
Jul 21 11:26:01 alpha kernel: *pde = 00000000
Jul 21 11:26:01 alpha kernel: Oops: 0000
Jul 21 11:26:01 alpha kernel: CPU: 0
Jul 21 11:26:01 alpha kernel: EIP: 0010:[<c01a2942>] Tainted: P
Jul 21 11:26:01 alpha kernel: EFLAGS: 00010002
Jul 21 11:26:01 alpha kernel: eax: c6852f00 ebx: c6852f00 ecx: 00000000 edx: ce562978
Jul 21 11:26:01 alpha kernel: esi: 087fde40 edi: c9461ee0 ebp: ce562000 esp: c9461eb4
Jul 21 11:26:01 alpha kernel: ds: 0018 es: 0018 ss: 0018
Jul 21 11:26:01 alpha kernel: Process bash (pid: 628, stackpage=c9461000)
Jul 21 11:26:01 alpha kernel: Stack: c9461ee0 c9461f4c c6852f24 c01a2a08 c6852f00 c9461ee0 087fde40 bffff268
Jul 21 11:26:01 alpha kernel: bffff28c ce562000 c9461f28 00001500 00000005 000004bf 00000b3b 7f1c0300
Jul 21 11:26:01 alpha kernel: 01000415 1a131100 170f1200 2f000016 c01a2cbb ce562000 c9461f28 ce562000
Jul 21 11:26:01 alpha kernel: Call Trace: [<c01a2a08>] [<c01a2cbb>] [<c01a2fe1>] [<c019fb2b>] [<c0141ec9>]
Jul 21 11:26:01 alpha kernel: [<c01086e7>]
Jul 21 11:26:01 alpha kernel:
Jul 21 11:26:01 alpha kernel: Code: 8b 16 89 d0 f7 d0 23 03 23 17 09 d0 89 03 8b 56 04 89 d0 f7
Jul 21 11:26:01 alpha kernel: <1>Unable to handle kernel paging request at virtual address 0800000c
Jul 21 11:26:01 alpha kernel: printing eip:
Jul 21 11:26:01 alpha kernel: c0141a10
Jul 21 11:26:01 alpha kernel: *pde = 00000000
Jul 21 11:26:01 alpha kernel: Oops: 0000
Jul 21 11:26:01 alpha kernel: CPU: 0
Jul 21 11:26:01 alpha kernel: EIP: 0010:[<c0141a10>] Tainted: P
Jul 21 11:26:01 alpha kernel: EFLAGS: 00010006
Jul 21 11:26:01 alpha kernel: eax: ffffffff ebx: 00000000 ecx: ce56212c edx: 08000000
Jul 21 11:26:01 alpha kernel: esi: 00000000 edi: ce56212c ebp: cebcc1c0 esp: c9461c94
Jul 21 11:26:01 alpha kernel: ds: 0018 es: 0018 ss: 0018
Jul 21 11:26:01 alpha kernel: Process bash (pid: 628, stackpage=c9461000)
Jul 21 11:26:01 alpha kernel: Stack: ce562000 cebcc1c0 00000000 c730b940 00000000 c019f170 ffffffff cebcc1c0
Jul 21 11:26:01 alpha kernel: 00000000 ce56212c ce562000 c86648c0 c1346380 c019e876 ffffffff cebcc1c0
Jul 21 11:26:01 alpha kernel: 00000000 ce562000 c026ad72 cebcc1c0 c86648c0 c1346380 c730b940 00005000
Jul 21 11:26:01 alpha kernel: Call Trace: [<c019f170>] [<c019e876>] [<c012f6ab>] [<c012fb23>] [<c01236d0>]
Jul 21 11:26:01 alpha kernel: [<c0123b32>] [<c019f05a>] [<c013620c>] [<c01351c5>] [<c0119a78>] [<c011a05f>]
Jul 21 11:26:01 alpha kernel: [<c0108cb6>] [<c0113d17>] [<c0113a10>] [<c011f27c>] [<c011f35d>] [<c011f7dd>]
Jul 21 11:26:01 alpha kernel: [<c011f8a4>] [<c01087d8>] [<c01a2942>] [<c01a2a08>] [<c01a2cbb>] [<c01a2fe1>]
Jul 21 11:26:01 alpha kernel: [<c019fb2b>] [<c0141ec9>] [<c01086e7>]
Jul 21 11:26:01 alpha kernel:
Jul 21 11:26:01 alpha kernel: Code: 39 6a 0c 75 22 85 f6 75 cb 8b 42 08 89 01 a1 b0 dd 2f c0 52
Jul 21 11:26:01 alpha kernel: <1>Unable to handle kernel paging request at virtual address 08000000
Jul 21 11:26:01 alpha kernel: printing eip:
Jul 21 11:26:01 alpha kernel: c0141a93
Jul 21 11:26:01 alpha kernel: *pde = 0eb0e067
Jul 21 11:26:01 alpha kernel: *pte = 00000000
Jul 21 11:26:01 alpha kernel: Oops: 0000
Jul 21 11:26:01 alpha kernel: CPU: 0
Jul 21 11:26:01 alpha kernel: EIP: 0010:[<c0141a93>] Tainted: P
Jul 21 11:26:01 alpha kernel: EFLAGS: 00010206
Jul 21 11:26:01 alpha kernel: eax: 08000000 ebx: 08000000 ecx: ce56212c edx: 0000001d
Jul 21 11:26:01 alpha kernel: esi: 00020001 edi: 0000001d ebp: cbc82168 esp: ce653e18
Jul 21 11:26:01 alpha kernel: ds: 0018 es: 0018 ss: 0018
Jul 21 11:26:01 alpha kernel: Process mc (pid: 626, stackpage=ce653000)
Jul 21 11:26:01 alpha kernel: Stack: ce56200a ce562000 00000000 c0141af6 08000000 0000001d 00020001 c01a1507
Jul 21 11:26:01 alpha kernel: ce56212c 0000001d 00020001 00000001 ce562000 00000000 080b1009 00000010
Jul 21 11:26:01 alpha kernel: 0a000017 00000001 00000001 00000000 00000000 cbc82168 c031c0c0 ce653fc4
Jul 21 11:26:01 alpha kernel: Call Trace: [<c0141af6>] [<c01a1507>] [<c012f3b4>] [<c01a3e83>] [<c01a2692>]
Jul 21 11:26:01 alpha kernel: [<c019e268>] [<c01a24e0>] [<c0135716>] [<c01086e7>]
Jul 21 11:26:01 alpha kernel:
Jul 21 11:26:01 alpha kernel: Code: 81 3b 01 46 00 00 74 15 68 c0 14 25 c0 e8 2b 5a fd ff 83 c4
On Mon, Jul 22, 2002 at 01:32:59PM +0000, Karol Olechowskii wrote:
> Hello
>
> Few days ago I've bought new processor Athlon XP 1800+ to my computer
> (MSI K7D Master with 256 MB PC2100 DDR).Before that I've got Athlon ThunderBird
> 900 processor and everything had been working well till I change to the new one.
> Now for every few minutes I've got segmetation fault or immediate system reboot.
> Could anyone tell me what's goin' on?
> ...
> Jul 21 11:26:01 alpha kernel: EIP: 0010:[<c01a2942>] Tainted: P
^^^^^^^^^^^
> nvidia: loading NVIDIA NVdriver Kernel Module 1.0-2960 Tue May 14 07:41:42 PDT 2002
> devfs_register(nvidiactl): could not append to parent, err: -17
> devfs_register(nvidia0): could not append to parent, err: -17
Ask nvidia. Only they can help you. They have the kernel source,
we don't have their source.
Dave.
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
On Mon, 2002-07-22 at 14:32, Karol Olechowskii wrote:
> Hello
>
> Few days ago I've bought new processor Athlon XP 1800+ to my computer
> (MSI K7D Master with 256 MB PC2100 DDR).Before that I've got Athlon ThunderBird
> 900 processor and everything had been working well till I change to the new one.
> Now for every few minutes I've got segmetation fault or immediate system reboot.
> Could anyone tell me what's goin' on?
> nvidia: loading NVIDIA NVdriver Kernel Module 1.0-2960 Tue May 14 07:41:42 PDT 2002
> devfs_register(nvidiactl): could not append to parent, err: -17
> devfs_register(nvidia0): could not append to parent, err: -17
Please duplicate the problem without ever loading the NVidia nvdriver
from a clean boot. If you can't do that then talk to Nvidia, if you can
then post new crash data here
On Mon, Jul 22, 2002 at 01:32:59PM +0000, Karol Olechowskii wrote:
> Hello
>
> Few days ago I've bought new processor Athlon XP 1800+ to my computer
> (MSI K7D Master with 256 MB PC2100 DDR).Before that I've got Athlon ThunderBird
> 900 processor and everything had been working well till I change to the new one.
> Now for every few minutes I've got segmetation fault or immediate system reboot.
> Could anyone tell me what's goin' on?
Is your Power Supply strong enough? Cooling OK?
Regards,
--
Kurt Garloff <[email protected]> Eindhoven, NL
GPG key: See mail header, key servers Linux kernel development
SuSE Linux AG, Nuernberg, DE SCSI, Security
On Mon, Jul 22, 2002 at 01:32:59PM +0000, Karol Olechowskii wrote:
> Hello
>
> Few days ago I've bought new processor Athlon XP 1800+ to my computer
> (MSI K7D Master with 256 MB PC2100 DDR).Before that I've got Athlon ThunderBird
> 900 processor and everything had been working well till I change to the new one.
> Now for every few minutes I've got segmetation fault or immediate system reboot.
> Could anyone tell me what's goin' on?
mem=nopentium on the command line seems to have a stabilizing effect.
Of course, as alan says, real debugging is impossible.
OG, with the same problem
On Mon, 2002-07-22 at 15:49, Olivier Galibert wrote:
> On Mon, Jul 22, 2002 at 01:32:59PM +0000, Karol Olechowskii wrote:
> > Hello
> >
> > Few days ago I've bought new processor Athlon XP 1800+ to my computer
> > (MSI K7D Master with 256 MB PC2100 DDR).Before that I've got Athlon ThunderBird
> > 900 processor and everything had been working well till I change to the new one.
> > Now for every few minutes I've got segmetation fault or immediate system reboot.
> > Could anyone tell me what's goin' on?
>
> mem=nopentium on the command line seems to have a stabilizing effect.
In your case thats the memory handling stuff that the NVidia module
happens to trip. Its actually a kernel related thing not their fault.
There is a horrible work around in 2.4.19-rc2, and people are working on
the right fixes for this.
On Mon, 2002-07-22 at 14:44, Alan Cox wrote:
> On Mon, 2002-07-22 at 14:32, Karol Olechowskii wrote:
> > Hello
> >
> > Few days ago I've bought new processor Athlon XP 1800+ to my computer
> > (MSI K7D Master with 256 MB PC2100 DDR).Before that I've got Athlon ThunderBird
> > 900 processor and everything had been working well till I change to the new one.
> > Now for every few minutes I've got segmetation fault or immediate system reboot.
> > Could anyone tell me what's goin' on?
>
> > nvidia: loading NVIDIA NVdriver Kernel Module 1.0-2960 Tue May 14 07:41:42 PDT 2002
> > devfs_register(nvidiactl): could not append to parent, err: -17
> > devfs_register(nvidia0): could not append to parent, err: -17
>
> Please duplicate the problem without ever loading the NVidia nvdriver
> from a clean boot. If you can't do that then talk to Nvidia, if you can
> then post new crash data here
>
Hi Alan
I've do exactly what You wrote me.(remove NVidia driver) but it isn't
change anything.In the moment of writing this letter a try to compile
kernel and I can't even do this.System hangs or logout console session
or write something like this
gcc: Internal compiler error:
program cc1 got fatal signal 11
make[3] : ***[igmp.o] Error 1
under X
Application "gkrellm" (process bal bal) has crashed
due to a fatal error
(Segmenataion fault)
It's something strange with my computer cause not only Linux hangs.On
the other disk I've got Win XP and it also hangs ( blue screen,memory
dump and things like that...).Almost every component is a brand
new(mother board, processor, memory, video card, power supply)
I've look at the logs and everything looks good.Please send me any tip,
what I can do with this stuff
best regards
Karol Olechowski
> It's something strange with my computer cause not only Linux hangs.On
> the other disk I've got Win XP and it also hangs ( blue screen,memory
> dump and things like that...).Almost every component is a brand
> new(mother board, processor, memory, video card, power supply)
Check the following things:
* Cooling - is the CPU fan, especially, working, and not clogged up with dust
* Memory - try booting Linux with MEM=16M or something - if the problem goes away, it's probably related to memory. Try removing and re-inserting the RAM, and cleaning the edge connectors, (I had a machine run fine for a couple of years, then suddenly keep failing. Cleaning the RAM edge connectors fixed it).
* PSU - make sure your power supply is suitable for the new CPU, (rule of thumb being 300+ Watt rating on it).
As almost 97% of people on this list will write you, run memtest for a
night and check your memory.
On 22 Jul 2002, Karol Olechowski wrote:
> Date: 22 Jul 2002 17:46:29 +0200
> From: Karol Olechowski <[email protected]>
> To: Alan Cox <[email protected]>
> Cc: [email protected]
> Subject: Re: Athlon XP 1800+ segemntation fault
>
> On Mon, 2002-07-22 at 14:44, Alan Cox wrote:
> > On Mon, 2002-07-22 at 14:32, Karol Olechowskii wrote:
> > > Hello
> > >
> > > Few days ago I've bought new processor Athlon XP 1800+ to my computer
> > > (MSI K7D Master with 256 MB PC2100 DDR).Before that I've got Athlon ThunderBird
> > > 900 processor and everything had been working well till I change to the new one.
> > > Now for every few minutes I've got segmetation fault or immediate system reboot.
> > > Could anyone tell me what's goin' on?
> >
> > > nvidia: loading NVIDIA NVdriver Kernel Module 1.0-2960 Tue May 14 07:41:42 PDT 2002
> > > devfs_register(nvidiactl): could not append to parent, err: -17
> > > devfs_register(nvidia0): could not append to parent, err: -17
> >
> > Please duplicate the problem without ever loading the NVidia nvdriver
> > from a clean boot. If you can't do that then talk to Nvidia, if you can
> > then post new crash data here
> >
>
> Hi Alan
>
> I've do exactly what You wrote me.(remove NVidia driver) but it isn't
> change anything.In the moment of writing this letter a try to compile
> kernel and I can't even do this.System hangs or logout console session
> or write something like this
>
> gcc: Internal compiler error:
> program cc1 got fatal signal 11
> make[3] : ***[igmp.o] Error 1
>
> under X
>
> Application "gkrellm" (process bal bal) has crashed
> due to a fatal error
> (Segmenataion fault)
>
>
> It's something strange with my computer cause not only Linux hangs.On
> the other disk I've got Win XP and it also hangs ( blue screen,memory
> dump and things like that...).Almost every component is a brand
> new(mother board, processor, memory, video card, power supply)
>
> I've look at the logs and everything looks good.Please send me any tip,
> what I can do with this stuff
>
> best regards
>
> Karol Olechowski
>
>
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
On Mon, 22 Jul 2002 [email protected] wrote:
Last week i buy new server with Athlon 2000+, and after one week of hard
work, i detect that one of my two hard disk have a problem with DST(Disk
Self-Test), you do not trust of the new hardware, by very good that it is.
Make all test(memory, hard disk, etc...)
Giro
> As almost 97% of people on this list will write you, run memtest for a
> night and check your memory.
>
> On 22 Jul 2002, Karol Olechowski wrote:
>
> > Date: 22 Jul 2002 17:46:29 +0200
> > From: Karol Olechowski <[email protected]>
> > To: Alan Cox <[email protected]>
> > Cc: [email protected]
> > Subject: Re: Athlon XP 1800+ segemntation fault
> >
> > On Mon, 2002-07-22 at 14:44, Alan Cox wrote:
> > > On Mon, 2002-07-22 at 14:32, Karol Olechowskii wrote:
> > > > Hello
> > > >
> > > > Few days ago I've bought new processor Athlon XP 1800+ to my computer
> > > > (MSI K7D Master with 256 MB PC2100 DDR).Before that I've got Athlon ThunderBird
> > > > 900 processor and everything had been working well till I change to the new one.
> > > > Now for every few minutes I've got segmetation fault or immediate system reboot.
> > > > Could anyone tell me what's goin' on?
> > >
> > > > nvidia: loading NVIDIA NVdriver Kernel Module 1.0-2960 Tue May 14 07:41:42 PDT 2002
> > > > devfs_register(nvidiactl): could not append to parent, err: -17
> > > > devfs_register(nvidia0): could not append to parent, err: -17
> > >
> > > Please duplicate the problem without ever loading the NVidia nvdriver
> > > from a clean boot. If you can't do that then talk to Nvidia, if you can
> > > then post new crash data here
> > >
> >
> > Hi Alan
> >
> > I've do exactly what You wrote me.(remove NVidia driver) but it isn't
> > change anything.In the moment of writing this letter a try to compile
> > kernel and I can't even do this.System hangs or logout console session
> > or write something like this
> >
> > gcc: Internal compiler error:
> > program cc1 got fatal signal 11
> > make[3] : ***[igmp.o] Error 1
> >
> > under X
> >
> > Application "gkrellm" (process bal bal) has crashed
> > due to a fatal error
> > (Segmenataion fault)
> >
> >
> > It's something strange with my computer cause not only Linux hangs.On
> > the other disk I've got Win XP and it also hangs ( blue screen,memory
> > dump and things like that...).Almost every component is a brand
> > new(mother board, processor, memory, video card, power supply)
> >
> > I've look at the logs and everything looks good.Please send me any tip,
> > what I can do with this stuff
> >
> > best regards
> >
> > Karol Olechowski
> >
> >
> >
> >
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to [email protected]
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
> >
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
*******************************************************************************
David Gironella Casademont
Estudiant Informatica de Sistemes - Universitat de Girona
Administrador d'Hades [email protected]
Secretari Associaci? d'Estudiants d'Inform?tica de Girona AEIGI
AEIGi Web - http://www.aeigi.org
Giro Web - http://hades.udg.es/~giro
*******************************************************************************
On Mon, 22 Jul 2002 [email protected] wrote:
> As almost 97% of people on this list will write you, run memtest for a
> night and check your memory.
> gcc: Internal compiler error:
> program cc1 got fatal signal 11
> make[3] : ***[igmp.o] Error 1
99.9999% probability memory error. This may not be 'bad' memory, but
memory that is running on a front-side bus at a speed for which it
was not designed. --And many board-vendors don't know the difference.
As a temporary 'fix', if your BIOS or board pin-headers provide a
100 MHz setting for the memory-bus, set it and see if it works.
Cheers,
Dick Johnson
Penguin : Linux version 2.4.18 on an i686 machine (797.90 BogoMips).
The US military has given us many words, FUBAR, SNAFU, now ENRON.
Yes, top management were graduates of West Point and Annapolis.
Karol Olechowskii wrote:
>
> Few days ago I've bought new processor Athlon XP 1800+ to my computer
> (MSI K7D Master with 256 MB PC2100 DDR).Before that I've got Athlon ThunderBird
> 900 processor and everything had been working well till I change to the new one.
> Now for every few minutes I've got segmetation fault or immediate system reboot.
> Could anyone tell me what's goin' on?
>
I too have the MSI K7D Master. As Alan mentioned, the 2.4.19-rc2-ac2
patch works fine. My machine has been rock solid and I'm running dual
XP 2000+. However, I'm running Radeon 8500 (I refused to give my money
to a company that doesn't release it's drivers). Bad memory is a
possibility, so run 'memtest' and see what happens as mentioned by
others. Also, I suggest you upgrade to v1.3 of the MSI 6501 BIOS which
is always a good idea. As far as your X crashes, you might try building
the latest X out of CVS and see if that helps at all, but it looks
like memory problems. Spend the money and buy good name brand like
Micron/Crucial has been good for me. Just my $0.02.
-Steve
> gcc: Internal compiler error:
> program cc1 got fatal signal 11
> make[3] : ***[igmp.o] Error 1
I'm _very_ used to see this in a cyriz 6x86MX 200 Mhz.
And it has only one cause in my system: cpu overhot (well, i let it to
cool a few and restar compiling ;). ).
and as you've said you have more problems with other operative systems,
then you should check your cooling / check your hardware