On Tue, Sep 10, 2013 at 09:45:50AM +0200, Jochen Striepe wrote: > Hello, > > On Mon, Sep 09, 2013 at 03:27:51PM -0700, Paul E. McKenney wrote: > > On Mon, Sep 09, 2013 at 11:58:36PM +0200, Jochen Striepe wrote: > > > I just got this on 3.10.11 on the same machine. Could that be > > > related? > > > > Several people helped track down another source of spurious stall > > warnings on large systems, please see below for the patch. > [...] > > This is quite rare, but apparently occurs deterministically > > on systems with about 6TB of memory. > > Hmm. My system is an ASUS Eee PC netbook with a total of 2G memory. > The latest stall was just when booting, while /dev was to be filled > by udev (and taking a really long time on that). So I think this > patch should not help at my machine, right? > > I tried to reproduce the stall, but without success. Is there anything > that could help reproducing? Their stall was due to old-style creation of sysfs entries for memory. Yours might be having a similar issue with the creation of /dev entries, so it would be worth trying it. One thing to try would be to insert delays into the code involved in creating the /dev entries. These delays will need to be busy-waits rather than sleeps. Thanx, Paul -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html