Bug#928736: initramfs-tools: With plymouth print misleading resuming from hibernation

Package: initramfs-tools Version: 0.133 Severity: normal When plymouth is installed, every time I power on my notebook the following message is printed on the screen: Resuming from hibernation But I'm not resuming from hibernation, I'm doing a regular boot from power off. Is it possible to show t

Bug#924553: linux-image-4.19.0-4-amd64: PKCS#7 signature not signed with a trusted key

Package: src:linux Version: 4.19.28-1 Severity: normal With this kernel version (but not with the last 4.19.0-3) journalctl shows many of these messages: PKCS#7 signature not signed with a trusted key A lot of such messages can also be seen on the early booting phase. Also I noticed that, below,

Bug#913119: Bug#913138: Bug#913119: linux-image-4.18.0-2-amd64: Hangs on lvm raid1

On 28/02/19 16:44, Thorsten Glaser wrote: please do consider uploading 4.19.24 to buster/sid with some haste. We have headless virtualisation hosts being unreachable/frozen now, and while these are “only” development systems, this is untenable. Like you I'm looking forward for that kernel. But,

Bug#913119: Bug#913138: Bug#913119: linux-image-4.18.0-2-amd64: Hangs on lvm raid1

On 13/02/19 18:21, Dragan Milenkovic wrote: This patch is already on its way to stable branches. I have tested it and confirmed that it resolves the problem. Hello Dragan, do you know if the patch was eventually included upstream and possibly in which version? Cesare.

Bug#913119: linux-image-4.18.0-2-amd64: Hangs on lvm raid1

On Tue, 5 Feb 2019 01:36:08 +0100 Dragan Milenkovic wrote: I have tracked the issue to this change: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/diff/block/blk-flush.c?id=344e9ffcbd1898e1dc04085564a6e05c30ea8199 Thank you very much for your deep analisys and thank you also

Bug#913119: linux-image-4.18.0-2-amd64: Hangs on lvm raid1

Hi Hans! On Sat, 24 Nov 2018 01:08:56 +0100 Hans van Kranenburg wrote: You didn't share any part of your logging. Can you share a part of dmesg logging that shows Oops in it? Here it is, attached to this message. Previously I didn't attached it because to me it looks substantially the same

Bug#913119: linux-image-4.18.0-2-amd64: Hangs on lvm raid1

Bug still present with the new 4.18.0-3-amd64 (4.18.20-1). This morning I've tryed to boot this new kernel version, removing the workaround given by the following kernel parameters: scsi_mod.use_blk_mq=0 dm_mod.use_blk_mq=0 The system showed disk hangs in less than 5 hours, and, as in previous

Bug#913119: linux-image-4.18.0-2-amd64: Hangs on lvm raid1

I've added some details in #913138, which I believe is the same bug as this one. There a commenter suggested two kernel parameters that, so far, have resolved the problem for me. Cesare.

Bug#913138: linux: I/O on md RAID 6 hangs completely

On Thu, 08 Nov 2018 23:28:16 +0100 =?UTF-8?Q?Stanis=C5=82aw?= wrote: I suffer the same problem while running RAID1 with kernel 4.18.10-2. Me too. For me this happens since the switch from 4.16 to 4.17.x, with two different PCs, both with LVM based RAID1. I've already opened bug #913119, then

Bug#841423: LVM: raid1 kernel module not loaded

Package: initramfs-tools Version: 0.125 Severity: normal Initially i thought to file this bug to lvm2 package but now i suspect it's more related with kernel modules dependencies and the manual_add_modules() hook of initramfs-tools. Suppose your system has lvm2 installed but not mdadm. Now search

Bug#808563: really should be serious bug: data loss

I've done the following tests that seems to prove that the bug is with the PAE kernel, also the last 4.4.0-rc5: * Boot with linux-image-4.4.0-rc5-686 (4.4~rc5-1~exp1): OK. * Boot with linux-image-4.4.0-rc5-686-pae (4.4~rc5-1~exp1): ata errors. * Boot with linux-image-4.3.0-1-686 (4.3.3-2): OK. * Bo

Bug#808563: really should be serious bug: data loss

On 21/12/2015 17:20, 積丹尼 Dan Jacobson wrote: ata1.00: exception Emask 0x60 SAct 0x1c SErr 0x800 action 0x6 frozen ata1.00: irq_stat 0x2000, host bus error ata1: SError: { HostInt } ata1.00: failed command: WRITE FPDMA QUEUED ata1.00: cmd 61/00:10:00:a8:10/08:00:26:00:00/40 tag 2 ncq 1048576 o

Bug#786382: Bug resolved

Today i've upgraded my system and the problem looks resolved. For details, see the bug opened upstream: https://bugs.freedesktop.org/show_bug.cgi?id=90617 To me this bug can be closed. Cesare.

Bug#786382: linux-image-4.0.0-1-amd64: Blank screen switching to a VT (Intel Haswell with HD4400)

When I replied I did not realize that what you intended for upstream was freedesktop.org, not kernel.org. I've just filed the bug upstream, as you requested: https://bugs.freedesktop.org/show_bug.cgi?id=90617 Also, in my initial message i did a typo in the notebook model: it's a PU301LA (not LS).

Bug#786382: linux-image-4.0.0-1-amd64: Blank screen switching to a VT (Intel Haswell with HD4400)

2015-05-21 11:28 GMT+02:00 Julien Cristau : > Please file this upstream at > https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM/Intel > See instructions at > https://01.org/linuxgraphics/documentation/development/how-report-bugs Ok, i'll do. I only ask to the kernel team if you i

Bug#786382: linux-image-4.0.0-1-amd64: Blank screen switching to a VT (Intel Haswell with HD4400)

Package: src:linux Version: 4.0.2-1 Severity: normal Since kernel version 4.0 (also the previous 4.0.0-trunk from experimental) if i try to switch to a VT from an X session (also from the login manager), the screen becomes black and i'm not able to recover from that situation, neither for the X se

Status of cpupower

Hi kernel team. Two years ago, in bug #639454 was discussed to replace cpufrequtils with cpupower and to integrate it in linux-tools, maybe with other kernel userland tools. What's the status on this? Any plan for Jessie? If that helps, seems Ubuntu has done that in 13.10: https://lists.ubun

Bug#746448: linux-image-3.14-1-486: acpi-cpufreq not loaded on some older system

Package: src:linux Version: 3.14.2-1 Severity: normal On some older PCs like mine, the acpi-cpufreq module doesn't load anymore with 3.14 kernel (also with the previous rc7 from experimental) so i'm currently stuck with 3.13. The effect on my notebook is that the cpu runs always at full speed, the

Bug#723675: Test on another PC

I've tested 3.11-1~exp1 on a completely different PC, intel based and it boots just fine. Apart for the different CPU vendor, they differ also for the architecture: AMD: i686 Intel: x86_64 No more ideas or things to try. Cesare. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.

Bug#723675: CPU details

My initial report doesn't show clearly what CPU i have. Maybe it can be useful to diagnose the problem. # lscpu Architecture: i686 CPU op-mode(s):32-bit, 64-bit Byte Order:Little Endian CPU(s):1 On-line CPU(s) list: 0 Thread(s) per core:1 Core(s

Bug#723675: linux-image-3.11-trunk-amd64: kernel panic in early boot

Package: src:linux Version: 3.11-1~exp1 Severity: normal Attached the image that shows what i see booting with: linux-image-3.11-trunk-amd64 (3.11-1~exp1) The panic happens just after "Booting the kernel." and some of its information scrolled off the screen. The boot is ok with: - linux-image-3.

Bug#685108: linux-image-3.2.0-3-amd64: Error message on each boot: [drm:intel_dsm_platform_mux_info] *ERROR* MUX INFO call failed

Package: src:linux Followup-For: Bug #685108 Ehm, the attachment... Cesare. -- System Information: Debian Release: 7.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (

Bug#685108: linux-image-3.2.0-3-amd64: Error message on each boot: [drm:intel_dsm_platform_mux_info] *ERROR* MUX INFO call failed

Package: src:linux Followup-For: Bug #685108 I see the same message on every boot but the system looks functional. I have a Sandy Bridge too (G640T) with an Intel board (DH1CR). Dmesg attached. Cesare. -- System Information: Debian Release: 7.0 APT prefers stable APT policy: (500, 'stable')

Re: Bug#699656: general: System freezes while using multimedia via DRI [Intel 82865G chip] on kernels above 3.2.0-3-686-pae

On 11/02/2013 03:33, Ben Hutchings wrote: I realise it's critical to you, but if it doesn't affect other users then I'm afraid it's just not that high a priority. Most i865 systems have been thrown out by now, and to be brutally honest I personally a more concerned about supporting today's hardw

Bug#687927: firmware-realtek: Missing rtl8411-1.fw and rtl8402-1.fw

Package: firmware-realtek Version: 0.36 Severity: normal I have an Intel D525MW motherboard (Atom) with a Realtek integrated network card. It doesn't work with the current kernel from testing: linux-image-3.2.0-3-amd64 (3.2.23-1) It doesn't print anything special in the syslog: # dmesg | grep r816

Bug#656813: cfg80211: failed to add phy80211 symlink to netdev!

Package: linux-2.6 Followup-For: Bug #656813 I admit that starting from the Stanislaw Gruszka's reply i was a bit lost in this bug report... With this followup i only wanted to say that with the kernel 3.5 the message "cfg80211: failed to add phy80211 symlink to netdev!" is gone. Now i see a "lp

Bug#653669: Installation works now

On 02/06/2012 07:00, Bernhard wrote: One thing, i have observed during installation: The installation of the packages takes very long. If i use ext4 as filesystem, the installation takes a significant shorter time. Maybe the entry regarding dpkg from this blog article could explain this: http:/

Bug#656813: cfg80211: failed to add phy80211 symlink to netdev!

On 22/01/2012 02:12, Ben Hutchings wrote: Can you test whether the attache patch fixes this (and doesn't cause any new problems)? Instructions for rebuilding the kernel package are at: http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official Looking inside your patch i'v

Bug#656813: cfg80211: failed to add phy80211 symlink to netdev!

Package: linux-2.6 Version: 3.2.1-1 Severity: normal Some kernel version ago (some version before #656812), i started to see this message on boot: --- waiting for /dev to be fully populated...[5.775083] cfg80211: failed to add phy80211 symlink to netdev! done. -

Bug#656812: linux-image-3.2.0-1-486: module dm-raid45/unix not found in modules.dep

Package: linux-2.6 Version: 3.2.1-1 Severity: normal I'm not sure if the kernel is the correct package for this bug: my apologize if i'm wrong. Since some version i see these messages on the early boot: --- Loading, please wait... modprobe: module dm-raid45 not found in modules.dep mo

Bug#655152: The problem with multiple "[drm:intel_prepare_page_flip] *ERROR* Prepared flip multiple times" is associated with KDE plasma desktop desktop effects

On 21/01/2012 00:50, Wojciech Zabolotny wrote: I have stated, that if I disable the "desktop effects" the problematic "[drm:intel_prepare_page_flip] *ERROR* Prepared flip multiple times" do not overload my logs. [...] Anyway the problem does not appear on my other machines with Intel graphic ch

Bug#644931: Update

In the past days i could test an Asrock E350 mainboard, the Asrock (almost) equivalent of the Sapphire board reported in this bug. The problem mounting the initial drive is still present *but* if i change hard disk everything is fine. In my initial post i've written that i was not able to mou

Doubt about bug #644931

Hi kernel team. Yesterday i have filed bug #644931 by hand (no reportbug), since it was referred to a different machine that had trouble booting. But thinking about it and about a past mail from Ben, that now i can't find, i'm not sure i've assigned to the correct package. Looking from past b

Bug#619472: X.org with i915 produces garbage sometimes being run on Linux 2.6.38

On 26/03/2011 18:12, Ben Hutchings wrote: I would suggest you to give a look at this: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619472 That is the very same bug report you are responding to. Probably not what you meant to refer to. Sorry for the error, i was referring to: http://bugs.

Bug#619472: X.org with i915 produces garbage sometimes being run on Linux 2.6.38

On 25/03/2011 11:42, Andrew O. Shadoura wrote: Possibly. But somehow this worked fine with 2.6.36. That's the point. Now i have to use the 2.6.37 because with 2.6.38 i have screen corruption. From what i've understood from Intel developers, 2.6.38 contains changes that require an x driver not

Bug#619472: X.org with i915 produces garbage sometimes being run on Linux 2.6.38

On 24/03/2011 11:30, Andrew O. Shadoura wrote: After upgrading the kernel, X.org produces garbage in random screen areas. That garbage persists in the windows in which it appears (I'm able to take a screenshot of it). I would suggest you to give a look at this: http://bugs.debian.org/cgi-bin/bu

Bug#618958: linux-base: Boot loader configuration not recognized

2011/3/19 Cesare Leonardi : > --- > The boot loader configuration for this system was not recognized. These > settings in the configuration may need to be updated: > > * The root device ID passed as a kernel parameter; > * The boot device ID used to install and upda

Bug#619022: linux-image-2.6.38-1-686: Screen corruption with i855

On 20/03/2011 15:48, Ben Hutchings wrote: DRI bugs are tracked on bugs.fd.o, regardless of whether they are in the X, Mesa or kernel part of DRI. Didn't know. If you and Julien wouldn't had told me, i would have reported to bugzilla.kernel.org. Ok, so i've reported the bug to fdo and this is

Bug#619022: linux-image-2.6.38-1-686: Screen corruption with i855

On 20/03/2011 15:20, Ben Hutchings wrote: Please report this upstream on, under product 'DRI', component 'DRM/Intel'. Let us know the bug URL so we can track it. bugs.freedesktop.org? So do you think it's a bug in X.org and not the kernel? But if i use 2.6.37, as

Bug#618958: linux-base: Boot loader configuration not recognized

nly modes which your graphic card supports via VBE # you can see them in real GRUB with the command `vbeinfo' #GRUB_GFXMODE=640x480 # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux #GRUB_DISABLE_LINUX_UUID=true # Uncomment to disable generation of r

Bug#618958: linux-base: Boot loader configuration not recognized

Package: linux-base Version: 3 Severity: minor Today i've updated linux-base to version 3 and the following message appeared: --- The boot loader configuration for this system was not recognized. These settings in the configuration may need to be updated: * The root device ID passed

Re: Bug#618486: linux-image-2.6.38-rc8-686: please set CONFIG_SCHED_AUTOGROUP

On 16/03/2011 04:12, Ben Hutchings wrote: This is very usefull for desktop users feature of this release: http://kernelnewbies.org/Linux_2_6_38#head- 59575a6aeafa38490226a560ee02de89829a5b20 Please set it (perhaps, "NO" by default). Yes, that makes sense. I'll enable the config option but pa

Bug#618665: linux-image-2.6.32-5-686: mouse pointer not visible and crashes when playing video files

On 17/03/2011 13:16, Tobias Küster wrote: After updating the packages 'linux-base' and 'linux-image-2.6.32-5-686' from version 2.6.32-30 (stable) to 2.6.32-31 (squeeze-proposed-updates) and restarting the system, my mouse pointer was not shown any more. The mouse and other pointing devices were s

Re: Dropping 686 non-pae kernel

On 13/03/2011 18:07, Ben Hutchings wrote: Put two sets of benchmark results in two files (one number per line). ministat then calculates statistical measures of each set and a comparison of the two sets. I've run the following in recovery mode (to avoid interference from other programs/daemons

Re: Dropping 686 non-pae kernel

On 13/03/2011 18:07, Ben Hutchings wrote: I think that one actually has PAE. /proc/cpuinfo will tell you for sure. Unfortunately not. flags: fpu vme de pse tsc msr mce cx8 sep mtrr pge mca cmov clflush dts acpi mmx fxsr sse sse2 ss tm pbe up bts est tm2 In the past i read that there are diffe

Re: Dropping 686 non-pae kernel

On 13/03/2011 04:45, Ben Hutchings wrote: This really ought to be checked on a Pentium M as well, though. Ok, my notebook uses a Pentium M 725 (Dothan). I've run the following script (it should be equivalent to yours) with 2.6.38-rc7 from experimental in recovery mode, both for 486 and 686. A

Re: Dropping 686 non-pae kernel

On 14/02/2011 13:11, Bastian Blank wrote: Are there any changes we could/should make to the 486 flavour that would make it perform better on 686-class processors? Should we consider also dropping 486 support and making it a 586 flavour with corresponding optimisations? The 486 flavour have onl

Bug#610267: linux-image-2.6.37-trunk-686: Brightness raised to max on boot during the KMS switch

Package: linux-2.6 Version: 2.6.37-1~experimental.1 Severity: normal I've took the liberty to CC Mattia Dongili as an expert of the sony-laptop module: maybe he could have an opinion. With this kernel and rc7, but not with .36 and previous version, the LCD brightness of my Sony laptop is raised t

Bug#610250: linux-image-2.6.37-trunk-686: Oops inserting a PCMCIA 56k modem

Package: linux-2.6 Version: 2.6.37-1~experimental.1 Severity: normal These days i had problems with my adsl so i had to use a 56kbps pccard modem i keep as backup. It has always worked in the past years with Linux, but with this kernel version it prints on the console what reported in "modem-pcmci

Bug#599368: Bug#608138: initramfs-tools: NMI error on boot only in recovery mode

On 01/02/2011 11:51 PM, Ben Hutchings wrote: Yes, I see, it doesn't say that this is a fatal error for watchdog initialisation. I've seen just now the patch (v1 and v2) you sent upstream: thank you very much for improving the error message and the documentation. Very very appreciated. Cesar

Bug#599368: Bug#608138: initramfs-tools: NMI error on boot only in recovery mode

On 01/02/2011 10:44 PM, Ben Hutchings wrote: Then add +1 to what Michael Biebl already asked: why that message should be showed? Because the watchdog feature was enabled at compile-time and you presumably want it to work. If you add 'nowatchdog' to the kernel parameters then the kernel will no

Bug#608138: initramfs-tools: NMI error on boot only in recovery mode

On 12/27/2010 09:36 PM, Cesare Leonardi wrote: Grub command lines are identical except that "lapic hpet=force" in normal boot is substituted by "single" in recovery mode. I've found that if i remove "lapic" from the command line, then the NMI error appears.

Bug#608138: initramfs-tools: NMI error on boot only in recovery mode

On 12/27/2010 10:16 PM, Ben Hutchings wrote: In a default GRUB configuration, kernel logging to the console is limited using the 'quiet' parameter, except in recovery mode. I use "quiet" in recovery mode too. Do you mean that when i use the "single" parameter, "quiet" is less quiet? Cesare.

Bug#608138: initramfs-tools: NMI error on boot only in recovery mode

On 12/27/2010 09:48 PM, Michael Prokop wrote: This is not an initramfs-tools issue. Re-assigning to linux-2.6 and leaving it to the kernel maintainers how to proceed with this issue Ah, thanks! In fact i were not sure at what package address this bug. (see #599368 for similar issue). Sorry,

Bug#608138: initramfs-tools: NMI error on boot only in recovery mode

Package: initramfs-tools Version: 0.98.7 Severity: normal Every time i boot in recovery mode, i see this message: - Loading Linux 2.6.37-rc5-686 ... Loading initial ramdisk ... [0.020165] NMI watchdog failed to create perf event on cpu0: ffa1 Loading, please wait... resume: libgcrypt v

Memtest kernel options

Hi all. Today i wanted to try the memtest= boot parameter but it didn't work. So i found that the memtest funcionality is not present in Debian kernels: neither 2.6.32-24 nor 2.6.36~rc6-1~experimental.1: # CONFIG_MEMTEST is not set I wonder why. Are there performance problems? Compatibility wi

hdparm: Nasty messages from the kernel on boot

Package: hdparm Version: 9.32-1 Severity: normal The latest update brought kernel 2.6.32-24 and hdparm 9.32-1. Rebooting with this kernel, during the initial udev activity (when it change to KMS mode and everything is black) there was a long pause with the hd light on but no noise from it. The sys

Re: Bug#598803: xserver-xorg-video-intel: X crashes / hung gpu, now and then

CCing the kernel team for letting them know. On 10/02/2010 01:45 PM, Steinar H. Gunderson wrote: I'm seeing the issue of hung GPU, after which a lot of applications (in particular urxvt) become very messed up. Restarting X does not help for me. [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck

Bug#598533: ERROR: Unable to locate IOAPIC for GSI

On 09/29/2010 09:07 PM, Michael Biebl wrote: Package: linux-2.6 Version: 2.6.36~rc5-1~experimental.1 Severity: minor File: /boot/vmlinuz-2.6.36-rc5-686 During boot I get the following error messages: [0.308439] ERROR: Unable to locate IOAPIC for GSI 4 [0.309371] ERROR: Unable to locate

Bug#592415: Invisible mouse update

On 08/20/2010 04:21 PM, Cesare Leonardi wrote: The latest kernel from experimental (2.6.35-1~experimental.2) didn't solved the problem. I were confident that 2.6.36 would have solved this problem, but sadly with 2.6.35rc5 is still here. No mouse pointer under X. Someone tested that

Squeeze kernel, i855 and KMS

Hi debian-kernel developers. I would just to let you know (in case you don't know yet) the latest changes in xserver-xorg-video-intel, that substantially reintroduces KMS for older chipsets like i855 and require it to not be blacklisted anymore in the kernel for these chipsets. This is the ch

Bug#596453: 855GM: X hard locks system on startup

On 09/11/2010 06:24 PM, Robert Scott wrote: Blacklisting the 855GM from KMS in 2.6.32-21 to fix bugs like 582105 seems to be causing my system to hard lock when X starts up. Magic sysrq key does nothing, and of course the 855GM being totally blacklisted means modeset=1 is powerless. Hi Robert,

Bug#595511: linux-image-2.6.32-5-686: Blacklisting KMS for i8xx makes xorg intel driver unusable on these chipsets

On 09/07/2010 02:27 PM, Ben Hutchings wrote: On Sun, Sep 05, 2010 at 02:25:25PM +0200, Cesare Leonardi wrote: It's both a kernel and a xserver-xorg-video-intel problem, but more the latter. The kernel team is probably waiting to know if KMS should be enabled or not for these chipsets a

Bug#595521: i915: system locks up when starting X

On 09/05/2010 02:35 PM, Cesare Leonardi wrote: Kernel-team: to me these two bugs could be merged. Didn't see Julien have already merged them, sorry. Cesare. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble?

Bug#595521: i915: system locks up when starting X

On 09/04/2010 10:15 PM, Edward Allcutt wrote: By "locks up" I mean: * Screen blanks * Unresponsive to network * Unresponsive to sysrq * No disk activity * No logs written to disk after that point in time I have xserver-xorg-video-intel 2:2.12.0+legacy1-1 installed. Before rebooting tod

Bug#595511: linux-image-2.6.32-5-686: Blacklisting KMS for i8xx makes xorg intel driver unusable on these chipsets

On 09/04/2010 08:00 PM, Soenke wrote: the recent update of linux-image-2.6.32 to 2.6.32-21 disables KMS for i8xx chipsets. This causes the xorg-video-intel driver to hang on X startup on my system. Yes, the situation for your i855 and previous intel chipset is in a bad shape. For example look

Re: Bug#594623: xserver-xorg-video-intel: after upgrade to 2.12.0+legacy1-1 X freeze on gdm start

On 08/28/2010 02:10 PM, Julien Cristau wrote: Could you guys test the driver pointed at http://lists.freedesktop.org/pipermail/intel-gfx/2010-August/007910.html? (probably with the 2.6.32-20 kernel) Situation summary: - the latest intel drivers and the latest kernel kms blacklisting cause hard

Re: Bug#594623: xserver-xorg-video-intel: after upgrade to 2.12.0+legacy1-1 X freeze on gdm start

For Chris Wilson: you can follow this bug history here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594623 On 08/29/2010 05:18 PM, Julien Cristau wrote: Although it looks like they crash the X server in dri2 code when I run glxinfo, so I put xserver packages with a fix for that crash at the

Re: Bug#594623: xserver-xorg-video-intel: after upgrade to 2.12.0+legacy1-1 X freeze on gdm start

On 08/29/2010 05:18 PM, Julien Cristau wrote: There are i386 packages at http://people.debian.org/~jcristau/intel-shadow/ which work for me on minimal testing. Hi Julien. As long as you provide .deb packages, i can test whatever you want! ;-) Here is my results. Now i'm writing with: - i855

Re: Bug#594623: after upgrade to 2.12.0+legacy1-1 X freeze on gdm start

On 08/27/2010 11:45 PM, Julien Cristau wrote: Does the legacy driver work with UMS at all (on a different kernel, e.g.)? I've now tried to downgrade the .32 kernel to 2.6.32-20 and rebooting passing i915.modeset=0 to the kernel and without the file /etc/modprobe.d/i915-kms.conf (which contain

Bug#592415: Invisible mouse update

On 08/27/2010 06:25 AM, Ben Hutchings wrote: Please test 2.6.32-21 which is now in unstable. This disables KMS for the 855 chipset, which may fix this. I Ben, for me the KMS disabling was a big trouble, as i explain in #594623. Cesare. -- To UNSUBSCRIBE, email to debian-kernel-requ...@list

Re: after upgrade to 2.12.0+legacy1-1 X freeze on gdm start

Package: xserver-xorg-video-intel Version: 2:2.12.0+legacy1-1 Severity: normal I cc the kernel team, since i believe it is something that relates to them also. I have the same problem as reported by Kamen: when GDM try to start, the screen goes black and the CPU fan starts to go at full speed (as

Bug#593720: Fwd: Deadline as default scheduler?

2010 00:04:44 +0200 From: Cesare Leonardi To: debian-kernel@lists.debian.org Hi all. I've noted some changes in the scheduler configuration of 2.6.35-trunk-686 and i wonder if they are erroneous or not, since their effect are rather evident and i've seen no discussion on d-k. I was fi

Bug#592415: Invisible mouse update

The latest kernel from experimental (2.6.35-1~experimental.2) didn't solved the problem. I've done some research and i can confirm that this bug is related to 855 intel chipset, and it is quite common. These bugs from Ubuntu and Arch contains useful informations: https://bugs.launchpad.net/ubu

Bug#592415: Bug#592955: linux-image-2.6.35-trunk-686: Can’t see mouse pointer in X

On 08/14/2010 03:34 PM, Andrea Bolognani wrote: when I run the 2.6.35 kernel, I can’t see the mouse pointer under X on my ThinkPad X40. The mouse pointer works fine: I can right–click to get context menus and select any of the menu items to activate it. Focus–follows–mouse also works fine, only

Deadline as default scheduler?

Hi all. I've noted some changes in the scheduler configuration of 2.6.35-trunk-686 and i wonder if they are erroneous or not, since their effect are rather evident and i've seen no discussion on d-k. I was filing a bug but i preferred to ask on the mailing list first. --- /boot/config-2.6.35-

Bug#592415: linux-image-2.6.35-trunk-686: invisible mouse under GDM and GNOME

Package: linux-2.6 Version: 2.6.35-1~experimental.1 Severity: normal Strange bug that could make think it's unrelated from kernel, but if i boot with 2.6.35-rc6 it doesn't happen. When gdm starts no mouse pointer is present, but loggin in shows that the pointer is only invisible, because i can se

Bug#592375: linux-image-2.6.35-trunk-686: update-grub not called anymore

Package: linux-2.6 Version: 2.6.35-1~experimental.1 Severity: normal I've installed 2.6.35-trunk from experimental upgrading linux-base to the same version. After reboot grub didn't show me the related entry. Rebooting the previous 2.6.35-rc6 and manually launching update-grub solved the problem.

Bug#574795: marked as done (libata missing workaround for HPA overlapping normal partitions)

On 18/05/2010 16:24, Debian Bug Tracking System wrote: Your message dated Tue, 18 May 2010 14:22:58 + with message-id and subject line Bug#572618: fixed in linux-2.6 2.6.32-13 has caused the Debian Bug report #572618, regarding libata missing workaround for HPA overlapping normal partitions t

Bug#576758: Debconf: Unknown template field _description

maximilian attems wrote: known, next time we will spam again with debconf ;) Astonishing! You replied in less than 4 minutes from my sending. Perhaps you are not human!? ;-) fixed in repo will be uploaded soonest, waiting for HPA libata fix. Many thanks. Cesare. -- To UNSUBSCRIBE, emai

Bug#576758: Debconf: Unknown template field _description

Package: linux-2.6 Version: 2.6.32-11 Severity: normal While installing 2.6.32-11 aptitude shows these train of messages: (1) - Preconfiguring packages ... debconf: Unknown template field '_description', in stanza #1 of /tmp/linux-image-2.6.32-4-686.template.38292 d

Bug#574797: Spurious libata message on boot

Ben Hutchings wrote: Can you run 'strace -o modprobe.strace modprobe foo' and then send the modprobe.strace file? Attached what you requested. Don't know why when processing /proc/cmdline, modprobe do a write(). Cesare. execve("/sbin/modprobe", ["modprobe", "foo"], [/* 18 vars */]) = 0 brk(0)

Bug#574797: Spurious libata message on boot

Ben Hutchings wrote: Try running: grep 'options libata' /etc/modprobe.conf /etc/modprobe.d That should of course be: grep -r 'options libata' /etc/modprobe.conf /etc/modprobe.d Hi Ben! That command gives no results: tommaso ~# grep -r 'options libata' /etc/modprobe.conf grep: /etc/m

Bug#574797: Spurious libata message on boot

Ben Hutchings wrote: Due to bug #574795 i was forced to add libata.ignore_hpa=1 on boot. Now during the boot phase i see several of the following string appearing asyncronously: options libata ignore_hpa=1 Do you mean that this exact line is printed to the screen? This is very strange! Yes,

Bug#574797: Spurious libata message on boot

Cesare Leonardi wrote: Package: linux-2.6 Version: 2.6.32-10 Severity: normal Sorry, i don't know why reportbug set this package name even if i run: reportbug linux-image-2.6.32-4-686 In bug #574795 i've corrected it by hand, but here i have forgotten. Package is linux-image-2.6.32

Bug#574797: Spurious libata message on boot

Package: linux-2.6 Version: 2.6.32-10 Severity: normal Due to bug #574795 i was forced to add libata.ignore_hpa=1 on boot. Now during the boot phase i see several of the following string appearing asyncronously: options libata ignore_hpa=1 I see many of them during the initramfs phase, two or t

Bug#574795: Libata transition and HPA caused disk size truncation

Package: linux-image-2.6.32-4-686 Version: 2.6.32-10 Severity: normal I will be verbose mainly to help the kernel team, because i suspect this problem will arise for others during this libata transition. Dear maintainter, this bug has documentation purposes: treat it as you like. It isn't really

Bug#567204: linux-image-686-bigmem: serious filesystem corruption with bigmem kernels

M. Dietrich wrote: Does this mean that with normal 686 or 486 kernel the corruption doesn't happen? yes. So could be a kernel bug. Or the bigmem kernel trigger the problem early or frequently. Have you already searched through internet if someone had hit your problem? Because i suspect it's

Bug#567204: linux-image-686-bigmem: serious filesystem corruption with bigmem kernels

M. Dietrich wrote: my system had serious filesystem corruption with several -bigmem kernel in the past (from 2.6.28 to 2.6.32). Does this mean that with normal 686 or 486 kernel the corruption doesn't happen? However many years ago i've experienced frequent filesystem corruption but i could

Bug#507676: initramfs-tools: does not wait for usb disks in fstab to show up

hugo vanwoerkom wrote: Booting linux-image-2.6.26-1-686 initramfs does not wait for the 2 USB disks that are in /etc/fstab to show up, causing the boot to fail. From what i've heard from previous posts, you can try with the "rootdelay=n" kernel boot parameter, where n is the number of seconds

Bug#491443: /var/lib/initramfs-tools/ not updated

Package: initramfs-tools Version: 0.92e Severity: minor Today i've changed "update_initramfs" variable from "yes" to "all". The update-initramfs scripts seems to look at the contents of the directory "/var/lib/initramfs-tools/" to know for what image to update (it contain MD5 files, one for eve

Bug#438736: intel driver produces kernel crash in a variety of situations

Robert Millan wrote: Well, since X is a userland process, I wouldn't expect it to be able to crash the kernel, even if it plays with /dev/agpgart in a bad way. It can even be a security issue. I'm not a X expert but the server contains many drivers that interact with the graphics hardware, i

Bug#438736: intel driver produces kernel crash in a variety of situations

Robert Millan wrote: I've recently upgraded my hardware (motherboard + cpu + ram) and am now getting Linux crashes in a variety of situations. I've detected them when any of the following conditions are met: - When starting a second X session. - When time goes backwards (e.g. due to ntpdate

Bug#395359: Bug#396197: linux-image-2.6.16-2-486: cannot be purged

Martin-Éric Racine wrote: dpkg: error processing linux-image-2.6.16-2-486 (--purge): subprocess post-removal script returned error exit status 128 Errors were encountered while processing: linux-image-2.6.16-2-486 I think that this bug could be merged with #395359, #390038, #388696. Regards.

Bug#390038: Bug#395359: Post-removal script fails on purge of linux-image-2.6.17-2-amd64

I think that this bug can be merged with #390038 and #388696: they are about the same issue. And to add information to these bug reports, i have verified that also the 2.6.18 series has the same problem (tryed to purge linux-image-2.6.18-1-486 version 2.6.18-3): - (Reading da

Bug#393329: After seemingly successful install on Turion X2 system, freeze on boot

Carl Fink wrote: Removing the second SODIMM from the laptop had no effect, but removing the first (and swapping the second into slot #1) seems to have stopped the freezes, at least on ten minutes of work. So maybe a combination of kernel and hardware problems? Since you suspect ram problems, i

Bug#388696: linux-image-2.6.16-2-686: will not uninstall

Matthew Darwin wrote: Package: linux-image-2.6.16-2-686 Version: 2.6.16-18 Severity: normal % dpkg --purge linux-image-2.6.16-2-686 (Reading database ... 18837 files and directories currently installed.) Removing linux-image-2.6.16-2-686 ... Purging configuration files for linux-image-2.6.16-2-

Bug#366680: linux-image: snd_intel8x0 module randomly fails to initialize sound hardware

Benjamin A. Okopnik wrote: Since I didn't get copied on this reply (I just saw it after searching the BTS), I didn't get a chance to follow up to it earlier. I'd appreciate being CCd in the future, thanks. Sorry, was my mistake. This machine initially came with Wind0ws, and I used it that way

Bug#369622: linux-image-2.6.16-2-amd64-k8: Sound (snd_atiixp) no longer works

I don't the status of the bug or if someone has already replied, since bugs.debian.org seems down now. Ray Kohler wrote: Package: linux-image-2.6.16-2-amd64-k8 Version: 2.6.16-14 Severity: normal After installing this kernel upgrade, my sound no longer works. It is a builtin board which uses t

Bug#366680: linux-image: snd_intel8x0 module randomly fails to initialize sound hardware

Benjamin A. Okopnik wrote: The frequency of how often this happens varies: sometimes, it's every single boot until I remove the laptop battery; at other times, it's only about one boot out of every five. It seems to be related to IRQ problems (booting the laptop without its battery, and inserting

  1   2   >