On Mon, May 13, 2013 at 12:40 PM, Christian T. Steigies <[email protected]> wrote:
>> > Well, I had this example last week where during two builds different test
>> > cases failed, and the third build succeeded. If this is the hardware, what
>> > should I do, reseat the CPU? I think Michael gave me a spare 060 some time
>> > ago... but Ingo has similar problems, but not with old kernels?
>>
>> Could be a kernel issue with '060s.
>
> Thats what I want to hear! And now that our kernel hacker is listening, what
> can we do to track this down and fix it?
If there are no problems with older kernels, you can try to bisect it.
Is it easy to trigger?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
Archive:
http://lists.debian.org/camuhmdwq6xcown6w_vk+gdj-zv5v7phxj+fzrn3wlnum1ns...@mail.gmail.com
