Your message dated Fri, 4 Aug 2006 00:46:10 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#364437: Uhm...
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: linux-2.6
Severity: critical
Justification: breaks the whole system
Hopefully my classification justification is correct, otherwise I have
to apologize.
When I'm using xawtv in overlay mode and at the same time, nxtvepg is
capturing vbi data, I can easily cause the console and syslog to be
spammed with error messages like the following:
----
Apr 23 04:27:14 abrasax kernel: bttv0: OCERR @ 1a44301c,bits: HSYNC OFLOW OCERR*
Apr 23 04:27:20 abrasax last message repeated 156 times
Apr 23 04:27:20 abrasax kernel: bttv0: OCERR @ 1a44301c,bits: HSYNC OFLOW FBUS
OCERR*
Apr 23 04:27:20 abrasax kernel: bttv0: OCERR @ 1a44301c,bits: HSYNC OFLOW OCERR*
Apr 23 04:27:24 abrasax last message repeated 101 times
Apr 23 04:27:24 abrasax nxtvepg[6584]: pid 6584: terminated by signal 15
Apr 23 04:27:24 abrasax nxtvepg[6584]: fd 8: closing connection
Apr 23 04:27:24 abrasax nxtvepg[6584]: pid 6584: shutting down
Apr 23 04:27:24 abrasax kernel: bttv0: OCERR @ 1a44301c,bits: HSYNC OFLOW OCERR*
Apr 23 04:27:25 abrasax last message repeated 13 times
----
How to reproduce:
- Start nxtvepg and let acquisition start. I'm currently using the
package with the vbi workaround for bug 362153
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=362153) but the
same bug occured with 2.6.15 and before (with every 2.6 kernel I
can remember, but I've been using grabdisplay mode for a while,
which doesn't trigger it)
- start xawtv, (or probably any other tv application that is able to
display overlayed tv) in overlay mode!
- Switch xawtv to fullscreen
- Move the mouse and at the same time press 'f' to leave fullscreen mode
The screen resolution won't be changed, the tv image stands still or
gets garbled, and the console and syslog gets spammed with the "OCERR
@" messages. User interaction is still possible and turning off
acquisition in nxtvepg "frees" xawtv from its misery. (i.e. it runs
again, screen resolution is switched and the error messages stop).
Kernel log continued:
Apr 23 04:27:25 abrasax kernel: bttv0: timeout: drop=3 irq=46161/46161,
risc=00c9510c, bits: HSYNC OFLOW
Apr 23 04:27:25 abrasax kernel: bttv0: reset, reinitialize
The "reset, reinitialize" does not occur, before the acquisition is stopped.
Then eventually (in this example, almost immediately, but mostly some
time later) an oops occurs. It's sometimes possible to save buffers
and kill some applications but eventually the system will completely
hang.
Continued log:
----
Apr 23 04:27:31 abrasax nxtvepg[6708]: pid 6708: started listening on local
socket
Apr 23 04:27:31 abrasax nxtvepg[6708]: fd 8: new connection from localhost via
named socket
Apr 23 04:27:52 abrasax kernel: Unable to handle kernel paging request at
virtual address 602c4d7d
Apr 23 04:27:52 abrasax kernel: printing eip:
Apr 23 04:27:52 abrasax kernel: b014171b
Apr 23 04:27:52 abrasax kernel: *pde = 00000000
Apr 23 04:27:52 abrasax kernel: Oops: 0002 [#1]
Apr 23 04:27:52 abrasax kernel: Modules linked in: radeon drm binfmt_misc
rpcsec_gss_krb5 auth_rpcgss nfs nfsd exportfs lockd nfs_acl sunrpc autofs4 ipv6
dm_mod sha1 des nls_iso8859_15 8139cp sg sr_mod tuner tvaudio tsdev 8139too mii
snd_ens1371 gameport snd_rawmidi snd_seq_device snd_ac97_codec snd_ac97_bus
psmouse snd_pcm_oss pcspkr serio_raw floppy bttv video_buf firmware_class
compat_ioctl32 i2c_algo_bit v4l2_common btcx_risc ir_common snd_mixer_oss
tveeprom videodev snd_pcm snd_timer rtc aic7xxx scsi_transport_spi scsi_mod snd
soundcore snd_page_alloc shpchp pci_hotplug amd_k7_agp ide_cd agpgart cdrom
ohci_hcd i2c_amd756 i2c_core usbcore ext3 jbd mbcache ide_disk amd74xx generic
ide_core evdev mousedev
Apr 23 04:27:52 abrasax kernel: CPU: 0
Apr 23 04:27:52 abrasax kernel: EIP: 0060:[shmem_unlink+17/124] Not
tainted VLI
Apr 23 04:27:52 abrasax kernel: EFLAGS: 00210a17 (2.6.16-1-k7 #2)
Apr 23 04:27:52 abrasax kernel: EIP is at shmem_unlink+0x11/0x7c
Apr 23 04:27:52 abrasax kernel: eax: b0141c39 ebx: 00000000 ecx: b0183144
edx: caf27dd4
Apr 23 04:27:52 abrasax kernel: esi: c9ef217c edi: caf27dd4 ebp: cb101000
esp: c0d8bf2c
Apr 23 04:27:52 abrasax kernel: ds: 007b es: 007b ss: 0068
Apr 23 04:27:52 abrasax kernel: Process FvwmThumbnail (pid: 4909,
threadinfo=c0d8a000 task=c0d41ab0)
Apr 23 04:27:52 abrasax kernel: Stack: <0>00000000 00000000 00000000 c9ef217c
caf27dd4 b01516e5 c9ef217c caf27dd4
Apr 23 04:27:52 abrasax kernel: caf27dd4 b284d238 caf27dd4 b01531f4
c9ef217c caf27dd4 bc0ff8d4 cbfe38a0
Apr 23 04:27:52 abrasax kernel: 8ba40bd5 0000000d cb10100d 00000010
00000000 00000000 00000007 c0d8bfbc
Apr 23 04:27:52 abrasax kernel: Call Trace:
Apr 23 04:27:53 abrasax kernel: [vfs_unlink+168/211] vfs_unlink+0xa8/0xd3
Apr 23 04:27:53 abrasax kernel: [do_unlinkat+145/249] do_unlinkat+0x91/0xf9
Apr 23 04:27:53 abrasax kernel: [sysenter_past_esp+84/117]
sysenter_past_esp+0x54/0x75
Apr 23 04:27:53 abrasax kernel: Code: 01 08 4c 27 b0 ff 07 53 57 e8 48 80 01 00
58 5a 31 c9 5e 5f 5b 5e 5f 89 c8 c3 57 56 53 53 53 8b 7c 24 1c 8b 00 01 00 00
00 01 00 <00> 2c 01 76 25 0f b7 43 28 25 00 f0 00 00 3d 00 40 00 00 74 15
----
If you need more examples of those Oopses, I have several of them.
lspci output:
----
0000:00:00.0 Host bridge: Advanced Micro Devices [AMD] AMD-751 [Irongate]
System Controller (rev 23)
0000:00:01.0 PCI bridge: Advanced Micro Devices [AMD] AMD-751 [Irongate] AGP
Bridge (rev 01)
0000:00:07.0 ISA bridge: Advanced Micro Devices [AMD] AMD-756 [Viper] ISA (rev
01)
0000:00:07.1 IDE interface: Advanced Micro Devices [AMD] AMD-756 [Viper] IDE
(rev 03)
0000:00:07.3 Bridge: Advanced Micro Devices [AMD] AMD-756 [Viper] ACPI (rev 03)
0000:00:07.4 USB Controller: Advanced Micro Devices [AMD] AMD-756 [Viper] USB
(rev 06)
0000:00:08.0 SCSI storage controller: Adaptec AHA-7850 (rev 03)
0000:00:09.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 10)
0000:00:0a.0 Multimedia video controller: Brooktree Corporation Bt848 Video
Capture (rev 11)
0000:00:0c.0 Multimedia audio controller: Ensoniq 5880 AudioPCI (rev 02)
0000:01:05.0 VGA compatible controller: ATI Technologies Inc Radeon RV100 QY
[Radeon 7000/VE]
----
One of the first athlon systems, with AMD chipset. Only 550 Mhz, which
is why I definitely prefer overlay mode.
Relevant part of xawtv configuration:
----
# $Id: .xawtv,v 1.2 2006/03/31 20:26:04 friedel Exp friedel $
[global]
fullscreen = 768 x 576
ratio = 4:3
freqtab = europe-west
pixsize = 128 x 96
pixcols = 6
jpeg-quality = 75
keypad-ntsc = no
keypad-partial = yes
osd = yes
osd-position = 30 , 20
use-wm-fullscreen = no
mixer = line1
[launch]
AleVT = Ctrl+A, alevt -oldbttv 333
showtime = Ctrl+T, xawtv-showdate
# [Station name]
# capture = overlay | grabdisplay | on | off
# input = Television | Composite1 | S-Video | ...
# norm = PAL | NTSC | SECAM | ...
# channel = #
# fine = # (-128..+127)
# key = keysym | modifier+keysym
# color = #
# bright = #
# hue = #
# contrast = #
[defaults]
group = main
norm = pal
input = television
#capture = grabdisplay
capture = overlay
#color = 75%
----
Other .xawtv settings (from ~/.Xdefaults)
----
xawtv.vidmode: true
xawtv.xv: true
xawtv.xvideo: true
xawtv.xv-xvideo: true
xawtv.xv-image: true
! xawtv.xvport: ''
xawtv.gl: true
xawtv.fullscreen: false
xawtv.dga: true
xawtv.hwscale: true
xawtv.parallel: 10
----
The tv card is an old WinTV:
----
Apr 22 15:05:10 abrasax kernel: bttv0: Bt848 (rev 17) at 0000:00:0a.0, irq: 5,
latency: 64, mmio: 0xda004000
Apr 22 15:05:10 abrasax kernel: bttv0: using: *** UNKNOWN/GENERIC ***
[card=0,autodetected]
Apr 22 15:05:10 abrasax kernel: bttv0: gpio: en=00000000, out=00000000
in=00fffffb [init]
Apr 22 15:05:10 abrasax kernel: bttv0: detected by eeprom: Hauppauge (bt848)
[card=2]
Apr 22 15:05:10 abrasax kernel: tveeprom 1-0050: Hauppauge model 56304, rev D
, serial# 304485
Apr 22 15:05:10 abrasax kernel: tveeprom 1-0050: tuner model is Temic 4002FH5
(idx 14, type 0)
Apr 22 15:05:10 abrasax kernel: tveeprom 1-0050: TV standards PAL(B/G) (eeprom
0x04)
Apr 22 15:05:10 abrasax kernel: tveeprom 1-0050: audio processor is None (idx 0)
Apr 22 15:05:10 abrasax kernel: tveeprom 1-0050: has no radio
Apr 22 15:05:10 abrasax kernel: bttv0: Hauppauge eeprom indicates model#56304
Apr 22 15:05:10 abrasax kernel: bttv0: using tuner=0
Apr 22 15:05:10 abrasax kernel: bttv0: i2c: checking for MSP34xx @ 0x80... not
found
Apr 22 15:05:10 abrasax kernel: bttv0: i2c: checking for TDA9875 @ 0xb0... not
found
Apr 22 15:05:10 abrasax kernel: bttv0: i2c: checking for TDA7432 @ 0x8a... not
found
Apr 22 15:05:10 abrasax kernel: bttv0: i2c: checking for TDA9887 @ 0x86... not
found
Apr 22 15:05:10 abrasax kernel: tuner 1-0061: chip found @ 0xc2 (bt848 #0 [sw])
Apr 22 15:05:10 abrasax kernel: tuner 1-0061: type set to 0 (Temic PAL (4002
FH5))
Apr 22 15:05:10 abrasax kernel: bttv0: registered device video0
Apr 22 15:05:10 abrasax kernel: bttv0: registered device vbi0
----
I'm using xserver-xorg-core 1:1.0.2-5 (updated yesterday), radeon
driver with dri enabled.
Please tell me which missing information I can provide or how else I
can help you.
Kind regards
Friedel
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-1-k7
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) (ignored: LC_ALL
set to de_DE.utf8)
--- End Message ---
--- Begin Message ---
On Thu, Aug 03, 2006 at 11:34:19PM +0200, Friedrich Delgado Friedrichs wrote:
> Uhm...
>
> It appears that using just ":0" instead of "localhost:0" or
> "localhost" works.
>
> However I didn't find any documentation on that behaviour.
>
> The real reason for trying this out was that I wanted to xmove a
> window through a ssh-forwarded display. Still struggling with that,
> but you can probably scratch this bugreport, as it's mostly a result
> of my confusion...
>
> Kind regards
> Friedel
ok thanks for your feedback, closing.
--
maks
--- End Message ---
