Bug#772297: linux-kbuild-3.16: bashism in /bin/sh script
Package: linux-kbuild-3.16
Severity: normal
Version: 3.16-2
User: debian-rele...@lists.debian.org
Usertags: goal-dash
Hi,
I've ran checkbashisms (from the 'devscripts' package) over the whole
archive and I found that your package has a /bin/sh script that uses a
bashism.
checkbashisms' output:
possible bashism in ./usr/lib/linux-kbuild-3.16/scripts/setlocalversion
line 87 (should be 'b = a'):
if [ `hg log -r . --template '{latesttagdistance}'` ==
1 ]; then
Not using bash (or a Debian Policy compliant shell interpreter that doesn't
provide such an extra feature) as /bin/sh is likely to lead to errors or
unexpected behaviours. Please be aware that dash is the default /bin/sh.
Please closely examine the above output and the script, and determine
what the proper severity of the bug is, and adjust it accordingly. If
it's important or greater please hurry to get this fixed for jessie.
Hints about how to fix bashisms can be found at:
https://wiki.ubuntu.com/DashAsBinSh
Thanks in advance,
Raphael Geissert
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1506320.D00f8LNljj@eee
Bug#772335: initramfs-tools: bashism in /bin/sh script
Package: initramfs-tools Severity: important Version: 0.118 User: debian-rele...@lists.debian.org Usertags: goal-dash Hi, I've ran checkbashisms (from the 'devscripts' package) over the whole archive and I found that your package has a /bin/sh script that uses a bashism. checkbashisms' output: possible bashism in ./usr/sbin/mkinitramfs line 357 ($UID should be $(id -ru)): [ $UID != 0 ] cpio_owner_root=-R 0:0 blkid -p -n swap $RESUME /dev/null 21; then Not using bash (or a Debian Policy compliant shell interpreter that doesn't provide such an extra feature) as /bin/sh is likely to lead to errors or unexpected behaviours. Please be aware that dash is the default /bin/sh. Please closely examine the above output and the script, and determine what the proper severity of the bug is, and adjust it accordingly. If it's important or greater please hurry to get this fixed for jessie. Hints about how to fix bashisms can be found at: https://wiki.ubuntu.com/DashAsBinSh Thanks in advance, Raphael Geissert -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/4043855.4VoL8qu7yY@eee
Bug#772416: initrd: support booting from chroot
Package: initramfs-tools
Version: 0.109.1
Severity: wishlist
Tags: patch
Hi,
Chroots are pretty neat to maintain different systems side by side
without too much hassle, however once in while you need to boot from one
of them and then you're in trouble (no easy way to do it afaik).
I came up with a script to patch wheezy's initrd and add support for a
'chroot=' boot param. Booting is easy then: just set 'chroot' param and
switch to 'rw':
menuentry Debian Wheezy, (chroot) {
insmod ext2
set root='(hd0,7)'
set chroot='/chroot/wheezy'
linux $chroot/boot/vmlinuz-3.2.0-4-686-pae
root=/dev/sda7 chroot=$chroot rw
initrd $chroot/boot/initrd.img-3.2.0-4-686-pae.chroot
}
It'd be really cool if something like this was supported by initramfs-tools.
Patch and details can be found here:
https://github.com/lemonsqueeze/boot_chroot
https://github.com/lemonsqueeze/boot_chroot/blob/master/initrd.patch
Cheers
--
lemonsqueeze
-- Package-specific info:
-- /etc/initramfs-tools/initramfs.conf
MODULES=most
BUSYBOX=y
COMPCACHE_SIZE=
BOOT=local
DEVICE=eth0
NFSROOT=auto
-- no debconf information
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/54832576.4040...@gmx.com
Bug#767742: linux-image-3.16.0-4-amd64: screen flickering with ATI Radeon X1600
Package: src:linux Version: 3.16.7-2 Followup-For: Bug #767742 Hi It appears that this problem affects multiple graphic cards that depend on the 'radeon' kernel module. Using 'nomodesetting' is not an option because the resolution gets too small (1024x768). On this laptop I still use the last 3.14.x kernel to be usable. Please include the proposed patch in Debian 8.0. Thanks -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: Hewlett-Packard product_name: HP Compaq nw8440 (RH415EA#ABB) product_version: F.16 chassis_vendor: Hewlett-Packard chassis_version: bios_vendor: Hewlett-Packard bios_version: 68YVD Ver. F.16 board_vendor: Hewlett-Packard board_name: 30A3 board_version: KBC Version 40.19 ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub [8086:27a0] (rev 03) Subsystem: Hewlett-Packard Company Compaq nw8440 [103c:30a3] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- INTx- Latency: 0 Capabilities: access denied 00:01.0 PCI bridge [0604]: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express PCI Express Root Port [8086:27a1] (rev 03) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: 4000-4fff Memory behind bridge: f460-f46f Prefetchable memory behind bridge: e000-efff Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: access denied Kernel driver in use: pcieport 00:1b.0 Audio device [0403]: Intel Corporation NM10/ICH7 Family High Definition Audio Controller [8086:27d8] (rev 01) Subsystem: Hewlett-Packard Company Compaq nw8440 [103c:30a3] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 45 Region 0: Memory at f470 (64-bit, non-prefetchable) [size=16K] Capabilities: access denied Kernel driver in use: snd_hda_intel 00:1c.0 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express Port 1 [8086:27d0] (rev 01) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Bus: primary=00, secondary=08, subordinate=08, sec-latency=0 I/O behind bridge: 6000-6fff Memory behind bridge: f410-f41f Prefetchable memory behind bridge: c400-c41f Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: access denied Kernel driver in use: pcieport 00:1c.1 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express Port 2 [8086:27d2] (rev 01) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Bus: primary=00, secondary=10, subordinate=10, sec-latency=0 I/O behind bridge: 7000-7fff Memory behind bridge: f400-f40f Prefetchable memory behind bridge: c420-c43f Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: access denied Kernel driver in use: pcieport 00:1c.3 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express Port 4 [8086:27d6] (rev 01) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Bug#772416: initrd: support booting from chroot
On Sat, Dec 06, 2014 at 04:49:10PM +0100, lemonsqueeze wrote: Patch and details can be found here: https://github.com/lemonsqueeze/boot_chroot https://github.com/lemonsqueeze/boot_chroot/blob/master/initrd.patch $ wget https://github.com/lemonsqueeze/boot_chroot/blob/master/initrd.patch --2014-12-06 17:39:48-- https://github.com/lemonsqueeze/boot_chroot/blob/master/initrd.patch Resolving github.com (github.com)... 192.30.252.130 Connecting to github.com (github.com)|192.30.252.130|:443... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/html] Saving to: 'initrd.patch' [ = ] 36,652 167KB/s in 0.2s 2014-12-06 17:39:49 (167 KB/s) - 'initrd.patch' saved [36652] $ file initrd.patch initrd.patch: HTML document, UTF-8 Unicode text, with very long lines $ :-( Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141206164402.gr3...@gpm.stappers.nl
Bug#772416: initrd: support booting from chroot
On Sat, Dec 06, 2014 at 05:44:02PM +0100, Geert Stappers wrote:
On Sat, Dec 06, 2014 at 04:49:10PM +0100, lemonsqueeze wrote:
Patch and details can be found here:
https://github.com/lemonsqueeze/boot_chroot
https://github.com/lemonsqueeze/boot_chroot/blob/master/initrd.patch
$ wget https://github.com/lemonsqueeze/boot_chroot/blob/master/initrd.patch
Length: unspecified [text/html]
Real patch is
https://raw.githubusercontent.com/lemonsqueeze/boot_chroot/master/initrd.patch
Here inline (and also attached)
diff -Nru orig/init new/init
--- orig/init 2014-12-04 11:42:27.0 +0100
+++ new/init2014-12-04 17:24:18.0 +0100
@@ -149,6 +149,9 @@
ip=*)
IP=${x#ip=}
;;
+ chroot=*)
+ CHROOT=${x#chroot=}
+ ;;
boot=*)
BOOT=${x#boot=}
;;
diff -Nru orig/scripts/local new/scripts/local
--- orig/scripts/local 2014-12-04 11:42:27.0 +0100
+++ new/scripts/local 2014-12-04 11:45:23.0 +0100
@@ -150,6 +150,37 @@
fi
fi
+ if [ $CHROOT ]; then
+ if [ $mountroot_status != 0 ]; then
+ if [ ${FSTYPE} = ntfs ] || [ ${FSTYPE} = vfat ]; then
+ panic
+Could not mount the partition ${ROOT}.
+This could also happen if the file system is not clean because of an operating
+system crash, an interrupted boot process, an improper shutdown, or unplugging
+of a removable device without first unmounting or ejecting it. To fix this,
+simply reboot into Windows, let it fully start, log in, run 'chkdsk /r', then
+gracefully shut down and reboot back into Windows. After this you should be
+able to reboot again and resume the installation.
+(filesystem = ${FSTYPE}, error code = $mountroot_status)
+
+ fi
+ fi
+
+ mkdir -p /host
+ mount -o move ${rootmnt} /host
+
+ if [ ! -d /host/${CHROOT} ]; then
+ panic ALERT! /host/${CHROOT} does not exist.
Dropping to a shell!
+ fi
+
+ # FIXME This has no error checking
+ mount --bind /host/${CHROOT} ${rootmnt}
+
+ if [ -d ${rootmnt}/host ]; then
+ mount -o move /host ${rootmnt}/host
+ fi
+ fi
+
[ $quiet != y ] log_begin_msg Running /scripts/local-bottom
run_scripts /scripts/local-bottom
[ $quiet != y ] log_end_msg
Thanks for the patch
Groeten
Geert Stappers
--
Leven en laten leven
diff -Nru orig/init new/init
--- orig/init 2014-12-04 11:42:27.0 +0100
+++ new/init 2014-12-04 17:24:18.0 +0100
@@ -149,6 +149,9 @@
ip=*)
IP=${x#ip=}
;;
+ chroot=*)
+ CHROOT=${x#chroot=}
+ ;;
boot=*)
BOOT=${x#boot=}
;;
diff -Nru orig/scripts/local new/scripts/local
--- orig/scripts/local 2014-12-04 11:42:27.0 +0100
+++ new/scripts/local 2014-12-04 11:45:23.0 +0100
@@ -150,6 +150,37 @@
fi
fi
+ if [ $CHROOT ]; then
+ if [ $mountroot_status != 0 ]; then
+ if [ ${FSTYPE} = ntfs ] || [ ${FSTYPE} = vfat ]; then
+panic
+Could not mount the partition ${ROOT}.
+This could also happen if the file system is not clean because of an operating
+system crash, an interrupted boot process, an improper shutdown, or unplugging
+of a removable device without first unmounting or ejecting it. To fix this,
+simply reboot into Windows, let it fully start, log in, run 'chkdsk /r', then
+gracefully shut down and reboot back into Windows. After this you should be
+able to reboot again and resume the installation.
+(filesystem = ${FSTYPE}, error code = $mountroot_status)
+
+ fi
+ fi
+
+ mkdir -p /host
+ mount -o move ${rootmnt} /host
+
+ if [ ! -d /host/${CHROOT} ]; then
+ panic ALERT! /host/${CHROOT} does not exist. Dropping to a shell!
+ fi
+
+ # FIXME This has no error checking
+ mount --bind /host/${CHROOT} ${rootmnt}
+
+ if [ -d ${rootmnt}/host ]; then
+ mount -o move /host ${rootmnt}/host
+ fi
+ fi
+
[ $quiet != y ] log_begin_msg Running /scripts/local-bottom
run_scripts /scripts/local-bottom
[ $quiet != y ] log_end_msg
Re: [CVE-2014-9090] x86_64, traps: Stop using IST for #SS
Hi Luis, On Fri, Dec 05, 2014 at 03:21:01PM +, Luis Henriques wrote: Your backport of commit 6f442be2fb22 (x86_64, traps: Stop using IST for #SS) seems to be identical to mine, but I'm unable to confirm that it is sufficient to fix the security issue. If that can help, I just found that this public test code from Andy is sufficient to test the backports : https://gitorious.org/linux-test-utils/linux-clock-tests/raw/sigreturn.c On a plain 2.6.32.64 (x86_64), running the code above built with -m32 kills the kernel, probably from a triple fault since I'm not seeing any panic message and it immediately reboots : $ /tmp/sigreturn [RUN] = reboot On the patched kernel : $ /tmp/sigreturn [RUN] 64-bit CS (33), 32-bit SS (2b) SP: 5aadc0de - 5aadc0de [OK]all registers okay [RUN] 32-bit CS (23), 32-bit SS (2b) SP: 5aadc0de - 5aadc0de [OK]all registers okay [RUN] 16-bit CS (7), 32-bit SS (2b) SP: 5aadc0de - 5aadc0de [OK]all registers okay [RUN] 64-bit CS (33), 16-bit SS (f) SP: 5aadc0de - 5aadc0de [OK]all registers okay [RUN] 32-bit CS (23), 16-bit SS (f) SP: 5aadc0de - 5aadc0de [OK]all registers okay [RUN] 16-bit CS (7), 16-bit SS (f) SP: 5aadc0de - 5aadc0de [OK]all registers okay [RUN] 64-bit CS (33), bogus SS (17) [OK]Got #GP(0x0) (i.e. Segmentation fault) [RUN] 32-bit CS (23), bogus SS (17) [OK]Got #GP(0x0) (i.e. Segmentation fault) [RUN] 16-bit CS (7), bogus SS (17) [OK]Got #GP(0x0) (i.e. Segmentation fault) [RUN] 64-bit CS (33), bogus SS (23) [OK]Got #GP(0x20) (i.e. GDT index 4, Segmentation fault) [RUN] 32-bit CS (23), bogus SS (23) [OK]Got #GP(0x20) (i.e. GDT index 4, Segmentation fault) [RUN] 16-bit CS (7), bogus SS (23) [OK]Got #GP(0x20) (i.e. GDT index 4, Segmentation fault) [RUN] 32-bit CS (1f), bogus SS (2b) [OK]Got #NP(0x1c) (i.e. LDT index 3, Bus error) [RUN] 32-bit CS (23), bogus SS (27) [OK]Got #GP(0x0) (i.e. Segmentation fault) $ Hoping this helps. BTW, I'm about to issue -rc1 which includes the last series of patches as well as the other CVE fixes that you and Moritz sent me. Best regards, Willy -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141206171308.ga3...@1wt.eu
Bug#772435: slow SSD performance with Apple PCIe SSD on MBP 11.2
Package: src:linux Version: 3.16.7-2 Severity: normal Tags: patch Hi, i have very bad disk IO performance on my MacBook Pro 11.2 with a Samsung PCIe SSD. This seems to be kernel issue https://bugzilla.kernel.org/show_bug.cgi?id=60731 Installing libreoffice on my MBP takes around 5 minutes without below settings. http://article.gmane.org/gmane.linux.ide/58740 respectivly setting device_nomsi=0x1600144d as kernel command line seems to solve the issue for me. It would be nice to include above patch into jessie kernel. Cheers, Martin -- Package-specific info: ** Version: Linux version 3.16.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.8.3 (Debian 4.8.3-13) ) #1 SMP Debian 3.16.7-2 (2014-11-06) ** Command line: BOOT_IMAGE=/vmlinuz-3.16.0-4-amd64 root=/dev/mapper/vg0-slash ro device_nomsi=0x1600144d quiet ** Tainted: PO (4097) * Proprietary module has been loaded. * Out-of-tree module has been loaded. ** Kernel log: [ 12.540700] [drm] Initialized drm 1.1.0 20060810 [ 12.543104] mei_me :00:16.0: irq 50 for MSI/MSI-X [ 12.549336] snd_hda_intel :00:1b.0: irq 51 for MSI/MSI-X [ 12.560707] [drm] Found 128MB of eLLC [ 12.560733] [drm] Memory usable by graphics device = 2048M [ 12.560734] [drm] Replacing VGA console driver [ 12.560737] checking generic (9000 1437000) vs hw (9000 1000) [ 12.560738] fb: switching to inteldrmfb from simple [ 12.560761] Console: switching to colour dummy device 80x25 [ 12.567558] EFI Variables Facility v0.08 2004-May-17 [ 12.572921] input: PC Speaker as /devices/platform/pcspkr/input/input7 [ 12.573128] sound hdaudioC1D0: autoconfig: line_outs=2 (0x12/0x13/0x0/0x0/0x0) type:speaker [ 12.573131] sound hdaudioC1D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 12.573132] sound hdaudioC1D0:hp_outs=1 (0x10/0x0/0x0/0x0/0x0) [ 12.573133] sound hdaudioC1D0:mono: mono_out=0x0 [ 12.573134] sound hdaudioC1D0:dig-out=0x21/0x0 [ 12.573135] sound hdaudioC1D0:inputs: [ 12.573136] sound hdaudioC1D0: Internal Mic=0x1c [ 12.573137] sound hdaudioC1D0: Mic=0x18 [ 12.575135] i915 :00:02.0: irq 52 for MSI/MSI-X [ 12.575148] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 12.575149] [drm] Driver supports precise vblank timestamp query. [ 12.575215] vgaarb: device changed decodes: PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [ 12.577862] input: HDA Intel PCH Mic as /devices/pci:00/:00:1b.0/sound/card1/input8 [ 12.577894] input: HDA Intel PCH Headphone as /devices/pci:00/:00:1b.0/sound/card1/input9 [ 12.577923] input: HDA Intel PCH SPDIF as /devices/pci:00/:00:1b.0/sound/card1/input10 [ 12.638593] apple_gmux: gmux device not present [ 12.643893] ACPI: Battery Slot [BAT0] (battery present) [ 12.650006] iTCO_vendor_support: vendor-support=0 [ 12.695637] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11 [ 12.695674] iTCO_wdt: unable to reset NO_REBOOT flag, device disabled by hardware/BIOS [ 12.711987] applesmc: key=599 fan=2 temp=37 index=36 acc=0 lux=2 kbd=1 [ 12.723111] input: bcm5974 as /devices/pci:00/:00:14.0/usb1/1-12/1-12:1.2/input/input11 [ 12.723151] cfg80211: Calling CRDA to update world regulatory domain [ 12.723207] usbcore: registered new interface driver bcm5974 [ 12.749985] wl: module license 'MIXED/Proprietary' taints kernel. [ 12.749989] Disabling lock debugging due to kernel taint [ 12.815015] wl :02:00.0: enabling device ( - 0002) [ 12.843457] wlan0: Broadcom BCM43a0 802.11 Hybrid Wireless Controller 6.30.223.248 (r487574) [ 12.846362] Adding 7811068k swap on /dev/mapper/vg0-swap. Priority:-1 extents:1 across:7811068k SSFS [ 12.854518] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null) [ 12.860998] pstore: Registered efi as persistent store backend [ 12.869544] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null) [ 12.874588] [drm] VBT doesn't support DRRS [ 12.934299] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null) [ 12.937283] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null) [ 13.018962] [drm] GMBUS [i915 gmbus vga] timed out, falling back to bit banging on pin 2 [ 13.037502] fbcon: inteldrmfb (fb0) is primary device [ 13.651695] Bluetooth: Core ver 2.19 [ 13.651703] NET: Registered protocol family 31 [ 13.651703] Bluetooth: HCI device and connection manager initialized [ 13.651708] Bluetooth: HCI socket layer initialized [ 13.651709] Bluetooth: L2CAP socket layer initialized [ 13.651714] Bluetooth: SCO socket layer initialized [ 13.655422] usbcore: registered new interface driver btusb [ 13.666177] usb 1-8.1: USB disconnect, device number 4 [ 13.923136] usb 1-8.2: USB disconnect, device number 5 [ 14.366571] Console: switching to colour frame buffer device 360x112 [ 14.380207] i915 :00:02.0: fb0: inteldrmfb frame buffer device [
Bug#772297: marked as done (linux-kbuild-3.16: bashism in /bin/sh script)
Your message dated Sun, 07 Dec 2014 01:36:37 +
with message-id 1417916197.11886.18.ca...@decadent.org.uk
and subject line Re: Bug#772297: linux-kbuild-3.16: bashism in /bin/sh script
has caused the Debian Bug report #772297,
regarding linux-kbuild-3.16: bashism in /bin/sh script
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.)
--
772297: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772297
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-kbuild-3.16
Severity: normal
Version: 3.16-2
User: debian-rele...@lists.debian.org
Usertags: goal-dash
Hi,
I've ran checkbashisms (from the 'devscripts' package) over the whole
archive and I found that your package has a /bin/sh script that uses a
bashism.
checkbashisms' output:
possible bashism in ./usr/lib/linux-kbuild-3.16/scripts/setlocalversion
line 87 (should be 'b = a'):
if [ `hg log -r . --template '{latesttagdistance}'` ==
1 ]; then
Not using bash (or a Debian Policy compliant shell interpreter that doesn't
provide such an extra feature) as /bin/sh is likely to lead to errors or
unexpected behaviours. Please be aware that dash is the default /bin/sh.
Please closely examine the above output and the script, and determine
what the proper severity of the bug is, and adjust it accordingly. If
it's important or greater please hurry to get this fixed for jessie.
Hints about how to fix bashisms can be found at:
https://wiki.ubuntu.com/DashAsBinSh
Thanks in advance,
Raphael Geissert
---End Message---
---BeginMessage---
On Sat, 2014-12-06 at 14:18 +0100, Raphael Geissert wrote:
Package: linux-kbuild-3.16
Severity: normal
Version: 3.16-2
User: debian-rele...@lists.debian.org
Usertags: goal-dash
Hi,
I've ran checkbashisms (from the 'devscripts' package) over the whole
archive and I found that your package has a /bin/sh script that uses a
bashism.
checkbashisms' output:
possible bashism in ./usr/lib/linux-kbuild-3.16/scripts/setlocalversion
line 87 (should be 'b = a'):
if [ `hg log -r . --template '{latesttagdistance}'` ==
1 ]; then
Not using bash (or a Debian Policy compliant shell interpreter that doesn't
provide such an extra feature) as /bin/sh is likely to lead to errors or
unexpected behaviours. Please be aware that dash is the default /bin/sh.
Please closely examine the above output and the script, and determine
what the proper severity of the bug is, and adjust it accordingly. If
it's important or greater please hurry to get this fixed for jessie.
Hints about how to fix bashisms can be found at:
https://wiki.ubuntu.com/DashAsBinSh
This code will only run when building a kernel from a branch maintained
in a Mercurial repository. As this package is only used to build
external modules, the code is not used and this bug does not matter.
Ben.
--
Ben Hutchings
Experience is directly proportional to the value of equipment destroyed.
- Carolyn Scheppner
signature.asc
Description: This is a digitally signed message part
---End Message---
Re: Proper way for vendors to build deb packages of kernels.
On Sat, Dec 6, 2014 at 8:24 AM, peter green wrote: Does anyone have any other suggestions on what the best way for a vendor to take a kernel source tree (not debian derived) and produce deb packages and a debian source package from it? Personally, I think the most useful way to do this would be to get the needed code/drivers/devicetree into Linux mainline, get that into Debian backports (or experimental during the freeze) and then build that version of Linux for Raspbian. -- bye, pabs https://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/caktje6gpy6qmqhi0suxgkrwt9uejaqr5ms3sggktfis5yrp...@mail.gmail.com
Processed: linux-image-3.16.0-4-amd64: Built-in display dimmed black if external monitor is plugged in
Processing control commands: notfound -1 3.14.15-2 Bug #772440 [src:linux] linux-image-3.16.0-4-amd64: Built-in display dimmed black if external monitor is plugged in Ignoring request to alter found versions of bug #772440 to the same values previously set found -13.16.3-2 Bug #772440 [src:linux] linux-image-3.16.0-4-amd64: Built-in display dimmed black if external monitor is plugged in Marked as found in versions linux/3.16.3-2. found -13.16.5-1 Bug #772440 [src:linux] linux-image-3.16.0-4-amd64: Built-in display dimmed black if external monitor is plugged in Marked as found in versions linux/3.16.5-1. -- 772440: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772440 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b.141792226823264.transcr...@bugs.debian.org
Bug#772440: linux-image-3.16.0-4-amd64: Built-in display dimmed black if external monitor is plugged in
Package: src:linux Version: 3.16.7-2 Severity: normal Control: notfound -1 3.14.15-2 Control: found -13.16.3-2 Control: found -13.16.5-1 Hi, most times my laptop screen (LVDS1) is completely dimmed (= black) after boot at the GDM login prompt, if the external monitor (HDMI1) is or gets plugged in. Trying to increase the brightness (Fn+F3) shows the brightness OSD on HDMI1, but the bar only moves up to about max. 5% (= which is still a black screen). Thus the GDM login prompt (which is placed on LVDS1) is not visible, while HDMI1 works but has no content to display. Switching to tty1 and back fixes the brightness level (= normal LVDS1 with visible login prompt). But it still can't be regulated below about 95% then. After login in Gnome brightness can be regulated again. With linux 3.14 brightness is up and regulatable. With linux 3.17 (3.17.4-1~exp1) it is up, but not regulatable. It may have happened less often with earlier 3.16 versions. Without an external monitor brightness is up and regulatable on the internal display. It happens indepently if I enable or disable the built-in display in Gnome before rebooting. (Normally I have turned it off. In the past it was also turned off then at the login prompt. But I guess this is an unrelated Gnome issue which just made me realize this at all.) Due to bug #762809 in libgl1-mesa-dri I have enabled SNA for my Intel graphics HD4000. But returning to the default does not help here. There are error messages shown on tty before login. But I get them always, independently if the screen is dark or not, and also with linux 3.17. So I don't know if this is related. (And a web search shows there is much noise around them.): ~ kernel: [2.352424] [drm:cpt_set_fifo_underrun_reporting] *ERROR* uncleared pch fifo underrun on pch transcoder A kernel: [2.352425] [drm:cpt_serr_int_handler] *ERROR* PCH transcoder A FIFO underrun ~ Should I file a bug about not being able to regulate the brightness level upstream and/or clone the bug here? Any more information? If I should bisect: against old good 3.14.15 or 3.14.17? Any tips beyond https://wiki.debian.org/DebianKernel/GitBisect? May I restrict the bisect to a certain dir/path? Thanks in advance and for all your work jre -- Package-specific info: ** Version: Linux version 3.16.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.8.3 (Debian 4.8.3-13) ) #1 SMP Debian 3.16.7-2 (2014-11-06) ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 root=UUID=6703b530-7dd3-4ce0-8986-05b1af26806d ro quiet ** Not tainted ** Kernel log: [2.288866] usb 3-2: Product: 4-Port USB 3.0 Hub [2.288868] usb 3-2: Manufacturer: VIA Labs, Inc. [2.292140] hub 3-2:1.0: USB hub found [2.343978] hub 3-2:1.0: 4 ports detected [2.436579] usb 1-1.5: new full-speed USB device number 3 using ehci-pci [2.457558] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x361f00) [2.473082] psmouse serio1: elantech: Synaptics capabilities query result 0x41, 0x15, 0x0f. [2.533452] usb 1-1.5: New USB device found, idVendor=8087, idProduct=07da [2.533457] usb 1-1.5: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [2.550045] Bluetooth: Core ver 2.19 [2.550069] NET: Registered protocol family 31 [2.550070] Bluetooth: HCI device and connection manager initialized [2.550079] Bluetooth: HCI socket layer initialized [2.550082] Bluetooth: L2CAP socket layer initialized [2.550097] Bluetooth: SCO socket layer initialized [2.556570] input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input6 [2.558149] usbcore: registered new interface driver btusb [2.604542] usb 1-1.6: new high-speed USB device number 4 using ehci-pci [2.659933] Console: switching to colour frame buffer device 200x56 [2.667755] i915 :00:02.0: fb0: inteldrmfb frame buffer device [2.667757] i915 :00:02.0: registered panic notifier [2.684108] random: nonblocking pool is initialized [2.689485] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) [2.689631] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input10 [2.689713] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 [2.689994] ACPI Warning: SystemIO range 0xefa0-0xefbf conflicts with OpRegion 0xefa0-0xefaf (\_SB_.PCI0.SBUS.SMBI) (20140424/utaddress-258) [2.69] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [2.707941] RPC: Registered named UNIX socket transport module. [2.707941] RPC: Registered udp transport module. [2.707941] RPC: Registered tcp transport module. [2.707942] RPC: Registered tcp NFSv4.1 backchannel transport module. [2.710448] FS-Cache: Loaded [2.717183] FS-Cache: Netfs 'nfs' registered for caching [2.723645] Installing knfsd (copyright
