On Fri, Apr 08, 2016 at 07:37:12PM +1000, Brian Chadwick wrote: > On 08/04/16 01:59, Greg KH wrote: > > On Fri, Apr 08, 2016 at 01:34:51AM +1000, Brian Chadwick wrote: > > > On 08/04/16 00:44, Greg KH wrote: > > > > On Thu, Apr 07, 2016 at 03:04:55PM +1000, Brian Chadwick wrote: > > > > > On 06/04/16 19:53, Greg KH wrote: > > > > > > On Tue, Apr 05, 2016 at 06:42:51PM +1000, Brian Chadwick wrote: > > > > > > > SETUP: > > > > > > > > > > > > > > i7 16GB Computer. > > > > > > > > > > > > > > 1 x PCI-x USB3 adaptor card (i think uses xhci-hcd)04:00.0 USB controller: > > > > > > > Renesas Technology Corp. uPD720202 USB 3.0 Host Controller (rev 02) > > > > > > > Kernel driver in use: xhci_hcd > > > > > > > > > > > > > > 2 x USB3 to dual SATA HDD docks. uses JMicron JMS56x Series controllers, > > > > > > > uses uas.ko kernel module > > > > > > > Bus 004 Device 002: ID 152d:9561 JMicron Technology Corp. / JMicron USA > > > > > > > Technology Corp. > > > > > > > Bus 004 Device 003: ID 152d:9561 JMicron Technology Corp. / JMicron USA > > > > > > > Technology Corp. > > > > > > > > > > > > > > 3 x Western Digital 320GB 3.5" SATA drives > > > > > > > > > > > > > > USE: > > > > > > > > > > > > > > RAID 5 > > > > > > > > > > > > > > KERNEL: > > > > > > > 4.3.5 > > > > > > > > > > > > > > System works perfectly as expected. > > > > > > > > > > > > > > > > > > > > > Change to kernel 4.4.x or 4.5 and RAID 5 doesnt work. I am not sure whether > > > > > > > its actually RAID 5 at fault or if its the USB Attached SCSI driver uas.ko, > > > > > > > or maybe the host driver xhci-hcd. > > > > > > Can you run 'git bisect' to try to track down the offending commit? > > > > > > > > > > > > thanks, > > > > > > > > > > > > greg k-h > > > > > Hi, I am unfamiliar with that command, when should it be run, and in what > > > > > directory? > > > > Use it on the Linux kernel source git tree. 'man git-bisect' will > > > > describe all about how to use it. If you have specific questions about > > > > it after reading that, please let us know. > > > > > > > > thanks, > > > > > > > > greg k-h > > > > > > > I am sorry to disappoint you ... I know nothing of the git tree ... I am > > > just a normal user who knows a little more than usual but not that much more > > > ... i only download the source tarballs from kernel.org, i don't use git ... > > > so i don't know how else to help > > If you are used to downloading source tarballs, using git is even > > easier. Just download the git tree once, and then updates are much > > smaller downloads. > > > > Download Linus's tree: > > git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git > > > > Copy your working .config file into the directory created: > > cp $MY_WORKING_CONFIG linux/ > > > > Go into the directory: > > cd linux/ > > > > run git bisect: > > git biset start > > git bisect good v4.3 > > git bisect bad v4.5 > > > > and it will chunk away and give you a kernel to test: > > make oldconfig > > make -j16 > > install and boot the kernel > > > > and continue on with your testing of trying to find out where it broke. > > > > Hope this helps, > > > > greg k-h > > -- > Hi, so I followed man and did "git bisect good" for each iteration that > worked ok. Now I have arrived at the bad kernel. Do I do "git bisect bad"? > and then what? Yes, do 'git bisect bad' and then git will give you another kernel to test, eventually it will narrow things down and tell you exactly what commit caused the problem, and you can email us that information. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
