; Okay, I finally have located the patch causing this bizzare
> problem
> > > > for me. Before I discuss it, I'm going to drag out the kernel
> bug reporting
> > > > guidelines and try to make a proper bug report out of this.
> > > >
> >
On Sat, Feb 16, 2013 at 05:18:10AM +, Ben Hutchings wrote:
> Don't worry about it - I think the log messages are a pretty good clue.
>
> Does this patch fix the log messages and/or the other issues?
>
Yes! In fact after a quick reboot, the log lines look to me like they exist
properly, acpi
t; for me. Before I discuss it, I'm going to drag out the kernel bug
> > > reporting
> > > guidelines and try to make a proper bug report out of this.
> > >
> > > [1.] One line summary of the problem:
> > > 3.2.38 most of the time has 1
> [1.] One line summary of the problem:
> 3.2.38 most of the time has 100% cpu use reported
>
> [2.] Full description of the problem/report:
> Reverse applying the patch for
>
> [9a1f08a1a192f9177d7063d903773aed800b840f] drivers/firmware/dmi_scan.c: fetch
> dmi version
4 matches
Mail list logo