Bug#925555: linux-image-4.19.0-4-amd64: [regression] No graphics on some IvyBridge / Haswell systems
Control: forcemerge -1 926193 Control: tags -1 upstream patch Control: retitle -1 linux-image-4.19.0-4-amd64: [regression] No graphics on some IvyBridge / Haswell systems Control: forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=109806 (Summary of the merged bugs - I haven't tried any of this myself) Workaround for individuals (from leandroembu) - install xserver-xorg-video-intel and copy /usr/share/doc/xserver-xorg-video-intel/xorg.conf to /etc/X11. This is probably not suitable as an official fix as it may cause problems on newer hardware (e.g. #860133). Possible patch: revert drm/i915/fbdev: Actually configure untiled displays (d179b88deb3bf6fed4991a31fd6f0f2cad21fab5). Has been applied upstream, but the real bug is thought to be in xorg not linux.
Bug#783208: linux-image-3.16.0-4-amd64: USB mouse randomly stops working
Package: src:linux Version: 3.16.7-ckt9-2 Severity: normal Dear Maintainer, My USB mouse intermittently stops working (pointer not responding to it, but responding normally to the internal trackpad); this has been happening for at least 1-2 months (possibly since install), but has been unusually frequent for the last few days. When not working, the mouse continues to appear in lsusb and /dev/bus/usb, but sudo cat /dev/input/mouse0 gives nothing; nothing appears in kern.log. It can be made to work again by a suspend/resume or hibernate/resume cycle, or by physically disconnecting and reconnecting it. Unlike #780923, it only ever affects the mouse, not the (also USB) keyboard. Boot messages for this device: Apr 20 20:01:10 rnpalmer-laptop kernel: [3.212600] usb 3-2: new low-speed USB device number 3 using xhci_hcd Apr 20 20:01:10 rnpalmer-laptop kernel: [3.380727] usb 3-2: device descriptor read/64, error -71 Apr 20 20:01:10 rnpalmer-laptop kernel: [3.616509] usb 3-2: New USB device found, idVendor=13ee, idProduct=0001 Apr 20 20:01:10 rnpalmer-laptop kernel: [3.616515] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Apr 20 20:01:10 rnpalmer-laptop kernel: [3.616518] usb 3-2: Product: AND Apr 20 20:01:10 rnpalmer-laptop kernel: [3.616521] usb 3-2: Manufacturer: MOON Apr 20 20:01:10 rnpalmer-laptop kernel: [3.616524] usb 3-2: SerialNumber: @ɌAB Apr 20 20:01:10 rnpalmer-laptop kernel: [3.616790] usb 3-2: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes Apr 20 20:01:10 rnpalmer-laptop kernel: [3.619421] input: MOON AND as /devices/pci:00/:00:14.0/usb3/3-2/3-2:1.0/0003:13EE:0001.0003/input/input7 Apr 20 20:01:10 rnpalmer-laptop kernel: [3.619602] hid-generic 0003:13EE:0001.0003: input,hidraw2: USB HID v1.00 Mouse [MOON AND ] on usb-:00:14.0-2/input0 $ sudo lsusb -d 13ee:0001 -v Bus 003 Device 003: ID 13ee:0001 MosArt Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x13ee MosArt idProduct 0x0001 bcdDevice0.10 iManufacturer 1 MOON iProduct2 AND iSerial 3 @ɌAB bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 34 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 2 Mouse iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.00 bCountryCode0 Not supported bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 52 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 10 Device Status: 0x (Bus Powered) rnpalmer@rnpalmer-laptop:~$ -- Package-specific info: ** Version: Linux version 3.16.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt9-2 (2015-04-13) ** Command line: BOOT_IMAGE=/vmlinuz-3.16.0-4-amd64 root=UUID=1ebca590-0a18-44f5-8d75-f96f5ca7c36e ro quiet ** Not tainted ** Kernel log: [ 629.323176] ehci-pci :00:1a.0: using default PCI settings [ 629.323189] snd_hda_intel :00:1b.0: no hotplug settings from platform [ 629.323196] pcieport :00:1c.0: no hotplug settings from platform [ 629.323202] pcieport :00:1c.1: no hotplug settings from platform [ 629.323266] ath9k :02:00.0: no hotplug settings from platform [ 629.323273] pcieport :00:1c.2: no hotplug settings from platform [ 629.323291] alx :03:00.0: no hotplug settings from platform [ 629.323297] ehci-pci :00:1d.0: no hotplug settings from platform [ 629.323300] ehci-pci :00:1d.0: using default PCI settings [ 629.323315] lpc_ich :00:1f.0: no hotplug settings from platform [ 629.323318] lpc_ich :00:1f.0: using default
Bug#767148: linux-image-3.16-3-amd64: OpenCL doesn't work on Intel GPU
Package: src:linux Version: 3.16.5-1 Severity: important Control: affects -1 beignet Control: tags -1 fixed-upstream X-Debbugs-CC: s...@debian.org,pkg-opencl-de...@lists.alioth.debian.org In current jessie, beignet (OpenCL for Intel GPUs, 0.8-1.1) is non-functional: $ sudo apt-get install beignet python3-pyopencl $ python3 beignet_test.py python3: /tmp/buildd/beignet-0.8/src/intel/intel_gpgpu.c:427: intel_gpgpu_check_binded_buf_address: Assertion `gpgpu-binded_buf[i]-offset != 0' failed. Aborted It had previously worked in Ubuntu 14.04 (beignet 0.8-1, linux 3.13.0) on the same hardware (i5-3230M). (beignet isn't in Wheezy.) beignet's upstream documentation [0] says this is a known issue with 3.15/3.16 kernels and suggested the workaround $ sudo sh -c echo -n 0 /sys/module/i915/parameters/enable_cmd_parser which made it work, but the description [1] suggests this will break some OpenGL functionality and might be a security risk. This is fixed upstream by [2]; I haven't yet tried this. [0] http://www.freedesktop.org/wiki/Software/Beignet/ [1] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/i915_cmd_parser.c [2] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/i915/i915_cmd_parser.c?id=c9224faa59c3071ecfa2d4b24592f4eb61e57069 -- Package-specific info: ** Version: Linux version 3.16-3-amd64 (debian-kernel@lists.debian.org) (gcc version 4.8.3 (Debian 4.8.3-12) ) #1 SMP Debian 3.16.5-1 (2014-10-10) ** Command line: BOOT_IMAGE=/vmlinuz-3.16-3-amd64 root=UUID=1ebca590-0a18-44f5-8d75-f96f5ca7c36e ro quiet ** Not tainted ** Kernel log: [ 27.077954] ACPI Warning: SystemIO range 0x0530-0x053f conflicts with OpRegion 0x0500-0x057f (\GPXX) (20140424/utaddress-258) [ 27.077959] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 27.077961] ACPI Warning: SystemIO range 0x0500-0x052f conflicts with OpRegion 0x0500-0x0563 (\GPIO) (20140424/utaddress-258) [ 27.077965] ACPI Warning: SystemIO range 0x0500-0x052f conflicts with OpRegion 0x0500-0x057f (\GPXX) (20140424/utaddress-258) [ 27.077970] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 27.077972] lpc_ich: Resource conflict(s) found affecting gpio_ich [ 27.248942] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [ 27.284399] toshiba_bluetooth: Detected Toshiba ACPI Bluetooth device - installing RFKill handler [ 27.284453] toshiba_bluetooth: Re-enabling Toshiba Bluetooth [ 27.502477] [drm] Memory usable by graphics device = 2048M [ 27.502492] [drm] Replacing VGA console driver [ 27.502508] checking generic (b000 408000) vs hw (b000 1000) [ 27.502512] fb: switching to inteldrmfb from simple [ 27.502568] Console: switching to colour dummy device 80x25 [ 27.524376] i915 :00:02.0: irq 43 for MSI/MSI-X [ 27.524393] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 27.524394] [drm] Driver supports precise vblank timestamp query. [ 27.524506] vgaarb: device changed decodes: PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [ 27.565932] fbcon: inteldrmfb (fb0) is primary device [ 27.582152] wmi: Mapper loaded [ 27.694480] Bluetooth: Core ver 2.19 [ 27.694494] NET: Registered protocol family 31 [ 27.694495] Bluetooth: HCI device and connection manager initialized [ 27.694501] Bluetooth: HCI socket layer initialized [ 27.694502] Bluetooth: L2CAP socket layer initialized [ 27.694509] Bluetooth: SCO socket layer initialized [ 27.833463] usbcore: registered new interface driver btusb [ 27.907603] cfg80211: Calling CRDA to update world regulatory domain [ 27.951039] EFI Variables Facility v0.08 2004-May-17 [ 27.959345] pstore: Registered efi as persistent store backend [ 28.248411] atkbd serio0: Unknown key released (translated set 2, code 0x7c on isa0060/serio0). [ 28.248413] atkbd serio0: Use 'setkeycodes 7c keycode' to make it known. [ 28.279982] input: PC Speaker as /devices/platform/pcspkr/input/input14 [ 28.377421] Console: switching to colour frame buffer device 170x48 [ 28.380569] i915 :00:02.0: fb0: inteldrmfb frame buffer device [ 28.380570] i915 :00:02.0: registered panic notifier [ 28.401883] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) [ 28.401985] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input15 [ 28.402061] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 [ 28.402441] snd_hda_intel :00:1b.0: irq 44 for MSI/MSI-X [ 28.421461] ath: phy0: ASPM enabled: 0x43 [ 28.421465] ath: EEPROM regdomain: 0x6a [ 28.421466] ath: EEPROM indicates we should expect a direct regpair map [
Bug#748070: sorry
Reinstalled system, confirming that the new kernel works when installed properly. Added sync call to rc.local. -- 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/5373ad16.1010...@bham.ac.uk
Bug#748070:
I don't think that sync should be needed, as dpkg already syncs all the files it writes Including maintainer scripts/triggers, or only unpacking? Does sync work if it doesn't know the cache mode (I get No Caching mode page found/Assuming drive cache: write through from sd on each boot)? If you're sure that dpkg was no longer running at the point you rebooted, I was at the login prompt: does sysvinit wait for rc.local to finish before displaying that? -- 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/5373e8d3.7070...@bham.ac.uk
Bug#748070: linux-image-3.2.0-4-amd64: moddep file not found
Package: linux-image-3.2.0-4-amd64 Version: 3.2.57-3+deb7u1 Control: fixed -1 3.2.57-3 On seeing that the apt-get upgrade in my rc.local script had installed this security update (and nothing else), I rebooted with Alt+SysRq+b rather than waste time logging in and immediately rebooting (in hindsight possibly a bad idea, but /var/log/dpkg.log says the install was completed). During boot, an error message appeared that a moddep file wasn't found (I can't give you the exact wording because it didn't go to kern.log), and the system came up without wifi (brcm80211) and with wider-than-normal console text (lack of framebuffer? nouveau/nvd9). I attempted to fix this by running update-initramfs -u, but this made things worse, dropping to an initramfs shell with Gave up waiting for root device and ALERT! /dev/disk/by-uuid/[...] does not exist. (This system uses EFI boot.) -- 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/53729026.9090...@bham.ac.uk
