On Tue, 6 Feb 2007, Chris Johns wrote:
Patrick Boettcher wrote:
I'm not exactly sure what needs to and what can be done.
I would like to stop the kernel oops. Having the kernel crash is a pain.
My question was related to USB debugging - I'm not sure what can be done
on the USB side
Patrick Boettcher wrote:
On Tue, 6 Feb 2007, Chris Johns wrote:
Patrick Boettcher wrote:
I'm not exactly sure what needs to and what can be done.
I would like to stop the kernel oops. Having the kernel crash is a pain.
My question was related to USB debugging - I'm
Hi,
I'm not exactly sure what needs to and what can be done.
Maybe asking on the linux-usb-devel-list helps to figure out the real
problem.
Patrick.
On Fri, 26 Jan 2007, Chris Johns wrote:
Patrick Boettcher wrote:
What exactly was it that improved the behaviour in 2.6.20-rc4 ?
Matt Doran wrote:
I've just upgraded to the ubuntu 2.6.20-5 kernel, which I believe is
based on 2.6.20-rc5.I'll see if this reduces the occurrence of the
problem.
I'm happy to help by running a different kernel or enabling
USB-debugging. Let me know what your after and how to do
Henrik Beckman wrote:
Hi,
On my myth box I have a simple script that checks messages every 10sec
and reboots if the usb disconnect line appears, I collect timestamped
copies of the messages files.
A distinct pattern i still to occur, but some channels are worse than
others, but that might be
A script that collects logfiles and reboots after an disconnect does both
save your recording and collect data in an orderly way ; )
Unfortunatly I´m not able to change kernel right know so I can´t contribute
=(
/Henrik
On 1/25/07, Matt Doran [EMAIL PROTECTED] wrote:
Henrik Beckman wrote:
On Thu, 25 Jan 2007, Matt Doran wrote:
Henrik Beckman wrote:
Hi,
On my myth box I have a simple script that checks messages every 10sec and
reboots if the usb disconnect line appears, I collect timestamped copies of
the messages files.
A distinct pattern i still to occur, but some
On Thu, 2007-01-25 at 13:29 +0100, Patrick Boettcher wrote:
Can someone check if the lsusb -v output is showing something like:
bmAttributes 0xe0
Self Powered
Remote Wakeup
Hi,
No I have an other output :
bmAttributes 0xa0
(Bus Powered)
Remote
On 25 Jan 2007, at 12:29, Patrick Boettcher wrote:
Can someone check if the lsusb -v output is showing something like:
bmAttributes 0xe0
Self Powered
Remote Wakeup
Mine is missing the Self Powered. I've experienced the oops /
disconnects.
Bus 008 Device 002: ID
Hmm?!
What exactly was it that improved the behaviour in 2.6.20-rc4 ?
What is the exact reason for the disconnect (USB-debugging need to be
enabled maybe)? Is it the device which disconnects itself or is it the bus
which disconnects the device due to an error?
Patrick.
On Thu, 25 Jan 2007,
Torgeir Veimo wrote:
On 25 Jan 2007, at 12:29, Patrick Boettcher wrote:
Can someone check if the lsusb -v output is showing something like:
bmAttributes 0xe0
Self Powered
Remote Wakeup
Mine is missing the Self Powered. I've experienced the oops / disconnects.
Same
Matt Doran wrote:
Torgeir Veimo wrote:
Can you include some output from /var/log/messages before the oops
itself? In my case I see USB disconnects, then an oops from something
unrelated just after that.
You're right. There's a USB disconnect before this occurs. The
messages are
Hi,
On my myth box I have a simple script that checks messages every 10sec and
reboots if the usb disconnect line appears, I collect timestamped copies of
the messages files.
A distinct pattern i still to occur, but some channels are worse than
others, but that might be time of day caused
Hi there,
I've just recently setup a Mythtv box with a Hauppauge Nova-T 500
card. The machine also has an Avermedia A777, but I believe only the
Nova-T was active at the time. The stack trace also has similarities
with other reported oops's. It did look a little different to the other
On 22 Jan 2007, at 23:28, Matt Doran wrote:
I've just recently setup a Mythtv box with a Hauppauge Nova-T 500
card. The machine also has an Avermedia A777, but I believe only
the Nova-T was active at the time. The stack trace also has
similarities with other reported oops's. It
Torgeir Veimo wrote:
Can you include some output from /var/log/messages before the oops
itself? In my case I see USB disconnects, then an oops from something
unrelated just after that.
You're right. There's a USB disconnect before this occurs. The
messages are attached. The same
16 matches
Mail list logo
