#160 xawtv crashes w/ DRI enabled

closed-later
nobody
3
2002-06-13
2000-07-26
Anonymous
No

When using the Rage 128 DRI driver with CVS XFree86 4.0.1, and kernel 2.4.0-test5-pre3, running xawtv 3.17 locks the system hard immediately - sysrq keys don't have any effect. Disabling GLX/DRI lets xawtv run normally.

Discussion

1 2 > >> (Page 1 of 2)
  • Rik Faith

    Rik Faith - 2000-08-12
    • assigned_to: nobody --> gareth
     
  • Gareth Hughes

    Gareth Hughes - 2000-08-19
    • milestone: 100100 --> System Hang/Kernel Oops/Panic
    • priority: 5 --> 3
    • status: open --> open-later
     
  • Gareth Hughes

    Gareth Hughes - 2000-08-19

    Will have to get xawtv installed and working. Assuming this will need a TV tuner card and can't be faked.

    -- Gareth

     
  • Gareth Hughes

    Gareth Hughes - 2000-08-19
    • priority: 3 --> 1
     
  • Gareth Hughes

    Gareth Hughes - 2000-08-19
    • priority: 1 --> 3
     
  • Ari Pollak

    Ari Pollak - 2000-08-23

    I can do some testing if you need me to, if you can't get to a machine with xawtv...

     
  • Gareth Hughes

    Gareth Hughes - 2000-08-23

    Can you try the ati-4-1-1-branch code out? Thanks.

     
  • Ari Pollak

    Ari Pollak - 2000-08-26

    Are the DRM drivers in kernel 2.4.0-test7 the same as in the current DRI CVS tree?

     
  • Gareth Hughes

    Gareth Hughes - 2000-08-26

    No, actually. The ati-4-1-1-branch doesn't have the SIGSTOP fix Rik Faith did last week - I'm going to merge that in today. I've been using 2.4.0-test7-pre4 up until now.

     
  • Nobody/Anonymous

    I noticed there were a lot of updates in 2.4.0-test8-pre2, do you know if these would happen to include any fixes?

     
  • Gareth Hughes

    Gareth Hughes - 2000-09-03

    If you mean DRI/DRM fixes, I don't think so. AFAIK, the only DRM update was the SIGSTOP fix by Rik Faith.

     
  • Nobody/Anonymous

    Has any progress been made on this bug? I will be switching to a Voodoo3 3000 this week, so I'm assuming I probably won't see this bug as it is ATI-specific.. If I do see this bug with a 3dfx card, it might be a TV-card specific problem, and I am also planning on getting a new TV card sometime this week.

     
  • Nobody/Anonymous

    Has any progress been made on this bug? I will be switching to a Voodoo3 3000 this week, so I'm assuming I probably won't see this bug as it is ATI-specific.. If I do see this bug with a 3dfx card, it might be a TV-card specific problem, and I am also planning on getting a new TV card sometime this week.

     
  • Alex Diaz

    Alex Diaz - 2000-11-03

    I have EXACTLY the same problem. I'm using an ATI Rage 128 card with an Avermedia Tv Capture98. I cannot tell where the problem is but the system lockup is complete! There seems to be something wrong between DRI and the ATI card.
    Any ideas? I'm using RH7.0 and kernel 2.4.0-test9.

     
  • Ari Pollak

    Ari Pollak - 2000-12-06

    Also a similar bug, but not exactly the same. When using a Voodoo 3 3000, the tdfx driver, the 'v4l' driver for XF 4.0.1, and running xawtv with Xv enabled causes the server to freeze. However, it's not a complete lockup - I can still telnet in from another computer on the network and reboot. This only happens when using the Xv extension, not regular xawtv w/ overlay.

     
  • Nathan Hand

    Nathan Hand - 2001-01-07

    This only happens if you have the DRI and V4L extensions loaded. If you disable the V4L extension then xawtv works (even with the Xv extension). I've confirmed this with dri-trunk and tdfx-3-0-0-branch as of today. 3D works in either case.

    For now please try disabling the V4L extension (comment it out of XF86Config).

     
  • Ari Pollak

    Ari Pollak - 2001-01-27

    Well obviously it's only with v4l/Xv enabled.. However it only happens with that & direct rendering enabled, so I'm assuming the problem is related to DRI.

     
  • Ari Pollak

    Ari Pollak - 2001-01-27

    Well obviously it's only with v4l/Xv enabled.. However it only happens with that & direct rendering enabled, so I'm assuming the problem is related to DRI.

     
  • Ari Pollak

    Ari Pollak - 2001-01-27

    Well obviously it's only with v4l/Xv enabled.. However it only happens with that & direct rendering enabled, so I'm assuming the problem is related to DRI.

     
  • Nobody/Anonymous

    Logged In: NO

    Is this bug ever going to be fixed????????

     
  • Gareth Hughes

    Gareth Hughes - 2001-03-05

    Logged In: YES
    user_id=4972

    As I said originally, I don't have a TV tuner card.
    Therefore, I can't work on this. Similarly, if there are
    people who really *do* want to fix this (ie. you), then
    those people can feel free to work on it themselves. This
    is an open-source project after all, isn't it?

     
  • Nobody/Anonymous

    Logged In: NO

    I have the same problem, ATI Rage 128 Pro, using RH7 XFRee86
    4.0.2, Kernel 2.4.1 and xawtv 3.17.
    I get the same problem as soon as anything tries to do DRI
    and DGA at the same time (xawtv and vmware) I am currently
    compiling the latest DRI XFree86 CVS tree and kernel modules
    to see if that will help.

     
  • Paul Leopardi

    Paul Leopardi - 2001-04-03

    Logged In: YES
    user_id=187854

    I have a Hauppauge TV Go card and an integrated 8MB
    Rage128 on my Intel 440ZX motherboard and can do some
    testing but probably no coding. I am very time poor right
    now.
    Maybe it would be better if I just gave you my TV card or
    tried to find someone who (1) knows the DRI, xawtv and
    bttv code and the ATI and bttv hardware (2) has a TV card
    and (3) has the skills and time to help fix this.
    Is there any other way to get this and 231132 fixed?
    They look like similar or the same bug to me.

     
  • Ari Pollak

    Ari Pollak - 2001-04-05

    Logged In: YES
    user_id=41611

    Well, it looks like I've finally found a combination that
    fixes this - using the current XFree86 from development CVS,
    with the ATI Radeon LE and the CVS radeon.o kernel module,
    enabling Xvideo and DRI at the same time doesn't cause any
    trouble - no freezes, no lockups.

     
  • Philip Graham Willoughby

    Logged In: YES
    user_id=37866

    With current CVS I have no problem (apart from poor TV
    reception, but I can't blame that on DRI...). My Hardware is
    an ATI Radeon (QD) 32Mb DDR, AMD Duron, VIA Chipset Mobo,
    Kernel 2.4.3, TV card is an ATI TV-Wonder VE. Xvideo works
    great. I don't use the v4l driver as I have not seen any
    performance problem without it.

     
1 2 > >> (Page 1 of 2)

Log in to post a comment.