lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 20 Nov 2012 15:41:36 +0100
From:	Udo van den Heuvel <udovdh@...all.nl>
To:	linux-usb@...r.kernel.org
CC:	Alan Stern <stern@...land.harvard.edu>,
	Jan Ceuleers <jan.ceuleers@...puter.org>,
	Clemens Ladisch <clemens@...isch.de>,
	Simon Jones <sijones2010@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: 3.4.4: disabling irq

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:        631        640        677        734   IO-APIC-edge      i8042
  4:       1026        976        961       1098   IO-APIC-edge      serial
  9:          0          0          0          0   IO-APIC-fasteoi   acpi
 16:        409        403        406        414   IO-APIC-fasteoi
snd_hda_intel
 17:          1          1          0          2   IO-APIC-fasteoi
ehci_hcd:usb4, ehci_hcd:usb5
 18:      62356      62649      64102      67369   IO-APIC-fasteoi
ohci_hcd:usb1, ohci_hcd:usb2, ohci_hcd:usb3
 20:       5774       5762       5902       6405   IO-APIC-fasteoi   serial
 40:          0          0          0          0   PCI-MSI-edge      AMD-Vi
 43:      19483      19239      19938      20909   PCI-MSI-edge      ahci
 44:      51837      52223      53122      55971   PCI-MSI-edge      eth0
 45:          0          0          0          0   PCI-MSI-edge
xhci_hcd
 46:          0          0          0          0   PCI-MSI-edge
xhci_hcd
 47:          0          0          0          0   PCI-MSI-edge
xhci_hcd
 48:          0          0          0          0   PCI-MSI-edge
xhci_hcd
 49:          0          0          0          0   PCI-MSI-edge
xhci_hcd
 50:          0          0          0          0   PCI-MSI-edge
xhci_hcd
 51:          0          0          0          0   PCI-MSI-edge
xhci_hcd
 52:          0          0          0          0   PCI-MSI-edge
xhci_hcd
 53:          0          0          0          0   PCI-MSI-edge
xhci_hcd
 54:          0          0          0          0   PCI-MSI-edge
xhci_hcd
 55:          0          0          0          0   PCI-MSI-edge
xhci_hcd
 56:         26         24         42         31   PCI-MSI-edge
snd_hda_intel
 57:      28748      28431      29792      32594   PCI-MSI-edge      radeon
NMI:          0          0          0          0   Non-maskable interrupts
LOC:     271724     235396     273222     256476   Local timer interrupts
SPU:          0          0          0          0   Spurious interrupts
PMI:          0          0          0          0   Performance
monitoring interrupts
IWI:          0          0          0          0   IRQ work interrupts
RTR:          0          0          0          0   APIC ICR read retries
RES:     534762     574540     368898     508436   Rescheduling interrupts
CAL:      30439      42897      30212      31668   Function call interrupts
TLB:          0          0          0          0   TLB shootdowns
THR:          0          0          0          0   Threshold APIC interrupts
MCE:          0          0          0          0   Machine check exceptions
MCP:          4          4          4          4   Machine check polls
ERR:          8
MIS:          0

> 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 0000:00:12.0: IRQ: 24 8000005a
ohci_hcd 0000:00:14.5: IRQ: 24 8000005a
#

So what does this mean?
I did not get the `disabling irq` yet.


Udo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ