On Tuesday, 16 October 2007 21:58, Mark Gross wrote:
> On Mon, Oct 15, 2007 at 10:40:02PM +0200, Rafael J. Wysocki wrote:
> > On Monday, 15 October 2007 18:09, Mark Gross wrote:
> > > On Fri, Oct 12, 2007 at 11:32:40PM +0200, Rafael J. Wysocki wrote:
> > > > On Friday, 12 October 2007 06:31, Andrew Morton wrote:
> > > > >
> > > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23/2.6.23-mm1/
> > > > >
> > > > > - I've been largely avoiding applying anything since rc8-mm2 in an attempt
> > > > > to stabilise things for the 2.6.23 merge.
> > > > >
> > > > > But that didn't stop all the subsystem maintainers from going nuts, with
> > > > > the usual accuracy. We're up to a 37MB diff now, but it seems to be working
> > > > > a bit better.
> > > >
> > > > I get many traces similar to the one below from it (w/ hotfixes):
> > > >
> > > > WARNING: at /home/rafael/src/mm/linux-2.6.23-mm1/arch/x86_64/kernel/smp.c:397 smp_call_function_mask()
> > >
> > > This is from : WARN_ON(irqs_disabled()) in the cmp_call_function_mask
> > > processor_idle.c is registering a acpi_processor_latency_notify
> > >
> > > my code changed the notifier call from blocking_notifier_call_chain to
> > > srcu_notifier_call_chain, because dynamic creation of notifier chains at
> > > runtime where easier with the srcu_notifier_call_chain than the
> > > blocking_notifier_call_chain.
> > >
> > > As dynamic creation of PM_QOS parameters are no longer needed I can
> > > change the notifiers back to match what was in lanency.c
> > >
> > > However; looking at the call tree differences between
> > > blockin_notifier_call_chain and srcu_notifier_call_chain I cannot see a
> > > difference in irq enabling / disabling. I'm not confident this will
> > > address this yet.
> >
> > Well, you can send me a patch to check. :-)
>
> I think I'll have to send you a patch that changes the notifiers but I
> doubt it will fix it.
>
> After a bit of messing around I have the 2.6.23-mm1 running on my core-2
> box note: Ubuntu's make-kpkg on the mm1 tree resulted in a system that
> wouldn't boot past the intrd. Looks like the pivot root failed or
> something.
>
> Anyway, I'm not reproducing your experience, snd_pcm is loaded. I don't
> know none of the WARN's are not hitting on my box.
>
> do you have some configuration information that could help me reproduce
> the issue?
Well, I can send you the .config, but the box is AMD-based (Turion 64 X2),
with an ATI chipset and an HP BIOS, so it seems to be much different from
yours.
Greetings,
Rafael
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]