Re: How to make bug report
W dniu 2012-06-20 18:42, Antti Palosaari pisze: As author of the AF9015 I would like to see some of those errors. And your driver version. Use latest v4l-dvb if possible as I have changed it very much recently. I forgot to mention: I use Debian testing with experimental kernel: Linux wuwek 3.4-trunk-686-pae #1 SMP Wed Jun 6 15:11:31 UTC 2012 i686 GNU/Linux As drivers I use media_build from 12.06.2012 While I have inserted Prof Revolution 8000, it isn't used (VDR is run with only this one adapter), so my USB tuner is the only one I use. uwek:~/media_build/media_build# lsusb -v Bus 002 Device 002: ID 15a4:9016 Afatech Technologies, Inc. AF9015 DVB-T USB2.0 stick Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x15a4 Afatech Technologies, Inc. idProduct 0x9016 AF9015 DVB-T USB2.0 stick bcdDevice2.00 iManufacturer 1 Afatech iProduct2 DVB-T 2 iSerial 3 01010101061 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 71 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 4 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x84 EP 4 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x85 EP 5 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 0 No Subclass bInterfaceProtocol 1 Keyboard iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.01 bCountryCode0 Not supported bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 65 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 10 Device Qualifier (for other device speed): bLength10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 bNumConfigurations 1 Device Status: 0x (Bus Powered) wuwek:~/media_build/media_build# lsmod | grep dvb dvb_usb_af9015 21114 7 dvb_usb22062 1 dvb_usb_af9015 videobuf_dvb 12682 1 cx23885 dvb_core 68023 3 cx23885,dvb_usb,videobuf_dvb
Re: How to make bug report
W dniu 2012-06-20 18:42, Antti Palosaari pisze: As author of the AF9015 I would like to see some of those errors. And your driver version. Use latest v4l-dvb if possible as I have changed it very much recently. I was viewing/recording EURO match an everything was ok. I've scanned channels with w_scan, I was able to switch to every channel without any problem for a few hour. Today stick has switched off (LED doesn't light) and in log there are such errors: Jun 22 01:22:09 wuwek kernel: [18522.492454] af9015: recv bulk message failed:-110 Jun 22 01:22:09 wuwek kernel: [18522.492490] af9015: af9015_rc_query: failed:-1 Jun 22 01:22:09 wuwek kernel: [18522.492509] dvb-usb: error -1 while querying for an remote control event. Jun 22 03:43:51 wuwek kernel: [27010.597986] af9015: recv bulk message failed:-110 Jun 22 03:43:51 wuwek kernel: [27010.598021] af9015: af9015_rc_query: failed:-1 Jun 22 03:43:51 wuwek kernel: [27010.598040] dvb-usb: error -1 while querying for an remote control event. Jun 22 04:14:05 wuwek kernel: [28821.371758] af9015: recv bulk message failed:-110 Jun 22 04:14:05 wuwek kernel: [28821.371794] af9015: af9015_rc_query: failed:-1 Jun 22 04:14:05 wuwek kernel: [28821.371813] dvb-usb: error -1 while querying for an remote control event. Now if I try to play and channel - it doesn't work and there is nothing in kern.log From the user.log: VDR was querying card all the time but suddenly at 00:38 it lost lock. Jun 22 00:00:25 wuwek vdr: [7018] streamdev-server: closing VTP connection to 127.0.0.1:57560 Jun 22 00:04:54 wuwek vdr: [7009] cleaning up schedules data Jun 22 00:05:25 wuwek vdr: [7018] Streamdev: Accepted new client (VTP) 127.0.0.1:57561 Jun 22 00:05:26 wuwek vdr: [7018] streamdev-server: closing VTP connection to 127.0.0.1:57561 Jun 22 00:05:31 wuwek vdr: [7018] Streamdev: Accepted new client (VTP) 127.0.0.1:57562 Jun 22 00:05:31 wuwek vdr: [7018] streamdev-server: closing VTP connection to 127.0.0.1:57562 Jun 22 00:10:26 wuwek vdr: [7018] Streamdev: Accepted new client (VTP) 127.0.0.1:57567 Jun 22 00:10:26 wuwek vdr: [7018] streamdev-server: closing VTP connection to 127.0.0.1:57567 Jun 22 00:15:26 wuwek vdr: [7018] Streamdev: Accepted new client (VTP) 127.0.0.1:57569 Jun 22 00:15:26 wuwek vdr: [7018] streamdev-server: closing VTP connection to 127.0.0.1:57569 Jun 22 00:15:31 wuwek vdr: [7018] Streamdev: Accepted new client (VTP) 127.0.0.1:57570 Jun 22 00:15:31 wuwek vdr: [7018] streamdev-server: closing VTP connection to 127.0.0.1:57570 Jun 22 00:16:00 wuwek vdr: [7019] EPGSearch: search timer update started Jun 22 00:16:00 wuwek vdr: [7019] EPGSearch: search timer update finished Jun 22 00:16:00 wuwek vdr: [7020] EPGSearch: timer conflict check started Jun 22 00:16:00 wuwek vdr: [7020] EPGSearch: timer conflict check finished Jun 22 00:20:26 wuwek vdr: [7018] Streamdev: Accepted new client (VTP) 127.0.0.1:57572 Jun 22 00:20:27 wuwek vdr: [7018] streamdev-server: closing VTP connection to 127.0.0.1:57572 Jun 22 00:25:27 wuwek vdr: [7018] Streamdev: Accepted new client (VTP) 127.0.0.1:57573 Jun 22 00:25:27 wuwek vdr: [7018] streamdev-server: closing VTP connection to 127.0.0.1:57573 Jun 22 00:25:32 wuwek vdr: [7018] Streamdev: Accepted new client (VTP) 127.0.0.1:57574 Jun 22 00:25:32 wuwek vdr: [7018] streamdev-server: closing VTP connection to 127.0.0.1:57574 Jun 22 00:30:27 wuwek vdr: [7018] Streamdev: Accepted new client (VTP) 127.0.0.1:57575 Jun 22 00:30:27 wuwek vdr: [7018] streamdev-server: closing VTP connection to 127.0.0.1:57575 Jun 22 00:35:27 wuwek vdr: [7018] Streamdev: Accepted new client (VTP) 127.0.0.1:57577 Jun 22 00:35:28 wuwek vdr: [7018] streamdev-server: closing VTP connection to 127.0.0.1:57577 Jun 22 00:38:37 wuwek vdr: [7014] frontend 1/0 lost lock on channel 1, tp 177 Jun 22 00:38:39 wuwek vdr: [7014] frontend 1/0 timed out while tuning to channel 1, tp 177 Jun 22 00:39:07 wuwek vdr: [7014] frontend 1/0 timed out while tuning to channel 9, tp 184 Jun 22 00:39:33 wuwek vdr: [7014] frontend 1/0 timed out while tuning to channel 1, tp 177 Jun 22 00:39:59 wuwek vdr: [7014] frontend 1/0 timed out while tuning to channel 9, tp 184 Jun 22 00:40:25 wuwek vdr: [7014] frontend 1/0 timed out while tuning to channel 1, tp 177 Jun 22 00:40:28 wuwek vdr: [7018] Streamdev: Accepted new client (VTP) 127.0.0.1:57578 Jun 22 00:40:28 wuwek vdr: [7018] streamdev-server: closing VTP connection to 127.0.0.1:57578 Jun 22 00:40:51 wuwek vdr: [7014] frontend 1/0 timed out while tuning to channel 9, tp 184 Jun 22 00:41:17 wuwek vdr: [7014] frontend 1/0 timed out while tuning to channel 1, tp 177 Jun 22 00:41:43 wuwek vdr: [7014] frontend 1/0 timed out while tuning to channel 9, tp 184 Jun 22 00:42:09 wuwek vdr: [7014] frontend 1/0 timed out while tuning to channel 1, tp 177 Above messages reapets till now. Reinsterting tuner and restarting VDR will help but after some time it will stop working again. Marx -- To
Re: How to make bug report
On 06/18/2012 09:40 AM, Marx wrote: Hello I have four DVB cards: DVB-S2: -Pinnacle PCTV SAT HDTV 452E PRO USB (main kernel support) -Terratec Cinergy S2 USB HD v.2 -Prof Revolution DVB-S2 8000 PCIe DVB-T: -AF9015 noname USB (main kernel support) on AMD Brazos platform (Asrock E350M1) with Debian (lately with 3.4 kernel). While I could be able to make all of them working via different drivers (media-build, patches, vendor drivers, Igor Liplianin's repo, yavdr dkms package etc) none of this card works stable (unlike Twinhan PCI I had previously). Prof hangs system, Pinnacle doesn't work with DVB-S2, Terratec records streams partially unplayable, AF9015 stops working after and hour or so etc. Often I see errors of I2C subsystem. As author of the AF9015 I would like to see some of those errors. And your driver version. Use latest v4l-dvb if possible as I have changed it very much recently. While I'm in process of testing it on different hardware (laptop) I would like to know if it's good place to write about dvb drivers bugs. Or maybe should I write directly to developer? or write bugs in Debian/kernel bugzilla or sth similair? How to properly report bugs? What kernel should I use, which driverset? What logs to attach (kernel.log)? how to enable debug options (if needed)? Maybe best to contact driver author directly and CC this mailing list. I think it's rather unusual all of cards doesn't work, so I suspect that there can be something wrong with my system. Maybe you, as skilled developers, can direct me what can be wrong, what can I test? regards Antti -- http://palosaari.fi/ -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
