Bug#639901: linux-image-3.0.0-1-686-pae: WARNING at radeon_fence wait: GPU lockup -- when starting gdm3, some fonts glyphs missings
Package: linux-2.6
Version: 3.0.0-3
Severity: important
I was booting about 10 times on this kernel and didn't have this issues.
Also I had no problem with my hardware.
When I was in the middle of boot process, and when gdm3 just started
starting (Xorg already started, blanked screen, and showed
spiining waithing wheel), I hit Ctrl-Alt-F1 to go back to the console
(I often do so, to look for the rest of the boot process, and to work from
the console).
This times however, just moments after seeing console (gdm3 was still initializing
and displaying its loging screen in the background), I saw warning
at 106 seconds on the screen (kernel log below).
I waited for boot process to end.
After switching back to Alt-F7, some font glyphs was missing (not rendered).
It was missing glyphs in user logins menu and system menu (this with restart / poweroff).
Notably glyphs a and i was missing, few others, but few other letters was present.
missing glyphs renderes just like empty space (probably with variable size like original glyphs).
Background color wasn't changed on this empty space (just like putting there a space).
Restarting gdm3 solved this problem. Strange.
It was fresh boot, no
upgrades going on in the same time gdm was starting or running.
Do not know if this is reproductible even on my hardware,
and with what freqency.
Thanks.
-- Package-specific info:
** Version:
Linux version 3.0.0-1-686-pae (Debian 3.0.0-3) (ben@decadent.org.uk) (gcc version 4.5.3 (Debian 4.5.3-8) ) #1 SMP Sat Aug 27 16:41:03 UTC 2011
iface tun0 inet static
pre-up ssh -N -f -w 0:0 149.156.82.206 'ifdown tun0; ifup tun0'
pre-up sleep 5
address 10.4.0.200
pointopoint 10.4.0.100
netmask 255.255.255.0
up /sbin/ip r add 10.4.0.0/24 via 10.4.0.200 dev tun0
up /sbin/ip r add 149.156.89.111 via 10.4.0.200 dev tun0
down /sbin/ip r del 149.156.89.111 via 10.4.0.200 dev tun0
down /sbin/ip r del 10.4.0.0/24 via 10.4.0.200 dev tun0
** Network status:
*** IP interfaces and addresses:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN qlen 1000
link/ether aa:00:04:00:0a:04 brd ff:ff:ff:ff:ff:ff
dnet 1.10/16 scope global eth0
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 00:16:6f:ba:e0:60 brd ff:ff:ff:ff:ff:ff
inet 10.6.6.11/24 brd 10.6.6.255 scope global eth1
inet6 fe80::216:6fff:feba:e060/64 scope link
valid_lft forever preferred_lft forever
4: dummy0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1370 qdisc noqueue state UNKNOWN
link/ether ba:9f:a6:b8:64:3c brd ff:ff:ff:ff:ff:ff
inet 1.0.0.1/24 scope global dummy0:1
inet6 2001:1d:de37:bbda:2c0d:4589:93bd:6f8f/28 scope global
valid_lft forever preferred_lft forever
inet6 fe80::b89f:a6ff:feb8:643c/64 scope link
valid_lft forever preferred_lft forever
5: virbr1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN
link/ether de:b4:25:4c:11:8d brd ff:ff:ff:ff:ff:ff
inet 192.168.130.1/24 brd 192.168.130.255 scope global virbr1
8: teredo: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1280 qdisc pfifo_fast state UNKNOWN qlen 500
link/none
inet6 2001:0:53aa:64c:1430:752f:a42a:f8/32 scope global
valid_lft forever preferred_lft forever
inet6 fe80::ffff:ffff:ffff/64 scope link
valid_lft forever preferred_lft forever
*** Protocol statistics:
Ip:
2361 total packets received
0 forwarded
0 incoming packets discarded
2280 incoming packets delivered
2420 requests sent out
4361 dropped because of missing route
30 reassemblies required
15 packets reassembled ok
Icmp:
26 ICMP messages received
0 input ICMP message failed.
ICMP input histogram:
destination unreachable: 6
echo replies: 20
44 ICMP messages sent
0 ICMP messages failed
ICMP output histogram:
destination unreachable: 24
echo request: 20
IcmpMsg:
InType0: 20
InType3: 6
OutType3: 24
OutType8: 20
Tcp:
60 active connections openings
16 passive connection openings
5 failed connection attempts
0 connection resets received
5 connections established
1072 segments received
1047 segments send out
28 segments retransmited
0 bad segments received.
7 resets sent
Udp:
1229 packets received
22 packets to unknown port received.
0 packet receive errors
1387 packets sent
UdpLite:
TcpExt:
1 invalid SYN cookies received
24 TCP sockets finished time wait in fast timer
37 delayed acks sent
Quick ack mode was activated 6 times
105 packets directly queued to recvmsg prequeue.
48454 bytes directly received in process context from prequeue
388 packet headers predicted
35 packets header predicted and directly queued to user
253 acknowledgments not containing data payload received
37 predicted acknowledgments
2 times recovered from packet loss by selective acknowledgements
2 congestion windows recovered without slow start after partial ack
1 timeouts after SACK recovery
1 timeouts in loss state
7 fast retransmits
6 retransmits in slow start
5 other TCP timeouts
1 SACK retransmits failed
6 DSACKs sent for old packets
2 DSACKs received
2 DSACKs for out of order packets received
1 connections aborted due to timeout
TCPDSACKIgnoredNoUndo: 2
TCPSackShiftFallback: 17
IPReversePathFilter: 2
IpExt:
InMcastPkts: 78
OutMcastPkts: 61
InOctets: 1066789
OutOctets: 394705
InMcastOctets: 17456
OutMcastOctets: 15316
Kernel: Linux 3.0.0-1-686-pae (SMP w/1 CPU core)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to pl_PL.UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages linux-image-3.0.0-1-686-pae depends on:
ii debconf [debconf-2.0] 1.5.41
ii initramfs-tools [linux-initramfs-tool] 0.99
ii linux-base 3.3
ii module-init-tools 3.16-1
Versions of packages linux-image-3.0.0-1-686-pae recommends:
ii firmware-linux-free 3
ii libc6-i686 2.13-18
Versions of packages linux-image-3.0.0-1-686-pae is related to:
ii firmware-bnx2 <none>
ii firmware-bnx2x <none>
ii firmware-ipw2x00 0.33
ii firmware-ivtv <none>
ii firmware-iwlwifi <none>
ii firmware-linux <none>
ii firmware-linux-nonfree 0.33
ii firmware-qlogic <none>
ii firmware-ralink <none>
ii xen-hypervisor-4.1-i386 [xen-hypervisor] 4.1.1-2
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110831134532.21915.41388.reportbug@sredniczarny. smp.if.uj.edu.pl">http://lists.debian.org/20110831134532.21915.41388.reportbug@sredniczarny. smp.if.uj.edu.pl
09-01-2011, 04:27 AM
Ben Hutchings
Bug#639901: linux-image-3.0.0-1-686-pae: WARNING at radeon_fence wait: GPU lockup -- when starting gdm3, some fonts glyphs missings
On Wed, 2011-08-31 at 15:45 +0200, Witold Baryluk wrote:
> Package: linux-2.6
> Version: 3.0.0-3
> Severity: important
>
> I was booting about 10 times on this kernel and didn't have this issues.
> Also I had no problem with my hardware.
>
> When I was in the middle of boot process, and when gdm3 just started
> starting (Xorg already started, blanked screen, and showed
> spiining waithing wheel), I hit Ctrl-Alt-F1 to go back to the console
> (I often do so, to look for the rest of the boot process, and to work from
> the console).
>
> This times however, just moments after seeing console (gdm3 was still initializing
> and displaying its loging screen in the background), I saw warning
> at 106 seconds on the screen (kernel log below).
Please report this upstream at <https://bugs.freedesktop.org> under
product 'DRI', component 'DRM/Radeon'. Let us know the bug number or
URL so we can track it.
> I waited for boot process to end.
>
> After switching back to Alt-F7, some font glyphs was missing (not rendered).
> It was missing glyphs in user logins menu and system menu (this with restart / poweroff).
> Notably glyphs a and i was missing, few others, but few other letters was present.
> missing glyphs renderes just like empty space (probably with variable size like original glyphs).
> Background color wasn't changed on this empty space (just like putting there a space).
>
> Restarting gdm3 solved this problem. Strange.
[...]
If the kernel driver resets the GPU, it can presumably destroy data
stored in the GPU memory by the X driver. If you restart gdm then you
are restarting the X server which will then reinitialise this data.
Ben.
09-01-2011, 04:27 AM
Ben Hutchings
Bug#639901: linux-image-3.0.0-1-686-pae: WARNING at radeon_fence wait: GPU lockup -- when starting gdm3, some fonts glyphs missings
On Wed, 2011-08-31 at 15:45 +0200, Witold Baryluk wrote:
> Package: linux-2.6
> Version: 3.0.0-3
> Severity: important
>
> I was booting about 10 times on this kernel and didn't have this issues.
> Also I had no problem with my hardware.
>
> When I was in the middle of boot process, and when gdm3 just started
> starting (Xorg already started, blanked screen, and showed
> spiining waithing wheel), I hit Ctrl-Alt-F1 to go back to the console
> (I often do so, to look for the rest of the boot process, and to work from
> the console).
>
> This times however, just moments after seeing console (gdm3 was still initializing
> and displaying its loging screen in the background), I saw warning
> at 106 seconds on the screen (kernel log below).
Please report this upstream at <https://bugs.freedesktop.org> under
product 'DRI', component 'DRM/Radeon'. Let us know the bug number or
URL so we can track it.
> I waited for boot process to end.
>
> After switching back to Alt-F7, some font glyphs was missing (not rendered).
> It was missing glyphs in user logins menu and system menu (this with restart / poweroff).
> Notably glyphs a and i was missing, few others, but few other letters was present.
> missing glyphs renderes just like empty space (probably with variable size like original glyphs).
> Background color wasn't changed on this empty space (just like putting there a space).
>
> Restarting gdm3 solved this problem. Strange.
[...]
If the kernel driver resets the GPU, it can presumably destroy data
stored in the GPU memory by the X driver. If you restart gdm then you
are restarting the X server which will then reinitialise this data.