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-next>] [day] [month] [year] [list]
Date:	Mon, 15 Apr 2013 22:16:57 +0200
From:	Michael Braun <michael.braun@....tu-ilmenau.de>
To:	Alan Stern <stern@...land.harvard.edu>
Cc:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	<linux-usb@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
	<projekt-wlan@....tu-ilmenau.de>
Subject: Regression in 3735ba8db8e6ea22ad3ff524328926d8d780a884 with
 Freescale P1020

Hi,

I'm running OpenWRT Kernel 3.8.3 (which already has 
f66dea709cd9309b2ee9f715697818001fb518de and 
5ed338778f917a035f0f0a52327fc4f72e36f7a1 applied) on a P1020WLAN (QorlQ, 
PPC) device.
Before updating the kernel from 3.3.0, USB host support was working 
fine. Now I get "fsl-ehci: USB PHY clock invalid" messages in dmesg and 
the lsusb output is empty, so USB host support is not working. When I 
apply the following patch, USB host support starts working again, so I 
guess 3735ba8db8e6ea22ad3ff524328926d8d780a884 is the cause.

Regards,
  M. Braun

--- a/drivers/usb/host/ehci-fsl.c       2013-04-15 21:13:52.924403077 
+0200
+++ b/drivers/usb/host/ehci-fsl.c       2013-04-15 21:13:57.572410838 
+0200
@@ -273,7 +273,6 @@ static int ehci_fsl_setup_phy(struct usb
                 if (!spin_event_timeout(in_be32(non_ehci + 
FSL_SOC_USB_CTRL) &
                                 PHY_CLK_VALID, FSL_USB_PHY_CLK_TIMEOUT, 
0)) {
                         printk(KERN_WARNING "fsl-ehci: USB PHY clock 
invalid\n");
-                       return -EINVAL;
                 }
         }


--
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