Skip to contentSkip to conversation

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

DISCUSSION Jos Hulzink 3 participants 5 messages Mar 22, 2003

lore
Share & tools
lore
#0 lore raw

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

called from:

sysfs_new_inode
sysfs_fill_super
get_sb_single
do_kern_mount
sysfs_fill_super
rest_init
kern_mount
rest_init

My config is attached.

Jos

#1 lore raw
Quoted 12 lines · Jos Hulzink

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?

#2 lore raw
Quoted 8 lines · Andrew Morton
Quoted 7 lines · Jos Hulzink

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.

Quoted 7 lines
Quoted 4 lines

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

#3 lore raw
Quoted 5 lines · Jos Hulzink

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

#4 lore raw
Quoted 9 lines · William Lee Irwin III
Quoted 5 lines · Jos Hulzink

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...

00:06.0 SCSI storage controller: Adaptec AIC-7880U

Onboard SCSI controller, MPS 1.4 enabled Intel 440 LX chipset (i.e. IRQ rerouting and stuff) Kernel is recompiled now (processor type change takes a while, for you need to recompile everything from scatch) to test the different IRQ settings, have dealt with problems like these before.

Note that I'm testing the official,plain Linus-2.5.65

Jos