Your message dated Sat, 22 Aug 2015 08:22:52 +0200
with message-id <20150822062252.gb6...@bongo.bofh.it>
and subject line Re: Bug#796471: kmod should check for breakage on new kernels
has caused the Debian Bug report #796471,
regarding kmod should check for breakage on new kernels
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
796471: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796471
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kmod
Version: 21-1
Severity: grave
Tags: upstream
Justification: renders package unusable

when new kernels come out sometimes there is kmod breakage. There is no known
reason for this as headers are installed during the updating process.

Errors like these are commonly encountered:

Error! Bad return status for module build on kernel: 4.1.0-1-amd64 (x86_64)
Consult /var/lib/dkms/fglrx/15.7/build/make.log for more information.

It is these types of errors that break video drivers(nVidia and ATI) and apps
like VirtualBox when there is no need for the breakage and
incompatibility.People should not be forced into a new app version or video
driver version on each and every kernel update.Besides this is too much work
for the manufacturer.



-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages kmod depends on:
ii  libc6     2.19-19
ii  libkmod2  21-1
ii  lsb-base  4.1+Debian13+nmu1

kmod recommends no packages.

kmod suggests no packages.

-- no debconf information
DKMS make.log for fglrx-15.7 for kernel 4.1.0-1-amd64 (x86_64)
Fri Aug 21 17:37:33 CDT 2015
make: Entering directory '/usr/src/linux-headers-4.1.0-1-amd64'
  LD      /var/lib/dkms/fglrx/15.7/build/built-in.o
  CC [M]  /var/lib/dkms/fglrx/15.7/build/firegl_public.o
/var/lib/dkms/fglrx/15.7/build/firegl_public.c: In function 
‘KCL_InstallInterruptHandler’:
/var/lib/dkms/fglrx/15.7/build/firegl_public.c:3504:22: error: ‘IRQF_DISABLED’ 
undeclared (first use in this function)
         ((useMSI) ? (IRQF_DISABLED) : (IRQF_SHARED)),    
                      ^
/var/lib/dkms/fglrx/15.7/build/firegl_public.c:3504:22: note: each undeclared 
identifier is reported only once for each function it appears in
/var/lib/dkms/fglrx/15.7/build/firegl_public.c: At top level:
/var/lib/dkms/fglrx/15.7/build/firegl_public.c:6447:12: warning: 
‘KCL_fpu_save_init’ defined but not used [-Wunused-function]
 static int KCL_fpu_save_init(struct task_struct *tsk)
            ^
/var/lib/dkms/fglrx/15.7/build/firegl_public.c: In function 
‘KCL_InstallInterruptHandler’:
/var/lib/dkms/fglrx/15.7/build/firegl_public.c:3508:1: warning: control reaches 
end of non-void function [-Wreturn-type]
 }
 ^
/usr/src/linux-headers-4.1.0-1-common/scripts/Makefile.build:263: recipe for 
target '/var/lib/dkms/fglrx/15.7/build/firegl_public.o' failed
make[3]: *** [/var/lib/dkms/fglrx/15.7/build/firegl_public.o] Error 1
/usr/src/linux-headers-4.1.0-1-common/Makefile:1400: recipe for target 
'_module_/var/lib/dkms/fglrx/15.7/build' failed
make[2]: *** [_module_/var/lib/dkms/fglrx/15.7/build] Error 2
Makefile:146: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
Makefile:8: recipe for target 'all' failed
make: *** [all] Error 2
make: Leaving directory '/usr/src/linux-headers-4.1.0-1-amd64'

--- End Message ---
--- Begin Message ---
On Aug 22, Richard Jasmin <frazzledj...@gmail.com> wrote:

> when new kernels come out sometimes there is kmod breakage. There is no known
> reason for this as headers are installed during the updating process.
This is not related in any way to kmod.
Please ask for help on your favourite end users support channel.

-- 
ciao,
Marco

Attachment: pgpt3LeaOowZG.pgp
Description: PGP signature


--- End Message ---

Reply via email to