Bug#714974: [PATCH] jfs: avoid misuse of cookie value of 2
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.
Hm, a first compile of 3.11-rc5 errors out with:
CC [M] fs/jfs/jfs_dtree.o
/usr/local/src/linux-git/fs/jfs/jfs_dtree.c: In function ‘add_index’:
/usr/local/src/linux-git/fs/jfs/jfs_dtree.c:493:13: error: invalid storage
class for function ‘free_index’
[...]
I'll run mrproper and try again...
This did not help, but adding a closing bracket did, in fs/jfs/jfs_dtree.c:354
if (jfs_ip-next_index 3) {
jfs_ip-next_index = 3;
}
-^
This compiled and booted and now I can run find(1) over that whole NFS
share, without any readdir loop messages and with unique inode numbers,
yay!
Tested-by: Christian Kujau li...@nerdbynature.de
Thanks!
Christian.
--
BOFH excuse #36:
dynamic software linking table corrupted
--
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/alpine.deb.2.10.1308150001530.7...@trent.utfs.org
Bug#714974: [PATCH] jfs: avoid misuse of cookie value of 2
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 0, 1 and 2 for a rewind, and the . and ..
entries. jfs was using 0 and 1 for . and .., but 2 for a regular entry.
This patch makes jfs conform by using 1 and 2 for . and .. and fixes
any regular entry using the value 2.
Signed-off-by: Dave Kleikamp dave.kleik...@oracle.com
diff --git a/fs/jfs/jfs_dtree.c b/fs/jfs/jfs_dtree.c
index 8743ba9..93466e8 100644
--- a/fs/jfs/jfs_dtree.c
+++ b/fs/jfs/jfs_dtree.c
@@ -349,11 +349,8 @@ static u32 add_index(tid_t tid, struct inode *ip, s64 bn,
int slot)
ASSERT(DO_INDEX(ip));
- if (jfs_ip-next_index 2) {
- jfs_warn(add_index: next_index = %d. Resetting!,
- jfs_ip-next_index);
- jfs_ip-next_index = 2;
- }
+ if (jfs_ip-next_index 3) {
+ jfs_ip-next_index = 3;
index = jfs_ip-next_index++;
@@ -2864,7 +2861,7 @@ void dtInitRoot(tid_t tid, struct inode *ip, u32 idotdot)
} else
ip-i_size = 1;
- jfs_ip-next_index = 2;
+ jfs_ip-next_index = 3;
} else
ip-i_size = IDATASIZE;
@@ -2951,7 +2948,7 @@ static void add_missing_indices(struct inode *inode, s64
bn)
for (i = 0; i p-header.nextindex; i++) {
d = (struct ldtentry *) p-slot[stbl[i]];
index = le32_to_cpu(d-index);
- if ((index 2) || (index = JFS_IP(inode)-next_index)) {
+ if ((index 3) || (index = JFS_IP(inode)-next_index)) {
d-index = cpu_to_le32(add_index(tid, inode, bn, i));
if (dtlck-index = dtlck-maxcnt)
dtlck = (struct dt_lock *) txLinelock(dtlck);
@@ -3031,7 +3028,7 @@ int jfs_readdir(struct file *file, struct dir_context
*ctx)
struct jfs_dirent *jfs_dirent;
int jfs_dirents;
int overflow, fix_page, page_fixed = 0;
- static int unique_pos = 2; /* If we can't fix broken index */
+ static int unique_pos = 3; /* If we can't fix broken index */
if (ctx-pos == DIREND)
return 0;
@@ -3039,15 +3036,16 @@ int jfs_readdir(struct file *file, struct dir_context
*ctx)
if (DO_INDEX(ip)) {
/*
* persistent index is stored in directory entries.
-* Special cases:0 = .
-* 1 = ..
+* Special cases:0 = rewind
+* 1 = .
+* 2 = ..
* -1 = End of directory
*/
do_index = 1;
dir_index = (u32) ctx-pos;
- if (dir_index 1) {
+ if (dir_index 2) {
struct dir_table_slot dirtab_slot;
if (dtEmpty(ip) ||
@@ -3090,18 +3088,18 @@ int jfs_readdir(struct file *file, struct dir_context
*ctx)
return 0;
}
} else {
- if (dir_index == 0) {
+ if (dir_index 2) {
/*
* self .
*/
- ctx-pos = 0;
+ ctx-pos = 1;
if (!dir_emit(ctx, ., 1, ip-i_ino, DT_DIR))
return 0;
}
/*
* parent ..
*/
- ctx-pos = 1;
+ ctx-pos = 2;
if (!dir_emit(ctx, .., 2, PARENT(ip), DT_DIR))
return 0;
@@ -3122,22 +3120,24 @@ int jfs_readdir(struct file *file, struct dir_context
*ctx)
/*
* Legacy filesystem - OS/2 Linux JFS 0.3.6
*
-* pn = index = 0: First entry .
-* pn = 0; index = 1: Second entry ..
+* pn = 0; index = 1: First entry .
+* pn = 0; index = 2: Second entry ..
* pn 0: Real entries, pn=1 - leftmost page
* pn = index = -1: No more entries
*/
dtpos = ctx-pos;
- if (dtpos == 0) {
+ if (dtpos 2) {
+ ctx-pos = 1;
/* build . entry */
if (!dir_emit(ctx, ., 1, ip-i_ino, DT_DIR))
return 0;
- dtoffset-index = 1;
+
[PATCH 0/4] Replace the kernel-package template system
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 debian/rules.gen, to the template system and syntax implemented in gencontrol.py. Along the way, it moves all those files into the debian/templates subdirectory and makes more use of debhelper. Ben. -- Ben Hutchings Man invented language to satisfy his deep need to complain. - Lily Tomlin signature.asc Description: This is a digitally signed message part
[PATCH 1/4] Don't require '.in' suffix on templates
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
+++ b/debian/lib/python/debian_linux/utils.py
@@ -19,13 +19,14 @@ class Templates(object):
def _read(self, name):
prefix, id = name.split('.', 1)
-for dir in self.dirs:
-filename = %s/%s.in % (dir, name)
-if os.path.exists(filename):
-f = codecs.open(filename, 'r', 'utf-8')
-if prefix == 'control':
-return read_control(f)
-return f.read()
+for suffix in ['.in', '']:
+for dir in self.dirs:
+filename = %s/%s%s % (dir, name, suffix)
+if os.path.exists(filename):
+f = codecs.open(filename, 'r', 'utf-8')
+if prefix == 'control':
+return read_control(f)
+return f.read()
def get(self, key, default=None):
if key in self._cache:
--
Ben Hutchings
Man invented language to satisfy his deep need to complain. - Lily Tomlin
signature.asc
Description: This is a digitally signed message part
[PATCH 2/4] Move templates in preparation for using a single template system
[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
]
--- a/debian/rules.real
+++ b/debian/rules.real
@@ -289,7 +289,7 @@ install-headers_$(ARCH)_$(FEATURESET)_$(
install -d $(PACKAGE_DIR)/DEBIAN
sed -e 's/=V/$(REAL_VERSION)/g' \
- debian/templates/temp.headers.plain/postinst \
+ debian/templates/headers.plain.postinst.in \
$(PACKAGE_DIR)/DEBIAN/postinst
chmod 755 $(PACKAGE_DIR)/DEBIAN/postinst
@@ -430,16 +430,18 @@ install-image_powerpcspe_$(FEATURESET)_$
install-image_ppc64_$(FEATURESET)_$(FLAVOUR)_plain_templates: ARG_KIMAGE =
vmlinux
install-image_$(ARCH)_$(FEATURESET)_$(FLAVOUR)_plain_templates:
- for i in $(wildcard debian/templates/temp.image.plain/*); do \
+ for i in $(wildcard debian/templates/image.plain.*.in); do \
+ target=$$(basename $$i .in); \
+ target=$${target#image.plain.}; \
sed \
-e 's@=B@$(KERNEL_ARCH)@g' \
-e 's/=I/$(ARG_INITRD)/g' \
-e 's/=K/$(ARG_KIMAGE)/g' \
-e 's/=V/$(REAL_VERSION)/g' \
- $$i debian/$(PACKAGE_NAME).$$(basename $$i) || exit; \
+ $$i debian/$(PACKAGE_NAME).$$target || exit; \
done
mkdir -p debian/$(PACKAGE_NAME).po
- for i in $(wildcard debian/po/*.po); do \
+ for i in $(wildcard debian/templates/po/*.po); do \
sed \
-e 's/=V/$(REAL_VERSION)/g' \
$$i debian/$(PACKAGE_NAME).po/$$(basename $$i) || exit; \
--- a/debian/changelog
+++ b/debian/changelog
@@ -3,6 +3,8 @@ linux (3.11~rc4-1~exp2) UNRELEASED; urge
* [arm,mips,s390,sh4] Enable KPROBES
* trace: Enable KPROBE_EVENT (Closes: #640953)
* trace: Enable UPROBES, UPROBE_EVENT (Closes: #691167)
+ * Clean up maintainer scripts and templating system
+- Move all templates under debian/templates
-- Ben Hutchings b...@decadent.org.uk Sun, 11 Aug 2013 19:34:47 +0200
--
Ben Hutchings
Man invented language to satisfy his deep need to complain. - Lily Tomlin
signature.asc
Description: This is a digitally signed message part
[PATCH 3/4] linux-image: Remove undocumented $KERNEL_ARCH variable from hook environment
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 source architecture name instead. Since no-one reported this bug,
I don't think anyone depends on it. codesearch didn't find any users
either. So remove it.
--- a/debian/templates/image.plain.postinst.in
+++ b/debian/templates/image.plain.postinst.in
@@ -22,7 +22,6 @@ my $use_hard_links= ''; # hardlinks
my $postinst_hook = ''; #Normally we do not
my $minimal_swap = ''; # Do not swap symlinks
my $ignore_depmod_err = ''; # normally we do not
-my $kernel_arch = =B;
my $ramdisk = '';
my $package_name = linux-image-$version;
@@ -99,8 +98,6 @@ if ($do_symlink $no_symlink) {
# most of our work is done in $image_dest (nominally /)
chdir($image_dest) or die could not chdir to $image_dest:$!\n;
-$ENV{KERNEL_ARCH}=$kernel_arch if $kernel_arch;
-
die Internal Error: Could not find image ( . $realimageloc
. $kimage-$version)\n unless -e $realimageloc
--- a/debian/templates/image.plain.postrm.in
+++ b/debian/templates/image.plain.postrm.in
@@ -24,7 +24,6 @@ my $link_in_boot = ;
my $kimage= =K;
my $initrd= =I; # initrd kernel
my $postrm_hook = ''; #Normally we do not
-my $kernel_arch = =B;
my $ramdisk = =MK; # List of tools to create initial ram fs.
my $package_name= linux-image-$version;
@@ -66,8 +65,6 @@ if (-d $image_dest) {
chdir($image_dest) or die could not chdir to $image_dest:$!\n;
}
-$ENV{KERNEL_ARCH}=$kernel_arch if $kernel_arch;
-
##
##
--- a/debian/templates/image.plain.preinst.in
+++ b/debian/templates/image.plain.preinst.in
@@ -13,7 +13,6 @@ $|=1;
my $version = =V;
my $kimage = =K;
my $preinst_hook= ''; #Normally we do not
-my $kernel_arch = =B;
my $package_name= linux-image-$version;
#known variables
@@ -40,8 +39,6 @@ if (-r $CONF_LOC -f $CONF_LOC )
}
}
-$ENV{KERNEL_ARCH}=$kernel_arch if $kernel_arch;
-
# set the env var stem
$ENV{'STEM'} = linux;
--- a/debian/templates/image.plain.prerm.in
+++ b/debian/templates/image.plain.prerm.in
@@ -11,7 +11,6 @@ $|=1;
my $version = =V;
my $kimage = =K;
my $prerm_hook = ''; #Normally we do not
-my $kernel_arch = =B;
my $package_name= linux-image-$version;
#known variables
@@ -43,8 +42,6 @@ if (-r $CONF_LOC -f $CONF_LOC )
}
-$ENV{KERNEL_ARCH}=$kernel_arch if $kernel_arch;
-
#check to see if we are trying to remove a running kernel
# if so we abort right now.
chop($running=`uname -r`);
--- a/debian/changelog
+++ b/debian/changelog
@@ -5,6 +5,8 @@ linux (3.11~rc4-1~exp2) UNRELEASED; urge
* trace: Enable UPROBES, UPROBE_EVENT (Closes: #691167)
* Clean up maintainer scripts and templating system
- Move all templates under debian/templates
+- linux-image: Remove undocumented $KERNEL_ARCH variable from hook
+ environment
-- Ben Hutchings b...@decadent.org.uk Sun, 11 Aug 2013 19:34:47 +0200
--
Ben Hutchings
Man invented language to satisfy his deep need to complain. - Lily Tomlin
signature.asc
Description: This is a digitally signed message part
[PATCH 4/4] Use only one template syntax
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 time) and should be ignored in svn.
Use debhelper to install the generated files at build time. This also
results in a redundant dependency on debconf (which we already have in
Pre-Depends), but this seems harmless.
--- a/debian/bin/gencontrol.py
+++ b/debian/bin/gencontrol.py
@@ -3,6 +3,9 @@
import sys
sys.path.append(debian/lib/python)
+import codecs
+import errno
+import glob
import os
import os.path
import subprocess
@@ -59,6 +62,14 @@ class Gencontrol(Base):
'SOURCEVERSION': self.version.complete,
})
+# Prepare to generate template-substituted translations
+for path in glob.glob('debian/templates/po/*.po'):
+target = 'debian/po/' + os.path.basename(path)
+with open(target, 'w') as f:
+f.write('# THIS IS A GENERATED FILE; DO NOT EDIT IT!\n'
+'# Translators should edit %s instead.\n'
+'#\n' % path)
+
def do_main_makefile(self, makefile, makeflags, extra):
fs_enabled = [featureset
for featureset in self.config['base', ]['featuresets']
@@ -98,6 +109,12 @@ class Gencontrol(Base):
def do_arch_setup(self, vars, makeflags, arch, extra):
config_base = self.config.merge('base', arch)
+
+if config_base['kernel-arch'] in ['mips', 'parisc', 'powerpc']:
+vars['image-stem'] = 'vmlinux'
+else:
+vars['image-stem'] = 'vmlinuz'
+
self._setup_makeflags(self.arch_makeflags, makeflags, config_base)
def do_arch_packages(self, packages, makefile, arch, vars, makeflags,
extra):
@@ -199,7 +216,6 @@ class Gencontrol(Base):
flavour_makeflags_image = (
('type', 'TYPE', False),
-('initramfs', 'INITRAMFS', True),
)
flavour_makeflags_other = (
@@ -219,6 +235,7 @@ class Gencontrol(Base):
override_localversion = config_image.get('override-localversion', None)
if override_localversion is not None:
vars['localversion-image'] = vars['localversion_headers'] + '-' +
override_localversion
+vars['initramfs'] = 'YES' if config_image.get('initramfs', True) else
''
self._setup_makeflags(self.flavour_makeflags_base, makeflags,
config_base)
self._setup_makeflags(self.flavour_makeflags_image, makeflags,
config_image)
@@ -379,6 +396,29 @@ class Gencontrol(Base):
makefile.add('build-arch_%s_%s_%s_real' % (arch, featureset, flavour),
cmds=cmds_build)
makefile.add('setup_%s_%s_%s_real' % (arch, featureset, flavour),
cmds=cmds_setup)
+# Substitute kernel version etc. into maintainer scripts,
+# translations and lintian overrides
+def substitute_file(template, target, append=False):
+with codecs.open(target, 'a' if append else 'w',
+ 'utf-8') as f:
+f.write(self.substitute(self.templates[template], vars))
+if config_entry_image['type'] == 'plain':
+substitute_file('headers.plain.postinst',
+'debian/linux-headers-%s%s.postinst' %
+(self.abiname, vars['localversion']))
+for name in ['postinst', 'postrm', 'preinst', 'prerm',
'templates']:
+substitute_file('image.plain.%s' % name,
+'debian/linux-image-%s%s.%s' %
+(self.abiname, vars['localversion'], name))
+for path in glob.glob('debian/templates/po/*.po'):
+substitute_file('po/' + os.path.basename(path),
+'debian/po/' + os.path.basename(path),
+append=True)
+if build_debug:
+substitute_file('image-dbg.lintian-override',
+'debian/linux-image-%s%s-dbg.lintian-overrides' %
+(self.abiname, vars['localversion']))
+
def merge_packages(self, packages, new, arch):
for new_package in new:
name = new_package['Package']
--- a/debian/rules.real
+++ b/debian/rules.real
@@ -287,12 +287,6 @@ install-headers_$(ARCH)_$(FEATURESET)_$(
ln -s /usr/src/$(PACKAGE_NAME)
$(PACKAGE_DIR)/lib/modules/$(REAL_VERSION)/build
ln -s /usr/src/$(PACKAGE_NAME_COMMON)
$(PACKAGE_DIR)/lib/modules/$(REAL_VERSION)/source
- install -d $(PACKAGE_DIR)/DEBIAN
- sed -e 's/=V/$(REAL_VERSION)/g' \
- debian/templates/headers.plain.postinst.in \
- $(PACKAGE_DIR)/DEBIAN/postinst
- chmod 755 $(PACKAGE_DIR)/DEBIAN/postinst
-
+$(MAKE_SELF) install-base
install-libc-dev_$(ARCH): PACKAGE_NAME =
Re: [PATCH 0/4] Replace the kernel-package template system
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
--- linux-image-3.11-rc4-amd64_3.11~rc4-1~exp1_amd64/DEBIAN/control
2013-08-08 14:27:02.0 +0200
+++ linux-image-3.11-rc4-amd64_3.11~rc4-1~exp2_amd64/DEBIAN/control
2013-08-15 01:45:58.0 +0200
@@ -1,11 +1,11 @@
Package: linux-image-3.11-rc4-amd64
Source: linux
-Version: 3.11~rc4-1~exp1
+Version: 3.11~rc4-1~exp2
Architecture: amd64
Maintainer: Debian Kernel Team debian-kernel@lists.debian.org
-Installed-Size: 113707
+Installed-Size: 113729
Pre-Depends: debconf | debconf-2.0
-Depends: kmod | module-init-tools, linux-base (= 3~), initramfs-tools (=
0.110~) | linux-initramfs-tool
+Depends: kmod | module-init-tools, linux-base (= 3~), debconf (= 0.5) |
debconf-2.0, initramfs-tools (= 0.110~) | linux-initramfs-tool
Recommends: firmware-linux-free (= 3~)
Suggests: linux-doc-3.11, debian-kernel-handbook, grub-pc | extlinux | lilo
Breaks: at ( 3.1.12-1+squeeze1), initramfs-tools ( 0.110~)
diff -urN linux-image-3.11-rc4-amd64_3.11~rc4-1~exp1_amd64/DEBIAN/postinst
linux-image-3.11-rc4-amd64_3.11~rc4-1~exp2_amd64/DEBIAN/postinst
--- linux-image-3.11-rc4-amd64_3.11~rc4-1~exp1_amd64/DEBIAN/postinst
2013-08-08 14:27:02.0 +0200
+++ linux-image-3.11-rc4-amd64_3.11~rc4-1~exp2_amd64/DEBIAN/postinst
2013-08-15 01:45:57.0 +0200
@@ -16,13 +16,12 @@
my $no_symlink= ;
my $do_symlink= Yes; # target machine defined
my $kimage= vmlinuz;
-my $initrd= YES;# initrd kernel
+my $initrd= YES;
my $mkimage = ; # command to generate the initrd image
my $use_hard_links= ''; # hardlinks do not work across fs boundaries
my $postinst_hook = ''; #Normally we do not
my $minimal_swap = ''; # Do not swap symlinks
my $ignore_depmod_err = ''; # normally we do not
-my $kernel_arch = x86;
my $ramdisk = '';
my $package_name = linux-image-$version;
@@ -99,8 +98,6 @@
# most of our work is done in $image_dest (nominally /)
chdir($image_dest) or die could not chdir to $image_dest:$!\n;
-$ENV{KERNEL_ARCH}=$kernel_arch if $kernel_arch;
-
die Internal Error: Could not find image ( . $realimageloc
. $kimage-$version)\n unless -e $realimageloc
diff -urN linux-image-3.11-rc4-amd64_3.11~rc4-1~exp1_amd64/DEBIAN/postrm
linux-image-3.11-rc4-amd64_3.11~rc4-1~exp2_amd64/DEBIAN/postrm
--- linux-image-3.11-rc4-amd64_3.11~rc4-1~exp1_amd64/DEBIAN/postrm
2013-08-08 14:27:02.0 +0200
+++ linux-image-3.11-rc4-amd64_3.11~rc4-1~exp2_amd64/DEBIAN/postrm
2013-08-15 01:45:58.0 +0200
@@ -22,10 +22,8 @@
my $version = 3.11-rc4-amd64;
my $link_in_boot = ;
my $kimage= vmlinuz;
-my $initrd= YES; # initrd kernel
+my $initrd= YES;
my $postrm_hook = ''; #Normally we do not
-my $kernel_arch = x86;
-my $ramdisk = =MK; # List of tools to create initial ram fs.
my $package_name= linux-image-$version;
#known variables
@@ -66,8 +64,6 @@
chdir($image_dest) or die could not chdir to $image_dest:$!\n;
}
-$ENV{KERNEL_ARCH}=$kernel_arch if $kernel_arch;
-
##
##
diff -urN linux-image-3.11-rc4-amd64_3.11~rc4-1~exp1_amd64/DEBIAN/preinst
linux-image-3.11-rc4-amd64_3.11~rc4-1~exp2_amd64/DEBIAN/preinst
--- linux-image-3.11-rc4-amd64_3.11~rc4-1~exp1_amd64/DEBIAN/preinst
2013-08-08 14:27:02.0 +0200
+++ linux-image-3.11-rc4-amd64_3.11~rc4-1~exp2_amd64/DEBIAN/preinst
2013-08-15 01:45:57.0 +0200
@@ -13,7 +13,6 @@
my $version = 3.11-rc4-amd64;
my $kimage = vmlinuz;
my $preinst_hook= ''; #Normally we do not
-my $kernel_arch = x86;
my $package_name= linux-image-$version;
#known variables
@@ -40,8 +39,6 @@
}
}
-$ENV{KERNEL_ARCH}=$kernel_arch if $kernel_arch;
-
# set the env var stem
$ENV{'STEM'} = linux;
diff -urN linux-image-3.11-rc4-amd64_3.11~rc4-1~exp1_amd64/DEBIAN/prerm
linux-image-3.11-rc4-amd64_3.11~rc4-1~exp2_amd64/DEBIAN/prerm
--- linux-image-3.11-rc4-amd64_3.11~rc4-1~exp1_amd64/DEBIAN/prerm
2013-08-08 14:27:02.0 +0200
+++ linux-image-3.11-rc4-amd64_3.11~rc4-1~exp2_amd64/DEBIAN/prerm
2013-08-15 01:45:57.0 +0200
@@ -11,7 +11,6 @@
my $version = 3.11-rc4-amd64;
my $kimage = vmlinuz;
my $prerm_hook = ''; #Normally we do not
-my $kernel_arch = x86;
my $package_name= linux-image-$version;
#known variables
@@ -43,8 +42,6 @@
}
-$ENV{KERNEL_ARCH}=$kernel_arch if $kernel_arch;
-
#check to see if we are trying to
[PATCH 0/3] Remove stale debconf warnings
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 signature.asc Description: This is a digitally signed message part
[PATCH 2/3] linux-image.postinst: Remove debconf warning about ramdisk variable in /etc/kernel-img.conf
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.
--- a/debian/templates/image.plain.postinst.in
+++ b/debian/templates/image.plain.postinst.in
@@ -22,7 +22,6 @@ my $use_hard_links= ''; # hardlinks
my $postinst_hook = ''; #Normally we do not
my $minimal_swap = ''; # Do not swap symlinks
my $ignore_depmod_err = ''; # normally we do not
-my $ramdisk = '';
my $package_name = linux-image-$version;
#known variables
@@ -68,7 +67,6 @@ if (-r $CONF_LOC -f $CONF_LOC )
$image_dest = $1 if /image_dest\s*=\s*(\S+)/i;
$postinst_hook = $1 if /postinst_hook\s*=\s*(\S+)/i;
$mkimage = $1 if /mkimage\s*=\s*(.+)$/i;
- $ramdisk = $1 if /ramdisk\s*=\s*(.+)$/i;
}
close CONF;
$have_conffile = Yes;
@@ -624,16 +622,6 @@ if (-d $modules_base/$version) {
}
-# Warn if we are ignoring the old ramdisk setting
-if ($ramdisk =~ /\S/) {
-my ($question, $ret, $seen);
-$question = ${package_name}/postinst/ignoring-ramdisk;
-($ret,$seen) = input('high', $question);
-die Error setting debconf question $question: $seen if $ret $ret !=
30;
-($ret,$seen) = go();
-die Error asking debconf question $question: $seen if $ret $ret != 30;
-}
-
# Only change the symlinks if we are not being upgraded
if (! defined $ARGV[1] || ! $ARGV[1] || $ARGV[1] =~ m/unknown/o) {
image_magic($kimage, $image_dest);
--- a/debian/templates/image.plain.templates.in
+++ b/debian/templates/image.plain.templates.in
@@ -52,12 +52,3 @@ _Description: Required firmware files ma
reconfigure the package manager to include the contrib and non-free
sections of the package archive before you can install these
firmware files.
-
-# This has not yet been reviewed
-Template: linux-image-@abiname@@localversion@/postinst/ignoring-ramdisk
-Type: error
-_Description: Ramdisk configuration must be updated
- Kernel packages will no longer run a specific ramdisk creator. The
- ramdisk creator package must install a script in
- /etc/kernel/postinst.d, and you should remove the line beginning
- 'ramdisk =' from /etc/kernel-img.conf.
--- a/debian/templates/po/ca.po
+++ b/debian/templates/po/ca.po
@@ -7,7 +7,7 @@ msgid
msgstr
Project-Id-Version: linux-2.6 2.6.32-24\n
Report-Msgid-Bugs-To: \n
-POT-Creation-Date: 2013-08-10 00:20+0200\n
+POT-Creation-Date: 2013-08-10 00:38+0200\n
PO-Revision-Date: 2013-08-15 13:20+0200\n
Last-Translator: Jordi Mallach jo...@debian.org\n
Language-Team: Catalan debian-l10n-cata...@lists.debian.org\n
@@ -129,18 +129,3 @@ msgstr
possible que necessiteu reconfigurar el gestor de paquets per a incloure les
seccions «contrib» i «non-free» de l'arxiu de paquets abans de poder
instaŀlar aquests fitxers de microprogramari.
-
-#. Type: error
-#. Description
-#: ../image.plain.templates.in:5001
-msgid Ramdisk configuration must be updated
-msgstr
-
-#. Type: error
-#. Description
-#: ../image.plain.templates.in:5001
-msgid
-Kernel packages will no longer run a specific ramdisk creator. The ramdisk
-creator package must install a script in /etc/kernel/postinst.d, and you
-should remove the line beginning 'ramdisk =' from /etc/kernel-img.conf.
-msgstr
--- a/debian/templates/po/cs.po
+++ b/debian/templates/po/cs.po
@@ -7,7 +7,7 @@ msgid
msgstr
Project-Id-Version: linux 3.2.21-3\n
Report-Msgid-Bugs-To: \n
-POT-Creation-Date: 2013-08-10 00:20+0200\n
+POT-Creation-Date: 2013-08-10 00:38+0200\n
PO-Revision-Date: 2012-06-30 13:02+0200\n
Last-Translator: Michal Simunek michal.simu...@gmail.com\n
Language-Team: Czech debian-l10n-cz...@lists.debian.org\n
@@ -122,22 +122,3 @@ msgstr
souladu se Zásadami svobodného softwaru Debianu. Než budete moci tyto
soubory s firmwarem nainstalovat, budete možná muset nastavit správce
balíčků, aby zahrnoval archiv sekce balíčků non-free.
-
-#. Type: error
-#. Description
-#: ../image.plain.templates.in:5001
-msgid Ramdisk configuration must be updated
-msgstr Nastavení ramdisku musí být aktualizováno
-
-#. Type: error
-#. Description
-#: ../image.plain.templates.in:5001
-msgid
-Kernel packages will no longer run a specific ramdisk creator. The ramdisk
-creator package must install a script in /etc/kernel/postinst.d, and you
-should remove the line beginning 'ramdisk =' from /etc/kernel-img.conf.
-msgstr
-Jaderný balíček již nespouští konkrétního tvůrce ramdisku. Balíček s tvůrcem
-ramdisku musí do adresáře /etc/kernel/postinst.d nainstalovat skript, a vy
-byste měli ze souboru /etc/kernel-img.conf odstranit řádek začínající
-'ramdisk ='.
--- a/debian/templates/po/da.po
+++ b/debian/templates/po/da.po
@@ -7,7 +7,7 @@ msgid
msgstr
Project-Id-Version: linux\n
Report-Msgid-Bugs-To: \n
-POT-Creation-Date:
[PATCH 3/3] linux-image.postinst: Remove debconf warning about missing firmware
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 work without it.
One thing we lose by doing this is a reminder that a firmware package
might also need to be upgraded, as a driver requires a newer version
of the firmware that has a different name. As an alternative, we
could compare the firmware file lists for old and new modules and only
warn about newly listed files that are missing. However, that would
also result in incorrect warnings for e.g. r8169 users, as that driver
may request a different file for each of the many chips it supports.
--- a/debian/templates/image.plain.postinst.in
+++ b/debian/templates/image.plain.postinst.in
@@ -522,98 +522,6 @@ sub do_modules {
}
}
}
-
- # If we are installing (not upgrading) a package for a newer
- # upstream version than that of the running kernel, check whether
- # the user might be missing necessary firmware, perhaps because
- # it has now been removed from the kernel.
- #
- # We base this check on the modules used in the running kernel and
- # the corresponding (by name) modules in the new kernel. This is
- # not entirely accurate because:
- # 1. A device may now be handled by a module with a different name,
- #leading us to miss the dependency
- # 2. A device may be handled by a module that needs firmware only
- #for some other device, leading us to claim a dependency wrongly
-
- if (!defined($ARGV[1]) || $ARGV[1] eq '') {
-sub version_code {
- my $version = shift;
- $version =~ s/^2\.(\d+)\.(\d+).*/2*65536 + $1*256 + $2/e
- or $version =~ s/^(\d+)\.(\d+).*/$1*65536 + $2*256/e
- or $version = 0;
- return $version;
-}
-(undef, undef, my $running_version) = POSIX::uname();
-
-if (version_code($version) version_code($running_version)) {
- my $missing = '';
- my %module_paths;
- open(DEP, $modules_base/$version/modules.dep) or return;
- while (DEP) {
- if (m|(.*/([^/]*)\.ko):|) {
- my ($path, $module) = ($1, $2);
- $module =~ s/-/_/g;
- $module_paths{$module} = $path;
- }
- }
- close(DEP);
- open(MODULES, '/proc/modules') or return;
- while (MODULES) {
- s/ .*//s;
- my $module = $_;
- my $module_path = $module_paths{$module};
- if (defined($module_path)) {
- my $first = 1;
- if ($module_path !~ m|^/|) {
- $module_path = $modules_base/$version/$module_path;
- }
- open(MODINFO, modinfo -F firmware '$module_path' |);
- while (MODINFO) {
- chomp;
- my $firmware = $_;
- unless (-e /lib/firmware/$firmware ||
- -e /lib/firmware/$version/$firmware) {
- if ($first) {
- $missing .= \\n if $missing ne '';
- $missing .= $module: ;
- $first = 0;
- } else {
- $missing .= ', ';
- }
- $missing .= $firmware;
- }
- }
- close(MODINFO);
- }
- }
- close(MODULES);
-
- if ($missing ne '') {
- my ($ret, $seen);
- my $text = ${package_name}/postinst/missing-firmware-${version};
-
- ($ret, $seen) = subst($text, 'runningversion', $running_version);
- die Error setting debconf substitutions in $text: $seen if $ret;
-
- ($ret, $seen) = subst($text, 'version', $version);
- die Error setting debconf substitutions in $text: $seen if $ret;
-
- ($ret, $seen) = subst($text, 'missing', $missing);
- die Error setting debconf substitutions in $text: $seen if $ret;
-
- ($ret, $seen) = input('high', $text);
- if ($ret $ret != 30) {
- die Error setting debconf question $text: $seen;
- }
-
- ($ret, $seen) = go();
- if ($ret $ret != 30) {
- die Error asking debconf question $text: $seen;
- }
- }
-}
- }
}
# We may not have any modules installed
--- a/debian/templates/po/ca.po
+++ b/debian/templates/po/ca.po
@@ -95,37 +95,3 @@ msgid
msgstr
És molt recomanable que avorteu la supressió del nucli si no esteu preparat
per a reparar el sistema després de la supressió.
-
-#. Type: note
-#. Description
-#: ../image.plain.templates.in:4001
-msgid Required firmware files may be missing
-msgstr És possible que manquen fitxers de microprogramari requerits
-
-#. Type: note
-#. Description
-#: ../image.plain.templates.in:4001
-msgid
-This system is currently running Linux ${runningversion} and you are
-installing Linux ${version}. In the new version some of the drivers used on
-this system may require additional firmware files:
-msgstr
-Actualment, el sistema està executant el Linux ${runningversion} i esteu
-instaŀlant
live-boot wheezy stuck during the boot process.
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? Thanks in advance!! atar. -- 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/op.w1uw03mle4gg2u@xp
Re: kernel in stable breaks gdb (on merulo)
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: Greetings! Stephen Gran sg...@debian.org writes: Hi, This one time, at band camp, Patrick Baggett said: Hi Camm, On Thu, Jul 4, 2013 at 10:51 AM, Camm Maguire c...@maguirefamily.orgwrote: Greetings! gdb stops with SIGTRAP at 0 on merulo, the sole debian ia64 porterbox. This is a known bug fixed in later versions of the 3.2 kernel series: http://www.mail-archive.com/debian-ia64@lists.debian.org/msg03404.html For some reason we are having trouble upgrading the kernel in the stable release, and debian-admin won't upgrade the merulo kernel without this. What is blocking the progress here? I would have thought Camm should try, at a guess, the maintainers of the kernel, as they should have something to do with uploads of the kernel. Maybe I've missed something, though. Indeed -- thanks! By way of further information, I can report that Dann Frazier has tried the kernel package in stable on his machine and can use gdb without issue. So would it be possible for the kernel maintainers listed above to determine why this bug, ostensibly fixed, is still present at merulo? Not a clue. Dann is the only kernel maintainer with responsibility for ia64 and I'm not sure he has much opportunity to work on it any more. I've just fixed occasional build failures; beyond that I don't know or care about the platform. Ben. -- Ben Hutchings The two most common things in the universe are hydrogen and stupidity. -- 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/caa9xbm4v8_mkxbuhykbb2mjsz3ytykukh_ho2zxhkhgvfw0...@mail.gmail.com
Re: live-boot wheezy stuck during the boot process.
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 to attach it to the mailing list. anyone can help? Thanks in advance!! This should be directed to the debian-l...@lists.debian.org list. Ben. -- Ben Hutchings Man invented language to satisfy his deep need to complain. - Lily Tomlin -- 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/1376573277.11676.133.ca...@deadeye.wl.decadent.org.uk
Bug#714974: [PATCH] jfs: avoid misuse of cookie value of 2
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
patch has so far only been lightly tested.
NFSv4 reserves cookie values 0, 1 and 2 for a rewind, and the . and ..
entries. jfs was using 0 and 1 for . and .., but 2 for a regular entry.
This patch makes jfs conform by using 1 and 2 for . and .. and fixes
any regular entry using the value 2.
Oh, I'd forgotten that. From rfc 5661:
For some file system environments, the directory entries . and
.. have special meaning, and in other environments, they do
not. If the server supports these special entries within a
directory, they SHOULD NOT be returned to the client as part of
the READDIR response. To enable some client environments, the
cookie values of zero, 1, and 2 are to be considered reserved.
Note that the UNIX client will use these values when combining
the server's response and local representations to enable a
fully formed UNIX directory presentation to the application.
OK!
--b.
Signed-off-by: Dave Kleikamp dave.kleik...@oracle.com
diff --git a/fs/jfs/jfs_dtree.c b/fs/jfs/jfs_dtree.c
index 8743ba9..93466e8 100644
--- a/fs/jfs/jfs_dtree.c
+++ b/fs/jfs/jfs_dtree.c
@@ -349,11 +349,8 @@ static u32 add_index(tid_t tid, struct inode *ip, s64
bn, int slot)
ASSERT(DO_INDEX(ip));
- if (jfs_ip-next_index 2) {
- jfs_warn(add_index: next_index = %d. Resetting!,
-jfs_ip-next_index);
- jfs_ip-next_index = 2;
- }
+ if (jfs_ip-next_index 3) {
+ jfs_ip-next_index = 3;
index = jfs_ip-next_index++;
@@ -2864,7 +2861,7 @@ void dtInitRoot(tid_t tid, struct inode *ip, u32
idotdot)
} else
ip-i_size = 1;
- jfs_ip-next_index = 2;
+ jfs_ip-next_index = 3;
} else
ip-i_size = IDATASIZE;
@@ -2951,7 +2948,7 @@ static void add_missing_indices(struct inode *inode,
s64 bn)
for (i = 0; i p-header.nextindex; i++) {
d = (struct ldtentry *) p-slot[stbl[i]];
index = le32_to_cpu(d-index);
- if ((index 2) || (index = JFS_IP(inode)-next_index)) {
+ if ((index 3) || (index = JFS_IP(inode)-next_index)) {
d-index = cpu_to_le32(add_index(tid, inode, bn, i));
if (dtlck-index = dtlck-maxcnt)
dtlck = (struct dt_lock *) txLinelock(dtlck);
@@ -3031,7 +3028,7 @@ int jfs_readdir(struct file *file, struct dir_context
*ctx)
struct jfs_dirent *jfs_dirent;
int jfs_dirents;
int overflow, fix_page, page_fixed = 0;
- static int unique_pos = 2; /* If we can't fix broken index */
+ static int unique_pos = 3; /* If we can't fix broken index */
if (ctx-pos == DIREND)
return 0;
@@ -3039,15 +3036,16 @@ int jfs_readdir(struct file *file, struct dir_context
*ctx)
if (DO_INDEX(ip)) {
/*
* persistent index is stored in directory entries.
- * Special cases:0 = .
- * 1 = ..
+ * Special cases:0 = rewind
+ * 1 = .
+ * 2 = ..
* -1 = End of directory
*/
do_index = 1;
dir_index = (u32) ctx-pos;
- if (dir_index 1) {
+ if (dir_index 2) {
struct dir_table_slot dirtab_slot;
if (dtEmpty(ip) ||
@@ -3090,18 +3088,18 @@ int jfs_readdir(struct file *file, struct dir_context
*ctx)
return 0;
}
} else {
- if (dir_index == 0) {
+ if (dir_index 2) {
/*
* self .
*/
- ctx-pos = 0;
+ ctx-pos = 1;
if (!dir_emit(ctx, ., 1, ip-i_ino, DT_DIR))
return 0;
}
/*
* parent ..
*/
- ctx-pos = 1;
+ ctx-pos = 2;
if (!dir_emit(ctx, .., 2, PARENT(ip), DT_DIR))
return 0;
@@ -3122,22 +3120,24 @@ int jfs_readdir(struct file *file, struct dir_context
*ctx)
/*
* Legacy filesystem - OS/2 Linux JFS 0.3.6
Processed: GDB stops with SIGTRAP at 0 address is back on ia64 Jessie
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 stops
with sigtrap at 0 address on ia64 wheezy
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions linux/3.2.35-2.
notfound 691576 linux-image-3.9-1-mckinley/3.9.8-1
Bug #691576 [src:linux] GDB stops with sigtrap at 0 address on ia64 wheezy
The source linux-image-3.9-1-mckinley and version 3.9.8-1 do not appear to
match any binary packages
Ignoring request to alter found versions of bug #691576 to the same values
previously set
found 691576 linux-image-3.10-2-mckinley/3.10.5-1
Bug #691576 [src:linux] GDB stops with sigtrap at 0 address on ia64 wheezy
The source linux-image-3.10-2-mckinley and version 3.10.5-1 do not appear to
match any binary packages
Marked as found in versions linux-image-3.10-2-mckinley/3.10.5-1.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
691576: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691576
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
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/handler.s.r.137658165024102.transcr...@bugs.debian.org
Bug#714974: [PATCH] jfs: avoid misuse of cookie value of 2
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
patch has so far only been lightly tested.
Hm, a first compile of 3.11-rc5 errors out with:
CC [M] fs/jfs/jfs_dtree.o
/usr/local/src/linux-git/fs/jfs/jfs_dtree.c: In function ‘add_index’:
/usr/local/src/linux-git/fs/jfs/jfs_dtree.c:493:13: error: invalid storage
class for function ‘free_index’
[...]
I'll run mrproper and try again...
This did not help, but adding a closing bracket did, in fs/jfs/jfs_dtree.c:354
if (jfs_ip-next_index 3) {
jfs_ip-next_index = 3;
}
-^
This compiled and booted and now I can run find(1) over that whole NFS
share, without any readdir loop messages and with unique inode numbers,
yay!
My bad. That's what happens when you clean up the patch after you test
it. I intended to remove the opening bracket when I removed a warning.
Tested-by: Christian Kujau li...@nerdbynature.de
Thanks. After sleeping on it, I'm contemplating a simpler patch. I'll
keep you up to date.
Thanks!
Christian.
--
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/520cd9c8.8000...@oracle.com
Bug#628444: iwlagn - MAC is in deep sleep, cannot restore wifi operation
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 (possibly due to a memory upgrade many months ago), but it still has chronic instability of the connection (drops out for varying intervals), and often, network-manager doesn't seem aware of the failure - reloading the driver isn't a reliable solution (sometimes appears to work, often does not) Does this bug still occur with more recent kernels/firmware, e.g. Wheezy? Cheers, Moritz -- 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/20130815163651.gb15...@inutil.org
Processed: Re: iwlagn - MAC is in deep sleep, cannot restore wifi operation
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 linux-2.6/3.2.9-1 and 2.6.39-1. Ignoring request to alter fixed versions of bug #628444 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 628444: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628444 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.137658488911022.transcr...@bugs.debian.org
Bug#628444: iwlagn - MAC is in deep sleep, cannot restore wifi operation
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 iwlwifi 11n_disable=1
since I am no longer running kernels which use iwlagn (currently
running 3.2.xx), I can't really speak to the original issue anymore.
Of course iwlwifi has had 11n related stability issues as well,
however, I have never seen the:
MAC is in deep sleep
bug (as far as I can recall) while running a newer kernel with iwlwifi
instead of iwlagn. Not sure how much code (if any) is common between
iwlwifi and the older iwlagn module.
AFAIK the code printing that particular error message is still the same
in 3.2. The error message was changed and a stack trace was added in
v3.4, so you have to look for another message if testing newer kernels:
commit aa5affbacb24cb5d8fd6f7c66e57d62164ed6d34
Author: Stanislaw Gruszka sgrus...@redhat.com
Date: Wed Mar 7 09:52:23 2012 -0800
iwlwifi: dump stack when fail to gain access to the device
Print dump stack when the device is not responding. This should give
some more clue about the reason of failure. Also change the message we
print, since MAC in deep sleep is kinda confusing.
On the way add unlikely(), as fail to gain NIC access is hmm ...
unlikely.
Signed-off-by: Stanislaw Gruszka sgrus...@redhat.com
Signed-off-by: Johannes Berg johannes.b...@intel.com
Signed-off-by: Wey-Yi Guy wey-yi.w@intel.com
Signed-off-by: John W. Linville linvi...@tuxdriver.com
diff --git a/drivers/net/wireless/iwlwifi/iwl-io.c
b/drivers/net/wireless/iwlwifi/iwl-io.c
index e2e3b5c..fc36535 100644
--- a/drivers/net/wireless/iwlwifi/iwl-io.c
+++ b/drivers/net/wireless/iwlwifi/iwl-io.c
@@ -121,10 +121,10 @@ int iwl_grab_nic_access_silent(struct iwl_trans *trans)
int iwl_grab_nic_access(struct iwl_trans *trans)
{
int ret = iwl_grab_nic_access_silent(trans);
- if (ret) {
+ if (unlikely(ret)) {
u32 val = iwl_read32(trans, CSR_GP_CNTRL);
- IWL_ERR(trans,
- MAC is in deep sleep!. CSR_GP_CNTRL = 0x%08X\n, val);
+ WARN_ONCE(1, Timeout waiting for hardware access
+(CSR_GP_CNTRL 0x%08x)\n, val);
}
return ret;
This code has since been refactored and moved into
drivers/net/wireless/iwlwifi/pcie/trans.c but the Timeout waiting for
hardware access message is still there.
I suppose I should try enabling 11n again to see what happens (I had
forgotten it was disabled).
Time to move on to 11ac now :)
Bjørn
--
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/87ppte7rg9@nemi.mork.no
Bug#628444: iwlagn - MAC is in deep sleep, cannot restore wifi operation
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 no longer running kernels which use iwlagn (currently running 3.2.xx), I can't really speak to the original issue anymore. Of course iwlwifi has had 11n related stability issues as well, however, I have never seen the: MAC is in deep sleep bug (as far as I can recall) while running a newer kernel with iwlwifi instead of iwlagn. Not sure how much code (if any) is common between iwlwifi and the older iwlagn module. I suppose I should try enabling 11n again to see what happens (I had forgotten it was disabled). The upgrade to wheezy is most notable for much shorter times required to make wireless connections, though I am not sure if it is the driver or network-manager responsible for that improvement. FWIW. Shannon C. Dealy | DeaTech Research Inc. de...@deatech.com | - Custom Software Development - Phone: (800) 467-5820 | - Natural Building Instruction - or: (541) 929-4089 | www.deatech.com On Thu, 15 Aug 2013, Moritz Muehlenhoff wrote: 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 (possibly due to a memory upgrade many months ago), but it still has chronic instability of the connection (drops out for varying intervals), and often, network-manager doesn't seem aware of the failure - reloading the driver isn't a reliable solution (sometimes appears to work, often does not) Does this bug still occur with more recent kernels/firmware, e.g. Wheezy? Cheers, Moritz -- 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/alpine.deb.2.02.1308151022300.20...@nashapur.deatech.com
Bug#719831: linux-image-3.10-2-686-pae: I/O errors after suspend/resume
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 remount in RO. Thanks, Luca -- Package-specific info: ** Version: Linux version 3.10-2-686-pae (debian-kernel@lists.debian.org) (gcc version 4.7.3 (Debian 4.7.3-6) ) #1 SMP Debian 3.10.5-1 (2013-08-07) ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.10-2-686-pae root=UUID=8fe61d81-3454-4fd7-86f3-3b119018117e ro quiet ** Not tainted ** Kernel log: [9.708678] ACPI: Video Device [VGA] (multi-head: yes rom: no post: no) [9.708930] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input6 [9.731744] cfg80211: Calling CRDA to update world regulatory domain [9.771353] input: HDA Intel Headphone as /devices/pci:00/:00:1b.0/sound/card0/input7 [9.771907] input: HDA Intel Mic as /devices/pci:00/:00:1b.0/sound/card0/input8 [ 10.103453] ath5k :02:00.0: registered as 'phy0' [ 10.146860] eeepc_laptop: Eee PC Hotkey Driver [ 10.146889] eeepc_laptop: Hotkey init flags 0x41 [ 10.147487] eeepc_laptop: TYPE (200) not reported by BIOS, enabling anyway [ 10.147504] eeepc_laptop: Get control methods supported: 0x2181711 [ 10.175448] input: Asus EeePC extra buttons as /devices/platform/eeepc/input/input9 [ 10.204426] ACPI Warning: 0x0828-0x082f SystemIO conflicts with Region \PMIO 1 (20130328/utaddress-251) [ 10.204448] ACPI Warning: 0x0828-0x082f SystemIO conflicts with Region \_SB_.PCI0.SBRG.PMS0 2 (20130328/utaddress-251) [ 10.204464] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 10.204476] ACPI Warning: 0x04b0-0x04bf SystemIO conflicts with Region \_SB_.PCI0.SBRG.GPSV 1 (20130328/utaddress-251) [ 10.204492] ACPI Warning: 0x04b0-0x04bf SystemIO conflicts with Region \_SB_.PCI0.SBRG.GPBX 2 (20130328/utaddress-251) [ 10.204507] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 10.204515] ACPI Warning: 0x0480-0x04af SystemIO conflicts with Region \_SB_.PCI0.SBRG.GPSV 1 (20130328/utaddress-251) [ 10.204531] ACPI Warning: 0x0480-0x04af SystemIO conflicts with Region \_SB_.PCI0.SBRG.GPBX 2 (20130328/utaddress-251) [ 10.204548] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 10.204554] lpc_ich: Resource conflict(s) found affecting gpio_ich [ 10.335847] cfg80211: World regulatory domain updated: [ 10.335856] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 10.335863] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 10.335869] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 10.335875] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [ 10.335880] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 10.335886] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 10.399024] leds_ss4200: no LED devices found [ 10.399114] [drm] Initialized drm 1.1.0 20060810 [ 10.435379] iTCO_vendor_support: vendor-support=0 [ 10.438309] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.10 [ 10.438388] iTCO_wdt: unable to reset NO_REBOOT flag, device disabled by hardware/BIOS [ 10.500684] [drm] Memory usable by graphics device = 256M [ 10.500707] i915 :00:02.0: setting latency timer to 64 [ 10.501374] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [ 10.501382] [drm] Driver supports precise vblank timestamp query. [ 10.502074] vgaarb: device changed decodes: PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [ 10.507042] [drm] initialized overlay support [ 10.518683] media: Linux media interface: v0.10 [ 10.530354] fbcon: inteldrmfb (fb0) is primary device [ 10.539905] Linux video capture interface: v2.00 [ 10.588906] uvcvideo: Found UVC 1.00 device Digital_Camera (093a:2700) [ 10.598129] input: Digital_Camera as /devices/pci:00/:00:1d.7/usb5/5-2/5-2:1.0/input/input10 [ 10.598717] usbcore: registered new interface driver uvcvideo [ 10.598720] USB Video Class driver (1.1.1) [ 10.688092] ath: EEPROM regdomain: 0x60 [ 10.688095] ath: EEPROM indicates we should expect a direct regpair map [ 10.688101] ath: Country alpha2 being used: 00 [ 10.688103] ath: Regpair used: 0x60 [ 10.774151] psmouse serio1: elantech: assuming hardware version 1 (with firmware version 0x020022) [ 10.848680] psmouse serio1: elantech: Synaptics capabilities query result 0x10, 0x02, 0x64. [ 11.211465] Console: switching to colour frame buffer device 128x37 [ 11.223681] i915 :00:02.0: fb0: inteldrmfb frame
Processed: update
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 as found in versions linux/3.9.8-1. Ignoring request to alter fixed versions of bug #719252 to the same values previously set found 719252 3.9.8-1 Bug #719252 [src:linux] ATA error message during stopping disk Marked as found in versions linux/3.9.8-1. found 719252 3.10.5-1 Bug #719252 [src:linux] ATA error message during stopping disk Marked as found in versions linux/3.10.5-1. thanks Stopping processing here. Please contact me if you need assistance. -- 719252: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719252 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.13765988181898.transcr...@bugs.debian.org
Bug#714974: [PATCH] jfs: fix readdir cookie incompatibility with NFSv4
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 entry. This incompatibility
can result in the nfs client reporting a readdir loop.
This patch doesn't change the value stored internally, but adds one to
the value exposed to the iterate method.
Signed-off-by: Dave Kleikamp dave.kleik...@oracle.com
---
fs/jfs/jfs_dtree.c | 31 +++
1 file changed, 23 insertions(+), 8 deletions(-)
diff --git a/fs/jfs/jfs_dtree.c b/fs/jfs/jfs_dtree.c
index 8743ba9..0ec767e 100644
--- a/fs/jfs/jfs_dtree.c
+++ b/fs/jfs/jfs_dtree.c
@@ -3047,6 +3047,14 @@ int jfs_readdir(struct file *file, struct dir_context
*ctx)
dir_index = (u32) ctx-pos;
+ /*
+* NFSv4 reserves cookies 1 and 2 for . and .. so we add
+* the value we return to the vfs is one greater than the
+* one we use internally.
+*/
+ if (dir_index)
+ dir_index--;
+
if (dir_index 1) {
struct dir_table_slot dirtab_slot;
@@ -3086,7 +3094,7 @@ int jfs_readdir(struct file *file, struct dir_context
*ctx)
if (p-header.flag BT_INTERNAL) {
jfs_err(jfs_readdir: bad index table);
DT_PUTPAGE(mp);
- ctx-pos = -1;
+ ctx-pos = DIREND;
return 0;
}
} else {
@@ -3094,14 +3102,14 @@ int jfs_readdir(struct file *file, struct dir_context
*ctx)
/*
* self .
*/
- ctx-pos = 0;
+ ctx-pos = 1;
if (!dir_emit(ctx, ., 1, ip-i_ino, DT_DIR))
return 0;
}
/*
* parent ..
*/
- ctx-pos = 1;
+ ctx-pos = 2;
if (!dir_emit(ctx, .., 2, PARENT(ip), DT_DIR))
return 0;
@@ -3122,22 +3130,23 @@ int jfs_readdir(struct file *file, struct dir_context
*ctx)
/*
* Legacy filesystem - OS/2 Linux JFS 0.3.6
*
-* pn = index = 0: First entry .
-* pn = 0; index = 1: Second entry ..
+* pn = 0; index = 1: First entry .
+* pn = 0; index = 2: Second entry ..
* pn 0: Real entries, pn=1 - leftmost page
* pn = index = -1: No more entries
*/
dtpos = ctx-pos;
- if (dtpos == 0) {
+ if (dtpos 2) {
/* build . entry */
+ ctx-pos = 1;
if (!dir_emit(ctx, ., 1, ip-i_ino, DT_DIR))
return 0;
- dtoffset-index = 1;
+ dtoffset-index = 2;
ctx-pos = dtpos;
}
if (dtoffset-pn == 0) {
- if (dtoffset-index == 1) {
+ if (dtoffset-index == 2) {
/* build .. entry */
if (!dir_emit(ctx, .., 2, PARENT(ip), DT_DIR))
return 0;
@@ -3228,6 +3237,12 @@ int jfs_readdir(struct file *file, struct dir_context
*ctx)
}
jfs_dirent-position = unique_pos++;
}
+ /*
+* We add 1 to the index because we may
+* use a value of 2 internally, and NFSv4
+* doesn't like that.
+*/
+ jfs_dirent-position++;
} else {
jfs_dirent-position = dtpos;
len = min(d_namleft, DTLHDRDATALEN_LEGACY);
--
1.8.3.4
--
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/520d3ea7.1010...@oracle.com
Bug#714974: [PATCH] jfs: fix readdir cookie incompatibility with NFSv4
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 messages and with unique inode numbers, great! Tested-by: Christian Kujau li...@nerdbynature.de Thanks for the fix! Christian. -- BOFH excuse #442: Trojan horse ran out of hay -- 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/alpine.deb.2.10.1308151420140.7...@trent.utfs.org
Bug#714974: [PATCH] jfs: fix readdir cookie incompatibility with NFSv4
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 to 3.11-rc5 and tested, no more readdir loop messages and with unique inode numbers, great! Tested-by: Christian Kujau li...@nerdbynature.de Thanks for the fix! Christian. Thanks for reporting, investigating and testing! Dave -- 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/520d519f.6080...@oracle.com
Build failure for armhf/armmp, linux 3.11-rc4
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] undefined!
ERROR: imx_pcm_fiq_exit [sound/soc/fsl/snd-soc-imx-ssi.ko] undefined!
ERROR: imx_pcm_dma_exit [sound/soc/fsl/snd-soc-imx-ssi.ko] undefined!
ERROR: imx_pcm_dma_init [sound/soc/fsl/snd-soc-fsl-ssi.ko] undefined!
ERROR: imx_pcm_dma_exit [sound/soc/fsl/snd-soc-fsl-ssi.ko] undefined!
These functions are defined in sound/soc/fsl/imx-pcm-{dma,fiq}.c which
are compiled into this kernel image. And the functions are exported.
Any ideas why this is failing?
Ben.
--
Ben Hutchings
I haven't lost my mind; it's backed up on tape somewhere.
--
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/1376605237.11042.16.ca...@deadeye.wl.decadent.org.uk
Bug#719843: linux-image-3.2.0-4-amd64: kernel bug in patch_generic_hdmi [snd_hda_codec_hdmi] on HP EliteBook 8770w
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. Usually takes 2 or 3 boots before it gets all the way thru and runs great for months (at least) thereafter. Thanks! Stephen -- Package-specific info: ** Version: Linux version 3.2.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.46-1 ** Command line: auto BOOT_IMAGE=Linux ro root=UUID=7fb615b4-c967-4f5c-a727-d7191d884cc5 ** Tainted: DO (4224) * Kernel has oopsed before. * Out-of-tree module has been loaded. ** Kernel log: [9.724752] input: HDA Intel PCH Mic as /devices/pci:00/:00:1b.0/sound/card0/input11 [9.724978] input: HDA Intel PCH Mic as /devices/pci:00/:00:1b.0/sound/card0/input12 [9.725127] input: HDA Intel PCH Line-out as /devices/pci:00/:00:1b.0/sound/card0/input13 [9.725268] input: HDA Intel PCH Headphone as /devices/pci:00/:00:1b.0/sound/card0/input14 [9.805486] Console: switching to colour frame buffer device 240x67 [9.818487] fb0: radeondrmfb frame buffer device [9.818535] drm: registered panic notifier [9.818596] [drm] Initialized radeon 2.16.0 20080528 for :01:00.0 on minor 0 [9.818910] snd_hda_intel :01:00.1: irq 53 for MSI/MSI-X [9.818954] snd_hda_intel :01:00.1: setting latency timer to 64 [ 10.339555] BUG: unable to handle kernel paging request at 8802338304f0 [ 10.339647] IP: [a0565368] patch_generic_hdmi+0x199/0x2c3 [snd_hda_codec_hdmi] [ 10.339739] PGD 1606063 PUD bef6f067 PMD 231a54063 PTE 800233830161 [ 10.339827] Oops: 0003 [#1] SMP [ 10.339872] CPU 5 [ 10.339895] Modules linked in: snd_hda_codec_hdmi snd_hda_codec_idt joydev tpm_infineon arc4 radeon snd_seq_midi snd_hda_intel(+) snd_seq_midi_event snd_hda_codec snd_rawmidi snd_hwdep snd_pcm_oss snd_mixer_oss snd_seq iwlwifi snd_pcm parport_pc snd_seq_device uvcvideo ttm parport mac80211 videodev hp_wmi drm_kms_helper snd_page_alloc v4l2_compat_ioctl32 coretemp crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 aes_generic i2c_i801 sparse_keymap snd_timer media cryptd pcspkr psmouse serio_raw evdev drm snd cfg80211 battery iTCO_wdt i2c_algo_bit rfkill i2c_core iTCO_vendor_support soundcore container wmi video tpm_tis tpm hp_accel(+) tpm_bios acpi_cpufreq lis3lv02d mperf input_polldev ac processor power_supply button ext4 crc16 jbd2 mbcache dm_mod sg sr_mod sd_mod cdrom crc_t10dif xhci_hcd ahci libahci libata scsi_mod firewire_ohci sdhci_pci sdhci firewire_core mmc_core crc_itu_t ehci_hcd usbcore thermal thermal_sys e1000e usb_common [last unloaded: scsi_wait_scan] [ 10.341178] [ 10.341199] Pid: 522, comm: modprobe Not tainted 3.2.0-4-amd64 #1 Debian 3.2.46-1 Hewlett-Packard HP EliteBook 8770w/176C [ 10.341320] RIP: 0010:[a0565368] [a0565368] patch_generic_hdmi+0x199/0x2c3 [snd_hda_codec_hdmi] [ 10.341430] RSP: 0018:880233573c78 EFLAGS: 00010202 [ 10.341484] RAX: 2440 RBX: 88023331b000 RCX: 1c7da248 [ 10.341554] RDX: 185600f0 RSI: RDI: 88023331b000 [ 10.341625] RBP: 88023382e000 R08: R09: 88023d00cc00 [ 10.341695] R10: 0094 R11: 0094 R12: 000b [ 10.341765] R13: 000b R14: 000c R15: 0009 [ 10.341837] FS: 7fc96af54700() GS:88023dd4() knlGS: [ 10.341917] CS: 0010 DS: ES: CR0: 8005003b [ 10.341975] CR2: 8802338304f0 CR3: 00023346e000 CR4: 001406e0 [ 10.342046] DR0: DR1: DR2: [ 10.342117] DR3: DR6: 0ff0 DR7: 0400 [ 10.342188] Process modprobe (pid: 522, threadinfo 880233572000, task 8802305dcee0) [ 10.342269] Stack: [ 10.342292] 88023331b000 000b a0569000 fff4 [ 10.342385] 88023331b000 a0569000 a0567288 [ 10.342476] a0569fb0 a0531981 a0329f64 2d6164682d646e73 [ 10.342568] Call Trace: [ 10.342605] [a0531981] ? snd_hda_codec_configure+0x2b9/0x3cc [snd_hda_codec] [ 10.342690] [a0329f64] ? azx_acquire_irq+0x93/0x93 [snd_hda_intel] [ 10.342772] [a032ba48] ? azx_probe+0x82e/0x905 [snd_hda_intel] [ 10.346399] [8134eb77] ? _raw_spin_unlock_irqrestore+0xe/0xf [ 10.350034] [811c610f] ? local_pci_probe+0x39/0x68 [ 10.353678] [811c6bb8] ? pci_device_probe+0xcd/0xfa [ 10.357332] [812517a9] ? driver_probe_device+0xa8/0x138 [ 10.361011] [81251888] ? __driver_attach+0x4f/0x6f [ 10.364667]
Bug#719277: linux-image-3.11-rc4-amd64: Kernel crashes when running Folding@Home as a system service
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 extract the kernel log from the dump. When I run the 'log' command within crash I get this message: log: WARNING: log buf data structure(s) have changed I can, however, get a backtrace and the process status information from the dump. If you think it would be useful, I can output what I am able to get from crash to a file to send to you for you to look at. Also, I have a few questions: 1) Is there any way at all to give the crash kernel more memory to work with? kdump-tools does not work if I specify an amount greater than 128M in the bootloader config file (the system does not reboot into the crash kernel), which seems unnecessarily small for a system with 4GB of memory available, and it seems like the small amount of memory available slows things down considerably. 2) How long should the crash dump collection process normally take? I've noticed that it usually takes about 4 or 5 minutes after the system finishes rebooting for the dump and dmesg files to show up in the crash dump folder specified (prior to which there's only one file, dump_incomplete), however the makedumpfile process seems to continue running even after 5 hours (watching it with top). 3) Is the system supposed to boot as normal when booting into the crash kernel to collect the crash dump? I ask, because mine does, and the severely limited amount of memory available doesn't seem to allow for a full boot. (I suspect I may need to specifically tell kdump-tools to boot into a more suitable runlevel, as it doesn't appear to do so on its own.) -- 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/520d6bc6.90...@gmail.com
Bug#719847: linux-image-3.10-2-amd64: hang and timout populating /dev no console after boot
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 is how I'm generating this report. This is an update/upgrade from wheezy. I had the same problem with the linux-image-3.9-1-amd64kernel, but had other priorities and didn't have time to work on it then. The linux-image-3.2.0-4-amd64 kernel worked fine and still will load and run fine using the jessie libs etc. I'll try building a custom kernel and see what that leads to. pete -- Package-specific info: ** Version: Linux version 3.10-2-amd64 (debian-kernel@lists.debian.org) (gcc version 4.7.3 (Debian 4.7.3-6) ) #1 SMP Debian 3.10.5-1 (2013-08-07) ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.10-2-amd64 root=UUID=3e23aeb5-68a5-49d1-a5db-ab53b5b3157b ro quiet ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [ 480.432548] [8111212a] ? __inode_permission+0x57/0x95 [ 480.432551] [811148cc] ? path_openat+0xc2/0x327 [ 480.432555] [81114dd4] ? do_filp_open+0x2a/0x6e [ 480.432560] [810fa39f] ? kmem_cache_alloc+0x8c/0xfd [ 480.432564] [8111dc59] ? __alloc_fd+0xcc/0xdb [ 480.432568] [81108a24] ? do_sys_open+0x5c/0xe0 [ 480.432572] [8138d4a9] ? system_call_fastpath+0x16/0x1b [ 600.432038] INFO: task modprobe:516 blocked for more than 120 seconds. [ 600.432044] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [ 600.432046] modprobeD 8802bfd94040 0 516431 0x0004 [ 600.432052] 8802b1070080 0086 8802b45920c0 00014040 [ 600.432056] 8802b1061fd8 8802b1061fd8 8802b1070080 8802b0d9c400 [ 600.432060] 8802b0d9c790 [ 600.432064] Call Trace: [ 600.432083] [a01da2c7] ? i801_transaction+0xa4/0xe9 [i2c_i801] [ 600.432090] [81057c48] ? abort_exclusive_wait+0x79/0x79 [ 600.432094] [a01dae08] ? i801_access+0x7a6/0x888 [i2c_i801] [ 600.432100] [8113aeeb] ? ep_poll_callback+0xe8/0x101 [ 600.432104] [8105d056] ? __wake_up_common+0x3f/0x71 [ 600.432113] [a01cecb0] ? i2c_smbus_xfer+0xc3/0x11d [i2c_core] [ 600.432118] [a01d0069] ? i2c_do_del_adapter+0x8/0x8f [i2c_core] [ 600.432124] [a01cfdaf] ? i2c_default_probe+0x93/0xf5 [i2c_core] [ 600.432129] [a01d0069] ? i2c_do_del_adapter+0x8/0x8f [i2c_core] [ 600.432135] [a01cfebe] ? i2c_do_add_adapter+0xad/0x22b [i2c_core] [ 600.432140] [811c3bf2] ? kobject_uevent_env+0x3de/0x420 [ 600.432146] [a01d003c] ? i2c_do_add_adapter+0x22b/0x22b [i2c_core] [ 600.432151] [a01d003c] ? i2c_do_add_adapter+0x22b/0x22b [i2c_core] [ 600.432156] [8127699f] ? bus_for_each_dev+0x4b/0x7c [ 600.432161] [a01d003c] ? i2c_do_add_adapter+0x22b/0x22b [i2c_core] [ 600.432167] [a01ce37c] ? i2c_for_each_dev+0x29/0x3f [i2c_core] [ 600.432172] [a01cf260] ? i2c_register_driver+0x7a/0x9f [i2c_core] [ 600.432182] [a010d000] ? 0xa010cfff [ 600.432186] [a010d000] ? 0xa010cfff [ 600.432190] [8100209e] ? do_one_initcall+0x74/0x106 [ 600.432195] [a010d000] ? 0xa010cfff [ 600.432200] [81082b8b] ? load_module+0x1b16/0x1e16 [ 600.432204] [8107f78e] ? free_notes_attrs+0x3c/0x3c [ 600.432209] [81082f29] ? SyS_init_module+0x9e/0xab [ 600.432214] [8138d4a9] ? system_call_fastpath+0x16/0x1b [ 600.432220] INFO: task modprobe:601 blocked for more than 120 seconds. [ 600.43] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [ 600.432224] modprobeD 8802bfc94040 0 601412 0x0006 [ 600.432228] 8802b3dbe040 0082 8802b44b4780 00014040 [ 600.432231] 8802b2ec5fd8 8802b2ec5fd8 8802b3dbe040 a01d20e0 [ 600.432235] 8802b3dbe040 a01d20e4 0002 [ 600.432239] Call Trace: [ 600.432246] [81387996] ? schedule_preempt_disabled+0x5/0x6 [ 600.432250] [81386a60] ? __mutex_lock_common.isra.8+0x1a3/0x1bf [ 600.432257] [a01cfa50] ? i2c_register_adapter+0x285/0x285 [i2c_core] [ 600.432260] [81386834] ? mutex_lock+0x17/0x27 [ 600.432266] [a01cfa61] ? i2c_add_adapter+0x11/0x59 [i2c_core] [ 600.432271] [a01e06aa] ? __i2c_bit_add_bus+0x33/0x284 [i2c_algo_bit] [ 600.432311] [a035f26f] ? radeon_i2c_create+0x1b8/0x1ea [radeon] [ 600.432338] [a034930a] ? radeon_combios_i2c_init+0x5b/0x227 [radeon] [ 600.432368] [a035cfe0] ? radeon_modeset_init+0x8da/0x916 [radeon] [ 600.432392] [a0340965] ?
Re: Build failure for armhf/armmp, linux 3.11-rc4
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 [sound/soc/fsl/snd-soc-imx-ssi.ko] undefined!
ERROR: imx_pcm_dma_init [sound/soc/fsl/snd-soc-imx-ssi.ko] undefined!
ERROR: imx_pcm_fiq_exit [sound/soc/fsl/snd-soc-imx-ssi.ko] undefined!
ERROR: imx_pcm_dma_exit [sound/soc/fsl/snd-soc-imx-ssi.ko] undefined!
ERROR: imx_pcm_dma_init [sound/soc/fsl/snd-soc-fsl-ssi.ko] undefined!
ERROR: imx_pcm_dma_exit [sound/soc/fsl/snd-soc-fsl-ssi.ko] undefined!
These functions are defined in sound/soc/fsl/imx-pcm-{dma,fiq}.c which
are compiled into this kernel image. And the functions are exported.
Any ideas why this is failing?
Ben,
This is fixed in the sound next branch:
https://git.kernel.org/cgit/linux/kernel/git/broonie/sound.git/commit/?h=for-nextid=3f1a91aa25579ba5e7268a47a73d2a83e4802c62
for v3.11-rc5 i just have them both built-in..
CONFIG_SND_SOC_IMX_SSI=y
CONFIG_SND_SOC_IMX_PCM_DMA=y
But after a quick search i couldn't find your v3.11-rc5 config to do a
full config diff..
Regards,
--
Robert Nelson
http://www.rcn-ee.com/
--
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/caochtyipkq-pd8zmfrkx6io5i+ubgcn37c-tir3zdtytido...@mail.gmail.com
