On 2015-12-21 19:10 -0500, Phillip Susi wrote:
> On 12/21/2015 05:29 PM, Sven Joachim wrote:
>> Wrong, both the old and the new kernel provide their modules in
>> /lib/modules/3.16.0-4-amd64. Jacob upgraded the
>> linux-image-3.16.0-4-amd64 package, he did no install a new
>> package.
>
> No... if the new kernel is 3.16.0-4, then the old one was 3.16.0-3.
Both the original report ("Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU
cores)") and the followup in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808380#25 show that
Jacob had already running 3.16.0-4. If he had been using 3.16.0-3, the
problem would not have shown up since modprobe does not try to load
3.16.0-4 modules into a 3.16.0-3 kernel.
> This is the reason why debian adds the extra digit to the version
> number and bumps it each time the kernel is updated.
Debian does not do this, to avoid uncontrolled proliferation of
kernels. In fact, the 3.16 kernel has been at the 3.16.0-4 ABI for over
a year (the last ABI bump was in November 2014, version 3.16.7-1).
Cheers,
Sven
