Bug#701744: Xen netback regression
On Thu, 2013-07-04 at 04:42 +0100, Ben Hutchings wrote: I must apologise for the poor response to this bug report. It should have been fixed long ago, and it was fixed upstream in April. While there are an overwhelming number of bugs against the kernel, this regression should have been treated as a particularly high priority. This is largely my fault, for not following things through to the end, sorry. I'm looking at it now. [...] As Ian requested, the netback fixes were included in Linux 3.2.47 and thus should appear in the wheezy-proposed-updates suite shortly. Aside from that, any regression that occurred as a result of a security update may also be fixed in a security update, and I hope we will be able to provide such updates for both Debian 6 (squeeze) and 7 (wheezy) in the next few weeks. I've put my test builds for both squeeze- and wheezy-security up at http://xenbits.xen.org/people/ianc/debian/701774/ I'm away all of next week so any testing would be much appreciated. I've not yet pushed to the Debian svn server. Ian. squeeze sha1: 65f36304ffb778e17f652605664733df7323 linux-headers-2.6.32-5-amd64_2.6.32-48squeeze4~ijc0_amd64.deb 6558256ce542dc6971f08e5e5729eb3e469dd244 linux-image-2.6.32-5-amd64-dbg_2.6.32-48squeeze4~ijc0_amd64.deb 3f582a2161b80108ad724ef41a255f21cefa7111 linux-image-2.6.32-5-amd64_2.6.32-48squeeze4~ijc0_amd64.deb c6bd7faa9cd3f1106e26bb5202e1a7dee5fef3c5 linux-headers-2.6.32-5-common_2.6.32-48squeeze4~ijc0_amd64.deb 357b27101f0a104c3f64b92ba26901190f6b9888 linux-headers-2.6.32-5-openvz-amd64_2.6.32-48squeeze4~ijc0_amd64.deb 2d9052da70cfcbf845f492e809cb5ca72246461f linux-image-2.6.32-5-openvz-amd64-dbg_2.6.32-48squeeze4~ijc0_amd64.deb cd42aee403f6438310c63ea7034b567b62d29bf6 linux-image-2.6.32-5-openvz-amd64_2.6.32-48squeeze4~ijc0_amd64.deb 53684d8006b976f10e78ea85efb0db4500f930ed linux-headers-2.6.32-5-common-openvz_2.6.32-48squeeze4~ijc0_amd64.deb e5951f3ed479cd13790aef78b0894d1fef411077 linux-headers-2.6.32-5-all_2.6.32-48squeeze4~ijc0_amd64.deb b47f97e4152feb1de7012244730ab01fe78806b2 linux-headers-2.6.32-5-all-amd64_2.6.32-48squeeze4~ijc0_amd64.deb 4555840f3a6c7bde10a8ab5af2fd16733a4f978d linux-libc-dev_2.6.32-48squeeze4~ijc0_amd64.deb f682b410ca525aac93783a493de51c7bae296e66 linux-tools-2.6.32_2.6.32-48squeeze4~ijc0_amd64.deb cd15f982c502b9a1d2c639ee5d76fd197c6578b9 linux-headers-2.6.32-5-vserver-amd64_2.6.32-48squeeze4~ijc0_amd64.deb 539688dc36c74f52018c4ad67a72693adf98bfd1 linux-image-2.6.32-5-vserver-amd64-dbg_2.6.32-48squeeze4~ijc0_amd64.deb 0e8f3190597446b999436ed44c3e5ad7655d444f linux-image-2.6.32-5-vserver-amd64_2.6.32-48squeeze4~ijc0_amd64.deb 0cb2067a8834ed8fda1059050234d418b62d633b linux-headers-2.6.32-5-common-vserver_2.6.32-48squeeze4~ijc0_amd64.deb bea318635fa4a1fd400b0a66ab36e55f6360bb08 linux-headers-2.6.32-5-xen-amd64_2.6.32-48squeeze4~ijc0_amd64.deb 9c22ffe924a9264f9b48412ee41f9f9c47d1bf63 linux-image-2.6.32-5-xen-amd64-dbg_2.6.32-48squeeze4~ijc0_amd64.deb 0264e97cb2513d44b8b3472df8e011cfc14c0fc7 linux-image-2.6.32-5-xen-amd64_2.6.32-48squeeze4~ijc0_amd64.deb 742c794ca994deab93005d6acf020420de6cf950 xen-linux-system-2.6.32-5-xen-amd64_2.6.32-48squeeze4~ijc0_amd64.deb 3c8deab3fce62286bd1025b7b2fab86f55a5756c linux-headers-2.6.32-5-common-xen_2.6.32-48squeeze4~ijc0_amd64.deb b0f2e5c4faf4974cecdea692494523b4eff6887b linux-2.6_2.6.32-48squeeze4~ijc0_amd64.changes 1c9278898a81c19804a11f5afb8edfb4567b1beb linux-2.6_2.6.32.orig.tar.gz 7bd40facb9aec671b5202ec3b92bad8799e5e180 linux-2.6_2.6.32-48squeeze4~ijc0.diff.gz e8f6fbbf554f616b4d08dd729762ce2b98fedaa5 linux-2.6_2.6.32-48squeeze4~ijc0.dsc wheezy sha1: 6eb9a8a69053066263a3454cde22c0059d71f56f linux-headers-3.2.0-4-amd64_3.2.41-2+deb7u3~ijc0_amd64.deb ff9e884bcff211c44aa24563ba84e88a0a7cfdd3 linux-image-3.2.0-4-amd64-dbg_3.2.41-2+deb7u3~ijc0_amd64.deb 7277a05de0321aa71220b85a8c7ff340c2b31ebb linux-image-3.2.0-4-amd64_3.2.41-2+deb7u3~ijc0_amd64.deb 3b374bcebc66026403e5aaa73e7b087d1750213b xen-linux-system-3.2.0-4-amd64_3.2.41-2+deb7u3~ijc0_amd64.deb 1d47cf40d6aaf316290e140a42ff3ff4c4b5e462 linux-headers-3.2.0-4-common_3.2.41-2+deb7u3~ijc0_amd64.deb 0169d90ce5fd835c0f6a77ca04ab3c890acfe3b0 linux-headers-3.2.0-4-all_3.2.41-2+deb7u3~ijc0_amd64.deb 9ad10e6dbecb959ea00e375bdf8bb22895325d8f linux-headers-3.2.0-4-all-amd64_3.2.41-2+deb7u3~ijc0_amd64.deb d9f566e2a9430b213f80a1197c7f184ea2e29160 linux-libc-dev_3.2.41-2+deb7u3~ijc0_amd64.deb 74c2d20ccd1c2f9f320986c503184d59e3d82ea8 linux-headers-3.2.0-4-rt-amd64_3.2.41-2+deb7u3~ijc0_amd64.deb ddf947460ab485e0e1ff832777a0fc0c4ec9882c linux-image-3.2.0-4-rt-amd64-dbg_3.2.41-2+deb7u3~ijc0_amd64.deb 532a947cfa8977ffa144373a9e15ff3b38088e57 linux-image-3.2.0-4-rt-amd64_3.2.41-2+deb7u3~ijc0_amd64.deb 050c325223ea6b86c45b014809c49be135eb5e1b linux-headers-3.2.0-4-common-rt_3.2.41-2+deb7u3~ijc0_amd64.deb 1fbcaf9fb956c52b7326ee2eb71f1dc24f13dd38
Processed: Re: [Pkg-alsa-devel] Bug#714345: alsa-base: No sound on PowerPC with Jessie upgrade
Processing commands for cont...@bugs.debian.org: reassign 714345 linux-image-3.9-1-powerpc Bug #714345 [alsa-base] alsa-base: No sound on PowerPC with Jessie upgrade Bug reassigned from package 'alsa-base' to 'linux-image-3.9-1-powerpc'. No longer marked as found in versions alsa-base/1.0.25+3. Ignoring request to alter fixed versions of bug #714345 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 714345: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714345 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.137310153729900.transcr...@bugs.debian.org
Uploading linux (3.10.1-1)
I'm intending to upload linux to unstable next week after the first stable update for 3.10. This will of course involve an ABI bump. 3.9.8-1 has not yet reached testing, and I may request that it be pushed into testing a day or two early, before it's superseded in unstable by 3.10.1-1. Ben. -- Ben Hutchings Tomorrow will be cancelled due to lack of interest. signature.asc Description: This is a digitally signed message part
[PATCH] New upstream release (3.10)
This patch updates the linux-tools package for linux-3.10. This was relatively straightforward except for the CONFIG_SYMBOL_PREFIX rework; I believe I have kept with the spirit of the v3.9 version of the package. HTH, Chris --- debian/changelog |6 ++ debian/patches/modpost-symbol-prefix.patch | 23 --- debian/patches/tools-perf-version.patch| 20 3 files changed, 26 insertions(+), 23 deletions(-) diff --git a/debian/changelog b/debian/changelog index f30d4cd..033aad1 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,9 @@ +linux-tools (3.10-1) UNRELEASED; urgency=low + + * New upstream release + + -- Chris Boot deb...@bootc.net Mon, 01 Jul 2013 22:07:42 +0100 + linux-tools (3.9.4-1) unstable; urgency=low * New upstream release diff --git a/debian/patches/modpost-symbol-prefix.patch b/debian/patches/modpost-symbol-prefix.patch index 7fc7e7a..07cfd4d 100644 --- a/debian/patches/modpost-symbol-prefix.patch +++ b/debian/patches/modpost-symbol-prefix.patch @@ -1,19 +1,12 @@ a/scripts/mod/modpost.c -+++ b/scripts/mod/modpost.c -@@ -16,15 +16,11 @@ - #include ctype.h - #include string.h +Index: linux-tools/scripts/mod/modpost.c +=== +--- linux-tools.orig/scripts/mod/modpost.c 2013-06-30 23:13:29.0 +0100 linux-tools/scripts/mod/modpost.c 2013-07-01 22:11:53.450887929 +0100 +@@ -18,7 +18,6 @@ + #include limits.h + #include stdbool.h #include modpost.h -#include ../../include/generated/autoconf.h #include ../../include/linux/license.h + #include ../../include/linux/export.h - /* Some toolchains use a `_' prefix for all user symbols. */ --#ifdef CONFIG_SYMBOL_PREFIX --#define MODULE_SYMBOL_PREFIX CONFIG_SYMBOL_PREFIX --#else -+/* No Debian architecture currently does this. */ - #define MODULE_SYMBOL_PREFIX --#endif - - - /* Are we using CONFIG_MODVERSIONS? */ diff --git a/debian/patches/tools-perf-version.patch b/debian/patches/tools-perf-version.patch index 8dc5971..1a04222 100644 --- a/debian/patches/tools-perf-version.patch +++ b/debian/patches/tools-perf-version.patch @@ -1,6 +1,8 @@ a/tools/perf/Makefile -+++ b/tools/perf/Makefile -@@ -1141,7 +1141,7 @@ perfexec_instdir_SQ = $(subst ','\'',$(p +Index: linux-tools/tools/perf/Makefile +=== +--- linux-tools.orig/tools/perf/Makefile 2013-06-30 23:13:29.0 +0100 linux-tools/tools/perf/Makefile2013-07-01 22:13:20.073226760 +0100 +@@ -1172,7 +1172,7 @@ install-bin: all $(INSTALL) -d -m 755 '$(DESTDIR_SQ)$(bindir_SQ)' @@ -9,7 +11,7 @@ $(INSTALL) -d -m 755 '$(DESTDIR_SQ)$(perfexec_instdir_SQ)/scripts/perl/Perf-Trace-Util/lib/Perf/Trace' $(INSTALL) -d -m 755 '$(DESTDIR_SQ)$(perfexec_instdir_SQ)/scripts/perl/bin' $(INSTALL) $(OUTPUT)perf-archive -t '$(DESTDIR_SQ)$(perfexec_instdir_SQ)' -@@ -1154,7 +1154,7 @@ install-bin: all +@@ -1185,7 +1185,7 @@ $(INSTALL) scripts/python/*.py -t '$(DESTDIR_SQ)$(perfexec_instdir_SQ)/scripts/python' $(INSTALL) scripts/python/bin/* -t '$(DESTDIR_SQ)$(perfexec_instdir_SQ)/scripts/python/bin' $(INSTALL) -d -m 755 '$(DESTDIR_SQ)$(sysconfdir_SQ)/bash_completion.d' @@ -18,7 +20,7 @@ $(INSTALL) -d -m 755 '$(DESTDIR_SQ)$(perfexec_instdir_SQ)/tests' $(INSTALL) tests/attr.py '$(DESTDIR_SQ)$(perfexec_instdir_SQ)/tests' $(INSTALL) -d -m 755 '$(DESTDIR_SQ)$(perfexec_instdir_SQ)/tests/attr' -@@ -1167,7 +1167,7 @@ install-python_ext: +@@ -1198,7 +1198,7 @@ # 'make install-doc' should call 'make -C Documentation install' $(INSTALL_DOC_TARGETS): @@ -27,9 +29,11 @@ ### Cleaning rules a/tools/perf/Documentation/Makefile -+++ b/tools/perf/Documentation/Makefile -@@ -188,13 +188,15 @@ ifdef missing_tools +Index: linux-tools/tools/perf/Documentation/Makefile +=== +--- linux-tools.orig/tools/perf/Documentation/Makefile 2013-06-30 23:13:29.0 +0100 linux-tools/tools/perf/Documentation/Makefile 2013-07-01 22:13:20.073226760 +0100 +@@ -188,13 +188,15 @@ $(error You need to install $(missing_tools) for man pages) endif -- 1.7.10.4 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1372716602-69171-1-git-send-email-deb...@bootc.net
Bug#626593: marked as done (linux-image-2.6.32-5-amd64: BUG during disk hot-plugging when setting the elevator via udev)
Your message dated Sat, 6 Jul 2013 17:57:49 +0200
with message-id 20130706155749.GA12523@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #626593,
regarding linux-image-2.6.32-5-amd64: BUG during disk hot-plugging when setting
the elevator via udev
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 ow...@bugs.debian.org
immediately.)
--
626593: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626593
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 2.6.32-31
Severity: normal
Hi,
We are experiencing the following problem on a number of machines using
2.6.32-5-amd64_2.6.32-31. The machines are used for virtual machine hosting and
have a number of LUNs exported from an FC-connected SAN connected to them via a
multipath topology. Our regular workflow involves hot-removing and hot-adding
disks according to the VMs hosted.
For the LUNs exported by the SAN storage, we have the following udev rule in
place:
-8-
# Set all netapp LUN schedulers to noop
# Skip partitions
KERNEL==*[0-9], GOTO=lunsched_end
# Set scheduler
ACTION==add, SUBSYSTEM==block, ATTRS{vendor}==NETAPP,
ATTRS{model}==LUN,ATTR{queue/scheduler}=noop
LABEL=lunsched_end
-8-
Having upgraded from lenny to squeeze last week, we encountered the following
crash during a SCSI bus rescan that added new disks to a system:
[ 1258.343275] [ cut here ]
[ 1258.343280] sd 0:0:0:226: [sdgv] Write cache: disabled, read cache: enabled,
doesn't support DPO or FUA
[ 1258.343287] kernel BUG at
/tmp/buildd/linux-2.6-2.6.32/debian/build/source_amd64_none/fs/sysfs/file.c:539!
[ 1258.343289] invalid opcode: [#2] SMP
[ 1258.343292] last sysfs file:
/sys/devices/pci:00/:00:05.0/:10:00.0/host0/rport-0:0-0/target0:0:0/0:0:0:216/block/sdgn/removable
[ 1258.343295] CPU 4
[ 1258.343296] Modules linked in: kvm_intel kvm nf_conntrack_ipv6
ip6table_filter ip6_tables xt_tcpudp xt_pkttype nf_conntrack_ipv4
nf_defrag_ipv4 xt_state nf_conntrack iptable_filter ip_tables x_tables 8021q
garp bridge stp bonding dm_round_robin dm_multipath scsi_dh ipmi_poweroff
ipmi_devintf radeon ttm drm_kms_helper snd_pcm ipmi_si drm ipmi_msghandler
i2c_algo_bit i5k_amb i2c_core snd_timer psmouse i5000_edac snd soundcore
snd_page_alloc hpwdt hpilo serio_raw edac_core pcspkr rng_core evdev shpchp
container pci_hotplug button processor ext3 jbd mbcache dm_mod sd_mod
crc_t10dif usbhid hid uhci_hcd qla2xxx scsi_transport_fc tg3 ehci_hcd bnx2
scsi_tgt usbcore nls_base cciss libphy scsi_mod thermal thermal_sys [last
unloaded: scsi_wait_scan]
[ 1258.343332] Pid: 12287, comm: async/20 Tainted: G D W 2.6.32-5-amd64
#1 ProLiant BL460c G1
[ 1258.343335] RIP: 0010:[8113ecff] [8113ecff]
sysfs_create_file+0x13/0x21
[ 1258.343340] RSP: 0018:8803ffd3fdd8 EFLAGS: 00010246
[ 1258.343342] RAX: RBX: 81485598 RCX: 589a
[ 1258.343344] RDX: 81476c38 RSI: 81485598 RDI:
[ 1258.343347] RBP: 88041afaba90 R08: R09: 813ad975
[ 1258.343349] R10: fff4 R11: 000186a0 R12:
[ 1258.343351] R13: R14: 8804264d4458 R15:
[ 1258.343354] FS: () GS:88000fd0()
knlGS:
[ 1258.343356] CS: 0010 DS: 0018 ES: 0018 CR0: 8005003b
[ 1258.343359] CR2: 7f541f42 CR3: 0003fddee000 CR4: 000426e0
[ 1258.343361] DR0: DR1: DR2:
[ 1258.343363] DR3: DR6: 0ff0 DR7: 0400
[ 1258.343366] Process async/20 (pid: 12287, threadinfo 8803ffd3e000, task
8804273f1530)
[ 1258.343368] Stack:
[ 1258.343369] 811761aa 8804078c6418
8804078c60f0
[ 1258.343372] 0 8118024b 8804264d4400 8804264d4400
8804083ba800
[ 1258.343375] 0 8804083ba928 0001 81184021
8804264d4400
[ 1258.343378] Call Trace:
[ 1258.343381] [811761aa] ? elv_register_queue+0x4f/0x6f
[ 1258.343385] [8118024b] ? blk_register_queue+0x7f/0xcc
[ 1258.343388] [81184021] ? add_disk+0xb8/0x108
[ 1258.343393] [a01506be] ? sd_probe_async+0x119/0x1d8 [sd_mod]
[ 1258.343396] [810698a7] ? async_thread+0x0/0x20d
[ 1258.343399] [810699a6] ? async_thread+0xff/0x20d
[ 1258.343403] [81049fee] ? default_wake_function+0x0/0x9
[ 1258.343406] [810698a7] ? async_thread+0x0/0x20d
[
Bug#613845: marked as done (base: Speaker doesn't work but headphones works well. Laptop HP G62.)
Your message dated Sat, 6 Jul 2013 17:57:49 +0200
with message-id 20130706155749.GA12523@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #613845,
regarding base: Speaker doesn't work but headphones works well. Laptop HP G62.
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 ow...@bugs.debian.org
immediately.)
--
613845: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613845
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: base
Severity: important
Tags: squeeze
-- System Information:
Debian Release: 6.0
APT prefers squeeze-updates
APT policy: (500, 'squeeze-updates'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
I can't make my audio system works properly on my HP G62 laptop. I can hear the
sound only in my headphone, and my speaker and microphone don't work at all.
Here some information:
# cat /proc/asound/card0/codec#* | grep Codec
Codec: Realtek ID 270
Codec: Intel G45 DEVIBX
# aplay -l output:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: HDA Generic [HDA Generic]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: Intel [HDA Intel], device 3: INTEL HDMI [INTEL HDMI]
Subdevices: 1/1
Subdevice #0: subdevice #0
# lspci | grep -i audio
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High
Definition Audio (rev 05)
Alsa information:
# dpkg -l | grep alsa
ii alsa-base1.0.23+dfsg-2 ALSA
driver configuration files
ii alsa-utils 1.0.23-3
Utilities for configuring and using ALSA
ii bluez-alsa 4.66-3
Bluetooth ALSA support
ii libsdl1.2debian-alsa 1.2.14-6.1
Simple DirectMedia Layer (with X11 and ALSA options)
Try to emulate such behave in console (without X). Run mpg123 and got the same
stuff - can only hear sound through headphones.
My /etc/modprobe.d/alsa-base.conf looks like:
# autoloader aliases
install sound-slot-0 /sbin/modprobe snd-card-0
install sound-slot-1 /sbin/modprobe snd-card-1
install sound-slot-2 /sbin/modprobe snd-card-2
install sound-slot-3 /sbin/modprobe snd-card-3
install sound-slot-4 /sbin/modprobe snd-card-4
install sound-slot-5 /sbin/modprobe snd-card-5
install sound-slot-6 /sbin/modprobe snd-card-6
install sound-slot-7 /sbin/modprobe snd-card-7
# Cause optional modules to be loaded above generic modules
install snd /sbin/modprobe --ignore-install snd { /sbin/modprobe --quiet
snd-ioctl32 ; /sbin/modprobe --quiet snd-seq ; }
install snd-rawmidi /sbin/modprobe --ignore-install snd-rawmidi {
/sbin/modprobe --quiet snd-seq-midi ; : ; }
install snd-emu10k1 /sbin/modprobe --ignore-install snd-emu10k1 {
/sbin/modprobe --quiet snd-emu10k1-synth ; : ; }
# Prevent abnormal drivers from grabbing index 0
options bt87x index=-2
options cx88_alsa index=-2
options snd-atiixp-modem index=-2
options snd-intel8x0m index=-2
options snd-via82xx-modem index=-2
# Keep snd-pcsp from beeing loaded as first soundcard
options snd-pcsp index=-2
# Keep snd-usb-audio from beeing loaded as first soundcard
options snd-usb-audio index=-2
Appended to config next line:
options snd-hda-intel model=basic
then change it to
options snd-hda-intel model=hp
And even try to comment out:
options snd-intel8x0m index=-2
After any changes reboot the system or run alsa force-reload. But nothing help
me.
Also tried to delete pulseaudio:
apt-get purge pulseaudio
But this step was unsuccessful too.
---End Message---
---BeginMessage---
Hi,
your bug has been filed against the linux-2.6 source package and was filed for
a kernel older than the recently released Debian 7.x / Wheezy with a severity
less than important.
We don't have the ressources to reproduce the complete backlog of all older
kernel
bugs, so we're closing this bug for now. If you can reproduce the bug with
Debian Wheezy
or a more recent kernel from testing or unstable, please reopen the bug by
sending
a mail to cont...@bugs.debian.org with the following three commands included in
the
mail:
reopen BUGNUMBER
reassign BUGNUMBER src:linux
thanks
Cheers,
Moritz---End Message---
Bug#627098: marked as done (linux-image-2.6.32-5-686: rndis_host fails to recognize usb device)
Your message dated Sat, 6 Jul 2013 17:57:49 +0200 with message-id 20130706155749.GA12523@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #627098, regarding linux-image-2.6.32-5-686: rndis_host fails to recognize usb device 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 ow...@bugs.debian.org immediately.) -- 627098: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627098 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-31 Severity: normal I'm running squeeze and I have a usb communication device that my 2.6.32-5-686 kernel doesn't recognize. The device, called a PC Port, is manufactured by 2Wire, which is now part of Pace Plc. It functions as an interface to a phone line based network using HomePNA technology. I use a 2Wire modem/router which is also a usb device running HomePNA, and it is recognized by rndis_host as an eth device, but my PC Port is not. -- Package-specific info: ** Version: Linux version 2.6.32-5-686 (Debian 2.6.32-31) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Tue Mar 8 21:36:00 UTC 2011 ** Command line: root=/dev/sdb2 ro acpi=off pci=noacpi BOOT_IMAGE=vmlinuz ** Not tainted ** Kernel log: [6.530154] scsi target2:0:6: Beginning Domain Validation [6.542446] scsi target2:0:6: Ending Domain Validation [8.884195] scsi 0:0:0:0: Direct-Access ATA ST320423A3.02 PQ: 0 ANSI: 5 [8.885045] scsi 0:0:1:0: Direct-Access ATA ST380021A3.19 PQ: 0 ANSI: 5 [8.889551] scsi 1:0:0:0: CD-ROM_NEC DVD_RW ND-3550A 1.05 PQ: 0 ANSI: 5 [8.948785] usbcore: registered new interface driver hiddev [8.969845] sd 0:0:0:0: [sdb] 40011300 512-byte logical blocks: (20.4 GB/19.0 GiB) [8.970143] sd 0:0:0:0: [sdb] Write Protect is off [8.970205] sd 0:0:0:0: [sdb] Mode Sense: 00 3a 00 00 [8.970297] sd 0:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [8.970843] sdb: [8.972468] sd 2:0:6:0: [sda] 196608 512-byte logical blocks: (100 MB/96.0 MiB) [8.974295] sd 2:0:6:0: [sda] Write Protect is off [8.974360] sd 2:0:6:0: [sda] Mode Sense: 31 00 00 08 [8.975419] sr0: scsi3-mmc drive: 48x/48x writer cd/rw xa/form2 cdda tray [8.975482] Uniform CD-ROM driver Revision: 3.20 [8.975626] sdb1 sdb2 sdb3 sdb4 [8.977076] sr 1:0:0:0: Attached scsi CD-ROM sr0 [8.977673] sd 2:0:6:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [8.984427] sda: sdb5 [8.994712] sd 0:0:1:0: [sdc] 156301488 512-byte logical blocks: (80.0 GB/74.5 GiB) [9.017525] sdb6 [9.018395] sd 0:0:1:0: [sdc] Write Protect is off [9.018459] sd 0:0:1:0: [sdc] Mode Sense: 00 3a 00 00 [9.018552] sd 0:0:1:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [9.021051] sdc: sda4 [9.030249] sdc1 sdc2 sdc3 sdc4 [9.030602] sd 2:0:6:0: [sda] Attached SCSI removable disk [9.050326] sd 0:0:0:0: [sdb] Attached SCSI disk [9.050408] sdc5 sdc6 [9.071474] sd 0:0:1:0: [sdc] Attached SCSI disk [9.129991] sd 2:0:6:0: Attached scsi generic sg0 type 0 [9.131411] sd 0:0:0:0: Attached scsi generic sg1 type 0 [9.132892] sd 0:0:1:0: Attached scsi generic sg2 type 0 [9.134253] sr 1:0:0:0: Attached scsi generic sg3 type 5 [9.342853] generic-usb 0003:051D:0002.0001: hiddev0,hidraw0: USB HID v1.10 Device [APC Back-UPS ES 350 FW:823.B1.D USB FW:B1] on usb-:00:1d.0-2/input0 [9.342999] usbcore: registered new interface driver usbhid [9.343061] usbhid: v2.6:USB HID core driver [ 14.325035] udev[261]: starting version 164 [ 15.369095] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 [ 15.562122] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [ 15.593819] udev[284]: renamed network interface eth1 to eth1-eth0 [ 15.603951] udev[301]: renamed network interface eth0 to eth1 [ 15.622165] intel_rng: Firmware space is locked read-only. If you can't or [ 15.622169] intel_rng: don't want to disable this in firmware setup, and if [ 15.622172] intel_rng: you are certain that your system has a functional [ 15.622174] intel_rng: RNG, try using the 'no_fwh_detect' option. [ 15.645398] udev[284]: renamed network interface eth1-eth0 to eth0 [ 16.034809] input: PC Speaker as /devices/platform/pcspkr/input/input1 [ 16.431069] i801_smbus :00:1f.3: PCI-APIC IRQ transform: INT B - IRQ 17 [ 16.433890] parport_pc 00:0c: reported by Plug and Play BIOS [ 16.434009] parport0: PC-style at 0x378, irq 7
Bug#627585: marked as done (/boot/vmlinux-2.6.32-5-powerpc: Only depth 8bpp works with XGI Volari Z9s card PCA-5612 when using sisfb)
Your message dated Sat, 6 Jul 2013 17:57:49 +0200 with message-id 20130706155749.GA12523@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #627585, regarding /boot/vmlinux-2.6.32-5-powerpc: Only depth 8bpp works with XGI Volari Z9s card PCA-5612 when using sisfb 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 ow...@bugs.debian.org immediately.) -- 627585: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627585 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-31 Severity: normal File: /boot/vmlinux-2.6.32-5-powerpc If a depth other than 8 bit is chosen colours are not mapped properly. The text on the virtual console is not white. The same happens when X.org is started. The virtual console is functional at 8 bpp (appart from the DVI port), but if I force depth with the X server with -- -depth 16, 24 or 32 I get the same problem. Many X apps are no longer functional with 256 colours. However, 16 bpp should be adequate. (i.e. 1400x1050x16 similar to vesa mode 0x0348) Also the DVI port on the PCA-5612 card is not active. This should mirror the CRT output. This may be bug #610710. -- Package-specific info: ** Version: Linux version 2.6.32-5-powerpc (Debian 2.6.32-31) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 Mon Mar 7 22:49:07 UTC 2011 ** Command line: video=sisfb:mode:1400x1050x8,rate:60 panic=300 root=UUID=39c3b58f-8331-4c14-828b-77eb1c2132df ** Not tainted ** Kernel log: [5.620254] usb usb3: SerialNumber: :00:0c.2 [5.634551] usb usb3: configuration #1 chosen from 1 choice [5.647784] hub 3-0:1.0: USB hub found [5.660707] hub 3-0:1.0: 2 ports detected [5.673640] firewire_core: created device fw0: GUID 001106004b2f, S400 [5.689507] ohci_hcd :00:06.1: OHCI Host Controller [5.734225] ohci_hcd :00:06.1: new USB bus registered, assigned bus number 4 [5.779583] ohci_hcd :00:06.1: irq 9, io mem 0x80001000 [5.794679] ide-cd driver 5.00 [5.809129] ide-cd: hdc: ATAPI 48X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache [5.822181] Uniform CD-ROM driver Revision: 3.20 [5.885375] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001 [5.898898] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [5.911951] usb usb4: Product: OHCI Host Controller [5.924925] usb usb4: Manufacturer: Linux 2.6.32-5-powerpc ohci_hcd [5.938112] usb usb4: SerialNumber: :00:06.1 [5.954113] usb usb4: configuration #1 chosen from 1 choice [5.967748] hub 4-0:1.0: USB hub found [5.981646] hub 4-0:1.0: 1 port detected [5.995123] uhci_hcd :00:0c.3: enabling device ( - 0001) [6.061666] usb 3-2: new full speed USB device using uhci_hcd and address 2 [6.101632] uhci_hcd :00:0c.3: UHCI Host Controller [6.121635] uhci_hcd :00:0c.3: new USB bus registered, assigned bus number 5 [6.134638] uhci_hcd :00:0c.3: irq 9, io base 0x1060 [6.147287] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001 [6.159729] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [6.172033] usb usb5: Product: UHCI Host Controller [6.184322] usb usb5: Manufacturer: Linux 2.6.32-5-powerpc uhci_hcd [6.196609] usb usb5: SerialNumber: :00:0c.3 [6.211537] usb usb5: configuration #1 chosen from 1 choice [6.224707] hub 5-0:1.0: USB hub found [6.237178] hub 5-0:1.0: 2 ports detected [6.294778] usb 3-2: not running at top speed; connect to a high speed hub [6.340797] usb 3-2: New USB device found, idVendor=03f0, idProduct=3417 [6.353363] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [6.365814] usb 3-2: Product: HP LaserJet 3055 [6.378045] usb 3-2: Manufacturer: Hewlett-Packard [6.390165] usb 3-2: SerialNumber: 00CNCK544241 [6.404118] usb 3-2: configuration #1 chosen from 1 choice [6.983152] REISERFS (device hda2): found reiserfs format 3.6 with standard journal [6.995804] REISERFS (device hda2): using ordered data mode [7.052130] REISERFS (device hda2): journal params: device hda2, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 [7.070240] REISERFS (device hda2): checking transaction log (hda2) [7.126399] REISERFS (device hda2): Using r5 hash to sort names [ 10.477154] udev[177]: starting version 164 [ 12.891899] vt596_smbus :00:0c.4: Enabling SMBus device [ 13.010758] parport_pc: VIA 686A/8231 detected [ 13.010776] parport_pc: probing current configuration [
Bug#638555: marked as done (linux-image-2.6.32-5-amd64: CPU time overflows for long-running processes.)
Your message dated Sat, 6 Jul 2013 17:58:37 +0200
with message-id 20130706155837.GC12523@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #638555,
regarding linux-image-2.6.32-5-amd64: CPU time overflows for long-running
processes.
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 ow...@bugs.debian.org
immediately.)
--
638555: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638555
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 2.6.32-35
Severity: normal
When a process exceeds 2^31-1 (probably) milliseconds of CPU, the CPU time
counter becomes corrupt. I have noted the
following effects:
1) The process disappears altogether from top (although the overall usage stats
show it to be running)
2) ps shows it as having about 107000 days of CPU time (this has happened twice
and the values were similar but not the same).
The CPU used shown does not change thereafter.
3) The Fortran cpu_time subroutine is returning a value that cannot be
contained by an F12.2 format.
The program showing this behaviour is a multi-threaded Fortran program using
openmp.
-- Package-specific info:
** Version:
Linux version 2.6.32-5-amd64 (Debian 2.6.32-35) (da...@debian.org) (gcc version
4.3.5 (Debian 4.3.5-4) ) #1 SMP Tue Jun 14 09:42:28 UTC 2011
** Command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-amd64
root=UUID=d6f0eba9-34b3-4611-9c53-c5add4d475ba ro quiet
** Not tainted
** Kernel log:
[3787284.372253] ata1.00: configured for UDMA/33
[3787284.384645] ata1: EH complete
[3790126.013583] ata1.00: qc timeout (cmd 0xa0)
[3790126.013616] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
frozen
[3790126.024247] sr 0:0:0:0: CDB: Test Unit Ready: 00 00 00 00 00 00
[3790126.024267] ata1.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
[3790126.024268] res 51/20:03:00:00:00/00:00:00:00:00/a0 Emask 0x5
(timeout)
[3790126.045306] ata1.00: status: { DRDY ERR }
[3790126.055880] ata1: soft resetting link
[3790126.277349] ata1.00: configured for UDMA/33
[3790126.289766] ata1: EH complete
[3796622.772435] ata1: lost interrupt (Status 0x58)
[3796622.812765] ata1: drained 32768 bytes to clear DRQ.
[3796622.846094] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
frozen
[3796622.856720] ata1.00: ATAPI check failed (ireason=0x1 bytes=8)
[3796622.867231] sr 0:0:0:0: CDB: Get event status notification: 4a 01 00 00 10
00 00 00 08 00
[3796622.867277] ata1.00: cmd a0/00:00:00:08:00/00:00:00:00:00/a0 tag 0 pio
16392 in
[3796622.867286] res 58/00:01:00:08:00/00:00:00:00:00/a0 Emask 0x2
(HSM violation)
[3796622.888327] ata1.00: status: { DRDY DRQ }
[3796622.898811] ata1: soft resetting link
[3796623.133731] ata1.00: configured for UDMA/33
[3796623.146139] ata1: EH complete
[3835031.109809] ata1.00: qc timeout (cmd 0xa0)
[3835031.109829] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
frozen
[3835031.120334] sr 0:0:0:0: CDB: Test Unit Ready: 00 00 00 00 00 00
[3835031.120347] ata1.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
[3835031.120349] res 51/20:03:00:00:00/00:00:00:00:00/a0 Emask 0x5
(timeout)
[3835031.141291] ata1.00: status: { DRDY ERR }
[3835031.151736] ata1: soft resetting link
[3835031.378066] ata1.00: configured for UDMA/33
[3835031.390446] ata1: EH complete
[3836095.820064] ata1: lost interrupt (Status 0x58)
[3836095.854730] ata1: drained 32768 bytes to clear DRQ.
[3836095.893809] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
frozen
[3836095.904277] ata1.00: ATAPI check failed (ireason=0x1 bytes=8)
[3836095.914704] sr 0:0:0:0: CDB: Get event status notification: 4a 01 00 00 10
00 00 00 08 00
[3836095.914716] ata1.00: cmd a0/00:00:00:08:00/00:00:00:00:00/a0 tag 0 pio
16392 in
[3836095.914718] res 58/00:01:00:08:00/00:00:00:00:00/a0 Emask 0x2
(HSM violation)
[3836095.935571] ata1.00: status: { DRDY DRQ }
[3836095.945966] ata1: soft resetting link
[3836096.177225] ata1.00: configured for UDMA/33
[3836096.189651] ata1: EH complete
[3837592.000137] ata1.00: qc timeout (cmd 0xa0)
[3837592.000171] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
frozen
[3837592.010691] sr 0:0:0:0: CDB: Test Unit Ready: 00 00 00 00 00 00
[3837592.010778] ata1.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
[3837592.010781] res 51/20:03:00:00:00/00:00:00:00:00/a0 Emask 0x5
(timeout)
[3837592.031693] ata1.00: status: { DRDY ERR }
[3837592.042144] ata1: soft resetting link
[3837592.284365] ata1.00: configured for UDMA/33
[3837592.296812] ata1: EH complete
[3837736.021310] ata1.00: qc timeout (cmd 0xa0)
Bug#628200: marked as done (2.6.32-5-686 null pointer dereference and panic; maybe rtl8139?)
Your message dated Sat, 6 Jul 2013 17:57:49 +0200 with message-id 20130706155749.GA12523@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #628200, regarding 2.6.32-5-686 null pointer dereference and panic; maybe rtl8139? 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 ow...@bugs.debian.org immediately.) -- 628200: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628200 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.32-5-686 Version: 2.6.32-34squeeze1 My Fabiatech FX5624 has started hanging within hours of boot, since upgrading to this kernel; so far this has happened three times in the last 24 hours. Console output from the most recent hang, and other info, attached. It did not happen with the same machine's previous kernel, which my backups indicate was 2.6.32-30 (and to which I'm planning to revert if it continues crashing). ttfn/rjk Loading Linux 2.6.32-5-686 ... Loading initial ramdisk ... [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 2.6.32-5-686 (Debian 2.6.32-34squeeze1) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Wed May 18 07:08:50 UTC 2011 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] NSC Geode by NSC [0.00] Cyrix CyrixInstead [0.00] Centaur CentaurHauls [0.00] Transmeta GenuineTMx86 [0.00] Transmeta TransmetaCPU [0.00] UMC UMC UMC UMC [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009fc00 (usable) [0.00] BIOS-e820: 0009fc00 - 000a (reserved) [0.00] BIOS-e820: 000e - 0010 (reserved) [0.00] BIOS-e820: 0010 - 3f80 (usable) [0.00] BIOS-e820: e000 - f000 (reserved) [0.00] BIOS-e820: fed13000 - fed1a000 (reserved) [0.00] BIOS-e820: fed1c000 - fed2 (reserved) [0.00] BIOS-e820: ffb0 - 0001 (reserved) [0.00] DMI 2.3 present. [0.00] AMI BIOS detected: BIOS may corrupt low RAM, working around it. [0.00] last_pfn = 0x3f800 max_arch_pfn = 0x10 [0.00] PAT not supported by CPU. [0.00] init_memory_mapping: -373fe000 [0.00] RAMDISK: 2f20d000 - 2fa3f22b [0.00] ACPI Error: A valid RSDP was not found (20090903/tbxfroot-219) [0.00] 132MB HIGHMEM available. [0.00] 883MB LOWMEM available. [0.00] mapped low ram: 0 - 373fe000 [0.00] low ram: 0 - 373fe000 [0.00] node 0 low ram: - 373fe000 [0.00] node 0 bootmap 00012000 - 00018e80 [0.00] (9 early reservations) == bootmem [00 - 00373fe000] [0.00] #0 [00 - 001000] BIOS data page == [00 - 001000] [0.00] #1 [001000 - 002000]EX TRAMPOLINE == [001000 - 002000] [0.00] #2 [006000 - 007000] TRAMPOLINE == [006000 - 007000] [0.00] #3 [000100 - 00014c8bb4]TEXT DATA BSS == [000100 - 00014c8bb4] [0.00] #4 [002f20d000 - 002fa3f22b] RAMDISK == [002f20d000 - 002fa3f22b] [0.00] #5 [09cc00 - 10]BIOS reserved == [09cc00 - 10] [0.00] #6 [00014c9000 - 00014cf1c1] BRK == [00014c9000 - 00014cf1c1] [0.00] #7 [01 - 012000] PGTABLE == [01 - 012000] [0.00] #8 [012000 - 019000] BOOTMAP == [012000 - 019000] [0.00] found SMP MP-table at [c00ff780] ff780 [0.00] Zone PFN ranges: [0.00] DMA 0x0010 - 0x1000 [0.00] Normal 0x1000 - 0x000373fe [0.00] HighMem 0x000373fe - 0x0003f800 [0.00] Movable zone start PFN for each node [0.00] early_node_map[2] active PFN ranges [0.00] 0: 0x0010 - 0x009f [0.00] 0: 0x0100 - 0x0003f800 [0.00] Using APIC driver default [0.00] SFI: Simple Firmware Interface v0.7 http://simplefirmware.org [0.00] Intel MultiProcessor Specification v1.4 [0.00] Virtual Wire compatibility mode. [0.00] MPTABLE: OEM ID: Intel [0.00] MPTABLE: Product ID: Alviso [0.00] MPTABLE: APIC at: 0xFEE0 [0.00] Processor #0 (Bootup-CPU) [
Bug#631942: marked as done (linux-image-3.0.0-rc4-686-pae: oops and/or hangs when mounting a samba share)
Your message dated Sat, 6 Jul 2013 17:58:15 +0200 with message-id 20130706155815.GB12523@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #631942, regarding linux-image-3.0.0-rc4-686-pae: oops and/or hangs when mounting a samba share 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 ow...@bugs.debian.org immediately.) -- 631942: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631942 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 3.0.0~rc4-1~experimental.1 Severity: normal hi, kernel oopsed when trying to mount a samba share, then oopsed again at the next try, but then it also hung the machine. I rebooted, tried again, and got another oops, didn't try to hang it a second time :-) That last oops is in the log some lines down. Seems easy to reproduce, so don't hesitate to ask for more info. Thanks, -- Rémi -- Package-specific info: ** Version: Linux version 3.0.0-rc4-686-pae (Debian 3.0.0~rc4-1~experimental.1) (m...@debian.org) (gcc version 4.4.6 (Debian 4.4.6-6) ) #1 SMP Thu Jun 23 22:45:46 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.0.0-rc4-686-pae root=UUID=d9369caf-8b2a-42b1-8d26-ffbc2ddafc8f ro quiet init=/bin/systemd ** Tainted: D (128) * Kernel has oopsed before. ** Kernel log: [ 69.836079] NetworkManager[1669]: keyfile: read connection 'Auto Sitecom87aa20' [ 69.836087] NetworkManager[1669]: keyfile: parsing Auto VOO-040518 ... [ 69.853486] NetworkManager[1669]: keyfile: read connection 'Auto VOO-040518' [ 69.853495] NetworkManager[1669]: keyfile: parsing Auto ake coucou,reseau non securiser ... [ 69.854488] NetworkManager[1669]: keyfile: read connection 'Auto ake coucou,reseau non securiser' [ 69.855533] NetworkManager[1669]: Ifupdown: get unmanaged devices count: 0 [ 69.856096] NetworkManager[1669]: info trying to start the modem manager... [ 69.857736] dbus[1645]: [system] Activating service name='org.freedesktop.ModemManager' (using servicehelper) [ 69.861844] modem-manager[1685]: info ModemManager (version 0.4.997) starting... [ 69.862713] dbus[1645]: [system] Activating service name='org.freedesktop.PolicyKit1' (using servicehelper) [ 69.864155] dbus[1645]: [system] Successfully activated service 'org.freedesktop.ModemManager' [ 69.864908] modem-manager[1685]: info Loaded plugin Longcheer [ 69.865076] modem-manager[1685]: info Loaded plugin X22X [ 69.865228] modem-manager[1685]: info Loaded plugin Gobi [ 69.865406] modem-manager[1685]: info Loaded plugin Sierra [ 69.865559] modem-manager[1685]: info Loaded plugin AnyData [ 69.865763] modem-manager[1685]: info Loaded plugin SimTech [ 69.865889] modem-manager[1685]: info Loaded plugin ZTE [ 69.866061] modem-manager[1685]: info Loaded plugin Samsung [ 69.866249] modem-manager[1685]: info Loaded plugin Option High-Speed [ 69.866423] modem-manager[1685]: info Loaded plugin Huawei [ 69.866599] modem-manager[1685]: info Loaded plugin Novatel [ 69.866765] modem-manager[1685]: info Loaded plugin MotoC [ 69.866932] modem-manager[1685]: info Loaded plugin Ericsson MBM [ 69.867102] modem-manager[1685]: info Loaded plugin Nokia [ 69.867268] modem-manager[1685]: info Loaded plugin Option [ 69.867440] modem-manager[1685]: info Loaded plugin Linktop [ 69.867604] modem-manager[1685]: info Loaded plugin Generic [ 69.867782] modem-manager[1685]: info Loaded plugin Wavecom [ 69.938795] polkitd[1688]: started daemon version 0.101 using authority implementation `local' version `0.101' [ 69.939474] dbus[1645]: [system] Successfully activated service 'org.freedesktop.PolicyKit1' [ 69.942827] NetworkManager[1669]: info monitoring kernel firmware directory '/lib/firmware'. [ 69.943467] NetworkManager[1669]: info found WiFi radio killswitch rfkill0 (at /sys/devices/pci:00/:00:1c.1/:03:00.0/ieee80211/phy0/rfkill0) (driver (unknown)) [ 69.945176] NetworkManager[1669]: info WiFi enabled by radio killswitch; enabled by state file [ 69.945209] NetworkManager[1669]: info WWAN enabled by radio killswitch; enabled by state file [ 69.945217] NetworkManager[1669]: info WiMAX enabled by radio killswitch; enabled by state file [ 69.945248] NetworkManager[1669]: info Networking is enabled by state file [ 69.946207] NetworkManager[1669]: info (wlan0): driver supports SSID scans (scan_capa 0x01). [ 69.946355] NetworkManager[1669]: info (wlan0): new 802.11 WiFi device (driver: 'iwlagn' ifindex: 3) [ 69.946398] NetworkManager[1669]: info (wlan0): exported as
Bug#629428: marked as done (linux-image-2.6.32-5-686: rtl818x broken for RTL-8185 IEEE 802.11a/b/g)
Your message dated Sat, 6 Jul 2013 17:58:15 +0200 with message-id 20130706155815.GB12523@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #629428, regarding linux-image-2.6.32-5-686: rtl818x broken for RTL-8185 IEEE 802.11a/b/g 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 ow...@bugs.debian.org immediately.) -- 629428: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629428 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-34squeeze1 Severity: normal The card is identified correctly, but never manages to associate with an AP. The card is a generic rtl8185 cannibalised out of a Maplin HTC PC bundle. Dmesg self-explanatory. Unfortunately the web site on sourceforge seems a bit blank so I cannot pick up a more recent driver to test build to see if this can be fixed. -- Package-specific info: ** Version: Linux version 2.6.32-5-686 (Debian 2.6.32-34squeeze1) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Wed May 18 07:08:50 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-686 root=UUID=ddf5a907-47ff-4167-adc8-f00fd59ed1f8 ro acpi_enforce_resources=lax quiet ** Not tainted ** Kernel log: [2.646116] uhci_hcd :00:10.3: PCI INT B - Link[ALKB] - GSI 21 (level, low) - IRQ 21 [2.646134] uhci_hcd :00:10.3: setting latency timer to 64 [2.646141] uhci_hcd :00:10.3: UHCI Host Controller [2.646160] uhci_hcd :00:10.3: new USB bus registered, assigned bus number 5 [2.646199] uhci_hcd :00:10.3: irq 21, io base 0xf400 [2.646281] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001 [2.646289] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [2.646295] usb usb5: Product: UHCI Host Controller [2.646300] usb usb5: Manufacturer: Linux 2.6.32-5-686 uhci_hcd [2.646306] usb usb5: SerialNumber: :00:10.3 [2.646640] usb usb5: configuration #1 chosen from 1 choice [2.647236] hub 5-0:1.0: USB hub found [2.647276] hub 5-0:1.0: 2 ports detected [2.824026] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [2.988236] ata2.00: ATA-7: Maxtor 6Y080M0, YAR511W0, max UDMA/100 [2.988245] ata2.00: 156301488 sectors, multi 16: LBA48 [3.004253] ata2.00: configured for UDMA/100 [3.004477] scsi 1:0:0:0: Direct-Access ATA Maxtor 6Y080M0 YAR5 PQ: 0 ANSI: 5 [3.303701] sd 1:0:0:0: [sda] 156301488 512-byte logical blocks: (80.0 GB/74.5 GiB) [3.303789] sd 1:0:0:0: [sda] Write Protect is off [3.303796] sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00 [3.303832] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [3.304151] sda: sda1 sda2 [3.326469] sd 1:0:0:0: [sda] Attached SCSI disk [3.599716] PM: Starting manual resume from disk [3.599727] PM: Resume from partition 8:1 [3.599732] PM: Checking hibernation image. [3.600083] PM: Error -22 checking image file [3.600087] PM: Resume from disk failed. [3.674961] kjournald starting. Commit interval 5 seconds [3.674984] EXT3-fs: mounted filesystem with ordered data mode. [5.254134] udev[309]: starting version 164 [5.907667] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 [5.936574] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0 [5.936593] ACPI: Power Button [PWRB] [5.936735] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1 [5.936752] ACPI: Sleep Button [SLPB] [5.936915] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 [5.936925] ACPI: Power Button [PWRF] [6.076088] processor LNXCPU:00: registered as cooling_device0 [6.113043] input: PC Speaker as /devices/platform/pcspkr/input/input3 [6.197120] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [6.261327] parport_pc 00:0a: reported by Plug and Play ACPI [6.261383] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE] [6.458051] cfg80211: Using static regulatory domain info [6.458058] cfg80211: Regulatory domain: US [6.458064] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [6.458072] (2402000 KHz - 2472000 KHz @ 4 KHz), (600 mBi, 2700 mBm) [6.458079] (517 KHz - 519 KHz @ 4 KHz), (600 mBi, 2300 mBm) [6.458087] (519 KHz - 521 KHz @ 4 KHz), (600 mBi, 2300 mBm) [6.458095] (521 KHz - 523 KHz @ 4 KHz), (600 mBi, 2300 mBm) [6.458102] (523 KHz - 533 KHz @ 4 KHz), (600 mBi, 2300 mBm) [6.458110] (5735000
Bug#641221: marked as done (Debian Squeeze problem with firewire_core (DV camera over FireWire))
Your message dated Sat, 6 Jul 2013 17:58:37 +0200 with message-id 20130706155837.GC12523@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #641221, regarding Debian Squeeze problem with firewire_core (DV camera over FireWire) 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 ow...@bugs.debian.org immediately.) -- 641221: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641221 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: firewire_core Hello Ladies and Gentlemen, It seems, that one can't help anymore: http://www.linux-archive.org/debian-user/573831-debian-squeeze-problem-firewire_core-dv-camera-over-firewire.html Is this the right address? Any ideas concerning this problem? Thank you in advance, regards, matpro_fhko...@lavabit.com ---End Message--- ---BeginMessage--- Hi, your bug has been filed against the linux-2.6 source package and was filed for a kernel older than the recently released Debian 7.x / Wheezy with a severity less than important. We don't have the ressources to reproduce the complete backlog of all older kernel bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy or a more recent kernel from testing or unstable, please reopen the bug by sending a mail to cont...@bugs.debian.org with the following three commands included in the mail: reopen BUGNUMBER reassign BUGNUMBER src:linux thanks Cheers, Moritz---End Message---
Bug#639780: marked as done (linux-image-3.0.0-1-amd64: Regression in automatic audio output switching on ASUS G72-GX laptop)
Your message dated Sat, 6 Jul 2013 17:58:37 +0200 with message-id 20130706155837.GC12523@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #639780, regarding linux-image-3.0.0-1-amd64: Regression in automatic audio output switching on ASUS G72-GX laptop 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 ow...@bugs.debian.org immediately.) -- 639780: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639780 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 3.0.0-3 Severity: normal Tags: wheezy I'm using ASUS G72-GX series laptop with debian testing and since following transition: [UPGRADE] linux-image-2.6-amd64 2.6.39+35.1 - 3.0.0+39 experience regression: 1. Boot up into default gnome shell (very little modifications, using default ALSA output) 2. Run some audiofile to ensure that playback is running 3. Plug in headphone jack into laptop Result: Audio is directed to both in-built speakers and headphones Expected: Audio from in-built speakers should be redirected to headphones Several notes: External mic properly mutes in-built one on current kernel version Currently available list of options which control audio: Headphone1 checked Headphone2 checked IEC958 not checked IEC958 Default PCM checked I tried to play with them and volume sliders. kernel doesn't expose even manual control over output device muting (as it used to do long time ago in 2.6 kernel series, switching to automatic mode like i described few months before the upgrade to 3.0) -- Package-specific info: ** Version: Linux version 3.0.0-1-amd64 (Debian 3.0.0-3) (b...@decadent.org.uk) (gcc version 4.5.3 (Debian 4.5.3-8) ) #1 SMP Sat Aug 27 16:21:11 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.0.0-1-amd64 root=UUID=6640fac2-a75d-4893-9107-5b593eb206de ro quiet nouveau.modeset=0 ** Tainted: PO (4097) * Proprietary module has been loaded. * Out-of-tree module has been loaded. ** Kernel log: [4.910294] PM: Hibernation image not present or could not be loaded. [4.963380] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [6.903858] udevd[310]: starting version 172 [7.694325] ACPI: acpi_idle registered with cpuidle [7.864938] acpi device:05: registered as cooling_device4 [7.865018] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:01/LNXVIDEO:00/input/input3 [7.865025] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) [7.882424] input: Lid Switch as /devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input4 [7.882462] ACPI: Lid Switch [LID] [7.882516] input: Sleep Button as /devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input5 [7.882523] ACPI: Sleep Button [SLPB] [7.882573] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input6 [7.882577] ACPI: Power Button [PWRB] [7.882633] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input7 [7.882637] ACPI: Power Button [PWRF] [7.888379] ACPI: AC Adapter [AC0] (on-line) [7.925932] input: PC Speaker as /devices/platform/pcspkr/input/input8 [7.960342] r592 :09:01.2: PCI INT B - GSI 17 (level, low) - IRQ 17 [7.960432] r592: driver successfully loaded [8.065290] i801_smbus :00:1f.3: PCI INT C - GSI 18 (level, low) - IRQ 18 [8.563674] Bluetooth: Core ver 2.16 [8.563706] NET: Registered protocol family 31 [8.563708] Bluetooth: HCI device and connection manager initialized [8.563711] Bluetooth: HCI socket layer initialized [8.563713] Bluetooth: L2CAP socket layer initialized [8.563915] Bluetooth: SCO socket layer initialized [8.625443] Bluetooth: Generic Bluetooth USB driver ver 0.6 [8.625614] usbcore: registered new interface driver btusb [8.878890] Disabling lock debugging due to kernel taint [8.878898] nvidia: module license 'NVIDIA' taints kernel. [9.052764] ACPI: Battery Slot [BAT0] (battery present) [9.086384] asus_laptop: Asus Laptop Support version 0.42 [9.086461] asus_laptop: Error calling BSTS [9.086479] asus_laptop: G72GX model detected [9.095909] asus_laptop: Backlight controlled by ACPI video driver [9.095969] input: Asus Laptop extra buttons as /devices/platform/asus_laptop/input/input9 [9.096105] Registered led device: asus::mail [9.096130] Registered led device: asus::touchpad [9.096428] Registered led device: asus::kbd_backlight [9.294297] r852 :09:01.3: PCI INT B - GSI 17 (level, low) - IRQ 17 [9.294364] r852: driver loaded successfully [9.320917] cfg80211: Calling CRDA to
Bug#649097: marked as done (linux-image-2.6.32-5-amd64: psmouse.ko module fails to handle PS/2 mouse)
Your message dated Sat, 6 Jul 2013 17:59:20 +0200 with message-id 20130706155920.GD12523@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #649097, regarding linux-image-2.6.32-5-amd64: psmouse.ko module fails to handle PS/2 mouse 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 ow...@bugs.debian.org immediately.) -- 649097: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649097 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-38 Severity: grave Justification: renders package unusable I'v been expericing PS/2 mouse bud in Xorg almost year. I upgareded kernel to 2.6.39 hoping it would solve the problem. However, it turns out the erractic mouse synchronization error still exists. In 2.6.32, psmouse.ko generated flooding messages like below. 2.6.39 module does once or twice when it detects the lost of synchronization. Below is the messages. [quote] Nov 16 15:13:19 theblue kernel: [275921.510266] psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away. Nov 16 22:43:26 theblue kernel: [293066.497048] psmouse.c: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. [/quote] When it happen, window managers of Xorg takes up CPU instantly while loosing mouse focus stop using Xorg, force to shut down Xorg in a termial. I tested on fluxbox which is my main window manager, tried openbox too. Here is a link I posted. http://forums.debian.net/viewtopic.php?f=6t=71950 The solution I found was to replace the PS/2 mouse with a USB mouse. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: Acer product_name: Aspire M1200 product_version: chassis_vendor: Acer chassis_version: 1.0 bios_vendor: American Megatrends Inc. bios_version: R03-B3 board_vendor: Acer board_name: RS740DVF board_version: ** PCI devices: 00:00.0 Host bridge [0600]: ATI Technologies Inc RS690 Host Bridge [1002:7911] Subsystem: Acer Incorporated [ALI] Device [1025:0155] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort+ SERR- PERR- INTx- Latency: 0 00:01.0 PCI bridge [0604]: ATI Technologies Inc RS690 PCI to PCI Bridge (Internal gfx) [1002:7912] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 64 Bus: primary=00, secondary=01, subordinate=01, sec-latency=64 I/O behind bridge: c000-cfff Memory behind bridge: fe70-fe8f Prefetchable memory behind bridge: d000-dfff Secondary status: 66MHz+ FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- BridgeCtl: Parity- SERR+ NoISA- VGA+ MAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: access denied 00:05.0 PCI bridge [0604]: ATI Technologies Inc RS690 PCI to PCI Bridge (PCI Express Port 1) [1002:7915] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 I/O behind bridge: d000-dfff Memory behind bridge: fe90-fe9f Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- BridgeCtl: Parity+ SERR+ NoISA- VGA- MAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: access denied Kernel driver in use: pcieport 00:06.0 PCI bridge [0604]: ATI Technologies Inc RS690 PCI to PCI Bridge (PCI Express Port 2) [1002:7916] (prog-if 00 [Normal decode]) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Bus: primary=00, secondary=03, subordinate=03, sec-latency=0 Memory behind bridge: fea0-feaf Secondary status: 66MHz- FastB2B-
Bug#648088: marked as done (rt2x00lib: Kernel Oops rt2x00queue_init_queues [rt2x00lib] of Linux 2.6.32-5-686 Debian 6.0.3)
Your message dated Sat, 6 Jul 2013 17:59:20 +0200 with message-id 20130706155920.GD12523@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #648088, regarding rt2x00lib: Kernel Oops rt2x00queue_init_queues [rt2x00lib] of Linux 2.6.32-5-686 Debian 6.0.3 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 ow...@bugs.debian.org immediately.) -- 648088: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648088 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-38 Severity: normal File: rt2x00lib Kernel Oops if I am trying to use the wireless D-link pci card. I am removing manually the packages firmware-ralink to avoid the card to be initialized and generate the related Oops. -- Package-specific info: ** Version: Linux version 2.6.32-5-686 (Debian 2.6.32-38) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Mon Oct 3 04:15:24 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-686 root=UUID=c65d3d24-40b5-4fda-b5ad-53c147e8a6ad ro single ** Not tainted ** Kernel log: Nov 7 10:22:28 DIM5000 kernel: [ 330.956522] phy0 - rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x2100, value=0x Nov 7 10:22:28 DIM5000 kernel: [ 330.958532] BUG: unable to handle kernel NULL pointer dereference at (null) Nov 7 10:22:28 DIM5000 kernel: [ 330.960003] IP: [f83a9a44] rt2x00queue_init_queues+0x1f/0x59 [rt2x00lib] Nov 7 10:22:28 DIM5000 kernel: [ 330.960003] *pde = Nov 7 10:22:28 DIM5000 kernel: [ 330.960003] Oops: 0002 [#1] SMP Nov 7 10:22:28 DIM5000 kernel: [ 330.960003] last sysfs file: /sys/devices/virtual/net/lo/type Nov 7 10:22:28 DIM5000 kernel: [ 330.960003] Modules linked in: binfmt_misc btrfs zlib_deflate crc32c libcrc32c ufs qnx4 hfsplus hfs minix ntfs vfat msdos fat jfs xfs exportfs reiserfs ext4 jbd2 crc16 ext2 fuse loop usblp usbhid hid arc4 ecb snd_intel8x0 rt61pci crc_itu_t b44 snd_ac97_codec i915 ac97_bus rt2x00pci ssb snd_pcm rt2x00lib mmc_core drm_kms_helper sg snd_seq led_class uhci_hcd ehci_hcd drm pcmcia pcmcia_core i2c_algo_bit sr_mod usbcore dcdbas snd_timer mac80211 i2c_i801 mii snd_seq_device video cfg80211 rfkill parport_pc pcspkr parport snd eeprom_93cx6 nls_base cdrom processor output rng_core i2c_core evdev button soundcore snd_page_alloc psmouse serio_raw ext3 jbd mbcache sd_mod crc_t10dif ata_generic ata_piix libata thermal thermal_sys scsi_mod Nov 7 10:22:28 DIM5000 kernel: [ 330.960003] Nov 7 10:22:28 DIM5000 kernel: [ 330.960003] Pid: 1998, comm: wpa_supplicant Not tainted (2.6.32-5-686 #1) Dimension 5000 Nov 7 10:22:28 DIM5000 kernel: [ 330.960003] EIP: 0060:[f83a9a44] EFLAGS: 00210202 CPU: 0 Nov 7 10:22:28 DIM5000 kernel: [ 330.960003] EIP is at rt2x00queue_init_queues+0x1f/0x59 [rt2x00lib] Nov 7 10:22:28 DIM5000 kernel: [ 330.960003] EAX: EBX: ef614c00 ECX: EDX: Nov 7 10:22:28 DIM5000 kernel: [ 330.960003] ESI: 0001 EDI: ef4f3a40 EBP: ef48cba0 ESP: f6553e30 Nov 7 10:22:28 DIM5000 kernel: [ 330.960003] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 Nov 7 10:22:28 DIM5000 kernel: [ 330.960003] Process wpa_supplicant (pid: 1998, ti=f6552000 task=ef63a640 task.ti=f6552000) Nov 7 10:22:28 DIM5000 kernel: [ 330.960003] Stack: Nov 7 10:22:28 DIM5000 kernel: [ 330.960003] ef4f3a40 ef4f3bb4 f83a89ed ef4f3a40 f83a8af4 ef48c800 Nov 7 10:22:28 DIM5000 kernel: [ 330.960003] 0 ef4f3260 f80bc8e8 ef48c800 ef4f3814 ef48c800 000d Nov 7 10:22:28 DIM5000 kernel: [ 330.960003] 0 ef48c800 1003 ef48c800 ef48c830 f80ca9c8 0001 c11daefd Nov 7 10:22:28 DIM5000 kernel: [ 330.960003] Call Trace: Nov 7 10:22:28 DIM5000 kernel: [ 330.960003] [f83a89ed] ? rt2x00lib_stop+0x4f/0xb4 [rt2x00lib] Nov 7 10:22:28 DIM5000 kernel: [ 330.960003] [f83a8af4] ? rt2x00lib_start+0xa2/0xaa [rt2x00lib] Nov 7 10:22:28 DIM5000 kernel: [ 330.960003] [f80bc8e8] ? ieee80211_open+0x232/0x585 [mac80211] Nov 7 10:22:28 DIM5000 kernel: [ 330.960003] [c11daefd] ? dev_open+0x90/0xcc Nov 7 10:22:28 DIM5000 kernel: [ 330.960003] [c11da7c7] ? dev_change_flags+0xa2/0x153 Nov 7 10:22:28 DIM5000 kernel: [ 330.960003] [c1219493] ? devinet_ioctl+0x236/0x4cb Nov 7 10:22:28 DIM5000 kernel: [ 330.960003] [c11ccbe1] ? sock_ioctl+0x1c9/0x1ee Nov 7 10:22:28 DIM5000 kernel: [ 330.960003] [c11cca18] ? sock_ioctl+0x0/0x1ee Nov 7 10:22:28 DIM5000 kernel: [ 330.960003] [c10bdce0] ? vfs_ioctl+0x1c/0x5f Nov 7 10:22:28 DIM5000 kernel: [ 330.960003] [c10be274] ?
Bug#649198: marked as done (linux-image-2.6.32-5-amd64: Kernel Oops on try to use an USB CD drive that was powered off)
Your message dated Sat, 6 Jul 2013 17:59:20 +0200 with message-id 20130706155920.GD12523@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #649198, regarding linux-image-2.6.32-5-amd64: Kernel Oops on try to use an USB CD drive that was powered off 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 ow...@bugs.debian.org immediately.) -- 649198: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649198 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-35 Severity: normal I experienced a kernel Oops at three occasions when i switched off a USB CD drive while it was in use by an application. It first happened with qemu (stress test), then with blkid (gnawing on medium with LEC uncorrectable error), and now with my own application (deliberately provoked). I opened a file descriptor on /dev/sr2 by $ xorriso -outdev /dev/sr2 -dialog on waited for the dialog prompt and switched off the drive's power. Logged by this line [ 215.717297] usb 1-3: USB disconnect, address 5 Some seconds later i let xorriso attempt an ioctl(SG_IO) transaction, by entering to the xorriso command prompt: -toc The reaction on the xorriso terminal is quite immediately: Killed Message from syslogd@debian2 at Nov 18 18:59:41 ... kernel:[ 231.149073] Oops: 0011 [#1] SMP and some of the lines which appear in the kernel log below. (Not all. They appear randomly picked.) The system seems still running well now. The drive re-appeared as /dev/sr3 when i switched it on again. /dev/sr2 does not exist any more. The first power off [ 137.749886] usb 1-3: USB disconnect, address 3 was made when no userspace application had a file descriptor open. No Oops happened and the drive re-appeared under its old device file address /dev/sr2. (I have switched off USB drives on older Linux kernels in the past. Including the one of Debian 5. There never happened an Oops. Sometimes /dev/sr numbers were not re-used.) -- Package-specific info: ** Version: Linux version 2.6.32-5-amd64 (Debian 2.6.32-35) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Tue Jun 14 09:42:28 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-amd64 root=UUID=e3378181-54dc-4fe3-97e2-d7f2b6c1d296 ro quiet ** Tainted: D (128) * Kernel has oopsed before. ** Kernel log: [ 15.745638] Bluetooth: HCI socket layer initialized [ 15.839019] Bluetooth: L2CAP ver 2.14 [ 15.839021] Bluetooth: L2CAP socket layer initialized [ 15.854583] Bluetooth: RFCOMM TTY layer initialized [ 15.854588] Bluetooth: RFCOMM socket layer initialized [ 15.854590] Bluetooth: RFCOMM ver 1.11 [ 15.966296] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.966299] Bluetooth: BNEP filters: protocol multicast [ 15.981540] Bridge firewalling registered [ 16.446574] Bluetooth: SCO (Voice Link) ver 0.6 [ 16.446577] Bluetooth: SCO socket layer initialized [ 17.026555] lp0: using parport0 (interrupt-driven). [ 17.064563] ppdev: user-space parallel port driver [ 20.402265] powernow-k8: Found 1 AMD Athlon(tm) II X4 620 Processor processors (4 cpu cores) (version 2.20.00) [ 20.402310] powernow-k8:0 : pstate 0 (2600 MHz) [ 20.402311] powernow-k8:1 : pstate 1 (1900 MHz) [ 20.402313] powernow-k8:2 : pstate 2 (1400 MHz) [ 20.402314] powernow-k8:3 : pstate 3 (800 MHz) [ 20.640051] eth0: no IPv6 routers present [ 137.749886] usb 1-3: USB disconnect, address 3 [ 160.256082] usb 1-3: new high speed USB device using ehci_hcd and address 5 [ 160.390473] usb 1-3: New USB device found, idVendor=152d, idProduct=2336 [ 160.390482] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=5 [ 160.390489] usb 1-3: Product: JM20336 SATA, USB Combo [ 160.390494] usb 1-3: Manufacturer: JMicron [ 160.390498] usb 1-3: SerialNumber: 306663601043 [ 160.390699] usb 1-3: configuration #1 chosen from 1 choice [ 160.391820] scsi9 : SCSI emulation for USB Mass Storage devices [ 160.392007] usb-storage: device found at 5 [ 160.392011] usb-storage: waiting for device to settle before scanning [ 165.392426] usb-storage: device scan complete [ 165.397853] scsi 9:0:0:0: CD-ROMOptiarc BD RW BD-5300S 1.04 PQ: 0 ANSI: 0 [ 165.433854] sr2: scsi3-mmc drive: 5x/48x writer dvd-ram cd/rw xa/form2 cdda tray [ 165.434123] sr 9:0:0:0: Attached scsi CD-ROM sr2 [ 165.434266] sr 9:0:0:0: Attached scsi generic sg3 type 5 [ 215.717297] usb 1-3: USB disconnect, address 5 [ 231.149032] kernel tried to execute NX-protected page - exploit attempt? (uid: 1000) [ 231.149041] BUG: unable to handle kernel
Bug#649406: marked as done (usb-storage: System freezes after attaching Huawei E156g usb modem)
Your message dated Sat, 6 Jul 2013 17:59:20 +0200 with message-id 20130706155920.GD12523@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #649406, regarding usb-storage: System freezes after attaching Huawei E156g usb modem 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 ow...@bugs.debian.org immediately.) -- 649406: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649406 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 3.1.1-1 File: usb-storage Severity: important Connecting a Huawei E156g completely freezes my system for 5-7 seconds every 10-15 seconds. I've had to remove usb-storage module to get it to work. The problem appeared when I switched to 3.1.0-1 kernel from 2.6.32-5. -- Package-specific info: ** Version: Linux version 3.1.0-1-amd64 (Debian 3.1.1-1) (b...@decadent.org.uk) (gcc version 4.6.2 (Debian 4.6.2-4) ) #1 SMP Mon Nov 14 08:02:25 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.1.0-1-amd64 root=UUID=1c1e57ee-69c1-45e3-a67f-93b994d55a49 ro quiet ** Tainted: WO (4608) * Taint on warning. * Out-of-tree module has been loaded. ** Kernel log: [ 4424.484120] usb 1-5: new high speed USB device number 9 using ehci_hcd [ 4424.627486] usb 1-5: New USB device found, idVendor=12d1, idProduct=1003 [ 4424.627496] usb 1-5: New USB device strings: Mfr=2, Product=1, SerialNumber=0 [ 4424.627503] usb 1-5: Product: HUAWEI Mobile [ 4424.627509] usb 1-5: Manufacturer: HUAWEI Technology [ 4424.631650] scsi17 : usb-storage 1-5:1.0 [ 4424.632957] usb 1-5: USB disconnect, device number 9 [ 4432.004088] usb 1-5: new high speed USB device number 10 using ehci_hcd [ 4432.147614] usb 1-5: New USB device found, idVendor=12d1, idProduct=1003 [ 4432.147624] usb 1-5: New USB device strings: Mfr=2, Product=1, SerialNumber=0 [ 4432.147632] usb 1-5: Product: HUAWEI Mobile [ 4432.147637] usb 1-5: Manufacturer: HUAWEI Technology [ 4432.152255] option 1-5:1.0: GSM modem (1-port) converter detected [ 4432.153466] usb 1-5: GSM modem (1-port) converter now attached to ttyUSB0 [ 4432.153790] option 1-5:1.1: GSM modem (1-port) converter detected [ 4432.154014] usb 1-5: GSM modem (1-port) converter now attached to ttyUSB1 [ 4432.154779] scsi20 : usb-storage 1-5:1.2 [ 4432.156943] scsi21 : usb-storage 1-5:1.3 [ 4433.155603] scsi 20:0:0:0: CD-ROMHUAWEI Mass Storage 2.31 PQ: 0 ANSI: 2 [ 4433.155697] scsi: killing requests for dead queue [ 4433.155768] scsi: killing requests for dead queue [ 4433.155826] scsi: killing requests for dead queue [ 4433.155883] scsi: killing requests for dead queue [ 4433.155938] scsi: killing requests for dead queue [ 4433.155994] scsi: killing requests for dead queue [ 4433.156228] scsi: killing requests for dead queue [ 4433.156285] scsi: killing requests for dead queue [ 4433.163238] scsi 21:0:0:0: Direct-Access HUAWEI MMC Storage 2.31 PQ: 0 ANSI: 2 [ 4433.163322] scsi: killing requests for dead queue [ 4433.163414] scsi: killing requests for dead queue [ 4433.163499] scsi: killing requests for dead queue [ 4433.163581] scsi: killing requests for dead queue [ 4433.163676] scsi: killing requests for dead queue [ 4433.163760] scsi: killing requests for dead queue [ 4433.163844] scsi: killing requests for dead queue [ 4433.163918] scsi: killing requests for dead queue [ 4433.166590] sr0: scsi-1 drive [ 4433.166839] sr 20:0:0:0: Attached scsi CD-ROM sr0 [ 4433.167026] sr 20:0:0:0: Attached scsi generic sg1 type 5 [ 4433.167428] sd 21:0:0:0: Attached scsi generic sg2 type 0 [ 4433.176599] sd 21:0:0:0: [sdb] Attached SCSI removable disk [ 4443.000292] option: option_instat_callback: error -108 [ 4443.000582] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0 [ 4443.000634] option 1-5:1.0: device disconnected [ 4447.373546] usb 1-5: USB disconnect, device number 10 [ 4447.380844] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1 [ 4447.380877] option 1-5:1.1: device disconnected [ 4447.384627] scsi: killing requests for dead queue [ 4447.389877] scsi: killing requests for dead queue [ 4464.732112] usb 1-7: new high speed USB device number 11 using ehci_hcd [ 4464.875368] usb 1-7: New USB device found, idVendor=12d1, idProduct=1003 [ 4464.875379] usb 1-7: New USB device strings: Mfr=2, Product=1, SerialNumber=0 [ 4464.875386] usb 1-7: Product: HUAWEI Mobile [ 4464.875391] usb 1-7: Manufacturer: HUAWEI Technology [ 4464.879552] scsi22 : usb-storage 1-7:1.0 [ 4464.880166] usb 1-7: USB disconnect, device number 11 [ 4472.256164] usb 1-7: new high speed USB device number 12 using
Bug#652475: marked as done (linux-image-3.1.0-1-amd64: USB autosuspend goes crazy filling the log files)
Your message dated Sat, 6 Jul 2013 17:59:20 +0200 with message-id 20130706155920.GD12523@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #652475, regarding linux-image-3.1.0-1-amd64: USB autosuspend goes crazy filling the log files 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 ow...@bugs.debian.org immediately.) -- 652475: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652475 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 3.1.1-1 Severity: normal Hi there! There is a problem somewhere with USB autosuspending on my ThinkPad X60. When enabled through powertop, the kernel splits out messages different times every seconds, thus filling the log files: = $ ls -lh /var/log/debug* /var/log/kern.log* /var/log/messages* /var/log/syslog* -rw-r- 1 root adm 302M Dec 15 21:25 /var/log/debug -rw-r- 1 root adm 157K Nov 25 15:05 /var/log/debug.1 -rw-r- 1 root adm 90 Nov 15 13:35 /var/log/debug.2.gz -rw-r- 1 root adm 1.5M Oct 29 22:32 /var/log/debug.3.gz -rw-r- 1 root adm 63 Oct 23 11:16 /var/log/debug.4.gz -rw-r- 1 root adm 697M Dec 15 21:25 /var/log/kern.log -rw-r- 1 root adm 601K Nov 25 18:00 /var/log/kern.log.1 -rw-r- 1 root adm 96 Nov 11 10:07 /var/log/kern.log.2.gz -rw-r- 1 root adm 227 Oct 31 18:14 /var/log/kern.log.3.gz -rw-r- 1 root adm 3.4M Oct 30 03:06 /var/log/kern.log.4.gz -rw-r- 1 root adm 395M Dec 15 21:25 /var/log/messages -rw-r- 1 root adm 844 Nov 27 06:25 /var/log/messages.1 -rw-r- 1 root adm 68K Nov 26 06:25 /var/log/messages.2.gz -rw-r- 1 root adm 512 Nov 13 06:25 /var/log/messages.3.gz -rw-r- 1 root adm 843 Nov 6 06:25 /var/log/messages.4.gz -rw-r- 1 root adm 698M Dec 15 21:25 /var/log/syslog -rw-r- 1 root adm 58K Nov 27 06:25 /var/log/syslog.1 -rw-r- 1 root adm 137K Nov 26 06:25 /var/log/syslog.2.gz -rw-r- 1 root adm 6.2K Nov 19 06:25 /var/log/syslog.3.gz -rw-r- 1 root adm 47K Nov 18 06:25 /var/log/syslog.4.gz -rw-r- 1 root adm 2.0K Nov 16 06:25 /var/log/syslog.5.gz -rw-r- 1 root adm 7.1K Nov 15 06:25 /var/log/syslog.6.gz -rw-r- 1 root adm 16K Nov 14 06:25 /var/log/syslog.7.gz $ cd /var/log $ for I in debug kern.log messages syslog; do \ cat $I | grep -v _hcd /home/luca/$I_20111215-USB-autosuspend.bug.grep-v_hcd; \ done $ for I in debug kern.log messages syslog; do \ ls -lh /var/log/$I /home/luca/$I_20111215-USB-autosuspend.bug.grep-v_hcd; \ done -rw-r--r-- 1 root root 352K Dec 15 21:49 /home/luca/debug_20111215-USB-autosuspend.bug.grep-v_hcd -rw-r- 1 root adm 302M Dec 15 21:25 /var/log/debug -rw-r--r-- 1 root root 1.2M Dec 15 21:50 /home/luca/kern.log_20111215-USB-autosuspend.bug.grep-v_hcd -rw-r- 1 root adm 697M Dec 15 21:25 /var/log/kern.log -rw-r--r-- 1 root root 948K Dec 15 21:50 /home/luca/messages_20111215-USB-autosuspend.bug.grep-v_hcd -rw-r- 1 root adm 395M Dec 15 21:25 /var/log/messages -rw-r--r-- 1 root root 2.7M Dec 15 21:50 /home/luca/syslog_20111215-USB-autosuspend.bug.grep-v_hcd -rw-r- 1 root adm 698M Dec 15 21:25 /var/log/syslog = Obviously, this is not acceptable and there is a problem somewhere. Feel free to ask for more tests, I will upgrade soon to the latest version in unstable (3.1.5-1) and report back the results. Thx, bye, Gismo / Luca -- Package-specific info: ** Version: Linux version 3.1.0-1-amd64 (Debian 3.1.1-1) (b...@decadent.org.uk) (gcc version 4.6.2 (Debian 4.6.2-4) ) #1 SMP Mon Nov 14 08:02:25 UTC 2011 ** Command line: BOOT_IMAGE=/vmlinuz-3.1.0-1-amd64 root=/dev/mapper/gismo-root ro quiet ** Not tainted ** Kernel log: [335534.196062] ehci_hcd :00:1d.7: power state changed by ACPI to D0 [335534.196079] ehci_hcd :00:1d.7: restoring config space at offset 0xf (was 0x400, writing 0x40b) [335534.196104] ehci_hcd :00:1d.7: restoring config space at offset 0x1 (was 0x290, writing 0x2900106) [335534.196181] ehci_hcd :00:1d.7: PME# disabled [335534.196190] ehci_hcd :00:1d.7: setting latency timer to 64 [335534.328130] ehci_hcd :00:1d.7: PME# enabled [335534.344055] ehci_hcd :00:1d.7: power state changed by ACPI to D3 [335534.940977] uhci_hcd :00:1d.2: power state changed by ACPI to D0 [335534.940986] uhci_hcd :00:1d.2: power state changed by ACPI to D0 [335534.941107] uhci_hcd :00:1d.2: setting latency timer to 64 [335535.020366] uhci_hcd :00:1d.1: setting latency timer to 64 [335535.020521] uhci_hcd :00:1d.2: power state changed by ACPI to D3 [335535.100216] uhci_hcd :00:1d.0: power state changed by ACPI to D0
Bug#640665: marked as done (linux-image-2.6.32-5-amd64: USB block device write error with images 4 GB)
Your message dated Sat, 6 Jul 2013 17:58:37 +0200 with message-id 20130706155837.GC12523@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #640665, regarding linux-image-2.6.32-5-amd64: USB block device write error with images 4 GB 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 ow...@bugs.debian.org immediately.) -- 640665: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640665 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-35 Severity: normal I've partitioned a USB stick with parted into two partitions. The first one is set to be slightly larger than an image files which is copied over onto with dd, followed by a bootloader installation into the MBR. Now, this setup works fine for image files up to around 4 GB. Recently, the file has grown to 4329570304 bytes which is slightly larger than this boundary. Suddenly, the dd invocation locks up at around the boundary and the kernel spits out some sort of device blocked for too long panic. The call trace can be found in the log below. Since the system is all amd64, this looks like a strange issue to me. Also, it affects not just one USB stick but even a newly bought one (costly bug reporting...). Just copying the image to another file on an ext4 partition also works without any issues. Here's the command line used for the copy to the device: sudo dd if=foo.img of=/dev/sdb1 bs=1048576 -- Package-specific info: ** Version: Linux version 2.6.32-5-amd64 (Debian 2.6.32-35) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Tue Jun 14 09:42:28 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-amd64 root=UUID=62f16ca4-eb34-479b-8791-2c979a729c1c ro quiet ** Not tainted ** Kernel log: [ 1641.568094] groups: 2 (cpu_power = 589) 3 (cpu_power = 589) [ 1641.568105] domain 1: span 0-3 level MC [ 1641.568110]groups: 2-3 (cpu_power = 1178) 0-1 (cpu_power = 1178) [ 1641.568123] CPU3 attaching sched-domain: [ 1641.568127] domain 0: span 2-3 level SIBLING [ 1641.568132] groups: 3 (cpu_power = 589) 2 (cpu_power = 589) [ 1641.568144] domain 1: span 0-3 level MC [ 1641.568149]groups: 2-3 (cpu_power = 1178) 0-1 (cpu_power = 1178) [ 1641.678982] usb 1-1.4: new full speed USB device using ehci_hcd and address 8 [ 1641.774061] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=217f [ 1641.774064] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 1641.774067] usb 1-1.4: Product: Broadcom Bluetooth Device [ 1641.774068] usb 1-1.4: Manufacturer: Broadcom Corp [ 1641.774069] usb 1-1.4: SerialNumber: 5CAC4CCCA816 [ 1641.774169] usb 1-1.4: configuration #1 chosen from 1 choice [ 4430.050179] usb 1-1.1: new high speed USB device using ehci_hcd and address 9 [ 4430.151155] usb 1-1.1: New USB device found, idVendor=18a5, idProduct=0302 [ 4430.151159] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 4430.151163] usb 1-1.1: Product: STORE N GO [ 4430.151165] usb 1-1.1: Manufacturer: Verbatim [ 4430.151167] usb 1-1.1: SerialNumber: 07B40807497A8A05 [ 4430.151299] usb 1-1.1: configuration #1 chosen from 1 choice [ 4430.151776] scsi7 : SCSI emulation for USB Mass Storage devices [ 4430.151956] usb-storage: device found at 9 [ 4430.151959] usb-storage: waiting for device to settle before scanning [ 4435.150411] usb-storage: device scan complete [ 4435.335136] scsi 7:0:0:0: Direct-Access Verbatim STORE N GO 5.00 PQ: 0 ANSI: 0 CCS [ 4435.335553] sd 7:0:0:0: Attached scsi generic sg2 type 0 [ 4436.038227] sd 7:0:0:0: [sdb] 15645120 512-byte logical blocks: (8.01 GB/7.45 GiB) [ 4436.038865] sd 7:0:0:0: [sdb] Write Protect is off [ 4436.038871] sd 7:0:0:0: [sdb] Mode Sense: 23 00 00 00 [ 4436.038875] sd 7:0:0:0: [sdb] Assuming drive cache: write through [ 4436.042171] sd 7:0:0:0: [sdb] Assuming drive cache: write through [ 4436.042176] sdb: sdb1 [ 4436.071557] sd 7:0:0:0: [sdb] Assuming drive cache: write through [ 4436.071563] sd 7:0:0:0: [sdb] Attached SCSI removable disk [ 4572.598727] e1000e :00:19.0: irq 29 for MSI/MSI-X [ 4572.653595] e1000e :00:19.0: irq 29 for MSI/MSI-X [ 4572.654945] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 4574.227071] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX [ 4574.227074] :00:19.0: eth0: 10/100 speed: disabling TSO [ 4574.229210] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 4585.164741] eth0: no IPv6 routers present [ 5880.800476] INFO: task blkid:4527 blocked for more than 120 seconds. [ 5880.800481] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables
Bug#652484: marked as done (linux-image-3.1.0-1-amd64: kernel oops when USB drive hot unplugged)
Your message dated Sat, 6 Jul 2013 17:59:20 +0200 with message-id 20130706155920.GD12523@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #652484, regarding linux-image-3.1.0-1-amd64: kernel oops when USB drive hot unplugged 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 ow...@bugs.debian.org immediately.) -- 652484: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652484 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 3.1.1-1 Severity: normal I used dd to write an entire 4GB USB flash drive. It was only going at 2MB/s, so I ran it overnight. In the morning, it was done, so I unplugged the USB drive. Immediately there was a kernel oops. The flash drive was plugged into a 7 port USB hub, which was plugged directly into the computer. The USB hub has been pretty flakey, and I don't really trust the flash drive much, either. I have trimmed the Kernel log below. It shows from the moment the drive was plugged in, through the oops. -- Package-specific info: ** Version: Linux version 3.1.0-1-amd64 (Debian 3.1.1-1) (b...@decadent.org.uk) (gcc version 4.6.2 (Debian 4.6.2-4) ) #1 SMP Mon Nov 14 08:02:25 UTC 2011 ** Command line: BOOT_IMAGE=/vmlinuz-3.1.0-1-amd64 root=/dev/mapper/hda4_crypt ro single ** Tainted: D (128) * Kernel has oopsed before. ** Kernel log: [800414.804508] usb 1-2.2: new high speed USB device number 22 using ehci_hcd [800415.050087] usb 1-2.2: New USB device found, idVendor=090c, idProduct=1000 [800415.050092] usb 1-2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [800415.050095] usb 1-2.2: SerialNumber: AA010474 [800415.050475] scsi16 : usb-storage 1-2.2:1.0 [800416.239552] scsi 16:0:0:0: Direct-Access 1100 PQ: 0 ANSI: 0 CCS [800416.239623] scsi: killing requests for dead queue [800416.239665] scsi: killing requests for dead queue [800416.239704] scsi: killing requests for dead queue [800416.239738] scsi: killing requests for dead queue [800416.239769] scsi: killing requests for dead queue [800416.239801] scsi: killing requests for dead queue [800416.239831] scsi: killing requests for dead queue [800416.239862] scsi: killing requests for dead queue [800416.240393] sd 16:0:0:0: Attached scsi generic sg10 type 0 [800416.241178] sd 16:0:0:0: [sdj] 7913472 512-byte logical blocks: (4.05 GB/3.77 GiB) [800416.242053] sd 16:0:0:0: [sdj] Write Protect is off [800416.242060] sd 16:0:0:0: [sdj] Mode Sense: 43 00 00 00 [800416.243914] sd 16:0:0:0: [sdj] No Caching mode page present [800416.243919] sd 16:0:0:0: [sdj] Assuming drive cache: write through [800416.247663] sd 16:0:0:0: [sdj] No Caching mode page present [800416.247667] sd 16:0:0:0: [sdj] Assuming drive cache: write through [800416.248797] sdj: [800416.251418] sd 16:0:0:0: [sdj] No Caching mode page present [800416.251423] sd 16:0:0:0: [sdj] Assuming drive cache: write through [800416.251426] sd 16:0:0:0: [sdj] Attached SCSI removable disk [834006.038021] usb 1-2.2: USB disconnect, device number 22 [834006.038712] scsi: killing requests for dead queue [834006.039764] BUG: unable to handle kernel NULL pointer dereference at 0008 [834006.039891] IP: [a0069792] sd_revalidate_disk+0x33/0x1603 [sd_mod] [834006.03] PGD b69dd067 PUD c0968067 PMD 0 [834006.040066] Oops: [#1] SMP [834006.040118] CPU 0 [834006.040149] Modules linked in: nls_iso8859_1 nls_cp437 vfat fat joydev xpad ff_memless kvm_amd kvm ppdev lp bnep rfcomm bluetooth rfkill crc16 uinput fuse bridge stp tun ipt_REJECT xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack xt_owner iptable_filter ip_tables x_tables ext2 loop snd_hda_codec_hdmi snd_hda_codec_via snd_hda_intel snd_hda_codec snd_pcm_oss radeon snd_mixer_oss usblp snd_usb_audio snd_hwdep snd_usbmidi_lib ttm snd_pcm snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq drm_kms_helper drm i2c_algo_bit sp5100_tco snd_timer power_supply snd_seq_device snd soundcore tpm_tis tpm tpm_bios amd64_edac_mod edac_core i2c_piix4 edac_mce_amd i2c_core shpchp snd_page_alloc parport_pc parport asus_atk0110 processor pci_hotplug pcspkr evdev k10temp button thermal_sys wmi ext3 jbd mbcache sha256_generic cryptd aes_x86_64 aes_generic cbc usbhid hid usb_storage uas dm_crypt dm_mod raid456 md_mod async_raid6_recov async_pq raid6_pq async_xor xor async_me mcpy async_tx sg sd_mod sr_mod crc_t10dif cdrom ata_generic ohci_hcd pata_atiixp ahci libahci libata ehci_hcd scsi_mod usbcore r8169 mii [last unloaded: scsi_wait_scan] [834006.041894] [834006.041918] Pid: 3309, comm:
Bug#649534: marked as done (linux-image-3.1.0-1-amd64: Kernel panic while doing nothing much in particular, after hibernating twice and suspending once)
Your message dated Sat, 6 Jul 2013 17:59:20 +0200 with message-id 20130706155920.GD12523@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #649534, regarding linux-image-3.1.0-1-amd64: Kernel panic while doing nothing much in particular, after hibernating twice and suspending once 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 ow...@bugs.debian.org immediately.) -- 649534: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649534 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 3.1.1-1 Severity: normal Booted computer (Samsung Q45), hibernated, booted back up, suspended, booted back up, hibernated again, booted back up... a few minutes later it panicked. I took a photo of the screen, while I'll mail to the bug in a moment... here's the info that appeared in syslog: Nov 21 23:18:02 durandal kernel: [ 1100.664518] BUG: unable to handle kernel NULL pointer dereference at 0008 Nov 21 23:18:02 durandal kernel: [ 1100.664601] IP: [810e4566] list_del+0x1b/0x2a Nov 21 23:18:02 durandal kernel: [ 1100.664653] PGD 72e13067 PUD 766e5067 PMD 0 Nov 21 23:18:02 durandal kernel: [ 1100.664700] Oops: 0002 [#1] SMP Nov 21 23:18:02 durandal kernel: [ 1100.664737] CPU 0 Nov 21 23:18:02 durandal kernel: [ 1100.664756] Modules linked in: binfmt_misc cpufreq_powersave acpi_cpufreq mperf parport_pc cpufreq_conservative ppdev cpufreq_stats lp parport cpufreq_userspace uvcvideo videodev media v4l2_compat_ioctl32 snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_seq_midi snd_rawmidi snd_seq_midi_event ecb snd_seq btusb bluetooth snd_timer snd_seq_device arc4 iwl3945 iwl_legacy mac80211 i2c_i801 r592 snd pcmcia cfg80211 soundcore joydev evdev yenta_socket snd_page_alloc memstick pcmcia_rsrc pcmcia_core r852 sm_common nand nand_ids samsung_laptop nand_ecc mtd rfkill pcspkr wmi psmouse serio_raw processor battery ac power_supply loop firewire_sbp2 autofs4 ext4 mbcache jbd2 crc16 sha256_generic cryptd aes_x86_64 aes_generic cbc dm_crypt dm_mod sg sr_mod cdrom sd_mod crc_t10dif ata_generic i915 firewire_ohci uhci_hcd sdhci_pci sdhci mmc_core fan firewire_core crc_itu_t ata_piix libata thermal drm_kms_helper scsi_mod drm ehci_hcd i2 c_algo_bit i2c_core button sky2 video t Nov 21 23:18:02 durandal kernel: hermal_sys usbcore [last unloaded: scsi_wait_scan] Nov 21 23:18:02 durandal kernel: [ 1100.665837] Nov 21 23:18:02 durandal kernel: [ 1100.665853] Pid: 5386, comm: bash Not tainted 3.1.0-1-amd64 #1 SAMSUNG ELECTRONICS CO., LTD. SQ45S70S/SQ45S70S Nov 21 23:18:02 durandal kernel: [ 1100.665944] RIP: 0010:[810e4566] [810e4566] list_del+0x1b/0x2a Nov 21 23:18:02 durandal kernel: [ 1100.666010] RSP: 0018:880072fbde10 EFLAGS: 00010046 Nov 21 23:18:02 durandal kernel: [ 1100.666055] RAX: 88007c82c740 RBX: 88007c81ec80 RCX: dead00100100 Nov 21 23:18:02 durandal kernel: [ 1100.666112] RDX: RSI: dead00200200 RDI: 88007c75b000 Nov 21 23:18:02 durandal kernel: [ 1100.666169] RBP: R08: 0005 R09: 88007c831000 Nov 21 23:18:02 durandal kernel: [ 1100.666226] R10: 0202 R11: 0202 R12: 000412d0 Nov 21 23:18:02 durandal kernel: [ 1100.666283] R13: 88007c82c740 R14: 88007c82d800 R15: 000e Nov 21 23:18:02 durandal kernel: [ 1100.666341] FS: 7fae4322c700() GS:88007f40() knlGS: Nov 21 23:18:02 durandal kernel: [ 1100.666407] CS: 0010 DS: ES: CR0: 80050033 Nov 21 23:18:02 durandal kernel: [ 1100.666453] CR2: 0008 CR3: 753f9000 CR4: 06f0 Nov 21 23:18:02 durandal kernel: [ 1100.666511] DR0: DR1: DR2: ** Model information sys_vendor: SAMSUNG ELECTRONICS CO., LTD. product_name: SQ45S70S product_version: 11ST chassis_vendor: SAMSUNG ELECTRONICS CO., LTD. chassis_version: N/A bios_vendor: Phoenix Technologies LTD bios_version: 11ST board_vendor: SAMSUNG ELECTRONICS CO., LTD. board_name: SQ45S70S board_version: ** Loaded modules: Module Size Used by binfmt_misc12957 1 cpufreq_powersave 12454 0 acpi_cpufreq 12935 1 parport_pc 22364 0 ppdev 12763 0 mperf 12453 1 acpi_cpufreq lp 17149 0 parport31858 3 parport_pc,ppdev,lp cpufreq_conservative13147 0 cpufreq_stats 12866 0 cpufreq_userspace 12576 0 uvcvideo
Bug#648966: marked as done (linux-image-3.1.0-1-amd64: module brcm80211 crashes the computer when connection channel 13)
Your message dated Sat, 6 Jul 2013 17:59:20 +0200 with message-id 20130706155920.GD12523@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #648966, regarding linux-image-3.1.0-1-amd64: module brcm80211 crashes the computer when connection channel 13 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 ow...@bugs.debian.org immediately.) -- 648966: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648966 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 3.1.1-1 Severity: important Dear Maintainer, When connecting on a WiFi using the channel 13 my computer becomes very very slow and eat all the CPU. Blacklisting the module makes my computer usable again (I then use tethering to connect to the internet hence the usb0 present in this bugreport). -- Package-specific info: ** Version: Linux version 3.1.0-1-amd64 (Debian 3.1.1-1) (b...@decadent.org.uk) (gcc version 4.6.2 (Debian 4.6.2-4) ) #1 SMP Mon Nov 14 08:02:25 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.1.0-1-amd64 root=UUID=817b61a4-242c-40d4-a61c-997f4b00513b ro quiet ** Not tainted ** Kernel log: [8.053192] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) [8.053252] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 [8.058137] snd_hda_intel :00:1b.0: power state changed by ACPI to D0 [8.058147] snd_hda_intel :00:1b.0: power state changed by ACPI to D0 [8.058169] snd_hda_intel :00:1b.0: PCI INT A - GSI 22 (level, low) - IRQ 22 [8.058249] snd_hda_intel :00:1b.0: irq 47 for MSI/MSI-X [8.058281] snd_hda_intel :00:1b.0: setting latency timer to 64 [8.644926] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/input/input11 [8.659942] HDMI status: Codec=3 Pin=5 Presence_Detect=0 ELD_Valid=0 [8.660275] HDMI status: Codec=3 Pin=6 Presence_Detect=0 ELD_Valid=0 [8.660607] HDMI status: Codec=3 Pin=7 Presence_Detect=0 ELD_Valid=0 [8.675788] input: HDA Intel PCH Mic at Ext Right Jack as /devices/pci:00/:00:1b.0/sound/card0/input12 [8.675909] input: HDA Intel PCH HP Out at Ext Right Jack as /devices/pci:00/:00:1b.0/sound/card0/input13 [8.676583] input: HDA Intel PCH HDMI/DP as /devices/pci:00/:00:1b.0/sound/card0/input14 [8.676650] input: HDA Intel PCH HDMI/DP as /devices/pci:00/:00:1b.0/sound/card0/input15 [8.676708] input: HDA Intel PCH HDMI/DP as /devices/pci:00/:00:1b.0/sound/card0/input16 [9.082046] Adding 7811068k swap on /dev/sda7. Priority:-1 extents:1 across:7811068k [9.085082] EXT4-fs (sda3): re-mounted. Opts: (null) [9.465932] EXT4-fs (sda3): re-mounted. Opts: errors=remount-ro [9.574148] loop: module loaded [ 11.391665] EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (null) [ 11.416686] EXT4-fs (sda8): mounted filesystem with ordered data mode. Opts: (null) [ 11.461892] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null) [ 11.504040] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null) [ 12.864397] fuse init (API version 7.17) [ 18.497967] lp0: using parport0 (interrupt-driven). [ 18.500870] ppdev: user-space parallel port driver [ 23.098613] pg_ctlcluster (2239): /proc/2239/oom_adj is deprecated, please use /proc/2239/oom_score_adj instead. [ 31.283273] e1000e :00:19.0: PME# enabled [ 33.174731] e1000e :00:19.0: BAR 0: set to [mem 0xd470-0xd471] (PCI address [0xd470-0xd471]) [ 33.174749] e1000e :00:19.0: BAR 1: set to [mem 0xd472a000-0xd472afff] (PCI address [0xd472a000-0xd472afff]) [ 33.174762] e1000e :00:19.0: BAR 2: set to [io 0x4060-0x407f] (PCI address [0x4060-0x407f]) [ 33.174800] e1000e :00:19.0: restoring config space at offset 0xf (was 0x100, writing 0x10a) [ 33.174818] e1000e :00:19.0: restoring config space at offset 0x1 (was 0x10, writing 0x17) [ 33.174859] e1000e :00:19.0: PME# disabled [ 33.321909] e1000e :00:19.0: irq 44 for MSI/MSI-X [ 33.374704] e1000e :00:19.0: irq 44 for MSI/MSI-X [ 33.375470] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 34.558277] e1000e :00:19.0: PCI INT A disabled [ 34.558286] e1000e :00:19.0: PME# enabled [ 40.291226] usb 2-1.2: new high speed USB device number 5 using ehci_hcd [ 55.355532] usb 2-1.2: device descriptor read/64, error -110 [ 70.523764] usb 2-1.2: device descriptor read/64, error -110 [ 70.699673] usb 2-1.2: new high speed USB device number 6 using ehci_hcd [ 85.763833] usb 2-1.2:
Bug#643805: marked as done (linux-image-3.0.0-1-686-pae: ipv4/conf/all/* entries do not work in /proc/sys/net/)
Your message dated Sat, 6 Jul 2013 17:58:37 +0200 with message-id 20130706155837.GC12523@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #643805, regarding linux-image-3.0.0-1-686-pae: ipv4/conf/all/* entries do not work in /proc/sys/net/ 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 ow...@bugs.debian.org immediately.) -- 643805: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643805 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 3.0.0-3 Severity: normal Dear Maintainer, I have a vpn gateway that periodically sends icmp redirects to the hosts of my network (when renegociating tunnels), I configured hosts not to accepts reidrects by uncommenting the default directive found in sysctl.conf: net.ipv4.conf.all.accept_redirects = 0 after reboot here is the config i get in /proc/sys: cat /proc/sys/net/ipv4/conf/*/accept_redirects 0 1 1 1 1 If i try to echo the value in the proc filesystem, It's no better: root@elronde:/home/alxgomzecho 0 /proc/sys/net/ipv4/conf/all/accept_redirects root@elronde:/home/alxgomz# cat /proc/sys/net/ipv4/conf/*/accept_redirects 0 1 1 1 1 Where I expected this to put all interfaces to zero. the entry ./default/accept_redirects seems to work as expected. I have seen the same behaviour for other proc entries such as send_redirects and notices the bug #630650 that is maybe related. -- Package-specific info: ** Version: Linux version 3.0.0-1-686-pae (Debian 3.0.0-3) (b...@decadent.org.uk) (gcc version 4.5.3 (Debian 4.5.3-8) ) #1 SMP Sat Aug 27 16:41:03 UTC 2011 ** Command line: BOOT_IMAGE=/vmlinuz-3.0.0-1-686-pae root=/dev/mapper/localvg-root ro splash quiet ** Tainted: C (1024) * Module from drivers/staging has been loaded. ** Kernel log: [ 97.965216] wlan0: associated [ 97.966015] ieee80211 phy0: wl_ops_bss_info_changed: qos enabled: true (implement) [ 97.966019] ieee80211 phy0: brcmsmac: wl_ops_bss_info_changed: associated [ 97.966034] ieee80211 phy0: wl_ops_bss_info_changed: arp filtering: enabled true, count 0 (implement) [ 97.966129] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 98.161428] ieee80211 phy0: wl_ops_bss_info_changed: arp filtering: enabled true, count 1 (implement) [ 104.159737] PPP generic driver version 2.4.2 [ 106.936206] PPP MPPE Compression module registered [ 108.492029] wlan0: no IPv6 routers present [ 110.528175] process `skype' is using obsolete setsockopt SO_BSDCOMPAT [ 2316.927514] usb 2-1.1.2: new high speed USB device number 7 using ehci_hcd [ 2317.019921] usb 2-1.1.2: New USB device found, idVendor=03f0, idProduct=4712 [ 2317.019929] usb 2-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 2317.019936] usb 2-1.1.2: Product: Officejet 4500 G510a-f [ 2317.019941] usb 2-1.1.2: Manufacturer: HP [ 2317.019945] usb 2-1.1.2: SerialNumber: CN0BUF10CC05H2 [ 2318.171544] usb 2-1.1.2: usbfs: process 4625 (usb) did not claim interface 0 before use [ 2504.341104] usb 2-1.1.2: USB disconnect, device number 7 [ 2530.612230] usb 2-1.1.2: new high speed USB device number 8 using ehci_hcd [ 2530.704860] usb 2-1.1.2: New USB device found, idVendor=03f0, idProduct=4712 [ 2530.704867] usb 2-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 2530.704871] usb 2-1.1.2: Product: Officejet 4500 G510a-f [ 2530.704875] usb 2-1.1.2: Manufacturer: HP [ 2530.704878] usb 2-1.1.2: SerialNumber: CN0BUF10CC05H2 [ 2531.794262] usb 2-1.1.2: usbfs: process 4764 (usb) did not claim interface 0 before use [ 2570.155587] usb 2-1.1.2: usbfs: process 4826 (usb) did not claim interface 0 before use [ 5983.799914] EXT4-fs (dm-1): re-mounted. Opts: errors=remount-ro,commit=0 [ 5984.607592] EXT4-fs (dm-3): re-mounted. Opts: commit=0 [ 7036.968457] usb 2-1.1.1: USB disconnect, device number 6 [13316.883146] GRE over IPv4 demultiplexor driver [13316.884641] GRE over IPv4 tunneling driver [13712.967501] oosplash.bin[11944]: segfault at 4d0 ip b75cfd6b sp bf9c0210 error 4 in libX11.so.6.3.0[b7599000+136000] [18358.128303] usb 2-1.1.1: new high speed USB device number 9 using ehci_hcd [18358.232932] usb 2-1.1.1: New USB device found, idVendor=0bb4, idProduct=0ff9 [18358.232935] usb 2-1.1.1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [18358.232937] usb 2-1.1.1: Product: Android Phone [18358.232939] usb 2-1.1.1: Manufacturer: HTC [18358.232940] usb 2-1.1.1: SerialNumber: HT9AEL901012 [18358.237673] scsi7 : usb-storage 2-1.1.1:1.0 [18359.237421] scsi 7:0:0:0: Direct-Access HTC Android Phone0100 PQ: 0 ANSI: 2 [18359.350418] sd 7:0:0:0: Attached scsi generic sg1
Bug#652505: marked as done (2.6.32-5-powerpc: Kernel error sometimes on connecting to Wifi)
Your message dated Sat, 6 Jul 2013 17:59:44 +0200 with message-id 20130706155944.GE12523@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #652505, regarding 2.6.32-5-powerpc: Kernel error sometimes on connecting to Wifi 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 ow...@bugs.debian.org immediately.) -- 652505: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652505 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-38 Severity: important File: 2.6.32-5-powerpc -- Package-specific info: ** Version: Linux version 2.6.32-5-powerpc (Debian 2.6.32-38) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 Mon Oct 3 04:26:33 UTC 2011 ** Command line: root=UUID=80d676e0-821e-40a8-af16-fe99a398035d ro ** Tainted: W (512) * Taint on warning. ** Kernel log: [ 3502.342204] Call Trace: [ 3502.342214] [d5c9bc50] [c005dbcc] __queue_work+0x24/0x3c (unreliable) [ 3502.342229] [d5c9bc70] [c006c834] do_gettimeofday+0x1c/0x48 [ 3502.342247] [d5c9bca0] [d9dd8508] evdev_event+0x28/0x130 [evdev] [ 3502.342262] [d5c9bcd0] [c029eef4] input_pass_event+0x78/0xb0 [ 3502.342275] [d5c9bcf0] [c02a1d80] input_event+0x6c/0x84 [ 3502.342288] [d5c9bd10] [c0289644] via_pmu_event+0x78/0x88 [ 3502.342303] [d5c9bd20] [c0287d00] via_pmu_interrupt+0xa14/0xa70 [ 3502.342316] [d5c9bd80] [c0287fdc] pmu_wait_complete+0x34/0x74 [ 3502.342329] [d5c9bd90] [c0289214] pmu_sys_resume+0x44/0x70 [ 3502.342343] [d5c9be10] [c0276140] __sysdev_resume+0x9c/0xfc [ 3502.342357] [d5c9be30] [c027620c] sysdev_resume+0x6c/0xd4 [ 3502.342370] [d5c9be50] [c007cd54] suspend_devices_and_enter+0x164/0x21c [ 3502.342384] [d5c9be70] [c007cf14] enter_state+0x108/0x158 [ 3502.342398] [d5c9be90] [c0286e6c] pmu_ioctl+0x78/0x194 [ 3502.342412] [d5c9bea0] [c0101c84] vfs_ioctl+0x68/0x80 [ 3502.342426] [d5c9beb0] [c0102424] do_vfs_ioctl+0x660/0x6f0 [ 3502.342440] [d5c9bf10] [c010250c] sys_ioctl+0x58/0x88 [ 3502.342453] [d5c9bf40] [c0014dac] ret_from_syscall+0x0/0x40 [ 3502.342470] --- Exception: c01 at 0xfa78b08 [ 3502.342476] LR = 0xfa78a6c [ 3502.342481] Instruction dump: [ 3502.342487] 38210030 7c0803a6 4e800020 9421ffe0 7c0802a6 3d20c051 bf410008 7c7f1b78 [ 3502.342507] 90010024 80092904 3160 7d2b0110 0f09 3d20c051 3b696210 3d20c051 [ 3502.353836] aty128fb :00:10.0: Refused to change power state, currently in D2 [ 3502.399393] firewire_ohci 0002:20:0e.0: Refused to change power state, currently in D3 [ 3502.399414] firewire_ohci 0002:20:0e.0: restoring config space at offset 0xf (was 0x, writing 0x180c0100) [ 3502.399431] firewire_ohci 0002:20:0e.0: restoring config space at offset 0xe (was 0x, writing 0x0) [ 3502.399447] firewire_ohci 0002:20:0e.0: restoring config space at offset 0xd (was 0x, writing 0x44) [ 3502.399463] firewire_ohci 0002:20:0e.0: restoring config space at offset 0xc (was 0x, writing 0x0) [ 3502.399479] firewire_ohci 0002:20:0e.0: restoring config space at offset 0xb (was 0x, writing 0x30106b) [ 3502.399495] firewire_ohci 0002:20:0e.0: restoring config space at offset 0xa (was 0x, writing 0x0) [ 3502.399510] firewire_ohci 0002:20:0e.0: restoring config space at offset 0x9 (was 0x, writing 0x0) [ 3502.399526] firewire_ohci 0002:20:0e.0: restoring config space at offset 0x8 (was 0x, writing 0x0) [ 3502.399541] firewire_ohci 0002:20:0e.0: restoring config space at offset 0x7 (was 0x, writing 0x0) [ 3502.399557] firewire_ohci 0002:20:0e.0: restoring config space at offset 0x6 (was 0x, writing 0x0) [ 3502.399573] firewire_ohci 0002:20:0e.0: restoring config space at offset 0x5 (was 0x, writing 0x0) [ 3502.399588] firewire_ohci 0002:20:0e.0: restoring config space at offset 0x4 (was 0x, writing 0xf500) [ 3502.399605] firewire_ohci 0002:20:0e.0: restoring config space at offset 0x3 (was 0x, writing 0x1008) [ 3502.399621] firewire_ohci 0002:20:0e.0: restoring config space at offset 0x2 (was 0x, writing 0xc001000) [ 3502.399637] firewire_ohci 0002:20:0e.0: restoring config space at offset 0x1 (was 0x, writing 0x2b00016) [ 3502.399653] firewire_ohci 0002:20:0e.0: restoring config space at offset 0x0 (was 0x, writing 0x30106b) [ 3502.416501] aty128fb: resumed ! [ 3502.551444] eth0: resuming [ 3502.615709] PHY ID: 4061e3, addr: 0 [ 3503.635390] eth1: Airport waking up [ 3504.083181] hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4 [ 3504.083493] adb: starting probe task... [ 3504.087433] hda: UDMA/33 mode selected [ 3504.089899]
Bug#519140: marked as done (WARNING: at net/sched/sch_generic.c:222 dev_watchdog+0x8f/0xdc())
Your message dated Sat, 6 Jul 2013 18:00:34 +0200 with message-id 20130706160034.GG12523@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #519140, regarding WARNING: at net/sched/sch_generic.c:222 dev_watchdog+0x8f/0xdc() 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 ow...@bugs.debian.org immediately.) -- 519140: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=519140 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-1-686 Version: 2.6.26-13 Severity: minor I get the follow Warning in dmesg [ 1088.000117] [ cut here ] [ 1088.000133] WARNING: at net/sched/sch_generic.c:222 dev_watchdog+0x8f/0xdc() [ 1088.000147] Modules linked in: ipv6 loop container parport_pc parport button snd_pcm snd_timer irtty_sir sir_dev snd soundcore snd_page_alloc irda hisax_fcpcipnp hisax_isac hisax crc_ccitt isdn i2c_piix4shpchp intel_agp slhc i2c_core pci_hotplug agpgart psmouse pcspkr evdev sg sr_mod sd_mod cdrom ext3 jbd mbcache raid1 md_mod ide_disk ide_pci_generic usbhid hid ff_memless piix ide_core ata_generic uhci_hcdaic7xxx floppy libata scsi_transport_spi 3c59x mii usbcore scsi_mod dock thermal processor fan thermal_sys [ 1088.000363] Pid: 0, comm: swapper Not tainted 2.6.26-1-686 #1 [ 1088.000392] [c012256f] warn_on_slowpath+0x40/0x66 [ 1088.000469] [c0134d68] up+0x9/0x2a [ 1088.000502] [c0122a10] release_console_sem+0x173/0x18c [ 1088.000611] [c0266aa2] dev_watchdog+0x0/0xdc [ 1088.000637] [c0122ea7] printk+0x14/0x18 [ 1088.000671] [c89df263] isdn_net_tx_timeout+0x1d/0x4f [isdn] [ 1088.000770] [c0266b31] dev_watchdog+0x8f/0xdc [ 1088.000805] [c0129658] run_timer_softirq+0x11a/0x17c [ 1088.000837] [c0266aa2] dev_watchdog+0x0/0xdc [ 1088.000885] [c0126579] __do_softirq+0x66/0xd3 [ 1088.000917] [c012662b] do_softirq+0x45/0x53 [ 1088.000940] [c01268e2] irq_exit+0x35/0x67 [ 1088.000961] [c0105f3f] do_IRQ+0x52/0x63 [ 1088.000994] [c0102656] default_idle+0x0/0x53 [ 1088.001024] [c01042a7] common_interrupt+0x23/0x28 [ 1088.001047] [c0102656] default_idle+0x0/0x53 [ 1088.001092] [c0114d54] native_safe_halt+0x2/0x3 [ 1088.001139] [c0102683] default_idle+0x2d/0x53 [ 1088.001161] [c01025ce] cpu_idle+0xab/0xcb [ 1088.001196] === [ 1088.001210] ---[ end trace ce97df7e538e590f ]--- -- Package-specific info: ** Version: Linux version 2.6.26-1-686 (Debian 2.6.26-13) (wa...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-24)) #1 SMP Sat Jan 10 18:29:31 UTC 2009 ** Command line: root=/dev/md0 ro quiet ** Tainted: G W (512) ** Kernel log: [ 38.054672] HiSax: Card 1 Protocol EDSS1 Id=fcpcipnp0 (0) [ 38.054710] HiSax: DSS1 Rev. 2.32.2.3 [ 38.054729] HiSax: 2 channels added [ 38.054742] HiSax: MAX_WAITING_CALLS added [ 38.055744] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11 [ 38.055764] PCI: setting IRQ 11 as level-triggered [ 38.055779] ACPI: PCI Interrupt :00:0c.0[A] - Link [LNKA] - GSI 11 (level, low) - IRQ 11 [ 38.055807] hisax_fcpcipnp: found adapter Fritz!Card PCI at :00:0c.0 [ 38.874301] NET: Registered protocol family 23 [ 41.089335] Error: Driver 'pcspkr' is already registered, aborting... [ 41.102479] input: Power Button (FF) as /class/input/input3 [ 41.128832] ACPI: Power Button (FF) [PWRF] [ 42.185332] parport_pc 00:09: activated [ 42.185357] parport_pc 00:09: reported by Plug and Play ACPI [ 42.185405] parport0: PC-style at 0x278, irq 5 [PCSPP,EPP] [ 42.282141] parport_pc 00:0a: unable to assign resources [ 42.282242] parport_pc: probe of 00:0a failed with error -16 [ 47.668606] Adding 987896k swap on /dev/md1. Priority:-1 extents:1 across:987896k [ 48.392173] EXT3 FS on md0, internal journal [ 49.248212] loop: module loaded [ 51.907394] eth0: setting half-duplex. [ 230.74] NET: Registered protocol family 10 [ 231.003030] lo: Disabled Privacy Extensions [ 241.568060] eth0: no IPv6 routers present [ 777.532032] kjournald starting. Commit interval 5 seconds [ 777.532032] EXT3 FS on sda1, internal journal [ 777.532032] EXT3-fs: mounted filesystem with ordered data mode. [ 907.565182] isdn: Verbose-Level is 2 [ 907.814746] ippp, open, slot: 0, minor: 0, state: [ 907.814789] ippp_ccp: allocated reset data structure c60e4000 [ 1081.808059] OPEN: 169.255.255.169 - 141.76.2.4 TCP, port: 54752 - 80 [ 1081.808059] ippp0: dialing 1 0191011... [ 1088.40] NETDEV WATCHDOG: ippp0: transmit timed out [ 1088.73] isdn_tx_timeout dev ippp0 dialstate 4 [ 1088.000117] [ cut here ] [ 1088.000133] WARNING:
Bug#584656: marked as done (linux-image-2.6.32-3-amd64: caps lock key doesn't toggle caps lock LED on virtual console)
Your message dated Sat, 6 Jul 2013 18:00:34 +0200 with message-id 20130706160034.GG12523@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #584656, regarding linux-image-2.6.32-3-amd64: caps lock key doesn't toggle caps lock LED on virtual console 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 ow...@bugs.debian.org immediately.) -- 584656: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584656 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-9 Severity: minor When I switch to a virtual console and press the Caps Lock key, I expect the Caps Lock LED on my laptop to toggle on and off. The Caps Lock key does make all the other keys use upper case, just the LED doesn't switch on. On virtual consoles the Num Lk and Scroll Lk keys both toggle their LEDs on and off. In Xorg under GNOME the Caps Lock key toggles its LED on and off fine. -- Package-specific info: ** Version: Linux version 2.6.32-3-amd64 (Debian 2.6.32-9) (m...@debian.org) (gcc version 4.3.4 (Debian 4.3.4-8) ) #1 SMP Wed Feb 24 18:07:42 UTC 2010 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.32-3-amd64 root=/dev/mapper/chianamo-root ro quiet loglevel=0 video=i915 ** Not tainted ** Kernel log: [26758.500518] sr0: CDROM not ready. Make sure there is a disc in the drive. [26758.720193] [drm] TV-14: set mode NTSC 480i 0 [26758.860598] [drm] TV-14: set mode NTSC 480i 0 [26769.497665] [drm] TV-14: set mode NTSC 480i 0 [26769.638023] [drm] TV-14: set mode NTSC 480i 0 [26773.568196] [drm] TV-14: set mode NTSC 480i 0 [26773.708565] [drm] TV-14: set mode NTSC 480i 0 [26810.040213] [drm] TV-14: set mode NTSC 480i 0 [26810.180225] [drm] TV-14: set mode NTSC 480i 0 [26816.716378] [drm] TV-14: set mode NTSC 480i 0 [26816.856755] [drm] TV-14: set mode NTSC 480i 0 [26823.971862] [drm] TV-14: set mode NTSC 480i 0 [26824.112333] [drm] TV-14: set mode NTSC 480i 0 [26826.068805] sr0: CDROM not ready. Make sure there is a disc in the drive. [26828.720452] sr0: CDROM not ready. Make sure there is a disc in the drive. [26828.940761] [drm] TV-14: set mode NTSC 480i 0 [26829.082010] [drm] TV-14: set mode NTSC 480i 0 [26836.148505] sr0: CDROM not ready. Make sure there is a disc in the drive. [27108.932511] sr0: CDROM not ready. Make sure there is a disc in the drive. [27109.153847] [drm] TV-14: set mode NTSC 480i 0 [27109.294173] [drm] TV-14: set mode NTSC 480i 0 [27119.933153] [drm] TV-14: set mode NTSC 480i 0 [27120.073851] [drm] TV-14: set mode NTSC 480i 0 [27126.457543] sr0: CDROM not ready. Make sure there is a disc in the drive. [27176.756497] sr0: CDROM not ready. Make sure there is a disc in the drive. [27176.995037] [drm] TV-14: set mode NTSC 480i 0 [27177.138811] [drm] TV-14: set mode NTSC 480i 0 [27187.764127] [drm] TV-14: set mode NTSC 480i 0 [27187.904579] [drm] TV-14: set mode NTSC 480i 0 [27207.324499] sr0: CDROM not ready. Make sure there is a disc in the drive. [27209.736493] [drm] TV-14: set mode NTSC 480i 0 [27209.877048] [drm] TV-14: set mode NTSC 480i 0 [27230.284499] sr0: CDROM not ready. Make sure there is a disc in the drive. [27234.508502] sr0: CDROM not ready. Make sure there is a disc in the drive. [27234.728149] [drm] TV-14: set mode NTSC 480i 0 [27234.868529] [drm] TV-14: set mode NTSC 480i 0 [27239.824594] [drm] TV-14: set mode NTSC 480i 0 [27239.965238] [drm] TV-14: set mode NTSC 480i 0 [27241.224504] sr0: CDROM not ready. Make sure there is a disc in the drive. [27242.296797] sr0: CDROM not ready. Make sure there is a disc in the drive. [27242.516221] [drm] TV-14: set mode NTSC 480i 0 [27242.656582] [drm] TV-14: set mode NTSC 480i 0 [27253.280656] [drm] TV-14: set mode NTSC 480i 0 [27253.420968] [drm] TV-14: set mode NTSC 480i 0 [27261.372488] [drm] TV-14: set mode NTSC 480i 0 [27261.512870] [drm] TV-14: set mode NTSC 480i 0 [27281.580615] [drm] TV-14: set mode NTSC 480i 0 [27281.721135] [drm] TV-14: set mode NTSC 480i 0 [27284.152493] sr0: CDROM not ready. Make sure there is a disc in the drive. [27362.244520] sr0: CDROM not ready. Make sure there is a disc in the drive. [27362.464374] [drm] TV-14: set mode NTSC 480i 0 [27362.604752] [drm] TV-14: set mode NTSC 480i 0 [27373.252298] [drm] TV-14: set mode NTSC 480i 0 [27373.392690] [drm] TV-14: set mode NTSC 480i 0 [27389.480469] sr0: CDROM not ready. Make sure there is a disc in the drive. [27390.772500] [drm] TV-14: set mode NTSC 480i 0 [27390.912930] [drm] TV-14: set mode NTSC 480i 0 [27416.700496] sr0: CDROM not ready. Make sure there is a disc in the drive. [27431.900544] sr0: CDROM not ready. Make sure there is a disc in
Bug#532804: marked as done (general: kernel messages appear when they shouldn't on LVM+LUKS systems)
Your message dated Sat, 6 Jul 2013 18:00:34 +0200 with message-id 20130706160034.GG12523@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #532804, regarding general: kernel messages appear when they shouldn't on LVM+LUKS systems 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 ow...@bugs.debian.org immediately.) -- 532804: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=532804 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: general Severity: minor Problem reproduction: Install a debian testing selecting LVM+encryption. Then, when the system boots, although there is the option quiet for silencing the kernel messages, after entering the passphrase, you start seeing kernel messages along with their timestamp on the beginning. Minor, but I guess those kernel messages should not appear... -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash ---End Message--- ---BeginMessage--- Hi, your bug has been filed against the linux-2.6 source package and was filed for a kernel older than the recently released Debian 7.x / Wheezy with a severity less than important. We don't have the ressources to reproduce the complete backlog of all older kernel bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy or a more recent kernel from testing or unstable, please reopen the bug by sending a mail to cont...@bugs.debian.org with the following three commands included in the mail: reopen BUGNUMBER reassign BUGNUMBER src:linux thanks Cheers, Moritz---End Message---
Bug#656911: marked as done (linux-image-3.2.0-1-686-pae: kernel NULL pointer dereference in vsnprintf)
Your message dated Sat, 6 Jul 2013 17:59:44 +0200 with message-id 20130706155944.GE12523@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #656911, regarding linux-image-3.2.0-1-686-pae: kernel NULL pointer dereference in vsnprintf 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 ow...@bugs.debian.org immediately.) -- 656911: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656911 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Subject: linux-image-3.2.0-1-686-pae: kernel NULL pointer dereference in vsnprintf Package: linux-2.6 Version: 3.2.1-1 Severity: normal Hi debian kernel team-- i just upgraded to 3.2 from unstable on this Asus EeePC 900. The machine was only up for about 20 minutes (i was already logged in, though), when i got the OOPS recorded below. I'm happy to provide any additional information or to run tests. please let me know what would be useful. Thanks for your work on Linux in Debian! Regards, --dkg -- Package-specific info: ** Version: Linux version 3.2.0-1-686-pae (Debian 3.2.1-1) (b...@decadent.org.uk) (gcc version 4.6.2 (Debian 4.6.2-11) ) #1 SMP Thu Jan 19 10:56:51 UTC 2012 ** Command line: BOOT_IMAGE=/vmlinuz-3.2.0-1-686-pae root=/dev/mapper/vg_pip0-root ro verbose ** Tainted: D (128) * Kernel has oopsed before. ** Kernel log: [ 1202.032255] keyboard: can't emulate rawmode for keycode 240 [ 1202.096235] keyboard: can't emulate rawmode for keycode 240 [ 1202.096256] keyboard: can't emulate rawmode for keycode 240 [ 1202.140272] keyboard: can't emulate rawmode for keycode 240 [ 1202.140294] keyboard: can't emulate rawmode for keycode 240 [ 1202.184250] keyboard: can't emulate rawmode for keycode 240 [ 1202.184271] keyboard: can't emulate rawmode for keycode 240 [ 1225.053589] kbd_keycode: 4 callbacks suppressed [ 1225.053597] keyboard: can't emulate rawmode for keycode 240 [ 1225.053615] keyboard: can't emulate rawmode for keycode 240 [ 1237.556379] keyboard: can't emulate rawmode for keycode 240 [ 1237.556402] keyboard: can't emulate rawmode for keycode 240 [ 1238.036243] keyboard: can't emulate rawmode for keycode 240 [ 1238.036265] keyboard: can't emulate rawmode for keycode 240 [ 1238.096226] keyboard: can't emulate rawmode for keycode 240 [ 1238.096248] keyboard: can't emulate rawmode for keycode 240 [ 1249.237586] keyboard: can't emulate rawmode for keycode 240 [ 1249.237608] keyboard: can't emulate rawmode for keycode 240 [ 1389.225219] keyboard: can't emulate rawmode for keycode 240 [ 1389.225242] keyboard: can't emulate rawmode for keycode 240 [ 1389.246101] keyboard: can't emulate rawmode for keycode 240 [ 1389.246123] keyboard: can't emulate rawmode for keycode 240 [ 1389.288280] keyboard: can't emulate rawmode for keycode 240 [ 1389.288302] keyboard: can't emulate rawmode for keycode 240 [ 1389.604610] keyboard: can't emulate rawmode for keycode 240 [ 1389.604632] keyboard: can't emulate rawmode for keycode 240 [ 1389.664405] keyboard: can't emulate rawmode for keycode 240 [ 1389.664429] keyboard: can't emulate rawmode for keycode 240 [ 1399.237568] kbd_keycode: 8 callbacks suppressed [ 1399.237577] keyboard: can't emulate rawmode for keycode 240 [ 1399.237597] keyboard: can't emulate rawmode for keycode 240 [ 1399.309418] keyboard: can't emulate rawmode for keycode 240 [ 1399.309441] keyboard: can't emulate rawmode for keycode 240 [ 1400.396275] keyboard: can't emulate rawmode for keycode 240 [ 1400.396296] keyboard: can't emulate rawmode for keycode 240 [ 1825.436224] keyboard: can't emulate rawmode for keycode 240 [ 1825.436246] keyboard: can't emulate rawmode for keycode 240 [ 1825.584448] keyboard: can't emulate rawmode for keycode 240 [ 1825.584469] keyboard: can't emulate rawmode for keycode 240 [ 1825.628218] keyboard: can't emulate rawmode for keycode 240 [ 1825.628239] keyboard: can't emulate rawmode for keycode 240 [ 1837.029568] keyboard: can't emulate rawmode for keycode 240 [ 1837.029590] keyboard: can't emulate rawmode for keycode 240 [ 2032.796611] keyboard: can't emulate rawmode for keycode 240 [ 2032.796632] keyboard: can't emulate rawmode for keycode 240 [ 2032.844226] keyboard: can't emulate rawmode for keycode 240 [ 2032.844249] keyboard: can't emulate rawmode for keycode 240 [ 2032.920253] keyboard: can't emulate rawmode for keycode 240 [ 2032.920274] keyboard: can't emulate rawmode for keycode 240 [ 2044.293560] keyboard: can't emulate rawmode for keycode 240 [ 2044.293582] keyboard: can't emulate rawmode for keycode 240 [ 2146.849187] keyboard: can't emulate rawmode for keycode 240 [ 2146.849209] keyboard: can't
Bug#657689: marked as done (e1000e Detected Hardware Unit Hang:)
Your message dated Sat, 6 Jul 2013 17:59:44 +0200 with message-id 20130706155944.GE12523@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #657689, regarding e1000e Detected Hardware Unit Hang: 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 ow...@bugs.debian.org immediately.) -- 657689: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657689 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-38 Linux version 2.6.32-5-xen-amd64 RAM 8GB Bug seems the same as #518182 and occurs on high traffic load. System automatically recovered after aprox. 50 minutes([1782786.812335] e1000e :00:19.0: eth0: Reset adapter) [1782779.812239] e1000e :00:19.0: eth0: Detected Hardware Unit Hang: [1782779.812241] TDH 46 [1782779.812242] TDT 4a [1782779.812243] next_to_use 4a [1782779.812244] next_to_clean46 [1782779.812245] buffer_info[next_to_clean]: [1782779.812247] time_stamp 11a8f9df5 [1782779.812248] next_to_watch46 [1782779.812249] jiffies 11a8f9ef2 [1782779.812250] next_to_watch.status 0 [1782779.812251] MAC Status 80280 [1782779.812252] PHY Status [1782779.812253] PHY 1000BASE-T Status [1782779.812254] PHY Extended Status [1782779.812256] PCI Status 10 [1782781.812247] e1000e :00:19.0: eth0: Detected Hardware Unit Hang: [1782781.812249] TDH 46 [1782781.812250] TDT 4a [1782781.812251] next_to_use 4a [1782781.812252] next_to_clean46 [1782781.812253] buffer_info[next_to_clean]: [1782781.812254] time_stamp 11a8f9df5 [1782781.812255] next_to_watch46 [1782781.812256] jiffies 11a8fa0e6 [1782781.812258] next_to_watch.status 0 [1782781.812259] MAC Status 80280 [1782781.812260] PHY Status [1782781.812261] PHY 1000BASE-T Status [1782781.812262] PHY Extended Status [1782781.812263] PCI Status 10 [1782783.812250] e1000e :00:19.0: eth0: Detected Hardware Unit Hang: [1782783.812252] TDH 46 [1782783.812253] TDT 4a [1782783.812254] next_to_use 4a [1782783.812255] next_to_clean46 [1782783.812256] buffer_info[next_to_clean]: [1782783.812257] time_stamp 11a8f9df5 [1782783.812259] next_to_watch46 [1782783.812260] jiffies 11a8fa2da [1782783.812261] next_to_watch.status 0 [1782783.812262] MAC Status 80280 [1782783.812263] PHY Status [1782783.812264] PHY 1000BASE-T Status [1782783.812265] PHY Extended Status [1782783.812266] PCI Status 10 [1782785.812687] e1000e :00:19.0: eth0: Detected Hardware Unit Hang: [1782785.812689] TDH 46 [1782785.812690] TDT 4a [1782785.812691] next_to_use 4a [1782785.812692] next_to_clean46 [1782785.812693] buffer_info[next_to_clean]: [1782785.812694] time_stamp 11a8f9df5 [1782785.812695] next_to_watch46 [1782785.812696] jiffies 11a8fa4ce [1782785.812698] next_to_watch.status 0 [1782785.812699] MAC Status 80280 [1782785.812700] PHY Status [1782785.812701] PHY 1000BASE-T Status [1782785.812702] PHY Extended Status [1782785.812703] PCI Status 10 [1782786.812020] [ cut here ] [1782786.812032] WARNING: at /build/buildd-linux-2.6_2.6.32-38-amd64-bk66e4/linu x-2.6-2.6.32/debian/build/source_amd64_xen/net/sched/sch_generic.c:261 dev_watch dog+0xe2/0x194() [1782786.812037] Hardware name: OptiPlex 755 [1782786.812040] NETDEV WATCHDOG: eth0 (e1000e): transmit queue 0 timed out [1782786.812043] Modules linked in: nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf _conntrack xt_physdev xt_multiport iptable_filter ip_tables x_tables xen_evtchn xenfs bridge stp loop i915 drm_kms_helper drm i2c_algo_bit snd_pcm snd_timer snd processor video soundcore snd_page_alloc button i2c_i801 psmouse pcspkr serio_r aw acpi_processor dcdbas i2c_core evdev output ext3 jbd mbcache dm_mod raid1 md_ mod sg sr_mod sd_mod cdrom crc_t10dif uhci_hcd 8139too ata_generic 8139cp mii at a_piix thermal thermal_sys e1000e libata ehci_hcd scsi_mod usbcore nls_base [las
Bug#375277: marked as done (double console messages about card reader)
Your message dated Sat, 6 Jul 2013 18:00:34 +0200 with message-id 20130706160034.GG12523@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #375277, regarding double console messages about card reader 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 ow...@bugs.debian.org immediately.) -- 375277: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=375277 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: hotplug Version: 0.0.20040329-25 Severity: minor At boot with a card reader with a CF card plugged in, hotplug gives double messages: $ dmesg|sort|uniq -D|uniq -c|perl -nae 'print if $F[0]==2' 2 SCSI device sdb: 250368 512-byte hdwr sectors (128 MB) 2 sdb: Mode Sense: 03 00 00 00 2 sdb: Write Protect is off 2 sdb: assuming drive cache: write through ---End Message--- ---BeginMessage--- Hi, your bug has been filed against the linux-2.6 source package and was filed for a kernel older than the recently released Debian 7.x / Wheezy with a severity less than important. We don't have the ressources to reproduce the complete backlog of all older kernel bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy or a more recent kernel from testing or unstable, please reopen the bug by sending a mail to cont...@bugs.debian.org with the following three commands included in the mail: reopen BUGNUMBER reassign BUGNUMBER src:linux thanks Cheers, Moritz---End Message---
Bug#509271: marked as done ([linux-image-2.6.26-1-686] vesafb as static interferes with other FB modules)
Your message dated Sat, 6 Jul 2013 18:00:34 +0200 with message-id 20130706160034.GG12523@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #509271, regarding [linux-image-2.6.26-1-686] vesafb as static interferes with other FB modules 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 ow...@bugs.debian.org immediately.) -- 509271: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=509271 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-1-686 Version: 2.6.26-12 Severity: minor Hello, I was trying to get my intelfb working, since I have: intelfb: Cannot reserve FB region. And, after some googling, I found that the problem is caused by vesafb being loaded *before*, and thus reserving the FB region I haven't tried a full kernel recompile yet, but, trying to remove vesafb, I found that it's not built as module: $ grep VESA /boot/config-2.6.26-1-686 CONFIG_FB_UVESA=m CONFIG_FB_VESA=y $ This is also present in 2.6.27-1~experimental.1~snapshot.12506 from kernel-archive.buildserver.net. I will try recompiling the kernel and making vesafb a module -- if that still doesn't work, I'll clone/retitle this bug for my specific problem. Kindly, David --- System information. --- Architecture: i386 Kernel: Linux 2.6.26-1-686 Debian Release: 5.0 500 unstablewww.debian-multimedia.org 500 unstableftp.de.debian.org 500 unstabledebian.corsac.net 500 kernel-dists-trunk kernel-archive.buildserver.net 1 experimentalwww.debian-multimedia.org 1 experimentaldebian.fastweb.it --- Package information. --- Depends (Version) | Installed =-+-= module-init-tools | 3.4-1 initramfs-tools(= 0.55) | 0.92n OR yaird(= 0.0.13) | OR linux-initramfs-tool | --- Output from package bug script --- -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ---End Message--- ---BeginMessage--- Hi, your bug has been filed against the linux-2.6 source package and was filed for a kernel older than the recently released Debian 7.x / Wheezy with a severity less than important. We don't have the ressources to reproduce the complete backlog of all older kernel bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy or a more recent kernel from testing or unstable, please reopen the bug by sending a mail to cont...@bugs.debian.org with the following three commands included in the mail: reopen BUGNUMBER reassign BUGNUMBER src:linux thanks Cheers, Moritz---End Message---
Bug#663707: marked as done (ALSA: Internal speakers don't shut up when I plug in a headset on ATI SBx00 Azalia (Intel HDA).)
Your message dated Sat, 6 Jul 2013 17:59:44 +0200 with message-id 20130706155944.GE12523@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #663696, regarding ALSA: Internal speakers don't shut up when I plug in a headset on ATI SBx00 Azalia (Intel HDA). 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 ow...@bugs.debian.org immediately.) -- 663696: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663696 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 3.2.7-1 Severity: normal Tags: upstream Dear Maintainer, I recently discovered that my internal speakers don't shut up when I plug in a headset on my laptop (eMachines G640) on ATI SBx00 Azalia (Intel HDA) [1002:4383]. This feature functions well on the same computer under Windows Seven, and DID FUNCTION in the past under Debian/GNU/Linux. I am unfortunate that I believe I cannot contribute much to debugging this trouble because of two things: - When I first witnessed this problem, I believed it was due to a hardware damage (jack plug) caused my me pulling the cable the wrong way. - Then, when I realized using Windows that the hardware is just fine, it was probably ages since the Linux bug first appeared, spannig multiple Linux versions for sure. Feel free to ask me for any tests and feedback, however. In hope my report will prove useful. Kind Regards, Valentin QUEQUET -- Package-specific info: ** Version: Linux version 3.2.0-1-amd64 (Debian 3.2.7-1) (debian-kernel@lists.debian.org) (gcc version 4.6.2 (Debian 4.6.2-16) ) #1 SMP Tue Feb 28 15:35:32 UTC 2012 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-1-amd64 root=UUID=33f066d5-b48c-457a-ad2b-0df0e19f6c0a ** Not tainted ** Kernel log: [34112.544599] pcieport :00:05.0: restoring config space at offset 0x7 (was 0x1f1, writing 0x21f1) [34112.544604] pcieport :00:05.0: restoring config space at offset 0x3 (was 0x1, writing 0x10008) [34112.544648] ahci :00:11.0: restoring config space at offset 0x1 (was 0x237, writing 0x2300407) [34112.544697] ohci_hcd :00:12.0: wake-up capability disabled by ACPI [34112.560119] ehci_hcd :00:12.2: BAR 0: set to [mem 0xd0506000-0xd05060ff] (PCI address [0xd0506000-0xd05060ff]) [34112.560148] ehci_hcd :00:12.2: restoring config space at offset 0x1 (was 0x2b0, writing 0x2b00013) [34112.560171] ehci_hcd :00:12.2: wake-up capability disabled by ACPI [34112.560175] ehci_hcd :00:12.2: PME# disabled [34112.560202] ohci_hcd :00:13.0: wake-up capability disabled by ACPI [34112.576118] ehci_hcd :00:13.2: BAR 0: set to [mem 0xd0506400-0xd05064ff] (PCI address [0xd0506400-0xd05064ff]) [34112.576147] ehci_hcd :00:13.2: restoring config space at offset 0x1 (was 0x2b0, writing 0x2b00013) [34112.576169] ehci_hcd :00:13.2: wake-up capability disabled by ACPI [34112.576174] ehci_hcd :00:13.2: PME# disabled [34112.576195] pci :00:14.0: restoring config space at offset 0x1 (was 0x2200403, writing 0x223) [34112.576204] pata_atiixp :00:14.1: restoring config space at offset 0xf (was 0x200, writing 0x20a) [34112.576215] pata_atiixp :00:14.1: restoring config space at offset 0x8 (was 0x1, writing 0x8451) [34112.576224] pata_atiixp :00:14.1: restoring config space at offset 0x3 (was 0x0, writing 0x4000) [34112.576230] pata_atiixp :00:14.1: restoring config space at offset 0x1 (was 0x220, writing 0x227) [34112.576258] snd_hda_intel :00:14.2: restoring config space at offset 0x1 (was 0x416, writing 0x412) [34112.576346] radeon :02:00.0: restoring config space at offset 0xf (was 0x1ff, writing 0x105) [34112.576360] radeon :02:00.0: restoring config space at offset 0x3 (was 0x80, writing 0x88) [34112.576398] snd_hda_intel :02:00.1: restoring config space at offset 0xf (was 0x2ff, writing 0x20b) [34112.576412] snd_hda_intel :02:00.1: restoring config space at offset 0x4 (was 0x4, writing 0xd0020004) [34112.576416] snd_hda_intel :02:00.1: restoring config space at offset 0x3 (was 0x80, writing 0x88) [34112.576421] snd_hda_intel :02:00.1: restoring config space at offset 0x1 (was 0x10, writing 0x13) [34112.576500] tg3 :03:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x8) [34112.576506] tg3 :03:00.0: restoring config space at offset 0x1 (was 0x10, writing 0x16) [34112.576550] ath9k :06:00.0: restoring config space at offset 0xf (was 0x1ff, writing 0x10a) [34112.576565] ath9k :06:00.0: restoring config space at offset 0x4 (was
Bug#663696: marked as done (ALSA: Internal speakers don't shut up when I plug in a headset on ATI SBx00 Azalia (Intel HDA).)
Your message dated Sat, 6 Jul 2013 17:59:44 +0200 with message-id 20130706155944.GE12523@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #663696, regarding ALSA: Internal speakers don't shut up when I plug in a headset on ATI SBx00 Azalia (Intel HDA). 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 ow...@bugs.debian.org immediately.) -- 663696: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663696 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 3.2.7-1 Severity: normal Dear Maintainer, I recently discovered that my internal speakers don't shut up when I plug in a headset on my laptop (eMachines G640) on ATI SBx00 Azalia (Intel HDA) [1002:4383]. This feature functions well on the same computer under Windows Seven, and DID FUNCTION in the past under Debian/GNU/Linux. I am unfortunate that I think I cannot contribute much to the debugging of this trouble because of two things: - When I first witnessed this problem, I believed it was due to a hardware damage (jack plug) caused my me pulling the cable the wrong way. - Then, when using Windows I realized that the hardware is just fine, it was probably ages since the Linux/ALSA bug first appeared, spannig multiple Linux versions for sure. Feel free to ask me for any test and feedback, however. In hope my report will prove useful. Kind Regards, Valentin QUEQUET -- Package-specific info: ** Version: Linux version 3.2.0-1-amd64 (Debian 3.2.7-1) (debian-kernel@lists.debian.org) (gcc version 4.6.2 (Debian 4.6.2-16) ) #1 SMP Tue Feb 28 15:35:32 UTC 2012 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-1-amd64 root=UUID=33f066d5-b48c-457a-ad2b-0df0e19f6c0a ** Not tainted ** Kernel log: [34112.544599] pcieport :00:05.0: restoring config space at offset 0x7 (was 0x1f1, writing 0x21f1) [34112.544604] pcieport :00:05.0: restoring config space at offset 0x3 (was 0x1, writing 0x10008) [34112.544648] ahci :00:11.0: restoring config space at offset 0x1 (was 0x237, writing 0x2300407) [34112.544697] ohci_hcd :00:12.0: wake-up capability disabled by ACPI [34112.560119] ehci_hcd :00:12.2: BAR 0: set to [mem 0xd0506000-0xd05060ff] (PCI address [0xd0506000-0xd05060ff]) [34112.560148] ehci_hcd :00:12.2: restoring config space at offset 0x1 (was 0x2b0, writing 0x2b00013) [34112.560171] ehci_hcd :00:12.2: wake-up capability disabled by ACPI [34112.560175] ehci_hcd :00:12.2: PME# disabled [34112.560202] ohci_hcd :00:13.0: wake-up capability disabled by ACPI [34112.576118] ehci_hcd :00:13.2: BAR 0: set to [mem 0xd0506400-0xd05064ff] (PCI address [0xd0506400-0xd05064ff]) [34112.576147] ehci_hcd :00:13.2: restoring config space at offset 0x1 (was 0x2b0, writing 0x2b00013) [34112.576169] ehci_hcd :00:13.2: wake-up capability disabled by ACPI [34112.576174] ehci_hcd :00:13.2: PME# disabled [34112.576195] pci :00:14.0: restoring config space at offset 0x1 (was 0x2200403, writing 0x223) [34112.576204] pata_atiixp :00:14.1: restoring config space at offset 0xf (was 0x200, writing 0x20a) [34112.576215] pata_atiixp :00:14.1: restoring config space at offset 0x8 (was 0x1, writing 0x8451) [34112.576224] pata_atiixp :00:14.1: restoring config space at offset 0x3 (was 0x0, writing 0x4000) [34112.576230] pata_atiixp :00:14.1: restoring config space at offset 0x1 (was 0x220, writing 0x227) [34112.576258] snd_hda_intel :00:14.2: restoring config space at offset 0x1 (was 0x416, writing 0x412) [34112.576346] radeon :02:00.0: restoring config space at offset 0xf (was 0x1ff, writing 0x105) [34112.576360] radeon :02:00.0: restoring config space at offset 0x3 (was 0x80, writing 0x88) [34112.576398] snd_hda_intel :02:00.1: restoring config space at offset 0xf (was 0x2ff, writing 0x20b) [34112.576412] snd_hda_intel :02:00.1: restoring config space at offset 0x4 (was 0x4, writing 0xd0020004) [34112.576416] snd_hda_intel :02:00.1: restoring config space at offset 0x3 (was 0x80, writing 0x88) [34112.576421] snd_hda_intel :02:00.1: restoring config space at offset 0x1 (was 0x10, writing 0x13) [34112.576500] tg3 :03:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x8) [34112.576506] tg3 :03:00.0: restoring config space at offset 0x1 (was 0x10, writing 0x16) [34112.576550] ath9k :06:00.0: restoring config space at offset 0xf (was 0x1ff, writing 0x10a) [34112.576565] ath9k :06:00.0: restoring config space at offset 0x4 (was 0x4,
Bug#657123: marked as done (USB modem hotplugging no longer works.)
Your message dated Sat, 6 Jul 2013 17:59:44 +0200 with message-id 20130706155944.GE12523@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #657123, regarding USB modem hotplugging no longer works. 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 ow...@bugs.debian.org immediately.) -- 657123: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657123 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: udev Version: 175-3 Hotplugging of USB modems no longer works. Earlier, when inserting a usb modem, devices /dev/ttyUSB* used to appear automatically, now I have to manually modprobe usbserial with the correct vendor, string values to get /dev/ttyUSB. I'm not sure this this's a problem with udev or usb_modeswitch (it does insert usbserial after switching right?). ---End Message--- ---BeginMessage--- Hi, your bug has been filed against the linux-2.6 source package and was filed for a kernel older than the recently released Debian 7.x / Wheezy with a severity less than important. We don't have the ressources to reproduce the complete backlog of all older kernel bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy or a more recent kernel from testing or unstable, please reopen the bug by sending a mail to cont...@bugs.debian.org with the following three commands included in the mail: reopen BUGNUMBER reassign BUGNUMBER src:linux thanks Cheers, Moritz---End Message---
Bug#670797: marked as done (linux-image-3.2.0-2-686-pae: CPU load not being distributed)
Your message dated Sat, 6 Jul 2013 18:00:09 +0200 with message-id 20130706160009.GF12523@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #670797, regarding linux-image-3.2.0-2-686-pae: CPU load not being distributed 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 ow...@bugs.debian.org immediately.) -- 670797: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670797 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 3.2.15-1 Severity: important Dear Maintainer, I'm seeing some unusual behaviour in my 4 cores desktop and can't figure out what's going on. Currently I'm using latest 'testing' kernel, but I've noticed this behavior in all 3.x debian stock kernel series. Even when the kernels have SMP enabled, only one of my 4 cores gets all the CPU affinity, distributing the load only when it's at 100%. I have checked for SMP_default_afinity, but it's in F (default), which I've read it's ok. I recently installed 'sar' to get more detailed information, but here are the outputs from mpstat and /proc/interrupts, they clearly show processing differences among all CPU cores: $ mpstat -P ALL Linux 3.2.0-2-686-pae (frankie) 29/04/12_i686_ (4 CPU) 01:03:26 CPU%usr %nice%sys %iowait%irq %soft %steal %guest %idle 01:03:26 all2,68 13,793,127,240,000,560,00 0,00 72,61 01:03:26 01,030,830,775,940,000,000,00 0,00 91,42 01:03:26 10,650,680,515,210,000,010,00 0,00 92,95 01:03:26 20,751,100,635,760,000,170,00 0,00 91,60 01:03:26 38,28 52,46 10,55 12,060,002,050,00 0,00 14,60 $ cat /proc/interrupts CPU0 CPU1 CPU2 CPU3 0: 87287 12806 143287 IO-APIC-edge timer 1: 0 3153 3351 IO-APIC-edge i8042 4: 0 0 0 2 IO-APIC-edge 6: 0 0 38 1334 IO-APIC-edge floppy 7: 1 0 0 0 IO-APIC-edge parport0 8: 0 0 2 54 IO-APIC-edge rtc0 9: 0 0 0 0 IO-APIC-fasteoi acpi 14: 1100 2774 46679 IO-APIC-edge pata_atiixp 15: 0 0 0 0 IO-APIC-edge pata_atiixp 16: 1 23816 32680 IO-APIC-fasteoi ohci_hcd:usb3, ohci_hcd:usb4, snd_hda_intel 17: 0 3209 21995 IO-APIC-fasteoi ehci_hcd:usb1 18: 0 0 1 52 IO-APIC-fasteoi ohci_hcd:usb5, ohci_hcd:usb6, ohci_hcd:usb7, fglrx[0]@PCI:1:5:0 19: 0 0 0 19 IO-APIC-fasteoi ehci_hcd:usb2, snd_hda_intel 21: 1210 7109 621617 IO-APIC-fasteoi ath 22: 4106 3942 112678 IO-APIC-fasteoi ahci 42: 0 0 0 0 PCI-MSI-edge eth0 NMI: 9 8 9137 Non-maskable interrupts LOC: 57319 43568 42688 624135 Local timer interrupts SPU: 0 0 0 0 Spurious interrupts PMI: 9 8 9137 Performance monitoring interrupts IWI: 0 0 0 0 IRQ work interrupts RES: 228406 119635 175374 296599 Rescheduling interrupts CAL: 4245 4228 4225539 Function call interrupts TLB: 2111 2331 2262 4288 TLB shootdowns TRM: 0 0 0 0 Thermal event interrupts THR: 0 0 0 0 Threshold APIC interrupts MCE: 0 0 0 0 Machine check exceptions MCP: 7 7 7 7 Machine check polls ERR: 1 MIS: 0 This is my processor: # cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 16 model : 2 model name : AMD Phenom(tm) 9600 Quad-Core Processor stepping: 2 microcode : 0x183 cpu MHz : 2300.000 cache size : 512 KB physical id : 0 siblings: 4 core id : 0 cpu cores : 4 apicid : 0 initial apicid : 0 fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level
Bug#673496: marked as done ([lenny - squeeze regression] wifi broken (?))
Your message dated Sat, 6 Jul 2013 18:00:09 +0200 with message-id 20130706160009.GF12523@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #673496, regarding [lenny - squeeze regression] wifi broken (?) 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 ow...@bugs.debian.org immediately.) -- 673496: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673496 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.32-5-amd64 Version: 2.6.32-27 When I use the ath5k driver, it fails to resolve an IP address from using the dhclient command. Here are the commands that I entered: ifconfig eth0 down ifconfig wlan0 up iwlist wlan0 scan iwconfig wlan0 essid default dhclient wlan0 These steps worked with Lenny. The card that I'm using is an SMCWPCI-G based Atheros card, which I believe uses the AR5007G chipset. Output from dmesg | grep ath5k: [5.689292] ath5k :00:09.0: PCI INT A - GSI 17 (level, low) - IRQ 17 [5.689353] ath5k :00:09.0: registered as 'phy0' [6.416794] ath5k phy0: Atheros AR2413 chip found (MAC: 0x78, PHY: 0x45) Output from kern | grep ath5k: Nov 22 14:12:05 debian-box kernel: [5.621466] ath5k :00:09.0: PCI INT A - GSI 17 (level, low) - IRQ 17 Nov 22 14:12:05 debian-box kernel: [5.621531] ath5k :00:09.0: registered as 'phy0' Nov 22 14:12:05 debian-box kernel: [6.231139] ath5k phy0: Atheros AR2413 chip found (MAC: 0x78, PHY: 0x45) Nov 22 17:19:45 debian-box kernel: [5.766165] ath5k :00:09.0: PCI INT A - GSI 17 (level, low) - IRQ 17 Nov 22 17:19:45 debian-box kernel: [5.766235] ath5k :00:09.0: registered as 'phy0' Nov 22 17:19:45 debian-box kernel: [6.469400] ath5k phy0: Atheros AR2413 chip found (MAC: 0x78, PHY: 0x45) Nov 22 19:34:41 debian-box kernel: [5.689279] ath5k :00:09.0: PCI INT A - GSI 17 (level, low) - IRQ 17 Nov 22 19:34:41 debian-box kernel: [5.689345] ath5k :00:09.0: registered as 'phy0' Nov 22 19:34:41 debian-box kernel: [6.299683] ath5k phy0: Atheros AR2413 chip found (MAC: 0x78, PHY: 0x45) Nov 22 19:45:10 debian-box kernel: [5.689292] ath5k :00:09.0: PCI INT A - GSI 17 (level, low) - IRQ 17 Nov 22 19:45:10 debian-box kernel: [5.689353] ath5k :00:09.0: registered as 'phy0' Nov 22 19:45:10 debian-box kernel: [6.416794] ath5k phy0: Atheros AR2413 chip found (MAC: 0x78, PHY: 0x45) Output from kern | grep wlan0: Nov 22 14:14:52 debian-box kernel: [ 176.720056] ADDRCONF(NETDEV_UP): wlan0: link is not ready Nov 22 14:14:54 debian-box kernel: [ 178.558439] wlan0: direct probe to AP 00:15:e9:65:fb:86 (try 1) Nov 22 14:14:54 debian-box kernel: [ 178.756014] wlan0: direct probe to AP 00:15:e9:65:fb:86 (try 2) Nov 22 14:14:54 debian-box kernel: [ 178.956008] wlan0: direct probe to AP 00:15:e9:65:fb:86 (try 3) Nov 22 14:14:55 debian-box kernel: [ 179.156007] wlan0: direct probe to AP 00:15:e9:65:fb:86 timed out Nov 22 19:35:56 debian-box kernel: [ 84.311427] ADDRCONF(NETDEV_UP): wlan0: link is not ready Nov 22 19:37:32 debian-box kernel: [ 180.328121] wlan0: direct probe to AP 00:15:e9:65:fb:86 (try 1) Nov 22 19:37:32 debian-box kernel: [ 180.528011] wlan0: direct probe to AP 00:15:e9:65:fb:86 (try 2) Nov 22 19:37:32 debian-box kernel: [ 180.602991] wlan0: direct probe responded Nov 22 19:37:32 debian-box kernel: [ 180.602995] wlan0: authenticate with AP 00:15:e9:65:fb:86 (try 1) Nov 22 19:37:32 debian-box kernel: [ 180.86] wlan0: authenticate with AP 00:15:e9:65:fb:86 (try 2) Nov 22 19:37:32 debian-box kernel: [ 181.07] wlan0: authenticate with AP 00:15:e9:65:fb:86 (try 3) Nov 22 19:37:33 debian-box kernel: [ 181.26] wlan0: authentication with AP 00:15:e9:65:fb:86 timed out The only issue I can see is in the last result, which is reporting authentication problems. However, I really don't know of any way of correcting the problem. I did, however, test the ath5k module against two other distros, Fedora 14, and Ubuntu 10.10, which use the 2.6.35 kernel and both were able to connect successfully. So this may be an upstream problem that was corrected, but wasn't ported back to this kernel. I don't know for sure because I'm not a kernel developer. Anyone willing to take a stab at it? ---End Message--- ---BeginMessage--- Hi, your bug has been filed against the linux-2.6 source package and was filed for a kernel older than the recently released Debian 7.x / Wheezy with a severity less than important. We don't have the ressources to reproduce the complete backlog of all older kernel bugs, so we're closing this bug for now. If you can reproduce the
Bug#678443: marked as done (Hard lockups due to lockup-detector (NMIs) on muti-Pentium-3 SMP systems on all kernel builds since 2.6.38)
Your message dated Sat, 6 Jul 2013 18:00:34 +0200 with message-id 20130706160034.GG12523@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #678443, regarding Hard lockups due to lockup-detector (NMIs) on muti-Pentium-3 SMP systems on all kernel builds since 2.6.38 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 ow...@bugs.debian.org immediately.) -- 678443: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678443 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.38-5 Hello! (Backgrund information: the motivation for this bug report comes from bug 639331 which already seems to have dug more deeply into the version introducing this berhaviour) The NMI watchdog mechanism (as I know today it is the probable source) has given me serious headaches since Debian kernel 2.6.38 was released. I cannot tell it definitely yet as it is an intermittent error in my case which may take up to a week to appear once, and I disabled the NMI watchdog mechanism by adding nowatchdog not until yesterday (20120620) when I came across the bug report mentioned above. A short summary of my problem: - among several uniprocessor systems with Debian and Ubuntu, I am running several older multiprocessor servers (IBM Netfinity 5000 (Dual-P3 (Coppermine)), IBM Netfinity 7000 M10 (Quad-P3-Xeon (Tanner)) and IBM xSeries 232 (Dual-P3 (Tualatin))) with Debian (using testing as rolling release after a long time with lenny) - the systems were running rock-solid up to and including the Debian-packaged kernel 2.6.32 (all sub-versions). - when Debian-packaged kernel 2.6.38 came out, my problem started and appeared mainly on the Netfinity 5000 (but less often also on the other systems): after running continuously for one to eight days, the system suddenly locked up hard, in most cases it was just idle when this happened - this lockup was a classic livelock which can be diagnosed nicely on these IBM machines as they have activity LEDs for each CPU which glowed with identical brightness and without any modulation, so both CPUs were switching between each other with short cycles - when comparing the basic system data and properties, I noticed a difference between kernel 2.6.32 and 2.6.38: the latter caused a continuously rising NMI count on each CPU which could not be seen with 2.6.32! Today I know where these NMIs are coming from: it is the watchdog mechanism also causing your laptop problem - I hoped that the problem might disappear with kernel 3.4 as there were a few discussions on LKML about several livelocks/deadlocks related to timers and the like (the config change concerning the lockup detector which got enabled from 2.6.32 to 2.6.38 remained unnoticed for me) - as you see it on the laptop, this lockup NEVER allows to get any message out via the debugging mechanisms, not even by attaching a serial cable and logging the console output on a second machine - now using kernel 3.4.2, the problem still exists, but has changed a bit in its consequences - instead of a livelock, it is a deadlock in most cases and activity stays on a single CPU, sometimes even causing a reboot instead of staying locked up - on a German forum I described the problem, but nobody could point me to this lockup-detector change in the kernel config though I posted this significant change from no NMIs to continuous NMIs. Here we see again how bad the documentation of open-source projects sometimes is cared about... even when configuring a kernel, the config help says that the nmi watchdog had to be enabled consciously by a boot parameter - in fact it seems to be activated by default as soon as SMP code is loaded and/or an APIC is detected (but though the presence of an APIC, I have not seen those NMIs on my uniprocessor P3 machines yet). Here is a link to my description on the German debianforum: http://debianforum.de/forum/viewtopic.php?f=33t=134210 I would like to report the bug to http://bugzilla.kernel.org if it has not yet been done by someone else. Therefore it would be great if you could give me a short note if you have reported it already. Basically I think this mechanism has its bugs and/or wrong assumptions on some machines and should undergo a critical review. I'm wondering if there are more people in the world getting set up by strange lockups of their machines which are wrongly diagnosed as hardware errors etc. Thanks and best regards, Hans-Juergen ---End Message--- ---BeginMessage--- Hi, your bug has been filed against the linux-2.6 source package
Bug#674424: marked as done (linux-image-3.2.0-0.bpo.2-686-pae: hangs requiring power cycle)
Your message dated Sat, 6 Jul 2013 18:00:09 +0200 with message-id 20130706160009.GF12523@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #674424, regarding linux-image-3.2.0-0.bpo.2-686-pae: hangs requiring power cycle 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 ow...@bugs.debian.org immediately.) -- 674424: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674424 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 3.2.15-1~bpo60+1 Severity: normal *** Please type your report below this line *** We are experiencing periodic lock-ups since upgrading to the latest backport kernel. Its happened two nights in a row now, and previously happened two days before. The machine is a relatively heavily I/O loaded backup server. Please find below the last two serial console outputs captured after the machine was hung. [1249211.944027] Pid: 3978, comm: kworker/1:1 Not tainted 3.2.0-0.bpo.2-686-pae #1 [1249211.944027] Call Trace: [1249211.944027] [c103b929] ? warn_slowpath_common+0x6a/0x7b [1249211.944027] [c107d600] ? watchdog_overflow_callback+0x81/0x8d [1249211.944027] [c107d57f] ? watchdog_timer_fn+0x12d/0x12d [1249211.944027] [c103b9a0] ? warn_slowpath_fmt+0x28/0x2c [1249211.944027] [c107d600] ? watchdog_overflow_callback+0x81/0x8d [1249211.944027] [c109b3c3] ? __perf_event_overflow+0x159/0x1ce [1249211.944027] [c1015c2b] ? x86_perf_event_set_period+0x1af/0x1b9 [1249211.944027] [c109b857] ? perf_event_overflow+0xd/0xf [1249211.944027] [c1017597] ? p4_pmu_handle_irq+0x14b/0x198 [1249211.944027] [c1037acd] ? check_preempt_wakeup+0xf3/0x14f [1249211.944027] [c12d74a0] ? perf_event_nmi_handler+0x14/0x15 [1249211.944027] [c12d6ee8] ? do_nmi+0x83/0x2f1 [1249211.944027] [c116d9ac] ? radix_tree_tag_clear+0x77/0xe2 [1249211.944027] [c12d67dc] ? nmi_stack_correct+0x2f/0x34 [1249211.944027] [c1058381] ? ktime_get+0x24/0x98 [1249211.944027] [c10a35c2] ? test_clear_page_writeback+0xb5/0xbe [1249211.944027] [c1054fea] ? hrtimer_interrupt+0x3b/0x1ed [1249211.944027] [f876fa6d] ? ext4_end_bio+0x1b6/0x21e [ext4] [1249211.944027] [c10203a2] ? smp_apic_timer_interrupt+0x64/0x73 [1249211.944027] [c12d64f1] ? apic_timer_interrupt+0x31/0x38 [1249211.944027] [c11f71d4] ? add_timer_randomness+0x5f/0xcc [1249211.944027] [c115b42b] ? blk_update_bidi_request+0x43/0x4c [1249211.944027] [c115b448] ? blk_end_bidi_request+0x14/0x47 [1249211.944027] [c115b4a6] ? blk_end_request+0x7/0x9 [1249211.944027] [f8260f6f] ? scsi_io_completion+0x1b4/0x41a [scsi_mod] [1249211.944027] [f825b40a] ? scsi_finish_command+0xa1/0xb9 [scsi_mod] [1249211.944027] [c10407f1] ? irq_enter+0x49/0x49 [1249211.944027] [c115efb1] ? blk_done_softirq+0x51/0x5d [1249211.944027] [c104088c] ? __do_softirq+0x9b/0x14e [1249211.944027] [c10407f1] ? irq_enter+0x49/0x49 [1249211.944027] IRQ [c10406d4] ? irq_exit+0x2f/0x91 [1249211.944027] [c100d486] ? do_IRQ+0x73/0x84 [1249211.944027] [c12daa30] ? common_interrupt+0x30/0x38 [1249211.944027] [c11500d8] ? crypto_alg_tested+0x167/0x170 [1249211.944027] [f82a4cea] ? serpent_encrypt+0xb77/0xd79 [serpent] [1249211.944027] [f8243214] ? crypt+0x92/0xe0 [xts] [1249211.944027] [f82432de] ? encrypt+0x3b/0x41 [xts] [1249211.944027] [f82a4173] ? serpent_setkey+0x2173/0x2173 [serpent] [1249211.944027] [f82a4173] ? serpent_setkey+0x2173/0x2173 [serpent] [1249211.944027] [c1151af3] ? async_encrypt+0x2f/0x35 [1249211.944027] [f8251cab] ? crypt_convert+0x21f/0x2b7 [dm_crypt] [1249211.944027] [f825202a] ? kcryptd_crypt+0x2e7/0x2fb [dm_crypt] [1249211.944027] [c104e814] ? process_one_work+0x17b/0x258 [1249211.944027] [f8251d43] ? crypt_convert+0x2b7/0x2b7 [dm_crypt] [1249211.944027] [c104e9e4] ? worker_thread+0xf3/0x1f4 [1249211.944027] [c104e8f1] ? process_one_work+0x258/0x258 [1249211.944027] [c10517ab] ? kthread+0x63/0x68 [1249211.944027] [c1051748] ? kthread_worker_fn+0x114/0x114 [1249211.944027] [c12daa3e] ? kernel_thread_helper+0x6/0x10 [1249211.944027] ---[ end trace 8671cd0afe3ecc53 ]--- [1249211.944027] [ cut here ] [1249211.944027] WARNING: at /build/buildd-linux-2.6_3.2.15-1~bpo60+1-i386-e lCmeb/linux-2.6-3.2.15/debian/build/source_i386_none/kernel/watchdog.c:241 watchdog_overflow_callback+0x81/0x8d() [1249211.944027] Hardware name: X5DP8 [1249211.944027] Watchdog detected hard LOCKUP on cpu 3 [1249211.944027] Modules linked in: btrfs zlib_deflate crc32c libcrc32c ufs qnx4 hfsplus hfs minix ntfs vfat msdos fat jfs xfs reiserfs ext2 joydev st ext4 jbd2 crc16 loop snd_pcm parport_pc snd_timer snd soundcore snd_page_alloc
Bug#670634: marked as done (linux-image-2.6.32-5-686: SV266A with VIA KT266A: suspend to RAM not available)
Your message dated Sat, 6 Jul 2013 18:00:09 +0200 with message-id 20130706160009.GF12523@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #670634, regarding linux-image-2.6.32-5-686: SV266A with VIA KT266A: suspend to RAM not available 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 ow...@bugs.debian.org immediately.) -- 670634: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670634 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-41squeeze2 Severity: normal Dear Debian folks, the option suspend to RAM is not available on the motherboard SV266A with a VIA KT266A(?) chipset [1]. $ echo mem | sudo tee /sys/power/state mem tee: /sys/power/state: No such device $ ls /sys/power/ diskimage_size pm_test resume state $ ls /sys/power/state /sys/power/state $ sudo su # echo mem /sys/power/state bash: echo: Schreibfehler: Kein passendes Gerät gefunden. I looked around in the BIOS and the option *ACPI functions* is set to *Enabled*. There is also an option *Suspend Mode* which I can set to *Disable* or to a number of minutes. But I guess I do not want the BIOS to suspend my system but using the operating system for that task. Is Linux looking at the ACPI tables and they are wrong in this case? Can I force suspend to RAM somehow to test it? Thanks, Paul [1] http://lists.freedesktop.org/archives/pm-utils/2010-June/002176.html -- Package-specific info: ** Version: Linux version 2.6.32-5-686 (Debian 2.6.32-41squeeze2) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Mon Mar 26 05:20:33 UTC 2012 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-686 root=UUID=582643ad-cb1e-4a01-bca4-5c8ad8562447 ro parport=0 quiet ** Not tainted ** Kernel log: [1.880840] Uniform CD-ROM driver Revision: 3.20 [1.881684] sr 0:0:1:0: Attached scsi CD-ROM sr0 [1.886508] sr1: scsi3-mmc drive: 40x/40x writer cd/rw xa/form2 cdda tray [1.886770] sr 1:0:0:0: Attached scsi CD-ROM sr1 [1.909648] sd 0:0:0:0: Attached scsi generic sg0 type 0 [1.910146] sr 0:0:1:0: Attached scsi generic sg1 type 5 [1.911441] sr 1:0:0:0: Attached scsi generic sg2 type 5 [1.940052] usb 2-1: new low speed USB device using uhci_hcd and address 2 [2.106022] usb 2-1: New USB device found, idVendor=1241, idProduct=1122 [2.106030] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [2.106235] usb 2-1: configuration #1 chosen from 1 choice [2.132546] usbcore: registered new interface driver hiddev [2.151697] input: HID 1241:1122 as /devices/pci:00/:00:10.0/usb2/2-1/2-1:1.0/input/input0 [2.151983] generic-usb 0003:1241:1122.0001: input,hidraw0: USB HID v1.00 Mouse [HID 1241:1122] on usb-:00:10.0-1/input0 [2.152093] usbcore: registered new interface driver usbhid [2.152458] usbhid: v2.6:USB HID core driver [2.348047] usb 2-2: new low speed USB device using uhci_hcd and address 3 [2.527930] usb 2-2: New USB device found, idVendor=046d, idProduct=c30f [2.527939] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [2.527944] usb 2-2: Product: Logitech USB Keyboard [2.527948] usb 2-2: Manufacturer: Logitech [2.528216] usb 2-2: configuration #1 chosen from 1 choice [2.545744] input: Logitech Logitech USB Keyboard as /devices/pci:00/:00:10.0/usb2/2-2/2-2:1.0/input/input1 [2.545953] generic-usb 0003:046D:C30F.0002: input,hidraw1: USB HID v1.10 Keyboard [Logitech Logitech USB Keyboard] on usb-:00:10.0-2/input0 [2.580104] input: Logitech Logitech USB Keyboard as /devices/pci:00/:00:10.0/usb2/2-2/2-2:1.1/input/input2 [2.580237] generic-usb 0003:046D:C30F.0003: input,hidraw2: USB HID v1.10 Device [Logitech Logitech USB Keyboard] on usb-:00:10.0-2/input1 [2.627161] PM: Starting manual resume from disk [2.627172] PM: Resume from partition 8:5 [2.627175] PM: Checking hibernation image. [2.648921] PM: Error -22 checking image file [2.648924] PM: Resume from disk failed. [2.735754] EXT4-fs (sda1): mounted filesystem with ordered data mode [ 18.393028] udev[329]: starting version 164 [ 18.701813] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3 [ 18.701831] ACPI: Power Button [PWRB] [ 18.701952] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input4 [ 18.701965] ACPI: Sleep Button [SLPB] [ 18.702103] input: Power Button as
Bug#685200: marked as done (base: ftdi_sio stop working after several hours)
Your message dated Sat, 6 Jul 2013 18:00:34 +0200 with message-id 20130706160034.GG12523@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #685200, regarding base: ftdi_sio stop working after several hours 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 ow...@bugs.debian.org immediately.) -- 685200: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685200 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: base Severity: grave Justification: renders package unusable I control a four relays board throught an USB cable connected to a Xen Dom0 running Debian 6.0.5. It works great: I can switch on and off the relays through some echo into /dev/ttyUSB0 (echo -e \xff\x01\x01 /dev/ttyUSB0). I added a crontab to send such echo every 15 minutes. It works great at the begining. But after some hours, I get this error message in /var/log/syslog each time I echo to ttyUSB0: #-8--8-- Aug 18 09:04:32 zen kernel: [1677762.865609] ftdi_sio ttyUSB0: Unable to write latency timer: -62 Aug 18 09:04:32 zen kernel: [1677762.869623] ftdi_sio ttyUSB0: ftdi_set_termios FAILED to set databits/stopbits/parity Aug 18 09:04:32 zen kernel: [1677762.871604] ftdi_sio ttyUSB0: ftdi_set_termios urb failed to set baudrate Aug 18 09:04:32 zen kernel: [1677762.875622] ftdi_sio ttyUSB0: urb failed to clear flow control Aug 18 09:04:32 zen kernel: [1677762.879604] ftdi_sio ttyUSB0: urb failed to clear flow control Aug 18 09:04:32 zen kernel: [1677762.881620] ftdi_sio ttyUSB0: error from flowcontrol urb Aug 18 09:04:32 zen kernel: [1677762.885623] ftdi_sio ttyUSB0: Unable to write latency timer: -62 Aug 18 09:04:32 zen kernel: [1677762.889637] ftdi_sio ttyUSB0: ftdi_set_termios FAILED to set databits/stopbits/parity Aug 18 09:04:32 zen kernel: [1677762.891622] ftdi_sio ttyUSB0: ftdi_set_termios urb failed to set baudrate Aug 18 09:04:32 zen kernel: [1677762.895616] ftdi_sio ttyUSB0: urb failed to clear flow control Aug 18 09:04:32 zen kernel: [1677762.903189] ftdi_sio ttyUSB0: error from flowcontrol urb #-8--8-- I have to unplug the USB cable and plug it back to get it to work again. Unplug: #-8--8-- Aug 18 09:04:46 zen kernel: [167.053078] usb 3-3: USB disconnect, address 17 Aug 18 09:04:46 zen kernel: [167.053233] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 Aug 18 09:04:46 zen kernel: [167.053248] ftdi_sio 3-3:1.0: device disconnected #-8--8-- Plug: #-8--8-- Aug 18 09:04:49 zen kernel: [169.816320] usb 3-3: new full speed USB device using ohci_hcd and address 18 Aug 18 09:04:49 zen kernel: [169.998248] usb 3-3: New USB device found, idVendor=0403, idProduct=6001 Aug 18 09:04:49 zen kernel: [169.998260] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Aug 18 09:04:49 zen kernel: [169.998270] usb 3-3: Product: FT232R USB UART Aug 18 09:04:49 zen kernel: [169.998278] usb 3-3: Manufacturer: FTDI Aug 18 09:04:49 zen kernel: [169.998284] usb 3-3: SerialNumber: AH01IAGC Aug 18 09:04:49 zen kernel: [1677780.006100] usb 3-3: configuration #1 chosen from 1 choice Aug 18 09:04:49 zen kernel: [1677780.013642] ftdi_sio 3-3:1.0: FTDI USB Serial Device converter detected Aug 18 09:04:49 zen kernel: [1677780.013712] usb 3-3: Detected FT232RL Aug 18 09:04:49 zen kernel: [1677780.013720] usb 3-3: Number of endpoints 2 Aug 18 09:04:49 zen kernel: [1677780.013728] usb 3-3: Endpoint 1 MaxPacketSize 64 Aug 18 09:04:49 zen kernel: [1677780.013736] usb 3-3: Endpoint 2 MaxPacketSize 64 Aug 18 09:04:49 zen kernel: [1677780.013744] usb 3-3: Setting MaxPacketSize 64 Aug 18 09:04:49 zen kernel: [1677780.015289] usb 3-3: FTDI USB Serial Device converter now attached to ttyUSB0 #-8--8-- The first times I echo to ttyUSB0 after plugin it, the log shows this: #-8--8-- Aug 18 09:09:36 zen kernel: [1678067.020400] hub 3-0:1.0: port 3 disabled by hub (EMI?), re-enabling... Aug 18 09:09:36 zen kernel: [1678067.020439] usb 3-3: USB disconnect, address 21 Aug 18 09:09:36 zen kernel: [1678067.020793] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 Aug 18 09:09:36 zen kernel: [1678067.020839] ftdi_sio
Processed: Re: Closing
Processing control commands:
reopen -1
Bug #584656 {Done: Moritz Mühlenhoff j...@inutil.org} [linux-2.6]
linux-image-2.6.32-3-amd64: caps lock key doesn't toggle caps lock LED on
virtual console
Bug reopened
Ignoring request to alter fixed versions of bug #584656 to the same values
previously set
reassign -1 src:linux
Bug #584656 [linux-2.6] linux-image-2.6.32-3-amd64: caps lock key doesn't
toggle caps lock LED on virtual console
Bug reassigned from package 'linux-2.6' to 'src:linux'.
No longer marked as found in versions 2.6.32-9.
Ignoring request to alter fixed versions of bug #584656 to the same values
previously set
--
584656: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584656
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/handler.s.b584656.137312785619758.transcr...@bugs.debian.org
Bug#584656: Closing
Control: reopen -1 Control: reassign -1 src:linux On Sat, 2013-07-06 at 18:00 +0200, Moritz Mühlenhoff wrote: We don't have the ressources to reproduce the complete backlog of all older kernel bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy or a more recent kernel from testing or unstable, please reopen the bug by sending a mail to cont...@bugs.debian.org with the following three commands included in the mail: I can reproduce this with linux-image-3.10-rc7-amd64 on a completely different laptop (Thinkpad X201t vs Dell Inspiron). I guess it is a general problem with Linux on laptops. -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Processed: tagging 705619
Processing commands for cont...@bugs.debian.org:
tags 705619 + pending
Bug #705619 {Done: Ben Hutchings b...@decadent.org.uk} [src:linux] The
package bug script ... exited with an error status (probably due to 'cat:
/proc/asound/cards: No such file or directory')
Added tag(s) pending.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
705619: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705619
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/handler.s.c.137313203411723.transcr...@bugs.debian.org
Processed: tagging 702641
Processing commands for cont...@bugs.debian.org:
tags 702641 + pending
Bug #702641 {Done: Ben Hutchings b...@decadent.org.uk} [src:linux] ia64,
wrong asm register contraints in the futex implementation
Added tag(s) pending.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
702641: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702641
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/handler.s.c.137313199310851.transcr...@bugs.debian.org
Processed: tagging 703607
Processing commands for cont...@bugs.debian.org:
tags 703607 + pending
Bug #703607 {Done: Ben Hutchings b...@decadent.org.uk} [src:linux] Please
include Cypress PS/2 Trackpad driver in linux-image-3.2.0-*
Added tag(s) pending.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
703607: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703607
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/handler.s.c.137313202311652.transcr...@bugs.debian.org
Processed: tagging 465823
Processing commands for cont...@bugs.debian.org:
tags 465823 + pending
Bug #465823 {Done: Ben Hutchings b...@decadent.org.uk} [src:linux] slrn:
bizaare deadlock if ctrl-s pressed when composing a message
Ignoring request to alter tags of bug #465823 to the same tags previously set
thanks
Stopping processing here.
Please contact me if you need assistance.
--
465823: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=465823
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/handler.s.c.137313201711458.transcr...@bugs.debian.org
Processed: tagging 707047
Processing commands for cont...@bugs.debian.org:
tags 707047 + pending
Bug #707047 {Done: Ben Hutchings b...@decadent.org.uk} [src:linux] Lockup and
possible hardware damage on VIA EPIA-PD motherboard
Added tag(s) pending.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
707047: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707047
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/handler.s.c.137313204611807.transcr...@bugs.debian.org
Processed: tagging 704933
Processing commands for cont...@bugs.debian.org:
tags 704933 + pending
Bug #704933 {Done: Ben Hutchings b...@decadent.org.uk}
[linux-image-3.2.0-4-amd64] linux-image-3.2.0-4-amd64:amd64: system hangs when
initializing primary video card (3.2.39-2 - 3.2.41-2 regression)
Added tag(s) pending.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
704933: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704933
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/handler.s.c.137313198710791.transcr...@bugs.debian.org
Processed: tagging 700333
Processing commands for cont...@bugs.debian.org:
tags 700333 + pending
Bug #700333 {Done: Ben Hutchings b...@decadent.org.uk} [src:linux]
linux-image-3.7-trunk-amd64: Suspend to disk broken
Added tag(s) pending.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
700333: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700333
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/handler.s.c.137313200510922.transcr...@bugs.debian.org
Processed: tagging 702639
Processing commands for cont...@bugs.debian.org:
tags 702639 + pending
Bug #702639 {Done: Ben Hutchings b...@decadent.org.uk} [src:linux] ia64,
wrong asm register contraints in the kvm implementation
Added tag(s) pending.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
702639: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702639
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/handler.s.c.137313199810877.transcr...@bugs.debian.org
Processed: tagging 705655
Processing commands for cont...@bugs.debian.org:
tags 705655 + pending
Bug #705655 {Done: Ben Hutchings b...@decadent.org.uk} [src:linux] iwlwifi
requests unpackaged firmware blob iwlwifi-6000g2a-6.ucode
Added tag(s) pending.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
705655: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705655
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/handler.s.c.137313202911690.transcr...@bugs.debian.org
Processed: tagging 661860
Processing commands for cont...@bugs.debian.org:
tags 661860 + pending
Bug #661860 {Done: Ben Hutchings b...@decadent.org.uk} [src:linux]
firmware-realtek: Intermittent problems with rtl8192cufw.bin
Added tag(s) pending.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
661860: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661860
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/handler.s.c.137313198310750.transcr...@bugs.debian.org
Processed: tagging 699361
Processing commands for cont...@bugs.debian.org:
tags 699361 + pending
Bug #699361 {Done: Ben Hutchings b...@decadent.org.uk} [src:linux]
linux-image-3.2.0-0.bpo.4-amd64: nfsd4 RELEASE_LOCKOWNER is slow and CPU
intensive
Added tag(s) pending.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
699361: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699361
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/handler.s.c.137313206311903.transcr...@bugs.debian.org
Processed: tagging 705788
Processing commands for cont...@bugs.debian.org:
tags 705788 + pending
Bug #705788 {Done: Ben Hutchings b...@decadent.org.uk}
[fb-modules-3.2.0-4-486-di] fb-modules-3.2.0-4-486-di: please include viafb
module for OLPC XO-1.5 support in d-i
Ignoring request to alter tags of bug #705788 to the same tags previously set
thanks
Stopping processing here.
Please contact me if you need assistance.
--
705788: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705788
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/handler.s.c.137313208612046.transcr...@bugs.debian.org
Processed: tagging 704269
Processing commands for cont...@bugs.debian.org:
tags 704269 + pending
Bug #704269 {Done: Ben Hutchings b...@decadent.org.uk} [src:linux]
linux-image-3.2.0-4-amd64: Kernel patch: udf: Fix handling of i_blocks
Added tag(s) pending.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
704269: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704269
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/handler.s.c.137313207511986.transcr...@bugs.debian.org
Processed: tagging 705780
Processing commands for cont...@bugs.debian.org:
tags 705780 + pending
Bug #705780 {Done: Ben Hutchings b...@decadent.org.uk}
[fb-modules-3.2.0-4-486-di] fb-modules-3.2.0-4-486-di: please include lxfb
module for OLPC XO-1 support in d-i
Added tag(s) pending.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
705780: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705780
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/handler.s.c.137313204011752.transcr...@bugs.debian.org
Processed: tagging 636029
Processing commands for cont...@bugs.debian.org:
tags 636029 + pending
Bug #636029 {Done: Ben Hutchings b...@decadent.org.uk} [src:linux] The
method, described in Documentation/kbuild/kconfig.txt, no longer works.
Added tag(s) pending.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
636029: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636029
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/handler.s.c.137313208012018.transcr...@bugs.debian.org
Processed: tagging 695968
Processing commands for cont...@bugs.debian.org:
tags 695968 + pending
Bug #695968 {Done: Ben Hutchings b...@decadent.org.uk} [src:linux]
linux-image-3.2.0-4-amd64: ath.ko starts printing thousands of error messages
several minutes after boot
Bug #695969 {Done: Ben Hutchings b...@decadent.org.uk} [src:linux]
linux-image-3.2.0-4-amd64: ath.ko prints thousands of error messages and
wireless connection goes down
Ignoring request to alter tags of bug #695968 to the same tags previously set
Ignoring request to alter tags of bug #695969 to the same tags previously set
thanks
Stopping processing here.
Please contact me if you need assistance.
--
695968: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695968
695969: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695969
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/handler.s.c.137313205211836.transcr...@bugs.debian.org
Processed: tagging 685407
Processing commands for cont...@bugs.debian.org:
tags 685407 + pending
Bug #685407 {Done: Ben Hutchings b...@decadent.org.uk} [src:linux]
linux-image-3.2.0-0.bpo.2-amd64: ext4 + nfs duplicate cookies problem with
large dovecot maildirs
Added tag(s) pending.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
685407: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685407
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/handler.s.c.137313209112074.transcr...@bugs.debian.org
Processed: tagging 706010
Processing commands for cont...@bugs.debian.org:
tags 706010 + pending
Bug #706010 {Done: Ben Hutchings b...@decadent.org.uk} [src:linux] drbdadm
triggers NULL pointer dereference in sock_ioctl+0x1a/0x212 when using dlm/sctp
Added tag(s) pending.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
706010: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706010
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/handler.s.c.137313205711870.transcr...@bugs.debian.org
Processed: tagging 656813
Processing commands for cont...@bugs.debian.org:
tags 656813 + pending
Bug #656813 {Done: Ben Hutchings b...@decadent.org.uk} [src:linux] cfg80211:
failed to add phy80211 symlink to netdev!
Added tag(s) pending.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
656813: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656813
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/handler.s.c.137313206911936.transcr...@bugs.debian.org
Processed: found 705635 in 3.2.46-1
Processing commands for cont...@bugs.debian.org: found 705635 3.2.46-1 Bug #705635 [linux-image-3.2.0-4-amd64] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung Marked as found in versions linux/3.2.46-1. thanks Stopping processing here. Please contact me if you need assistance. -- 705635: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705635 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.137313780911622.transcr...@bugs.debian.org
Bug#705635: Found in 3.2.46-1
I done a fresh install of Wheezy on my Thinkpad E130 (Core i3, Sandybridge) today and can confirm this bug is present in 3.2.46-1. Not figured out, how to trigger it in a reliable way, but my graphics just froze the second time while just using the Gnome Shell. signature.asc Description: This is a digitally signed message part
Bug#701744: Xen netback regression
On Sat, 2013-07-06 at 08:10 +0100, Ian Campbell wrote: wheezy sha1: Replaced with a version built on the correct baseline: abbf6e229470de2848b643c846491ce4b8ec001d linux_3.2.46.orig.tar.xz e2168426623b7f518a124f9768d83d4a782ecfa6 linux_3.2.46-1+deb7u1~ijc0.debian.tar.xz 36a6fffda39cfbcf722011d923a43f75245650e8 linux_3.2.46-1+deb7u1~ijc0.dsc a313adee85c456cca29b224c0cd38e990b6adbb1 linux-headers-3.2.0-4-amd64_3.2.46-1+deb7u1~ijc0_amd64.deb 27c8e63869035e421410b6538219a5a8c5d45be2 linux-image-3.2.0-4-amd64-dbg_3.2.46-1+deb7u1~ijc0_amd64.deb b4c6ffa0ae38ac6459a6f4105f7ca7c5e6256c3e linux-image-3.2.0-4-amd64_3.2.46-1+deb7u1~ijc0_amd64.deb ee579f10535bcd17c31ecb3729d2e3bbed92ff37 xen-linux-system-3.2.0-4-amd64_3.2.46-1+deb7u1~ijc0_amd64.deb 149abf7edfed1f49fbaebe1023e1f66a4db68e0e linux-headers-3.2.0-4-common_3.2.46-1+deb7u1~ijc0_amd64.deb c0fdf1820595e9fdb75716c3e73a170deb5441ff linux-headers-3.2.0-4-all_3.2.46-1+deb7u1~ijc0_amd64.deb fe45f1ea67846916f61ec78059f5fdebe090d6bd linux-headers-3.2.0-4-all-amd64_3.2.46-1+deb7u1~ijc0_amd64.deb 79ef6b6984b0dbde4ff55d4864fb81e42cf63835 linux-libc-dev_3.2.46-1+deb7u1~ijc0_amd64.deb e4c01d6a6444dabfba66d09d5fa719535da852a3 linux-headers-3.2.0-4-rt-amd64_3.2.46-1+deb7u1~ijc0_amd64.deb 0645a6f27f2f1a757fed9792efc725cbd384f470 linux-image-3.2.0-4-rt-amd64-dbg_3.2.46-1+deb7u1~ijc0_amd64.deb 65bfb5b5f667aa6c1abd90c48095a5ade08f1bd4 linux-image-3.2.0-4-rt-amd64_3.2.46-1+deb7u1~ijc0_amd64.deb 3ea78afef3d9c19e847df2e642dd108306360311 linux-headers-3.2.0-4-common-rt_3.2.46-1+deb7u1~ijc0_amd64.deb 154e540ccbaff1ae831b17e1c5ae36d434086a11 linux_3.2.46-1+deb7u1~ijc0_amd64.changes signature.asc Description: This is a digitally signed message part
Bug#701744: Xen netback regression
On Thu, 2013-07-04 at 07:36 +0200, Ingo Jürgensmann wrote: [...] As Ian requested, the netback fixes were included in Linux 3.2.47 and thus should appear in the wheezy-proposed-updates suite shortly. Aside from that, any regression that occurred as a result of a security update may also be fixed in a security update, and I hope we will be able to provide such updates for both Debian 6 (squeeze) and 7 (wheezy) in the next few weeks. Do you have a suggestion of in the next few weeks? [...] Sorry, I don't know precisely how long it may take. Ben. -- Ben Hutchings Tomorrow will be cancelled due to lack of interest. signature.asc Description: This is a digitally signed message part
