On Mon, 2012-02-06 at 09:51 +0100, Hector Palacios wrote: > On 02/03/2012 06:39 PM, Steven Rostedt wrote: > > Note that you see that this causes a hang in the system if ksoftirqd is > > a real time task. > > This is true. > > > Not to mention, that ksoftirqd spins in an infinite > > loop if the cable isn't connected (regardless of ksoftirqd's priority). > > This is not true. The infinite loop is only hit when ksoftirqd is a real time task. I > think you got confused by the different patches we tried. That dirty hack of yours > with the workqueue was the one hanging with the cable disconnected. ;o) > I didn't say it was going to hang the box, I said it was going to spin. With the cable disconnected, did you run top to see if ksoftirqd was running at near 100%? It wont lock up the box because ksoftirqd is not a real time task in mainline. -- Steve -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
