On Fri, Jul 22, 2011 at 2:58 AM, Michal Pokrywka wrote:
>> I had the same problem when I upgraded to 2.6.38 vanilla (and
>> currently at 2.6.39.1), but I can't remember what the last successful
>> version was (probably greater than 2.6.32). My syslog was full of the
>> WARN_ON trace from sch_hfsc.
Oops - my logs are again filled with the WARN_ON from
net/sched/sch_hfsc.c:1427. Sorry for the confusion, it looks like
"initialize parent's cl_cfmin properly in init_vf()" is not to blame.
This is an amd64 system. Vanilla kernel.org kernel except with fglrx
(the amd/ati radeon proprietary driver
I had the same problem when I upgraded to 2.6.38 vanilla (and
currently at 2.6.39.1), but I can't remember what the last successful
version was (probably greater than 2.6.32). My syslog was full of the
WARN_ON trace from sch_hfsc.c:1427.
I looked back through the history for sch_hfsc.c (see
http:/
3 matches
Mail list logo