> Sure, I do not have multiple processors though. I mistakenly chose SMP
> when setting up my kernel at some point. Will it still be helpful for
> me to recompile with SMP? If so I don't mind.
Yes, please. I'd like to know if the Oops returns when running with that
kernel.
Thanks,
Hans
>
> On 1/13/06, Hans Verkuil <[EMAIL PROTECTED]> wrote:
>> Good news. But now I want to know whether the oops returns if you try
>> the SMP kernel again. If so, then there's a SMP bug somewhere. Can you
>> test this?
>>
>> Thanks,
>>
>> Hans
>>
>> On Friday 13 January 2006 01:41, XeNoS wrote:
>> > Hello all,
>> >
>> > Well, I removed SMP support. And installed the latest svn (from
>> > around 7:00pm EST) and now it is detecting both 150's. A 'cat
>> > /dev/video0 > test.mpg' works. Looks like I'm good to go, now I need
>> > to get MyTV back in working order and I'll be set. Thank you for the
>> > support.
>> >
>> > Conor
>> >
>> > On 1/12/06, XeNoS <[EMAIL PROTECTED]> wrote:
>> > > Thank you for your quick responce. In the future I'll post to the
>> > > dev list any kernel oops'. When I get home I will recompile my
>> > > kernel without SMP, and install the 0.4.2 driver.
>> > >
>> > > I'll let you know how it turns out. Unfortunatly that's a good 4
>> > > hours off from now. :(
>> > >
>> > > Thank you,
>> > >
>> > > Conor
>> > >
>> > > On 1/12/06, Hans Verkuil <[EMAIL PROTECTED]> wrote:
>> > > > Odd. But before I dig into this you'd better upgrade to the
>> > > > upcoming 0.4.2 driver in the subversion repository (see
>> > > > www.ivtvdriver.org) as I committed support for your Samsung tuner
>> > > > just 30 minutes ago! It's not going to work with 0.4.1 anyway for
>> > > > that reason.
>> > > >
>> > > > See also my announcement in the ivtv-devel list. If you still get
>> > > > a kernel oops, then please post to the ivtv-devel list and I'll
>> > > > take it from there. Also, you have an SMP kernel: do you actually
>> > > > have two processors (or dual core)? Can you switch (temporarily)
>> > > > to an UP kernel and see if the oops goes away? This in case that
>> > > > it is a race condition.
>> > > >
>> > > > Hans
>> > > >
>> > > > On Thursday 12 January 2006 19:30, XeNoS wrote:
>> > > > > Hello,
>> > > > > I just bought a PVR-500 to replace a PVR-250 that crapped out
>> > > > > on me. I was having IRQ conflicts with my nForce2 boards built
>> > > > > in video using the 2.6.14-r1 Gentoo Sources. This resulted in a
>> > > > > "nobody cares" message. So I upgraded the the 2.6.15 Gentoo
>> > > > > Sources and recompiled and installed the nvidia and ivtv
>> > > > > drivers. Now I don't have the conflict problem, and it doesn't
>> > > > > lock up my system. But I do get a kernel oops when trying to
>> > > > > modprobe the ivtv driver.
>> > > > >
>> > > > > My system is a Shuttle SNG41B nForce2 based system with 512MB
>> > > > > ram, built in network, sound, video, etc. Running Gentoo kernel
>> > > > > 2.6.15(Gentoo Srouces), nVidia 1.0.8178 drivers. And custom
>> > > > > compiled ivtv-4.1.0 drivers (custom meaning not emerged, just
>> > > > > tar xvzf <src_file>, cd <sourcedir>, make, make install,
>> > > > > nothing crazy) Here is the oops error:
>> > > > >
>> > > > >
>> > > > > Linux video capture interface: v1.00
>> > > > > ivtv: ==================== START INIT IVTV ====================
>> > > > > ivtv: version 0.4.1 (tagged release) loading
>> > > > > ivtv: Linux version: 2.6.15-gentoo SMP preempt K7 gcc-3.3
>> > > > > ivtv: In case of problems please include the debug info between
>> > > > > ivtv: the START INIT IVTV and END INIT IVTV lines, along with
>> > > > > ivtv: any module options, when mailing the ivtv-users
>> > > > > mailinglist. ivtv0: Autodetected WinTV PVR 150 card (cx23416
>> > > > > based) ACPI: PCI Interrupt Link [APC3] enabled at IRQ 18
>> > > > > ACPI: PCI Interrupt 0000:02:08.0[A] -> Link [APC3] -> GSI 18
>> > > > > (level, high) -> IRQ 20
>> > > > > ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
>> > > > > tveeprom: Second (radio) tuner idx 101
>> > > > > tveeprom: ivtv version
>> > > > > tveeprom: Hauppauge: model = 23552, rev = D487, serial# =
>> > > > > 8742990 tveeprom: tuner = Samsung TCPN 2121P30A (idx = 87, type
>> > > > > = 4) tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 =
>> > > > > 0x00001000) tveeprom: audio processor = CX25843 (type = 25)
>> > > > > tveeprom: decoder processor = CX25843 (type = 1e)
>> > > > > ivtv0: i2c attach to card #0 ok [client=, addr=50] Unable to
>> > > > > handle kernel NULL pointer dereference at virtual address
>> > > > > 00000004
>> > > > > printing eip:
>> > > > > de87b799
>> > > > > *pde = 00000000
>> > > > > Oops: 0000 [#1]
>> > > > > PREEMPT SMP
>> > > > > Modules linked in: tveeprom ivtv firmware_class i2c_algo_bit
>> > > > > i2c_core videodev nvidia nvidia_agp agpgart
>> > > > > CPU: 0
>> > > > > EIP: 0060:[<de87b799>] Tainted: P VLI
>> > > > > EFLAGS: 00010246 ( 2.6.15-gentoo)
>> > > > > EIP is at tveeprom_command+0x19/0x40 [tveeprom]
>> > > > > eax: 00000000 ebx: d96d9600 ecx: d70f9e2c edx: 00000000
>> > > > > esi: 00000000 edi: d4da0000 ebp: 00000050 esp: d70f9de8
>> > > > > ds: 007b es: 007b ss: 0068
>> > > > > Process modprobe (pid: 7683, threadinfo=d70f8000 task=dd79ca30)
>> > > > > Stack: de9d2043 d96d9600 00000000 d70f9e2c d4da0000 d4da0000
>> > > > > 00800000 de9e4db4
>> > > > > de9d21ab d4da0000 00000050 00000000 d70f9e2c de9cd6ec d4da0000
>> > > > > 00000000 d70f9e2c d4da1c40 de9d228f d4da19b0 d4da0000 00000001
>> > > > > d4da0000 00000001
>> > > > > Call Trace:
>> > > > > [<de9d2043>] ivtv_call_i2c_client+0xc6/0x140 [ivtv]
>> > > > > [<de9d21ab>] ivtv_hauppauge+0x13/0x17 [ivtv]
>> > > > > [<de9cd6ec>] ivtv_read_eeprom+0x18/0x2ef [ivtv]
>> > > > > [<de9d228f>] init_ivtv_i2c+0xe0/0xe8 [ivtv]
>> > > > > [<de9ce9b5>] ivtv_probe+0x3bf/0xc4f [ivtv]
>> > > > > [<c03d15ae>] preempt_schedule+0x3e/0x54
>> > > > > [<c0125867>] call_usermodehelper_keys+0xc9/0xd6
>> > > > > [<c012575a>] __call_usermodehelper+0x0/0x44
>> > > > > [<c025954f>] pci_call_probe+0xf/0x12
>> > > > > [<c0259585>] __pci_device_probe+0x33/0x47
>> > > > > [<c02595b8>] pci_device_probe+0x1f/0x34
>> > > > > [<c02bbc73>] driver_probe_device+0x3a/0x84
>> > > > > [<c02bbd1f>] __driver_attach+0x0/0x38
>> > > > > [<c02bbd44>] __driver_attach+0x25/0x38
>> > > > > [<c02bb4c0>] bus_for_each_dev+0x47/0x6d
>> > > > > [<c025174f>] kobject_add+0x7a/0x99
>> > > > > [<c02bbd6b>] driver_attach+0x14/0x18
>> > > > > [<c02bbd1f>] __driver_attach+0x0/0x38
>> > > > > [<c02bb89e>] bus_add_driver+0x54/0x99
>> > > > > [<c02bc0bb>] driver_register+0x42/0x45
>> > > > > [<c02597a9>] __pci_register_driver+0x88/0x96
>> > > > > [<de9cf6f1>] module_start+0xbc/0xe2 [ivtv]
>> > > > > [<c012f3ef>] sys_init_module+0xc8/0x1d9
>> > > > > [<c01028a9>] syscall_call+0x7/0xb
>> > > > > Code: e9 39 ce 89 e1 8d b6 00 00 00 00 8d bc 27 00 00 00 00 8b
>> > > > > 44 24 04 8b 4c 24 0c 83 c0 14 8b 90 f0 00 00 00 8b 44 24 08 85
>> > > > > c0 75 1f <8b> 42
>> > > > > 04 89 01 8b 42 08 89 41 04 8b 42 1c 89 41 08 8b 42 20 89
>> > > > >
>> > > > >
>> > > > > Any help would be much appreciated. I have been without PVR for
>> > > > > over a month now, imagine my anger when I got errors trying to
>> > > > > fire up my new toy. :(
>> > > > >
>> > > > >
>> > > > > --
>> > > > > XeNoS
>> > > > >
>> > > > > _______________________________________________
>> > > > > ivtv-users mailing list
>> > > > > [email protected]
>> > > > > http://ivtvdriver.org/mailman/listinfo/ivtv-users
>> > > >
>> > > > _______________________________________________
>> > > > ivtv-users mailing list
>> > > > [email protected]
>> > > > http://ivtvdriver.org/mailman/listinfo/ivtv-users
>> > >
>> > > --
>> > > XeNoS
>> >
>> > --
>> > XeNoS
>> >
>> > _______________________________________________
>> > ivtv-users mailing list
>> > [email protected]
>> > http://ivtvdriver.org/mailman/listinfo/ivtv-users
>>
>> _______________________________________________
>> ivtv-users mailing list
>> [email protected]
>> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>>
>
>
> --
> XeNoS
>
> _______________________________________________
> ivtv-users mailing list
> [email protected]
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>
_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users
