Andi Kleen <[email protected]> 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?
> I'm not sure it was that good an idea to enable this warning by default in 2.6.17.
> It will be still in the release and probably generate some user queries.
>
> Might be better to disable it for 2.6.17 again and only reenable for 2.6.18 after
> some auditing?
>
Yes, I'm inclined to agree. It's finding some real but very minor
problems. Probably too minor to be scaring users. I'll cook up a patch to
move it under `initcall_debug'.
-
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]
