Bug#778942: linux-kbuild-3.16-3
hi. I just posted Bug#778942. After posting, I rebooted and studied my package listing for linux related packages. Apparently I had been using the i386 linux-kbuild package! I have no idea how that got there, this has always been a 64-bit system. ii linux-kbuild-3.16 3.16-3 i386 K Yikes! Did a dependency wire get crossed somewhere? Suffice to say, after aptitude install linux-kbuild-3.16:amd64 (uninstalling linux-kbuild-3.16:i386) Everything works as expected! Thank you so much for making debian awesome! have a day.yad jdpf
Bug#778942: linux-kbuild-3.16: scripts/recordmcount fails, emits Value too large for defined data type on large XFS file-system
Package: linux-kbuild-3.16 Version: 3.16-3 Severity: important Tags: lfs Dear Maintainer, * What led up to the situation? I am running Debian Jessie, Linux debian 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt2-1 (2014-12-08) x86_64 GNU/Linux. I attempted to install fglrx and discovered that ALL dkms kernel module builds were failing for me with: Value too large for defined data type I have a ~4TB XFS filesystem... According to XFS documentation, by default for any FS over 2GB, the filesystem is created to support 64 bit inodes. There have been many years of migration efforts to address LFS issues with tools compiled in 32bit mode. In retrospect, this issue has been present for some months now. Here is the mount-line showing that XFS is mounted with inode64: # mount /dev/mapper/root on / type xfs (rw,relatime,attr2,inode64,noquota) * What exactly did you do (or not do) that was effective (or ineffective)? When attempting to run a dkms build, the build would fail. For example, here is the case for acpi-call. ALL other kernel modules fail for me due to the inode64 issue. root@debian:/usr/src# aptitude install acpi-call-dkms The following NEW packages will be installed: acpi-call-dkms 0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 12.9 kB of archives. After unpacking 73.7 kB will be used. Get: 1 http://debian.lcs.mit.edu/debian/ testing/main acpi-call-dkms all 1.1.0-2 [12.9 kB] Fetched 12.9 kB in 0s (82.9 kB/s) Retrieving bug reports... Done Parsing Found/Fixed information... Done Selecting previously unselected package acpi-call-dkms. (Reading database ... 716228 files and directories currently installed.) Preparing to unpack .../acpi-call-dkms_1.1.0-2_all.deb ... Unpacking acpi-call-dkms (1.1.0-2) ... Setting up acpi-call-dkms (1.1.0-2) ... Loading new acpi-call-1.1.0 DKMS files... First Installation: checking all kernels... Building only for 3.16.0-4-amd64 Building initial module for 3.16.0-4-amd64 Error! Bad return status for module build on kernel: 3.16.0-4-amd64 (x86_64) Consult /var/lib/dkms/acpi-call/1.1.0/build/make.log for more information. * What was the outcome of this action? A failed build for rather mysterious reasons: root@debian:/usr/src# cat /var/lib/dkms/acpi-call/1.1.0/build/make.log DKMS make.log for acpi-call-1.1.0 for kernel 3.16.0-4-amd64 (x86_64) Sat Feb 14 16:09:33 EST 2015 make: Entering directory '/usr/src/linux-headers-3.16.0-4-amd64' make[1]: Entering directory `/usr/src/linux-headers-3.16.0-4-amd64' LD /var/lib/dkms/acpi-call/1.1.0/build/built-in.o CC [M] /var/lib/dkms/acpi-call/1.1.0/build/acpi_call.o /var/lib/dkms/acpi-call/1.1.0/build/acpi_call.o: Value too large for defined data type /usr/src/linux-headers-3.16.0-4-common/scripts/Makefile.build:268: recipe for target '/var/lib/dkms/acpi-call/1.1.0/build/acpi_call.o' failed make[3]: *** [/var/lib/dkms/acpi-call/1.1.0/build/acpi_call.o] Error 1 /usr/src/linux-headers-3.16.0-4-common/Makefile:1350: recipe for target '_module_/var/lib/dkms/acpi-call/1.1.0/build' failed make[2]: *** [_module_/var/lib/dkms/acpi-call/1.1.0/build] Error 2 Makefile:181: 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-3.16.0-4-amd64' Some days later I narrowed the build action down to make, and ran strace on the make process: # cd /usr/src/acpi-call-1.1.0 # strace -v -ttt -T -e trace=file -y -ff -o acpi_call-strace-make make --debug 1424548709.184383 execve(./scripts/recordmcount, [./scripts/recordmcount, /usr/src/acpi-call-1.1.0/acpi_ca...], [SUDO_GID=1000, ARCH=x86, MAIL=/va r/mail/root, USER=root, LANGUAGE=, OBJCOPY=objcopy, mod_strip_cmd=true, MODVERDIR=/usr/src/acpi-call-1.1..., HOSTCC=gcc, SHLVL=1, HOME=/root , OLDPWD=/usr/src, REALMODE_CFLAGS= -m32 -include /..., GENKSYMS=scripts/genksyms/genksy..., INSTALLKERNEL=installkernel, CONFIG_X86_X32_ABI=y, VP ATH=/usr/src/linux-headers-3.1..., LDFLAGS=-m elf_x86_64, KBUILD_VERBOSE=0, KBUILD_BUILTIN=, MAKEFLAGS=rR -I/usr/src/linux-he..., HOSTCXXFLAGS=-O2 , LDFLAGS_MODULE=, Q=@, CPP= gcc-4.8 -E, KBUILD_MODULES=1, SRCARCH=x86, SUDO_UID=1000, STRIP=strip, VERSION=3, LOGNAME=root, CROSS_COMPILE =, KERNELVERSION=3.16.7-ckt4, _=/usr/bin/strace, O=/usr/src/linux- headers-3.16.0-..., AR=ar, KERNELRELEASE=3.16.0-4-amd64, NOSTDINC_FLAGS= -nostd inc -isyst..., USERNAME=root, AS=as, OBJCOPYFLAGS=, CHECK=sparse, RCS_FIND_IGNORE=\\( -name SCCS -o..., TERM=xterm, AWK=awk, KBUILD_EXTMOD=/u sr/src/acpi-call..., KBUILD_CHECKSRC=0, quiet=quiet_, CFLAGS_KERNEL=, LC_COLLATE=C, KBUILD_SUBDIR_CCFLAGS= , KBUILD_SRC=/usr/src/linux- header... , PATH=/usr/local/sbin:/usr/local/..., KBUILD_AFLAGS_KERNEL=, M=/usr/src /acpi-call-1.1.0, MAKELEVEL=5, KBUILD_AFLAGS=-D__ASSEMBLY__ -m6..., DISPLA Y=:0, KCONFIG_CONFIG=.config, KBUILD_CFLAGS_KERNEL=, obj=/usr/src/acpi- call-1.1.0, UTS_MACHINE=x86_64,
Bug#664574: libgtk2.0-0: amdcccle (fglrx-control) (segfault), reportbug (trap divide error): in libgdk-x11-2.0.so.0.2400.10
Package: libgtk2.0-0 Version: 2.24.10-1 Severity: important Justification: breaks multiple packages Dear Maintainer, While this might look like I am reporting a compound bug here, I believe that both of these failures are tied to libgdk-x11-2.0.so.0.2400.10 which is a part of libgtk2.0-0. amdcccle * What led up to the situation? sudo aptitude update; sudo aptitude safe-upgrade Now on latest in debian testing (wheezy). This ended up breaking lots of things sadly, particulary pulseaudio and plasma-desktop--- but those breakages are (as of yet) unrelated to this issue. Upon restart of X11, fglrx and plasma-desktop were no longer friends, and windows were being rendered behind the plasma desktop background images. (Worked around this issue by asking a shell to stay on top, then removed plasma-desktop preferences.) * What exactly did you do (or not do) that was effective (or ineffective)? 1. Launch amdcccle using: $(kde4-config --path libexec)kdesu /usr/bin/amdcccle (from Kicker under KDE4) 2. Change something. 3. Click Apply. 4. (Result): amdcccle crashes without touching /etc/X11/xorg.conf. Please see the following /var/log/messages and backtrace information from gdb. As it is proprietary, I can't get much more useful information from amdcccle. * What was the outcome of this action? Mar 18 16:20:02 debian kernel: [ 289.161458] amdcccle[4101]: segfault at 114 ip 7f0d2c61b101 sp 7fff561b5f30 error 6 in libgdk-x11-2.0.so.0.2400.10[7f0d2c5c9000+af000] * What outcome did you expect instead? Expected outcome: amdcccle will write configuration changes to /etc/X11/xorg.conf. This does not happen at all. /etc/X11/xorg.conf is untouched. Make some display changes to enable the Apply button in amdcccle. /etc/X11/xorg.conf is not written or touched. root 5895 /usr/bin/amdcccle sudo gdb --pid=5895 snip (gdb) continue Continuing. Program received signal SIGSEGV, Segmentation fault. IA__gdk_display_open (display_name=optimized out) at /tmp/buildd/gtk+2.0-2.24.10/gdk/x11/gdkdisplay-x11.c:173 173 /tmp/buildd/gtk+2.0-2.24.10/gdk/x11/gdkdisplay-x11.c: No such file or directory. (gdb) bt #0 IA__gdk_display_open (display_name=optimized out) at /tmp/buildd/gtk+2.0-2.24.10/gdk/x11/gdkdisplay-x11.c:173 #1 0x005bc356 in ?? () #2 0x00499fb9 in ?? () #3 0x0049da9e in ?? () #4 0x004a1e5f in ?? () #5 0x004b7977 in ?? () #6 0x00425351 in ?? () #7 0x0059f32c in ?? () #8 0x7f27d0fc7eba in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #9 0x7f27d1b1f2c2 in QAbstractButton::clicked(bool) () from /usr/lib/libQtGui.so.4 #10 0x7f27d186734e in ?? () from /usr/lib/libQtGui.so.4 #11 0x7f27d186868b in ?? () from /usr/lib/libQtGui.so.4 #12 0x7f27d18688fc in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /usr/lib/libQtGui.so.4 #13 0x7f27d1505346 in QWidget::event(QEvent*) () from /usr/lib/libQtGui.so.4 #14 0x7f27d14b4c64 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #15 0x7f27d14ba3eb in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #16 0x7f27d0fb528c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #17 0x7f27d14b5c32 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointerQWidget, bool) () from /usr/lib/libQtGui.so.4 #18 0x7f27d1532118 in ?? () from /usr/lib/libQtGui.so.4 #19 0x7f27d1530f1a in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/libQtGui.so.4 #20 0x7f27d1559252 in ?? () from /usr/lib/libQtGui.so.4 #21 0x7f27cdd9d0cf in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x7f27cdd9d8c8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x7f27cdd9da99 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x7f27d0fdfe2f in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #25 0x7f27d1558eee in ?? () from /usr/lib/libQtGui.so.4 #26 0x7f27d0fb4492 in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #27 0x7f27d0fb468f in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #28 0x7f27d0fb8837 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4 #29 0x0041f54a in ?? () #30 0x7f27ce489ead in __libc_start_main (main=optimized out, argc=optimized out, ubp_av=optimized out, init=optimized out, fini=optimized out, rtld_fini=optimized out, stack_end=0x7fff85db2078) at libc-start.c:228 #31 0x0041d02a in ?? () #32 0x7fff85db2078 in ?? () #33 0x001c in ?? () #34 0x0001 in ?? ()
