Bug#1068356: linux-image-6.1.0-18-amd64: it's working as expected - please delete this bug report

Package: src:linux Followup-For: Bug #1068356 X-Debbugs-Cc: vek.m1...@gmail.com Please ignore this bug report - it's working as expected and isn't a bug

Bug#1068356: linux-image-6.1.0-18-amd64: Debian 12.5 6.1.0-18-amd64 hibernate works the 1st time then "no space left on device" in journalctl

Package: src:linux Version: 6.1.76-1 Severity: important X-Debbugs-Cc: vek.m1...@gmail.com Dear Maintainer, * What led up to the situation? doing systemctl hibernate led to the issue * What exactly did you do (or not do) that was effective (or ineffective)? the swap space in the

Bug#1040416: linux-image-6.1.0-9-amd64: Under heavy load Debian V12 and V11 causes data corruption on XFS filesystems.

Hi On Tue, Nov 07, 2023 at 08:33:58PM +0100, Diederik de Haas wrote: > Control: found -1 6.1~rc3-1~exp1 > Control: found -1 6.1.55-1 > > On Saturday, 4 November 2023 20:35:43 CET Jose M Calhariz wrote: > > > Ok. Please test (when you have time) 6.1.55-1. > > > >

Bug#1040416: linux-image-6.1.0-9-amd64: Under heavy load Debian V12 and V11 causes data corruption on XFS filesystems.

Hi On Thu, Nov 02, 2023 at 07:40:38PM +0100, Diederik de Haas wrote: > > On Thursday, 2 November 2023 18:03:25 CET Jose M Calhariz wrote: > > On Thu, Nov 02, 2023 at 03:37:39PM +0100, Diederik de Haas wrote: > > > On Wednesday, 5 July 2023 19:07:15 CET Jose M Calhariz w

Bug#1032391: Under heavy load Debian V12 and V11 causes data corruption on XFS filesystems.

Hi, After some research it was found the problem was not HW related, but related with XFS driver and is present until linux 6.1. So I opened new bug report on https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040416 Kind regards Jose M Calhariz -- -- A vida feliz, meu Deus, consiste

Bug#1040416: linux-image-6.1.0-9-amd64: Under heavy load Debian V12 and V11 causes data corruption on XFS filesystems.

On Thu, Nov 02, 2023 at 03:37:39PM +0100, Diederik de Haas wrote: > Control: tag -1 moreinfo > > On Wednesday, 5 July 2023 19:07:15 CET Jose M Calhariz wrote: > > Package: src:linux > > Version: 6.1.27-1 > > Can you try with the latest version in the 6.1.x s

Re: Upcoming changes to Debian Linux kernel packages

On Mon, 2023-09-25 at 04:35 +0200, Andreas Beckmann wrote: > On 25/09/2023 00.50, Bastian Blank wrote: > > Already built modules remain until someone deletes it.  So you can > > also > > switch back to the still installed older kernel version and it will > > have > > the still working module

Bug#1043024: amdgpu: When updating I get a "Possible missing firmware /lib/firmware/amdgpu/modules" (Sapphire Nitro R9 390)

Hello Gregor, Sorry for the late reply, didn't get the update in my email. This is the output from apt when I update my system: Processing triggers for initramfs-tools (0.142) ... update-initramfs: Generating /boot/initrd.img-6.1.0-11-amd64 W: Possible missing firmware

Problem with a custom kernel and my Debian-based distribution

Good afternoon, I send you my best regards. I'm having a problem creating a custom kernel image for my own Debian based distribution, in this case I'm working with version 5.15.124. Let me explain my problem: At the time of making the kernel compilation I take a predefined configuration, it

Bug#1050654: linux-image-6.4.0-3-amd64: Virtualbox kernel modules fail to load on linux-image-6.4.0-3-amd64

Package: src:linux Version: 6.4.11-1 Severity: important X-Debbugs-Cc: mrdowdsouthmo...@gmail.com Dear Maintainer, Upon update to kernel 6.4.0-3-amd64, Virtualbox kernel modules no longer load. Virtualbox works normally when booting with kernel 6.4.0-2 -- Package-specific info: ** Version:

Bug#1049409: firmware-amd-graphics: Possible missing firmware for module amdgpu

Package: firmware-amd-graphics Version: 20230210-5 Severity: normal X-Debbugs-Cc: sm.snowstorm...@passinbox.com Dear Maintainer, When running update-initramfs I get the following warnings: --- Setting up linux-image-6.1.0-10-amd64 (6.1.38-2) ... /etc/kernel/postinst.d/initramfs-tools:

Bug#1028001: closing 1028001

Hi On Thu, Jan 5, 2023 at 4:27 PM Salvatore Bonaccorso wrote: > Hi, > > On Thu, Jan 05, 2023 at 04:15:16PM -0500, Raouf M. Bencheraiet wrote: > > is 2.5.4-1~exp1 available for debian stable?! > > No, it will be in the next upcoming stable release Debian bookworm, as &g

Re: Arch qualification for bookworm: call for DSA, Security, toolchain concerns

On Sat, Jul 16, 2022 at 11:46 AM Ben Hutchings wrote: > On Sat, 2022-07-16 at 11:20 -0400, Timothy M Butterworth wrote: > [...] > > i386 is anchient in tech terms it was introduced in 1985. If debian wants > > to keep supporting 32 bit OS then it should bump up to i686.

Re: Arch qualification for bookworm: call for DSA, Security, toolchain concerns

On Fri, Jul 15, 2022 at 7:51 AM Ben Hutchings wrote: > On Wed, 2022-06-22 at 10:05 +0200, Graham Inggs wrote: > > Hi, > > > > As part of the interim architecture qualification for bookworm, we > > request that DSA, the security team, Wanna build, and the toolchain > > maintainers review and

Re: Uploading linux (5.17.6-1)

On Wed, May 11, 2022 at 6:09 AM Bastian Blank wrote: > Hi > > I will upload linux version 5.17.6-1 to unstable later today. It > includes an ABI bump. > > Please upload it to backports. > Bastian > > -- > Extreme feminine beauty is always disturbing. > -- Spock, "The Cloud

Bug#1005927: linux-image-5.15.0-0.bpo.3-amd64: Linux kernel 5.15.0-0.bpo.3-amd64 fails to complete suspend and stays unresponsive to wakeup events

Package: src:linux Version: 5.15.15-2~bpo11+1 Severity: important Tags: upstream X-Debbugs-Cc: m.alfa...@gmail.com Hi. Today i installed new backport version of linux kernel. I tried suspend the machine, but it got stuck. The machine stayed on but the USB bus and harddrive was turned off.

Bug#795013: Closing this bug (BTS maintenance for src:linux bugs)

reopen 795013 thanks # Dear Salvatore: # I have not said anything for a long time, but not because the bug # didn't occur, but because I didn't know what to do when the startup # failed the described way, and because the failure was infrequent. I # always simply restarted the laptop. The

Bug#973417: Also happens on Amazon EC2 & Lightsail

Hi, I can confirm this bug happening on Amazon Lightsail and EC2 instances running Debian. After kernel upgrade the machines won't boot anymore and end in kernel panic. Here is a log from failed boot on EC2: [0.16] [] ? rest_init+0x80/0x80 [0.16] [] ? kernel_init+0xa/0x100

Bug#885846: Recurring Atheros Driver Crash

Package: firmware-atheros Version: 20190114-2 Followup-For: Bug #885846 Dear Maintainer, I am seeing a similar crash as reported in bug 885846, using wireless driver ATH9k with a TP-Link TL-WN851ND. The system freezes during moderate to high wifi activity, such as streaming or running speedtest

Bug#958737: linux-image-5.5.0-2-amd64: Intel Cannon Point-LP audio controller no longer works

i-amd64 2.04-6 pn linux-doc-5.5 Versions of packages linux-image-5.5.0-2-amd64 is related to: pn firmware-amd-graphics pn firmware-atheros pn firmware-bnx2 pn firmware-bnx2x ii firmware-brcm8021120190717-2 pn firmware-cavium ii firmware-intel-sound 20190717-2 pn firmware-intelwimax pn firmware-ipw2x00 pn firmware-ivtv ii firmware-iwlwifi 20190717-2 pn firmware-libertas pn firmware-linux-nonfree ii firmware-misc-nonfree 20190717-2 pn firmware-myricom pn firmware-netxen pn firmware-qlogic pn firmware-realtek pn firmware-samsung pn firmware-siano pn firmware-ti-connectivity pn xen-hypervisor -- no debconf information -- brian m. carlson: Houston, Texas, US OpenPGP: https://keybase.io/bk2204 signature.asc Description: PGP signature

Bug#958126: linux-image-5.5.0-2-amd64: Alt-SysRq-x no longer lifts Secure Boot restrictions

On 2020-04-18 at 21:59:35, Ben Hutchings wrote: > Control: tag -1 wontfix > > On Sat, 2020-04-18 at 18:50 +0000, brian m. carlson wrote: > > Package: src:linux > > Version: 5.5.17-1 > > Severity: important > > > > By default, Debian ships kernels

Bug#958126: linux-image-5.5.0-2-amd64: Alt-SysRq-x no longer lifts Secure Boot restrictions

-oom-kill(f) kill-all-tasks(i) thaw-filesystems(j) sak(k) show-backtrace-all-active-cpus(l) show-memory-usage(m) nice-all-RT-tasks(n) poweroff(o) show-registers(p) show-all-timers(q) unraw(r) sync(s) show-task-states(t) unmount(u) force-fb(V) show-blocked-tasks(w) dump-ftrace-buffer(z) Other

Bug#939170: linux: does not suspend completely, locks up

On Sun, 26 Jan 2020 18:03:23 +0100 Felix Rublack wrote: > Hi everyone, > > I have the same issue on a ThinkPad T460s (suspend works only half way, > reboot and poweroff stop just short before actual shutdown). > > I bisected the problem to the TPM driver. Blacklisting the module in > modprobe.d

Bug#944257: Confirmed, possible duplicate

Hi, I have exactly the same behavior on my lenovo E460 laptop. No suspend and shutdown working since upgrade to linux 5.x. I don't know how to get more attention to this. Can we raise the severity or flag it? Some more info in my earlier report #939170. Maybe even duplicate? Cheers, Daniel

Bug#945898: linux-image-5.3.0-2-amd64: No i2c_amd_mp2 kernel module

Package: src:linux Version: 5.3.9-3 Severity: normal Dear Maintainer, I have a Lenovo Ideapad 530s with an AMD ryzen cpu. This has been running fine under Debian, since I first bought the computer, although the touchpad does not work after boot. I found a very simple remedy for this using the

Debian Kernel Source

Hi, Where/How can i get the complete latest debian kernel source with the applied debian patches. I need the source similar to the linux base kernel source with similar directory tree. Need that for some research? -- Best, - Ghani

debian patches from upstream

Hi, What is the current workflow of the patch propagation from linux mainline to debian stable kernel versions? are the downstream debian kernels rebased against the latest mainline kernel version or are they just rebased against the lts upstream version from which the debian kernel was initially

Debian kernel patch propagation

Hi, What is the current workflow of the patch propagation from linux mainline to debian stable kernel versions? are the downstream debian kernels rebased against the latest mainline kernel version or are they just rebased against the lts upstream version from which the debian kernel was initially

Bug#939170: Maybe wrong package?

Hi, is it possible this one is reported against the wrong package? It seems like there are a few lenovo laptop / thinkpad owners who experience this. Is there some (pseudo)package to report this to? Maybe it gets a bit more traction there... Cheers, Daniel

Bug#939170: Also with systemctl suspend

Hi, this also happens to me when I try systemctl suspend instead of a GUI action. So it's not a problem of the desktop environment but of kernel or even systemd. Maybe something with the thinkpad kernel module? Cheers, Daniel

Bug#939170: linux: does not suspend completely, locks up

Source: linux Version: 5.2.9-2 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of

Bug#932250: linux-image-amd64: adding segfault data

Package: linux-image-amd64 Version: 4.19+105 Followup-For: Bug #932250 adding file with segfault data -- System Information: APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE,

Bug#932250: linux-image-amd64: random segfaults without taking something down

Package: linux-image-amd64 Version: 4.19+105 Severity: important Hi. Im currently running debian buster kernel and i experienced some segfaults. Segfaults are random, which prevents me from pinpointing the trigger. First i tried disabling overcommit on memory, the behavior stoped. Today it

Bug#930351: linux-image-4.9.0-9-amd64: soft lockup / stuck in pid_revalidate

On 11/06/2019 22.28, Ben Hutchings wrote: > On Tue, 2019-06-11 at 10:13 +0200, Bernhard M. Wiedemann wrote: > [...] >> kernel:[1616241.072680] NMI watchdog: BUG: soft lockup - CPU#5 stuck for >> 22s! [ps:28525] >> >> [1626796.848128] CPU: 5 PID: 28525 Comm: ps Taint

Bug#930351: linux-image-4.9.0-9-amd64: soft lockup / stuck in pid_revalidate

On 11/06/2019 22.28, Ben Hutchings wrote: > On Tue, 2019-06-11 at 10:13 +0200, Bernhard M. Wiedemann wrote: > [...] >> kernel:[1616241.072680] NMI watchdog: BUG: soft lockup - CPU#5 stuck for >> 22s! [ps:28525] >> >> [1626796.848128] CPU: 5 PID: 28525 Comm: ps Taint

Bug#930351: linux-image-4.9.0-9-amd64: soft lockup / stuck in pid_revalidate

Package: src:linux Version: 4.9.168-1+deb9u2 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? ran the server for some days with KVM VMs on top * What exactly did you do (or not do) that

Bug#895378: sky2: sky2: did not recover correctly after waking up from S3

Hi, just an update about my previous post. The "pci=nomsi,noaer" workaround is effective for resume after suspend, but it locks my computer in resume after hibernation (the computer resumes, but it locks on resume with a black screen when it should instead show the login dialog; this probably

Bug#909852: linux-image-4.18-0-0.bpo.1-amd64: backtrace in dmesg after suspend

Package: src:linux Version: 4.18.6-1~bpo9+1 Followup-For: Bug #909852 Dear Maintainer, I tried to suspend the system today and it resulted with a backtrace after waking the system. The dmesg shows that amdgpu is involved with this backtrace. It looks to me it has trouble to resume. Interesting

Bug#907717: linux-image-4.17.0-0.bpo.3-amd64: another backtrace with result of unusable system till reboot

Package: linux-image-4.17.0-0.bpo.3-amd64 Followup-For: Bug #907717 Dear Maintainer, Today i experienced a backtrace which resulted to a system without a graphic output. In logs i found a entry about a bug with a message Unable to handle kernel NULL pointer deference. The process involved in

Bug#907717: linux-image-4.17.0-0.bpo.3-amd64: random backtrace caused by refcount on Xorg

Package: src:linux Version: 4.17.17-1~bpo9+1 Severity: normal Dear Maintainer, I had installed new kernel from debian backports repository, but im experiencing some backtrace logs in system kern.log file. This does not affect systems stability. Backtrace is caused by refcount and its affecting

firmware-atheros

All, The current Ath3K firmware is failing to load on IMC Networks Atheros AR3012 Bluetooth 4.0 Adapter's This is relatively old hardware 5+ years. I tested the hardware with Ubuntu 16.04 and it works. usb 1-1.1: firmware: failed to load ar3k/AthrBT_0x01020200.dfu (-2) Bluetooth: Loading patch

Bug#906107: linux-image-3.16.0-6-amd64: Latests kernel 3.16 on KVM host breaks Linux guest with lastests kernels

On Tue, Aug 14, 2018 at 10:39:12AM +0100, Jose M Calhariz wrote: > Package: src:linux > Version: 3.16.57-2 > Severity: important > > We use OpenNebula on Debian 8 to run KVM guests. Our latest upgrade of the > host and guests broke badly. > The host can not run guests wi

Bug#906107: linux-image-3.16.0-6-amd64: Latests kernel 3.16 on KVM host breaks Linux guest with lastests kernels

and the host. Kind regards Jose M Calhariz -- Package-specific info: ** Version: Linux version 3.16.0-6-amd64 (debian-kernel@lists.debian.org) (gcc version 4.9.2 (Debian 4.9.2-10+deb8u1) ) #1 SMP Debian 3.16.57-2 (2018-07-14) ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-amd64 root=/dev/mapper

Bug#900442: linux-image-4.16.0-2-amd64: LVM2 COW snapshots fail as of 4.16

ume.snap. Creating MyGroup-MyVolume.snap Loading MyGroup-MyVolume.snap table (253:M) Resuming MyGroup-MyVolume.snap (253:M) Initializing 4.00 KiB of logical volume "MyGroup/MyVolume.snap" with value 0. Removing MyGroup-MyVolume.snap (253:M) Creating logical volume snap

Bug#893912: firmware-realtek: Failed to load rtl_bt/rtl8821a_config.bin

t; Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > firmware-realtek depends on no packages. > > firmware-realtek recommends no packages. > > Versions of packages firmware-realtek suggests: > ii initramfs-tools 0.130 > > -- no debconf information > -- -- []s, Francisco M Neto

Bug#885245: linux: FTBFS on powerpcspe: sstep.c: ptesync unrecognized

gular DD who helps ensure that build errors for packages that have recently emerged from NEW don't accidentally escape notice. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#885245: linux: FTBFS on powerpcspe: sstep.c: ptesync unrecognized

lately: {standard input}: Assembler messages: {standard input}:5854: Error: unrecognized opcode: `ptesync' /<>/scripts/Makefile.build:319: recipe for target 'arch/powerpc/lib/sstep.o' failed make[6]: *** [arch/powerpc/lib/sstep.o] Error 1 Could you please take a look? Thanks! -- A

Bug#883980: security information -- dsa-4073-1 linux

I installed "security information -- dsa-4073-1 linux" and rebooted into the 4.9.0-4-amd64 kernel. The screen-blacking problem still exists, but now it is accented by longer periods when the screen goes haywire. All I have to do to create the problem now is to (1) start Terminator, (2) make

Bug#815037: firmware-iwlwifi: Bug also leads to kernel panic and freezes

Bug message and freezes / panic is solved when I downgraded to stable. So no HW problem.

Bug#883980: Experimenting with 4.9.0-4-amd64 and 4.9.0-3-amd64

Without installing, updating or removing any software, I am experimenting with kernels 4.9.0-4-amd64 and 4.9.0-3-amd64. When I applied the Debian 9.3 upgrade, it installed a new kernel and retained the older kernel. I can select the newer or older kernel using the advanced boot menu. When I

Bug#883980: Fifth Manifestation

I was using the latest, built-in version of Firefox ESR 52.5.2 (64-bit), and I noticed that I got the same, consistent problem as with Chromium. When I move the mouse cursor between surrounding page and embedded video (either direction), the screen goes black for 1 second. This behavior is

Bug#883980: Steps to Duplicate Problem

After a clean reboot, I began experimenting to find repeatable steps to duplicate the problem. I have the following programs running across 9 workspaces (which are always running on my machine): Chromium & gPHPEdit, Web (Ephiphany) & Geany, and Terminator (running a split screen). The problem

Bug#869511: linux: binNMU-unsafe dependency on linux-headers-*-common

Source: linux Version: 4.11.11-1 Severity: grave Justification: renders package unusable (uninstallable) The recent binNMU of linux for Perl 5.26 broke the build-specific headers packages, which are architecture-dependent but depend on an identical *binary* version of the architecture-independent

Bug#862013: initramfs-tools-core: /run tmpfs size hardcoded at 10% RAM, but 16.0 MiB free required in /run/systemd

Thanks for the suggestions! On the subject of RAM requirements, for i386 systems (the case in my original message) a minimum of 128 MB is still mentioned in https://www.debian.org/releases/stable/i386/ch03s04.html.en Thus it might make sense to automatically cater for such low-mem i386 systems,

Bug#867677: initramfs-tools: [patch] feature request: provide hook to set host name in InitRAMFS config dynamically

And if you remove the extension .sh, then it is also backwards compatible with Debian 4.0 "Etch" :) # Define your network setup for the InitRAMFS via IP variable # # Still a kernel ip parameter will override any InitRAMFS config # setting (see script /usr/share/initramfs-tools/init). # #

Bug#867677: initramfs-tools: [patch] feature request: provide hook to set host name in InitRAMFS config dynamically

Updated script, more clean and also processes conf/initramfs.conf#!/bin/sh # # This InitRAMFS hook provides: # Simple script to set IP parameter in InitRAMFS config with current # hostname, instead of manually maintaining InitRAMFS config. PREREQ="" prereqs() { echo "${PREREQ}" } case "${1}"

Bug#867677: initramfs-tools: [patch] feature request: provide hook to set host name in InitRAMFS config dynamically

Package: initramfs-tools Version: 0.130 Severity: wishlist Tags: patch Dear Maintainer, when connecting to the InitRAMFS via network (e.g. encrypted root fs), then it is helpful if the machine can be registered by its name in the DNS, making it possible to connect to it via its DNS name.

Bug#862013: initramfs-tools-core: /run tmpfs size hardcoded at 10% RAM, but 16.0 MiB free required in /run/systemd

Package: initramfs-tools-core Version: 0.130 Severity: important In a virtual machine with 160 MiB RAM, running a freshly installed Debian stretch system (i686), got messages like this logged from (at least) sh and ifup: "Failed to reload daemon: Refusing to reload, not enough space

Bug#851928: linux-image-4.9.0-1-amd64: Kernel 4.9 fails to boot on Thinkpad T440p

On Sat, 2017-01-21 at 16:33 +0900, Roger Shimizu wrote: > Control: tag -1 + patch upstream > Control: forwarded -1 https://bugzilla.kernel.org/show_bug.cgi?id=191 > 121 > > On Fri, Jan 20, 2017 at 11:26 AM, JWM wrote: > > Package: src:linux > > Version: 4.9.2-2 > >

Bug#841007: linux-image-4.8.0-rc8-amd64-unsigned: Shutdown when pressing any key on Asus E200 HA

Is to tell that the new 4.9-rc works. Now I can login into the machine. During the weekend I will do a longer review of the kernel in search of regressions. Thank you. Kind regards Jose M Calhariz On 16/11/16 17:01, Santiago Vila wrote: > forcemerge 833016 841007 > thanks > >

Bug#837907: stat() hangs on a particular file

Sergio Gelato writes: Package: linux-image-3.16.0-4-amd64 Version: 3.16.36-1+deb8u1 One of our systems is suddenly unable to stat() a particular file (cookies.sqlite-wal in a user's Firefox profile). Any attempt to ^^ do so hangs in the system

Bug#841007: linux-image-4.8.0-rc8-amd64-unsigned: Shutdown when pressing any key on Asus E200 HA

On 24/10/16 03:30, Ben Hutchings wrote: > On Sun, 2016-10-16 at 21:22 +0100, Jose M Calhariz wrote: >> Package: src:linux >> Version: 4.8~rc8-1~exp1 >> Severity: important >> >> Dear Maintainer, >> >>* What led up to the situation? >&

Bug#841007: linux-image-4.8.0-rc8-amd64-unsigned: Shutdown when pressing any key on Asus E200 HA

to gather more debugging information? Kind regards Jose M Calhariz -- Package-specific info: ** Version: Linux version 4.8.0-rc8-amd64 (debian-kernel@lists.debian.org) (gcc version 5.4.1 20160904 (Debian 5.4.1-2) ) #1 SMP Debian 4.8~rc8-1~exp1 (2016-09-26) ** Command line: BOOT_IMAGE=/boot/vmlinuz

Bug#833009: linux-image-4.6.0-1-amd64: Hibernation does not work on Asus E200HA because of i915 and i2c_designware

regards Jose M Calhariz signature.asc Description: OpenPGP digital signature

Bug#833016: linux-image-4.7.0-rc7-amd64-unsigned: Shutdown when pressed any key of the keyboard

Hi, I have just tried a vanilla kernel 4.7 and it just works. Kind regards Jose M Calhariz signature.asc Description: OpenPGP digital signature

Bug#833016: linux-image-4.7.0-rc7-amd64-unsigned: Shutdown when pressed any key of the keyboard

this happens, but being a regression, I decided to report. Kind regards Jose M Calhariz -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: ASUSTeK COMPUTER INC. product_name: E200HA product_version: 1.0 chassis_vendor: ASUSTeK COMPUTER INC

Bug#833009: linux-image-4.6.0-1-amd64: Hibernation does not work on Asus E200HA because of i915 and i2c_designware

lex, lpa 0xCDE1 [ 129.340496] i2c_designware 808622C1:00: timeout in enabling adapter [ 130.348085] i2c_designware 808622C1:00: controller timed out [ 130.355959] i2c_designware 808622C1:00: Unknown Synopsys component type: 0x Kind regards Jose M Calhariz -- Package-specific info: ** Versio

Bug#832925: firmware-atheros: Please add the firmware for the wireless QCA9377 from atheros

Jose M Calhariz -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash

Bug#832458: linux-image-4.6.0-0.bpo.1-amd64: Please enable SND_SOC_INTEL_BYT_MAX98090_MACH, needed for some Baytrail devices

Package: src:linux Version: 4.6.3-1~bpo8+1 Severity: normal Dear Maintainer, Please enable CONFIG_SND_SOC_INTEL_BYT_MAX98090_MACH=m - it is necessary for audio on certain Baytrail hardware. (I note that it is also necessary to set CONFIG_DW_DMAC=y (not m) for this, although I don't understand

Bug#814320: linux-image-4.3.0-1-amd64: Slab leak

On 10/02/16 16:51, Ben Hutchings wrote: Control: severity -1 important Control: tag -1 patch On Wed, 2016-02-10 at 11:20 +0100, Josep M. Perez wrote: Package: src:linux Version: 4.3.5-1 Severity: grave Justification: renders package unusable No it doesn't. Dear Maintainer, The current

Bug#814320: linux-image-4.3.0-1-amd64: Slab leak

Package: src:linux Version: 4.3.5-1 Severity: grave Justification: renders package unusable Dear Maintainer, The current kernel is having an apparent memory leak on my computer. Over time it consumes all memory. The output of slabtop -s c after having the system on for 24h is is the following:

Bug#793185: [linux-sunxi] Re: forwarding a bug: cpufreq missing in debian stable on a cuibeboard

Am Freitag, 24. Juli 2015 14:49:42 UTC+2 schrieb Thomas Kaiser: Ah, now I think I understand. You're talking about these lines here?     https://github.com/RobertCNelson/u-boot/blob/master/arch/arm/dts/sun7i-a20-cubietruck.dts#L244-L269 Yes. So while using CONFIG_REGULATOR_AXP20X=y

Bug#793185: [linux-sunxi] Re: forwarding a bug: cpufreq missing in debian stable on a cuibeboard

Am Freitag, 24. Juli 2015 14:12:57 UTC+2 schrieb Thomas Kaiser: Maxime Ripard wrote:   What puzzles me is that exactly the same kernel (I used Igor Pečovnik's build system) provides working cpufreq support on 5 A20 devices and one it fails. And none of those 5 use CPU

Bug#755822: Info received ([SOLVED] modifying snd-hda-intel parameters)

Hi again! It seems that my solution was not complete, I also have to add the parameter 'model=vaio' to the module options line, so the correct one for me in /etc/modprobe.d/alsa-base.conf is this: options snd-hda-intel model=vaio position_fix=1 Once again, hope this helps someone in the same

Bug#755822: [SOLVED] modifying snd-hda-intel parameters

Hi, After submiting this bug back in july'14 and no receiving any answers I decided to play with module snd-hda-intel parameters. In my case it seems that: options snd-hda-intel position_fix=1 written in /etc/modprobe.d/alsa-base.conf does the trick. Currently I'm running a 4.0.4 kernel,

Bug#785564: initramfs-tools: Boot fails do to missing switch_root

Package: initramfs-tools Version: 0.120 Severity: normal If busybox is not installed and the option is BUSYBOX=y the system don't boot. Where the previous initramfs-tools could generate a bootable initrd image. -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 3.0M Apr 26

Bug#777644: linux: UDF complains about inode size of file it just created

none -- debconf information: linux-image-3.18.0-trunk-amd64/prerm/removing-running-kernel-3.18.0-trunk-amd64: true linux-image-3.18.0-trunk-amd64/postinst/depmod-error-initrd-3.18.0-trunk-amd64: false linux-image-3.18.0-trunk-amd64/postinst/mips-initrd-3.18.0-trunk-amd64: -- brian m. carlson

Bug#763606: Confirmation

M. Perez -- 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/f708a000-4d2e-4233-a543-91ddeb0b5...@gmail.com

Bug#764566: (second attempt) kernel panic apparently caused by killing alsa_in process

Package: linux-image-3.2.0-4-amd64 Version: 3.2.60-1+deb7u3 (Second attempt to report this.) A few days ago, running Debian 7 (Wheezy), I had a kernel panic immediately (less than a small fraction of a second) after pressing Enter on a command to kill a process running alsa_in somewhere around

Bug#762984: initramfs-tools: Alert! /dev/vg0/usr does not exist

On 10/07/2014 11:59 AM, IOhannes m zmoelnig wrote: i am hit by the same problem. as a temporary fix, i added the 'vgchange -ay' to /usr/share/initramfs-tools/scripts/local-top/lvm2 as adding it to /etc/initramfs-tools/scripts/local-top/vgscan somehow did not work (most likely due wrong

Bug#762984: initramfs-tools: Alert! /dev/vg0/usr does not exist

Package: initramfs-tools Version: 0.118 Followup-For: Bug #762984 i am hit by the same problem. as a temporary fix, i added the 'vgchange -ay' to /usr/share/initramfs-tools/scripts/local-top/lvm2 as adding it to /etc/initramfs-tools/scripts/local-top/vgscan somehow did not work (most likely

Bug#741450: Also on newer kernels

Hi, The issue happens to me with current kernel as well. I also tried 3.16-trunk, and the issue persists. # dmidecode -t system | grep Version lspci -vvv | grep Wireless Version: ThinkPad T440p 04:00.0 Network controller: Intel Corporation Wireless 7260 (rev 83) Subsystem: Intel

Bug#741584: booting T440p with Debian testing - problems

by default. -- John. On Sun, 2014-08-10 at 20:21 +0100, Ben Hutchings wrote: Sorry we didn't respond to this earlier. On Tue, 2014-04-22 at 06:30 -0500, John M. wrote: Hi, My workaround was to (boot in recovery mode and) blacklist nouveau, as in: # echo 'blacklist nouveau

Bug#750360: systemd-sysv: breaks NFS root systems

On Tue, Jun 03, 2014 at 07:49:08PM +0200, maximilian attems wrote: thank you very much, pushed out to initramfs repo: http://anonscm.debian.org/gitweb/?p=kernel/initramfs-tools.git will upload soonish. Hi. It's two months later and people (e.g. me!) are being bitten by this bug when

Bug#755822: linux-image-3.14-2-686-pae: Sound plays at twice its normal speed.

Package: src:linux Version: 3.14.13-1 Severity: important Tags: upstream Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Installing and booting a 3.14.x long term stable kernel. * What exactly did you do (or

Bug#741584: booting T440p with Debian testing - problems

Hi, My workaround was to (boot in recovery mode and) blacklist nouveau, as in: # echo 'blacklist nouveau' /etc/modprobe.d/blacklist-nouveau.conf After that, reboot in normal mode. It seems that the 3.13.x kernel is trying to load drivers for both the Intel and NVIDIA cards, and there's a

Bug#700513: Confirmation required...

Dear User, Please confirm the details of your email account to resolve the irregularities we noticed over the past few days. Follow the web link below to do so immediately: Click Here to Confirm

Bug#736415: linux-image-3.12-0.bpo.1-amd64: Failing to boot from xfs - libcrc32c.ko does not declare its dependencies

: Universal TUN/TAP device driver, 1.6 [ 172.574040] tun: (C) 1999-2004 Max Krasnyansky m...@qualcomm.com [ 173.328783] device t54-02-00 entered promiscuous mode [ 173.347478] device t00-01-00 entered promiscuous mode [ 173.352158] device t00-01-01 entered promiscuous mode [ 173.390334] device t55-02

Bug#733770: linux-libc-dev: linux/btrfs.h: 'NULL' undeclared

Package: linux-libc-dev Version: 3.11.10-1 Severity: important Control: affects -1 src:trinity Attempting to #include linux/btrfs.h without first ensuring a definition of NULL (for instancy, by including stddef.h) fails: /usr/include/linux/btrfs.h: In function 'btrfs_err_str':

Bug#732208: linux: 3.2.53 breaks chromium on stable/ Debian Wheezy

Any fix for this? Same thing happened to me. Got the proposed update, went to go use chromium, but get the exact same thing. I run Debian Wheezy After Debian Proposed Upgrade to linux-image-3.2.0-4-amd64:amd64 3.2.53-1 Chromium does not start. Terminal Output: $ chromium

Bug#725275: 725275 is reproducible

I can reproduce the inability to boot 3.11-trunk-amd64 (and the preceding 3.11-rc7-amd64) with initramfs-tools 0.114. With 0.113, everything works fine. -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP

Bug#717195: linux-kbuild-3.10: modpost wrapper crashes due to bad getline call

Package: linux-kbuild-3.10 Version: 3.10-1 Severity: important debian/build/scripts/mod/modpost passes getline pointers to uninitialized name and name_len variables, leading to crashes under some circumstances. According to getline's manpage, initializing name to NULL should let the call

Bug#717195: linux-kbuild-3.10: modpost wrapper crashes due to bad getline call

the modpost binary under Valgrind to help track the problem down. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject

Bug#714497: More info: not found in 3.8-2-amd64

Hi, I booted my old kernel (3.8-2) and the problem has gone away, so it is definitely something in the 3.9 kernel. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive:

Bug#714497: kernel BUG at /build/linux-eHaf39/linux-3.9.6/include/drm/drm_mm.h:100

interface [ 181.871080] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready [ 193.023365] tun: Universal TUN/TAP device driver, 1.6 [ 193.023373] tun: (C) 1999-2004 Max Krasnyansky m...@qualcomm.com [ 193.402444] CUSE: failed to register chrdev region [ 193.402478] CUSE: failed to register

Bug#714497: More info: also found in RedHat

It seems this bug is reported at least four times to Fedora project, so it's likely an upstream issue. Fedora references: https://bugzilla.redhat.com/show_bug.cgi?id=964120 https://bugzilla.redhat.com/show_bug.cgi?id=967282 https://bugzilla.redhat.com/show_bug.cgi?id=975073

Bug#713030: linux-image-3.9: [3.2-3.9] Warnings of CPU intel-microcode not found

the updated microcode installed, I think it may be worth having the installer telling you. 2013/6/22 Ben Hutchings b...@decadent.org.uk Control: tag -1 wontfix On Sat, 2013-06-22 at 01:13 +0200, Eugenio M. Vigo wrote: Hi, I want to get rid of the warning, mainly because I don't know whether

Bug#713030: linux-image-3.9: [3.2-3.9] Warnings of CPU intel-microcode not found

Package: src:linux Version: 3.9.6-1 Severity: normal File: linux-image-3.9 Dear Maintainer, after the last kernel update from 3.2.x to 3.9.x in Debian Jessie, a warning is shown upon boot up about some CPU microcode not being found. In my case, the warning is the following one: platform

Bug#713030: linux-image-3.9: [3.2-3.9] Warnings of CPU intel-microcode not found

escribió: On Sat, 2013-06-22 at 00:26 +0200, Eugenio M. Vigo wrote: after the last kernel update from 3.2.x to 3.9.x in Debian Jessie, a warning is shown upon boot up about some CPU microcode not being found. In my case, the warning is the following one: platform microcode: firmware: agent

Bug#711202: linux-image-3.2.0-4-amd64: e1000e Detected Hardware Unit Hang only on kernel 3.2

Package: src:linux Version: 3.2.41-2+deb7u2 Severity: normal Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? The openafs fileserver, under normal workload, the kernel says: Jun 4 13:33:25 tania kernel: e1000e

  1   2   3   >