Re: initcall warnings in 2.6.17

[Pavel Machek]

On Pá 28-04-06 10:54:03, Andrew Morton wrote:
> Andi Kleen <ak@xxxxxxx> wrote:
> >
> > I still get
> > 
> > initcall at 0xffffffff807414c2: pci_iommu_init+0x0/0x501(): returned with error code -1
> 
> Should be returning -ENODEV.
> 
> > initcall at 0xffffffff80748b4d: init_autofs4_fs+0x0/0xc(): returned with error code -16
> 
> hm.  Why'd that happen?
> 
> > initcall at 0xffffffff803c7d5c: init_netconsole+0x0/0x6b(): returned with error code -22
> 
> Yeah.  I think netconsole is just being wrong here.  If it wasn't enabled
> there's no error.
> 
> > initcall at 0xffffffff80249307: software_resume+0x0/0xcf(): returned with error code -2
> 
> Similarly, there's no resume file configured so should we really consider
> this an error?

That one is easier to solve. But "configured but image not present"
will also produce warning I guess. If I return -ENODEV, will it keep
debugging system quiet?
								Pavel
-- 
Thanks for all the (sleeping) penguins.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/