Ticket #1689 (new bug)

Opened 18 months ago

Last modified 4 months ago

acquire_sem doesn't timeout

Reported by: marcusoverhagen Owned by: marcusoverhagen
Priority: blocker Milestone: R1
Component: System/Kernel Version: R1 development
Cc: Blocked By:
Platform: All Blocking:

Description

acquire_sem doesn't timeout after 100ms in the ide stack.

This is reproduceable with r23209 and earlier, happens with 4 cores, and also when SMP is disabled by boot menu.

Attachments

haiku-smp-prob12.txt (109.7 KB) - added by marcusoverhagen 18 months ago.
test with 4 cores active
haiku-smp-prob13.txt (67.8 KB) - added by marcusoverhagen 18 months ago.
test with SMP disabled
haiku-smp-prob14.txt (97.9 KB) - added by marcusoverhagen 18 months ago.
retest 1 with syslog disabled
haiku-smp-prob15.txt (66.8 KB) - added by marcusoverhagen 18 months ago.
retest 2 with syslog disabled
haiku-smp-prob16.txt (70.0 KB) - added by marcusoverhagen 18 months ago.
retest 3 with syslog disabled
interrupts.txt (6.0 KB) - added by marcusoverhagen 18 months ago.
Interrupts

Change History

Changed 18 months ago by marcusoverhagen

test with 4 cores active

Changed 18 months ago by marcusoverhagen

test with SMP disabled

Changed 18 months ago by axeld

So it's inside dprintf_args() and never returns from there? What the hell is it doing there? Is it possible that writing to the syslog is the problem here?

Changed 18 months ago by marcusoverhagen

retest 1 with syslog disabled

Changed 18 months ago by marcusoverhagen

retest 2 with syslog disabled

Changed 18 months ago by marcusoverhagen

retest 3 with syslog disabled

Changed 18 months ago by marcusoverhagen

I disabled syslog and retried three times. First try was different, but 2 and 3 get stuck at the same point.

Changed 18 months ago by marcusoverhagen

Interrupts

Changed 18 months ago by marcusoverhagen

I think it is quite likely that the IDE stack never acknowleges the IRQ 11, and that is the reason why the system is stuck at the restore_interrupts() after dprintf.

I'll have a look at that.

Changed 18 months ago by axeld

  • owner changed from axeld to marcusoverhagen

Changed 8 months ago by jackburton

Is this still valid ?

Changed 4 months ago by stippi

  • milestone changed from R1/alpha1 to R1

Even if this is still valid, it's certainly an issue on specific hardware, not a general issue. Therefore I don't believe it should be in the R1/alpha1 milestone.

Note: See TracTickets for help on using tickets.