Hi Sven,
Sven Hartge wrote:
> > > But, and here it becomes strange: It does work on a third system
> > > of mine. Question now is: What is different and/or broken on the
> > > first two systems?
> >
> > Exactly.
>
> Now I am up two for two.
>
> The only thing of note I can think of is the age of the systems
> involved:
>
> One failing system was installed in 2000 and kept on daily unstable
> ever since, the other was installed in 2002 and also kept on daily
> unstable.
Still have none where it failed. Installation dates of my machines
where an installation with 5.9.0-1 headers and image (not running that
kernel though) installed so far succeeded:
2007 (amd64; Xen DomU Guest)
2012 (amd64; Xen DomU Guest; runs Testing by default)
2013 (i386; EeePC 900)
2015 (amd64; Thinkpad X250)
2016 (amd64; Workstation)
> The other systems installation was more recently (2006ish).
My gut feeling: Left over files from ancient packages. The older such
systems are, the higher is the chance that a crash with follwing file
system check happened which then didn't properly clean up a half
installed or half removed package.
> Next step would be to strace the dkms build process and compare the
> output to find out what files are referenced to find the offending
> header files.
Good idea, thanks!
Regards, Axel
--
,''`. | Axel Beckert <a...@debian.org>, https://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
