Fedora 20 , Problems , Problems and Problems.

[Ger van Dijck]

Hello ,

First excuses for the "test" I abusively did sent .

I have a new machine : Dell Inspiron 3721 , disk 1 TB, VGA compatible  
controller 3rd generation Rev.09 Intelcorp and Radeon HD 8730 M , Mem size  
8 Gb.

First problem :

I cannot adjust the brightnes of the screen.

Second problem :

When booting I get the message

[2.234578] drm:cpt-error-serr-int-handler *ERROR* PHC encoder A FIFO  
underrun.

Third problem :

After login I get the message : GDBus.Error.org.free  
desktop.Policikit1.Error.Failed :
An autification agent already exists for the given subject.

Fourth problem :

When rebooting I get the message : [429.0649464] watchdog watchdog0:  
watchdog did not stop !

Fifth problem :

When halting the system I get the following message and thereafter I have  
to power off manually :

[439.308512] radeon 000:01::00.0:ring3 stalled for more than 1000msec
[440.686009] [drm:r600-ib-test]*ERROR*radeon:fence wait failed (-35)
[440.686050] [drm .radeon-ib-ring-tests]*ERROR*radeon failed testing IB on  
GFX ring (-35)
[440.6860931 [drm:radeon resume-kms]*ERROR*ibring test failed (-35)

Be so kind to inform me ,

Ger van Dijck.

[Kevin Fenzi]

On Wed, 27 Aug 2014 16:19:57 +0200
"Ger van Dijck"  wrote:
> Hello ,
>
> First excuses for the "test" I abusively did sent .
>
> I have a new machine : Dell Inspiron 3721 , disk 1 TB, VGA
> compatible controller 3rd generation Rev.09 Intelcorp and Radeon HD
> 8730 M , Mem size 8 Gb.

First as a general troubleshooting tool, have you applied all updates
and rebooted into the latest kernel? Some of the issues below might be
already fixed.
> First problem :
>
> I cannot adjust the brightnes of the screen.

There's been a lot of work on this in recent kernels. Do try the most
recent updated one.

Did you install in 'basic' graphics mode and/or are passing 'nomodeset'
on the boot line? If so, that could be the problem as that will cause
you to get the VESA graphics driver that can't do lots of things.
> Second problem :
>
> When booting I get the message
>
> [2.234578] drm:cpt-error-serr-int-handler *ERROR* PHC encoder A FIFO  
> underrun.
>
> Third problem :
>
> After login I get the message : GDBus.Error.org.free  
> desktop.Policikit1.Error.Failed :
> An autification agent already exists for the given subject.

Is that in a pop up? Dialog? When you do something?
> Fourth problem :
>
> When rebooting I get the message : [429.0649464] watchdog watchdog0:  
> watchdog did not stop !

Odd. Watchdog shouldn't be enabled by default. Did you configure it any?
> Fifth problem :
>
> When halting the system I get the following message and thereafter I
> have to power off manually :
>
> [439.308512] radeon 000:01::00.0:ring3 stalled for more than 1000msec
> [440.686009] [drm:r600-ib-test]*ERROR*radeon:fence wait failed (-35)
> [440.686050] [drm .radeon-ib-ring-tests]*ERROR*radeon failed testing
> IB on GFX ring (-35)
> [440.6860931 [drm:radeon resume-kms]*ERROR*ibring test failed (-35)

No idea off hand. :(

kevin

[Tom Horsley]

On Wed, 27 Aug 2014 09:12:57 -0600
Kevin Fenzi wrote:
> > When rebooting I get the message : [429.0649464] watchdog watchdog0:  
> > watchdog did not stop !
>
> Odd. Watchdog shouldn't be enabled by default. Did you configure it any?

I've gotten that every time I rebooted for a long time, going
back to at least f18 I think. It never seems to hurt anything
other than maybe taking an extra second or so at the end of
the reboot sequence.

[Kevin Fenzi]

On Wed, 27 Aug 2014 11:35:13 -0400
Tom Horsley  wrote:
> On Wed, 27 Aug 2014 09:12:57 -0600
> Kevin Fenzi wrote:
> > > When rebooting I get the message : [429.0649464] watchdog
> > > watchdog0: watchdog did not stop !
> >
> > Odd. Watchdog shouldn't be enabled by default. Did you configure it
> > any?
>
> I've gotten that every time I rebooted for a long time, going
> back to at least f18 I think. It never seems to hurt anything
> other than maybe taking an extra second or so at the end of
> the reboot sequence.

Huh. I see it here too, so I did a bit of digging.

it's actually systemd. It fires up the kernel watchdog and sets a
10minute timeout. Then it does some more things. If any of them hang,
10min later the watchdog reboots your machine instead of it hanging
forever.

https://bbs.archlinux.org/viewtopic.php?pid=1372562#p1372562

seems to be a good summary. ;)

You learn something every day (if you are lucky).

kevin