Am Montag, den 01.02.2010, 19:06 +0100 schrieb Thomas Voegtle:
Hello,
yesterday I moved from 2.6.31.y to 2.6.32 and found a reproducable kernel
oops.
Bug is in Linus' tree, too.
I use a Hauppauge Nova-T Stick with dvb_usb_dib0700
I start mplayer (no problems so far) and then alevt.
Thomas Voegtle wrote:
Hello,
yesterday I moved from 2.6.31.y to 2.6.32 and found a reproducable
kernel oops.
Bug is in Linus' tree, too.
Please try the two patches I sent to the ML today that fixes two potential
situations where the OOPS bug may hit.
I suspect that alevt-dvb is doing
On Mon, 1 Feb 2010, Chicken Shack wrote:
Hi Thomas,
thanks for reproducing that kernel oops.
Question:
Can you also confirm / reproduce that alevt does not follow the new TV
or radio channel if the new channel, tuned by dvbstream / mplayer for
example, is part of another transponder?
On Mon, 1 Feb 2010, Mauro Carvalho Chehab wrote:
Thomas Voegtle wrote:
Hello,
yesterday I moved from 2.6.31.y to 2.6.32 and found a reproducable
kernel oops.
Bug is in Linus' tree, too.
Please try the two patches I sent to the ML today that fixes two potential
situations where the OOPS bug
Am Montag, den 01.02.2010, 17:46 -0200 schrieb Mauro Carvalho Chehab:
Thomas Voegtle wrote:
Hello,
yesterday I moved from 2.6.31.y to 2.6.32 and found a reproducable
kernel oops.
Bug is in Linus' tree, too.
Mauro,
To begin with: Thanks for your investigation and patch authoring of
Am Montag, den 01.02.2010, 21:50 +0100 schrieb Thomas Voegtle:
On Mon, 1 Feb 2010, Chicken Shack wrote:
Hi Thomas,
thanks for reproducing that kernel oops.
Question:
Can you also confirm / reproduce that alevt does not follow the new TV
or radio channel if the new channel, tuned
