On Wed, 14 Aug 2013 at 21:29, Christian Kujau wrote:
On Wed, 14 Aug 2013 at 22:54, Dave Kleikamp wrote:
It looks like the problem is that jfs was using a cookie value of 2 for
a real directory entry, where NFSv4 expect 2 to represent ... This
patch has so far only been lightly tested.
For the sake of those not watching
https://bugzilla.kernel.org/show_bug.cgi?id=60737
It looks like the problem is that jfs was using a cookie value of 2 for
a real directory entry, where NFSv4 expect 2 to represent ... This
patch has so far only been lightly tested.
NFSv4 reserves cookie values
During DebCamp I started work on cleaning up the maintainer scripts and
the templating for them. I'm going to post changes for review in
several groups.
As a first step, this patch series changes several files from
kernel-package template system, now implemented using sed expressions in
The PO files processed by debconf-updatepo, which in our case are
templates, must have names ending in .po rather than .in. So look for
un-suffixed template files after looking for files with the .in
suffix.
--- a/debian/lib/python/debian_linux/utils.py
+++
[Omitted the file diffs for renaming, which is done like this:
mkdir debian/templates/po/
mv debian/po/* debian/templates/po/
for type in headers image; do
for file in debian/templates/temp.$type.plain/*; do
mv $file debian/templates/$type.$(basename $file).in
done
done
]
---
Maintainer scripts generated by kernel-package pass an environment
variable $KERNEL_ARCH to hook scripts. This is undocumented but seems
to be the architecture string that the kernel will report
(e.g. through 'uname -m').
However, for the past few years our maintainer scripts have set it to
the
Use the same template syntax and implementation for maintainer
scripts, translations, etc. as we do for the control files. Define
the image-stem and initramfs variables to replace the old K and I
variables.
After this, debian/linux-* and debian/po/*.po are generated files (at
source preparation
Here's the diff between control files for linux-image-3.11-rc4-amd64
before and after this patch series (ignoring the md5sums):
diff -urN linux-image-3.11-rc4-amd64_3.11~rc4-1~exp1_amd64/DEBIAN/control
linux-image-3.11-rc4-amd64_3.11~rc4-1~exp2_amd64/DEBIAN/control
---
This series removes some warning messages that were important
information for users during earlier upgrades but should no longer be
needed.
It depends on the previous cleanup of templates.
Ben.
--
Ben Hutchings
Man invented language to satisfy his deep need to complain. - Lily Tomlin
We warned about removal of the 'ramdisk' configuration variable
on upgrade to wheezy, and don't need to warn about it again - at
least not this prominently.
---
A following patch series will add a warning for *all* unrecognised
configuration variables, but not using debconf.
Ben.
---
At this point, Debian users should know that they may need to install
firmware from non-free. People using e.g. the r8169 driver may quite
reasonably choose not to install the associated firmware, either
because the driver doesn't actually request it for their chip or
because the driver can still
Hi there!!
I've installed a live-boot Debian wheezy on my USB stick. all was going
perfect until yesterday when wheezy has begun to stuck during the boot
process. I've taken a snapshot of the screen but I don't know if this is
permitted to attach it to the mailing list.
anyone can help?
Hi,
Just to let you know that, while kernel 3.9.8-1 was working fine, the
gdb stops with SIGTRAP at 0 bug is back with kernel 3.10.5-1 in
today's Jessie Testing updates :-(
Émeric
2013/8/8 Ben Hutchings b...@decadent.org.uk:
On Wed, 2013-08-07 at 16:54 -0400, Camm Maguire wrote:
On Thu, 2013-08-15 at 15:01 +0300, atar wrote:
Hi there!!
I've installed a live-boot Debian wheezy on my USB stick. all was going
perfect until yesterday when wheezy has begun to stuck during the boot
process. I've taken a snapshot of the screen but I don't know if this is
permitted
On Wed, Aug 14, 2013 at 10:54:31PM -0500, Dave Kleikamp wrote:
For the sake of those not watching
https://bugzilla.kernel.org/show_bug.cgi?id=60737
It looks like the problem is that jfs was using a cookie value of 2 for
a real directory entry, where NFSv4 expect 2 to represent ... This
Processing commands for cont...@bugs.debian.org:
unarchive 691576
Bug #691576 {Done: Ben Hutchings b...@decadent.org.uk} [src:linux] GDB stops
with sigtrap at 0 address on ia64 wheezy
Unarchived Bug 691576
reopen 691576
Bug #691576 {Done: Ben Hutchings b...@decadent.org.uk} [src:linux] GDB
On 08/15/2013 02:09 AM, Christian Kujau wrote:
On Wed, 14 Aug 2013 at 21:29, Christian Kujau wrote:
On Wed, 14 Aug 2013 at 22:54, Dave Kleikamp wrote:
It looks like the problem is that jfs was using a cookie value of 2 for
a real directory entry, where NFSv4 expect 2 to represent ... This
reassign 628444 src:linux
thanks
On Wed, Mar 14, 2012 at 08:37:17PM -0700, Shannon Dealy wrote:
Like others, the problems seemed to start around 2.6.39.
Thought I should note here, my system showed this problem with 2.6.36
through 2.6.39. It seems to have stopped showing the problem
Processing commands for cont...@bugs.debian.org:
reassign 628444 src:linux
Bug #628444 [linux-2.6] linux-image-2.6.39-1-686-pae: iwlagn - MAC is in deep
sleep, cannot restore wifi operation
Bug reassigned from package 'linux-2.6' to 'src:linux'.
No longer marked as found in versions
Shannon Dealy de...@deatech.com writes:
I have not seen this problem or any of the other iwl instabilities in
a long time, however, I have been running with these option lines
disabling 11n functionality in order to achieve that stability:
options iwlagn 11n_disable50=1
options
Hi Moritz,
I have not seen this problem or any of the other iwl instabilities in a
long time, however, I have been running with these option lines disabling
11n functionality in order to achieve that stability:
options iwlagn 11n_disable50=1
options iwlwifi 11n_disable=1
since I am
Package: src:linux
Version: 3.10.5-1
Severity: important
Dear Maintainer,
on my old eeepc, today, I do a dist-upgrade after many month, I upgrade from
kernel 3.0 to 3.10.
On kernel 3.0 supsend/resume works prfectly, on 3.10 every time a do a
suspend/resume I get an I/O error
and my root FS is
Processing commands for cont...@bugs.debian.org:
reassign 719252 src:linux
Bug #719252 [linux-image-3.9-1-686-pae] ATA error message during stopping disk
Warning: Unknown package 'linux-image-3.9-1-686-pae'
Bug reassigned from package 'linux-image-3.9-1-686-pae' to 'src:linux'.
No longer marked
This patch replaces the one I posted yesterday. I like this better since
it doesn't require fixing existing on-disk cookies or skipping a
position in the in-inode index table.
NFSv4 reserves readdir cookie values 0-2 for special entries (. and ..),
but jfs allows a value of 2 for a non-special
On Thu, 15 Aug 2013 at 15:48, Dave Kleikamp wrote:
This patch replaces the one I posted yesterday. I like this better since
it doesn't require fixing existing on-disk cookies or skipping a
position in the in-inode index table.
Thanks. Applied to 3.11-rc5 and tested, no more readdir loop
On 08/15/2013 04:26 PM, Christian Kujau wrote:
On Thu, 15 Aug 2013 at 15:48, Dave Kleikamp wrote:
This patch replaces the one I posted yesterday. I like this better since
it doesn't require fixing existing on-disk cookies or skipping a
position in the in-inode index table.
Thanks. Applied
The build of linux 3.11~rc4-1~exp1
https://buildd.debian.org/status/fetch.php?pkg=linuxarch=armhfver=3.11~rc4-1~exp1stamp=1376523445
ended with errors from modpost:
ERROR: imx_pcm_fiq_init [sound/soc/fsl/snd-soc-imx-ssi.ko] undefined!
ERROR: imx_pcm_dma_init [sound/soc/fsl/snd-soc-imx-ssi.ko]
Subject: linux-image-3.2.0-4-amd64: kernel bug in patch_generic_hdmi
[snd_hda_codec_hdmi] on HP EliteBook 8770w
Package: src:linux
Version: 3.2.46-1
Severity: important
Dear Maintainer,
The outcome is different each time I reboot, and sometimes it gets all
the way thru and runs like a champ.
Apparently having the kernel image debug package installed is a good
idea when trying to do anything with crash dumps... After installing the
~2GB (unpacked) package I was able to use the crash utility to analyze
(to a degree) the crash dump file made by kdump-tools, however I am
unable to
Package: src:linux
Version: 3.10.5-1
Severity: important
Dear Maintainer,
System fails to boot cleanly. It hangs while populating /dev and then
kicks out a bunch of modprobe hung errors. It eventually comes up sorta. but I
have no console or keyboard. I can ssh into the system and that
On Thu, Aug 15, 2013 at 5:20 PM, Ben Hutchings b...@decadent.org.uk wrote:
The build of linux 3.11~rc4-1~exp1
https://buildd.debian.org/status/fetch.php?pkg=linuxarch=armhfver=3.11~rc4-1~exp1stamp=1376523445
ended with errors from modpost:
ERROR: imx_pcm_fiq_init
31 matches
Mail list logo
