instant reboot when Xorg exits on 8.1-RC2 with Radeon 4850

swills@

swills@

Developer
Subject pretty much says it all. I've upgraded my 8.0-STABLE system to 8.1-RC2 and updated ports. I use KDM and can login to KDE4 just fine. However, when I log out, my system reboots. I've tried setting dumpdev in /etc/rc.conf in hopes of getting a panic message, but there isn't one. Any ideas would be appreciated.
 
I realized I should include more info. I'm using the radeonhd driver. I tried radeonhd-devel, but get the same behavior. Another thing I've noticed (by disabling kdm and using startx) is that it isn't the logout that causes the reboot, it's starting X the second time.
 
swills said:
I realized I should include more info. I'm using the radeonhd driver.
Click to expand...

Use radeon instead.

I tried radeonhd-devel, but get the same behavior. Another thing I've noticed (by disabling kdm and using startx) is that it isn't the logout that causes the reboot, it's starting X the second time.
Click to expand...

/var/log/Xorg.0.log might be useful in seeing what's happening.
 
Code: 
(EE) config/hal: couldn't initialise context: unknown error (null)

That looks odd but certainly shouldn't cause a reboot. Nothing else really jumps out.

Maybe it's not X but something in KDE. Do you still have the problem if you just run twm from .xinitrc?
Code: 
twm &
xclock -geometry 50x50-1+1 &
xterm -geometry 80x50+494+51 &
xterm -geometry 80x20+494-0 &
exec xterm -geometry 80x66+0+0 -name login
 
Yep, doesn't really matter if it's KDM or if I disable that and run startx (with twm) from command line. First time it starts up fine, second time, instant reboot.
 
Worth testing with Composite disabled, but that seems doubtful.

Are there any odd things going on, like custom CFLAGS or overclocking?
 
The CPU is overclocked, but only slightly and that has never been a problem before. It's an Intel Core i7 920, currently at 3ghz, and from what I've read, it can handle a lot more. Been like that for over a year and never had any problems on 8.0

There are no custom CFLAGS.

Disabling Composite didn't change anything.
 
When I was on 8.0 I was also on Xorg 7.4. Both were upgraded at the same time. Sorry if that was misleadingly worded.
 
What happens if you unload the 'radeon' kernel module after starting X, and then reloading it manually before starting X the second time?

Adam
 
With my current xorg.conf, radeon kernel modules is not even getting loaded. And yet the problem still happens.
 
swills said:
With my current xorg.conf, radeon kernel modules is not even getting loaded. And yet the problem still happens.
Click to expand...

Sorry, I don't understand. radeon.ko should be auto-loaded when you start X, and should still be hanging around after exit:

Code: 
% kldstat
Id Refs Address    Size     Name
...
 7    1 0xc6487000 68000    radeon.ko
 8    1 0xc64ef000 13000    drm.ko

Unless you have it built into the kernel (but why?).

Just to make sure I'm not assuming something:
WITHOUT_NOUVEAU=yes in /etc/make.conf
upgraded to 8.1-rc2 via source; didn't forget installworld!
 
wblock said:
Sorry, I don't understand. radeon.ko should be auto-loaded when you start X, and should still be hanging around after exit:

Code: 
% kldstat
Id Refs Address    Size     Name
...
 7    1 0xc6487000 68000    radeon.ko
 8    1 0xc64ef000 13000    drm.ko

Unless you have it built into the kernel (but why?).

Just to make sure I'm not assuming something:
WITHOUT_NOUVEAU=yes in /etc/make.conf
upgraded to 8.1-rc2 via source; didn't forget installworld!
Click to expand...

He said he disabled DRI previously, so I assume that's why radeon isn't getting loaded.

The odd thing here is that most graphics related reboots and hangs are due to the kernel DRM code, but apparently that's not the case for the OP.

Adam
 
adamk said:
He said he disabled DRI previously, so I assume that's why radeon isn't getting loaded.
Click to expand...

Assumption on my part; if it didn't make any difference, I'd have turned it back on to avoid changing more than one thing at a time.
 
Fair point, but it was easier to test with it already disabled and since it didn't make a difference, I didn't bother testing the other way. I do have WITHOUT_NOUVEAU=yes in /etc/make.conf, BTW.
 
Decided to try unloading radeon and drm after the first start. Now when I try to startx the second time, I get:

Code: 
(EE) Failed to load module "fbdev" (module does not exist, 0)
(EE) RADEON(0): No valid MMIO address
(EE) Screen(s) found, but none have a usable configuration.
If I then manually load them, it changes slightly to:

Code: 
(EE) Failed to load module "fbdev" (module does not exist, 0)
(EE) RADEON(0): No valid linear framebuffer address
(EE) Screen(s) found, but none have a usable configuration.
No idea what to make of that.
 
Oh, and if I then switch it to radeonhd, I get:

Code: 
(EE) RADEONHD(0): No Video RAM detected.
(EE) Screen(s) found, but none have a usable configuration.
With this in the log:


Code: 
(II) RADEONHD(0): Analog TV Default Mode: 8
(II) RADEONHD(0): Found default TV Mode PAL
(II) RADEONHD(0): The detected amount of videoram exceeds the PCI BAR aperture.
(II) RADEONHD(0): Using only 0kB of the total 1048576kB.
(EE) RADEONHD(0): No Video RAM detected.
(II) UnloadModule: "radeonhd"
(EE) Screen(s) found, but none have a usable configuration.
Seems like a bug in drm, but I'm not sure.
 
It doesn't make sense that it's a bug in the DRM since you have this problem even when the 'radeon' kernel module isn't loaded.

Adam
 
swills said:
The CPU is overclocked, but only slightly and that has never been a problem before. It's an Intel Core i7 920, currently at 3ghz, and from what I've read, it can handle a lot more. Been like that for over a year and never had any problems on 8.0
Click to expand...

Back to this: you have a newer version of the OS along with different xorg-server and drivers. Maybe now it's touchier about the overclocking.
 
You must log in or register to reply here.
Back
Top