Bug#484432: linux-image-2.6.24-1-versatile: Please enable the RTC
Package: linux-image-2.6.24-1-versatile Version: 2.6.24-7 Severity: important # CONFIG_RTC_DRV_PL031 is not set This is both the device emulated by qemu, and the device present (I believe) on real Versatile boards. Without it qemu always starts the clock at the epoch. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.25-rc9 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#484365: closed by maximilian attems <[EMAIL PROTECTED]> (Re: suggestion: switch to linux-libre in main)
On Jun 3, 2008, [EMAIL PROTECTED] (Debian Bug Tracking System) wrote: > first of all such suggestion are better discussed on > mailing list see http://wiki.debian.org/DebianKernel I'm not really interested in taking part in a debate. I was merely offering a suggestion in the form of a bug report, as suggested by a friend of mine who's involved in Debian's development. I'll let him know the procedure he suggested was inappropriate and suggest him to follow that route. Thanks, and sorry if this caused any trouble. > why did none of your effort got productive AFAICT we have produced a working 100% Free kernel, something that Debian has wished for for several years. Our goals are different from those of kernel upstream or Debian, that appear to feel a need to help hardware vendors keep their customers helpless and dependent. Catering to this kind of issue is not part of the charter of this project. > and turned into upstream patches? upstream wouldn't take patches that remove the non-Free Software, and we already have the kernel we need. It wouldn't make sense for us to work more to advance goals that are actually opposite to ours. > nor do you seem to work on relicensing firmware. That's also not part of the project charter. The goal of the project is to ensure there are well-maintained 100% Free Linux tarballs for anyone who wishes to take freedom seriously. Work on getting firmware relicensed as Free Software is certainly good work to do, but it's not part of this project. > why does it not incorporate the upstream posted request_firmware() > patches from David Woodhouse? or did i oversee them!?! Because it doens't incorporate any patches whatsoever. It tracks upstream. If David's patches are merged, our scripts will be adjusted to remove the non-Free bits from wherever they land, if they remain. If they aren't, why bother?, they don't make any difference for someone who does not want to install non-Free Software on their computers anyway, or for distros that don't want to be part of the distribution of any non-Free Software to their users. These are the use cases linux-libre is designed to serve. > closing as you can only be kidding to consider yourself as appropriate > linux-2.6 upstream source. I'm not kidding, but it's not really upstream. You can regard it as a filter midstream that keeps downstream from polution thrown in the river by upstream. We don't mess with the precious water, we just remove the pollutants. Now, if you prefer to keep on deviating from your own policies and counting on exceptions to ensure main can keep on containing non-Free Software, that's certainly your decision. If you'd rather duplicate this work yourselves, it might make sense to join forces, for I take it you've been trying to fix this problem for a very long time. I offered help because I thought Debian might be interested, considering its policies and all. Of course, you don't have to trust us right away. You can keep an eye for a while and see how quickly our releases come out after an upstream release, and how easily patches for upstream still apply. I've been doing that for freed-ora for a while, it's really a no-brainer. And then, should we fail you, you might as well just go back to your beloved non-free upstream :-) Your call... Best regards, and keep up the good work, -- Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/ Free Software Evangelist [EMAIL PROTECTED], gnu.org} FSFLA Board Member ¡Sé Libre! => http://www.fsfla.org/ Red Hat Compiler Engineer [EMAIL PROTECTED], gcc.gnu.org} -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#484365: suggestion: switch to linux-libre in main
On Jun 3, 2008, Thiemo Seufer <[EMAIL PROTECTED]> wrote: > What are the specific instances of non-free software you found in > Debian's kernel? I ran deblob-check on http://ftp.br.debian.org/debian/pool/main/l/linux-2.6/linux-2.6_2.6.25.orig.tar.gz that I found referenced as the source tarball for some linux-2.6 Debian package on some debian.org web page. Then I ran deblob-check with -C, and it printed a few megabytes. Then I deleted both the tarball and the output. > I didn't find documentation about what was actually removed. You can find deblob-check as well as the much smaller deblob scripts for each upstream release at http://fsfla.org/svn/fsfla/software/linux-libre/scripts/ -- Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/ Free Software Evangelist [EMAIL PROTECTED], gnu.org} FSFLA Board Member ¡Sé Libre! => http://www.fsfla.org/ Red Hat Compiler Engineer [EMAIL PROTECTED], gcc.gnu.org} -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#482007: marked as done (redhat-cluster_2.20080229-1.1(sparc/unstable): FTBFS on sparc, error: 'ret' may be used uninitialized in this function)
Your message dated Tue, 03 Jun 2008 22:32:09 + with message-id <[EMAIL PROTECTED]> and subject line Bug#482007: fixed in redhat-cluster 2.20080603-1 has caused the Debian Bug report #482007, regarding redhat-cluster_2.20080229-1.1(sparc/unstable): FTBFS on sparc, error: 'ret' may be used uninitialized in this function to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 482007: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=482007 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: redhat-cluster Version: 2.20080229-1.1 Severity: serious There was an error while trying to autobuild your package: > Automatic build of redhat-cluster_2.20080229-1.1 on spontini by sbuild/sparc > 99.99 > Build started at 20080519-2319 [...] > ** Using build dependencies supplied by package: > Build-Depends: dpatch, debhelper (>= 4.2.28), libxml2-dev, libncurses5-dev, > libopenais-dev (>= 0.82-2), libvolume-id-dev (>= 0.105-4), linux-libc-dev (>= > 2.6.24), libvirt-dev (>= 0.3.0) [amd64 i386], libnss3-dev [amd64 i386], > libnspr4-dev [amd64 i386], bzip2, libslang2-dev [...] > gcc -o clufindhostname clufindhostname.o -L/usr/lib -L../clulib -lclulib > gcc -g -O2 -Wall -Wformat=2 -O2 -g > -I/build/buildd/redhat-cluster-2.20080229/config > -DDEFAULT_CONFIG_DIR=\"/etc/cluster\" -DDEFAULT_CONFIG_FILE=\"cluster.conf\" > -DRELEASE_VERSION=\"2.0\" -Wall -Wformat=2 -O2 -g > -I/build/buildd/redhat-cluster-2.20080229/config > -DDEFAULT_CONFIG_DIR=\"/etc/cluster\" -DDEFAULT_CONFIG_FILE=\"cluster.conf\" > -DRELEASE_VERSION=\"2.0\" -Wall -Wformat=2 -O2 -g > -I/build/buildd/redhat-cluster-2.20080229/config > -DDEFAULT_CONFIG_DIR=\"/etc/cluster\" -DDEFAULT_CONFIG_FILE=\"cluster.conf\" > -DRELEASE_VERSION=\"2.0\" -Wall -Wformat=2 -O2 -g > -I/build/buildd/redhat-cluster-2.20080229/config > -DDEFAULT_CONFIG_DIR=\"/etc/cluster\" -DDEFAULT_CONFIG_FILE=\"cluster.conf\" > -DRELEASE_VERSION=\"2.0\" -Werror -Wstrict-prototypes -Wshadow -fPIC > -D_GNU_SOURCE -I/build/buildd/redhat-cluster-2.20080229/ccs/lib > -I/build/buildd/redhat-cluster-2.20080229/cman/lib > -I/build/buildd/redhat-cluster-2.20080229/dlm/lib -I/usr/include > -I/build/buildd/redhat-cluster-2.20080229/rgmanager/src/utils/../../include > -I/usr/include -c -o clustat.o > /build/buildd/redhat-cluster-2.20080229/rgmanager/src/utils/clustat.c > cc1: warnings being treated as errors > /build/buildd/redhat-cluster-2.20080229/rgmanager/src/utils/clustat.c: In > function 'txt_cluster_status': > /build/buildd/redhat-cluster-2.20080229/rgmanager/src/utils/clustat.c:830: > error: 'ret' may be used uninitialized in this function > make[4]: *** [clustat.o] Error 1 > make[4]: Leaving directory > `/build/buildd/redhat-cluster-2.20080229/rgmanager/src/utils' > make[3]: *** [all] Error 2 > make[3]: Leaving directory > `/build/buildd/redhat-cluster-2.20080229/rgmanager/src' > make[2]: *** [all] Error 2 > make[2]: Leaving directory `/build/buildd/redhat-cluster-2.20080229/rgmanager' > make[1]: *** [rgmanager] Error 2 > make[1]: Leaving directory `/build/buildd/redhat-cluster-2.20080229' > make: *** [build-stamp] Error 2 > dpkg-buildpackage: failure: debian/rules build gave error exit status 2 A full build log can be found at: http://buildd.debian.org/build.php?arch=sparc&pkg=redhat-cluster&ver=2.20080229-1.1 --- End Message --- --- Begin Message --- Source: redhat-cluster Source-Version: 2.20080603-1 We believe that the bug you reported is fixed in the latest version of redhat-cluster, which is due to be installed in the Debian FTP archive: cman_2.20080603-1_amd64.deb to pool/main/r/redhat-cluster/cman_2.20080603-1_amd64.deb gfs-tools_2.20080603-1_amd64.deb to pool/main/r/redhat-cluster/gfs-tools_2.20080603-1_amd64.deb gfs2-tools_2.20080603-1_amd64.deb to pool/main/r/redhat-cluster/gfs2-tools_2.20080603-1_amd64.deb gnbd-client_2.20080603-1_amd64.deb to pool/main/r/redhat-cluster/gnbd-client_2.20080603-1_amd64.deb gnbd-server_2.20080603-1_amd64.deb to pool/main/r/redhat-cluster/gnbd-server_2.20080603-1_amd64.deb libcman-dev_2.20080603-1_amd64.deb to pool/main/r/redhat-cluster/libcman-dev_2.20080603-1_amd64.deb libcman2_2.20080603-1_amd64.deb to pool/main/r/redhat-cluster/libcman2_2.20080603-1_amd64.deb libdlm-dev_2.20080603-1_amd64.deb to pool/main/r/redhat-cluster/libdlm-dev_2.20080603-1_amd64.deb libdlm2_2.20080603-1_amd64.deb to pool/main/r/redhat-cluster/libdlm2_2.20080603-1_amd64.deb redhat-cluster-source_2.20080603-1_all.deb to pool/main/r/redhat-cluster/redhat-cluster-source_2.20080603-1_all.deb redhat-cluster-suite
Bug#479721: marked as done (FTBFS with 2.6.25-1)
Your message dated Tue, 03 Jun 2008 22:32:09 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#479721: fixed in redhat-cluster 2.20080603-1
has caused the Debian Bug report #479721,
regarding FTBFS with 2.6.25-1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
479721: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479721
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: redhat-cluster
Severity: serious
Hi,
your package fails to build with 2.6.25-1.
As a side note, if you try to compile it yourself, make sure you have
linux-kbuild with debian version 2.6.25-2. Due to a bug in -1, it would
fail (for different reasons) anyway.
Regards,
Daniel
--
Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist
Email: [EMAIL PROTECTED]
Internet: http://people.panthera-systems.net/~daniel-baumann/
for templ in
/usr/src/modules/redhat-cluster/debian/redhat-cluster-modules-_KVERS_.postinst;
do \
cp $templ `echo $templ | sed -e 's/_KVERS_/2.6.25-1-686/g'` ; \
done
for templ in `ls debian/*.modules.in` ; do \
test -e ${templ%.modules.in}.backup || cp ${templ%.modules.in}
${templ%.modules.in}.backup 2>/dev/null || true; \
sed -e 's/##KVERS##/2.6.25-1-686/g ;s/#KVERS#/2.6.25-1-686/g ;
s/_KVERS_/2.6.25-1-686/g ; s/##KDREV##/2.6.25-1/g ; s/#KDREV#/2.6.25-1/g ;
s/_KDREV_/2.6.25-1/g ' < $templ > ${templ%.modules.in}; \
done
dh_clean
/usr/bin/make -C /lib/modules/2.6.25-1-686/build
M=/usr/src/modules/redhat-cluster clean USING_KBUILD=1
make[1]: Entering directory `/usr/src/linux-headers-2.6.25-1-686'
make[1]: Leaving directory `/usr/src/linux-headers-2.6.25-1-686'
/usr/bin/make -f debian/rules kdist_clean kdist_config binary-modules
make[1]: Entering directory `/usr/src/modules/redhat-cluster'
for templ in
/usr/src/modules/redhat-cluster/debian/redhat-cluster-modules-_KVERS_.postinst;
do \
cp $templ `echo $templ | sed -e 's/_KVERS_/2.6.25-1-686/g'` ; \
done
for templ in `ls debian/*.modules.in` ; do \
test -e ${templ%.modules.in}.backup || cp ${templ%.modules.in}
${templ%.modules.in}.backup 2>/dev/null || true; \
sed -e 's/##KVERS##/2.6.25-1-686/g ;s/#KVERS#/2.6.25-1-686/g ;
s/_KVERS_/2.6.25-1-686/g ; s/##KDREV##/2.6.25-1/g ; s/#KDREV#/2.6.25-1/g ;
s/_KDREV_/2.6.25-1/g ' < $templ > ${templ%.modules.in}; \
done
dh_clean
/usr/bin/make -C /lib/modules/2.6.25-1-686/build
M=/usr/src/modules/redhat-cluster clean USING_KBUILD=1
/bin/sh:
/usr/src/linux-headers-2.6.25-1-686/scripts/gcc-x86_64-has-stack-protector.sh:
No such file or directory
/bin/sh:
/usr/src/linux-headers-2.6.25-1-686/scripts/gcc-x86_64-has-stack-protector.sh:
No such file or directory
make[2]: Entering directory `/usr/src/linux-headers-2.6.25-1-686'
make[2]: Leaving directory `/usr/src/linux-headers-2.6.25-1-686'
make[1]: Nothing to be done for `kdist_config'.
dh_testdir
dh_testroot
dh_clean -k
# build the module
make -C /lib/modules/2.6.25-1-686/build M=/usr/src/modules/redhat-cluster/
modules USING_KBUILD=1
make[2]: Entering directory `/usr/src/linux-headers-2.6.25-1-686'
CC [M] /usr/src/modules/redhat-cluster/gfs/acl.o
CC [M] /usr/src/modules/redhat-cluster/gfs/bits.o
CC [M] /usr/src/modules/redhat-cluster/gfs/bmap.o
CC [M] /usr/src/modules/redhat-cluster/gfs/daemon.o
CC [M] /usr/src/modules/redhat-cluster/gfs/dio.o
CC [M] /usr/src/modules/redhat-cluster/gfs/dir.o
CC [M] /usr/src/modules/redhat-cluster/gfs/eaops.o
CC [M] /usr/src/modules/redhat-cluster/gfs/eattr.o
CC [M] /usr/src/modules/redhat-cluster/gfs/file.o
CC [M] /usr/src/modules/redhat-cluster/gfs/glock.o
CC [M] /usr/src/modules/redhat-cluster/gfs/glops.o
CC [M] /usr/src/modules/redhat-cluster/gfs/inode.o
CC [M] /usr/src/modules/redhat-cluster/gfs/ioctl.o
CC [M] /usr/src/modules/redhat-cluster/gfs/lm.o
CC [M] /usr/src/modules/redhat-cluster/gfs/log.o
CC [M] /usr/src/modules/redhat-cluster/gfs/lops.o
CC [M] /usr/src/modules/redhat-cluster/gfs/lvb.o
CC [M] /usr/src/modules/redhat-cluster/gfs/main.o
CC [M] /usr/src/modules/redhat-cluster/gfs/mount.o
CC [M] /usr/src/modules/redhat-cluster/gfs/ondisk.o
CC [M] /usr/src/modules/redhat-cluster/gfs/ops_address.o
CC [M] /usr/src/modules/redhat-cluster/gfs/ops_dentry.o
CC [M] /usr/src/modules/redhat-cluster/gfs/ops_export.o
CC [M] /usr/src/modules/redhat-cluster/gfs/ops_file.o
CC [M] /usr/src/modules/redhat-cluster/gfs/ops_fstype.o
CC [M] /usr/src/modules/redhat-cluster/gfs/ops_inode.o
CC [M] /usr/src/modules/redhat-cluster/gfs/ops_super.o
CC [M] /usr/src/modules/redhat-
Bug#483781: Ответ: Bug#483781: FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
OK, thank you for documenting the test cases. (No wonder I never stumbled into problems: I use Chinese, which probably has very few upper/lower case pairs.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
redhat-cluster_2.20080603-1_amd64.changes ACCEPTED
Accepted: cman_2.20080603-1_amd64.deb to pool/main/r/redhat-cluster/cman_2.20080603-1_amd64.deb gfs-tools_2.20080603-1_amd64.deb to pool/main/r/redhat-cluster/gfs-tools_2.20080603-1_amd64.deb gfs2-tools_2.20080603-1_amd64.deb to pool/main/r/redhat-cluster/gfs2-tools_2.20080603-1_amd64.deb gnbd-client_2.20080603-1_amd64.deb to pool/main/r/redhat-cluster/gnbd-client_2.20080603-1_amd64.deb gnbd-server_2.20080603-1_amd64.deb to pool/main/r/redhat-cluster/gnbd-server_2.20080603-1_amd64.deb libcman-dev_2.20080603-1_amd64.deb to pool/main/r/redhat-cluster/libcman-dev_2.20080603-1_amd64.deb libcman2_2.20080603-1_amd64.deb to pool/main/r/redhat-cluster/libcman2_2.20080603-1_amd64.deb libdlm-dev_2.20080603-1_amd64.deb to pool/main/r/redhat-cluster/libdlm-dev_2.20080603-1_amd64.deb libdlm2_2.20080603-1_amd64.deb to pool/main/r/redhat-cluster/libdlm2_2.20080603-1_amd64.deb redhat-cluster-source_2.20080603-1_all.deb to pool/main/r/redhat-cluster/redhat-cluster-source_2.20080603-1_all.deb redhat-cluster-suite_2.20080603-1_all.deb to pool/main/r/redhat-cluster/redhat-cluster-suite_2.20080603-1_all.deb redhat-cluster_2.20080603-1.diff.gz to pool/main/r/redhat-cluster/redhat-cluster_2.20080603-1.diff.gz redhat-cluster_2.20080603-1.dsc to pool/main/r/redhat-cluster/redhat-cluster_2.20080603-1.dsc redhat-cluster_2.20080603.orig.tar.gz to pool/main/r/redhat-cluster/redhat-cluster_2.20080603.orig.tar.gz rgmanager_2.20080603-1_amd64.deb to pool/main/r/redhat-cluster/rgmanager_2.20080603-1_amd64.deb Override entries for your package: cman_2.20080603-1_amd64.deb - optional admin gfs-tools_2.20080603-1_amd64.deb - optional admin gfs2-tools_2.20080603-1_amd64.deb - optional admin gnbd-client_2.20080603-1_amd64.deb - optional admin gnbd-server_2.20080603-1_amd64.deb - optional admin libcman-dev_2.20080603-1_amd64.deb - optional libdevel libcman2_2.20080603-1_amd64.deb - optional libs libdlm-dev_2.20080603-1_amd64.deb - optional libdevel libdlm2_2.20080603-1_amd64.deb - optional libs redhat-cluster-source_2.20080603-1_all.deb - optional admin redhat-cluster-suite_2.20080603-1_all.deb - optional admin redhat-cluster_2.20080603-1.dsc - source admin rgmanager_2.20080603-1_amd64.deb - optional admin Announcing to [EMAIL PROTECTED] Closing bugs: 479721 482007 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#463653: marked as done (linux-modules-2.6.18-6-xen-amd64: e1000 doesn't work any more)
Your message dated Wed, 4 Jun 2008 00:19:28 +0200 with message-id <[EMAIL PROTECTED]> and subject line Re: linux-modules-2.6.18-6-xen-amd64: e1000 doesn't work any more has caused the Debian Bug report #463653, regarding linux-modules-2.6.18-6-xen-amd64: e1000 doesn't work any more to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 463653: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=463653 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: linux-modules-2.6.18-6-xen-amd64 Version: 2.6.18.dfsg.1-17etch1 Severity: important With the update to 2.6.18-6-xen-amd64 the e1000 module doesn't seem to work any more. I found the following in the kern.log when trying to load the kernel module: Feb 1 16:33:35 urd kernel: e1000: :08:00.0: e1000_probe: PHY reset is blocked due to SOL/IDER session. Feb 1 16:33:35 urd kernel: e1000: :08:00.0: e1000_probe: The EEPROM Checksum Is Not Valid Feb 1 16:33:35 urd kernel: e1000: probe of :08:00.0 failed with error -5 TIA Martin --- End Message --- --- Begin Message --- Version: 2.6.24-1 > Feb 1 16:33:35 urd kernel: e1000: :08:00.0: e1000_probe: The EEPROM > Checksum Is Not Valid > Feb 1 16:33:35 urd kernel: e1000: probe of :08:00.0 failed with error -5 fixed in newer e1000 driver, thus closing. thanks for report. -- maks --- End Message ---
Bug#443314: linux-image-2.6.22-2-686: kernel BUG at fs/nfs/nfs4xdr.c:716! on NFSv4 client
On Wed, 30 Jan 2008, maximilian attems wrote: > > As soon as kernel 2.6.23 is released I will upgrade the computers... > > can we have an update on that issue, sid has 2.6.24 inbetween. please give an update on 2.6.25, as no oops was posted since initial i'd assume otherwise fixed with newer nfs4 thanks for feedback. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing of redhat-cluster_2.20080603-1_amd64.changes
redhat-cluster_2.20080603-1_amd64.changes uploaded successfully to localhost along with the files: redhat-cluster_2.20080603-1.dsc redhat-cluster_2.20080603.orig.tar.gz redhat-cluster_2.20080603-1.diff.gz cman_2.20080603-1_amd64.deb libcman2_2.20080603-1_amd64.deb libcman-dev_2.20080603-1_amd64.deb libdlm2_2.20080603-1_amd64.deb libdlm-dev_2.20080603-1_amd64.deb gfs-tools_2.20080603-1_amd64.deb gfs2-tools_2.20080603-1_amd64.deb gnbd-client_2.20080603-1_amd64.deb gnbd-server_2.20080603-1_amd64.deb rgmanager_2.20080603-1_amd64.deb redhat-cluster-suite_2.20080603-1_all.deb redhat-cluster-source_2.20080603-1_all.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#457044: marked as done (My box doesn't reboot after each upgrade of linux-image)
Your message dated Wed, 4 Jun 2008 00:17:57 +0200 with message-id <[EMAIL PROTECTED]> and subject line Re: My box doesn't reboot after each upgrade of linux-image has caused the Debian Bug report #457044, regarding My box doesn't reboot after each upgrade of linux-image to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 457044: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=457044 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: linux-image-2.6.18-4-686 Version: linux-image-2.6.18-4-686 2.6.18.dfsg.1-12etch2 Severity: critical Justification: breaks the whole system This morning, as usual I did : apt-get update apt-get upgrade today, there was a security update on linux-image-2.6.18-4-686 I followed the given instructions : >You are attempting to install a kernel version that is the same as the version >you are currently running (version 2.6.18-4-686). >The modules list is quite likely to have been changed, and the modules >dependency file /lib/modules/2.6.18-4-686/modules.dep needs to be re-built. >It can not be built correctly right now, since the module list for the running >kernel are likely to be different from the kernel installed. >I am creating a new modules.dep file, but that may not be correct. It shall be >regenerated correctly at next reboot. > ? > >I repeat: you have to reboot in order for the modules file to be created >correctly. Until you reboot, it may be impossible to load some modules. > Reboot as soon as this install is finished (Do not reboot right now, since > you may not be able to boot back up until installation is over, but boot > immediately after). >I can not stress that too much. You need to reboot soon. So I rebooted my machine (a distant one) And then... nothing else. My production server never came up until now. I asked to my hosting provider an electrical reboot as I had no way to act, but the machine didn't boot. As it's a distant server, I can't tell you what error messages it can show. The only thing I can provide is the listing of the session from the apt-get upgrade command to the reboot command I'll send it in a next post Of course, I'm not sending this report for the concerned server, as at the moment it's dead, but from a local test box with a very similar configuration -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.18-4-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored: LC_ALL set to [EMAIL PROTECTED]) Shell: /bin/sh linked to /bin/bash -- Ce message a été vérifié par MailScanner pour des virus ou des polluriels et rien de suspect n'a été trouvé. For all your IT requirements visit: http://www.transtec.co.uk --- End Message --- --- Begin Message --- closing as real boot error didn't come up. most probably a missing lilo run. using lilo is masochistic, grub is the default since some time. all the best. -- maks --- End Message ---
Bug#484365: suggestion: switch to linux-libre in main
Alexandre Oliva wrote: > Package: linux-2.6 > Severity: normal > > > In case you're not aware, the linux-libre project grew out of > gNewSense's efforts to publish 100% Free Software extracts from the > kernel distributed by kernel.org, later on picked up by BLAG and, more > recently, by FSF Latin America. You might want to use it, instead of > kernel.org's kernel, to get closer to compliance with your policy of > shipping only Free Software in main. > > Whether you move the non-Free kernel you currently ship to non-free, or > simply remove it, is something you should discuss and decide on your > own, but I thought I'd remind you of both possibilities. What are the specific instances of non-free software you found in Debian's kernel? > linux-libre is currently available at > http://www.fsfla.org/~lxoliva/fsfla/linux-libre/ > > There's a README in there. We're considering creating a freed-ebian > repository with linux-libre-based kernels for Debian GNU/Linux in there, > but we hope that, knowing how seriously you take your social contract > and the freedom of your users, I thought you might want to preempt > that move. I didn't find documentation about what was actually removed. Thiemo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 482007
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.26 > tags 482007 + pending Bug#482007: redhat-cluster_2.20080229-1.1(sparc/unstable): FTBFS on sparc, error: 'ret' may be used uninitialized in this function There were no tags set. Tags added: pending > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#484365: marked as done (suggestion: switch to linux-libre in main)
Your message dated Wed, 4 Jun 2008 00:05:11 +0200 with message-id <[EMAIL PROTECTED]> and subject line Re: suggestion: switch to linux-libre in main has caused the Debian Bug report #484365, regarding suggestion: switch to linux-libre in main to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 484365: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=484365 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: linux-2.6 Severity: normal In case you're not aware, the linux-libre project grew out of gNewSense's efforts to publish 100% Free Software extracts from the kernel distributed by kernel.org, later on picked up by BLAG and, more recently, by FSF Latin America. You might want to use it, instead of kernel.org's kernel, to get closer to compliance with your policy of shipping only Free Software in main. Whether you move the non-Free kernel you currently ship to non-free, or simply remove it, is something you should discuss and decide on your own, but I thought I'd remind you of both possibilities. linux-libre is currently available at http://www.fsfla.org/~lxoliva/fsfla/linux-libre/ There's a README in there. We're considering creating a freed-ebian repository with linux-libre-based kernels for Debian GNU/Linux in there, but we hope that, knowing how seriously you take your social contract and the freedom of your users, I thought you might want to preempt that move. In case you'd like to make such a move using an older version of Linux than those we've already deblobbed, I'd be happy to assist. Just let us know at [EMAIL PROTECTED] Hope this helps, and that Debian one more time sets an example of promoting the Free Software philosophy and caring about users' freedom. Best regards, --- End Message --- --- Begin Message --- first of all such suggestion are better discussed on mailing list see http://wiki.debian.org/DebianKernel > In case you're not aware, the linux-libre project grew out of > gNewSense's efforts to publish 100% Free Software extracts from the > kernel distributed by kernel.org, later on picked up by BLAG and, more > recently, by FSF Latin America. You might want to use it, instead of > kernel.org's kernel, to get closer to compliance with your policy of > shipping only Free Software in main. why did none of your effort got productive and turned into upstream patches? nor do you seem to work on relicensing firmware. > Whether you move the non-Free kernel you currently ship to non-free, or > simply remove it, is something you should discuss and decide on your > own, but I thought I'd remind you of both possibilities. > > linux-libre is currently available at > http://www.fsfla.org/~lxoliva/fsfla/linux-libre/ why does it not incorporate the upstream posted request_firmware() patches from David Woodhouse? or did i oversee them!?! closing as you can only be kidding to consider yourself as appropriate linux-2.6 upstream source. -- maks --- End Message ---
Processed: tagging 482387
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.26 > tags 482387 + pending Bug#482387: iwl3945: please include the monitor mode patch. Tags were: fixed-upstream patch Tags added: pending > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#484365: suggestion: switch to linux-libre in main
Package: linux-2.6 Severity: normal In case you're not aware, the linux-libre project grew out of gNewSense's efforts to publish 100% Free Software extracts from the kernel distributed by kernel.org, later on picked up by BLAG and, more recently, by FSF Latin America. You might want to use it, instead of kernel.org's kernel, to get closer to compliance with your policy of shipping only Free Software in main. Whether you move the non-Free kernel you currently ship to non-free, or simply remove it, is something you should discuss and decide on your own, but I thought I'd remind you of both possibilities. linux-libre is currently available at http://www.fsfla.org/~lxoliva/fsfla/linux-libre/ There's a README in there. We're considering creating a freed-ebian repository with linux-libre-based kernels for Debian GNU/Linux in there, but we hope that, knowing how seriously you take your social contract and the freedom of your users, I thought you might want to preempt that move. In case you'd like to make such a move using an older version of Linux than those we've already deblobbed, I'd be happy to assist. Just let us know at [EMAIL PROTECTED] Hope this helps, and that Debian one more time sets an example of promoting the Free Software philosophy and caring about users' freedom. Best regards, -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#428895: Configuring Xen domain 0 to use serial console
On Tue, 2008-06-03 at 23:12 +0200, Bastian Blank wrote:
> On Tue, Jun 03, 2008 at 09:07:35PM +0100, Ian Campbell wrote:
> > Unfortunately this doesn't help with wanting to use serial ports for
> > non-console use in domain 0, although passing xencons={off,tty} might
> > free up the ttyS device major for 8250.ko to use.
>
> xencons=xvc console=/dev/xvc0
Unfortunately the "xvc" console type isn't present in the Etch kernel.
Ian.
--
Ian Campbell
Disk crisis, please clean up!
signature.asc
Description: This is a digitally signed message part
Processed: unmerging 396169
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.28 > unmerge 396169 Bug#396169: linux-image-2.6.18-1-xen-686: Does not support PC serial ports Bug#397797: no serial console support in xen kernel Bug#428895: No way to use serial console with Xen kernel Disconnected #396169 from all other report(s). > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#428895: Configuring Xen domain 0 to use serial console
On Tue, Jun 03, 2008 at 09:07:35PM +0100, Ian Campbell wrote:
> Unfortunately this doesn't help with wanting to use serial ports for
> non-console use in domain 0, although passing xencons={off,tty} might
> free up the ttyS device major for 8250.ko to use.
xencons=xvc console=/dev/xvc0
Bastian
--
Those who hate and fight must stop themselves -- otherwise it is not stopped.
-- Spock, "Day of the Dove", stardate unknown
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
openais_0.83-1_amd64.changes ACCEPTED
Accepted: libopenais-dev_0.83-1_amd64.deb to pool/main/o/openais/libopenais-dev_0.83-1_amd64.deb libopenais2_0.83-1_amd64.deb to pool/main/o/openais/libopenais2_0.83-1_amd64.deb openais_0.83-1.diff.gz to pool/main/o/openais/openais_0.83-1.diff.gz openais_0.83-1.dsc to pool/main/o/openais/openais_0.83-1.dsc openais_0.83-1_amd64.deb to pool/main/o/openais/openais_0.83-1_amd64.deb openais_0.83.orig.tar.gz to pool/main/o/openais/openais_0.83.orig.tar.gz Override entries for your package: libopenais-dev_0.83-1_amd64.deb - optional libdevel libopenais2_0.83-1_amd64.deb - optional libs openais_0.83-1.dsc - source admin openais_0.83-1_amd64.deb - optional admin Announcing to [EMAIL PROTECTED] Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#402969: marked as done (linux-image-2.6.18-3-xen-686: blktab driver for XEN is disabled)
Your message dated Tue, 3 Jun 2008 22:30:40 +0200 with message-id <[EMAIL PROTECTED]> and subject line Re: Bug#402969: linux-image-2.6.18-3-xen-686: blktab driver for XEN is disabled has caused the Debian Bug report #402969, regarding linux-image-2.6.18-3-xen-686: blktab driver for XEN is disabled to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 402969: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=402969 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: linux-image-2.6.18-3-xen-686 Version: 2.6.18-6 Severity: important The blktab driver is disabled: CONFIG_XEN_BLKDEV_TAP is not set in config-2.6.18-3-xen-686 Without these driver I must use the deprecated loopback-mounted file-backed VBDs ... see point 6.2.1 of the XEN user.pdf. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (990, 'testing'), (900, 'stable'), (700, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-xen-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages linux-image-2.6.18-3-xen-686 depends on: ii initramfs-tools 0.85b tools for generating an initramfs ii linux-modules-2.6.18-3-xen-68 2.6.18-6 Linux 2.6.18 modules on PPro/Celer Versions of packages linux-image-2.6.18-3-xen-686 recommends: ii libc6-xen2.3.6.ds1-8 GNU C Library: Shared libraries [X -- no debconf information --- End Message --- --- Begin Message --- adding the blktab driver would be a nice feature, but is pretty significant according to xen maintainer and thus not suitable for a stable release. also the blktap user tool is missing in Etch. "For Lenny it will only become relevant when the paravirt_ops kernels support domain 0, at that time it definitely makes sense to enable blktap." - Ian Campbell we always enable new drivers when they are merged upstream see http://wiki.debian.org/DebianKernelPatchAcceptanceGuidelines for more info thanks for the report -- maks --- End Message ---
Processing of openais_0.83-1_amd64.changes
openais_0.83-1_amd64.changes uploaded successfully to localhost along with the files: openais_0.83-1.dsc openais_0.83.orig.tar.gz openais_0.83-1.diff.gz openais_0.83-1_amd64.deb libopenais2_0.83-1_amd64.deb libopenais-dev_0.83-1_amd64.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#428895: Configuring Xen domain 0 to use serial console
It is possible to use a serial console with a Xen kernel by configuring
Xen to use a serial console and Linux to use the Xen console, which may
(confusingly) actually be masquerading as ttyS in the 2.6.18 kernels.
For example I use "xen.gz com1=115200,8n1 console=com1" together with
"vmlinuz console=/dev/ttyS0 xencons=ttyS" (the xencons=ttyS is redundant
in the kernel from Etch since it is the default in domain0)
Unfortunately this doesn't help with wanting to use serial ports for
non-console use in domain 0, although passing xencons={off,tty} might
free up the ttyS device major for 8250.ko to use.
Ian.
--
Ian Campbell
You may call me by my name, Wirth, or by my value, Worth.
-- Nicklaus Wirth
signature.asc
Description: This is a digitally signed message part
Bug#481125: [linux-image-2.6.24-1-amd64] Booting sometime freeze 8 to 9 minutes
On Tue, Jun 03, 2008 at 08:41:54PM +0200, Robert Chéramy wrote: > Hi, > > I just tried latest kernel from unstable, and still have the problem. > > $ uname -a > Linux rubis 2.6.25-2-amd64 #1 SMP Tue May 27 12:45:24 UTC 2008 x86_64 > GNU/Linux > $ dpkg -l | grep linux-image-2.6.25 > ii linux-image-2.6.25-2-amd64 > 2.6.25-4 Linux 2.6.25 image on AMD64 > > Robert here you have newer 2.6.24-rc4, please check it out -> http://photon.itp.tuwien.ac.at/~mattems/ if it still does not work upstream bug report would be cool. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#481125: [linux-image-2.6.24-1-amd64] Booting sometime freeze 8 to 9 minutes
Hi, I just tried latest kernel from unstable, and still have the problem. $ uname -a Linux rubis 2.6.25-2-amd64 #1 SMP Tue May 27 12:45:24 UTC 2008 x86_64 GNU/Linux $ dpkg -l | grep linux-image-2.6.25 ii linux-image-2.6.25-2-amd64 2.6.25-4 Linux 2.6.25 image on AMD64 Robert maximilian attems schrieb: > On Tue, 13 May 2008, Robert Chéramy wrote: > > >> Package: linux-image-2.6.24-1-amd64 >> Version: 2.6.24-6 >> Severity: normal >> >> --- Please enter the report below this line. --- >> >> Hi, >> >> I've got a Dell inspiron 530n (the ones sold with ubuntu preinstalled). >> Some times, not systematicly (perhaps every third power on and at most >> reboots), the boot process is blocked 8 to 9 minutes (see attached dmesg >> for the point of freeze). The keyboard is freezed (Caps or Num LED won't >> change). >> >> After this random time, the boot process goes on and the system boots up >> normaly. >> > > please try out 2.6.25 from unstable and give feedback on it? > installs just fine in testing. > > thanks > >
Bug#382985: marked as done (teergrubes NATted connections due to mangled IPv4 checksums)
Your message dated Tue, 3 Jun 2008 16:23:55 +0200 with message-id <[EMAIL PROTECTED]> and subject line Re: teergrubes NATted connections due to mangled IPv4 checksums has caused the Debian Bug report #382985, regarding teergrubes NATted connections due to mangled IPv4 checksums to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 382985: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=382985 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: linux-image-2.6.16-2-xen-686 Version: 2.6.16-17 Severity: grave A recently added optimization skips checksums on all packets it believes are destined for another Xen domain inside the same box. Too bad, it is sometimes wrong -- an analysis can be found on http://lists.xensource.com/archives/html/xen-users/2006-03/msg00159.html This had been fixed before -- NETIF_F_NO_CSUM was changed to 0; however, in the current version of the Xen patch in unstable it is again enabled, set to NETIF_F_IP_CSUM (ie, IPv4 tcp and udp only) this time. Unfortunately, an idiot running nearly only IPv6 can miss this bug, unknowingly teergrubing other hosts. I've personally managed to do this to lists.debian.org, making it keep a number of exim4 processes trying to deliver mail to my server. Thus, it was suggested to file this bug as 'grave'. IPv4 ICMP, all IPv6 and connections which actually don't leave the box work fine; same for those which get bridged away to a physical interface without passing through NAT. The fix: as in the quoted link, change dev->features= NETIF_F_IP_CSUM; to dev->features= 0; -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing'), (202, 'unstable'), (201, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-2-xen-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.16-2-xen-686 depends on: ii initramfs-tools [linux-initra 0.73c tools for generating an initramfs ii linux-modules-2.6.16-2-xen-68 2.6.16-17 Linux kernel modules 2.6.16 image Versions of packages linux-image-2.6.16-2-xen-686 recommends: ii libc6-xen 2.3.6-19 GNU C Library: Shared libraries [X -- no debconf information --- End Message --- --- Begin Message --- > The fix: as in the quoted link, change > dev->features= NETIF_F_IP_CSUM; > to > dev->features= 0; upstream 2.6.26-rc4 has still netdev->features= NETIF_F_IP_CSUM; so i doubt that this bug report is valid. closing -- maks --- End Message ---
Bug#241963: marked as done (kernel-image-2.6.4-1-686: aic79xx occasionally loses track of SCBs)
Your message dated Tue, 3 Jun 2008 14:19:22 +0200 with message-id <[EMAIL PROTECTED]> and subject line Re: kernel-image-2.6.4-1-686: aic79xx occasionally loses track of SCBs has caused the Debian Bug report #241963, regarding kernel-image-2.6.4-1-686: aic79xx occasionally loses track of SCBs to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 241963: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=241963 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: kernel-image-2.6.4-1-686 Version: 2.6.4-1 Severity: normal Over the past few weeks, I've had problems with both an Adaptec AIC-29320 and an AIC-29320A card. On the same system, using an AIC-29160 card has no problems. Given that I've had similar problems with 2 different cards using the aic79xx driver, this makes me think the problem is with the driver not the hardware. I should note that I've experienced these problems not only with kernel-image-2.6.4-1-686, but also the 2.6.3 image, and the 2.4.24 image. I had the card plugged into PCI-32 slots on the Intel D865GBF motherboard. I had 4 Maxtor ATLASU320_73_WLS Rev: B430 drives connected to the internal LVD connector using an U320-rated cable (I tried replacing the cable and terminator just to be sure; that had no effect either). I also had an old HP C5683A tape drive connected to the internal SE connector part of the time. My /etc/modules-2.6 contained sd_mod ide-cd ide-detect aic79xx uhci-hcd md intel-agp pcspkr I have RAID-5 configured on the 4 SCSI drives using the md driver. Here's what the kernel reported on this card when it booted this morning, as per kern.log: Apr 3 09:26:25 fig kernel: scsi2 : Adaptec AIC79XX PCI-X SCSI HBA DRIVER, Rev 1.3.11 Apr 3 09:26:25 fig kernel: Apr 3 09:26:25 fig kernel: aic7901: Ultra320 Wide Channel A, SCSI Id=7, PCI 33 or 66Mhz, 512 SCBs Apr 3 09:26:25 fig kernel: Apr 3 09:26:25 fig kernel: (scsi2:A:0): 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|RTI|QAS, 16bit) Apr 3 09:26:25 fig kernel: (scsi2:A:2): 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|RTI|QAS, 16bit) Apr 3 09:26:25 fig kernel: (scsi2:A:3): 40.000MB/s transfers (20.000MHz, 16bit) Apr 3 09:26:25 fig kernel: (scsi2:A:4): 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|RTI|QAS, 16bit) Apr 3 09:26:25 fig kernel: (scsi2:A:6): 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|RTI|QAS, 16bit) Apr 3 09:26:25 fig kernel: Vendor: MAXTORModel: ATLASU320_73_WLS Rev: B430 Apr 3 09:26:25 fig kernel: Type: Direct-Access ANSI SCSI revision: 03 Apr 3 09:26:25 fig kernel: scsi2:A:0:0: Tagged Queuing enabled. Depth 32 Apr 3 09:26:25 fig kernel: SCSI device sda: 143666192 512-byte hdwr sectors (73557 MB) Apr 3 09:26:25 fig kernel: SCSI device sda: drive cache: write back Apr 3 09:26:25 fig kernel: /dev/scsi/host2/bus0/target0/lun0: p1 Apr 3 09:26:25 fig kernel: Attached scsi disk sda at scsi2, channel 0, id 0, lun 0 Apr 3 09:26:25 fig kernel: Vendor: MAXTORModel: ATLASU320_73_WLS Rev: B430 Apr 3 09:26:25 fig kernel: Type: Direct-Access ANSI SCSI revision: 03 Apr 3 09:26:25 fig kernel: scsi2:A:2:0: Tagged Queuing enabled. Depth 32 Apr 3 09:26:25 fig kernel: SCSI device sdb: 143666192 512-byte hdwr sectors (73557 MB) Apr 3 09:26:25 fig kernel: SCSI device sdb: drive cache: write back Apr 3 09:26:25 fig kernel: /dev/scsi/host2/bus0/target2/lun0: p1 Apr 3 09:26:25 fig kernel: Attached scsi disk sdb at scsi2, channel 0, id 2, lun 0 Apr 3 09:26:25 fig kernel: Vendor: HPModel: C5683ARev: C908 Apr 3 09:26:25 fig kernel: Type: Sequential-Access ANSI SCSI revision: 02 Apr 3 09:26:25 fig kernel: Vendor: MAXTORModel: ATLASU320_73_WLS Rev: B430 Apr 3 09:26:25 fig kernel: Type: Direct-Access ANSI SCSI revision: 03 Apr 3 09:26:25 fig kernel: scsi2:A:4:0: Tagged Queuing enabled. Depth 32 Apr 3 09:26:25 fig kernel: SCSI device sdc: 143666192 512-byte hdwr sectors (73557 MB) Apr 3 09:26:25 fig kernel: SCSI device sdc: drive cache: write back Apr 3 09:26:25 fig kernel: /dev/scsi/host2/bus0/target4/lun0: p1 Apr 3 09:26:25 fig kernel: Attached scsi disk sdc at scsi2, channel 0, id 4, lun 0 Apr 3 09:26:25 fig kernel: Vendor: MAXTORModel: ATLASU320_73_WLS Rev: B430 Apr 3 09:26:25 fig kernel: Type: Direct-Access ANSI SCSI revision: 03 Apr 3 09:26:25 fig kernel: scsi2:A:6:0: Tagged Queuing enabled. Depth 32 Apr 3 09:26:25 fig kernel: SCSI device sdd: 143666192 512-byte hdwr
Bug#470426: marked as done (linux-image-2.6.18-6-xen-amd64: UnionFS not available for Xen Kernels)
Your message dated Tue, 3 Jun 2008 13:58:50 +0200 with message-id <[EMAIL PROTECTED]> and subject line Re: linux-image-2.6.18-6-xen-amd64: UnionFS not available for Xen Kernels has caused the Debian Bug report #470426, regarding linux-image-2.6.18-6-xen-amd64: UnionFS not available for Xen Kernels to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 470426: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=470426 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: linux-image-2.6.18-6-xen-amd64 Version: 2.6.18.dfsg.1-18etch1 Severity: wishlist I'd like to request UnionFS be packaged for the Xen kernels. It's currently not available, and unionfs/aufs/etc are very useful when working with Xen. Given that Xen kernels don't build as easily as 'normal' kernels with debian's build tools, having a pre-packaged unionfs could potentially save a lot of people grief. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-6-xen-amd64 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.18-6-xen-amd64 depends on: ii e2f 1.39+1.40-WIP-2006.11.14+dfsg-2etch1 ext2 file system utilities and lib ii ini 0.85htools for generating an initramfs ii lin 2.6.18.dfsg.1-18etch1Linux 2.6.18 modules on AMD64 linux-image-2.6.18-6-xen-amd64 recommends no packages. -- no debconf information --- End Message --- --- Begin Message --- source is available to build it against xen kernels. thus closing. -- maks --- End Message ---
Bug#402533: marked as done (ata.2 CD-ROM errors on boot)
Your message dated Tue, 3 Jun 2008 13:47:07 +0200 with message-id <[EMAIL PROTECTED]> and subject line Re: ata.2 CD-ROM errors on boot has caused the Debian Bug report #402533, regarding ata.2 CD-ROM errors on boot to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 402533: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=402533 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: linux-image-2.6.18-3-686 Version: 2.6.18-7 Booting a Toshiba Tecra S2 running Debian Etch. System pauses and posts the following messages: ata2.01: qc timeout (cmd 0xa1) ata2.01: failed to IDENTIFY (I/O error, err_mask=0x4) ata2: failed to recover some devices, retrying in 5 secs ata2.01: qc timeout (cmd 0xa1) ata2.01: failed to IDENTIFY (I/O error, err_mask=0x4) ata2: failed to recover some devices, retrying in 5 secs ata2.01: qc timeout (cmd 0xa1) ata2.01: failed to IDENTIFY (I/O error, err_mask=0x4) ata2: failed to recover some devices, retrying in 5 secs ata2.00: configured for UDMA/33 Vendor: MATSHITA Model: UJDA750 DVD/CDRW Rev: 1.60 Type: CD-ROM ANSI SCSI revision: 05 Booting continues normally after that. The system runs fine after booting. lspci gives: 00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller (rev 03) 00:01.0 PCI bridge: Intel Corporation Mobile 915GM/PM Express PCI Express Root Port (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1 (rev 03) 00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 03) 00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 03) 00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 (rev 03) 00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 (rev 03) 00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev d3) 00:1e.2 Multimedia audio controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller (rev 03) 00:1e.3 Modem: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Modem Controller (rev 03) 00:1f.0 ISA bridge: Intel Corporation 82801FBM (ICH6M) LPC Interface Bridge (rev 03) 00:1f.2 IDE interface: Intel Corporation 82801FBM (ICH6M) SATA Controller (rev 03) 00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus Controller (rev 03) 01:00.0 VGA compatible controller: ATI Technologies Inc M24 1P [Radeon Mobility X600] 02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8053 PCI-E Gigabit Ethernet Controller (rev 15) 06:02.0 Network controller: Intel Corporation PRO/Wireless 2915ABG Network Connection (rev 05) 06:04.0 CardBus bridge: Texas Instruments PCIxx21/x515 Cardbus Controller 06:04.1 CardBus bridge: Texas Instruments PCIxx21/x515 Cardbus Controller 06:04.2 FireWire (IEEE 1394): Texas Instruments OHCI Compliant IEEE 1394 Host Controller 06:04.3 Mass storage controller: Texas Instruments PCIxx21 Integrated FlashMedia Controller 06:04.4 Generic system peripheral [0805]: Texas Instruments PCI6411, PCI6421, PCI6611, PCI6621, PCI7411, PCI7421, PCI7611, PCI7621 Secure Digital (SD) Controller __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --- End Message --- --- Begin Message --- Version: 2.6.25-1 fixed in upstream commit e59724c7db9afd14827f1b737605f54d47f2d226 * Add IDE_CD_FLAG_PLAY_AUDIO_OK flag and handle quirky MATSHITA DVD-ROMs using ide_cd_quirks_list[]. available in unstable, thus closing. -- maks --- End Message ---
Bug#402083: marked as done (USB infinite event loop)
Your message dated Tue, 3 Jun 2008 13:35:53 +0200 with message-id <[EMAIL PROTECTED]> and subject line Re: USB infinite event loop has caused the Debian Bug report #402083, regarding USB infinite event loop to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 402083: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=402083 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: linux-image-2.6.17-2-686 Version: 2.6.17-9 Hardware: Laptop Acer 1692 WLMi Keyboard: USB Genius KKB-2040US OS: Debian Etch (testing) uname -a: Linux portatil 2.6.17-2-686 #1 SMP Wed Sep 13 16:34:10 UTC 2006 i686 GNU/Linux When the system boots the message "drivers/usb/input/hid-core.c: input irq status -75 received" is displayed until the keyboard is disconnected from USB or any special multimedia key is pressed. If the keyboard remains connected the same message is logged to logs and in few hours I have about 500 MB of logs: /var/log# tail debug Dec 7 21:29:25 localhost kernel: evbug.c: Event. Dev: usb-:00:1d.2-2/input0, Type: 0, Code: 0, Value: 0 Dec 7 21:29:25 localhost kernel: evbug.c: Event. Dev: usb-:00:1d.2-2/input0, Type: 1, Code: 32, Value: 0 Dec 7 21:29:25 localhost kernel: evbug.c: Event. Dev: usb-:00:1d.2-2/input0, Type: 1, Code: 18, Value: 0 Dec 7 21:29:25 localhost kernel: evbug.c: Event. Dev: usb-:00:1d.2-2/input0, Type: 0, Code: 0, Value: 0 Dec 7 21:29:25 localhost kernel: evbug.c: Event. Dev: usb-:00:1d.2-2/input0, Type: 1, Code: 15, Value: 1 Dec 7 21:29:25 localhost kernel: evbug.c: Event. Dev: usb-:00:1d.2-2/input0, Type: 0, Code: 0, Value: 0 Dec 7 21:29:26 localhost kernel: evbug.c: Event. Dev: usb-:00:1d.2-2/input0, Type: 1, Code: 15, Value: 0 Dec 7 21:29:26 localhost kernel: evbug.c: Event. Dev: usb-:00:1d.2-2/input0, Type: 0, Code: 0, Value: 0 Dec 7 21:29:26 localhost kernel: evbug.c: Event. Dev: usb-:00:1d.2-2/input0, Type: 1, Code: 28, Value: 1 Dec 7 21:29:26 localhost kernel: evbug.c: Event. Dev: usb-:00:1d.2-2/input0, Type: 0, Code: 0, Value: 0 /var/log# tail kern.log Dec 7 21:29:52 localhost kernel: evbug.c: Event. Dev: usb-:00:1d.2-2/input0, Type: 0, Code: 0, Value: 0 Dec 7 21:29:52 localhost kernel: drivers/usb/input/hid-core.c: input irq status -75 received Dec 7 21:29:52 localhost last message repeated 9 times Dec 7 21:29:52 localhost kernel: evbug.c: Event. Dev: usb-:00:1d.2-2/input0, Type: 1, Code: 15, Value: 0 Dec 7 21:29:52 localhost kernel: evbug.c: Event. Dev: usb-:00:1d.2-2/input0, Type: 0, Code: 0, Value: 0 Dec 7 21:29:52 localhost kernel: drivers/usb/input/hid-core.c: input irq status -75 received Dec 7 21:29:53 localhost last message repeated 58 times Dec 7 21:29:53 localhost kernel: evbug.c: Event. Dev: usb-:00:1d.2-2/input0, Type: 1, Code: 28, Value: 1 Dec 7 21:29:53 localhost kernel: evbug.c: Event. Dev: usb-:00:1d.2-2/input0, Type: 0, Code: 0, Value: 0 Dec 7 21:29:53 localhost kernel: drivers/usb/input/hid-core.c: input irq status -75 received /var/log# tail syslog Dec 7 21:30:25 localhost kernel: evbug.c: Event. Dev: usb-:00:1d.2-2/input0, Type: 0, Code: 0, Value: 0 Dec 7 21:30:25 localhost kernel: drivers/usb/input/hid-core.c: input irq status -75 received Dec 7 21:30:25 localhost last message repeated 10 times Dec 7 21:30:25 localhost kernel: evbug.c: Event. Dev: usb-:00:1d.2-2/input0, Type: 1, Code: 15, Value: 0 Dec 7 21:30:25 localhost kernel: evbug.c: Event. Dev: usb-:00:1d.2-2/input0, Type: 0, Code: 0, Value: 0 Dec 7 21:30:25 localhost kernel: drivers/usb/input/hid-core.c: input irq status -75 received Dec 7 21:30:25 localhost last message repeated 70 times Dec 7 21:30:25 localhost kernel: evbug.c: Event. Dev: usb-:00:1d.2-2/input0, Type: 1, Code: 28, Value: 1 Dec 7 21:30:25 localhost kernel: evbug.c: Event. Dev: usb-:00:1d.2-2/input0, Type: 0, Code: 0, Value: 0 Dec 7 21:30:25 localhost kernel: drivers/usb/input/hid-core.c: input irq status -75 received /var/log# tail dmesg drivers/usb/input/hid-core.c: input irq status -75 received drivers/usb/input/hid-core.c: input irq status -75 received drivers/usb/input/hid-core.c: input irq status -75 received drivers/usb/input/hid-core.c: input irq status -75 received drivers/usb/input/hid-core.c: input irq status -75 received drivers/usb/input/hid-core.c: input irq status -75 received drivers/usb/input/hid-core.c: input irq status -75 received drivers/usb/input/hid-core.c: input irq status -75 received drivers/usb/input/hid-core.c: input irq status -75 received drivers/usb/i
Bug#401934: marked as done (st.o module does not allow 1MB blocks)
Your message dated Tue, 3 Jun 2008 13:39:20 +0200 with message-id <[EMAIL PROTECTED]> and subject line Re: st.o module does not allow 1MB blocks has caused the Debian Bug report #401934, regarding st.o module does not allow 1MB blocks to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 401934: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=401934 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: linux-image-2.6.18-3-amd64 Version: 2.6.18-7 This same issue also applied to kernels 2.6.16-2-amd64-k8-smp and 2.6.17-1-amd64-k8-smp, I believe as well. When trying to read or write a tape with blocks of 2048*512 bytes using the st module, the application (either dd using bs=1048576 or tar using "--blocking-factor=2048) quits with an error that says that the device is "busy". If you try reading/writing with smaller blocks things work fine. The problem is that I have hundreds of tapes written (using earlier kernels) using 2048x512B blocks Was there a Debian-specific patch that limited the block size in order to conserve memory usage, for example? If so, could that please be removed or else tweaked to allow at least 1MB blocks? Most of the tapes that I have, have been written using recent versions of RHEL. Here is my uname string: Linux uller 2.6.18-3-amd64 #1 SMP Mon Dec 4 17:04:37 CET 2006 x86_64 GNU/Linux I'm running Debian unstable as of 05 Dec 2006 libc = 2.3.6.ds1-8 Thanks a bunch, Scott PS: I submitted this previously with incorrect package/version names. Sorry about that -- Scott M. RansomAddress: NRAO Phone: (434) 296-0320 520 Edgemont Rd. email: [EMAIL PROTECTED] Charlottesville, VA 22903 USA GPG Fingerprint: 06A9 9553 78BE 16DB 407B FFCA 9BFA B6FF FFD3 2989 --- End Message --- --- Begin Message --- Version: 2.6.21-1 fixed in commit 9abe16c670bd3d4ab5519257514f9f291383d104 for stable use http://wiki.debian.org/EtchAndAHalf thanks for report -- maks --- End Message ---
Bug#484239: linux-image-2.6.25-2-686: kadahat in zalahat
On Tue, Jun 03, 2008 at 12:46:32PM +0300, Shai Berger wrote: > On Tuesday 03 June 2008 11:13:20 you wrote: > > On Tue, Jun 03, 2008 at 10:19:05AM +0300, Shai Berger wrote: > > > Subject: linux-image-2.6.25-2-686: sound breaks on second login to main X > > > session (vt7) Package: linux-image-2.6.25-2-686 > > > Version: 2.6.25-4 > > > Severity: normal > > > > > > > > > This report corrects my misdiagnosis of the problem as > > > reported in bug #483664. > > > > > > I use a desktop machine with multiple X sessions in virtual terminals. > > > with kernel 2.6.25, I have this scenario, reproducibly: > > > > > > - After boot, first user logs into X session on vt7 > > > - First user logs out > > > - Again, a user logs in on vt7 (I used same user, but I don't think that > > > matters) - Sound dies > > > > again missing vital info, like dmesg output when that happen. > > There's nothing in dmesg when that happens. I only see messages in dmesg when > I run alsaconf to fix; I will paste them here when I am back at the machine > tonight. I've also looked at syslog and found nothing there. hmm still not buying the kernel error yet. > > we need more info then "Sound dies" > > > > I just don't know where to look. Any suggestions beyond dmesg > and /var/log/syslog? > > > what sound application are you using? > > I'm not sure what you mean by "sound application" -- I use artsd as part of > KDE 3.5.9, and it reports no errors, but plays no sounds (system sounds). > Other applications rely on it, If I'm not mistaken. which applications? anyway it seems we are in userland trouble here. post output of that script has relevant sound output http://hg.alsa-project.org/alsa/raw-file/tip/alsa-info.sh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#399324: linux-image-2.6.17-2-686: OSS layer for ALSA mixer module bugs PCM volume setting
On Thu, 29 May 2008, Fabien COUTANT wrote: > Le Mon, 26 May 2008 20:08:03 +0200, maximilian attems a écrit: > > > > 2.6.24 is a bit old to report upstream to the alsa guys. > > > > Same thing as 2.6.24-7, while running linux-image-2.6.25-2-686 2.6.25-3 from > sid. > > -- > Hope this helps, > Fabien. as this seems an longstanding bug, please report upstream on bugzilla.kernel.org include the output of this alsa script http://hg.alsa-project.org/alsa/raw-file/tip/alsa-info.sh thanks for letting us know the upstream bug number. best regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: reassign 480060 to linux-2.6
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.28 > reassign 480060 linux-2.6 Bug#480060: linux-doc-2.6.24: inconsistency between image/headers virtual package and doc virtual package Bug reassigned from package `linux-doc-2.6.24' to `linux-2.6'. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: reassign 480060 to linux-2.6
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.28 > reassign 480060 linux-2.6 Bug#480060: linux-doc-2.6.24: inconsistency between image/headers virtual package and doc virtual package Bug reassigned from package `linux-2.6' to `linux-2.6'. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: forcibly merging 347284 480060
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.28 > forcemerge 347284 480060 Bug#347284: linux-doc-2.6.14: get the latest linux-doc Bug#480060: linux-doc-2.6.24: inconsistency between image/headers virtual package and doc virtual package Forcibly Merged 347284 480060. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#482940: linux-source-2.6.24: saa7134-empress or saa6752hs problem
On Tue, Jun 3, 2008 at 8:56 AM, maximilian attems <[EMAIL PROTECTED]> wrote: > tags 482940 moreinfo > stop > > On Mon, 26 May 2008, maximilian attems wrote: > >> On Mon, May 26, 2008 at 03:21:44AM +0200, Wiktor Stasiak wrote: >> > Package: linux-source-2.6.24 >> > Version: 2.6.24-7 >> > Severity: normal >> > >> > >> > I am using KNC 1 tv card with MPEG2 encoder to stream some analog video to >> > network. >> > Since upgrade to 2.6.24 it is possible to get audio trough hardware >> > encoder, but new problem was introduced. >> > >> > Driver hangs when accessing some of it options. >> >> check out linux image 2.6.25 in unstable installs just fine in testing. >> >> thanks for feedback based on it. > > please provide the asked feedback > > > thanks > > > -- > maks > I didn't tested yet because I have some technical difficulties (simply I need a display to do a kernel upgrade, which I don't have at the moment). I will provide feedback in two weeks. Wiktor -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#484177: firmware-nonfree: keyspan
On Mon, Jun 02, 2008 at 02:10:08PM -0700, Matt Taggart wrote: > I'm a little unclear on the license of the keyspan firmware. On > http://wiki.debian.org/KernelFirmwareLicensing > it lists a note for all the keyspan stuff of > "4. redistributable as part of a Linux or other Open Source operating > system kernel" > Does that imply that a stand-alone package like firmware-nonfree would be > unacceptable? I would interpret it this way. > B.) have documentation that clearly states the decision (probably on the > above wiki page, in the firmware-nonfree package, and maybe even have the > kernel print something when attempting to load those drivers). This keyspan drivers are currently not included at all in the binary Linux images. Bastian -- You're dead, Jim. -- McCoy, "The Tholian Web", stardate unknown -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#484239: linux-image-2.6.25-2-686: kadahat in zalahat
On Tue, Jun 03, 2008 at 10:19:05AM +0300, Shai Berger wrote: > > Subject: linux-image-2.6.25-2-686: sound breaks on second login to main X > session (vt7) > Package: linux-image-2.6.25-2-686 > Version: 2.6.25-4 > Severity: normal > > > This report corrects my misdiagnosis of the problem as > reported in bug #483664. > > I use a desktop machine with multiple X sessions in virtual terminals. > with kernel 2.6.25, I have this scenario, reproducibly: > > - After boot, first user logs into X session on vt7 > - First user logs out > - Again, a user logs in on vt7 (I used same user, but I don't think that > matters) > - Sound dies again missing vital info, like dmesg output when that happen. we need more info then "Sound dies" what sound application are you using? -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#484241: closing 484241
# Automatically generated email from bts, devscripts version 2.10.28 # dup report close 484241 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#484239: This was a mistake...
I'm already filing a bug report on reportbug for the weirdness that made me submit this in this form. Please ignore this bug; the report with a sane title is in bug #484241. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#483375: marked as done (linux-image-2.6.25-2-amd64: 2.6.25-4 broke cpu frequency scaling)
Your message dated Tue, 3 Jun 2008 10:01:53 +0200 with message-id <[EMAIL PROTECTED]> and subject line Re: Bug#483375: linux-image-2.6.25-2-amd64: 2.6.25-4 broke cpu frequency scaling has caused the Debian Bug report #483375, regarding linux-image-2.6.25-2-amd64: 2.6.25-4 broke cpu frequency scaling to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 483375: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=483375 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: linux-image-2.6.25-2-amd64 Version: 2.6.25-4 Severity: normal Hi, with latest update of linux-image-2.6.25-2-amd4, I lost the folders /sys/devices/system/cpu/cpu*/cpufreq and thus, kpowersave does not show the frequency used and does not allow to chose between ondemand, performance, powersave as it did before. Regards, Didier -- Package-specific info: ** Version: Linux version 2.6.25-2-amd64 (Debian 2.6.25-4) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080420 (prerelease) (Debian 4.1.2-22)) #1 SMP Tue May 27 12:45:24 UTC 2008 ** Command line: BOOT_IMAGE=(hd0,1)/vmlinuz-2.6.25-2-amd64 root=/dev/mapper/Tamino-Root ro quiet vga=792 ** Not tainted ** Kernel log: [12840.499674] usb 7-2: new full speed USB device using uhci_hcd and address 24 [12920.661435] CPU0 attaching NULL sched-domain. [12920.661448] CPU1 attaching NULL sched-domain. [12920.680336] CPU0 attaching sched-domain: [12920.680348] domain 0: span 0003 [12920.680353] groups: 0001 0002 [12920.680364] domain 1: span 0003 [12920.680370]groups: 0003 [12920.680378]domain 2: span 0003 [12920.680385] groups: 0003 [12920.680394] CPU1 attaching sched-domain: [12920.680399] domain 0: span 0003 [12920.680405] groups: 0002 0001 [12920.680415] domain 1: span 0003 [12920.680421]groups: 0003 [12920.680428]domain 2: span 0003 [12920.680434] groups: 0003 [12840.674052] usb 7-2: configuration #1 chosen from 1 choice [12840.677112] usb 7-2: New USB device found, idVendor=0483, idProduct=2016 [12840.677123] usb 7-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [12840.677129] usb 7-2: Product: Biometric Coprocessor [12840.677133] usb 7-2: Manufacturer: STMicroelectronics [12840.912834] usb 7-1.2: new full speed USB device using uhci_hcd and address 25 [12841.031017] usb 7-1.2: configuration #1 chosen from 1 choice [12841.034200] usb 7-1.2: New USB device found, idVendor=0b97, idProduct=7772 [12841.034210] usb 7-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [12841.034216] usb 7-1.2: Product: O2Micro CCID SC Reader [12841.034220] usb 7-1.2: Manufacturer: O2 [12844.683098] CPU0 attaching NULL sched-domain. [12844.683111] CPU1 attaching NULL sched-domain. [12844.703771] CPU0 attaching sched-domain: [12844.703783] domain 0: span 0003 [12844.703788] groups: 0001 0002 [12844.703796] domain 1: span 0003 [12844.703800]groups: 0003 [12844.703807] CPU1 attaching sched-domain: [12844.703811] domain 0: span 0003 [12844.703815] groups: 0002 0001 [12844.703821] domain 1: span 0003 [12844.703825]groups: 0003 [12850.444863] wlan0: no IPv6 routers present [14131.680235] CPU0 attaching NULL sched-domain. [14131.680250] CPU1 attaching NULL sched-domain. [14131.703368] CPU0 attaching sched-domain: [14131.703381] domain 0: span 0003 [14131.703386] groups: 0001 0002 [14131.703396] domain 1: span 0003 [14131.703402]groups: 0003 [14131.703412] CPU1 attaching sched-domain: [14131.703417] domain 0: span 0003 [14131.703423] groups: 0002 0001 [14131.703433] domain 1: span 0003 [14131.703439]groups: 0003 [14280.205220] hub 4-0:1.0: unable to enumerate USB device on port 2 [14280.445219] usb 5-2: new low speed USB device using uhci_hcd and address 3 [14195.520990] usb 5-2: configuration #1 chosen from 1 choice [14195.561666] input: Logitech USB Receiver as /class/input/input12 [14195.607816] input,hidraw0: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-:00:1d.0-2 [14195.640787] input: Logitech USB Receiver as /class/input/input13 [14195.710682] input,hiddev96,hidraw1: USB HID v1.11 Device [Logitech USB Receiver] on usb-:00:1d.0-2 [14195.710847] usb 5-2: New USB device found, idVendor=046d, idProduct=c521 [14195.710853] usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [14195.710858] usb 5-2: Product: USB Receiver [14195.710862] usb 5-2: Manufacturer: Logitech [14531.170340] CPU0 attaching NULL sched-domain. [14531.170352] CPU1 attaching NULL sched-domai
Processed: retitle 484239 to sound breaks on second login to main X session vt7
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.28 > retitle 484239 sound breaks on second login to main X session vt7 Bug#484239: linux-image-2.6.25-2-686: kadahat in zalahat Changed Bug title to `sound breaks on second login to main X session vt7' from `linux-image-2.6.25-2-686: kadahat in zalahat'. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: closing 484241
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.28 > # dup report > close 484241 Bug#484241: linux-image-2.6.25-2-686: sound breaks on second login to main X session (vt7) 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Shai Berger <[EMAIL PROTECTED]> > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#480347: Boot errors
> Version: April 21 version. sorry but that version string is wrong. please give feedback on 2.6.25 from unstable installs just in testing. otherwise i'd have to close this report missing vital info. thanks -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [PATCH] Trunk build fix
On Mon, 2008-06-02 at 10:21 +0200, maximilian attems wrote: > hello Ian, > > On Tue, 27 May 2008, dann frazier wrote: > > > On Tue, May 27, 2008 at 12:50:51AM +0200, maximilian attems wrote: > > > if nobody disagrees in the next 48 hours from kernel team it be great > > > to have Ian added to the alioth kernel team. his alioth account is > > > ijc-guest. > > > [snip] > thanks dannf for add. > Ian welcome to the team, happy hacking :) Thanks guys. Ian. -- Ian Campbell Doubt isn't the opposite of faith; it is an element of faith. -- Paul Tillich, German theologian. signature.asc Description: This is a digitally signed message part
Bug#484241: linux-image-2.6.25-2-686: sound breaks on second login to main X session (vt7)
Package: linux-image-2.6.25-2-686 Version: 2.6.25-4 Severity: normal Subject: linux-image-2.6.25-2-686: sound breaks on second login to main X session (vt7) Package: linux-image-2.6.25-2-686 Version: 2.6.25-4 Severity: normal This report corrects my misdiagnosis of the problem as reported in bug #483664. I use a desktop machine with multiple X sessions in virtual terminals. with kernel 2.6.25, I have this scenario, reproducibly: - After boot, first user logs into X session on vt7 - First user logs out - Again, a user logs in on vt7 (I used same user, but I don't think that matters) - Sound dies This happens whether or not there are other users in other vt's, and sound dies for all sessions (including sessions which opened before on other vt's and had sound). running alsaconf at this point restores sound, but only until the next login on vt7. 2.6.24 doesn't have the problem at all, and all I can see in dmesg or /var/log/syslog is the device being restarted by alsaconf (that is, no errors). I realize that my use of an nvidia blob makes my kernel "unsupported"; I will try later, when I have more time, to see if I can reproduce the problem without it. What seemed before (in #483664) like an upgrade problem, appears now to be an actual problem with the new kernel, so I will make more of an effort to pinpoint it; I wanted to report it anyway in case the better description rings a bell. I have gone back to 2.6.24 to let the other users of this computer enjoy sound -- I'm attaching the 2.6.25 kernel info (from my earlier report) after the 2.6.24 info. -- Package-specific info: -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.25-2-686 depends on: ii debconf [debconf-2.0] 1.5.22 Debian configuration management sy ii initramfs-tools [linux-initra 0.92a tools for generating an initramfs ii module-init-tools 3.4-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.25-2-686 recommends: ii libc6-i6862.7-11 GNU C Library: Shared libraries [i -- debconf information: linux-image-2.6.25-2-686/preinst/abort-install-2.6.25-2-686: linux-image-2.6.25-2-686/postinst/bootloader-test-error-2.6.25-2-686: linux-image-2.6.25-2-686/prerm/removing-running-kernel-2.6.25-2-686: true linux-image-2.6.25-2-686/postinst/old-initrd-link-2.6.25-2-686: true linux-image-2.6.25-2-686/preinst/initrd-2.6.25-2-686: linux-image-2.6.25-2-686/postinst/kimage-is-a-directory: linux-image-2.6.25-2-686/postinst/depmod-error-2.6.25-2-686: false shared/kernel-image/really-run-bootloader: true linux-image-2.6.25-2-686/preinst/overwriting-modules-2.6.25-2-686: true linux-image-2.6.25-2-686/prerm/would-invalidate-boot-loader-2.6.25-2-686: true linux-image-2.6.25-2-686/preinst/elilo-initrd-2.6.25-2-686: true linux-image-2.6.25-2-686/postinst/depmod-error-initrd-2.6.25-2-686: false linux-image-2.6.25-2-686/preinst/bootloader-initrd-2.6.25-2-686: true linux-image-2.6.25-2-686/preinst/lilo-has-ramdisk: linux-image-2.6.25-2-686/postinst/bootloader-error-2.6.25-2-686: linux-image-2.6.25-2-686/preinst/lilo-initrd-2.6.25-2-686: true linux-image-2.6.25-2-686/postinst/old-system-map-link-2.6.25-2-686: true linux-image-2.6.25-2-686/postinst/create-kimage-link-2.6.25-2-686: true linux-image-2.6.25-2-686/postinst/old-dir-initrd-link-2.6.25-2-686: true linux-image-2.6.25-2-686/preinst/abort-overwrite-2.6.25-2-686: linux-image-2.6.25-2-686/preinst/failed-to-move-modules-2.6.25-2-686: -- Package-specific info: ** Version: Linux version 2.6.25-2-686 (Debian 2.6.25-4) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080420 (prerelease) (Debian 4.1.2-22)) #1 SMP Tue May 27 15:38:35 UTC 2 008 ** Command line: root=/dev/sda1 ro ** Tainted: P (1) ** Kernel log: [1.352098] firewire_ohci: Added fw-ohci device :07:03.0, OHCI version 1.10 [1.496103] ahci :00:1f.2: version 3.0 [1.496103] ACPI: PCI Interrupt :00:1f.2[A] -> GSI 19 (level, low) -> IRQ 19 [1.552178] firewire_core: created device fw0: GUID 0090270001c9c70a, S400 [1.512135] ahci :00:1f.2: AHCI 0001.0100 32 slots 6 ports 3 Gbps 0x3f impl RAID mode [1.512196] ahci :00:1f.2: flags: 64bit ncq sntf led clo pio slum part [1.512247] PCI: Setting latency timer of device :00:1f.2 to 64 [1.512502] scsi2 : ahci [1.512626] scsi3 : ahci [1.516156] scsi4 : ahci [1.516272] scsi5 : ahci [1.516374] scsi6 : ahci [1.516483] scsi7 : ahci [1.516600] ata3: SATA max UDMA/133 abar [EMAIL PROTECTED] port 0x93225100 irq 217 [1.516656] ata4: SATA max UDMA/133 abar [EMAIL PROTECTED] port 0x93225180 irq 217 [1.516712] ata5: SATA max UDMA/133 abar [EMAIL PROTECTED]
Bug#481125: [linux-image-2.6.24-1-amd64] Booting sometime freeze 8 to 9 minutes
On Tue, 13 May 2008, Robert Chéramy wrote: > Package: linux-image-2.6.24-1-amd64 > Version: 2.6.24-6 > Severity: normal > > --- Please enter the report below this line. --- > > Hi, > > I've got a Dell inspiron 530n (the ones sold with ubuntu preinstalled). > Some times, not systematicly (perhaps every third power on and at most > reboots), the boot process is blocked 8 to 9 minutes (see attached dmesg > for the point of freeze). The keyboard is freezed (Caps or Num LED won't > change). > > After this random time, the boot process goes on and the system boots up > normaly. please try out 2.6.25 from unstable and give feedback on it? installs just fine in testing. thanks -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#484239: linux-image-2.6.25-2-686: kadahat in zalahat
Package: linux-image-2.6.25-2-686 Version: 2.6.25-4 Severity: normal Subject: linux-image-2.6.25-2-686: sound breaks on second login to main X session (vt7) Package: linux-image-2.6.25-2-686 Version: 2.6.25-4 Severity: normal This report corrects my misdiagnosis of the problem as reported in bug #483664. I use a desktop machine with multiple X sessions in virtual terminals. with kernel 2.6.25, I have this scenario, reproducibly: - After boot, first user logs into X session on vt7 - First user logs out - Again, a user logs in on vt7 (I used same user, but I don't think that matters) - Sound dies This happens whether or not there are other users in other vt's, and sound dies for all sessions (including sessions which opened before on other vt's and had sound). running alsaconf at this point restores sound, but only until the next login on vt7. 2.6.24 doesn't have the problem at all, and all I can see in dmesg or /var/log/syslog is the device being restarted by alsaconf (that is, no errors). I realize that my use of an nvidia blob makes my kernel "unsupported"; I will try later, when I have more time, to see if I can reproduce the problem without it. What seemed before (in #483664) like an upgrade problem, appears now to be an actual problem with the new kernel, so I will make more of an effort to pinpoint it; I wanted to report it anyway in case the better description rings a bell. I have gone back to 2.6.24 to let the other users of this computer enjoy sound -- I'm attaching the 2.6.25 kernel info (from my earlier report) after the 2.6.24 info. -- Package-specific info: -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.25-2-686 depends on: ii debconf [debconf-2.0] 1.5.22 Debian configuration management sy ii initramfs-tools [linux-initra 0.92a tools for generating an initramfs ii module-init-tools 3.4-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.25-2-686 recommends: ii libc6-i6862.7-11 GNU C Library: Shared libraries [i -- debconf information: linux-image-2.6.25-2-686/preinst/abort-install-2.6.25-2-686: linux-image-2.6.25-2-686/postinst/bootloader-test-error-2.6.25-2-686: linux-image-2.6.25-2-686/prerm/removing-running-kernel-2.6.25-2-686: true linux-image-2.6.25-2-686/postinst/old-initrd-link-2.6.25-2-686: true linux-image-2.6.25-2-686/preinst/initrd-2.6.25-2-686: linux-image-2.6.25-2-686/postinst/kimage-is-a-directory: linux-image-2.6.25-2-686/postinst/depmod-error-2.6.25-2-686: false shared/kernel-image/really-run-bootloader: true linux-image-2.6.25-2-686/preinst/overwriting-modules-2.6.25-2-686: true linux-image-2.6.25-2-686/prerm/would-invalidate-boot-loader-2.6.25-2-686: true linux-image-2.6.25-2-686/preinst/elilo-initrd-2.6.25-2-686: true linux-image-2.6.25-2-686/postinst/depmod-error-initrd-2.6.25-2-686: false linux-image-2.6.25-2-686/preinst/bootloader-initrd-2.6.25-2-686: true linux-image-2.6.25-2-686/preinst/lilo-has-ramdisk: linux-image-2.6.25-2-686/postinst/bootloader-error-2.6.25-2-686: linux-image-2.6.25-2-686/preinst/lilo-initrd-2.6.25-2-686: true linux-image-2.6.25-2-686/postinst/old-system-map-link-2.6.25-2-686: true linux-image-2.6.25-2-686/postinst/create-kimage-link-2.6.25-2-686: true linux-image-2.6.25-2-686/postinst/old-dir-initrd-link-2.6.25-2-686: true linux-image-2.6.25-2-686/preinst/abort-overwrite-2.6.25-2-686: linux-image-2.6.25-2-686/preinst/failed-to-move-modules-2.6.25-2-686: -- Package-specific info: ** Version: Linux version 2.6.25-2-686 (Debian 2.6.25-4) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080420 (prerelease) (Debian 4.1.2-22)) #1 SMP Tue May 27 15:38:35 UTC 2 008 ** Command line: root=/dev/sda1 ro ** Tainted: P (1) ** Kernel log: [1.352098] firewire_ohci: Added fw-ohci device :07:03.0, OHCI version 1.10 [1.496103] ahci :00:1f.2: version 3.0 [1.496103] ACPI: PCI Interrupt :00:1f.2[A] -> GSI 19 (level, low) -> IRQ 19 [1.552178] firewire_core: created device fw0: GUID 0090270001c9c70a, S400 [1.512135] ahci :00:1f.2: AHCI 0001.0100 32 slots 6 ports 3 Gbps 0x3f impl RAID mode [1.512196] ahci :00:1f.2: flags: 64bit ncq sntf led clo pio slum part [1.512247] PCI: Setting latency timer of device :00:1f.2 to 64 [1.512502] scsi2 : ahci [1.512626] scsi3 : ahci [1.516156] scsi4 : ahci [1.516272] scsi5 : ahci [1.516374] scsi6 : ahci [1.516483] scsi7 : ahci [1.516600] ata3: SATA max UDMA/133 abar [EMAIL PROTECTED] port 0x93225100 irq 217 [1.516656] ata4: SATA max UDMA/133 abar [EMAIL PROTECTED] port 0x93225180 irq 217 [1.516712] ata5: SATA max UDMA/133 abar [EMAIL PROTECTED]
Processed: severity of 480060 is wishlist
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.28 > severity 480060 wishlist Bug#480060: linux-doc-2.6.24: inconsistency between image/headers virtual package and doc virtual package Severity set to `wishlist' from `normal' > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#478658: marked as done (linux-image-2.6.24-1-amd64: Wi-fi adapter deauthenticated every )
Your message dated Tue, 3 Jun 2008 09:22:22 +0200 with message-id <[EMAIL PROTECTED]> and subject line Re: linux-image-2.6.24-1-amd64: Wi-fi adapter deauthenticated every has caused the Debian Bug report #478658, regarding linux-image-2.6.24-1-amd64: Wi-fi adapter deauthenticated every to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 478658: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=478658 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: linux-image-2.6.24-1-amd64 Version: 2.6.24-5 Severity: normal Tags: l10n I noticed that many deauthenting messages apper in dmesg : eth1: Initial auth_alg=0 eth1: authenticate with AP 00:12:43:bf:2e:90 eth1: RX authentication from 00:12:43:bf:2e:90 (alg=0 transaction=2 status=0) eth1: authenticated eth1: associate with AP 00:12:43:bf:2e:90 eth1: RX AssocResp from 00:12:43:bf:2e:90 (capab=0x421 status=0 aid=74) eth1: associated eth1: CTS protection enabled (BSSID=00:12:43:bf:2e:90) eth1: switched to short barker preamble (BSSID=00:12:43:bf:2e:90) eth1: WMM queue=2 aci=0 acm=0 aifs=3 cWmin=15 cWmax=1023 burst=0 eth1: WMM queue=3 aci=1 acm=0 aifs=7 cWmin=15 cWmax=1023 burst=0 eth1: WMM queue=1 aci=2 acm=0 aifs=2 cWmin=7 cWmax=15 burst=30 eth1: WMM queue=0 aci=3 acm=0 aifs=2 cWmin=3 cWmax=7 burst=15 eth1: association frame received from 00:12:43:bf:2e:90, but not in associate state - ignored eth1: RX deauthentication from 00:12:43:bf:2e:90 (reason=2) eth1: deauthenticated eth1: authenticate with AP 00:12:43:bf:2e:90 eth1: RX authentication from 00:12:43:bf:2e:90 (alg=0 transaction=2 status=0) eth1: authenticated eth1: associate with AP 00:12:43:bf:2e:90 eth1: RX ReassocResp from 00:12:43:bf:2e:90 (capab=0x421 status=0 aid=75) eth1: associated eth1: CTS protection enabled (BSSID=00:12:43:bf:2e:90) eth1: switched to short barker preamble (BSSID=00:12:43:bf:2e:90) eth1: RX deauthentication from 00:12:43:bf:2e:90 (reason=2) eth1: deauthenticated eth1: authenticate with AP 00:12:43:bf:2e:90 eth1: RX authentication from 00:12:43:bf:2e:90 (alg=0 transaction=2 status=0) eth1: authenticated eth1: associate with AP 00:12:43:bf:2e:90 eth1: RX ReassocResp from 00:12:43:bf:2e:90 (capab=0x421 status=0 aid=76) eth1: associated eth1: CTS protection enabled (BSSID=00:12:43:bf:2e:90) eth1: switched to short barker preamble (BSSID=00:12:43:bf:2e:90) eth1: RX deauthentication from 00:12:43:bf:2e:90 (reason=2) eth1: deauthenticated eth1: authenticate with AP 00:12:43:bf:2e:90 eth1: RX authentication from 00:12:43:bf:2e:90 (alg=0 transaction=2 status=0) eth1: authenticated eth1: associate with AP 00:12:43:bf:2e:90 eth1: RX ReassocResp from 00:12:43:bf:2e:90 (capab=0x421 status=0 aid=77) eth1: associated eth1: CTS protection enabled (BSSID=00:12:43:bf:2e:90) eth1: switched to short barker preamble (BSSID=00:12:43:bf:2e:90) eth1: RX deauthentication from 00:12:43:bf:2e:90 (reason=2) eth1: deauthenticated eth1: authenticate with AP 00:12:43:bf:2e:90 eth1: RX authentication from 00:12:43:bf:2e:90 (alg=0 transaction=2 status=0) eth1: authenticated eth1: associate with AP 00:12:43:bf:2e:90 eth1: RX ReassocResp from 00:12:43:bf:2e:90 (capab=0x421 status=0 aid=78) eth1: associated eth1: CTS protection enabled (BSSID=00:12:43:bf:2e:90) eth1: switched to short barker preamble (BSSID=00:12:43:bf:2e:90) eth1: RX deauthentication from 00:12:43:bf:2e:90 (reason=2) eth1: deauthenticated eth1: authenticate with AP 00:12:43:bf:2e:90 eth1: RX authentication from 00:12:43:bf:2e:90 (alg=0 transaction=2 status=0) eth1: authenticated eth1: associate with AP 00:12:43:bf:2e:90 eth1: RX ReassocResp from 00:12:43:bf:2e:90 (capab=0x421 status=0 aid=79) eth1: associated eth1: CTS protection enabled (BSSID=00:12:43:bf:2e:90) eth1: switched to short barker preamble (BSSID=00:12:43:bf:2e:90) while in 2.6.23 there is now such begaiveor -- Package-specific info: ** Version: Linux version 2.6.24-1-amd64 (Debian 2.6.24-5) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080308 (prerelease) (Debian 4.1.2-21)) #1 SMP Thu Mar 27 16:52:38 UTC 2008 ** Command line: root=/dev/sda7 ro quiet ** Not tainted ** Kernel log: Synaptics Touchpad, model: 1, fw: 6.2, id: 0x12a0b1, caps: 0xa04713/0x204000 input: SynPS/2 Synaptics TouchPad as /class/input/input9 Adding 1951856k swap on /dev/sda6. Priority:-1 extents:1 across:1951856k EXT3 FS on sda7, internal journal loop: module loaded kjournald starting. Commit interval 5 seconds EXT3 FS on sda4, internal journal EXT3-fs: mounted filesystem with ordered data mode. eth0: link down pnp: the driver 'parport_pc' has been registered lp: driver loaded but no
Bug#478428: marked as done (linux-image-2.6.24-etchnhalf.1: Vmware-Module-Build exits with Error)
Your message dated Tue, 3 Jun 2008 09:23:09 +0200 with message-id <[EMAIL PROTECTED]> and subject line Re: linux-image-2.6.24-etchnhalf.1: Vmware-Module-Build exits with Error has caused the Debian Bug report #478428, regarding linux-image-2.6.24-etchnhalf.1: Vmware-Module-Build exits with Error to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 478428: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=478428 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: linux-image-2.6.24-etchnhalf.1 Version: 2.6.24-6~etchnhalf.1 Severity: normal See Log. Vmware-Version is Vmware-Server 1.0.4. Trying to find a suitable vmmon module for your running kernel. None of the pre-built vmmon modules for VMware Server is suitable for your running kernel. Do you want this program to try to build the vmmon module for your system (you need to have a C compiler installed on your system)? [yes] Using compiler "/usr/bin/gcc". Use environment variable CC to override. What is the location of the directory of C header files that match your running kernel? [/lib/modules/2.6.24-etchnhalf.1-686/build/include] Extracting the sources of the vmmon module. Building the vmmon module. Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-config0/vmmon-only' make -C /lib/modules/2.6.24-etchnhalf.1-686/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules make[1]: Entering directory `/usr/src/linux-headers-2.6.24-etchnhalf.1-686' CC [M] /tmp/vmware-config0/vmmon-only/linux/driver.o In file included from /tmp/vmware-config0/vmmon-only/./include/vmware.h:25, from /tmp/vmware-config0/vmmon-only/linux/driver.c:48: /tmp/vmware-config0/vmmon-only/./include/vm_basic_types.h:161: error: conflicting types for 'uintptr_t' include/linux/types.h:40: error: previous declaration of 'uintptr_t' was here In file included from /tmp/vmware-config0/vmmon-only/linux/driver.h:20, from /tmp/vmware-config0/vmmon-only/linux/driver.c:49: /tmp/vmware-config0/vmmon-only/./include/compat_wait.h:37:5: warning: "VMW_HAVE_EPOLL" is not defined /tmp/vmware-config0/vmmon-only/./include/compat_wait.h:43:5: warning: "VMW_HAVE_EPOLL" is not defined In file included from /tmp/vmware-config0/vmmon-only/linux/driver.h:20, from /tmp/vmware-config0/vmmon-only/linux/driver.c:49: /tmp/vmware-config0/vmmon-only/./include/compat_wait.h:60: error: conflicting types for 'poll_initwait' include/linux/poll.h:65: error: previous declaration of 'poll_initwait' was here /tmp/vmware-config0/vmmon-only/linux/driver.c:147: warning: initialization from incompatible pointer type /tmp/vmware-config0/vmmon-only/linux/driver.c:151: warning: initialization from incompatible pointer type /tmp/vmware-config0/vmmon-only/linux/driver.c: In function 'LinuxDriver_Ioctl': /tmp/vmware-config0/vmmon-only/linux/driver.c:1659: error: 'struct mm_struct' has no member named 'dumpable' make[2]: *** [/tmp/vmware-config0/vmmon-only/linux/driver.o] Error 1 make[1]: *** [_module_/tmp/vmware-config0/vmmon-only] Error 2 make[1]: Leaving directory `/usr/src/linux-headers-2.6.24-etchnhalf.1-686' make: *** [vmmon.ko] Error 2 make: Leaving directory `/tmp/vmware-config0/vmmon-only' Unable to build the vmmon module. For more information on how to troubleshoot module-related problems, please visit our Web site at "http://www.vmware.com/download/modules/modules.html"; and "http://www.vmware.com/support/reference/linux/prebuilt_modules_linux.html";. -- System Information: Debian Release: 4.0 APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.24-etchnhalf.1-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) --- End Message --- --- Begin Message --- you are missing its build dependency aka kbuild or headers. closing -- maks --- End Message ---
Bug#482940: linux-source-2.6.24: saa7134-empress or saa6752hs problem
tags 482940 moreinfo stop On Mon, 26 May 2008, maximilian attems wrote: > On Mon, May 26, 2008 at 03:21:44AM +0200, Wiktor Stasiak wrote: > > Package: linux-source-2.6.24 > > Version: 2.6.24-7 > > Severity: normal > > > > > > I am using KNC 1 tv card with MPEG2 encoder to stream some analog video to > > network. > > Since upgrade to 2.6.24 it is possible to get audio trough hardware > > encoder, but new problem was introduced. > > > > Driver hangs when accessing some of it options. > > check out linux image 2.6.25 in unstable installs just fine in testing. > > thanks for feedback based on it. please provide the asked feedback thanks -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#481875: marked as done (linux-image-2.6.24-1-amd64 page allocation failure when under load)
Your message dated Tue, 3 Jun 2008 09:12:24 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: linux-image-2.6.24-1-amd64 page allocation failure when
under load
has caused the Debian Bug report #481875,
regarding linux-image-2.6.24-1-amd64 page allocation failure when under load
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
481875: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=481875
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: linux-image-2.6.24-1-amd64
Version: 2.6.24-5
Severity: normal
I seem to be getting a lot of swapper page allocation faults especially
when I am loading the network, 1G with 9k mtu. I am using forcedeth with
max_int_work set to 15
I have attached a sample from the syslog, not sure what else is need. I
started seeing this from 2.6.23 and up. Although it has become more
previlant now
Alex
-- Package-specific info:
** Version:
Linux version 2.6.24-1-amd64 (Debian 2.6.24-5) ([EMAIL PROTECTED]) (gcc version
4.1.3 20080308 (prerelease) (Debian 4.1.2-21)) #1 SMP Thu Mar 27 16:52:38 UTC
2008
** Command line:
root=/dev/md1 ro console=tty0 selinux=1
** Tainted: PF (3)
** Kernel log:
EXT3-fs: mounted filesystem with ordered data mode.
SELinux: initialized (dev dm-21, type ext3), uses xattr
Filesystem "dm-24": Disabling barriers, not supported by the underlying device
XFS mounting filesystem dm-24
Ending clean XFS mount for filesystem: dm-24
SELinux: initialized (dev dm-24, type xfs), uses xattr
Filesystem "dm-5": Disabling barriers, not supported by the underlying device
XFS mounting filesystem dm-5
Ending clean XFS mount for filesystem: dm-5
SELinux: initialized (dev dm-5, type xfs), uses xattr
kjournald starting. Commit interval 5 seconds
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS on dm-15, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
SELinux: initialized (dev dm-15, type ext3), uses xattr
kjournald starting. Commit interval 5 seconds
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS on dm-8, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
SELinux: initialized (dev dm-8, type ext3), uses xattr
Adding 1959800k swap on /dev/md2. Priority:-1 extents:1 across:1959800k
ip_tables: (C) 2000-2006 Netfilter Core Team
nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
audit(1211063036.304:29): avc: denied { read write } for pid=4158
comm="modprobe" path="socket:[12082]" dev=sockfs ino=12082
scontext=system_u:system_r:insmod_t:s0 tcontext=system_u:system_r:iptables_t:s0
tclass=rawip_socket
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
ip6_tables: (C) 2000-2006 Netfilter Core Team
audit(1211063037.611:30): avc: denied { append } for pid=2556 comm="ifup"
name="ifstate" dev=md1 ino=586883
scontext=system_u:system_r:udev_t:s0-s0:c0.c1023
tcontext=system_u:object_r:etc_runtime_t:s0 tclass=file
audit(1211063038.460:31): avc: denied { search } for pid=4366
comm="rpc.statd" name="sbin" dev=md1 ino=1026145
scontext=system_u:system_r:rpcd_t:s0 tcontext=system_u:object_r:bin_t:s0
tclass=dir
audit(1211063038.460:32): avc: denied { execute } for pid=4366
comm="rpc.statd" name="sm-notify" dev=md1 ino=1026569
scontext=system_u:system_r:rpcd_t:s0 tcontext=system_u:object_r:bin_t:s0
tclass=file
audit(1211063038.460:33): avc: denied { read } for pid=4366 comm="rpc.statd"
name="sm-notify" dev=md1 ino=1026569 scontext=system_u:system_r:rpcd_t:s0
tcontext=system_u:object_r:bin_t:s0 tclass=file
audit(1211063038.460:34): avc: denied { execute_no_trans } for pid=4366
comm="rpc.statd" path="/sbin/sm-notify" dev=md1 ino=1026569
scontext=system_u:system_r:rpcd_t:s0 tcontext=system_u:object_r:bin_t:s0
tclass=file
audit(1211063038.912:35): avc: denied { search } for pid=4366
comm="sm-notify" scontext=system_u:system_r:rpcd_t:s0
tcontext=system_u:object_r:sysctl_fs_t:s0 tclass=dir
audit(1211063041.015:36): avc: denied { read } for pid=4676 comm="auditd"
name="audit" dev=dm-1 ino=98305 scontext=system_u:system_r:auditd_t:s0
tcontext=root:object_r:var_log_t:s0 tclass=dir
audit(1211063041.019:37): avc: denied { read append } for pid=4676
comm="auditd" name="audit.log" dev=dm-1 ino=98311
scontext=system_u:system_r:auditd_t:s0 tcontext=system_u:object_r:var_log_t:s0
tclass=file
audit(1211063041.019:38): avc: denied { getattr } for pid=4676 comm="auditd"
path="/var/log/audit/audit.log" dev=dm-1 ino=98311
scontext=system_u:system_r:auditd_t:s0 tcontext=system_u:object_r:var_log_t:s0
tc
Bug#483375: linux-image-2.6.25-2-amd64: 2.6.25-4 broke cpu frequency scaling
tags 483375 moreinfo unreproducible stop On Wed, 28 May 2008, Didier Raboud wrote: > Package: linux-image-2.6.25-2-amd64 > Version: 2.6.25-4 > Severity: normal > > Hi, > > with latest update of linux-image-2.6.25-2-amd4, I lost the folders > /sys/devices/system/cpu/cpu*/cpufreq and thus, kpowersave does not show > the frequency used and does not allow to chose between ondemand, > performance, powersave as it did before. > > Regards, > > Didier can't reproduce your statement. have for example cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq 80 -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#481554: marked as done (Cannot find vmlinux)
Your message dated Tue, 3 Jun 2008 09:08:27 +0200 with message-id <[EMAIL PROTECTED]> and subject line re: Cannot find vmlinux has caused the Debian Bug report #481554, regarding Cannot find vmlinux to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 481554: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=481554 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: linux-image-2.6.25-1-amd64 Version: 2.6.25-1 I need a vmlinux (not vmlinuz) in order to use oprofile, but this file doesn't seem to be included in any of the binary packages. Juliusz --- End Message --- --- Begin Message --- right we don't provide yet "debug" images, as there enough other open bug reports about it closing. we might consider after lenny. best regards -- maks --- End Message ---
Bug#483985: marked as done (linux-image-2.6.25-2-686: CONFIG_PATA_* disabled)
Your message dated Tue, 3 Jun 2008 08:50:26 +0200 with message-id <[EMAIL PROTECTED]> and subject line Re: Bug#483985: linux-image-2.6.25-2-686: CONFIG_PATA_* disabled has caused the Debian Bug report #483985, regarding linux-image-2.6.25-2-686: CONFIG_PATA_* disabled to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 483985: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=483985 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: linux-image-2.6.25-2-686 Version: 2.6.25-4 Severity: normal CONFIG_PATA_* options are unset in config. This makes all IDE drives to get hdx names instead of sdx and my system does not boot. Is there serious reason to unset this options? They were set in 2.6.24 and earlier... -- Package-specific info: -- System Information: Debian Release: lenny/sid APT prefers experimental APT policy: (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.25-2-k7-toi3.0-rc7 (SMP w/1 CPU core) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.25-2-686 depends on: ii debconf [debconf-2.0] 1.5.22 Debian configuration management sy ii initramfs-tools [linux-initra 0.92b tools for generating an initramfs ii module-init-tools 3.4-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.25-2-686 recommends: ii libc6-i6862.7-11 GNU C Library: Shared libraries [i -- debconf information: linux-image-2.6.25-2-686/preinst/abort-install-2.6.25-2-686: linux-image-2.6.25-2-686/postinst/bootloader-test-error-2.6.25-2-686: linux-image-2.6.25-2-686/prerm/removing-running-kernel-2.6.25-2-686: true linux-image-2.6.25-2-686/postinst/old-initrd-link-2.6.25-2-686: true linux-image-2.6.25-2-686/preinst/initrd-2.6.25-2-686: linux-image-2.6.25-2-686/postinst/kimage-is-a-directory: linux-image-2.6.25-2-686/postinst/depmod-error-2.6.25-2-686: false shared/kernel-image/really-run-bootloader: true linux-image-2.6.25-2-686/preinst/overwriting-modules-2.6.25-2-686: true linux-image-2.6.25-2-686/prerm/would-invalidate-boot-loader-2.6.25-2-686: true linux-image-2.6.25-2-686/preinst/elilo-initrd-2.6.25-2-686: true linux-image-2.6.25-2-686/postinst/depmod-error-initrd-2.6.25-2-686: false linux-image-2.6.25-2-686/preinst/bootloader-initrd-2.6.25-2-686: true linux-image-2.6.25-2-686/preinst/lilo-has-ramdisk: linux-image-2.6.25-2-686/postinst/bootloader-error-2.6.25-2-686: linux-image-2.6.25-2-686/preinst/lilo-initrd-2.6.25-2-686: true linux-image-2.6.25-2-686/postinst/old-system-map-link-2.6.25-2-686: true linux-image-2.6.25-2-686/postinst/create-kimage-link-2.6.25-2-686: true linux-image-2.6.25-2-686/postinst/old-dir-initrd-link-2.6.25-2-686: true linux-image-2.6.25-2-686/preinst/abort-overwrite-2.6.25-2-686: linux-image-2.6.25-2-686/preinst/failed-to-move-modules-2.6.25-2-686: --- End Message --- --- Begin Message --- On Sun, 01 Jun 2008, Roman S Dubtsov wrote: > > CONFIG_PATA_* options are unset in config. This makes all IDE drives to > get hdx names instead of sdx and my system does not boot. Is there serious > reason to unset this options? They were set in 2.6.24 and earlier... > the kernel never guarantees stable device names. use UUID if you want to use stable device names. fix is easy in grub.lst and fstab. closing as not a kernel trouble and no we have not yet switched to PATA so aboves info is false. best regards -- maks --- End Message ---
Bug#482651: marked as done (linux-image-2.6.24-1-amd64: Update from 2.6.24-6 to 2.6.24-7 failed to execute "lilo" causing boot loop)
Your message dated Tue, 3 Jun 2008 09:00:18 +0200 with message-id <[EMAIL PROTECTED]> and subject line Re: linux-image-2.6.24-1-amd64: Update from 2.6.24-6 to 2.6.24-7 failed to execute "lilo" causing boot loop has caused the Debian Bug report #482651, regarding linux-image-2.6.24-1-amd64: Update from 2.6.24-6 to 2.6.24-7 failed to execute "lilo" causing boot loop to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 482651: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=482651 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: linux-image-2.6.24-1-amd64 Version: 2.6.24-7 Severity: normal Updating the system from 2.6.24-6 to 2.6.24-7 rendered the system unuseable. After the reboot lilo started but was not able to load the kernel, the system rebooted, entering an infinite boot loop. The update had been done with synaptic. Fix: Booting from the install CD into the rescue mode, mounting the root partition and the boot partition (root and boot live in different partitions here) and issuing the command "lilo" allowed the system to boot normal again. Afterwards I remembered that I had seen no "lilo" command in synaptics terminal window. Previous kernel updates within the 2.6.24 kernel series had not shown this defect. -- Package-specific info: ** Version: Linux version 2.6.24-1-amd64 (Debian 2.6.24-7) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080114 (prerelease) (Debian 4.1.2-19)) #1 SMP Sat May 10 09:28:10 UTC 2008 ** Command line: auto BOOT_IMAGE=Linux ro root=803 ** Tainted: P (1) ** Kernel log: skge 1.13 addr 0xfdef8000 irq 19 chip Yukon-Lite rev 9 skge eth0: addr 00:30:1b:42:98:ad ata_piix :00:1f.2: version 2.12 ata_piix :00:1f.2: MAP [ P0 P2 P1 P3 ] ACPI: PCI Interrupt :00:1f.2[B] -> GSI 19 (level, low) -> IRQ 19 PCI: Setting latency timer of device :00:1f.2 to 64 scsi0 : ata_piix scsi1 : ata_piix ata1: SATA max UDMA/133 cmd 0xfa00 ctl 0xf900 bmdma 0xf600 irq 19 ata2: SATA max UDMA/133 cmd 0xf800 ctl 0xf700 bmdma 0xf608 irq 19 Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx pnp: the driver 'ide' has been registered ata1.00: ATA-7: ST3400833NS, 3.AEH, max UDMA/133 ata1.00: 781422768 sectors, multi 1: LBA48 NCQ (depth 0/32) ata1.00: configured for UDMA/133 scsi 0:0:0:0: Direct-Access ATA ST3400833NS 3.AE PQ: 0 ANSI: 5 ICH7: IDE controller (0x8086:0x27df rev 0x01) at PCI slot :00:1f.1 ACPI: PCI Interrupt :00:1f.1[A] -> GSI 18 (level, low) -> IRQ 18 ICH7: not 100% native mode: will probe irqs later ide0: BM-DMA at 0xfb00-0xfb07, BIOS settings: hda:DMA, hdb:pio ICH7: IDE port disabled Probing IDE interface ide0... Driver 'sd' needs updating - please use bus_type methods sd 0:0:0:0: [sda] 781422768 512-byte hardware sectors (400088 MB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sd 0:0:0:0: [sda] 781422768 512-byte hardware sectors (400088 MB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sda: sda1 sda2 sda3 sda4 sd 0:0:0:0: [sda] Attached SCSI disk firewire_core: created new fw device fw0 (0 config rom retries, S400) hda: _NEC DVD_RW ND-4571A, ATAPI CD/DVD-ROM drive hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4 hda: UDMA/33 mode selected ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 hda: ATAPI 48X DVD-ROM DVD-R-RAM CD-R/RW drive, 2048kB Cache Uniform CD-ROM driver Revision: 3.20 device-mapper: uevent: version 1.0.3 device-mapper: ioctl: 4.12.0-ioctl (2007-10-02) initialised: [EMAIL PROTECTED] Attempting manual resume kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. input: PC Speaker as /class/input/input2 pnp: the driver 'parport_pc' has been registered parport_pc 00:07: reported by Plug and Play ACPI parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.02 (26-Jul-2007) iTCO_wdt: Found a ICH7 or ICH7R TCO device (Version=2, TCOBASE=0x0460) iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) parport_pc 00:07: driver attached input: Power Button (FF) as /class/input/input3 intel_rng: FWH not detected ACPI: Power Button (FF) [PWRF] input: Power Button (CM) as /class/input/input4 ACPI: PCI Interrupt :00:1f.3[B] -> GSI 19 (level, low) -> IRQ 19 ACPI: Power Button (CM) [PWRB] ACPI: PCI Interrupt :00:1b.0[A] ->
Bug#482675: marked as done (Kernel oops on amd64 quad core 9850)
Your message dated Tue, 3 Jun 2008 08:57:54 +0200 with message-id <[EMAIL PROTECTED]> and subject line Re: Bug#482675: Kernel oops on amd64 quad core 9850 has caused the Debian Bug report #482675, regarding Kernel oops on amd64 quad core 9850 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 482675: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=482675 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: installation-reports Boot method: netboot Image version: http://people.debian.org/~aba/d-i/images/daily/netboot/netboot.tar.gz Date: 2008-05-24 Machine: Homemade monster Processor: AMD Quad Core 9850 Memory: 8 GB Partitions: 50 GB / ext3, 8 GB swap, 500 GB /home ext3 Output of lspci -nn and lspci -vnn: see attached files. Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [ ] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [E] Install base system:[E] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: This is a brand new machine, also the harddrive is a new 1 TB sata (tried the same on an old 200 GB sata, but same problem). Everyting goes well until its formatting the second partition to ext3. It will hang in installation and the console gives me an oops. Unable to handle kernel paging request at Process seems to be sh Also tried not formatting the second partition and then installation begins but hangs at installing python, same oops message. Process: update-alternative I've done memtests with no errors. Ubuntu live CD works fine, but installation dies at the same place when formatting partition. (Could not see the oops) Also tried ubuntu netboot and hang at installing of kernel package. Attached lspci output and dmesg output. I've also run memtests but no errors. TIA, Marcus 00:00.0 Host bridge [0600]: ATI Technologies Inc RD790 Northbridge only dual slot PCI-e_GFX and HT3 K8 part [1002:5956] 00:02.0 PCI bridge [0604]: ATI Technologies Inc RD790 PCI to PCI bridge (external gfx0 port A) [1002:5978] 00:06.0 PCI bridge [0604]: ATI Technologies Inc RD790 PCI to PCI bridge (PCI express gpp port C) [1002:597c] 00:07.0 PCI bridge [0604]: ATI Technologies Inc RD790 PCI to PCI bridge (PCI express gpp port D) [1002:597d] 00:09.0 PCI bridge [0604]: ATI Technologies Inc RD790 PCI to PCI bridge (PCI express gpp port E) [1002:597e] 00:0a.0 PCI bridge [0604]: ATI Technologies Inc RD790 PCI to PCI bridge (PCI express gpp port F) [1002:597f] 00:12.0 SATA controller [0106]: ATI Technologies Inc SB600 Non-Raid-5 SATA [1002:4380] 00:13.0 USB Controller [0c03]: ATI Technologies Inc SB600 USB (OHCI0) [1002:4387] 00:13.1 USB Controller [0c03]: ATI Technologies Inc SB600 USB (OHCI1) [1002:4388] 00:13.2 USB Controller [0c03]: ATI Technologies Inc SB600 USB (OHCI2) [1002:4389] 00:13.3 USB Controller [0c03]: ATI Technologies Inc SB600 USB (OHCI3) [1002:438a] 00:13.4 USB Controller [0c03]: ATI Technologies Inc SB600 USB (OHCI4) [1002:438b] 00:13.5 USB Controller [0c03]: ATI Technologies Inc SB600 USB Controller (EHCI) [1002:4386] 00:14.0 SMBus [0c05]: ATI Technologies Inc SBx00 SMBus Controller [1002:4385] (rev 14) 00:14.1 IDE interface [0101]: ATI Technologies Inc SB600 IDE [1002:438c] 00:14.2 Audio device [0403]: ATI Technologies Inc SBx00 Azalia [1002:4383] 00:14.3 ISA bridge [0601]: ATI Technologies Inc SB600 PCI to LPC Bridge [1002:438d] 00:14.4 PCI bridge [0604]: ATI Technologies Inc SBx00 PCI to PCI Bridge [1002:4384] 00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] HyperTransport Configuration [1022:1200] 00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] Address Map [1022:1201] 00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] DRAM Controller [1022:1202] 00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] Miscellaneous Control [1022:1203] 00:18.4 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron] Link Control [1022:1204] 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon HD 3870 [1002:9501] 01:00.1 Audio device [0403]: ATI Technologies Inc Radeon HD 3870 Audio device [1002:aa18] 02:00.0 Ethernet controller [0200]: Re
Processed: bug 482964 is forwarded to http://bugzilla.kernel.org/show_bug.cgi?id=10839
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.28 > forwarded 482964 http://bugzilla.kernel.org/show_bug.cgi?id=10839 Bug#482964: boot freezes with kernel 2.6.24-1-686 Noted your statement that Bug has been forwarded to http://bugzilla.kernel.org/show_bug.cgi?id=10839. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#482940: linux-source-2.6.24: saa7134-empress or saa6752hs problem
Processing commands for [EMAIL PROTECTED]: > tags 482940 moreinfo Bug#482940: linux-source-2.6.24: saa7134-empress or saa6752hs problem There were no tags set. Tags added: moreinfo > stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#482531: marked as done (DPMS off mode issue with )
Your message dated Tue, 3 Jun 2008 09:01:50 +0200 with message-id <[EMAIL PROTECTED]> and subject line Re: DPMS off mode issue with has caused the Debian Bug report #482531, regarding DPMS off mode issue with to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 482531: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=482531 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: linux-image-2.6.18-6-686 Version: 2.6.18.dfsg.1-18etch3 I've noticed that since I've upgraded from linux-image-2.6.18-6 version 2.6.18.dfsg.1-18etch1 that I have been having issues with DPMS off mode. This began after the following upgrade: '[UPGRADE] linux-image-2.6.18-6-686 2.6.18.dfsg.1-18etch1 -> 2.6.18.dfsg.1-18etch3'. it is also present in version 2.6.18.dfsg.1-18etch4 as well. All other versions of Debian kernels that I've ran have not exhibited this issue. So I have a strong feeling the bug was introduced in 1-18etch3. What happens is that sometimes the system will not come out of DPMS off mode. This issue only happens at the virtual console, where as in Xorg, DPMS works just fine. The problem is a bit intermittent, but I have a found a way to make it happen more frequently, which I'll get into more detail further down. Essentially, when the buggy DPMS behavior happens, I'll tap a key like you normally do to get the display to come out of DPMS (power save mode) when at the console, but in this case it will show the display for a half second then go right back into DPMS off mode. The only way to bring it out of this buggy DPMS state is to pull the plug on my LCD monitor to have it completely power down/reset. What tends to trigger it the most is when I exit xfce4 (version 4.3.99.2). As soon as it exits Xorg from there and goes back to the virtual console it goes into the buggy DPMS state described above. I've noticed that it tends to happen more rarely when exiting icewm (version 1.2.28-4). However, sometimes it will happen just when the virtual console has had a chance for be idle enough for DPMS off mode to kick in. Just for reference, this is in Debian Etch/stable which you may have already guessed from the versions of the packages I described above. --- End Message --- --- Begin Message --- Version: 2.6.24-1 assuming fixed with newer drivers in newer linux images. for etch checkout etch + half images -> http://wiki.debian.org/EtchAndAHalf thanks for report -- maks --- End Message ---
Processed: tagging 482331
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.26 > tags 482331 + pending Bug#482331: linux-libc-dev: possibly another include/linux/netfilter.h problem There were no tags set. Tags added: pending > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#484048: marked as done (gettimeofday() crashes if given a timezone on amd64)
Your message dated Tue, 3 Jun 2008 08:48:26 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: gettimeofday() crashes if given a timezone on amd64
has caused the Debian Bug report #484048,
regarding gettimeofday() crashes if given a timezone on amd64
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
484048: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=484048
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: libc6
Version: 2.7-10
I just upgraded from etch to lenny on an amd64 machine. gdm crashed
at startup. I traced it down to gdm calling gettimeofday() with a
timezone. The following program also crashes:
#include
#include
int
main(int argc, char *argv[])
{
struct timeval tv;
struct timezone tz;
gettimeofday(&tv, &tz);
return 0;
}
If you remove the timezone, it works fine. The timezone was
pointless in gdm, so I removed it and it works fine now.
It seems to work fine on an x86 box, which has a different problem :(.
I am using Debian lenny/sid, kernel 2.6.25.
--- End Message ---
--- Begin Message ---
tried to reproduce but example code, just runs fine.
> I recompiled it to see what was happening and the problem went away.
> The only difference was that I compiled by hand (with "make") instead of
> using the debian tool to compile it, and it was compiled under etch. So
> it's not a problem any more, but if you see this again you know what it
> is.
seems you used an supported gcc version, gcc 4.3 was known to miscompile
older kernel versions.
thus closing
--
maks
--- End Message ---
