Current-Users archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: panic running include/t_paths
On Tue, May 05, 2015 at 07:13:39AM +0800, Paul Goyette wrote:
> Also, I'm having a bit of difficulty in reproducing a XEN_DOM0 kernel that
> matches yours. The panic was at sysmonopen()+0x8a but that seems to end up
> in the middle of an instruction! Can you either disassemble sysmonopen()
> for me, or point me at the kernel file that I can download?
this is a domU kernel, from the HEAD autobuild
On Tue, May 05, 2015 at 07:55:05AM +0800, Paul Goyette wrote:
> OK, I think I found this one!
>
> It seems that when sysmonopen() is called, it might need to autoload the
> module that handles the specific sub-comopnent (envsys, power, or wdog). But
> if the autoload failed, the code blindly proceeded to call the
> sub-component's open routine anyway (indirectly through the sysmon_opvec
> table). Since autoload had failed, the opvec entry was never loaded and we
> jumped off into never-never land. :)
this is likely to be the problem. Xen kernels are not MODULAR.
>
> I've fixed the code to just return the error code ENODEV if autoload fails.
>
> The include/t_paths test will likely still fail, since it won't be able to
> open /dev/{sysmon,power,wdog} paths. But at least it shouldn't panic any
> more.
thanks, I'll watch the test runs and see if the next autobuild fixes it
(this may take up to two days)
--
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
NetBSD: 26 ans d'experience feront toujours la difference
--
Home |
Main Index |
Thread Index |
Old Index