Messages in this thread | | | From | Jos Hulzink <> | Subject | Re: 2.5.65: oops: EIP at current_kernel_time +0x0f/0x40 | Date | Sat, 22 Mar 2003 13:34:41 +0100 |
| |
On Saturday 22 March 2003 13:17, Andrew Morton wrote: > Jos Hulzink <josh@stack.nl> wrote: > > Hi, > > > > Here the early oops I'm stuck with in 2.5.65. Had to write it down > > manually, so the report is not complete. If I missed something crucial, > > please ask. The bug is easy to reproduce, so I can write anything down > > you need. > > > > exact oops message scrolled away, console isn't set up yet, so I can't > > scroll back. > > > > EIP at current_kernel_time +0x0f/0x40 > > That might be an lfence instruction. I suspect you've chosen the wrong > CPU type?
Gee, you guys are good. Now I'm only left wondering how this setting could be reset to PIV, while I'm sure I set it to PII (as you can see from earlier postings, I managed to get it running till a SCSI lockup caused by probably IRQ prioblems). For now I'll not blame the kernel and tell myself I'm stupid ;-)
Jos - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |