On Sat, 23 Aug 2008, Meelis Roos wrote: > > Meelis, in keeping with David's suggestion about posting the PCI > > writes, you ought to apply this patch along with the previous one. > > I doubt it will make any difference, but it's worth doing anyway. > > Now got it to boot with 9600 again, with both your patches applied (and > your earlier patch too) and it works (have not tried anything isn USB > port yet, the machine is remote): > [ 178.372334] usb usb1: New USB device found, idVendor=1d6b, idProduct=0001 > [ 178.461654] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 > [ 178.556720] usb usb1: Product: OHCI Host Controller > [ 178.620908] usb usb1: Manufacturer: Linux 2.6.27-rc3-00661-g82d63fc-dirty ohci_hcd > [ 178.720478] usb usb1: SerialNumber: 0000:00:0a.0 > [ 178.782540] hub 1-0:1.0: state 7 ports 2 chg 0000 evt 0000 > [ 179.030025] hub 1-0:1.0: state 7 ports 2 chg 0000 evt 0000 > [ 179.280279] hub 1-0:1.0: state 7 ports 2 chg 0000 evt 0000 > [ 179.532264] hub 1-0:1.0: state 7 ports 2 chg 0000 evt 0000 > [ 179.798787] hub 1-0:1.0: state 7 ports 2 chg 0000 evt 0000 > [ 180.050417] hub 1-0:1.0: state 7 ports 2 chg 0000 evt 0000 > [ 180.288167] hub 1-0:1.0: state 7 ports 2 chg 0000 evt 0000 > [ 180.534724] hub 1-0:1.0: state 7 ports 2 chg 0000 evt 0000 > [ 180.840060] hub 1-0:1.0: state 7 ports 2 chg 0000 evt 0000 > [ 181.177408] hub 1-0:1.0: state 7 ports 2 chg 0000 evt 0000 > [ 181.442548] hub 1-0:1.0: state 7 ports 2 chg 0000 evt 0000 > [ 181.670547] hub 1-0:1.0: state 7 ports 2 chg 0000 evt 0000 > [ 181.751735] ps used greatest stack depth: 0 bytes left All those hub debugging messages are normal for a system that's polling with a broken RHSC interrupt status bit. But what happened to the two ohci_info() calls I had you include? At least one of them should show up. Unless for some reason you have CONFIG_PM disabled? And I admit, I still don't know why it was working with the old kernel version... Alan Stern -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
