Re: 2.5.65: oops: EIP at current_kernel_time +0x0f/0x40

William Lee Irwin III (wli@holomorphy.com)
Sat, 22 Mar 2003 04:46:07 -0800

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Alexander Hoogerhuis: "2.5.65-mm3 bad: scheduling while atomic! [SCSI]"
Previous message: Bill Davidsen: "Re: [2.5.65] Broken gcc test"
In reply to: Jos Hulzink: "Re: 2.5.65: oops: EIP at current_kernel_time +0x0f/0x40"

On Sat, Mar 22, 2003 at 01:34:41PM +0100, Jos Hulzink wrote:
> 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
> ;-)

Which SCSI? I've been seeing numerous aic7xxx badnesses ca. whatever bk
snapshot 2.5.65-mm2 was based on. Still looking for the use-after-free...

-- wli
-
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/

Next message: Alexander Hoogerhuis: "2.5.65-mm3 bad: scheduling while atomic! [SCSI]"
Previous message: Bill Davidsen: "Re: [2.5.65] Broken gcc test"
In reply to: Jos Hulzink: "Re: 2.5.65: oops: EIP at current_kernel_time +0x0f/0x40"