On Wed, 11 Oct 2000 14:26:08 +0100 (BST), [EMAIL PROTECTED] wrote: >I actually thought that the i686 target was the same as the i586 target >with different instruction scheduling rules. Seems my judgement was off. >/me goes to read gcc docs Sounds like you got caught by the conditional move instruction that is generated for 686. It causes oops on 586, and somewhere in the oops or printk code you hit another cmove. Double fault, kernel hang. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
- Re: [OT] linux article with kernel referenc... Alan Cox
- Re: [OT] linux article with kernel refe... Roman Zippel
- Re: [OT] linux article with kernel... John Alvord
- Re: [OT] linux article with ke... James Simmons
- Re: 2.4.0-test9 + Winchip2/2A processor family ... Frank de Lange
- Re: 2.4.0-test9 + Winchip2/2A processor family ... Frank de Lange
- Re: 2.4.0-test9 + Winchip2/2A processor family ... Frank de Lange
- Re: 2.4.0-test9 + Winchip2/2A processor fam... Alan Cox
- Re: 2.4.0-test9 + Winchip2/2A processor fam... davej
- Re: 2.4.0-test9 + Winchip2/2A processor... Keith Owens
- Re: 2.4.0-test9 + Winchip2/2A proc... davej
- Re: 2.4.0-test9 + Winchip2/2A ... Jamie Lokier
- Re: 2.4.0-test9 + Winchip2/2A processor... Michael Meissner
- Re: 2.4.0-test9 + Winchip2/2A processor family == hang o... Mikael Pettersson