On Fri, Sep 2, 2016 at 9:47 PM, Ronan Arraes Jardim Chagas <ronisbr@xxxxxxxxx> wrote: > Hi Chris, > > Em Sex, 2016-09-02 às 21:41 -0600, Chris Murphy escreveu: >> I suggest removing the hardware, and the proprietary driver, and >> retest the system with the existing Tumbleweed 4.7.0 kernel; and if >> that still fails, then try the Leap 4.4 kernel. >> >> Proprietary kernels can do all kinds of crazy things they shouldn't >> so >> it's entirely possible that driver is a factor in the problem. > > Actually it is just a module that I load. It is only loaded when I need > to work with it. However, I can assure this is not the problem because > I installed the board one month ago +-, but I have been seeing ENOSPC > since the beginning of the year IIRC. I am using Tumbleweed default > kernel right now, but I just can try Leap when 42.2 is released. If you want a work around sooner than later, pick up one of the latest Leap 42.2 kernels from the URL I provided, I haven't tried it but it ought to work. Leap 42.2 isn't going to be released for another 2.5 months. -- Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
