On Sat, 1 Dec 2012, Udo van den Heuvel wrote:
> > Secondly, try building a kernel with the patch below and
> > CONFIG_USB_DEBUG enabled. Let's see what the dmesg log says when the
> > problem occurs.
> [root@a mesa]# dmesg|sort|uniq
The sort messes up the order of the messages. uniq by itself
On 2012-11-19 17:41, Alan Stern wrote:
> On Sat, 17 Nov 2012, Udo van den Heuvel wrote:
>> How to proceed next?
>
> Firstly, what does /proc/interrupts say?
>
> Secondly, try building a kernel with the patch below and
> CONFIG_USB_DEBUG enabled. Let's see what the dmesg log says when the
> pro
On Tue, 20 Nov 2012, Udo van den Heuvel wrote:
> > Secondly, try building a kernel with the patch below and
> > CONFIG_USB_DEBUG enabled. Let's see what the dmesg log says when the
> > problem occurs.
>
> I just booted into 3.6.7 with the patch:
>
> # dmesg|sort|uniq
> ohci_hcd :00:12.0:
On 2012-11-19 17:41, Alan Stern wrote:
> Firstly, what does /proc/interrupts say?
# cat /proc/interrupts
CPU0 CPU1 CPU2 CPU3
0: 40 0 0 0 IO-APIC-edge timer
1:631640677734 IO-APIC-edge
On 2012-11-19 17:41, Alan Stern wrote:
>> How to proceed next?
>
> Firstly, what does /proc/interrupts say?
# cat /proc/interrupts
CPU0 CPU1 CPU2 CPU3
0: 39 0 0 0 IO-APIC-edge timer
1:716721730
On Sat, 17 Nov 2012, Udo van den Heuvel wrote:
> The problem still happens. irq 18 is dsiabled every now and then.
> This time on different, new hardware.
> The motherboard is now a Gigabyte F2A85X-UP4.
> Camera is the same pwc cam.
>
> Recently I removed the USB printer that was attached to the
On 2012-07-15 20:28, Alan Stern wrote:
> Um, I think you missed the point. The whole idea of the test is to see
> what happens while the controller is unbound from the driver. Binding
> it again defeats the purpose.
The problem still happens. irq 18 is dsiabled every now and then.
This time on
Well,
The issue appeared again.
irq 18 was disabled, one pwc webcam was on that irq.
This time on new hardware: Gigabyte F2A85X-UP4 with A10-5800K APU.
The box was busy with it's raid10 array, this time, by running bonnie++;
also a raid-check was in progress. (unknown at the time)
So what does t
On Sun, 15 Jul 2012, Udo van den Heuvel wrote:
> On 2012-07-15 17:35, Alan Stern wrote:
> > echo :00:13.1 >/sys/bus/pci/drivers/ohci_hcd/unbind
>
> Afterwards I did:
>
> > echo :00:13.1 >/sys/bus/pci/drivers/ohci_hcd/bind
Um, I think you missed the point. The whole idea of the test is
On 2012-07-15 17:55, Udo van den Heuvel wrote:
> After doing this I could modprobe pwc and start mrtg without problem.
Euh: s/mrtg/motion/
Udo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
On 2012-07-15 17:35, Alan Stern wrote:
> echo :00:13.1 >/sys/bus/pci/drivers/ohci_hcd/unbind
Afterwards I did:
> echo :00:13.1 >/sys/bus/pci/drivers/ohci_hcd/bind
And I saw:
Jul 15 17:50:30 surfplank2 kernel: ohci_hcd :00:13.1: remove, state 1
Jul 15 17:50:30 surfplank2 kernel: usb
On Sun, 15 Jul 2012, Udo van den Heuvel wrote:
> > The conclusion is that ohci-hcd is the only driver using IRQ 18. If
> > you build a kernel with CONFIG_USB_DEBUG enabled, it will be possible
> > to see if the OHCI hardware is responsible for the IRQ problem.
> >
> > When the IRQ line gets di
On 2012-07-15 16:28, Udo van den Heuvel wrote:
> After disabling:
And somewhat later:
bus pci, device :00:12.0
OHCI Host Controller
ohci_hcd
OHCI 1.0, NO legacy support registers, rh state running
control 0x083 HCFS=operational CBSR=3
cmdstatus 0x0 SOC=0
intrstatus 0x0024 FNO SF
intr
On 2012-07-12 16:54, Alan Stern wrote:
> On Thu, 12 Jul 2012, Udo van den Heuvel wrote:
>
>> # cat /proc/interrupts
(...)
>> 18: 25190 18052161 21311 IO-APIC-fasteoi
>> ohci_hcd:usb5, ohci_hcd:usb6, ohci_hcd:usb7
(...)
>> So what can we conclude?
> The conclusion is that
On Thu, 12 Jul 2012, Udo van den Heuvel wrote:
> # cat /proc/interrupts
>CPU0 CPU1 CPU2 CPU3
> 0: 40 0 0 0 IO-APIC-edge timer
> 1: 1 4 91884418 IO-APIC-edge i8042
> 4: 1
On 2012-07-12 15:43, Jan Ceuleers wrote:
> On 07/12/2012 03:23 PM, Udo van den Heuvel wrote:
>> How to list what modules/programs are using that irq?
>
> cat /proc/interrupts
# cat /proc/interrupts
CPU0 CPU1 CPU2 CPU3
0: 40 0 0 0
On 07/12/2012 03:23 PM, Udo van den Heuvel wrote:
> How to list what modules/programs are using that irq?
cat /proc/interrupts
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel
On 2012-07-11 17:15, Alan Stern wrote:
> On Wed, 11 Jul 2012, Udo van den Heuvel wrote:
>
>> New occurrence:
>
>> Any clues and/or updates?
>
> Didn't you see the message I posted on Monday?
>
> http://marc.info/?l=linux-usb&m=134186054713868&w=2
Nothing changed except the kernel.
Main c
On Wed, 11 Jul 2012, Udo van den Heuvel wrote:
> New occurrence:
>
> Jul 11 16:45:26 box3 kernel: irq 18: nobody cared (try booting with the
> "irqpoll" option)
> Jul 11 16:45:26 box3 kernel: Pid: 1465, comm: irq/18-ohci_hcd Not
> tainted 3.4.4 #3
> Any clues and/or updates?
Didn't you see the
On 2012-07-09 15:54, Clemens Ladisch wrote:
> (forwarded to linux-usb)
>
> Udo van den Heuvel wrote:
>>
>> One moment the box is runing OK.
>> One moment the 3.4.4 kernel decides to disable an interrupt.
>> Why?
>>
>> Jul 8 07:43:49 box3 ntpd[5067]: parse: convert_rawdcf: INCOMPLETE DATA -
>> ti
On Mon, 9 Jul 2012, Clemens Ladisch wrote:
> (forwarded to linux-usb)
>
> Udo van den Heuvel wrote:
> > Hello,
> >
> > One moment the box is runing OK.
> > One moment the 3.4.4 kernel decides to disable an interrupt.
> > Why?
The kernel disables IRQs when too many interrupts arrive too quickly.
On 2012-07-09 15:54, Clemens Ladisch wrote:
> (forwarded to linux-usb)
>
> Udo van den Heuvel wrote:
>> Hello,
>>
>> One moment the box is runing OK.
>> One moment the 3.4.4 kernel decides to disable an interrupt.
>> Why?
>>
>> Jul 8 07:43:49 box3 ntpd[5067]: parse: convert_rawdcf: INCOMPLETE DAT
Hello,
One moment the box is runing OK.
One moment the 3.4.4 kernel decides to disable an interrupt.
Why?
Jul 8 07:43:49 box3 ntpd[5067]: parse: convert_rawdcf: INCOMPLETE DATA
- time code only has 1 bits
Jul 8 07:44:53 box3 kernel: irq 18: nobody cared (try booting with the
"irqpoll" option)
J
23 matches
Mail list logo
