On Sat, 2011-09-24 at 18:20 -0700, David Witbrodt wrote:
I just upgraded to gcc-multilib 4.6.1-3 and found that APT
blew away /usr/include/asm without warning. This directory
belongs to my locally-built 'linux-libc-dev' which is produced
using upstream kernel sources and 'make deb-pkg'.
I
Package: linux-2.6
Severity: normal
I believe this is another case of a user needing
acpi_enforce_resources=lax in their kernel boot parameters.
Ferry, can you try the advice provided here,
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568126#44
and see if it helps.
HTH,
Dave W.
--
I'm no expert on kernel matters, but this looks like another instance of
someone being affected by the relatively recent change in upstream
kernel policy toward ACPI resource overlaps.
Possibly adding this to the kernel boot parameters would help:
acpi_enforce_resources=lax
HTH,
Dave W.
Package: nfs-common
Version: 1:1.2.2-1
Severity: normal
I don't mean to intrude in this bug report, but I have been experiencing
a similar issue for several months. I did not report a bug for two
reasons:
1) I believed there must have been some recent change upstream (late
2009 or early 2010)
Package: lm-sensors
Severity: normal
This looks like a consequence of a recent change in kernel policy
regarding resource conflicts. According to the 'kernel-parameters.txt'
file in the kernel documentation, the default value of the parameter
acpi_enforce_resources has changed:
$ grep -A 15
My apologies if I am interfering by posting to this thread. I mostly
run kernels that I have compiled myself, but keep a Debian stock kernel
installed in case bad things happen to my custom kernels.
I try to keep up to date on the LKML happenings, and the writing is
clearly on the wall that
Package: firmware-linux-nonfree
Version: 0.22
Severity: normal
Ben, your patch works for me. Will this be made part of the Debian
2.6.32 kernel, or were you merely experimenting? (It would really help
if the KT used this, unless/until the r8169 firmware can be used in
Debian.)
I don't seem to
Ben Hutchings wrote:
On Wed, 2009-12-16 at 11:49 -0500, Dave Witbrodt wrote:
[...]
May I provide evidence to the contrary?
I compile my own kernels, and use them exclusively unless some problem
arises which forces me to use another kernel. Therefore, I keep a stock
Debian kernel installed
Package: firmware-linux-nonfree
Version: 0.21
Severity: normal
On Wed, 2009-12-16 at 10:11 +0900, Miles Bader wrote:
Package: firmware-linux-nonfree
Version: 0.21
Severity: normal
Installing the new kernel package linux-image-2.6.32-trunk-amd64
results in new warning messages
Ben Hutchings wrote:
On Wed, 2009-12-16 at 11:49 -0500, Dave Witbrodt wrote:
When 2.6.32-truck (AMD64 here) was released, I tried switching to that
for my Debian backup kernel... but it hangs in boot, with some very
nasty backtracing. It does print the warning about missing firmware
On Fri, 16 Oct 2009 16:02:09 +0100, Ben Hutchings wrote:
On Fri, Oct 16, 2009 at 09:49:11AM -0400, Dave Witbrodt wrote:
[...]
Has the kernel team decided to no longer make DEBs available for
upcoming versions of kernels? Or will the 'experimental'
distribution be used to make
I've read the notes posted by Vincent Sanders about the meetings at the
Plumber's Conference. I saw the references to automated testing and
uploads of 2.6.31 to experimental in the notes about Session 4, but I
saw no comments about the loss of kernel-archive.buildserver.net.
Has the kernel
On Tue, 15 Sep 2009 09:39:59 +0200, Bastian Blank wrote:
It is down after a catastrophic UPS failure.
Wow... bummer. Will it be resuscitated or has it been abandoned?
Dave W.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Hi,
Can some kind member of the Debian Kernel Team direct me to some
documentation about how the package 'linux-libc-dev' fits into the
picture. I am learning about the standard toolchain, and just noticed
that installing 'gcc' brings in a dependency on 'libc6-dev'. (That
makes sense to
Package: linux-image-2.6.26-1-amd64
Version: 2.6.26-*
Followup-For: Bug #493479
After originally filing this bug report here on the Debian BTS, I
performed a kernel bisection and took my findings to the LKML. About
3 weeks later, the problem had finally been correctly diagnosed:
changes between
Package: linux-image-2.6.26-1-amd64
Version: 2.6.26-3
Followup-For: Bug #493479
Well, I've been providing information and making myself and my hardware
available to the Linux kernel team for nearly 3 weeks, and today I
was provided with a patch that allows development kernels (2.6.27*)
to boot
sources, then it could lead to all sorts of other problems
down the road.
Thanks,
Dave Witbrodt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: linux-image-2.6.26-1-amd64
Version: 2.6.26-1
Followup-For: Bug #493479
I worked on finding a config for 2.6.26 last night that would allow it to
boot, until I got too tired to continue. As mentioned previously, the
stock kernel freezes on this system early during the boot process; my
Package: linux-image-2.6.26-1-amd64
Version: 2.6.26-1
Followup-For: Bug #493479
After removing all of the boot parameters for debugging as mentioned in my
last message, I then began removing the parameters which disable kernel
features one at time. The result was that I could remove all of the
Package: linux-image-2.6.26-1-amd64
Version: 2.6.26-1
Severity: critical
Justification: breaks the whole system
[NB: I refer below to self-compiled kernels a bit, but this report IS
against the stock kernel.]
I saw that there is a push to get 2.6.26 into Lenny, so when
Package: linux-image-2.6.26-1-amd64
Version: 2.6.26-1
Followup-For: Bug #493479
CORRECTION: The motherboard on the machine where linux-image-2.6.26-1-amd64
refuses to boot is an ECS AMD690GM-M2, not ECS AMD790GM-M2 (a little
misspelling there).
The last kernel I compiled before filing the bug
Package: linux-image-2.6.26-1-amd64
Version: 2.6.26-1
Followup-For: Bug #493479
Well, I really believed I had found a way to isolate the config option that
was causing the kernel to freeze. Of the list of options I listed in my
previous message, I found that only 7 could be manually configured
22 matches
Mail list logo
