I was able to track this down by building kernels against /base/stable/9 (it took -hours!-).
The issue does occur with commit 244616, but does not occur with 244614. The only difference is a small patch to /usr/src/sys/dev/acpica/acpi_cpu.c - this code appears to do with c-state processing. I'll note it in the ticket, but somebody might want to look at this ASAP On Thu, Aug 29, 2013 at 7:10 AM, Adrian Chadd <adr...@freebsd.org> wrote: > Wow. Uhm, can you downgrade to 9.1 and see if it still happens? > > Would you be able to bisect the kernel source and see if you can find > where along stable/9 it happened? That's the fastest way to determine what > broke. > > Thanks! > > > > -adrian > > > > On 29 August 2013 06:32, Mike Harding <mvhard...@gmail.com> wrote: > >> I opened a ticket about this: kern/181632 >> >> Basically, if I do a 'zzz' and then wake the system up, operations like a >> buildworld or portmaster take much longer after the resume - systat shows >> very low CPU/disk utilization. It's 100% repeatable, I don't recall this >> happening on 9.1 >> >> I build 9.2-RC3 from source (as I have for years) - this is a fairly >> generic SMP system (i5 750 with 4 cpus). >> >> Let me know if I can provide any data - this is a fairly significant >> regression for me as I have taken to bringing the system up as needed vs. >> leaving it on all of the time. >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" >> > > _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
