On Tue, Dec 9, 2008 at 9:00 AM, Mikael Abrahamsson <[email protected]> wrote:
> On Tue, 9 Dec 2008, Giangiacomo Mariotti wrote:
>
>> In its i386 version the mce didn't get logged for me too, but I noticed
>> something like an option for non critical MCEs wasn't configured in the i386
>> kernel. That might be the cause, or it's just a problem for the 64 bit
>> version. Anyway, as I've already posted here lkml.org/lkml/2008/12/9/4,
>> rebooting with a kexec completely removes the MCE, so I guess it's a bios
>> problem.
>
> Yes, this bios seems very flakey. After I have booted linux a few times
> (haven't narrowed down the problem exactly) both rtl8169 devices are removed
> for me. They're completely gone, lspci doesn't show them, neither are they
> shown in bios bootup screen. The built in bios cable testing option doesn't
> find them either.
>
> Factory default:ing the BIOS usually bring them back. I have resorted to a
> PCI 32bit e1000 for network connectivity because I grew bored of resetting
> the bios every couple of times I booted linux on it.
>
> Vista doesn't cause this problem from what I have seen (but it might, I
> don't have enough data).
>
> --
> Mikael Abrahamsson email: [email protected]
>
Yes, that happens to me too regularly. Also now my bios completely
freezes after having successfully done the dmi pool check at boot if I
try to boot directly from my HD, so I have to boot from my usb dvd
writer. At the moment I successfully booted that rescuecd in 64 bit
mode and the kexeced into my 2.6.27.8 debian system. I still haven't
tried to make a bootable cd with grub and see if I can also boot
directly into my HD at boot or if not even Grub can see it. The very
good point of using the kexec method is that, even if my bios cannot
boot my hd directly, I can bypass it. But I still don't know if I have
this problem too.
On Tue, Dec 9, 2008 at 9:30 AM, Giangiacomo Mariotti
<[email protected]> wrote:
> Yes, that happens to me too regularly. Also now my bios completely
> freezes after having successfully done the dmi pool check at boot if I
> try to boot directly from my HD, so I have to boot from my usb dvd
> writer. At the moment I successfully booted that rescuecd in 64 bit
> mode and the kexeced into my 2.6.27.8 debian system. I still haven't
> tried to make a bootable cd with grub and see if I can also boot
> directly into my HD at boot or if not even Grub can see it. The very
> good point of using the kexec method is that, even if my bios cannot
> boot my hd directly, I can bypass it. But I still don't know if I have
> this problem too.
>
Well, I'm not exactly sure that the dmi pool check is successful.