Hendrik . wrote:
So I think there is a problem with this specific CK804
ATA controller causing the MCE... Any clues?
Yes, the SATA chip is broken. Probably time to check the known errata
on the chip, and if it isn't known, bring nvidia in to debug their
silicon.
-
To unsubscribe from this
Hendrik . wrote:
Ok, I did actually not copy the coreret code in the
mcelog, leaving me some errors about the Northbridge.
If I do it again it gives me something else. I made 2
digital photo's of 2 lockups when it happened and this
is the result of the tool, the TSC is different in
both errors,
Hendrik . wrote:
Ok, I did actually not copy the coreret code in the
mcelog, leaving me some errors about the Northbridge.
If I do it again it gives me something else. I made 2
digital photo's of 2 lockups when it happened and this
is the result of the tool, the TSC is different in
both errors,
Hendrik . wrote:
So I think there is a problem with this specific CK804
ATA controller causing the MCE... Any clues?
Yes, the SATA chip is broken. Probably time to check the known errata
on the chip, and if it isn't known, bring nvidia in to debug their
silicon.
-
To unsubscribe from this
After even more tests I found out the following:
- Running 'dd_rescue /dev/sda1 /dev/zero' on the
on-board Silicon Image Inc. SiI 3114 controller
handles the bad sector just fine and does not give a
MCE. This is on the same motherboard that does give
the MCE error on the Nvidia port.
The
After even more tests I found out the following:
- Running 'dd_rescue /dev/sda1 /dev/zero' on the
on-board Silicon Image Inc. SiI 3114 controller
handles the bad sector just fine and does not give a
MCE. This is on the same motherboard that does give
the MCE error on the Nvidia port.
The
Ok, I did actually not copy the coreret code in the
mcelog, leaving me some errors about the Northbridge.
If I do it again it gives me something else. I made 2
digital photo's of 2 lockups when it happened and this
is the result of the tool, the TSC is different in
both errors, the rest is the
>> hangs. If I try it after a reboot with 'mcelog --k8
>> --ascii' or whatever parameter, there is no output
at
> You could type error back in from the email ?
Ok I copied it into the tool, it gives me:
CPU 0 4 northbridge TSC b7d4a144d0
Northbridge ECC error
ECC syndrome = 0
STATUS 0
> How can I do this? I have installed mcelog but I
> cannot run it after the MCE error because the whole PC
> hangs. If I try it after a reboot with 'mcelog --k8
> --ascii' or whatever parameter, there is no output at
You could type error back in from the email ?
> Isn't it strange to say that
Probably a similar problem is described in the
linux-ide mailing list a while ago:
http://www.opensubscriber.com/message/[EMAIL PROTECTED]/6490911.html
>> Argh. I'm seeing a show stopper bug on sata_nv
here.
>> ata_exec_internal
>> is MCE-ing on the READ_NATIVE_MAX_EXT command on
>> both
> > HARDWARE ERROR
> > CPU 0: Machine Check Exception: 4 Bank 4:
> > b2070f0f
> > TSC b7d4a144d0
> > This is not a software problem!
> > Run through mcelog --ascii to decode and contact
> your
> > hardware vendor
> > Kernel panic - not syncing: Machine check
>
> You should run this
Hendrik . wrote:
Last night I discovered a problem in my RAID5 array
and finally after a lot of tests I narrowed it down to
a bad sector on one of the hard disks and some goofy
kernels.
I just yesterday build a new PC using an existing
array of 5 disks in RAID 5. I did build the array with
only
Hendrik . wrote:
Last night I discovered a problem in my RAID5 array
and finally after a lot of tests I narrowed it down to
a bad sector on one of the hard disks and some goofy
kernels.
I just yesterday build a new PC using an existing
array of 5 disks in RAID 5. I did build the array with
only
HARDWARE ERROR
CPU 0: Machine Check Exception: 4 Bank 4:
b2070f0f
TSC b7d4a144d0
This is not a software problem!
Run through mcelog --ascii to decode and contact
your
hardware vendor
Kernel panic - not syncing: Machine check
You should run this through mcelog as it
Probably a similar problem is described in the
linux-ide mailing list a while ago:
http://www.opensubscriber.com/message/[EMAIL PROTECTED]/6490911.html
Argh. I'm seeing a show stopper bug on sata_nv
here.
ata_exec_internal
is MCE-ing on the READ_NATIVE_MAX_EXT command on
both i386 and
How can I do this? I have installed mcelog but I
cannot run it after the MCE error because the whole PC
hangs. If I try it after a reboot with 'mcelog --k8
--ascii' or whatever parameter, there is no output at
You could type error back in from the email ?
Isn't it strange to say that the
hangs. If I try it after a reboot with 'mcelog --k8
--ascii' or whatever parameter, there is no output
at
You could type error back in from the email ?
Ok I copied it into the tool, it gives me:
CPU 0 4 northbridge TSC b7d4a144d0
Northbridge ECC error
ECC syndrome = 0
STATUS 0 MCGSTATUS
Ok, I did actually not copy the coreret code in the
mcelog, leaving me some errors about the Northbridge.
If I do it again it gives me something else. I made 2
digital photo's of 2 lockups when it happened and this
is the result of the tool, the TSC is different in
both errors, the rest is the
18 matches
Mail list logo
