Bug#1063468: linux-image-6.1.0-17-amd64: Loud squeals/crackles from Steelseries 2 Channel HD Audio chipset after restarting from Windows 11

2024-02-08 Thread Luke Feetham
f the linux kernel. I have tested this problem within live environments of both Kubuntu 23.10 (kernel 6.5.0-9-generic) and Fedora 39 (kernel 6.5.6-300.fc39.x86_64). Again, this is whenever I restart from Windows 11. Please let me know if you need further information. Best regards Luke Laptop

Bug#986887: linux-image-5.10.0-5-amd64: mpt3sas driver fails to initialize drives on LSI SAS2116 chipset without a queue depth workaround

2021-04-13 Thread Luke Reeves
Package: src:linux Version: 5.10.26-1 Severity: important Tags: upstream X-Debbugs-Cc: luke.ree...@gmail.com Dear Maintainer, I've upgraded from Buster to Bullseye and my external drive array using an LSI SAS2116 chipset (and the mpt3sas driver) stopped detecting all drives. There were no error

Bug#955022: i915: Frequent graphics lockups; GPU HANG: ecode 9:1:0x00000000, hang on rcs0

2020-03-26 Thread Luke Faraone
9.2.1 20200117 (Debian 9.2.1-24)) #1 SMP Debian 5.4.13-1 (2020-01-19) [3]: https://gitlab.freedesktop.org/drm/intel/issues/673 [4]: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395 Please let me know if there's any additional information I can provide. Cheers, Luke Farao

Bug#901006: closed by Ben Hutchings (Re: Bug#901006: linux-image-4.16.0-2-amd64: "core has locked up" kernel messagee)

2018-06-07 Thread Luke Kenneth Casson Leighton
On Fri, Jun 8, 2018 at 2:27 AM, Debian Bug Tracking System wrote: > -- Forwarded message -- > From: Ben Hutchings > To: 901006-d...@bugs.debian.org > Cc: > Bcc: > Date: Fri, 08 Jun 2018 02:24:57 +0100 > Subject: Re: Bug#901006: linux-image-4.16.0-2-amd64: "core has locked up" > k

Re: UPDATE: Re: Proposal: UEFI secure boot implementation sprint, 5-8 April 2018

2018-02-05 Thread Luke W Faraone
On 28/01/18 11:46, Steve McIntyre wrote: > On Sun, Jan 21, 2018 at 05:49:20PM +, Steve McIntyre wrote: >> >> We have 7 people with dates in the poll so far: >> >> Helen Koike >> Luke Faraone >> Me >> Ben Hutchings >> Tollef Fog Heen

Re: Proposal: UEFI secure boot implementation sprint, early 2018

2017-12-04 Thread Luke Faraone
and in Berlin through 4 January. Happy to do something in the 1-4 January timeframe, or alternatively some time in February or March. > c) ideas on when/where we could meet up, if you have any I'd probably get in to Europe SFO→AMS, so Essen would be easier than Fulda :) -- Luke Far

Bug#856843:

2017-04-10 Thread Luke Suchocki
he TCP session will be reestablished as soon as the connection is reset, but echos are not required until "real" SMB services are requested again by the client... --Luke Suchocki

Bug#856843:

2017-04-06 Thread Luke Suchocki
cond point. The other 25k are in the next 5 seconds until I stopped the trace. Believe it or not, my workaround is to add: */5 * * * * ls -l /mnt/ftp to my crontab, and that keeps the CIFS connection active enough to prevent this. --Luke Suchocki

Bug#855558: linux-image-4.9.0-1-amd64: ACPI boot error causes /sbin/init to segfault (!)

2017-02-22 Thread Luke Kenneth Casson Leighton
faakin 'ell :) woo, ok. setting acpi_os_name="Windows 2009" and also removing vesafb from /etc/initramfs-tools/modules resulted in a boot (attaching dmesg boot which contains two ACPI-related kernel-level warnings). sorry it's an attachment rather than inline. i don't know if it was the setting

Bug#855558: linux-image-4.9.0-1-amd64: ACPI boot error causes /sbin/init to segfault (!)

2017-02-22 Thread Luke Kenneth Casson Leighton
--- crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68 On Wed, Feb 22, 2017 at 12:06 PM, Ben Hutchings wrote: > Control: retitle -1 linux-image-4.9.0-1-amd64: Failed to execute /init > Control: tag -1 moreinfo > > On Mon, 20 Feb 2017 04:00:03 + lkcl wrote: >> Package: s

Bug#855558: linux-image-4.9.0-1-amd64: ACPI boot error causes /sbin/init to segfault (!)

2017-02-22 Thread Luke Kenneth Casson Leighton
http://www.linuxquestions.org/questions/linux-from-scratch-13/acpi-errors-when-booting-927408/ ah christ almighty, they're talking about "updating the bios fixes the problem" *sigh*. 3.16, 4.7 and 4.8 are all fine - so wtf is 4.9 doing not being capable of running /init when all prior version can

Bug#855818: linux-image-4.8.0-2-amd64: segfault in intel 9815 drm kernel module

2017-02-21 Thread Luke Kenneth Casson Leighton
--- crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68 On Wed, Feb 22, 2017 at 2:38 AM, Ben Hutchings wrote: > Control: tag -1 - upstream > Control: tag -1 moreinfo > > On Wed, 2017-02-22 at 01:45 +, lkcl wrote: >> Package: src:linux >> Version: 4.8.15-2 >> Severity: nor

Bug#829602: solved

2016-08-03 Thread Luke
The problem is solved installing skylake graphics microcode from 01.org and installing xserver-xorg-video-intel. Details can be found here: https://wiki.debian.org/InstallingDebianOn/Thinkpad/X1%20Carbon%204thGen %20PCIe_SSD/jessie

Bug#776959: linux-image-3.16.0-4-amd64: [regression] sd card reader in retina macbook pro no longer working

2015-02-03 Thread Luke Kenneth Casson Leighton
On Tue, Feb 3, 2015 at 7:58 PM, Ben Hutchings wrote: > Control: tag -1 important > > On Tue, 2015-02-03 at 15:39 +, lkcl wrote: >> Package: src:linux >> Version: 3.16.7-ckt2-1 >> Severity: important >> >> after upgrading from 3.13 where the built-in sd card worked perfectly, >> there is no lon

Bug#776959: linux-image-3.16.0-4-amd64: [regression] sd card reader in retina macbook pro no longer working

2015-02-03 Thread Luke Kenneth Casson Leighton
On Tue, Feb 3, 2015 at 9:28 PM, Luke Kenneth Casson Leighton wrote: > On Tue, Feb 3, 2015 at 7:58 PM, Ben Hutchings wrote: >> Control: tag -1 important >> >> On Tue, 2015-02-03 at 15:39 +, lkcl wrote: >>> Package: src:linux >>> Version: 3.16.7-ckt2-

Bug#745147: closed by Ben Hutchings (Re: WARNING on removal of SCSI device which is still in use)

2014-09-24 Thread Luke Kenneth Casson Leighton
thanks for keeping an eye on this ben On Wed, Sep 24, 2014 at 2:42 PM, Debian Bug Tracking System wrote: > Subject: Re: WARNING on removal of SCSI device which is still in use > Version: 3.15~rc5-1~exp1 > > This is supposed to be fixed in 3.15-rc1 by: > > commit e63ed0d7a98014fdfc2cfeb3f6dada31

Bug#744994: linux-image-3.13-1-amd64: segfault on use of external (usb) dvdrw

2014-04-18 Thread Luke Kenneth Casson Leighton
On Fri, Apr 18, 2014 at 2:11 PM, Ben Hutchings wrote: >> Apr 17 09:24:08 teenymac kernel: [1201449.213969] usb 2-5: USB disconnect, >> device number 18 > > Drive removed. yes. bit of a melt-down on another USB hub, i had to unplug it (and the attached nothing-to-do-with-the-USB-DVD-drive USB h

Re: Bug#730482: linux-image-3.9.6: PCI/USB reset not being done on Geode LX800 / CS5536

2013-11-28 Thread Luke Kenneth Casson Leighton
On Thu, Nov 28, 2013 at 9:22 AM, Andrei POPESCU wrote: > Hi Kernel Maintainers, > > Since the package doesn't exist this landed in the wrong place. Could > you please have a look and take over the bug if useful? thanks andrei. i've since observed that the two ethernet ports of the alix6f2 (whic

CONFIG_GPIO_SYSFS

2013-11-27 Thread Luke Leighton
hi all, i'm doing an embedded remote firewall/router and "management" system (preliminary approval's been obtained to release the code as GPL at some point) using a pc-engines alix6f2 (AMD Geode LX800), and have had to make the rather unfortunate and necessary decision to custom-compile the kernel

Re: ARM kernel config for Linux 3.11

2013-09-15 Thread Luke Kenneth Casson Leighton
On Sun, Sep 15, 2013 at 4:42 PM, Ben Hutchings wrote: > As discussed previously, I think PCI should be enabled for the > armhf/armmp flavour as the Marvell Armada SoCs have PCIe interfaces. and the freescale iMX6, and one of the samsung SoCs (the exynos5), and the TI AM3389 (although that's a bi

Bug#721924: Acknowledgement (linux-image-3.10-2-amd64: btrfs writing several small files causes massive load spike)

2013-09-05 Thread Luke Kenneth Casson Leighton
https://bugzilla.kernel.org/show_bug.cgi?id=60860 cf upstream bugreport. On Thu, Sep 5, 2013 at 3:36 PM, Debian Bug Tracking System wrote: > Thank you for filing a new Bug report with Debian. > > This is an automatically generated reply to let you know your message > has been received. > > Your

Bug#715370: Acknowledgement (linux-image-3.9-1-486: CONFIG_GPIO_CS5535 has been set to 'y' when it should be 'M')

2013-07-08 Thread Luke Kenneth Casson Leighton
right. having enormous difficulty tracking this down, but there appears to be some kernel config dependencies of CONFIG_GPIO_CS5535 which are set to "Y" which are forcing CONFIG_GPIO_CS5535 to "y". ... but that actually turns out not to be the main problem: the main problem is that although GPIO_

Re: [Arm-netbook] getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-07 Thread Luke Kenneth Casson Leighton
On Fri, Jun 7, 2013 at 8:35 PM, Russell King - ARM Linux wrote: > On Fri, Jun 07, 2013 at 08:18:14PM +0100, Luke Kenneth Casson Leighton wrote: >> On Fri, Jun 7, 2013 at 7:26 PM, Russell King - ARM Linux >> wrote: >> > Luke Leighton on the other hand is demanding that w

Re: [Arm-netbook] getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-07 Thread Luke Kenneth Casson Leighton
On Fri, Jun 7, 2013 at 7:26 PM, Russell King - ARM Linux wrote: > Luke Leighton on the other hand is demanding that we no demands have been made, russell: i've informed you of an immovable deadline which will pass beyond which the opportunity being presented is lost. > (L

Re: getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread Luke Kenneth Casson Leighton
On Thu, Jun 6, 2013 at 12:27 AM, Tomasz Figa wrote: >> their sheer overwhelming success provides us with mass-volume >> ultra-low cost hardware. to not make an effort to accommodate them >> would in this specific instance be a huge missed opportunity, > OK, this is a large volume of hardware t

Re: getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread Luke Kenneth Casson Leighton
[removing debian-release again - at their request] On Wed, Jun 5, 2013 at 11:11 PM, Tomasz Figa wrote: > Allwinner has just reinvented a wheel, without even considering the fact > that it has been already invented. apologies, tomasz, but i believe i covered this issue in, again, my reply to rus

Re: getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread Luke Kenneth Casson Leighton
On Wed, Jun 5, 2013 at 10:52 PM, Tomasz Figa wrote: > Hi Luke, allo tomasz :) ok - much of what you say is duplicated by what russell said, so in effect the same reply is relevant, but there's been some cross-over. i'll summarise below and cut all but the key question below:

Re: getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread Luke Kenneth Casson Leighton
t; (all Tegra to some extent, and a couple each Samsung Exynos and Xilinx >> boards). I suspect/guess this is the kind of thing that Luke was >> referring to re: U-Boot fex integration. > > Reading what I have of this thread, this is just another case of > $company runs of and do

Re: getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread Luke Kenneth Casson Leighton
[ please remove debian-release from future replies! my mistake - please don't propagate it, thanks ] On Wed, Jun 5, 2013 at 10:00 PM, Stephen Warren wrote: > On 06/05/2013 02:46 PM, jonsm...@gmail.com wrote: >> On Wed, Jun 5, 2013 at 3:46 PM, Luke Kenneth Casson Leighton >>

Re: getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread Luke Kenneth Casson Leighton
[i've just received word, please remove debian-release from discussions!] On Wed, Jun 5, 2013 at 9:46 PM, jonsm...@gmail.com wrote: > Why don't you try converting the sunxi code over to device tree? ok. perhaps i wasn't clear. whatever is proposed has to be be acceptable to allwinner, and i'm

getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread Luke Kenneth Casson Leighton
On Fri, May 31, 2013 at 3:52 AM, Ben Hutchings wrote: > The 3.8.y branch is over, so I think we have to move to 3.9, ready or > not. I merged the work in progress from trunk to sid and am going > through the config changes at the moment. > > I'm rather disappointed that nothing at all has been c

Bug#706476: Info received (Bug#706476: Info received (Bug#706476 closed by Ben Hutchings (Re: Bug#706476: linux-image-3.2.0-4-486: amd geode gpio-cs5535 module not being compile

2013-05-02 Thread Luke Kenneth Casson Leighton
ok, it turns out that CONFIG_SYSFS_GPIO is "safe", because you have to explicitly take action in order to make GPIO accessible (export). following the instructions here was easy to do: https://sites.google.com/site/bifferboard/Home/gpio so, basically, CONFIG_SYSFS_GPIO could be switched on (as bui

Bug#706476: Info received (Bug#706476 closed by Ben Hutchings (Re: Bug#706476: linux-image-3.2.0-4-486: amd geode gpio-cs5535 module not being compiled (needed for alix6f2)))

2013-05-01 Thread Luke Kenneth Casson Leighton
i've added these at the end of debian/config/i386/none/config.i486 and then checked debian/build/build_i386_none_486/.config but CONFIG_GPIO_CS5535 had been modified to "y", ah well. fakeroot make -f debian/rules.gen -j16 binary-arch_i386_none_486 still running... # # GPIOLIB and SYSFS # CONFIG_

Bug#706476: closed by Ben Hutchings (Re: Bug#706476: linux-image-3.2.0-4-486: amd geode gpio-cs5535 module not being compiled (needed for alix6f2))

2013-05-01 Thread Luke Kenneth Casson Leighton
On Wed, May 1, 2013 at 10:56 AM, Luke Kenneth Casson Leighton wrote: >> It *is* still enabled, but it's built-in on the 486 flavour because >> OLPC_XO1_SCI selects it. > > thanks ben... investigating further: > > # PCI GPIO expanders: > # > CONFIG_GPIO_CS553

Bug#706476: closed by Ben Hutchings (Re: Bug#706476: linux-image-3.2.0-4-486: amd geode gpio-cs5535 module not being compiled (needed for alix6f2))

2013-05-01 Thread Luke Kenneth Casson Leighton
On Wed, May 1, 2013 at 3:33 AM, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the linux-image-3.2.0-4-486 package: > > #706476: linux-image-3.2.0-4-486: amd geode gpio-cs5535 module not being > compiled (needed for alix6f

Bug#706476: linux-image-3.2.0-4-486: amd geode gpio-cs5535 module not being compiled (needed for alix6f2)

2013-04-30 Thread Luke Kenneth Casson Leighton
On Tue, Apr 30, 2013 at 6:39 PM, Ben Hutchings wrote: > On Tue, Apr 30, 2013 at 05:22:56PM +0100, lkcl wrote: >> Package: linux-image-3.2.0-4-486 >> Severity: important >> >> >> discovered from another debian bugreport that pc-engines systems can be >> upgraded to more recent firmware and work wit

Re: Bug#636123: Info received (Bug#636123: linux-image-2.6.39-2-amd64: root filesystem not recognised -> new bug report)

2011-10-04 Thread Luke Kenneth Casson Leighton
right - _finally_ i've encountered a requirement to upgrade a 2nd system that has lvm2 and (in this 2nd case 2.6.18-486) a linux kernel image, and have encountered the *exact* same problem as is in bugs 636123 and 638896. this time, however, i was anticipating that something might go wrong, so was

Bug#640650: closed by dann frazier (Bug#640650: fixed in user-mode-linux 2.6.32-1um-4+37)

2011-09-30 Thread Luke-Jr
But these (642380 also) were OpenVZ, not UML... -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201109301635.32894.l...@dashjr.org

Bug#642380: Cannot chkpnt (live migrate) VEs

2011-09-22 Thread Luke-Jr
On Thursday, September 22, 2011 10:21:30 AM Ben Hutchings wrote: > Looking at the OpenVZ patch for the RHEL 6 kernel (which is what > Parallels is selling), I see that ext4 has been added to the accepted > list and doesn't require special handling. So I think we could add it > in Debian. Thanks.

Bug#642380: Cannot chkpnt (live migrate) VEs

2011-09-21 Thread Luke-Jr
On Wednesday, September 21, 2011 10:55:42 PM Ben Hutchings wrote: > If OpenVZ doesn't support migration of ext4, you'll have to use another > filesystem for the containers. According to http://openvz.org/pipermail/users/2008-January/001669.html , this is a meaningless check (in kernel/cpt/cpt_fil

Bug#642381: Impossible to interact with VE connection tracking?

2011-09-21 Thread Luke-Jr
Package: linux-image-2.6.32-5-openvz-amd64 Within Virtual Environments (VEs) only... The conntrack userland tool gets "Connection refused" on the netlink socket required to interact (list, flush, etc) with connection tracking. The old procfs interface is no longer supported in 2.6.32. P.S. Is t

Bug#642380: Cannot chkpnt (live migrate) VEs

2011-09-21 Thread Luke-Jr
Package: linux-image-2.6.32-5-openvz-amd64 *** Please type your report below this line *** # vzctl chkpnt 132 Setting up checkpoint... suspend... Can not suspend container: Invalid argument Error: unsupported fs type ext4 Checkpointing failed -- Package-specific info: ** Version: Linux v

Bug#640650: linux-image-2.6.32-5-openvz-amd64: kernel NULL pointer dereference

2011-09-06 Thread Luke-Jr
On Tuesday, September 06, 2011 12:20:17 PM Ben Hutchings wrote: > On Tue, Sep 06, 2011 at 11:06:24AM -0400, Luke-Jr wrote: > > On Tuesday, September 06, 2011 9:41:05 AM Ben Hutchings wrote: > > > I understand this and found a patch that should fix it. > > > > Is thi

Bug#640650: linux-image-2.6.32-5-openvz-amd64: kernel NULL pointer dereference

2011-09-06 Thread Luke-Jr
On Tuesday, September 06, 2011 9:41:05 AM Ben Hutchings wrote: > I understand this and found a patch that should fix it. Is this a security vulnerability, or am I safe to assume my system was not exploited at least through this issue? -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.de

Bug#640650: linux-image-2.6.32-5-openvz-amd64: kernel NULL pointer dereference

2011-09-05 Thread Luke
Package: linux-2.6 Version: 2.6.32-35 Severity: important [5353473.940460] BUG: unable to handle kernel NULL pointer dereference at 0070 [5353473.940511] IP: [] d_instantiate+0x10/0x3c [5353473.940544] PGD 4a7592067 PUD 44b0d8067 PMD 0 [5353473.940575] Oops: [#1] SMP [5353473.

Bug#638896: Fw: linux-image-2.6.39-bpo.2-amd64 root filesystem not found on boot

2011-08-22 Thread Luke Kenneth Casson Leighton
On Mon, Aug 22, 2011 at 10:02 PM, Luke Kenneth Casson Leighton wrote: >> From: Valentijn Scholten >> Sent: Monday, August 22, 2011 10:45 PM >> To: 638...@bugs.debian.org >> Subject: Re: linux-image-2.6.39-bpo.2-amd64 root filesystem not found on >> boot >> >

Bug#638896: clarification

2011-08-22 Thread Luke Kenneth Casson Leighton
> After making some backups, I tried to upgrade the kernel again. > Guess what? It just works now. arghhh! valentijn, that's *exactly* the "mistake" that i made :) actually in my case, i installed grub (and lvm2) which triggered off the postinst initramfs-tools hook. you cannot "back-recover

Bug#636123: linux-image-2.6.39-2-amd64: root filesystem not recognised -> new bug report

2011-08-22 Thread Luke Kenneth Casson Leighton
On Mon, Aug 22, 2011 at 8:30 PM, Valentijn Scholten wrote: > I opened a new bug report: > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638896 thanks valentijn. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@

Re: Bug#636123: linux-image-2.6.39-2-amd64: root filesystem (LVM) not recognised

2011-08-22 Thread Luke Kenneth Casson Leighton
On Mon, Aug 22, 2011 at 7:54 PM, Ben Hutchings wrote: > On Mon, Aug 22, 2011 at 07:44:35PM +0100, Luke Kenneth Casson Leighton wrote: >> On Mon, Aug 22, 2011 at 7:35 PM, Ben Hutchings wrote: >> > On Mon, Aug 22, 2011 at 06:56:16PM +0100, Luke Kenneth Casson Leighton >>

Bug#636123: linux-image-2.6.39-2-amd64: root filesystem (LVM) not recognised

2011-08-22 Thread Luke Kenneth Casson Leighton
On Mon, Aug 22, 2011 at 8:02 PM, Ben Hutchings wrote: > On Mon, Aug 22, 2011 at 07:55:28PM +0100, Luke Kenneth Casson Leighton wrote: >> On Mon, Aug 22, 2011 at 7:42 PM, Luke Kenneth Casson Leighton >> wrote: >> > On Mon, Aug 22, 2011 at 7:21 PM, Valentijn Scholten >&

Re: Bug#636123: linux-image-2.6.39-2-amd64: root filesystem (LVM) not recognised

2011-08-22 Thread Luke Kenneth Casson Leighton
On Mon, Aug 22, 2011 at 7:35 PM, Ben Hutchings wrote: > On Mon, Aug 22, 2011 at 06:56:16PM +0100, Luke Kenneth Casson Leighton wrote: >> Valentijn, this is very important: >> >> please can you keep and make available the initrd that was generated >> by initramfs-tools?

Bug#636123: linux-image-2.6.39-2-amd64: root filesystem (LVM) not recognised

2011-08-22 Thread Luke Kenneth Casson Leighton
On Mon, Aug 22, 2011 at 7:42 PM, Luke Kenneth Casson Leighton wrote: > On Mon, Aug 22, 2011 at 7:21 PM, Valentijn Scholten > wrote: >> Hello Luke, >> Thanks for jumping in. >> I only have a /boot/initrd.img-2.6.32-5-amd64 at the moment. >> This is the one probably g

Bug#636123: linux-image-2.6.39-2-amd64: root filesystem (LVM) not recognised

2011-08-22 Thread Luke Kenneth Casson Leighton
On Mon, Aug 22, 2011 at 7:21 PM, Valentijn Scholten wrote: > Hello Luke, > Thanks for jumping in. > I only have a /boot/initrd.img-2.6.32-5-amd64 at the moment. > This is the one probably generated (reinstalled) after I reinstalled Squeeze > on top of the existing problemati

Re: Bug#636123: linux-image-2.6.39-2-amd64: root filesystem (LVM) not recognised

2011-08-22 Thread Luke Kenneth Casson Leighton
Valentijn, this is very important: please can you keep and make available the initrd that was generated by initramfs-tools? the file is going to be /boot/initrd.img-2.6.38-2-{insert_arch_name} DO NOT attempt to "recover" the system right away (unless you take a backup of /boot/initrg.img-2.6.38-

Bug#636123: linux-image-2.6.39 not booting due to older package (not in list of dependencies!)

2011-08-06 Thread Luke Kenneth Casson Leighton
On Sat, Aug 6, 2011 at 9:14 PM, Jonathan Nieder wrote: > (culling the cc list) > Hi Luke, allo jonathan. appreciate that you took time on this one, very much. i started writing a comprehensive reply, but then decided i was spending my time on an issue where there's no guarantee

Bug#636123: linux-image-2.6.39 not booting due to older package (not in list of dependencies!)

2011-08-06 Thread Luke Kenneth Casson Leighton
On Tue, Aug 2, 2011 at 2:05 PM, Luke Kenneth Casson Leighton wrote: > now, i've discussed this on the bugtracker and there clearly isn't - > and really shouldn't be - a listed debian dependency between > linux-image-2.6.39 kernel and a userspace library.  however

Bug#636123: closed by Ben Hutchings (Re: Bug#636123: "fixed" the problem: broken/missing dependency)

2011-08-02 Thread Luke Kenneth Casson Leighton
On Tue, Aug 2, 2011 at 4:03 PM, Ben Hutchings wrote: > Luke, you will get no help from me so long as you insult me and > refuse to help me to fix the problem. ... and closing the bugreport whilst i'm in the middle of investigating isn't insulting? if i didn't feel insult

Bug#636123: linux-image-2.6.39 not booting due to older package (not in list of dependencies!)

2011-08-02 Thread Luke Kenneth Casson Leighton
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636123 there's a rather complex set of interdependencies between linux-image-2.6.39, libdevmapper, initramfs-tools and LVM that has resulted in a system which last had 2.6.32-trunk-amd64 installed (and associated packages) failing to boot when the l

Bug#636123: closed by Ben Hutchings (Re: Bug#636123: "fixed" the problem: broken/missing dependency)

2011-08-02 Thread Luke Kenneth Casson Leighton
:28 +0100 > Subject: Re: Bug#636123: "fixed" the problem: broken/missing dependency > On Tue, 2011-08-02 at 05:51 +0100, Luke Kenneth Casson Leighton wrote: >> On Tue, Aug 2, 2011 at 12:44 AM, Ben Hutchings wrote: >> > On Sun, 2011-07-31 at 14:37 +0100, Luke Kenn

Bug#636290: linux-image-2.6.32-5-amd64: serious ext4 filesystem corruption even after fsck

2011-08-02 Thread Luke Kenneth Casson Leighton
On Tue, Aug 2, 2011 at 11:41 AM, Ben Hutchings wrote: > On Tue, 2011-08-02 at 03:51 +0100, Luke Kenneth Casson Leighton wrote: >> On Tue, Aug 2, 2011 at 1:54 AM, Ben Hutchings wrote: >> > On Tue, 2011-08-02 at 01:29 +0100, lkcl wrote: >> >> Package: lin

Bug#636290: linux-image-2.6.32-5-amd64: serious ext4 filesystem corruption even after fsck

2011-08-01 Thread Luke Kenneth Casson Leighton
On Tue, Aug 2, 2011 at 1:54 AM, Ben Hutchings wrote: > On Tue, 2011-08-02 at 01:29 +0100, lkcl wrote: >> Package: linux-2.6 >> Version: 2.6.32-5 > > Not an actual version number. > >> Severity: important >> >> >> running 2.6.32-5-amd64, after running fsck on a corrupted ext4 >> filesystem which is

Bug#636123: "fixed" the problem: broken/missing dependency

2011-07-31 Thread Luke Kenneth Casson Leighton
ok - i've established the cause of the failure: incorrect dependencies in linux-image-2.6.39-2-amd64. the most likely candidate which is the broken/missing dependency i am guessing isn't grub or lvm2, but probably libdevmapper. but - looking in /var/lib/dpkg/info with ls -altr shows the list of l

Re: [Pkg-alsa-devel] alsa-source

2011-05-18 Thread Luke Yelavich
; experimental. It is worse to provide a paralell source package. > Removing this package will flush maintainers garbage a bit ;-) Users > who want to build their own driver should be able to customize a > kernelbuild [0] > > What do you think? Fine by me. Luke -- To UNSU

Bug#510191: linux-image-2.6.26-1-686: madwifi compiles and works perfectly on 2.6.18 but same source fails on 2.6.26

2008-12-30 Thread Luke Kenneth Casson Leighton
On Tue, Dec 30, 2008 at 6:36 PM, lkcl wrote: > Package: linux-image-2.6.26-1-686 > Version: 2.6.26-12 > Severity: important > > > madwifi source code hasn't changed in 18 months: works perfectly under > 2.6.18-4-686, sets up wifi0 etc. etc. and yet exactly the same source > fails miserably under 2

Bug#319823: closed by Bastian Blank <[EMAIL PROTECTED]> (disagrees with d-i)

2008-09-14 Thread Luke Kenneth Casson Leighton
tested, uses this kernels and specifies around 40mb as > minimum for a running installer. > > Bastian > > -- > Vulcans do not approve of violence. >-- Spock, "Journey to Babel", stardate 3842.4 > > > > -- Forwarded message --

Bug#468112: Initramfs generation reliability fixes.

2008-04-07 Thread Luke Yelavich
Sorry I haven't gotten back to you until now. On Tue, Apr 01, 2008 at 07:53:44AM EST, maximilian attems wrote: > On Wed, 27 Feb 2008, Luke Yelavich wrote: > > > Attached is a patch to improve the way update-initramfs handles the > > generating of new or updated initramfs

Bug#468116: update-initramfs: ro_bootcheck fix.

2008-02-26 Thread Luke Yelavich
Package: initramfs-tools Severity: wishlist Version: 0.91e User: [EMAIL PROTECTED] Usertags: origin-ubuntu ubuntu-patch hardy ubuntu Attached is a patch to fix a possible ro_bootcheck error. The Ubuntu changelog contains the following: * Fix broken test in ro_boot_check (LP: #187282). It was ma

Bug#468115: Support for mount failure hooks.

2008-02-26 Thread Luke Yelavich
Package: initramfs-tools Severity: wishlist Version: 0.91e User: [EMAIL PROTECTED] Usertags: origin-ubuntu ubuntu-patch hardy ubuntu Attached is a patch to allow scripts in either local-top or init-premount to register hook to perform specific actions in the event the root device cannot be found

Bug#468114: Loopback file system support.

2008-02-26 Thread Luke Yelavich
Package: initramfs-tools Severity: wishlist Version: 0.91e User: [EMAIL PROTECTED] Usertags: origin-ubuntu ubuntu-patch hardy ubuntu Attached is a patch to allow an initramfs to use a root filesystem as a loop device, on top of another file system. A good example and use of this code is for Ubun

Bug#468112: Initramfs generation reliability fixes.

2008-02-26 Thread Luke Yelavich
Package: initramfs-tools Severity: wishlist Version: 0.91e User: [EMAIL PROTECTED] Usertags: origin-ubuntu ubuntu-patch hardy ubuntu Attached is a patch to improve the way update-initramfs handles the generating of new or updated initramfs images for kernels. It puts in place a few measures to e

Bug#468113: PlayStation 3 script update.

2008-02-26 Thread Luke Yelavich
Package: initramfs-tools Severity: wishlist Version: 0.91e User: [EMAIL PROTECTED] Usertags: origin-ubuntu ubuntu-patch hardy ubuntu Attached is a patch to update the ps3 script. This patch allows the supporting of old and new ps3 hardware configurations. The patch applies against git head. diff

Bug#409222: linux-image-2.6.18-3-686: on system with absolutely no SATA drives - 'ata1: port is slow to respond, please be patient'

2007-02-08 Thread Luke Kenneth Casson Leighton
On Thu, Feb 01, 2007 at 10:03:19AM +, Luke Kenneth Casson Leighton wrote: > On Thu, Feb 01, 2007 at 08:05:29AM +0100, Frans Pop wrote: > > On Thursday 01 February 2007 03:18, Luke Kenneth Casson Leighton wrote: > > > unfortunately there is no change. > > > >

Bug#409222: linux-image-2.6.18-3-686: on system with absolutely no SATA drives - 'ata1: port is slow to respond, please be patient'

2007-02-04 Thread Luke Kenneth Casson Leighton
On Sun, Feb 04, 2007 at 05:28:00PM +0100, maximilian attems wrote: > On Thu, Feb 01, 2007 at 10:03:19AM +, Luke Kenneth Casson Leighton wrote: > > On Thu, Feb 01, 2007 at 08:05:29AM +0100, Frans Pop wrote: > > > On Thursday 01 February 2007 03:18, Luke Kenneth Casson Leighton wr

Bug#409222: linux-image-2.6.18-3-686: on system with absolutely no SATA drives - 'ata1: port is slow to respond, please be patient'

2007-02-01 Thread Luke Kenneth Casson Leighton
On Thu, Feb 01, 2007 at 08:05:29AM +0100, Frans Pop wrote: > On Thursday 01 February 2007 03:18, Luke Kenneth Casson Leighton wrote: > > unfortunately there is no change. > > > > this is with 2.6.18-6-686. > > > > ghfield:~# apt-cache show linux-image-2.6.18-3-68

Bug#409222: linux-image-2.6.18-3-686: on system with absolutely no SATA drives - 'ata1: port is slow to respond, please be patient'

2007-01-31 Thread Luke Kenneth Casson Leighton
On Thu, Feb 01, 2007 at 02:02:54AM +0100, Norbert Tretkowski wrote: > tags 409222 +moreinfo > thanks > > * Luke Kenneth Casson Leighton wrote: > > adds nearly two minutes to the boot time as the timeouts on both > > ata1 and ata2 are nearly 50 seconds - 30 seconds wa

Bug#409222: linux-image-2.6.18-3-686: on system with absolutely no SATA drives - 'ata1: port is slow to respond, please be patient'

2007-01-31 Thread Luke Kenneth Casson Leighton
Package: linux-image-2.6.18-3-686 Severity: normal adds nearly two minutes to the boot time as the timeouts on both ata1 and ata2 are nearly 50 seconds - 30 seconds waiting time each plus several 5 second retries. l. -- System Information: Debian Release: testing/unstable Architecture: i386 Ker

No work tomorrow; Office closed

2006-10-15 Thread Luke Martiniere
, Learn how to generate 1.5 - 3.5k daily from your house. 800.439.1088 Contact me at my number if you can return calls. Respects, Luke Martiniere -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#338543: acknowledged by developer (Bug#338543: fixed in linux-2.6 2.6.14-3)

2005-11-14 Thread Luke Kenneth Casson Leighton
thank you! On Mon, Nov 14, 2005 at 11:33:30AM -0800, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > #338543: linux-image-2.6.14-1-686: CONFIG_SECURITY_NETWORK is disabled which > totally breaks SE/Linux, > which was filed against the linux-image-

Bug#338543: linux-image-2.6.14-1-686: CONFIG_SECURITY_NETWORK is disabled which totally breaks SE/Linux

2005-11-10 Thread Luke Kenneth Casson Leighton
Package: linux-image-2.6.14-1-686 Severity: normal On Thu, Nov 10, 2005 at 01:50:24PM -0500, Stephen Smalley wrote: > On Wed, 2005-11-09 at 08:36 -0500, Stephen Smalley wrote: > > On Tue, 2005-11-08 at 20:31 +0100, Erich Schubert wrote: > > > Hi, > > > > Hmmm...can you supply any more info to hel

Bug#334445: kernel-image-2.6.12-1-686: auditd not packaged for debian, kernel headers don't support required interfaces

2005-10-19 Thread Luke Kenneth Casson Leighton
Package: kernel-image-2.6.12-1-686 Severity: normal on selinux mailing list, copy of message from russell coker: On Tuesday 18 October 2005 02:39, Stephen Smalley <[EMAIL PROTECTED]> wrote: > > (In or out of enforcing mode). What's the best way for me to get > > the kernel to log the appropriat

Bug#319878: kernel-image-2.6-686: the entire range of 2.6 deb ian kernels do not install on m/cs with <= 48mb RAM

2005-08-10 Thread Luke Kenneth Casson Leighton
On Tue, Aug 09, 2005 at 10:06:15PM +0200, Sven Luther wrote: > > when i get a chance, which will likely be sunday, i will install a 2.6 > > kernel on my P1XX machine, then remove 16mb from it (i found someone > > who had an old machine...) > > So, you really have no idea of what is going wrong

Bug#319878: kernel-image-2.6-686: the entire range of 2.6 deb ian kernels do not install on m/cs with <= 48mb RAM

2005-08-09 Thread Luke Kenneth Casson Leighton
On Mon, Aug 08, 2005 at 02:28:12PM +0200, Sven Luther wrote: > On Mon, Jul 25, 2005 at 11:25:18PM +0100, Luke Kenneth Casson Leighton wrote: > > On Mon, Jul 25, 2005 at 11:56:21AM -0300, Humberto Massa Guimar?es wrote: > > > ** Luke Kenneth Casson Leighton :: > >

Bug#319878: kernel-image-2.6-686: the entire range of 2.6 debian kernels do not install on m/cs with <= 48mb RAM

2005-07-25 Thread Luke Kenneth Casson Leighton
On Mon, Jul 25, 2005 at 05:52:54PM -0700, Steve Langasek wrote: > On Tue, Jul 26, 2005 at 12:45:48AM +0100, Luke Kenneth Casson Leighton wrote: > > On Mon, Jul 25, 2005 at 03:51:22PM -0700, Matt Taggart wrote: > > > for this P120 (whatever) i have *shudder* had to use a >

Bug#319878: kernel-image-2.6-686: the entire range of 2.6 debian kernels do not install on m/cs with <= 48mb RAM

2005-07-25 Thread Luke Kenneth Casson Leighton
On Mon, Jul 25, 2005 at 05:06:49PM -0700, Steve Langasek wrote: > Incidentally, I have no idea why this bug was filed against > kernel-image-2.6-686; ... because i believed it to be a... wossisname... dummy package (2.6.N ... 2.6.NN) oops. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] wi

Bug#319823: Bug#319878: kernel-image-2.6-686: the entire range of 2.6 debian kernels do not install on m/cs with <= 48mb RAM

2005-07-25 Thread Luke Kenneth Casson Leighton
On Mon, Jul 25, 2005 at 12:03:48PM -0700, Matt Taggart wrote: > Luke, > > Sorry for the previous terse replies to your bug reports #319878 and #319823. > The debian-kernel team gets a lot of email/bugs and sometimes is quick to > response/close bugs without a lot of explanation.

Bug#319878: kernel-image-2.6-686: the entire range of 2.6 debian kernels do not install on m/cs with <= 48mb RAM

2005-07-25 Thread Luke Kenneth Casson Leighton
On Mon, Jul 25, 2005 at 03:51:22PM -0700, Matt Taggart wrote: > It would probably be a good idea to record what ought to work in any given > release and maybe have an ongoing idea what it should be. The answer might be > architecture specific? ISTR either the d-i team or apt/dpkg/aptitude tryin

Bug#319878: kernel-image-2.6-686: the entire range of 2.6 deb ian kernels do not install on m/cs with <= 48mb RAM

2005-07-25 Thread Luke Kenneth Casson Leighton
On Mon, Jul 25, 2005 at 04:17:10PM -0700, Matt Taggart wrote: > debian-release cc'd due to minimum system requirement stuff mentioned in a > previous message... > > Luke Kenneth Casson Leighton writes... > > > my bug report invites you to consider the impact that s

Re: Bug#319878: kernel-image-2.6-686: the entire range of 2.6 deb ian kernels do not install on m/cs with <= 48mb RAM

2005-07-25 Thread Luke Kenneth Casson Leighton
On Mon, Jul 25, 2005 at 11:56:21AM -0300, Humberto Massa Guimar?es wrote: > ** Luke Kenneth Casson Leighton :: > > > telling people to "roll their own" kernel (mr horms) isn't an > > acceptable option, either. i may be able to do that (mr horms) >

Bug#319878: kernel-image-2.6-686: the entire range of 2.6 debian kernels do not install on m/cs with <= 48mb RAM

2005-07-25 Thread Luke Kenneth Casson Leighton
: > On Mon, 25 Jul 2005, Luke Kenneth Casson Leighton wrote: > > >telling people to "roll their own" kernel (mr horms) isn't an > >acceptable option, either. i may be able to do that (mr horms) > >but other people won't be able to. > > > >y

Bug#319878: kernel-image-2.6-686: the entire range of 2.6 debian kernels do not install on m/cs with <= 48mb RAM

2005-07-25 Thread Luke Kenneth Casson Leighton
Package: kernel-image-2.6-686 Version: 2.6.5-2 Severity: normal not one single one of the 2.6 kernels - 2.6.5, 2.6.6, 2.6.7, 2.6.8, 2.6.9, 2.6.10, 2.6.11 nor 2.6.12 - can be installed on a system with less than 48mb of RAM - because of the hungry memory requirements of the initial ram disk. righ

Bug#319823: kernel-image-2.6-686: 2.6 debian kernels do not install on m/cs with <= 48mb RAM!!!

2005-07-24 Thread Luke Kenneth Casson Leighton
Package: kernel-image-2.6-686 Version: 2.6.5-2 Severity: normal any system with 48mb of ram or less results in a kernel panic due to a lack of memory, at boot time. 2.6 kernels use more memory, more resources... and now this. welcome to bloatware, roll-on windows 3.1. urk!! -- System Informa

Bug#319429: linux-image-2.6.12-1-686: installation, when used with grub and a separate /boot partition results in boot failure

2005-07-21 Thread Luke Kenneth Casson Leighton
Package: linux-image-2.6.12-1-686 Severity: normal setup: - grub not lilo - /boot separate partition - mbr - grub in /dev/hda1 (/boot) install linux-image-2.6.12-1-686: reboot, whammo. NOTHING boots. i get grub error messages about "must load linux kernel before initrd". on BOTH THE OLD AND

Bug#312871: initrd-tools: please provide support for udev _and_ selinux

2005-06-10 Thread Luke Kenneth Casson Leighton
Package: initrd-tools Version: 0.1.77 Severity: wishlist just like is done in FC2 and above's initrd, please could you consider putting uclib'd udev into the initrd, and then making sure that the programs in it are selinux-enabled / aware? i had to make a pig's ear of debian/selinux when udev is

Bug#312714: acknowledged by developer (Re: Bug#312714: initrd-tools: swsuspend requires an extra line in order to avoid filesystem corruption)

2005-06-09 Thread Luke Kenneth Casson Leighton
SpamAssassin 2.60-bugs.debian.org_2005_01_02 > (1.212-2003-09-23-exp) on spohr.debian.org > X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER > autolearn=no version=2.60-bugs.debian.org_2005_01_02 > X-Spam-Level: > > On Thu, 09 Jun 2005, Lu

Bug#312714: initrd-tools: swsuspend requires an extra line in order to avoid filesystem corruption

2005-06-09 Thread Luke Kenneth Casson Leighton
Package: initrd-tools Version: 0.1.77 Severity: normal according to http://www.suspend2.net/HOWTO-2.html you need this: echo > /proc/software_suspend/do_resume BEFORE the script mounts your filesystem. If the line is missing, your system will not resume. If the line comes afte

Bug#298334: kernel-image-2.6.10-1-686: volume being listed as an input not an output for CS4299 rev6 (I440MX)

2005-03-06 Thread Luke Kenneth Casson Leighton
Package: kernel-image-2.6.10-1-686 Version: 2.6.10-4 Severity: normal like the usb-audio device i have (a PDT cyberphone with mono capabilities), my Intel I440MX Cirrus Logic CS4299 (rev 6) has started being reported with volume as an INPUT device not an OUTPUT. the I440MX was not until about 2.

Bug#294982: kernel-image-2.6.10-1-686: usb audio device stopped working since about 2.6.8

2005-02-12 Thread Luke Kenneth Casson Leighton
Package: kernel-image-2.6.10-1-686 Version: 2.6.10-4 Severity: normal i have a USB handset and it used to work in about 2.6.8. USB HID v1.00 Device [Promotion and Display Technology Ltd USB VoIP Cyberphone Handse] on usb-:00:07.2-1 2.6.10 the microphone works (wavrecord) but playback does n

Bug#288263: initrd-tools: capability module missing from /etc/mkinitrd/modules

2005-01-02 Thread Luke Kenneth Casson Leighton
On Sun, Jan 02, 2005 at 08:29:19PM +0100, Christoph Hellwig wrote: > On Sun, Jan 02, 2005 at 07:22:28PM +0000, Luke Kenneth Casson Leighton wrote: > > Package: initrd-tools > > Version: 0.1.65 > > Severity: normal > > > > > > 2.6.9 and above now have c

Bug#288263: initrd-tools: capability module missing from /etc/mkinitrd/modules

2005-01-02 Thread Luke Kenneth Casson Leighton
Package: initrd-tools Version: 0.1.65 Severity: normal 2.6.9 and above now have capability as a module. if this module is not loaded, udev will not operate properly. selinux also is now a module and it too should probably be loaded, otherwise if /sbin/init runs and finds that selinux isn't enab

Bug#274880: kernel-image-2.6.8-1-k7: CAPABILITIES module needs to be compiled in-kernel for getcap and setcap to work

2004-10-04 Thread Luke Kenneth Casson Leighton
Package: kernel-image-2.6.8-1-k7 Severity: wishlist Jens Axboe wrote: > On Mon, Oct 04 2004, Luke Kenneth Casson Leighton wrote: > >>found it. >> >>it's a new piece of kernel code verify_command in >>drivers/block/scsi_ioctl.c, which checks for the capabili

  1   2   >