Mailing List Archive: ivtv: users

ivtvfb causes shutdown procedure to crash

Index | Next | Previous | View Threaded

baloedebruinebeer at gmail

Dec 29, 2008, 8:54 AM

Post #1 of 13 (3503 views)
Permalink

ivtvfb causes shutdown procedure to crash

I am taking advantage of the holidays to address a couple of annoyances with
my Hauppauge 350 set up, which has Ubuntu 8.10 (kernel 2.6.9-27, ivtv
version 1.4) installed. One of them is not being able to properly shutdown
when ivtvfb is loaded.

* When initiating the shutdown procedure, the screens (I use separate X
servers for my monitor and the framebuffer on the TV) go blank almost
immediately, a beep sounds from the pc speaker and then the system hangs. No
mouse cursor, numlock won't work, but there is some occasional disc
activity. Eventually, I have to press the off button. I can tell the
shutdown procedure is not completed, because mounted volumes are not
properly unmounted.

I do not know what info/output I should give to help debug this problem. I
cannot ssh into the machine when it has crashed (if that was an option to
begin with). All I know is that when I comment out ivtvfb in /etc/modules,
the computer shuts down fine.

* Another annoyance might actually be a Mythtv (v0.21) problem. When I quit
live tv, it tends to hang for 15-20 seconds (about 20 % of the time) or hang
indefinetely (about 5 % of the time). What info would be required to debug
this?

* And finally, another Mythtv problem, probably, but I might as well post it
here while I am at it: PAL teletext does not work. I get a 'page not
available' message, but that is it.

sander.sweers at gmail

Dec 29, 2008, 3:36 PM

Post #2 of 13 (3420 views)
Permalink

Re: ivtvfb causes shutdown procedure to crash [In reply to]

On Mon, Dec 29, 2008 at 17:54, Paul van Gerven
<baloedebruinebeer [at] gmail> wrote:
> I am taking advantage of the holidays to address a couple of annoyances with
> my Hauppauge 350 set up, which has Ubuntu 8.10 (kernel 2.6.9-27, ivtv
> version 1.4) installed. One of them is not being able to properly shutdown
> when ivtvfb is loaded.

This version of ivtv is very old and does is not supported anymore.
But... see below

> * When initiating the shutdown procedure, the screens (I use separate X
> servers for my monitor and the framebuffer on the TV) go blank almost
> immediately, a beep sounds from the pc speaker and then the system hangs. No
> mouse cursor, numlock won't work, but there is some occasional disc
> activity. Eventually, I have to press the off button. I can tell the
> shutdown procedure is not completed, because mounted volumes are not
> properly unmounted.

What does /var/log/Xorg.log say?

> I do not know what info/output I should give to help debug this problem. I
> cannot ssh into the machine when it has crashed (if that was an option to
> begin with). All I know is that when I comment out ivtvfb in /etc/modules,
> the computer shuts down fine.

See [1] for the trouble shooting page and if nothing turns up for you
then see [2] on how to ask for help.

> * Another annoyance might actually be a Mythtv (v0.21) problem. When I quit
> live tv, it tends to hang for 15-20 seconds (about 20 % of the time) or hang
> indefinetely (about 5 % of the time). What info would be required to debug
> this?

See previous answer.

> * And finally, another Mythtv problem, probably, but I might as well post it
> here while I am at it: PAL teletext does not work. I get a 'page not
> available' message, but that is it.

Can you test wiith other programs to read teletext? It should be on
/dev/vbi0 (if you only have 1 ivtv card).

In general it is recommended to upgrade to an ivtv version that was
merged into the mainline kernel (2.6.26 and up should be a good
starting point). I know if it aint broke dont fix it but this version
is so old and current in kernel ivtv has so many fixes and
improvements. If you do decide to upgrade make sure you make a backup
of everything so when it does not work out for you then at least you
can go back.

Greets
Sander

[1] http://ivtvdriver.org/index.php/Troubleshooting
[2] http://ivtvdriver.org/index.php/Asking_for_help

_______________________________________________
ivtv-users mailing list
ivtv-users [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-users

sander.sweers at gmail

Dec 29, 2008, 3:50 PM

Post #3 of 13 (3401 views)
Permalink

Re: ivtvfb causes shutdown procedure to crash [In reply to]

On Tue, Dec 30, 2008 at 00:36, Sander Sweers <sander.sweers [at] gmail> wrote:
> On Mon, Dec 29, 2008 at 17:54, Paul van Gerven
> <baloedebruinebeer [at] gmail> wrote:
>> I am taking advantage of the holidays to address a couple of annoyances with
>> my Hauppauge 350 set up, which has Ubuntu 8.10 (kernel 2.6.9-27, ivtv
>> version 1.4) installed. One of them is not being able to properly shutdown
>> when ivtvfb is loaded.
>
> This version of ivtv is very old and does is not supported anymore.

Whoops, ignore that... :(

Just to be sure here. Are you using a 2.6.9 kernel or a more recent
one? ivtv 1.x is the in kernel version and that did not happen untill
much.

The 2 links are still valid as refference points.

Greets
Sander

_______________________________________________
ivtv-users mailing list
ivtv-users [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-users

sander.sweers at gmail

Dec 29, 2008, 3:59 PM

Post #4 of 13 (3406 views)
Permalink

Re: ivtvfb causes shutdown procedure to crash [In reply to]

Note to self, do not send e-mails at 1 am in the morning after a 14
hour work day...

On Tue, Dec 30, 2008 at 00:50, Sander Sweers <sander.sweers [at] gmail> wrote:

> ivtv 1.x is the in kernel version and that did not happen untill much.

This should have been: ivtv 1.x is the in kernel version and that did
not happen untill much later.

Sorry for the many e-mail.

greets
Sander

_______________________________________________
ivtv-users mailing list
ivtv-users [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-users

baloedebruinebeer at gmail

Dec 30, 2008, 5:03 AM

Post #5 of 13 (3387 views)
Permalink

Re: ivtvfb causes shutdown procedure to crash [In reply to]

Oops, typo! It is indeed a recent kernel: 2.6.27-9. Sorry for the confusion,
Sander.

I did check out the Troubleshooting link before posting here, but I cannot
see anything relevant for me. I also checked the how to ask for help link,
but the little dmesg script does not output anything. Here's what I feel is
the relevant part of the dmesg output:

[ 19.036515] ivtv: Start initialization, version 1.4.0
[ 19.037286] ivtv0: Initializing card #0
[ 19.037290] ivtv0: Autodetected Hauppauge card (cx23415 based)
[ 19.037335] ivtv 0000:07:05.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
[ 19.090615] tveeprom 0-0050: Hauppauge model 48139, rev K2B7, serial#
9924044
[ 19.090618] tveeprom 0-0050: tuner model is Philips FM1216ME MK5 (idx
117, type 38)
[ 19.090620] tveeprom 0-0050: TV standards PAL(B/G) PAL(I) SECAM(L/L')
PAL(D/D1/K) (eeprom 0x74)
[ 19.090623] tveeprom 0-0050: audio processor is MSP4418 (idx 25)
[ 19.090624] tveeprom 0-0050: decoder processor is SAA7115 (idx 19)
[ 19.090627] tveeprom 0-0050: has radio, has IR receiver, has no IR
transmitter
[ 19.090629] ivtv0: Autodetected Hauppauge WinTV PVR-350
[ 19.398871] saa7115 0-0021: saa7115 found (1f7115d0e100000) @ 0x42 (ivtv
i2c driver #0)
[ 19.423649] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) ->
IRQ 22
[ 19.423677] HDA Intel 0000:00:1b.0: setting latency timer to 64
[ 19.453868] hda_codec: Unknown model for ALC882, trying auto-probe from
BIOS...
[ 19.596209] saa7127 0-0044: saa7129 found @ 0x88 (ivtv i2c driver #0)
[ 19.605966] msp3400 0-0040: MSP4418G-B3 found @ 0x80 (ivtv i2c driver #0)
[ 19.605968] msp3400 0-0040: msp3400 supports nicam and radio, mode is
autodetect and autoselect
[ 19.740163] tuner 0-0043: chip found @ 0x86 (ivtv i2c driver #0)
[ 19.754048] tda9887 0-0043: creating new instance
[ 19.754051] tda9887 0-0043: tda988[5/6/7] found
[ 19.755341] tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0)
[ 19.770596] tuner-simple 0-0061: creating new instance
[ 19.770599] tuner-simple 0-0061: type set to 38 (Philips PAL/SECAM multi
(FM1216ME MK3))
[ 19.782987] ivtv0: Registered device video0 for encoder MPG (4096 kB)
[ 19.783016] ivtv0: Registered device video32 for encoder YUV (2048 kB)
[ 19.783041] ivtv0: Registered device vbi0 for encoder VBI (1024 kB)
[ 19.783066] ivtv0: Registered device video24 for encoder PCM (320 kB)
[ 19.783091] ivtv0: Registered device radio0 for encoder radio
[ 19.783116] ivtv0: Registered device video16 for decoder MPG (1024 kB)
[ 19.783142] ivtv0: Registered device vbi8 for decoder VBI (64 kB)
[ 19.783167] ivtv0: Registered device vbi16 for decoder VOUT
[ 19.783193] ivtv0: Registered device video48 for decoder YUV (1024 kB)
[ 19.783195] ivtv0: Initialized card #0: Hauppauge WinTV PVR-350
[ 19.783221] ivtv: End initialization
[ 21.009585] loop: module loaded
[ 21.051046] lp: driver loaded but no devices found
[ 21.740171] firmware: requesting v4l-cx2341x-enc.fw
[ 21.802303] ivtv0: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
[ 21.802323] firmware: requesting v4l-cx2341x-dec.fw
[ 21.818066] ivtv0: Loaded v4l-cx2341x-dec.fw firmware (262144 bytes)
[ 22.016406] ivtv0: Encoder revision: 0x02060039
[ 22.016529] ivtv0: Decoder revision: 0x02020023
[ 22.068105] firmware: requesting v4l-cx2341x-init.mpg
[ 22.109812] ivtv0: Loaded v4l-cx2341x-init.mpg firmware (155648 bytes)
[ 22.304178] ivtvfb0: Framebuffer at 0xf5510000, mapped to 0xfa710000,
size 1665k
[ 22.379198] Console: switching to colour frame buffer device 80x30
[ 22.412114] ivtvfb0: Framebuffer registered on ivtv card id 0

Here's the Xorg.log for the framebuffer (as I said, on a separate X server).
I left out a part for mouse and keyboard.

X.Org X Server 1.5.2
Release Date: 10 October 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-19-server i686 Ubuntu
Current Operating System: Linux snotrochel 2.6.27-9-generic #1 SMP Thu Nov
20 21:57:00 UTC 2008 i686
Build Date: 24 October 2008 08:00:16AM
xorg-server 2:1.5.2-2ubuntu3 (buildd [at] rothera)
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Dec 29 16:46:09 2008
(==) Using config file: "/etc/X11/xorg.conf"
(++) ServerLayout "seat0"
(**) |-->Screen "tv1" (0)
(**) | |-->Monitor "PALTV"
(**) | |-->Device "HauppaugePVR"
(==) Automatically adding devices
(==) Automatically enabling devices
(==) No FontPath specified. Using compiled-in default.
(WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
Entry deleted from font path.
(==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType
(==) ModulePath set to "/usr/lib/xorg/modules"
(II) Cannot locate a core pointer device.
(II) Cannot locate a core keyboard device.
(II) The server relies on HAL to provide the list of input devices.
If no devices become available, reconfigure HAL or disable
AllowEmptyInput.
(II) Open ACPI successful (/var/run/acpid.socket)
(II) Loader magic: 0x81d9a40
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 4.1
X.Org XInput driver : 2.1
X.Org Server Extension : 1.1
X.Org Font Renderer : 0.6
(II) Loader running on linux
(++) using VT number 7

(--) PCI:*(0@1:0:0) nVidia Corporation G70 [GeForce 7600 GT] rev 161, Mem @
0xfa000000/0, 0xd0000000/0, 0xfb000000/0, I/O @ 0x00009f00/0, BIOS @
0x????????/131072
(--) PCI: (0@7:5:0) Internext Compression Inc iTVC15 MPEG-2 Encoder rev 1,
Mem @ 0xf4000000/0
(II) System resource ranges:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[5] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
(II) "extmod" will be loaded. This was enabled by default and also specified
in the config file.
(II) "dbe" will be loaded. This was enabled by default and also specified in
the config file.
(II) "glx" will be loaded. This was enabled by default and also specified in
the config file.
(II) "freetype" will be loaded. This was enabled by default and also
specified in the config file.
(II) "record" will be loaded by default.
(II) "dri" will be loaded by default.
(II) LoadModule: "dbe"

(II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 1.5.2, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 1.1
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "v4l"

(II) Loading /usr/lib/xorg/modules/drivers//v4l_drv.so
(II) Module v4l: vendor="X.Org Foundation"
compiled for 1.5.0, module version = 0.1.1
ABI class: X.Org Video Driver, version 4.1
(II) LoadModule: "extmod"

(II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 1.5.2, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 1.1
(II) Loading extension SHAPE
(II) Loading extension MIT-SUNDRY-NONSTANDARD
(II) Loading extension BIG-REQUESTS
(II) Loading extension SYNC
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XC-MISC
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-Misc
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension TOG-CUP
(II) Loading extension Extended-Visual-Information
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "type1"

(WW) Warning, couldn't open module type1
(II) UnloadModule: "type1"
(EE) Failed to load module "type1" (module does not exist, 0)
(II) LoadModule: "freetype"

(II) Loading /usr/lib/xorg/modules//fonts/libfreetype.so
(II) Module freetype: vendor="X.Org Foundation & the After X-TT Project"
compiled for 1.5.2, module version = 2.1.0
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.6
(II) Loading font FreeType
(II) LoadModule: "glx"

(II) Loading /usr/lib/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Server Extension
(II) NVIDIA GLX Module 173.14.12 Thu Jul 17 18:36:35 PDT 2008
(II) Loading extension GLX
(II) LoadModule: "record"

(II) Loading /usr/lib/xorg/modules/extensions//librecord.so
(II) Module record: vendor="X.Org Foundation"
compiled for 1.5.2, module version = 1.13.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 1.1
(II) Loading extension RECORD
(II) LoadModule: "dri"

(II) Loading /usr/lib/xorg/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 1.5.2, module version = 1.0.0
ABI class: X.Org Server Extension, version 1.1
(II) Loading extension XFree86-DRI
(II) LoadModule: "ivtv"

(II) Loading /usr/lib/xorg/modules/drivers//ivtv_drv.so
(II) Module ivtv: vendor="X.Org Foundation"
compiled for 1.4.99.905, module version = 1.0.1
ABI class: X.Org Video Driver, version 4.1
(II) v4l driver for Video4Linux
(II) IVTV: driver for ivtv framebuffer: PVR-350
(II) Primary Device is: PCI 01 [at] 0:00:0
(WW) Falling back to old probe method for v4l
(WW) Falling back to old probe method for ivtv
(--) Chipset PVR-350 found
(II) IVTV(0): using /dev/fb0
(II) resource ranges after probing:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[5] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
(--) IVTV(0): Framebuffer id from dev /dev/fb0 is 0
(II) IVTV(0): IVTV driver version 1.4.0
(II) IVTV(0): Using new API
(II) IVTV(0): Linked framebuffer 'dev/fb0' to yuv device '/dev/video48'
(**) IVTV(0): Depth 24, (**) framebuffer bpp 32
(==) IVTV(0): RGB weight 888
(==) IVTV(0): Default visual is TrueColor
(==) IVTV(0): Using gamma correction (1.0, 1.0, 1.0)
(II) IVTV(0): Hardware: cx23415 TV out (vidmem: 1665k)
(II) IVTV(0): Checking Modes against framebuffer device...
(II) IVTV(0): mode "720x576" ok
(II) IVTV(0): Checking Modes against monitor...
(--) IVTV(0): Virtual size is 720x576 (pitch 720)
(**) IVTV(0): Mode "720x576": 42.6 MHz (scaled from 0.0 MHz), 45.1 kHz,
75.0 Hz
(II) IVTV(0): Modeline "720x576"x0.0 42.60 720 760 832 944 576 577 580
602 -hsync -vsync (45.1 kHz)
(==) IVTV(0): DPI set to (96, 96)
(II) Loading sub module "fb"
(II) LoadModule: "fb"

(II) Loading /usr/lib/xorg/modules//libfb.so
(II) Module fb: vendor="X.Org Foundation"
compiled for 1.5.2, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(**) IVTV(0): Using "Shadow Framebuffer"
(II) Loading sub module "shadow"
(II) LoadModule: "shadow"

(II) Loading /usr/lib/xorg/modules//libshadow.so
(II) Module shadow: vendor="X.Org Foundation"
compiled for 1.5.2, module version = 1.1.0
ABI class: X.Org ANSI C Emulation, version 0.4
(--) Depth 24 pixmap format is 32 bpp
(II) do I need RAC? No, I don't.
(II) resource ranges after preInit:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[5] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
(II) IVTV(0): bitsPerPixel=32, depth=24, defaultVisual=TrueColor
mask: ff0000,ff00,ff, offset: 16,8,0
(II) IVTV(0): Screen init width 720 height 576 virtual 720 576
(==) IVTV(0): Backing store disabled
(II) IVTV(0): DPMS enabled
(II) IVTV(0): Init Video
(II) IVTV(0): Enabling Xv support for PVR350
(==) RandR enabled
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
(EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not
found)
(II) config/hal: Adding input device Macintosh mouse button emulation
(II) LoadModule: "evdev"

The stalling when stopping live TV seems to be related to this (bold text is
mine):

2008-12-30 13:21:35.716 TV: Attempting to change from WatchingLiveTV to None
2008-12-30 13:21:43.762
RingBuf(/media/mythtv/intrepid/1007_20081230132120.mpg): Waited 8.0 seconds
for data to become available...
2008-12-30 13:21:43.762 Checking to see if there's a new livetv program to
switch to..
*2008-12-30 13:21:51.763
RingBuf(/media/mythtv/intrepid/1007_20081230132120.mpg) Error: Waited 16
seconds for data, aborting.*
2008-12-30 13:21:51.867 TV: Changing from WatchingLiveTV to None
2008-12-30 13:21:51.926 DPMS Reactivated.
2008-12-30 13:31:18.689 Received a remote 'Clear Cache' request

described a long time ago:
http://www.mail-archive.com/mythtv-commits [at] mythtv/msg05500.html and
supposedly fixed. This is now probably a Mythtv problem and I'll take it to
that list (cannot google any useful info).

As for the teletext: /dev/vbi0 is there indeed, I'll get cracking on it.

Thanks,

Paul

On Tue, Dec 30, 2008 at 12:59 AM, Sander Sweers <sander.sweers [at] gmail>wrote:

> Note to self, do not send e-mails at 1 am in the morning after a 14
> hour work day...
>
> On Tue, Dec 30, 2008 at 00:50, Sander Sweers <sander.sweers [at] gmail>
> wrote:
>
> > ivtv 1.x is the in kernel version and that did not happen untill much.
>
> This should have been: ivtv 1.x is the in kernel version and that did
> not happen untill much later.
>
> Sorry for the many e-mail.
>
> greets
> Sander
>
> _______________________________________________
> ivtv-users mailing list
> ivtv-users [at] ivtvdriver
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>

sander.sweers at gmail

Dec 31, 2008, 4:12 AM

Post #6 of 13 (3371 views)
Permalink

Re: ivtvfb causes shutdown procedure to crash [In reply to]

On Tue, Dec 30, 2008 at 14:03, Paul van Gerven
<baloedebruinebeer [at] gmail> wrote:
> Oops, typo! It is indeed a recent kernel: 2.6.27-9.

Good :-)

> but the little dmesg script does not output anything.

That is because the output of ivtv changed. This needs fixing on the wiki.

> Here's what I feel is the relevant part of the dmesg output:

Indeed and it looks good.

> Here's the Xorg.log for the framebuffer (as I said, on a separate X server).
> I left out a part for mouse and keyboard.

I see nothing weird, is there no backtrace at the end of the previous log?

> The stalling when stopping live TV seems to be related to this (bold text is
> mine):

<snip>

> RingBuf(/media/mythtv/intrepid/1007_20081230132120.mpg): Waited 8.0 seconds
> for data to become available...
> 2008-12-30 13:21:43.762 Checking to see if there's a new livetv program to
> switch to..
> 2008-12-30 13:21:51.763
> RingBuf(/media/mythtv/intrepid/1007_20081230132120.mpg) Error: Waited 16
> seconds for data, aborting.

When you see these is there anything in /var/log/messages at the same
time for ivtv or ivtvfb?

To rule out ivtv can you do some tests *without* having mythtv
running? When you do the tests please keep an eye on .var.log.messages
for errors from ivtv.

To test normal capuring please run "cat /dev/video0 > test.mpg" and
check if it keeps working and that the file is playing properly. You
can also redirect it to /dev/null if you do not have a lot of space
but preferably not.

To test the tv-out you can run "dd if=/dev/video of=/dev/video16 bs=64k".

If these 2 tests work without issue it likely is not ivtv that is
causing issues. It might be ivtvfb but if it is then the logs should
have something of an error (backtrace maybe?).

Greets
Sander

<---- ivtv output ---->
> [ 19.036515] ivtv: Start initialization, version 1.4.0
> [ 19.037286] ivtv0: Initializing card #0
> [ 19.037290] ivtv0: Autodetected Hauppauge card (cx23415 based)
> [ 19.037335] ivtv 0000:07:05.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
> [ 19.090615] tveeprom 0-0050: Hauppauge model 48139, rev K2B7, serial#
> 9924044
> [ 19.090618] tveeprom 0-0050: tuner model is Philips FM1216ME MK5 (idx
> 117, type 38)
> [ 19.090620] tveeprom 0-0050: TV standards PAL(B/G) PAL(I) SECAM(L/L')
> PAL(D/D1/K) (eeprom 0x74)
> [ 19.090623] tveeprom 0-0050: audio processor is MSP4418 (idx 25)
> [ 19.090624] tveeprom 0-0050: decoder processor is SAA7115 (idx 19)
> [ 19.090627] tveeprom 0-0050: has radio, has IR receiver, has no IR
> transmitter
> [ 19.090629] ivtv0: Autodetected Hauppauge WinTV PVR-350
> [ 19.398871] saa7115 0-0021: saa7115 found (1f7115d0e100000) @ 0x42 (ivtv
> i2c driver #0)
> [ 19.596209] saa7127 0-0044: saa7129 found @ 0x88 (ivtv i2c driver #0)
> [ 19.605966] msp3400 0-0040: MSP4418G-B3 found @ 0x80 (ivtv i2c driver #0)
> [ 19.605968] msp3400 0-0040: msp3400 supports nicam and radio, mode is
> autodetect and autoselect
> [ 19.740163] tuner 0-0043: chip found @ 0x86 (ivtv i2c driver #0)
> [ 19.754048] tda9887 0-0043: creating new instance
> [ 19.754051] tda9887 0-0043: tda988[5/6/7] found
> [ 19.755341] tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0)
> [ 19.770596] tuner-simple 0-0061: creating new instance
> [ 19.770599] tuner-simple 0-0061: type set to 38 (Philips PAL/SECAM multi
> (FM1216ME MK3))
> [ 19.782987] ivtv0: Registered device video0 for encoder MPG (4096 kB)
> [ 19.783016] ivtv0: Registered device video32 for encoder YUV (2048 kB)
> [ 19.783041] ivtv0: Registered device vbi0 for encoder VBI (1024 kB)
> [ 19.783066] ivtv0: Registered device video24 for encoder PCM (320 kB)
> [ 19.783091] ivtv0: Registered device radio0 for encoder radio
> [ 19.783116] ivtv0: Registered device video16 for decoder MPG (1024 kB)
> [ 19.783142] ivtv0: Registered device vbi8 for decoder VBI (64 kB)
> [ 19.783167] ivtv0: Registered device vbi16 for decoder VOUT
> [ 19.783193] ivtv0: Registered device video48 for decoder YUV (1024 kB)
> [ 19.783195] ivtv0: Initialized card #0: Hauppauge WinTV PVR-350
> [ 19.783221] ivtv: End initialization
> [ 21.009585] loop: module loaded
> [ 21.740171] firmware: requesting v4l-cx2341x-enc.fw
> [ 21.802303] ivtv0: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
> [ 21.802323] firmware: requesting v4l-cx2341x-dec.fw
> [ 21.818066] ivtv0: Loaded v4l-cx2341x-dec.fw firmware (262144 bytes)
> [ 22.016406] ivtv0: Encoder revision: 0x02060039
> [ 22.016529] ivtv0: Decoder revision: 0x02020023
> [ 22.068105] firmware: requesting v4l-cx2341x-init.mpg
> [ 22.109812] ivtv0: Loaded v4l-cx2341x-init.mpg firmware (155648 bytes)
> [ 22.304178] ivtvfb0: Framebuffer at 0xf5510000, mapped to 0xfa710000,
> size 1665k
> [ 22.379198] Console: switching to colour frame buffer device 80x30
> [ 22.412114] ivtvfb0: Framebuffer registered on ivtv card id 0

_______________________________________________
ivtv-users mailing list
ivtv-users [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-users

baloedebruinebeer at gmail

Jan 1, 2009, 9:51 AM

Post #7 of 13 (3362 views)
Permalink

Re: ivtvfb causes shutdown procedure to crash [In reply to]

Alright, I got some more data:

1) The halt-on-switching-off-liveTV: there are no entries in
/var/log/messages at or around the time the frontend reports that RingBuf
error. Furthermore, I got no errors when testing normal capture or the
tv-out. So this seems a Mythtv issue.

2) The teletext: I used Alevt to test and it works fine. Another Mythtv
issue, it seems.

3) That leaves the inproper shutdown, which is certainly an issue with the
ivtvfb module. Any ideas to debug this?

Thanks so far,

Paul

On Wed, Dec 31, 2008 at 1:12 PM, Sander Sweers <sander.sweers [at] gmail>wrote:

> On Tue, Dec 30, 2008 at 14:03, Paul van Gerven
> <baloedebruinebeer [at] gmail> wrote:
> > Oops, typo! It is indeed a recent kernel: 2.6.27-9.
>
> Good :-)
>
> > but the little dmesg script does not output anything.
>
> That is because the output of ivtv changed. This needs fixing on the wiki.
>
> > Here's what I feel is the relevant part of the dmesg output:
>
> Indeed and it looks good.
>
> > Here's the Xorg.log for the framebuffer (as I said, on a separate X
> server).
> > I left out a part for mouse and keyboard.
>
> I see nothing weird, is there no backtrace at the end of the previous log?
>
> > The stalling when stopping live TV seems to be related to this (bold text
> is
> > mine):
>
> <snip>
>
> > RingBuf(/media/mythtv/intrepid/1007_20081230132120.mpg): Waited 8.0
> seconds
> > for data to become available...
> > 2008-12-30 13:21:43.762 Checking to see if there's a new livetv program
> to
> > switch to..
> > 2008-12-30 13:21:51.763
> > RingBuf(/media/mythtv/intrepid/1007_20081230132120.mpg) Error: Waited 16
> > seconds for data, aborting.
>
> When you see these is there anything in /var/log/messages at the same
> time for ivtv or ivtvfb?
>
>
> To rule out ivtv can you do some tests *without* having mythtv
> running? When you do the tests please keep an eye on .var.log.messages
> for errors from ivtv.
>
> To test normal capuring please run "cat /dev/video0 > test.mpg" and
> check if it keeps working and that the file is playing properly. You
> can also redirect it to /dev/null if you do not have a lot of space
> but preferably not.
>
> To test the tv-out you can run "dd if=/dev/video of=/dev/video16 bs=64k".
>
> If these 2 tests work without issue it likely is not ivtv that is
> causing issues. It might be ivtvfb but if it is then the logs should
> have something of an error (backtrace maybe?).
>
> Greets
> Sander
>
> <---- ivtv output ---->
> > [ 19.036515] ivtv: Start initialization, version 1.4.0
> > [ 19.037286] ivtv0: Initializing card #0
> > [ 19.037290] ivtv0: Autodetected Hauppauge card (cx23415 based)
> > [ 19.037335] ivtv 0000:07:05.0: PCI INT A -> GSI 21 (level, low) -> IRQ
> 21
> > [ 19.090615] tveeprom 0-0050: Hauppauge model 48139, rev K2B7, serial#
> > 9924044
> > [ 19.090618] tveeprom 0-0050: tuner model is Philips FM1216ME MK5 (idx
> > 117, type 38)
> > [ 19.090620] tveeprom 0-0050: TV standards PAL(B/G) PAL(I) SECAM(L/L')
> > PAL(D/D1/K) (eeprom 0x74)
> > [ 19.090623] tveeprom 0-0050: audio processor is MSP4418 (idx 25)
> > [ 19.090624] tveeprom 0-0050: decoder processor is SAA7115 (idx 19)
> > [ 19.090627] tveeprom 0-0050: has radio, has IR receiver, has no IR
> > transmitter
> > [ 19.090629] ivtv0: Autodetected Hauppauge WinTV PVR-350
> > [ 19.398871] saa7115 0-0021: saa7115 found (1f7115d0e100000) @ 0x42
> (ivtv
> > i2c driver #0)
> > [ 19.596209] saa7127 0-0044: saa7129 found @ 0x88 (ivtv i2c driver #0)
> > [ 19.605966] msp3400 0-0040: MSP4418G-B3 found @ 0x80 (ivtv i2c driver
> #0)
> > [ 19.605968] msp3400 0-0040: msp3400 supports nicam and radio, mode is
> > autodetect and autoselect
> > [ 19.740163] tuner 0-0043: chip found @ 0x86 (ivtv i2c driver #0)
> > [ 19.754048] tda9887 0-0043: creating new instance
> > [ 19.754051] tda9887 0-0043: tda988[5/6/7] found
> > [ 19.755341] tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0)
> > [ 19.770596] tuner-simple 0-0061: creating new instance
> > [ 19.770599] tuner-simple 0-0061: type set to 38 (Philips PAL/SECAM
> multi
> > (FM1216ME MK3))
> > [ 19.782987] ivtv0: Registered device video0 for encoder MPG (4096 kB)
> > [ 19.783016] ivtv0: Registered device video32 for encoder YUV (2048 kB)
> > [ 19.783041] ivtv0: Registered device vbi0 for encoder VBI (1024 kB)
> > [ 19.783066] ivtv0: Registered device video24 for encoder PCM (320 kB)
> > [ 19.783091] ivtv0: Registered device radio0 for encoder radio
> > [ 19.783116] ivtv0: Registered device video16 for decoder MPG (1024 kB)
> > [ 19.783142] ivtv0: Registered device vbi8 for decoder VBI (64 kB)
> > [ 19.783167] ivtv0: Registered device vbi16 for decoder VOUT
> > [ 19.783193] ivtv0: Registered device video48 for decoder YUV (1024 kB)
> > [ 19.783195] ivtv0: Initialized card #0: Hauppauge WinTV PVR-350
> > [ 19.783221] ivtv: End initialization
> > [ 21.009585] loop: module loaded
> > [ 21.740171] firmware: requesting v4l-cx2341x-enc.fw
> > [ 21.802303] ivtv0: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
> > [ 21.802323] firmware: requesting v4l-cx2341x-dec.fw
> > [ 21.818066] ivtv0: Loaded v4l-cx2341x-dec.fw firmware (262144 bytes)
> > [ 22.016406] ivtv0: Encoder revision: 0x02060039
> > [ 22.016529] ivtv0: Decoder revision: 0x02020023
> > [ 22.068105] firmware: requesting v4l-cx2341x-init.mpg
> > [ 22.109812] ivtv0: Loaded v4l-cx2341x-init.mpg firmware (155648 bytes)
> > [ 22.304178] ivtvfb0: Framebuffer at 0xf5510000, mapped to 0xfa710000,
> > size 1665k
> > [ 22.379198] Console: switching to colour frame buffer device 80x30
> > [ 22.412114] ivtvfb0: Framebuffer registered on ivtv card id 0
>
> _______________________________________________
> ivtv-users mailing list
> ivtv-users [at] ivtvdriver
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>

sander.sweers at gmail

Jan 2, 2009, 2:34 AM

Post #8 of 13 (3345 views)
Permalink

Re: ivtvfb causes shutdown procedure to crash [In reply to]

Please do not top post. Thanks

On Thu, Jan 1, 2009 at 18:51, Paul van Gerven
<baloedebruinebeer [at] gmail> wrote:
> Alright, I got some more data:
>
> 1) The halt-on-switching-off-liveTV: there are no entries in
> /var/log/messages at or around the time the frontend reports that RingBuf
> error. Furthermore, I got no errors when testing normal capture or the
> tv-out. So this seems a Mythtv issue.
>
> 2) The teletext: I used Alevt to test and it works fine. Another Mythtv
> issue, it seems.

We ruled out ivtv, good for us but not for you :-(

> 3) That leaves the inproper shutdown, which is certainly an issue with the
> ivtvfb module. Any ideas to debug this?

Can you try to unload the ivtvfb module via "modprobe -r ivtvfb" and check:
if this produces anything in the logs?
does it also lock the machibe up, imediatly or again at shutdown?

If you have closed source modules loaded could you disale them and see
if it still locks up?

It there any backtrace or error message just before it locks in the kernel log?

Swapping the card to a different slot and check if the slot/cards is dusty.

Greets
Sander

_______________________________________________
ivtv-users mailing list
ivtv-users [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-users

baloedebruinebeer at gmail

Jan 4, 2009, 3:31 AM

Post #9 of 13 (3292 views)
Permalink

Re: ivtvfb causes shutdown procedure to crash [In reply to]

On Fri, Jan 2, 2009 at 11:34 AM, Sander Sweers <sander.sweers [at] gmail>wrote:

> Please do not top post. Thanks
>

Apologies :)

>
> On Thu, Jan 1, 2009 at 18:51, Paul van Gerven
> <baloedebruinebeer [at] gmail> wrote:
> > Alright, I got some more data:
> >
> > 1) The halt-on-switching-off-liveTV: there are no entries in
> > /var/log/messages at or around the time the frontend reports that RingBuf
> > error. Furthermore, I got no errors when testing normal capture or the
> > tv-out. So this seems a Mythtv issue.
> >
> > 2) The teletext: I used Alevt to test and it works fine. Another Mythtv
> > issue, it seems.
>
> We ruled out ivtv, good for us but not for you :-(
>

I consider it progress, as I can take it to the proper forum now :)

> > 3) That leaves the inproper shutdown, which is certainly an issue with
> the
> > ivtvfb module. Any ideas to debug this?
>
> Can you try to unload the ivtvfb module via "modprobe -r ivtvfb" and check:
> if this produces anything in the logs?
> does it also lock the machibe up, imediatly or again at shutdown?
>

This just results in a message that the module is still in use. Shouldn't I
stop the framebuffer first? (If so: how?)

>
> If you have closed source modules loaded could you disale them and see
> if it still locks up?
>

I have Nvidia drivers, but as I mentioned they are loaded on a separate
X-server. Is it still worthwhile to try this?

>
> It there any backtrace or error message just before it locks in the kernel
> log?
>

Nope :(

>
> Swapping the card to a different slot and check if the slot/cards is dusty.
>

Swapping is not an option, unfortunately: it just doesn't fit in any other
slot. I did take it out for a bit of a clean, but that doesn't seems to make
a difference.

>
> Greets
> Sander
>
>
Thanks,

Paul

> _______________________________________________
> ivtv-users mailing list
> ivtv-users [at] ivtvdriver
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>

sander.sweers at gmail

Jan 4, 2009, 5:40 AM

Post #10 of 13 (3305 views)
Permalink

Re: ivtvfb causes shutdown procedure to crash [In reply to]

On Sun, Jan 4, 2009 at 12:31, Paul van Gerven
<baloedebruinebeer [at] gmail> wrote:
>> > 3) That leaves the improper shutdown, which is certainly an issue with
>> > the
>> > ivtvfb module. Any ideas to debug this?
>>
>> Can you try to unload the ivtvfb module via "modprobe -r ivtvfb" and
>> check:
>> if this produces anything in the logs?
>> does it also lock the machine up, immediately or again at shutdown?
>
> This just results in a message that the module is still in use. Shouldn't I
> stop the framebuffer first? (If so: how?)

Yes, any program using the framebuffer should be stopped.

>> If you have closed source modules loaded could you disable them and see
>> if it still locks up?
>
> I have Nvidia drivers, but as I mentioned they are loaded on a separate
> X-server. Is it still worthwhile to try this?

Maybe, the nvidia driver is a black box and there is no way to tell
what is going on. You can switch to the nv driver when testing. In
xorg.conf in de device section change nvidia to nv.

>> It there any backtrace or error message just before it locks in the kernel
>> log?
>
> Nope :(

Maybe there is one after unloading the ivtvfb module.

Greets
Sander

_______________________________________________
ivtv-users mailing list
ivtv-users [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-users

baloedebruinebeer at gmail

Jan 11, 2009, 12:39 AM

Post #11 of 13 (3165 views)
Permalink

Re: ivtvfb causes shutdown procedure to crash [In reply to]

On Sun, Jan 4, 2009 at 2:40 PM, Sander Sweers <sander.sweers [at] gmail>wrote:

> On Sun, Jan 4, 2009 at 12:31, Paul van Gerven
> <baloedebruinebeer [at] gmail> wrote:
> >> > 3) That leaves the improper shutdown, which is certainly an issue with
> >> > the
> >> > ivtvfb module. Any ideas to debug this?
> >>
> >> Can you try to unload the ivtvfb module via "modprobe -r ivtvfb" and
> >> check:
> >> if this produces anything in the logs?
> >> does it also lock the machine up, immediately or again at shutdown?
> >
> > This just results in a message that the module is still in use. Shouldn't
> I
> > stop the framebuffer first? (If so: how?)
>
> Yes, any program using the framebuffer should be stopped.
>

I took me quite long to get around to it (holidays are over), but I created
a xorg.conf that doesn't start a framebuffer at all. Strangely, when I issue
the modprobe command, it still says it is in use. Perhaps that's the fatal
error when I try to shutdown.

>
> >> If you have closed source modules loaded could you disable them and see
> >> if it still locks up?
> >
> > I have Nvidia drivers, but as I mentioned they are loaded on a separate
> > X-server. Is it still worthwhile to try this?
>
> Maybe, the nvidia driver is a black box and there is no way to tell
> what is going on. You can switch to the nv driver when testing. In
> xorg.conf in de device section change nvidia to nv.
>

Done. The xorg.conf I mentioned used nv.

>
> >> It there any backtrace or error message just before it locks in the
> kernel
> >> log?
> >
> > Nope :(
>
> Maybe there is one after unloading the ivtvfb module.
>

I still cannot see anything interesting in /var/log/messages.

>
> Greets
> Sander
>
> _______________________________________________
> ivtv-users mailing list
> ivtv-users [at] ivtvdriver
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>

sander.sweers at gmail

Jan 11, 2009, 2:21 PM

Post #12 of 13 (3193 views)
Permalink

Re: ivtvfb causes shutdown procedure to crash [In reply to]

On Sun, Jan 11, 2009 at 09:39, Paul van Gerven
<baloedebruinebeer [at] gmail> wrote:
>> Yes, any program using the framebuffer should be stopped.
>
> I took me quite long to get around to it (holidays are over), but I created
> a xorg.conf that doesn't start a framebuffer at all. Strangely, when I issue
> the modprobe command, it still says it is in use. Perhaps that's the fatal
> error when I try to shutdown.

You can check which program is still using the device lsof
/dev/ivtvfb0. It could be the cause.

> Done. The xorg.conf I mentioned used nv.

Is the kernel module still loading? I assume you get the same behaviour..

>> >> It there any backtrace or error message just before it locks in the
>> >> kernel
>> >> log?
>> >
>> > Nope :(
>>
>> Maybe there is one after unloading the ivtvfb module.
>
> I still cannot see anything interesting in /var/log/messages.

And without it it is very hard to get any clue what is going on :-(

Maybe Ian or Hans have any ideas..

Greets
Sander

_______________________________________________
ivtv-users mailing list
ivtv-users [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-users

baloedebruinebeer at gmail

Jan 13, 2009, 11:29 AM

Post #13 of 13 (3101 views)
Permalink

Re: ivtvfb causes shutdown procedure to crash [In reply to]

On Sun, Jan 11, 2009 at 11:21 PM, Sander Sweers <sander.sweers [at] gmail>wrote:

> On Sun, Jan 11, 2009 at 09:39, Paul van Gerven
> <baloedebruinebeer [at] gmail> wrote:
> >> Yes, any program using the framebuffer should be stopped.
> >
> > I took me quite long to get around to it (holidays are over), but I
> created
> > a xorg.conf that doesn't start a framebuffer at all. Strangely, when I
> issue
> > the modprobe command, it still says it is in use. Perhaps that's the
> fatal
> > error when I try to shutdown.
>
> You can check which program is still using the device lsof
> /dev/ivtvfb0. It could be the cause.
>

Well, there is no /dev/ivtvfb0, but there is a /dev/fb0.

lsof /dev/fb0 doesn't give a result.
sudo lsof /dev/fb0 gives:
lsof: WARNING: can't stat() fuse.gvfs-fuse-daemon file system
/home/multimedia/.gvfs
Output information may be incomplete.

> > Done. The xorg.conf I mentioned used nv.
>
> Is the kernel module still loading? I assume you get the same behaviour..
>

Yes, same behavior when shutting down. And yes, the kernel module is still
loading. I could get it out, I suppose.

>
> >> >> It there any backtrace or error message just before it locks in the
> >> >> kernel
> >> >> log?
> >> >
> >> > Nope :(
> >>
> >> Maybe there is one after unloading the ivtvfb module.
> >
> > I still cannot see anything interesting in /var/log/messages.
>
> And without it it is very hard to get any clue what is going on :-(
>
> Maybe Ian or Hans have any ideas..
>
> Greets
> Sander
>
> _______________________________________________
> ivtv-users mailing list
> ivtv-users [at] ivtvdriver
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads