On Sun, Jun 18, 2023 at 08:15:43AM +0900, Mike Hommey wrote:
> On Sun, Jun 18, 2023 at 06:09:57AM +0900, Mike Hommey wrote:
> > On Sat, Jun 17, 2023 at 01:20:30AM +0200, Diederik de Haas wrote:
> > > Control: tag -1 -moreinfo
> > > Control: found -1 6.1.20-1
> > &
On Sun, Jun 18, 2023 at 06:09:57AM +0900, Mike Hommey wrote:
> On Sat, Jun 17, 2023 at 01:20:30AM +0200, Diederik de Haas wrote:
> > Control: tag -1 -moreinfo
> > Control: found -1 6.1.20-1
> >
> > On Saturday, 17 June 2023 01:00:58 CEST Mike Hommey wrote:
> > &
On Sat, Jun 17, 2023 at 01:20:30AM +0200, Diederik de Haas wrote:
> Control: tag -1 -moreinfo
> Control: found -1 6.1.20-1
>
> On Saturday, 17 June 2023 01:00:58 CEST Mike Hommey wrote:
> > > 6.1.12-1 and 6.1.15-1 are good. 6.1.20-1 is the first broken one.
>
> Excelle
On Sat, Jun 17, 2023 at 07:59:17AM +0900, Mike Hommey wrote:
> On Sat, Jun 17, 2023 at 12:13:13AM +0200, Diederik de Haas wrote:
> > Control: tag -1 moreinfo
> >
> > On Fri Jun 16, 2023 at 11:21 PM CEST, Mike Hommey wrote:
> > > Package: src:linux
> > &
On Sat, Jun 17, 2023 at 12:13:13AM +0200, Diederik de Haas wrote:
> Control: tag -1 moreinfo
>
> On Fri Jun 16, 2023 at 11:21 PM CEST, Mike Hommey wrote:
> > Package: src:linux
> > Version: 6.1.27-1
> >
> > After upgrading to bookworm, my bluetooth trackpad s
Package: src:linux
Version: 6.1.27-1
Severity: important
Dear Maintainer,
After upgrading to bookworm, my bluetooth trackpad stopped working. It's
properly connected, and `libinput list-devices` displays this message:
event15 - Logitech Rechargeable Trackpad T651: kernel bug: device has min ==
severity 992219 important
retitle 992219 Cannot open
/usr/src/linux-headers-5.13.0-trunk-common/scripts/modules-check.sh: No such
file
thanks
On Sun, Aug 15, 2021 at 06:48:02PM -0600, Antonio Russo wrote:
> Control: severity -1 wishlist
> Control: retitle -1 Please backport support for 5.13
>
Hi,
Are you planning an update in buster-backports, too?
Cheers,
Mike
On Sun, Jan 05, 2020 at 01:45:49PM +0100, Salvatore Bonaccorso wrote:
> Hi
>
> I'm intenting to upload linux version 5.4.8-1 to unstable today
> (Sunday) unless some surprises arise. As perfering to move to the new
> stable
On Thu, Oct 25, 2018 at 03:20:11PM +0900, Mike Hommey wrote:
> Package: linux-perf-4.18
> Version: 4.18.10-2
> Severity: wishlist
> File: /usr/bin/perf_4.18
>
> Dear Maintainer,
>
> Running e.g. perf report with dwarf call graph info can take a long time
> depending
Package: linux-perf-4.18
Version: 4.18.10-2
Severity: wishlist
File: /usr/bin/perf_4.18
Dear Maintainer,
Running e.g. perf report with dwarf call graph info can take a long time
depending on the size of the profile and the size of dwarf info in the
binaries being profiled. That's because each
Package: firmware-iwlwifi
Version: 20151207-1
Severity: normal
# dmesg | grep iwlwifi | head -5
[7.473576] iwlwifi :06:00.0: enabling device ( -> 0002)
[7.475332] iwlwifi :06:00.0: firmware: failed to load
iwlwifi-7260-17.ucode (-2)
[7.475337] iwlwifi :06:00.0: Direct
Package: src:linux
Version: 3.18-1~exp1
Severity: important
Preliminary note: this works fine with linux-image-3.16.0-4-amd64 and all
versions before that.
My setup involves a luks encrypted root file system, so I get a prompt
during boot for the passphrase. When booting with the kernel from
On Tue, Dec 16, 2014 at 09:22:42AM +0900, Mike Hommey wrote:
Package: src:linux
Version: 3.18-1~exp1
Severity: important
Preliminary note: this works fine with linux-image-3.16.0-4-amd64 and all
versions before that.
My setup involves a luks encrypted root file system, so I get a prompt
On Sat, Dec 01, 2012 at 10:17:54PM +, Ben Hutchings wrote:
On Thu, 2012-11-29 at 23:40 +0100, Mike Hommey wrote:
Package: linux-tools-3.6
Version: 3.6-1~experimental.1
Severity: important
debian/build/tools/perf/Makefile reads:
else ifeq ($(DEB_HOST_ARCH_CPU),amd64
On Sat, Dec 01, 2012 at 10:50:22PM +, Ben Hutchings wrote:
On Sat, 2012-12-01 at 23:42 +0100, Mike Hommey wrote:
On Sat, Dec 01, 2012 at 10:17:54PM +, Ben Hutchings wrote:
On Thu, 2012-11-29 at 23:40 +0100, Mike Hommey wrote:
Package: linux-tools-3.6
Version: 3.6-1
Package: linux-tools-3.6
Version: 3.6-1~experimental.1
Severity: important
debian/build/tools/perf/Makefile reads:
else ifeq ($(DEB_HOST_ARCH_CPU),amd64)
KERNEL_ARCH_PERF = x86
This should really be:
else ifeq ($(DEB_HOST_ARCH_CPU),amd64)
KERNEL_ARCH_PERF = x86_64
Because
On Thu, Nov 29, 2012 at 11:40:29PM +0100, Mike Hommey wrote:
Package: linux-tools-3.6
Version: 3.6-1~experimental.1
Severity: important
debian/build/tools/perf/Makefile reads:
else ifeq ($(DEB_HOST_ARCH_CPU),amd64)
KERNEL_ARCH_PERF = x86
This should really be:
else ifeq
On Sun, May 20, 2012 at 02:00:21PM +0100, Ben Hutchings wrote:
On Sun, 2012-05-20 at 11:27 +0200, Goswin von Brederlow wrote:
Ben Hutchings b...@decadent.org.uk writes:
Most new PCs have an Intel or AMD 64-bit processor, and
popcon.debian.org shows amd64 numbers almost matching i386.
On Mon, Dec 06, 2010 at 08:44:14AM +0100, Mike Hommey wrote:
On Mon, Dec 06, 2010 at 04:25:13AM +, Ben Hutchings wrote:
On Thu, 2010-12-02 at 13:39 +0100, Mike Hommey wrote:
Is the following going to be considered for squeeze?
I've cherry-picked all the necessary changes (I think
On Mon, Dec 06, 2010 at 04:25:13AM +, Ben Hutchings wrote:
On Thu, 2010-12-02 at 13:39 +0100, Mike Hommey wrote:
Is the following going to be considered for squeeze?
I've cherry-picked all the necessary changes (I think):
8b6d043b7ee2d1b819dc833d677ea2aead71a0c0 resource: shared I/O
On Mon, Nov 29, 2010 at 07:18:17AM +0100, Guillem Jover wrote:
What's going on here? sync_file_range() is a Linux specific system
call that has been around for a while. It allows program to control
when writeback happens in a very low-level fashion. The first set of
sync_file_range()
On Tue, Nov 30, 2010 at 10:35:11AM +0100, Samuel Thibault wrote:
Mike Hommey, le Tue 30 Nov 2010 10:07:55 +0100, a écrit :
On Mon, Nov 29, 2010 at 07:18:17AM +0100, Guillem Jover wrote:
What's going on here? sync_file_range() is a Linux specific system
call that has been around
On Sun, Nov 21, 2010 at 09:18:04AM +0100, Raphael Hertzog wrote:
On Sun, 21 Nov 2010, Ben Hutchings wrote:
I'm coming to this late. It sounds like dpkg has changed its behaviour
several times recently. Please can you summarise dpkg's current and
proposed use of fsync() vs sync(), and the
On Thu, Oct 14, 2010 at 03:26:08PM +0200, Mike Hommey wrote:
Package: linux-2.6
Version: 2.6.32-24
Severity: normal
The btrfs tool, which is the canonical tool for btrfs handling, doesn't
have a useful output for btrfs filesystem df because the necessay ioctl
isn't available in 2.6.32
Package: linux-2.6
Version: 2.6.32-26
Severity: wishlist
This is a followup from bug 597820. I would like to get the watchdog
support for f71889fg with a squeeze kernel. The support for that chip
isn't yet upstream, and I understand that you wouldn't want to include
it (yet). However, it would be
On Mon, Oct 04, 2010 at 09:44:28AM +0200, Mike Hommey wrote:
On Mon, Oct 04, 2010 at 09:29:20AM +0200, Mike Hommey wrote:
Right, it seems that I forgot a single break-statement (causing the
driver to fall through to the undetected part). Attached patch has this
fixed and should work
Package: linux-2.6
Version: 2.6.32-24
Severity: normal
The btrfs tool, which is the canonical tool for btrfs handling, doesn't
have a useful output for btrfs filesystem df because the necessay ioctl
isn't available in 2.6.32. Would you consider adding it?
1406e4327be3a533a2b18582f715ce2cfbcf6804
On Sun, Oct 03, 2010 at 02:02:32PM +0200, Giel van Schijndel wrote:
On Sun, Oct 03, 2010 at 09:14:44AM +0200, Mike Hommey wrote:
On Sun, Oct 03, 2010 at 01:14:24AM +0200, Giel van Schijndel wrote:
On Sat, Oct 02, 2010 at 08:42:19PM +0100, Ben Hutchings wrote:
On Tue, 2010-09-28 at 10:36
On Sun, Oct 03, 2010 at 02:47:11PM +0200, Giel van Schijndel wrote:
On Sun, Oct 03, 2010 at 11:21:42AM +0200, Mike Hommey wrote:
On Sun, Oct 03, 2010 at 01:33:23AM +0200, Giel van Schijndel wrote:
On Sun, Oct 03, 2010 at 01:14:24AM +0200, Giel van Schijndel wrote:
On Sat, Oct 02, 2010 at 08
On Mon, Oct 04, 2010 at 09:29:20AM +0200, Mike Hommey wrote:
Right, it seems that I forgot a single break-statement (causing the
driver to fall through to the undetected part). Attached patch has this
fixed and should work properly.
I may have fucked up, but it looks like it doesn't work
On Sun, Oct 03, 2010 at 01:14:24AM +0200, Giel van Schijndel wrote:
On Sat, Oct 02, 2010 at 08:42:19PM +0100, Ben Hutchings wrote:
On Tue, 2010-09-28 at 10:36 +0200, Mike Hommey wrote:
On Thu, Sep 23, 2010 at 12:36:04PM +0200, Mike Hommey wrote:
Package: linux-2.6
Version: 2.6.32-23
On Sun, Oct 03, 2010 at 01:33:23AM +0200, Giel van Schijndel wrote:
On Sun, Oct 03, 2010 at 01:14:24AM +0200, Giel van Schijndel wrote:
On Sat, Oct 02, 2010 at 08:42:19PM +0100, Ben Hutchings wrote:
On Tue, 2010-09-28 at 10:36 +0200, Mike Hommey wrote:
I would also be interested
On Thu, Sep 23, 2010 at 12:36:04PM +0200, Mike Hommey wrote:
Package: linux-2.6
Version: 2.6.32-23
Severity: wishlist
Tags: squeeze
I installed a fresh squeeze on a new PC with a MSI P55M-GD45 motherboard
that uses a f71889fg sensor chip. Unfortunately, while lm-sensors'
sensor-detect
Package: linux-2.6
Version: 2.6.32-23
Severity: wishlist
Tags: squeeze
I installed a fresh squeeze on a new PC with a MSI P55M-GD45 motherboard
that uses a f71889fg sensor chip. Unfortunately, while lm-sensors'
sensor-detect is able to find the chip and suggest a kernel module, the
module doesn't
On Tue, Dec 08, 2009 at 08:55:34AM +0100, Reinhard Karcher wrote:
Status update for kernel-image-2.6.32-trunk-amd64:
things improved a little bit. Console switching is now possible, but in
X only a black screen is visible, with the exception of the mouse
cursor, which is visible and moves
On Mon, Mar 30, 2009 at 01:11:52AM +0200, maximilian attems wrote:
On Sat, 28 Mar 2009, Mike Hommey wrote:
On Wed, Mar 28, 2007 at 12:19:49AM +0200, maximilian attems wrote:
# Automatically generated email from bts, devscripts version 2.9.26
tags 416063 - patch
Would you mind
On Wed, Mar 28, 2007 at 12:19:49AM +0200, maximilian attems wrote:
# Automatically generated email from bts, devscripts version 2.9.26
tags 416063 - patch
Would you mind explaining?
The patch solves two issues:
- inconsistency between documentation and behaviour:
You can read the
On Fri, Oct 24, 2008 at 01:15:10AM +0200, Frank Lin PIAT wrote:
Hello,
[CC'ing since someone may have the answer]
I have just tested Lenny on a laptop[1] with an Intel Pro Wireless 2200
chipset. As you probably known the kernel module ipw2200 requires a
non-free firmware.
I'm wondering
On Wed, Feb 06, 2008 at 03:37:05PM +, Sam Morris wrote:
Package: linux-image-2.6.24-1-686
Version: 2.6.24-2
Severity: important
Since upgrading to 2.6.24, my laptop keeps locking up for short periods
of time. I have noticed that the following kernel messages are logged
about 30 times
On Thu, Feb 14, 2008 at 05:17:08PM -0200, Otavio Salvador wrote:
Mike Hommey [EMAIL PROTECTED] writes:
On Thu, Feb 14, 2008 at 07:56:55PM +0100, maximilian attems wrote:
On Thu, 14 Feb 2008, Otavio Salvador wrote:
Hello RM and SRM teams,
I hereby ask for a block on linux-2.6
Package: initramfs-tools
Followup-For: Bug #366175
I got the same issue here. Why not solve the problem by adding calls to
lvm initialization in the Waiting for root filesystem loop ?
A workaround is to add break=mount to the kernel command line, wait for
the usb disk to come up and just exit,
On Sun, Dec 16, 2007 at 04:00:50PM +0100, maximilian attems wrote:
On Sun, 16 Dec 2007, Mike Hommey wrote:
I got the same issue here. Why not solve the problem by adding calls to
lvm initialization in the Waiting for root filesystem loop ?
A workaround is to add break=mount
On Mon, Apr 09, 2007 at 08:43:00PM +0200, Bas Zoetekouw [EMAIL PROTECTED]
wrote:
Package: linux-2.6
Severity: wishlist
Could you please enable CONFIG_BLK_DEV_IO_TRACE in the default debian
kernel?
It's needed for blktrace, which I'm planning to upload to unstable
soonish, now that the
Package: linux-image-2.6.21-1-686
Version: 2.6.21-1~experimental.1~snapshot.8516
Severity: wishlist
Please enable CONFIG_TIMER_STATS in 2.6.21 kernel packages, so that
powertop can display useful information to help users and developers to
tackle applications preventing more idle time.
See
]
On Tue, Oct 24, 2006 at 08:41:38PM +0200, Mike Hommey wrote:
When installing a new kernel over the currently running one, and suspend to
disk is enabled, the system will fail to resume with the newer kernel at
resuming time. It would be safer if it was impossible to suspend to disk
On Wed, Oct 25, 2006 at 09:39:13AM +0200, maximilian attems [EMAIL PROTECTED]
wrote:
reassign 395086 kernel-package
retitle 395086 disable swsusp on new linux-image install
stop
On Wed, Oct 25, 2006 at 08:36:38AM +0200, Mike Hommey wrote:
On Tue, Oct 24, 2006 at 08:41:38PM +0200, Mike
Package: linux-image-2.6.18-1-686
Version: 2.6.18-3
Severity: wishlist
When installing a new kernel over the currently running one, and suspend to
disk is enabled, the system will fail to resume with the newer kernel at
resuming time. It would be safer if it was impossible to suspend to disk
Version: 2.6.18-2
This is fixed in 2.6.18-2. Therefore closing now.
Is 2.6.18-2+ kernels intended to be released with etch ? If not, this bug
should be reopened to be fixed in the kernel package that will be shipped.
Mike
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
On Tue, Aug 08, 2006 at 06:49:32AM +0200, Sven Luther [EMAIL PROTECTED] wrote:
On Mon, Aug 07, 2006 at 04:46:09PM -0700, Thomas Bushnell BSG wrote:
[EMAIL PROTECTED] (Marco d'Itri) writes:
On Aug 08, Thomas Bushnell BSG [EMAIL PROTECTED] wrote:
We Do Not Distribute Non-Free Software
Package: linux-image-2.6.16-1-xen-686
Severity: normal
As said in the subject, the /boot/config-2.6.16-1-xen-686 file is not
shipped in the package.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:
On Mon, Apr 17, 2006 at 12:29:04AM +0200, Bastian Blank [EMAIL PROTECTED]
wrote:
Hi folks
For sarge updates of the linux kernels, grub needs to be updated before
linux-image*. Can this be forced by an conflict with older versions? A
dependency is not appropriate.
Why does grub have to be
On Sat, Feb 11, 2006 at 10:33:32AM +0100, Marco d'Itri [EMAIL PROTECTED]
wrote:
I also plan a GR to accept in main less free artwork which if removed
does not change the functionality of the software using it (e.g. the
firefox logo).
The main problem with the firefox logo is not its
Package: kernel-image-2.6.10-1-686
Version: 2.6.10-4
Severity: normal
Preliminary note: this didn't happen with 2.6.9.
When suspending to RAM for a quite long time (like, the whole night),
at wake up time, the clock is far ahead. It seems to be running twice as
fast, actually, because it was 10
On Thu, Dec 02, 2004 at 08:33:32AM +1100, Brian May [EMAIL PROTECTED] wrote:
Mike == Mike Hommey [EMAIL PROTECTED] writes:
Mike On Wed, Dec 01, 2004 at 01:33:32PM +0100, Marco d'Itri
Mike [EMAIL PROTECTED] wrote:
This is not a problem
(/etc/hotplug/blacklist.d/kernel
On Wed, Dec 01, 2004 at 06:48:35PM +0900, Horms [EMAIL PROTECTED]
wrote:
If the blacklist exists for other devices, then yes this sounds like a
good idea. The e100 should be used over the eepro100 as the later is
in the process of being debricated upstream.
The problem is the following: is the
55 matches
Mail list logo