Bug #1823

panic after xdm is started

Added by Johannes.Hofmann almost 4 years ago. Updated almost 4 years ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-

Description

Hi,

with recent kernel (v2.7.3.840.gf5f1b-DEVELOPMENT) I get a panic on my
UP laptop when I start xdm. Xorg without xdm works ok.
It seems that after xdm has been started a subsequent
kprintf() causes the panic. I've seen different kprintf()'s causing
this. The panic message is:
panic: Attempt to acquire token 0xc03dc800 not already held in hard
code section
A dump is on leaf.

Cheers,
Johannes

PS: With this new kernel the system (or is it X11?) feels a lot
snappier :-)

History

#1 Updated by dillon almost 4 years ago

:Hi,
:
:with recent kernel (v2.7.3.840.gf5f1b-DEVELOPMENT) I get a panic on my
:UP laptop when I start xdm. Xorg without xdm works ok.
:It seems that after xdm has been started a subsequent
:kprintf() causes the panic. I've seen different kprintf()'s causing
:this. The panic message is:
:panic: Attempt to acquire token 0xc03dc800 not already held in hard
:code section
:A dump is on leaf.
:
:Cheers,
:Johannes

Very nice dump, I'm working on it. It looks like a tty token is being
improperly acquired in the kprintf() path.

:PS: With this new kernel the system (or is it X11?) feels a lot
: snappier :-)

Yes, for me too.

-Matt
Matthew Dillon
<>

#2 Updated by dillon almost 4 years ago

This should be fixed momentarily. I just have to test it. The
problem is the console intercept that X/xdm does. This causes
kprintf()'s to run through the constty and if the kprintf() is
made from a hard code section (which is a set of assertions that
I added recently) then Ka-Boom.

I'm changing it to only use the console tty if it can get the
tty_token non-blocking. Certainly this is not perfect, and if
it isn't good enough I'll remove the console intercept entirely
(which was a bad idea anyway, long ago).

-Matt
Matthew Dillon
<>

#3 Updated by sjg almost 4 years ago

Is this confirmed fixed?

#4 Updated by Johannes.Hofmann almost 4 years ago

"Samuel J. Greear \(via DragonFly issue tracker\)" <> wrote:
>
> Samuel J. Greear <> added the comment:
>
> Is this confirmed fixed?

Yes, it's fixed.

Johannes

Also available in: Atom PDF