Paul, On Thu, Nov 25, 2010 at 7:15 PM, Paul Walmsley <paul@xxxxxxxxx> wrote: > Hi > > On Thu, 25 Nov 2010, Jean Pihet wrote: > >> On Thu, Nov 25, 2010 at 12:49 AM, Paul Walmsley <paul@xxxxxxxxx> wrote: >> > >> > The console semaphore must be held while the OMAP UART devices are >> > disabled, lest a console write cause an ARM abort (and a kernel crash) >> > when the underlying console device is inaccessible. These crashes >> > only occur when the console is on one of the OMAP internal serial >> > ports. >> This does not fix the issue for me on Beagle (console on ttyO2). >> >> Doing: >> / # echo 5 > /sys/devices/platform/omap/omap-hsuart.0/sleep_timeout >> / # echo 5 > /sys/devices/platform/omap/omap-hsuart.1/sleep_timeout >> / # echo 5 > /sys/devices/platform/omap/omap-hsuart.2/sleep_timeout >> and waiting 5 seconds hangs the console. > > By the way, I just tried this on a Beagle 35xx rev C2, with Tony's commit > 063d907edaf3fbf9776c189c3e02f2c7a129d18c, and did not see any hang. Are > you using a linux-omap kernel? Yes this is using l-o master on Beagle B5. > > > - Paul Jean -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
