Processed (with 1 errors): Re: Processed (with 1 errors): Re: Bug#358751 closed by Moritz Mühlenhoff (Re: Bug#358751: tilt buttons are inverted with MX 1000 mouse)
Processing commands for cont...@bugs.debian.org:
> reassign 358751 src:linux
Bug #358751 [linux] tilt buttons are inverted with MX 1000 mouse
Bug reassigned from package 'linux' to 'src:linux'.
Ignoring request to alter found versions of bug #358751 to the same values
previously set
Ignoring request to alter fixed versions of bug #358751 to the same values
previously set
> merge 358751 347677
Bug #358751 [src:linux] tilt buttons are inverted with MX 1000 mouse
Unable to merge bugs because:
forwarded of #347677 is 'https://bugzilla.kernel.org/show_bug.cgi?id=1786' not
'http://bugzilla.kernel.org/show_bug.cgi?id=1786'
Failed to merge 358751: Did not alter merged bugs
Debbugs::Control::set_merged('transcript', 'GLOB(0x2179e50)',
'requester', 'Christian Marillat ', 'request_addr',
'cont...@bugs.debian.org', 'request_msgid',
'<878v1b57xf@christian.marillat.net>', 'request_subject', ...) called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 538
eval {...} called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 537
Debbugs::Control::Service::control_line('line', 'merge 358751 347677',
'clonebugs', 'HASH(0x20b9ae8)', 'limit', 'HASH(0x20b94d0)',
'common_control_options', 'ARRAY(0x20b9518)', 'errors', ...) called at
/usr/lib/debbugs/service line 474
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
347677: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=347677
358751: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=358751
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.137369439621846.transcr...@bugs.debian.org
Processed (with 1 errors): Re: Processed (with 1 errors): Re: Bug#358751 closed by Moritz Mühlenhoff (Re: Bug#358751: tilt buttons are inverted with MX 1000 mouse)
Processing commands for cont...@bugs.debian.org:
> reassign 358751 linux
Bug #358751 [src:linux-2.6] tilt buttons are inverted with MX 1000 mouse
Warning: Unknown package 'src:linux-2.6'
Bug reassigned from package 'src:linux-2.6' to 'linux'.
Ignoring request to alter found versions of bug #358751 to the same values
previously set
Ignoring request to alter fixed versions of bug #358751 to the same values
previously set
> merge 358751 347677
Bug #358751 [linux] tilt buttons are inverted with MX 1000 mouse
Unable to merge bugs because:
forwarded of #347677 is 'https://bugzilla.kernel.org/show_bug.cgi?id=1786' not
'http://bugzilla.kernel.org/show_bug.cgi?id=1786'
package of #347677 is 'src:linux' not 'linux'
Failed to merge 358751: Did not alter merged bugs
Debbugs::Control::set_merged('transcript', 'GLOB(0x1f94c98)',
'requester', 'Christian Marillat ', 'request_addr',
'cont...@bugs.debian.org', 'request_msgid',
'<87bo67587n@christian.marillat.net>', 'request_subject', ...) called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 538
eval {...} called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 537
Debbugs::Control::Service::control_line('line', 'merge 358751 347677',
'clonebugs', 'HASH(0x1ed4ae8)', 'limit', 'HASH(0x1ed44d0)',
'common_control_options', 'ARRAY(0x1ed4518)', 'errors', ...) called at
/usr/lib/debbugs/service line 474
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
347677: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=347677
358751: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=358751
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.137369402719922.transcr...@bugs.debian.org
Processed (with 1 errors): Re: Bug#358751 closed by Moritz Mühlenhoff (Re: Bug#358751: tilt buttons are inverted with MX 1000 mouse)
Processing commands for cont...@bugs.debian.org:
> reopen 358751
Bug #358751 {Done: Moritz Mühlenhoff } [src:linux-2.6] tilt
buttons are inverted with MX 1000 mouse
Warning: Unknown package 'src:linux-2.6'
Bug reopened
Warning: Unknown package 'src:linux-2.6'
Warning: Unknown package 'src:linux-2.6'
Ignoring request to alter fixed versions of bug #358751 to the same values
previously set
Warning: Unknown package 'src:linux-2.6'
> merge 358751 347677
Bug #358751 [src:linux-2.6] tilt buttons are inverted with MX 1000 mouse
Warning: Unknown package 'src:linux-2.6'
Unable to merge bugs because:
forwarded of #347677 is 'https://bugzilla.kernel.org/show_bug.cgi?id=1786' not
'http://bugzilla.kernel.org/show_bug.cgi?id=1786'
package of #347677 is 'src:linux' not 'src:linux-2.6'
Failed to merge 358751: Did not alter merged bugs
Debbugs::Control::set_merged('transcript', 'GLOB(0x2d21690)',
'requester', 'Christian Marillat ', 'request_addr',
'cont...@bugs.debian.org', 'request_msgid',
'<87hafzvyvp@christian.marillat.net>', 'request_subject', ...) called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 538
eval {...} called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 537
Debbugs::Control::Service::control_line('line', 'merge 358751 347677',
'clonebugs', 'HASH(0x2c5cae8)', 'limit', 'HASH(0x2c5c4d0)',
'common_control_options', 'ARRAY(0x2c5c518)', 'errors', ...) called at
/usr/lib/debbugs/service line 474
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
347677: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=347677
358751: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=358751
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.13736915748624.transcr...@bugs.debian.org
Processed: Re: [3.6.9 -> 3.7.1 regression] Dell D630: System doesn't reboot nor power off
Processing commands for cont...@bugs.debian.org: > fixed 697635 3.9.8-1 Bug #697635 [src:linux] linux-image-3.7-trunk-amd64: System doesn't reboot nor power off with 3.7.1-1~experimental.2 Marked as fixed in versions linux/3.9.8-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 697635: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697635 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.137368966031239.transcr...@bugs.debian.org
Bug#697635: [3.6.9 -> 3.7.1 regression] Dell D630: System doesn't reboot nor power off
fixed 697635 3.9.8-1 thanks Dear Maintainers, Problem fixed in 3.9.8-1, certainly because of commit 67842e50729b9f9c9ebd1449735f2f3d129e2325 (in 3.9.7) regards, Nicolas
Aprenda a Investir em Imóveis - Cursos para o Mercado Imobiliário
Caso não esteja visualizando este e-mail, clique aqui (http://uinewsletter.com.br/lt.php?c=719&m=716&nl=7&s=8b143b6d811c5267c07a8f3256185ead&lid=27848&l=-http--www.investeducar.com.br/) Você está recebendo esta mensagem porque se cadastrou em nosso site com o email debian-kernel@lists.debian.org. Clique no link abaixo para cancelar sua inscrição: http://uinewsletter.com.br/box.php?nl=7&c=719&m=716&s=8b143b6d811c5267c07a8f3256185ead&funcml=unsub2
Bug#661830: marked as done (linux-image-3.2.0-1-amd64: snd_hda_intel ALC269 regression)
Your message dated Sat, 13 Jul 2013 00:51:17 +0200 with message-id <20130712225116.GB4722@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #661830, regarding linux-image-3.2.0-1-amd64: snd_hda_intel ALC269 regression 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.) -- 661830: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661830 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 3.2.7-1 Severity: normal Hi, There is a problem with a headphones jack detection in the 3.2 kernel for the ALC269 codec: sound comes from both speaker and headphones simultaneously and never switches between them. The problem arised when I upgraded my system to the 3.2 kernel, and when I rolled back to the 3.1 kernel, everything was ok. Some of old kernels (may be 2.6.32) had the same problem, but for them it could be fixed by choosing appropriate "model" option for the snd_hda_intel module in the /etc/modprobe.d/alsa-base.conf. Now this doesn't help. Best Regards, Pavel -- 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: root=/dev/mapper/system-root--debtest resume=/dev/sda2 splash=none quiet vga0x317 ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [8.905233] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/input/input9 [8.957856] HDMI status: Codec=3 Pin=4 Presence_Detect=0 ELD_Valid=0 [8.958022] HDMI status: Codec=3 Pin=5 Presence_Detect=0 ELD_Valid=0 [8.958187] HDMI status: Codec=3 Pin=6 Presence_Detect=0 ELD_Valid=0 [8.958344] input: HDA Intel HDMI/DP,pcm=8 as /devices/pci:00/:00:1b.0/sound/card0/input10 [8.958436] input: HDA Intel HDMI/DP,pcm=7 as /devices/pci:00/:00:1b.0/sound/card0/input11 [8.958523] input: HDA Intel HDMI/DP,pcm=3 as /devices/pci:00/:00:1b.0/sound/card0/input12 [8.958875] input: HDA Intel Headphone as /devices/pci:00/:00:1b.0/sound/card0/input13 [ 10.70] EXT4-fs (dm-0): re-mounted. Opts: (null) [ 10.840111] EXT4-fs (dm-0): re-mounted. Opts: errors=remount-ro [ 13.176100] loop: module loaded [ 13.705621] Adding 6291452k swap on /dev/mapper/system-swap--deb. Priority:-1 extents:1 across:6291452k [ 14.259493] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: acl,user_xattr [ 14.345995] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: errors=remount-ro [ 14.432445] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: errors=remount-ro [ 14.444208] EXT4-fs (dm-8): mounted filesystem with ordered data mode. Opts: errors=remount-ro [ 14.753414] IBM TrackPoint firmware: 0x0e, buttons: 3/3 [ 14.983683] ehci_hcd :00:1d.0: PCI INT A disabled [ 14.983738] ehci_hcd :00:1d.0: PME# enabled [ 15.001238] input: TPPS/2 IBM TrackPoint as /devices/platform/i8042/serio4/serio5/input/input14 [ 15.282703] kvm: VM_EXIT_LOAD_IA32_PERF_GLOBAL_CTRL does not work properly. Using workaround [ 15.658711] RPC: Registered named UNIX socket transport module. [ 15.658714] RPC: Registered udp transport module. [ 15.658716] RPC: Registered tcp transport module. [ 15.658717] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 15.727244] FS-Cache: Loaded [ 15.796346] FS-Cache: Netfs 'nfs' registered for caching [ 15.808061] Installing knfsd (copyright (C) 1996 o...@monad.swb.de). [ 17.635253] fuse init (API version 7.17) [ 20.451409] input: ACPI Virtual Keyboard Device as /devices/virtual/input/input15 [ 23.137998] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 23.138005] Bluetooth: BNEP filters: protocol multicast [ 23.181978] Bluetooth: RFCOMM TTY layer initialized [ 23.181989] Bluetooth: RFCOMM socket layer initialized [ 23.181993] Bluetooth: RFCOMM ver 1.11 [ 24.411959] lp: driver loaded but no devices found [ 25.077701] ppdev: user-space parallel port driver [ 27.854032] ehci_hcd :00:1d.0: BAR 0: set to [mem 0xf0907000-0xf09073ff] (PCI address [0xf0907000-0xf09073ff]) [ 27.854057] ehci_hcd :00:1d.0: restoring config space at offset 0xf (was 0x100, writing 0x10b) [ 27.854086] ehci_hcd :00:1d.0: restoring config space at offset 0x1 (was 0x290, writing 0x2900102) [ 27.854207] ehci_hcd :00:1d.0: PME# disabled [ 27.854219] ehci_hcd :00:1d.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23 [ 27.854226] ehci_hcd :00:1d.0: sett
Bug#584724: marked as done (linux-image-2.6.32-5-amd64: NETDEV WATCHDOG: (via-rhine): transmit queue 0 timed out)
Your message dated Sat, 13 Jul 2013 00:51:17 +0200 with message-id <20130712225116.GB4722@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #584724, regarding linux-image-2.6.32-5-amd64: NETDEV WATCHDOG: (via-rhine): transmit queue 0 timed out 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.) -- 584724: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584724 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.32-15 Severity: normal This appears to be the same bug as: https://bugzilla.kernel.org/show_bug.cgi?id=11663 I have attached kernel output; once the timeout occurs, the interface is unusable and bounces spastically (without becoming operational) until the system is rebooted. This most often is triggered by samba traffic, but that could be because that is just the heaviest traffic on my system. ;-) BTW, this interface is reported by lspci as: 00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 7c) Double-BTW, this is not a new problem with 2.6.32, but our activity levels have picked up recently and trigger it more frequently. -- Package-specific info: ** Version: Linux version 2.6.32-5-amd64 (Debian 2.6.32-15) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-1) ) #1 SMP Tue Jun 1 06:11:58 UTC 2010 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.32-5-amd64 root=/dev/mapper/vg00-root ro ipv6.disable=1 rootdelay=10 ** Not tainted ** Kernel log: [ 20.917471] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [ 20.924598] udev: renamed network interface eth0 to eth1 [ 20.953407] udev: renamed network interface eth1_rename to eth0 [ 21.014759] parport_pc 00:0a: reported by Plug and Play ACPI [ 21.014871] parport0: PC-style at 0x378, irq 7 [PCSPP] [ 21.018448] input: PC Speaker as /devices/platform/pcspkr/input/input5 [ 21.032277] k8temp :00:18.3: Temperature readouts might be wrong - check erratum #141 [ 21.209202] EDAC MC: Ver: 2.1.0 Jun 1 2010 [ 21.226787] st0: Block limits 2 - 16777214 bytes. [ 21.229458] EDAC amd64_edac: Ver: 3.2.0 Jun 1 2010 [ 21.229633] EDAC amd64: This node reports that Memory ECC is currently disabled, set F3x44[22] (:00:18.3). [ 21.229720] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. [ 21.229722] Either enable ECC checking or force module loading by setting 'ecc_enable_override'. [ 21.229723] (Note that use of the override may cause unknown side effects.) [ 21.229934] amd64_edac: probe of :00:18.2 failed with error -22 [ 21.373141] HDA Intel :04:01.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 [ 21.373280] HDA Intel :04:01.0: setting latency timer to 64 [ 21.373285] HDA Intel :04:01.0: PCI: Disallowing DAC for device [ 21.461004] hda_codec: ALC883: BIOS auto-probing. [ 21.462907] input: HDA Digital PCBeep as /devices/pci:00/:00:13.0/:04:01.0/input/input6 [ 22.156505] Adding 262136k swap on /dev/mapper/vg00-swap. Priority:-1 extents:1 across:262136k [ 32.897030] kjournald starting. Commit interval 5 seconds [ 32.909096] EXT3 FS on md0, internal journal [ 32.909200] EXT3-fs: mounted filesystem with ordered data mode. [ 33.073055] kjournald starting. Commit interval 5 seconds [ 33.156713] EXT3 FS on dm-5, internal journal [ 33.156817] EXT3-fs: mounted filesystem with ordered data mode. [ 33.181588] kjournald starting. Commit interval 5 seconds [ 33.182243] EXT3 FS on dm-4, internal journal [ 33.182343] EXT3-fs: mounted filesystem with ordered data mode. [ 33.232237] EXT4-fs (dm-9): mounted filesystem with ordered data mode [ 33.287448] EXT4-fs (dm-6): mounted filesystem with ordered data mode [ 33.348953] EXT4-fs (dm-3): mounted filesystem with ordered data mode [ 33.414076] EXT4-fs (dm-1): mounted filesystem with ordered data mode [ 33.497949] EXT4-fs (dm-2): mounted filesystem with ordered data mode [ 33.672536] EXT4-fs (dm-12): mounted filesystem with ordered data mode [ 33.725336] EXT4-fs (dm-7): mounted filesystem with ordered data mode [ 33.791361] EXT4-fs (dm-10): mounted filesystem with ordered data mode [ 33.865425] EXT4-fs (dm-11): mounted filesystem with ordered data mode [ 33.964434] EXT4-fs (dm-13): mounted filesystem with ordered data mode [ 50.233632] RPC: Registered udp transport module. [ 50.233703] RPC: Registered tcp transport module. [ 50.233759] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 50.261049] Slow work thread pool: Starting up [ 50.261195] Slow work
Bug#584238: marked as done (linux-image-2.6.32-3-486: When using USB to Ethernet nework adapter later on get error: blocked for more than 120 seconds)
Your message dated Sat, 13 Jul 2013 00:51:17 +0200 with message-id <20130712225116.GB4722@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #584238, regarding linux-image-2.6.32-3-486: When using USB to Ethernet nework adapter later on get error: blocked for more than 120 seconds 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.) -- 584238: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584238 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.32-9 Severity: normal Tags: squeeze When using USB to Ethernet adapter later on get error on console: [11531.988248] INOF: task khubd:618 blocked for more than 120 seconds. [11531.988377] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [11531.990656] INFO: task pegasus:1156 blocked for more than 120 seconds. [11531.990722] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. After that I can't reconfigure anymore network, nor reboot the system with the command: sudo shutdown -t 1 -r now because the system hangs forever. It is not help if I unplug and plug in again the network adapter, it is not recognised by the kernel anymore. -- Package-specific info: ** Version: Linux version 2.6.32-3-486 (Debian 2.6.32-9) (m...@debian.org) (gcc version 4.3.4 (Debian 4.3.4-8) ) #1 Thu Feb 25 05:35:13 UTC 2010 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-3-486 root=UUID=127a8e72-b9d4-4a28-8aa9-e6cdcb3985c9 ro all_generic_ide quiet ** Not tainted ** Kernel log: [9.225611] PM: Error -22 checking image file [9.225628] PM: Resume from disk failed. [9.414135] EXT3-fs: INFO: recovery required on readonly filesystem. [9.414163] EXT3-fs: write access will be enabled during recovery. [ 10.688535] kjournald starting. Commit interval 5 seconds [ 10.688652] EXT3-fs: recovery complete. [ 10.710733] EXT3-fs: mounted filesystem with ordered data mode. [ 14.472786] udev: starting version 154 [ 16.350029] Marking TSC unstable due to TSC halts in idle [ 16.360220] Switching to clocksource acpi_pm [ 16.364952] processor LNXCPU:00: registered as cooling_device1 [ 16.973885] ACPI: AC Adapter [ADP1] (on-line) [ 17.006719] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input1 [ 17.009207] ACPI: Lid Switch [LID] [ 17.014108] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 [ 17.016375] ACPI: Power Button [PWRF] [ 17.061928] ACPI: Battery Slot [MBAT] (battery absent) [ 17.171064] input: PC Speaker as /devices/platform/pcspkr/input/input3 [ 17.264959] psmouse serio1: ID: 12 02 3c [ 17.988705] input: PS/2 Generic Mouse as /devices/platform/i8042/serio1/input/input4 [ 18.017149] NET: Registered protocol family 23 [ 18.052666] yenta_cardbus :00:13.0: CardBus bridge found [1179:0001] [ 18.116480] parport_pc 00:0b: reported by Plug and Play ACPI [ 18.116647] parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE] [ 18.137705] toshiba_acpi: Toshiba Laptop ACPI Extras version 0.19 [ 18.137734] toshiba_acpi: HCI method: \_SB_.VALD.GHCI [ 18.232354] yenta_cardbus :00:13.0: ISA IRQ mask 0x0638, PCI irq 11 [ 18.232382] yenta_cardbus :00:13.0: Socket status: 3007 [ 18.237856] yenta_cardbus :00:13.1: CardBus bridge found [1179:0001] [ 18.365096] yenta_cardbus :00:13.1: ISA IRQ mask 0x0638, PCI irq 11 [ 18.365127] yenta_cardbus :00:13.1: Socket status: 3007 [ 18.589661] donauboe :00:11.0: power state changed by ACPI to D0 [ 18.673099] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11 [ 18.673147] donauboe :00:11.0: PCI INT A -> Link[LNKC] -> GSI 11 (level, low) -> IRQ 11 [ 18.683045] IrDA: Registered device irda0 [ 18.683071] toshoboe: Using multiple tasks [ 19.942533] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x100-0x3af: excluding 0x220-0x22f 0x330-0x337 0x388-0x38f [ 19.943975] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x3e0-0x4ff: clean. [ 19.946283] pcmcia_socket pcmcia_socket1: cs: IO port probe 0x100-0x3af: excluding 0x220-0x22f 0x330-0x337 0x388-0x38f [ 19.947698] pcmcia_socket pcmcia_socket1: cs: IO port probe 0x3e0-0x4ff: clean. [ 19.948699] pcmcia_socket pcmcia_socket1: cs: IO port probe 0x820-0x8ff: clean. [ 19.949502] pcmcia_socket pcmcia_socket1: cs: IO port probe 0xc00-0xcf7: clean. [ 19.951565] pcmcia_socket pcmcia_socket1: cs: IO port probe 0xa00-0xaff: clean. [ 19.952689] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x820-0x8ff: clean. [ 19.953498]
Bug#583935: marked as done (linux-image-2.6.32-5-amd64: kernel trace in net/ipv4/tcp_input.c:2540 tcp_ack)
Your message dated Sat, 13 Jul 2013 00:50:45 +0200 with message-id <20130712225044.GA4722@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #583935, regarding linux-image-2.6.32-5-amd64: kernel trace in net/ipv4/tcp_input.c:2540 tcp_ack 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.) -- 583935: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583935 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.32-14 Severity: normal Tags: squeeze I haven't noticed a stability issue as such but saw this kernel trace logged into dmesg. -- Package-specific info: ** Version: Linux version 2.6.32-5-amd64 (Debian 2.6.32-14) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-1) ) #1 SMP Sun May 30 17:20:42 UTC 2010 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.32-5-amd64 root=/dev/mapper/LocalDisk-ROOT ro quiet security=tomoyo splash ** Tainted: W (512) * Taint on warning. ** Kernel log: [ 28.406886] iwlagn :03:00.0: firmware: requesting iwlwifi-5000-2.ucode [ 28.548635] iwlagn :03:00.0: loaded firmware version 8.24.2.12 [ 28.692813] Registered led device: iwl-phy0::radio [ 28.692830] Registered led device: iwl-phy0::assoc [ 28.692847] Registered led device: iwl-phy0::RX [ 28.692863] Registered led device: iwl-phy0::TX [ 28.705588] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 28.977787] ip_tables: (C) 2000-2006 Netfilter Core Team [ 29.974096] CPU0 attaching NULL sched-domain. [ 29.974107] CPU1 attaching NULL sched-domain. [ 30.000216] CPU0 attaching sched-domain: [ 30.000225] domain 0: span 0-1 level MC [ 30.000231] groups: 0 1 [ 30.000243] CPU1 attaching sched-domain: [ 30.000248] domain 0: span 0-1 level MC [ 30.000253] groups: 1 0 [ 30.752068] CE: hpet increasing min_delta_ns to 15000 nsec [ 34.129035] e1000e :00:19.0: irq 28 for MSI/MSI-X [ 34.184125] e1000e :00:19.0: irq 28 for MSI/MSI-X [ 34.185657] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 40.052965] Registered led device: iwl-phy0::radio [ 40.053013] Registered led device: iwl-phy0::assoc [ 40.053057] Registered led device: iwl-phy0::RX [ 40.053099] Registered led device: iwl-phy0::TX [ 40.062505] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 40.456244] e1000e :00:19.0: irq 28 for MSI/MSI-X [ 40.512218] e1000e :00:19.0: irq 28 for MSI/MSI-X [ 40.513753] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 40.820920] Registered led device: iwl-phy0::radio [ 40.820972] Registered led device: iwl-phy0::assoc [ 40.821016] Registered led device: iwl-phy0::RX [ 40.821067] Registered led device: iwl-phy0::TX [ 40.838420] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 46.301012] wlan0: direct probe to AP 00:16:b6:a5:e7:1c (try 1) [ 46.303662] wlan0: direct probe responded [ 46.303669] wlan0: authenticate with AP 00:16:b6:a5:e7:1c (try 1) [ 46.305533] wlan0: authenticated [ 46.305566] wlan0: associate with AP 00:16:b6:a5:e7:1c (try 1) [ 46.308078] wlan0: RX AssocResp from 00:16:b6:a5:e7:1c (capab=0x411 status=0 aid=2) [ 46.308084] wlan0: associated [ 46.322057] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 46.393592] padlock: VIA PadLock not detected. [ 50.772185] tun: Universal TUN/TAP device driver, 1.6 [ 50.772191] tun: (C) 1999-2004 Max Krasnyansky [ 50.775190] tun0: Disabled Privacy Extensions [ 57.217677] CPU0 attaching NULL sched-domain. [ 57.217681] CPU1 attaching NULL sched-domain. [ 57.240126] CPU0 attaching sched-domain: [ 57.240130] domain 0: span 0-1 level MC [ 57.240133] groups: 0 1 [ 57.240139] CPU1 attaching sched-domain: [ 57.240141] domain 0: span 0-1 level MC [ 57.240144] groups: 1 0 [ 85.004087] hrtimer: interrupt took 544273 ns [ 86.926725] TOMOYO-WARNING: Domain ' /etc/init.d/kdm /sbin/start-stop-daemon /usr/bin/kdm /etc/kde4/kdm/Xsession /bin/bash /usr/bin/ssh-agent /usr/bin/gpg-agent /usr/bin/dbus-launch /usr/bin/startkde /usr/lib/kde4/libexec/start_kdeinit_wrapper /usr/lib/kde4/libexec/start_kdeinit /usr/bin/kdeinit4 /usr/bin/plasma-desktop' has so many ACLs to hold. Stopped learning mode. [ 174.886226] padlock: VIA PadLock Hash Engine not detected. [ 364.553852] TOMOYO-WARNING: Domain ' /etc/init.d/kdm /sbin/start-stop-daemon /usr/bin/kdm /etc/kde4/kdm/Xsession /bin/bash /usr/bin/ssh-agent /usr/bin/gpg-agent /usr/bin/dbus-launch /usr/bin/startkde /usr/lib/kde4/libexec/start_kdeinit_wrapper /usr/lib/kde4/libexec/start_kdeinit /usr/bin/kdeinit4 /usr/bin/kontact' has so many ACLs to hold. Stopped l
Bug#587014: marked as done ([linux-2.6] screen brightness can't be modified on Panasonic S9)
Your message dated Sat, 13 Jul 2013 00:51:54 +0200 with message-id <20130712225154.GC4722@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #587014, regarding [linux-2.6] screen brightness can't be modified on Panasonic S9 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.) -- 587014: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=587014 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Severity: normal --- Please enter the report below this line. --- Presing the "light up" / "light down" keys doesn't modify the LCD screen brightness. Directly writing to /sys/class/backlight/panasonic/brightness has the same effect : nothing. /sys/class/backlight/panasonic/actual_brightness is modified, but the screen brightness isn't affected. I tried to reboot with lenny 2.6.26-2 kernel on the same system, and the brightness could be changed by pressing the up/down keys, so I believe it is a kernel issue (but gdm couldn't properly start, so it is not a proper workaround). It is a serious issue, since the screen default brightness is very strong and uncomfortable. I believe it is related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/588983 I tried to use acpi packages from unstable, without improvement. --- System information. --- Architecture: amd64 Kernel: Linux 2.6.32-5-amd64 Debian Release: squeeze/sid 700 testing security.debian.org 700 testing ftp.jaist.ac.jp 600 unstableftp.jaist.ac.jp 500 stable ftp.jaist.ac.jp 00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 02) Subsystem: Matsushita Electric Industrial Co., Ltd. Device 8338 Flags: bus master, fast devsel, latency 0 Capabilities: [e0] Vendor Specific Information: Len=0c Kernel driver in use: agpgart-intel 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02) (prog-if 00 [VGA controller]) Subsystem: Matsushita Electric Industrial Co., Ltd. Device 8338 Flags: bus master, fast devsel, latency 0, IRQ 35 Memory at f000 (64-bit, non-prefetchable) [size=4M] Memory at e000 (64-bit, prefetchable) [size=256M] I/O ports at e0b0 [size=8] Expansion ROM at [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [a4] PCI Advanced Features Kernel driver in use: i915 00:19.0 Ethernet controller: Intel Corporation 82577LM Gigabit Network Connection (rev 06) Subsystem: Matsushita Electric Industrial Co., Ltd. Device 8338 Flags: bus master, fast devsel, latency 0, IRQ 33 Memory at f4a0 (32-bit, non-prefetchable) [size=128K] Memory at f4a29000 (32-bit, non-prefetchable) [size=4K] I/O ports at e040 [size=32] Capabilities: [c8] Power Management version 2 Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [e0] PCI Advanced Features Kernel driver in use: e1000e 00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06) (prog-if 20 [EHCI]) Subsystem: Matsushita Electric Industrial Co., Ltd. Device 8338 Flags: bus master, medium devsel, latency 0, IRQ 16 Memory at f4a28000 (32-bit, non-prefetchable) [size=1K] Capabilities: [50] Power Management version 2 Capabilities: [58] Debug port: BAR=1 offset=00a0 Capabilities: [98] PCI Advanced Features Kernel driver in use: ehci_hcd 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06) Subsystem: Matsushita Electric Industrial Co., Ltd. Device 8338 Flags: bus master, fast devsel, latency 0, IRQ 22 Memory at f4a2 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [130] Root Complex Link Kernel driver in use: HDA Intel 00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 06) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: d000-dfff
Bug#582275: marked as done (linux-image-2.6.32-bpo.4-686: ext3 filesystem corruption with md RAID1 on Seagate disks)
Your message dated Sat, 13 Jul 2013 00:50:45 +0200 with message-id <20130712225044.GA4722@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #582275, regarding linux-image-2.6.32-bpo.4-686: ext3 filesystem corruption with md RAID1 on Seagate disks 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.) -- 582275: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582275 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.32-11~bpo50+1 Severity: critical Justification: causes serious data loss I keep getting ext3 filesystem corruptions on one of my md RAID1 arrays. Shortly after booting, I get messages like the following one: EXT3-fs error (device md1): htree_dirblock_to_tree: bad entry in directory #17269110: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0 This forces an automatic fsck at the next reboot that fails. The manual fsck.ext3 -y /dev/md1 takes a long time but manages to get a clean FS again. After the reboot, it takes just a few minutes until the first of these messages appear again. The two disks used in the RAID1 md device are both Seagate ST31000528AS that show no errors in long and short SMART test and Seatools. Memtest shows no memory problems. Two other RAID1 systems connected to the same Intel Ibex Peak 6 port SATA AHCI Controller (rev 06) show no such problems. A RAID5 with 4 Seagate ST3750640AS on a Promise PDC40718 (SATA 300 TX4) also works without problems in the same system. I saw that sata_sil.c has a blacklist that includes mainly Seagate drives but do not know if this is related to my problem since my system uses an Intel SATA controller. -- Package-specific info: ** Version: Linux version 2.6.32-bpo.4-686 (Debian 2.6.32-11~bpo50+1) (norb...@tretkowski.de) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) #1 SMP Mon Apr 12 16:20:13 UTC 2010 ** Command line: root=UUID=a059fdf2-4ff6-4c30-ba7f-77c85e7f5d1b ro quiet splash ** Not tainted ** Kernel log: [9.619225] md0: detected capacity change from 0 to 2250460889088 [9.619426] md: md1 stopped. [9.619507] md0: unknown partition table [9.627810] md: bind [9.627937] md: bind [9.637594] raid1: raid set md1 active with 2 out of 2 mirrors [9.637607] md1: detected capacity change from 0 to 991614926848 [9.637814] md: md2 stopped. [9.637897] md1: unknown partition table [9.675765] md: bind [9.675894] md: bind [9.685475] raid1: raid set md2 active with 2 out of 2 mirrors [9.685489] md2: detected capacity change from 0 to 8587116544 [9.685682] md: md3 stopped. [9.685764] md2: unknown partition table [9.747654] md: bind [9.747756] md: bind [9.757332] raid1: raid set md3 active with 2 out of 2 mirrors [9.757345] md3: detected capacity change from 0 to 2000396222464 [9.757541] md: md4 stopped. [9.757625] md3: unknown partition table [9.804386] md: bind [9.804488] md: bind [9.814098] raid1: raid set md4 active with 2 out of 2 mirrors [9.814111] md4: detected capacity change from 0 to 2000396222464 [9.814323] md4: unknown partition table [9.994122] device-mapper: uevent: version 1.0.3 [9.994182] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-de...@redhat.com [ 10.009098] PM: Starting manual resume from disk [ 10.009100] PM: Resume from partition 9:2 [ 10.009101] PM: Checking hibernation image. [ 10.013003] PM: Error -22 checking image file [ 10.013004] PM: Resume from disk failed. [ 10.082000] kjournald starting. Commit interval 5 seconds [ 10.082004] EXT3-fs: mounted filesystem with ordered data mode. [ 11.327588] udevd version 125 started [ 11.898037] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2 [ 11.898041] ACPI: Power Button [PWRB] [ 11.924627] Monitor-Mwait will be used to enter C-1 state [ 11.951685] Monitor-Mwait will be used to enter C-2 state [ 11.983607] Monitor-Mwait will be used to enter C-3 state [ 11.983664] processor LNXCPU:00: registered as cooling_device0 [ 11.983706] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3 [ 11.983709] ACPI: Power Button [PWRF] [ 12.102371] processor LNXCPU:01: registered as cooling_device1 [ 12.183683] processor LNXCPU:02: registered as cooling_device2 [ 12.269226] input: PC Speaker as /devices/platform/pcspkr/input/input4 [ 12.287409] input: X10 Wireless Technology Inc USB Receiver as /devices/pci:00/:00:1a.7/usb7/7-4/7-4.4/input/input5 [ 12.287462] usbcore:
Bug#598784: marked as done ([linux-2.6] Philips SPC 1300NC webcam not recognised)
Your message dated Sat, 13 Jul 2013 00:51:54 +0200 with message-id <20130712225154.GC4722@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #598784, regarding [linux-2.6] Philips SPC 1300NC webcam not recognised 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.) -- 598784: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=598784 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.32-23 Severity: normal My Philips SPC 1300NC webcam is not recognised when I plug it in. Only my 32bit laptop is affected by this bug. My Logitech webcam works fine on the same machine. The Philips webcam works without issues on my 64bit Debian Squeeze machine. lsusb: Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub dmesg: [ 378.284388] hub 1-0:1.0: unable to enumerate USB device on port 4 [ 378.540147] usb 1-4: new high speed USB device using ehci_hcd and address 70 [ 378.608494] hub 1-0:1.0: unable to enumerate USB device on port 4 [ 378.809418] hub 1-0:1.0: unable to enumerate USB device on port 4 [ 378.996430] hub 1-0:1.0: unable to enumerate USB device on port 4 [ 379.184319] hub 1-0:1.0: unable to enumerate USB device on port 4 [ 379.372334] hub 1-0:1.0: unable to enumerate USB device on port 4 [ 379.560345] hub 1-0:1.0: unable to enumerate USB device on port 4 [ 379.748487] hub 1-0:1.0: unable to enumerate USB device on port 4 [ 379.936528] hub 1-0:1.0: unable to enumerate USB device on port 4 [ 380.124390] hub 1-0:1.0: unable to enumerate USB device on port 4 [ 380.368148] usb 1-4: new high speed USB device using ehci_hcd and address 79 [ 380.436367] hub 1-0:1.0: unable to enumerate USB device on port 4 ... To get it running I have to reload the ehci_hcd module each time I use it: sudo modprobe -r ehci_hcd lsusb: Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 002: ID 0471:0331 Philips (or NXP) SPC 1300NC PC Camera Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub dmesg: [ 463.728507] hub 1-0:1.0: unable to enumerate USB device on port 4 [ 463.876590] ehci_hcd :00:1d.7: remove, state 1 [ 463.876600] usb usb1: USB disconnect, address 1 [ 463.928064] hub 1-0:1.0: hub_port_status failed (err = -19) [ 463.928081] hub 1-0:1.0: cannot disable port 4 (err = -19) [ 463.928105] hub 1-0:1.0: cannot reset port 4 (err = -19) [ 463.928116] hub 1-0:1.0: cannot disable port 4 (err = -19) [ 463.928130] hub 1-0:1.0: cannot reset port 4 (err = -19) [ 463.928140] hub 1-0:1.0: cannot disable port 4 (err = -19) [ 463.928155] hub 1-0:1.0: cannot reset port 4 (err = -19) [ 463.928165] hub 1-0:1.0: cannot disable port 4 (err = -19) [ 463.928176] hub 1-0:1.0: unable to enumerate USB device on port 4 [ 463.928185] hub 1-0:1.0: cannot disable port 4 (err = -19) [ 463.986359] ehci_hcd :00:1d.7: USB bus 1 deregistered [ 463.986403] ehci_hcd :00:1d.7: PCI INT D disabled [ 464.236062] usb 3-2: new full speed USB device using uhci_hcd and address 2 [ 464.433234] usb 3-2: config 1 has an invalid descriptor of length 7, skipping remainder of the config [ 464.455227] usb 3-2: New USB device found, idVendor=0471, idProduct=0331 [ 464.455238] usb 3-2: New USB device strings: Mfr=2, Product=1, SerialNumber=0 [ 464.455248] usb 3-2: Product: Philips SPC 1300NC Webcam [ 464.455256] usb 3-2: Manufacturer: Philips CE [ 464.455487] usb 3-2: configuration #1 chosen from 1 choice [ 464.716237] 2:3:1 : no or invalid class specific endpoint descriptor [ 464.728897] usbcore: registered new interface driver snd-usb-audio [ 464.793189] Linux video capture interface: v2.00 [ 465.038049] uvcvideo: Found UVC 1.00 device Philips SPC 1300NC Webcam (0471:0331) [ 465.046775] input: Philips SPC 1300NC Webcam as /devices/pci:00/:00:1d.1/usb3/3-2/3-2:1.0/input/input11 [ 465.047115] usbcore: registered new interface driver uvcvideo [ 465.047900] USB Video Class driver (v0.1.0) And it works (in cheese). --- System information. --- Architecture: i386 Kernel: Linux 2.6.32-5-686 Debian Release: squeeze/sid 500 testing security.debian.org 500 testing mirror.switch.ch 500 hardy debian.isg.ee.ethz.ch 300 unstable mirror.switch.ch --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Sugge
Bug#577747: marked as done (Occasional RX DMA corruption with atl1c and atl1e)
Your message dated Sat, 13 Jul 2013 00:51:17 +0200 with message-id <20130712225116.GB4722@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #577747, regarding Occasional RX DMA corruption with atl1c and atl1e 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.) -- 577747: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=577747 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.32-11 Severity: normal Tags: upstream Some minutes after booting (cold boot, or resume from hibernation, at least before #534422 prevents me to use hibernation), my Iceweasel session launched through a SSH connection always fail with following error message : Corrupted MAC on input. Disconnecting: Packet corrupt Restarting the SSH connection, the problem don't occur anymore before next reboot. I've checked and replaced the ethernet cable, without change. I also tested the memory, seems ok. I thought at start it was a iceweasel or openssh problem, but then found other people have the same problem, like : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/60764 https://bugzilla.kernel.org/show_bug.cgi?id=12282 and perhaps also https://bugzilla.kernel.org/show_bug.cgi?id=13404 The problem is here at least since 2.6.30, and is always present with latest kernel from Sid. -- Package-specific info: ** Version: Linux version 2.6.32-4-686 (Debian 2.6.32-11) (m...@debian.org) (gcc version 4.3.4 (Debian 4.3.4-8) ) #1 SMP Tue Apr 6 07:02:27 UTC 2010 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-4-686 root=UUID=e295254a-3f31-41d0-91b3-01c982751390 ro quiet init=/sbin/bootchartd ** Not tainted ** Kernel log: [ 20.698740] name_count maxed, losing inode data: dev=00:07, inode=3668 [ 20.698754] name_count maxed, losing inode data: dev=00:07, inode=3760 [ 20.698766] name_count maxed, losing inode data: dev=00:07, inode=3760 [ 20.702285] input: Kensington Kensington Expert Mouse as /devices/pci:00/:00:1d.7/usb1/1-4/1-4.6/1-4.6:1.0/input/input10 [ 20.702372] name_count maxed, losing inode data: dev=00:05, inode=802 [ 20.702402] name_count maxed, losing inode data: dev=00:05, inode=802 [ 20.702490] name_count maxed, losing inode data: dev=00:05, inode=802 [ 20.702508] name_count maxed, losing inode data: dev=00:05, inode=802 [ 20.702614] name_count maxed, losing inode data: dev=00:05, inode=4 [ 20.702632] name_count maxed, losing inode data: dev=00:05, inode=4 [ 20.702685] generic-usb 0003:047D:1020.0003: input,hidraw2: USB HID v1.10 Mouse [Kensington Kensington Expert Mouse] on usb-:00:1d.7-4.6/input0 [ 20.702712] name_count maxed, losing inode data: dev=00:07, inode=3668 [ 20.702737] name_count maxed, losing inode data: dev=00:07, inode=3767 [ 20.702750] name_count maxed, losing inode data: dev=00:07, inode=3767 [ 20.702797] usbcore: registered new interface driver usbhid [ 20.702807] usbhid: v2.6:USB HID core driver [ 21.072045] HDA Intel :00:1b.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 21.072117] HDA Intel :00:1b.0: setting latency timer to 64 [ 21.177858] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/input/input11 [ 22.180011] hda-intel: azx_get_response timeout, switching to polling mode: last cmd=0x020c [ 22.182130] name_count maxed, losing inode data: dev=00:05, inode=4127 [ 22.182241] name_count maxed, losing inode data: dev=00:05, inode=4 [ 22.182261] name_count maxed, losing inode data: dev=00:05, inode=4 [ 22.785849] Adding 2096440k swap on /dev/sda5. Priority:-1 extents:1 across:2096440k [ 22.926683] EXT3 FS on sda8, internal journal [ 23.029031] name_count maxed, losing inode data: dev=00:05, inode=4 [ 23.030645] name_count maxed, losing inode data: dev=00:07, inode=8 [ 23.030661] name_count maxed, losing inode data: dev=00:07, inode=4569 [ 23.030710] name_count maxed, losing inode data: dev=00:05, inode=4 [ 23.030732] name_count maxed, losing inode data: dev=00:05, inode=4 [ 23.031225] name_count maxed, losing inode data: dev=00:07, inode=8 [ 23.031241] name_count maxed, losing inode data: dev=00:07, inode=4573 [ 23.031280] name_count maxed, losing inode data: dev=00:05, inode=4 [ 23.031298] name_count maxed, losing inode data: dev=00:05, inode=4 [ 23.032603] name_count maxed, losing inode data: dev=00:07, inode=8 [ 23.032619] name_count maxed, losing inode data: dev=00:07, inode=4579 [ 23.032666] name_count maxed, losing inode data: dev=00:05, inode=4 [ 23.032691] name_count maxed, losing inode data: dev=00:05,
Bug#575476: marked as done (linux-image-2.6.32-4-vserver-686-bigmem: task find:18553 blocked for more than 120 seconds.)
Your message dated Sat, 13 Jul 2013 00:52:29 +0200 with message-id <20130712225229.GD4722@pisco.westfalen.local> and subject line Closing vserver bugs has caused the Debian Bug report #575476, regarding linux-image-2.6.32-4-vserver-686-bigmem: task find:18553 blocked for more than 120 seconds. 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.) -- 575476: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=575476 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.32-10 Severity: normal The machine would report a lot of "task name:pid blocked for more than 120 seconds." >From my logs: Mar 24 19:23:59 postamt kernel: [95403.132478] INFO: task cron:11671 blocked for more than 120 seconds. Mar 24 19:24:02 postamt kernel: [95403.137228] INFO: task cron:11672 blocked for more than 120 seconds. Mar 24 19:24:06 postamt kernel: [95403.140292] INFO: task cron:11673 blocked for more than 120 seconds. Mar 25 22:18:55 postamt kernel: [191043.688456] INFO: task cron:11473 blocked for more than 120 seconds. Mar 26 06:52:33 postamt kernel: [30602.905237] INFO: task find:18553 blocked for more than 120 seconds. for the last incidence I'm attaching the complete message from kern.log -- Package-specific info: ** Version: Linux version 2.6.32-4-vserver-686-bigmem (Debian 2.6.32-10) (m...@debian.org) (gcc version 4.3.4 (Debian 4.3.4-8) ) #1 SMP Wed Mar 17 20:01:31 UTC 2010 ** Command line: root=UUID=70cb4228-b702-4dc3-b8ac-a70de2bc6d39 ro ** Not tainted ** Kernel log: [ 165.356482] EXT4-fs (dm-0): mounted filesystem with ordered data mode [ 167.736772] eth0: link up [ 171.672255] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 [ 171.677681] acpiphp: Slot [32] registered [ 171.678062] acpiphp: Slot [33] registered [ 171.678299] acpiphp: Slot [34] registered [ 171.678752] acpiphp: Slot [35] registered [ 171.678958] acpiphp: Slot [36] registered [ 171.679149] acpiphp: Slot [37] registered [ 171.679342] acpiphp: Slot [38] registered [ 171.679627] acpiphp: Slot [39] registered [ 171.679843] acpiphp: Slot [40] registered [ 171.680042] acpiphp: Slot [41] registered [ 171.680645] acpiphp: Slot [42] registered [ 171.680840] acpiphp: Slot [43] registered [ 171.681038] acpiphp: Slot [44] registered [ 171.681246] acpiphp: Slot [45] registered [ 171.686580] acpiphp: Slot [46] registered [ 171.686854] acpiphp: Slot [47] registered [ 171.687074] acpiphp: Slot [48] registered [ 171.687303] acpiphp: Slot [49] registered [ 171.687542] acpiphp: Slot [50] registered [ 171.687767] acpiphp: Slot [51] registered [ 171.687984] acpiphp: Slot [52] registered [ 171.688214] acpiphp: Slot [53] registered [ 171.689183] acpiphp: Slot [54] registered [ 171.689447] acpiphp: Slot [55] registered [ 171.689684] acpiphp: Slot [56] registered [ 171.689903] acpiphp: Slot [57] registered [ 171.690122] acpiphp: Slot [58] registered [ 171.690328] acpiphp: Slot [59] registered [ 171.690762] acpiphp: Slot [60] registered [ 171.690973] acpiphp: Slot [61] registered [ 171.691550] acpiphp: Slot [62] registered [ 171.691804] acpiphp: Slot [63] registered [ 171.692572] acpiphp: Slot [160] registered [ 171.698370] acpiphp: Slot [192] registered [ 171.698637] acpiphp: Slot [224] registered [ 171.698904] acpiphp: Slot [256] registered [ 171.699209] acpiphp: Slot [161] registered [ 171.699454] acpiphp: Slot [162] registered [ 171.699746] acpiphp: Slot [163] registered [ 171.699971] acpiphp: Slot [164] registered [ 171.700221] acpiphp: Slot [165] registered [ 171.700527] acpiphp: Slot [166] registered [ 171.700808] acpiphp: Slot [167] registered [ 171.701047] acpiphp: Slot [193] registered [ 171.701325] acpiphp: Slot [194] registered [ 171.701588] acpiphp: Slot [195] registered [ 171.701918] acpiphp: Slot [196] registered [ 171.702192] acpiphp: Slot [197] registered [ 171.702479] acpiphp: Slot [198] registered [ 171.702765] acpiphp: Slot [199] registered [ 171.703027] acpiphp: Slot [225] registered [ 171.714039] acpiphp: Slot [226] registered [ 171.726102] acpiphp: Slot [227] registered [ 171.731608] acpiphp: Slot [228] registered [ 171.731885] acpiphp: Slot [229] registered [ 171.732125] acpiphp: Slot [230] registered [ 171.732397] acpiphp: Slot [231] registered [ 171.732635] acpiphp: Slot [257] registered [ 171.732878] acpiphp: Slot [258] registered [ 171.733131] acpiphp: Slot [259] registered [ 171.733370] acpiphp: Slot [260] registered [ 171.733606] acpiphp: Slot [261] registered [ 171.733861] acpiphp: Slot [262] registered [ 171.734225] acpiph
Bug#571242: marked as done (linux-image-2.6.32-2-amd64: running 8 copies of bonnie deadlocks(?) in sync)
Your message dated Sat, 13 Jul 2013 00:50:45 +0200 with message-id <20130712225044.GA4722@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #571242, regarding linux-image-2.6.32-2-amd64: running 8 copies of bonnie deadlocks(?) in sync 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.) -- 571242: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571242 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.32-8 Severity: normal Running 8 copies of bonnie++ on 8 different filesystems on 8 disks seems to produce a deadlock in sync(2). Initialy all the bonnie++ processes seem to be running ok, but after a while only 2-3 of the disks are showing any I/O activiy and the dmesg output shows: [ 360.284601] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 360.284693] bonnieD 88034ac0f9f0 0 2941 2937 0x0008 [ 360.284697] 88063d4b54c0 0082 880338e8fe88 880338e8fe84 [ 360.284700] 0003 000155c0 f8a0 880338e8ffd8 [ 360.284703] 000155c0 000155c0 88033cf5cdb0 88033cf5d0a8 [ 360.284706] Call Trace: [ 360.284715] [] ? __mutex_lock_common+0x10b/0x17b [ 360.284720] [] ? try_to_wake_up+0x249/0x259 [ 360.284722] [] ? mutex_lock+0x1a/0x31 [ 360.284726] [] ? sync_filesystems+0x13/0xe3 [ 360.284728] [] ? sys_sync+0x12/0x2e [ 360.284733] [] ? system_call_fastpath+0x16/0x1b [ 360.284736] INFO: task bonnie:2946 blocked for more than 120 seconds. At this point any attempt to use "sync" hangs. The system seems to work again if the bonnie++ processes are killed. -- Package-specific info: ** Version: Linux version 2.6.32-2-amd64 (Debian 2.6.32-8) (b...@decadent.org.uk) (gcc version 4.3.4 (Debian 4.3.4-6) ) #1 SMP Fri Feb 12 00:01:47 UTC 2010 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.32-2-amd64 root=/dev/mapper/caronia_vg-root ro quiet ** Not tainted ** Kernel log: [ 181.785606] kjournald starting. Commit interval 5 seconds [ 181.791652] EXT3 FS on sdo, internal journal [ 181.791657] EXT3-fs: mounted filesystem with ordered data mode. [ 181.797389] kjournald starting. Commit interval 5 seconds [ 181.797486] EXT3 FS on sdp, internal journal [ 181.797491] EXT3-fs: mounted filesystem with ordered data mode. [ 181.802969] kjournald starting. Commit interval 5 seconds [ 181.803069] EXT3 FS on sdq, internal journal [ 181.803074] EXT3-fs: mounted filesystem with ordered data mode. [ 360.284498] INFO: task bonnie:2941 blocked for more than 120 seconds. [ 360.284601] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 360.284693] bonnieD 88034ac0f9f0 0 2941 2937 0x0008 [ 360.284697] 88063d4b54c0 0082 880338e8fe88 880338e8fe84 [ 360.284700] 0003 000155c0 f8a0 880338e8ffd8 [ 360.284703] 000155c0 000155c0 88033cf5cdb0 88033cf5d0a8 [ 360.284706] Call Trace: [ 360.284715] [] ? __mutex_lock_common+0x10b/0x17b [ 360.284720] [] ? try_to_wake_up+0x249/0x259 [ 360.284722] [] ? mutex_lock+0x1a/0x31 [ 360.284726] [] ? sync_filesystems+0x13/0xe3 [ 360.284728] [] ? sys_sync+0x12/0x2e [ 360.284733] [] ? system_call_fastpath+0x16/0x1b [ 360.284736] INFO: task bonnie:2946 blocked for more than 120 seconds. [ 360.284807] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 360.284890] bonnieD 88034ac4f9f0 0 2946 2937 0x [ 360.284893] 88063e4a0e20 0082 880338051e88 880338051e84 [ 360.284895] 0003 000155c0 f8a0 880338051fd8 [ 360.284898] 000155c0 000155c0 88033cf5bf90 88033cf5c288 [ 360.284900] Call Trace: [ 360.284903] [] ? __mutex_lock_common+0x10b/0x17b [ 360.284905] [] ? try_to_wake_up+0x249/0x259 [ 360.284907] [] ? mutex_lock+0x1a/0x31 [ 360.284909] [] ? sync_filesystems+0x13/0xe3 [ 360.284911] [] ? sys_sync+0x12/0x2e [ 360.284914] [] ? system_call_fastpath+0x16/0x1b [ 360.284916] INFO: task bonnie:2947 blocked for more than 120 seconds. [ 360.284983] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 360.285066] bonnieD 88034ac755c0 0 2947 2937 0x [ 360.285068] 88033cf5d4c0 0082 88033822be88 88033822be84 [ 360.285071] 88033cfebb80 81047f3d f8a0 88033822bfd8 [ 360.285073] 000155c0
Bug#567212: marked as done (rt73usb with 2.6.32-trunk kernel)
Your message dated Sat, 13 Jul 2013 00:50:45 +0200 with message-id <20130712225044.GA4722@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #567212, regarding rt73usb with 2.6.32-trunk kernel 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.) -- 567212: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567212 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.32-trunk-686 Version: 2.6.32-5 Debian Squeeze I use Edimax EW-7318USg usb wifi adapter with rt73 chipset - i use default rt73usb driver that is built in kernel and standard firmware from non-free repository package: firmware-ralink (0.22) - on new 2.6.32 trunk kernel, connection is very unstable - i can connect to my access point but i get disconnected periodicly in about 6 to 10 seconds and get connected again afer about 4 seconds. This process repeats itself continously. I use WPAPSK autentication TKIP encryption in managed mode - with wpa_supplicant - encryption works but i guess becouse of such frequent disconnetions dhclient can't get IP and i can't connect to internet. On previous 2.6.30 kernel and same configuration, everything works fine and connection is stable. scanning with iwlist works on both kernels but on 2.6.32-trunk takes 2 times longer. I assume that problem is some collision in kernel modules or in driver. best regards Dawid --- End Message --- --- Begin Message --- 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#574560: marked as done (linux-image-2.6.32: Netbook Philco PHN 10108 doesn't supported by kernel to change LCD brightness level)
Your message dated Sat, 13 Jul 2013 00:50:45 +0200 with message-id <20130712225044.GA4722@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #574560, regarding linux-image-2.6.32: Netbook Philco PHN 10108 doesn't supported by kernel to change LCD brightness level 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.) -- 574560: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574560 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.32-9 Severity: normal I think it is a kernel bug and you can track it here: http://bugzilla.kernel.org/show_bug.cgi?id=15575 Please, if possible, include a patch in 2.6.32 (or .33) Debian kernel after the solution. Regards, Eriberto - Brazil -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.34-rc1-git6 (SMP w/2 CPU cores) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-image-2.6.32 depends on: ii coreutils 7.4-2 The GNU core utilities ii debconf [debconf-2.0] 1.5.28 Debian configuration management sy linux-image-2.6.32 recommends no packages. Versions of packages linux-image-2.6.32 suggests: pn fdutils(no description available) pn ksymoops (no description available) pn linux-doc-2.6.32 | linux-sour (no description available) pn linux-image-2.6.32-dbg (no description available) -- debconf information excluded --- End Message --- --- Begin Message --- 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#575229: marked as done (network-manager: Wireless performance problems with ath5k driver)
Your message dated Sat, 13 Jul 2013 00:50:45 +0200 with message-id <20130712225044.GA4722@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #575229, regarding network-manager: Wireless performance problems with ath5k driver 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.) -- 575229: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=575229 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: network-manager Version: 0.8-1 Severity: normal File: network-manager This may more properly belong to the ath5k driver or kernel but since it was my machine's recent migration to network-manager that caused me to notice it, I'll report it here - please feel free to reassign. The ath5k driver apparently uses lots of cpu and causes long pauses in connectivity when the wireless networks available are being scanned...since network manager does this a lot, it leads to persistent and annoying networking hangs, particularly noticable in interactive sessions (ie, ssh). It took me a while to figure out what was going on - throughput with scp, ftp, etc seemed fine, but there were frequent pauses otherwise even when signal strength seemed fine. Finally I noticed in 'top' the phy0 process spiking CPU whenever this happened. I found this bug against Fedora https://bugzilla.redhat.com/show_bug.cgi?id=506659 which claims that there is unspecified "work done in the upstream kernel that will mitigate this issue." This is probably the upstream bug - https://bugzilla.kernel.org/show_bug.cgi?id=12635 I figured for tracking purposes there should be something in Debian about this problem. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-3-amd64 (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 Versions of packages network-manager depends on: ii adduser 3.112 add and remove users and groups ii dbus 1.2.20-2 simple interprocess messaging syst ii dhcp3-client 3.1.3-2DHCP client ii ifupdown 0.6.10 high level tools to configure netw ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib ii libdbus-1-3 1.2.20-2 simple interprocess messaging syst ii libdbus-glib-1-2 0.84-1 simple interprocess messaging syst ii libgcrypt11 1.4.5-2LGPL Crypto library - runtime libr ii libglib2.0-0 2.22.4-1 The GLib library of C routines ii libgnutls26 2.8.5-2the GNU TLS library - runtime libr ii libgudev-1.0-0151-2 GObject-based wrapper library for ii libnl11.1-5 library for dealing with netlink s ii libnm-glib2 0.8-1 network management framework (GLib ii libnm-util1 0.8-1 network management framework (shar ii libpolkit-gobject-1-0 0.96-1 PolicyKit Authorization API ii libuuid1 2.16.2-0 Universally Unique ID library ii lsb-base 3.2-23 Linux Standard Base 3.2 init scrip ii udev 151-2 /dev/ and hotplug management daemo ii wpasupplicant 0.6.10-2 client support for WPA and WPA2 (I Versions of packages network-manager recommends: ii dnsmasq-base 2.52-1A small caching DNS proxy and DHCP ii iptables 1.4.6-2 administration tools for packet fi ii modemmanager 0.3-2 D-Bus service for managing modems pn network-manager-gnome | ne (no description available) ii policykit-10.96-1framework for managing administrat ii ppp2.4.4rel-10.1 Point-to-Point Protocol (PPP) - da Versions of packages network-manager suggests: ii avahi-autoipd 0.6.25-3 Avahi IPv4LL network address confi --- End Message --- --- Begin Message --- 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
Bug#511449: marked as done (linux-image-2.6.26-1-vserver-686: Problem with Vserver CPU scheduler, vserver never hold (hold-ticks always 0))
Your message dated Sat, 13 Jul 2013 00:52:29 +0200 with message-id <20130712225229.GD4722@pisco.westfalen.local> and subject line Closing vserver bugs has caused the Debian Bug report #511449, regarding linux-image-2.6.26-1-vserver-686: Problem with Vserver CPU scheduler, vserver never hold (hold-ticks always 0) 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.) -- 511449: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=511449 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.26-1-vserver-686 Version: 2.6.26-12 Severity: normal Hi, i was trying out the token bucket directly with lenny but seems that no configuration makes the guest vserver get hold. The status and the configuration of the scheduler can be shown here: beta:/etc/vservers/amule# cat /proc/virtual/40001/sched FillRate: 1,1 Interval: 1,8 TokensMin: 750 TokensMax: 2988 PrioBias: 0 cpu 0: 2 7 0 0 0 RI 1 750 2988 1/1 1/8 0 0 cpu 1: 62829 22 0 0 0 RI 1 750 2988 1/1 1/8 0 0 The guest was running the "burnMMX" application for some time consumming 100% of one of the two cpu's. The flags of the vserver are as follows: beta:/etc/vservers/amule# cat flags sched_hard virt_mem virt_uptime virt_cpu virt_load virt_time beta:/etc/vservers/amule# cat /proc/virtual/40001/status UseCnt: 5 Tasks: 2 Flags: 0016021f0110 BCaps: 04ff CCaps: 0101 Spaces: 1c020200 I hope it wont be a configuration problem, after reading quite a few documentation from linux-vserver.org and googling for examples, configurations and similar cases like this i reached the conclusion that maybe a bug. Thanks in advance :) -- Package-specific info: ** Version: Linux version 2.6.26-1-vserver-686 (Debian 2.6.26-12) (wa...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-24)) #1 SMP Mon Dec 15 21:11:05 UTC 2008 ** Command line: root=/dev/mapper/system-root ro quiet ** Not tainted ** Kernel log: [3.536428] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [3.536437] usb usb1: Product: UHCI Host Controller [3.536444] usb usb1: Manufacturer: Linux 2.6.26-1-vserver-686 uhci_hcd [3.536452] usb usb1: SerialNumber: :00:07.2 [3.536415] ACPI: PCI Interrupt :00:07.3[D] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11 [3.536415] uhci_hcd :00:07.3: VIA VLink IRQ fixup, from 9 to 11 [3.536415] uhci_hcd :00:07.3: UHCI Host Controller [3.536415] uhci_hcd :00:07.3: new USB bus registered, assigned bus number 2 [3.536415] uhci_hcd :00:07.3: irq 11, io base 0xd000 [3.536588] usb usb2: configuration #1 chosen from 1 choice [3.536685] hub 2-0:1.0: USB hub found [3.536709] hub 2-0:1.0: 2 ports detected [3.641989] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001 [3.642003] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [3.642012] usb usb2: Product: UHCI Host Controller [3.642020] usb usb2: Manufacturer: Linux 2.6.26-1-vserver-686 uhci_hcd [3.642027] usb usb2: SerialNumber: :00:07.3 [3.648811] VP_IDE: IDE controller (0x1106:0x0571 rev 0x06) at PCI slot :00:07.1 [3.648811] VP_IDE: not 100% native mode: will probe irqs later [3.648885] VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci:00:07.1 [3.648910] ide0: BM-DMA at 0xffa0-0xffa7 [3.648931] ide1: BM-DMA at 0xffa8-0xffaf [3.648947] Probing IDE interface ide0... [3.832749] 8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004) [3.955466] FDC 0 is a post-1991 82077 [4.070868] hda: Maxtor 6Y160P0, ATA DISK drive [4.743265] hda: host max PIO5 wanted PIO255(auto-tune) selected PIO4 [4.743407] hda: UDMA/100 mode selected [4.743529] Probing IDE interface ide1... [5.306238] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 [5.306238] ide1 at 0x170-0x177,0x376 on irq 15 [5.351274] 8139cp :00:0a.0: This (id 10ec:8139 rev 10) is not an 8139C+ compatible chip [5.351324] 8139cp :00:0a.0: Try the "8139too" driver instead. [5.352029] No dock devices found. [5.361397] 8139too Fast Ethernet driver 0.9.28 [5.361397] ACPI: PCI Interrupt :00:0a.0[A] -> GSI 18 (level, low) -> IRQ 18 [5.363631] eth0: RealTek RTL8139 at 0xc800, 00:c0:26:a0:86:d3, IRQ 18 [5.363641] eth0: Identified 8139 chip type 'RTL-8139B' [5.401184] SCSI subsystem initialized [5.449184] libata version 3.00 loaded. [5.502478] hda: max request
Bug#551810: marked as done (linux-image-2.6.30-1-amd64: trackpad unstable on macbook pro with bcm5974 driver)
Your message dated Sat, 13 Jul 2013 00:51:54 +0200 with message-id <20130712225154.GC4722@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #551810, regarding linux-image-2.6.30-1-amd64: trackpad unstable on macbook pro with bcm5974 driver 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.) -- 551810: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=551810 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.30-1-amd64 Version: 2.6.30-6 Severity: normal On linux 2.6.30 on my macbook pro, the keyboard and trackpad stop responding occasionally. I see messages like this in the system log: [29552.773474] bcm5974: bcm5974: could not read from device [29552.773483] bcm5974: mode switch failed [29552.784494] bcm5974: bcm5974: could not read from device [29552.784501] bcm5974: mode switch failed [29552.830223] hub 5-0:1.0: port 2 disabled by hub (EMI?), re-enabling... [29552.830235] usb 5-2: USB disconnect, address 34 [29553.112176] usb 5-2: new full speed USB device using uhci_hcd and address 35 [29553.292693] usb 5-2: New USB device found, idVendor=05ac, idProduct=0230 [29553.292702] usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [29553.292709] usb 5-2: Product: Apple Internal Keyboard / Trackpad [29553.292714] usb 5-2: Manufacturer: Apple, Inc. [29553.292927] usb 5-2: configuration #1 chosen from 1 choice [29553.302802] input: Apple, Inc. Apple Internal Keyboard / Trackpad as /devices/pci:00/:00:1d.2/usb5/5-2/5-2:1.0/input/input327 [29553.302959] apple 0003:05AC:0230.0141: input,hidraw1: USB HID v1.11 Keyboard [Apple, Inc. Apple Internal Keyboard / Trackpad] on usb-:00:1d.2-2/input0 [29553.319516] usb 5-2: ctrl urb status -75 received [29553.319649] apple 0003:05AC:0230.0142: hidraw2: USB HID v1.11 Device [Apple, Inc. Apple Internal Keyboard / Trackpad] on usb-:00:1d.2-2/input1 [29553.320775] input: bcm5974 as /devices/pci:00/:00:1d.2/usb5/5-2/5-2:1.2/input/input328 [29553.321224] hub 5-0:1.0: port 2 disabled by hub (EMI?), re-enabling... [29553.321233] usb 5-2: USB disconnect, address 35 [29553.608169] usb 5-2: new full speed USB device using uhci_hcd and address 36 [29553.788672] usb 5-2: New USB device found, idVendor=05ac, idProduct=0230 [29553.788680] usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [29553.788687] usb 5-2: Product: Apple Internal Keyboard / Trackpad [29553.788692] usb 5-2: Manufacturer: Apple, Inc. [29553.75] usb 5-2: configuration #1 chosen from 1 choice [29553.798726] input: Apple, Inc. Apple Internal Keyboard / Trackpad as /devices/pci:00/:00:1d.2/usb5/5-2/5-2:1.0/input/input329 [29553.798886] apple 0003:05AC:0230.0143: input,hidraw1: USB HID v1.11 Keyboard [Apple, Inc. Apple Internal Keyboard / Trackpad] on usb-:00:1d.2-2/input0 [29553.851553] usb 5-2: ctrl urb status -75 received Things work great in 2.6.26, except that extra trackpad features like tap-to-click, and double-finger scroll don't work. -- Package-specific info: ** Version: Linux version 2.6.30-1-amd64 (Debian 2.6.30-6) (wa...@debian.org) (gcc version 4.3.4 (Debian 4.3.4-1) ) #1 SMP Sat Aug 15 18:09:19 UTC 2009 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.30-1-amd64 root=UUID=01948f95-8859-4617-9c54-a16704e84da1 ro noapic quiet ** Tainted: P W (513) ** Kernel log: [34101.608598] usb 5-2: Manufacturer: Apple, Inc. [34101.608788] usb 5-2: configuration #1 chosen from 1 choice [34101.618779] input: Apple, Inc. Apple Internal Keyboard / Trackpad as /devices/pci:00/:00:1d.2/usb5/5-2/5-2:1.0/input/input921 [34101.618932] apple 0003:05AC:0230.0393: input,hidraw1: USB HID v1.11 Keyboard [Apple, Inc. Apple Internal Keyboard / Trackpad] on usb-:00:1d.2-2/input0 [34101.963557] usb 5-2: ctrl urb status -75 received [34101.963717] apple 0003:05AC:0230.0394: hidraw2: USB HID v1.11 Device [Apple, Inc. Apple Internal Keyboard / Trackpad] on usb-:00:1d.2-2/input1 [34101.966741] input: bcm5974 as /devices/pci:00/:00:1d.2/usb5/5-2/5-2:1.2/input/input922 [34102.045515] bcm5974: bcm5974: could not read from device [34102.045520] bcm5974: mode switch failed [34102.060528] bcm5974: bcm5974: could not read from device [34102.060533] bcm5974: mode switch failed [34102.140144] hub 5-0:1.0: port 2 disabled by hub (EMI?), re-enabling... [34102.140150] usb 5-2: USB disconnect, address 82 [34102.432186] usb 5-2: new full speed USB device using uhci_hcd and address 83 [34102.612697] usb 5-2: New USB device found, idVendor=05ac, idProduct=0230 [34102.612705] usb 5-2: New USB
Bug#570382: marked as done (after upgrade: "vlogin: openpty(): No such file or directory")
Your message dated Sat, 13 Jul 2013 00:52:29 +0200 with message-id <20130712225229.GD4722@pisco.westfalen.local> and subject line Closing vserver bugs has caused the Debian Bug report #570382, regarding after upgrade: "vlogin: openpty(): No such file or directory" 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.) -- 570382: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570382 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.26-21lenny3 Severity: normal After upgrading the kernel from linux-image-2.6.26-2-vserver-686 2.6.26-21 to 2.6.26-21lenny3 and rebooting we could not log into the vservers any more and got the mentioned error instead: # vserver foo enter vlogin: openpty(): No such file or directory # since we had some instance where the procedure had worked we compared /dev and added the devices that were not on the instances where it did not work and restarted the vserver instances. Now everything seemed to behave as expected. We're not sure whether adding the devices cured the problem or whether it was restarting the vserver instances or both. We add the following devices under /var/lib/vserver/foo lrwxrwxrwx 1 root root 13 fd -> /proc/self/fd lrwxrwxrwx 1 root root4 stderr -> fd/2 lrwxrwxrwx 1 root root4 stdin -> fd/0 lrwxrwxrwx 1 root root4 stdout -> fd/1 Additionally /var/lib/vserver/foo/dev/[u]random had different permissions (only owner had write permussion). So we added "group" and "other" write permissions: # chmod og+w /var/lib/vserver/foo/dev/*random crw-rw-rw- 1 root root 1, 8 random crw-rw-rw- 1 root root 1, 9 urandom *t -- Package-specific info: ** Version: Linux version 2.6.26-2-vserver-686 (Debian 2.6.26-21lenny3) (da...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Wed Feb 10 10:39:33 UTC 2010 ** Command line: root=/dev/sda6 ro console=tty0 ** Not tainted ** Kernel log: [4.249273] scsi: waiting for bus probes to complete ... [5.596939] scsi[0]: scanning scsi channel 1 [virtual] for logical drives [5.596939] scsi 0:1:0:0: Direct-Access MegaRAID LD 0 RAID1 69G 521S PQ: 0 ANSI: 2 [5.632088] scsi 0:0:6:0: Attached scsi generic sg0 type 3 [5.632195] scsi 0:1:0:0: Attached scsi generic sg1 type 0 [5.636929] Driver 'sd' needs updating - please use bus_type methods [5.636929] sd 0:1:0:0: [sda] 143114240 512-byte hardware sectors (73274 MB) [5.636929] sd 0:1:0:0: [sda] Write Protect is off [5.636929] sd 0:1:0:0: [sda] Mode Sense: 00 00 00 00 [5.636929] sd 0:1:0:0: [sda] Asking for cache data failed [5.636929] sd 0:1:0:0: [sda] Assuming drive cache: write through [5.636929] sd 0:1:0:0: [sda] 143114240 512-byte hardware sectors (73274 MB) [5.636929] sd 0:1:0:0: [sda] Write Protect is off [5.636929] sd 0:1:0:0: [sda] Mode Sense: 00 00 00 00 [5.636929] sd 0:1:0:0: [sda] Asking for cache data failed [5.636929] sd 0:1:0:0: [sda] Assuming drive cache: write through [5.636929] sda: sda1 sda2 < sda5 sda6 sda7 sda8 > [5.654206] sd 0:1:0:0: [sda] Attached SCSI disk [5.908237] device-mapper: uevent: version 1.0.3 [5.908681] device-mapper: ioctl: 4.13.0-ioctl (2007-10-18) initialised: dm-de...@redhat.com [5.931368] PM: Starting manual resume from disk [5.956270] kjournald starting. Commit interval 5 seconds [5.956270] EXT3-fs: mounted filesystem with ordered data mode. [7.046533] udevd version 125 started [7.403059] dcdbas dcdbas: Dell Systems Management Base Driver (version 5.6.0-3.2) [7.651747] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 [7.667746] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [7.835942] EDAC MC: Ver: 2.1.0 Feb 10 2010 [7.839944] Contact your BIOS vendor to see if the E752x error registers can be safely un-hidden [7.891943] input: Power Button (FF) as /class/input/input0 [7.916333] ACPI: Power Button (FF) [PWRF] [8.555946] ACPI Exception (video-1631): AE_NOT_FOUND, Evaluating _DOD [20080321] [8.555946] input: Video Bus as /class/input/input1 [8.575975] ACPI: Video Device [EVGA] (multi-head: no rom: yes post: no) [8.581115] input: PC Speaker as /class/input/input2 [8.719815] usb-storage: device scan complete [8.727946] scsi 1:0:0:0: Direct-Access Seagate FreeAgent102C PQ: 0 ANSI: 4 [8.727946] sd 1:0:0:0: [sdb] 2930277168 512-byte hardware sectors (1500302 MB) [8.731946] sd 1:0:0:0: [sdb] Write Protect is off [8.731946] sd 1:0:0:0: [sdb] Mode Sense: 1c 0
Bug#557033: marked as done (linux-image-2.6.31-1-amd64: Kernel logs WARNING at hpet.c:390.)
Your message dated Sat, 13 Jul 2013 00:51:17 +0200 with message-id <20130712225116.GB4722@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #557033, regarding linux-image-2.6.31-1-amd64: Kernel logs WARNING at hpet.c:390. 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.) -- 557033: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=557033 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Subject: linux-image-2.6.31-1-amd64: Kernel logs WARNING at hpet.c:390. Package: linux-2.6 Version: 2.6.31-1 Severity: normal *** Please type your report below this line *** syslog reports WARNING at hpet.c:390. The system appears to run normally, except for a single message from GNOME: "Your system had a kernel failure". However, hpet.c:390 is an invocation of macro WARN_ON_ONCE, so I wonder if the system might be taking a performance hit if the fault is actually occurring many times (see below for more information on this). The computer is a new Intel core i7-860, Chipset P55, Gigabyte P55UD3p, nVidia Geforce 9600GT. Two Seagate 1TB disks in mirrored RAID configuration. The fault initially occurred in the stable lenny distribution with kernel 2.6.26. I installed linux-image-2.6.31-1-amd64 from sid to see if it would go away. It didn't. A similar fault in linux-image-2.6.26-1-686 was reported in bug report 512617 in January 2009, and closed in July 2009. History of my installation: Initially I installed the 32-bit version of lenny: debian-502-i386-DVD-n.iso. When I booted the system, it wrote WARNING messages from hpet.c at the rate of megabytes per minute. I then installed the 64-bit version of lenny: debian-503-amd64-DVD-n.iso. hpet.c:390 from linux-image-2.6.31-1-amd64 invokes WARN_ON_ONCE, but my previous experience with the 32-bit distribution makes me believe that the fault is in fact occurring many times per second, and hence I wonder if there might be a performance hit. -- Package-specific info: ** Version: Linux version 2.6.31-1-amd64 (Debian 2.6.31-1) (wa...@debian.org) (gcc version 4.3.4 (Debian 4.3.4-5) ) #1 SMP Sat Oct 24 17:50:31 UTC 2009 ** Command line: root=/dev/mapper/isw_ifdfaidbh_Volume05 ro quiet ** Tainted: W (512) * Taint on warning. ** Kernel log: [5.049081] sdb14 sdb15 > [5.072861] sd 5:0:0:0: [sdb] Attached SCSI disk [5.081135] sd 4:0:0:0: Attached scsi generic sg0 type 0 [5.081153] sd 5:0:0:0: Attached scsi generic sg1 type 0 [5.081172] sr 7:0:0:0: Attached scsi generic sg2 type 5 [5.236070] device-mapper: uevent: version 1.0.3 [5.236630] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-de...@redhat.com [5.926876] PM: Starting manual resume from disk [5.950589] kjournald starting. Commit interval 5 seconds [5.950594] EXT3-fs: mounted filesystem with ordered data mode. [6.702415] udevd version 125 started [6.978535] Monitor-Mwait will be used to enter C-1 state [6.978593] Monitor-Mwait will be used to enter C-2 state [6.998699] Monitor-Mwait will be used to enter C-3 state [6.998762] ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3]) [6.998794] processor LNXCPU:00: registered as cooling_device0 [6.998799] ACPI: Processor [CPU0] (supports 8 throttling states) [6.998857] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3 [6.998863] ACPI: Power Button [PWRF] [6.999463] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input4 [6.999468] ACPI: Power Button [PWRB] [7.002603] ACPI: CPU1 (power states: C1[C1] C2[C2] C3[C3]) [7.002624] processor LNXCPU:01: registered as cooling_device1 [7.002629] ACPI: Processor [CPU1] (supports 8 throttling states) [7.027097] ACPI: CPU2 (power states: C1[C1] C2[C2] C3[C3]) [7.027123] processor LNXCPU:02: registered as cooling_device2 [7.027128] ACPI: Processor [CPU2] (supports 8 throttling states) [7.035724] ACPI: CPU3 (power states: C1[C1] C2[C2] C3[C3]) [7.035742] processor LNXCPU:03: registered as cooling_device3 [7.035744] ACPI: Processor [CPU3] (supports 8 throttling states) [7.036353] ACPI: CPU4 (power states: C1[C1] C2[C2] C3[C3]) [7.036375] processor LNXCPU:04: registered as cooling_device4 [7.036380] ACPI: Processor [CPU4] (supports 8 throttling states) [7.037120] ACPI: CPU5 (power states: C1[C1] C2[C2] C3[C3]) [7.037141] processor LNXCPU:05: registered as cooling_device5 [7.037145] ACPI: Processor [CPU5] (supports 8 throttling states) [7.037775] [ cut here ] [7.037782] WAR
Bug#566516: marked as done (linux-image-2.6.32-trunk-686: suspend failure in ehci_hcd)
Your message dated Sat, 13 Jul 2013 00:50:45 +0200 with message-id <20130712225044.GA4722@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #566516, regarding linux-image-2.6.32-trunk-686: suspend failure in ehci_hcd 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.) -- 566516: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=566516 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.32-5 Severity: normal Sometimes, my Eee PC 1000HG fails to suspend and I get: [130899.106047] sd 0:0:0:0: [sda] Stopping disk [130899.971193] ACPI handle has no context! [130899.971205] ACPI handle has no context! [130899.984470] ata_piix :00:1f.2: PCI INT B disabled [130900.000260] hcd_pci_suspend(): ehci_pci_suspend+0x0/0x6f [ehci_hcd] returns -22 [130900.000305] pci_pm_suspend(): hcd_pci_suspend+0x0/0x6c [usbcore] returns -22 [130900.000324] pm_op(): pci_pm_suspend+0x0/0xc1 returns -22 [130900.000335] PM: Device :00:1d.7 failed to suspend: error -22 [130900.000342] PM: Some devices failed to suspend Running rmmod ehci_hcd && modprobe ehci_hcd cures the problem. Cheers! Thiemo Nagel -- Package-specific info: ** Version: Linux version 2.6.32-trunk-686 (Debian 2.6.32-5) (b...@decadent.org.uk) (gcc version 4.3.4 (Debian 4.3.4-6) ) #1 SMP Sun Jan 10 06:32:16 UTC 2010 ** Command line: BOOT_IMAGE=//vmlinuz-2.6.32-trunk-686 root=/dev/mapper/sda7_crypt ro vga=6 quiet ** Tainted: W (512) * Taint on warning. ** Kernel log: [132849.248274] CPU1 attaching sched-domain: [132849.248284] domain 0: span 0-1 level SIBLING [132849.248294] groups: 1 (cpu_power = 589) 0 (cpu_power = 589) [132849.248317] domain 1: span 0-1 level MC [132849.248327]groups: 0-1 (cpu_power = 1178) [132849.932710] CPU0 attaching NULL sched-domain. [132849.932722] CPU1 attaching NULL sched-domain. [132849.953142] CPU0 attaching sched-domain: [132849.953153] domain 0: span 0-1 level SIBLING [132849.953161] groups: 0 (cpu_power = 589) 1 (cpu_power = 589) [132849.953178] domain 1: span 0-1 level MC [132849.953185]groups: 0-1 (cpu_power = 1178) [132849.953200] CPU1 attaching sched-domain: [132849.953207] domain 0: span 0-1 level SIBLING [132849.953214] groups: 1 (cpu_power = 589) 0 (cpu_power = 589) [132849.953230] domain 1: span 0-1 level MC [132849.953237]groups: 0-1 (cpu_power = 1178) [132859.880981] pci :01:00.0: reg 10 64bit mmio: [0x00-0x00] [132860.215158] ath5k :01:00.0: enabling device ( -> 0002) [132860.215193] ath5k :01:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19 [132860.215232] ath5k :01:00.0: setting latency timer to 64 [132860.215905] ath5k :01:00.0: registered as 'phy5' [132860.717603] ath: EEPROM regdomain: 0x60 [132860.717615] ath: EEPROM indicates we should expect a direct regpair map [132860.717629] ath: Country alpha2 being used: 00 [132860.717637] ath: Regpair used: 0x60 [132860.718579] phy5: Selected rate control algorithm 'minstrel' [132860.722900] Registered led device: ath5k-phy5::rx [132860.723100] Registered led device: ath5k-phy5::tx [132860.723115] ath5k phy5: Atheros AR2425 chip found (MAC: 0xe2, PHY: 0x70) [132865.161498] ADDRCONF(NETDEV_UP): wlan0: link is not ready [132873.329256] wlan0: direct probe to AP 00:1c:f0:84:61:52 (try 1) [132873.329344] wlan0: deauthenticating from 00:1c:f0:84:61:52 by local choice (reason=3) [132873.329408] wlan0: direct probe to AP 00:1c:f0:84:61:52 (try 1) [132873.331907] wlan0: direct probe responded [132873.331907] wlan0: authenticate with AP 00:1c:f0:84:61:52 (try 1) [132873.335760] wlan0: authenticated [132873.335823] wlan0: associate with AP 00:1c:f0:84:61:52 (try 1) [132873.337770] wlan0: RX AssocResp from 00:1c:f0:84:61:52 (capab=0x431 status=0 aid=2) [132873.337780] wlan0: associated [132873.339501] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [132884.068067] wlan0: no IPv6 routers present [132980.345052] rpcbind: server lurch.nestnet not responding, timed out [136698.891529] CPU0 attaching NULL sched-domain. [136698.891548] CPU1 attaching NULL sched-domain. [136698.945259] CPU0 attaching sched-domain: [136698.945280] domain 0: span 0-1 level SIBLING [136698.945296] groups: 0 (cpu_power = 589) 1 (cpu_power = 589) [136698.945329] domain 1: span 0-1 level MC [136698.945343]groups: 0-1 (cpu_power = 1178) [136698.945372] CPU1 attaching sched-domain: [136698.945385] domain 0: span 0-1 level SIBLING [136698.945399] groups: 1 (cpu_power = 589) 0 (cpu_power = 589) [136698.945431] domain 1: span 0-1 level MC [136698.945445]g
Bug#704564: not working here
FWIW - after having installed the linux-image-3.10-rc7-amd64 kernel from experimental I saw it complain that it couldn't find SUMO_uvd.bin. I found the suggestion in this bugreport and thus put http://people.freedesktop.org/~agd5f/radeon_ucode/SUMO_uvd.bin under /lib/firmware/radeon. The result was this when booting: [ 13.939512] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 14.951349] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 15.963186] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 16.975017] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 17.986858] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 18.998687] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 20.010522] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 21.022360] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 22.034199] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 23.046026] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 23.065939] [drm:r600_uvd_init] *ERROR* UVD not responding, giving up!!! [ 23.066004] [drm:evergreen_startup] *ERROR* radeon: error initializing UVD (-1). Note that's 10 seconds of boot delay. It's well possible that I did something other wrong though (there's no howto so...). *t -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/alpine.DEB.2.02.130710250.7703@hier
Processed: tagging 572537
Processing commands for cont...@bugs.debian.org: > tags 572537 + pending Bug #572537 [src:linux] udev spins on drm device Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 572537: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572537 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.137364235528343.transcr...@bugs.debian.org
Processed: reassign 572537 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 572537 src:linux Bug #572537 [linux-2.6] udev spins on drm device Bug reassigned from package 'linux-2.6' to 'src:linux'. No longer marked as found in versions 2.6.32-8 and 2.6.32-9. Ignoring request to alter fixed versions of bug #572537 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 572537: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572537 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.137364213126450.transcr...@bugs.debian.org
Bug#599768: [PATCH] toshiba_acpi: backlight broken after resume.
reassign 599768 src:linux thanks On Sun, Nov 13, 2011 at 08:17:47PM -0430, Niv Sardi wrote: > > Hi, > > this was first sent to debian as bug 599768, but Ben Hutchings > recommended sending it to you guys too. > > anyway, the drill: backlight on my R800 laptop works fine until I > suspend it, then, /sys/class/backlight/* doesn't change anything > anymore. > > This patch is taken from the old toshset tool (that. btw. seems to > document a few HCI commands we're not using in the toshiba_acpi code, > maybe interesting to have a look), and the important part is the code > that sets HCI_LCD_BRIGHTNESS in set_lcd. > > after this patch, backlight works through > /sys/class/backlight/toshiba/brightness but for some reason the keys > (that are still detected) don't trigger any backlight change (or call of > set_lcd), ... and I really don't know how to debug that. (they still get > to me in the .notify callback, but I fail to find documentation on the > link between that and get_lcd... > > (do I need to call backlight_device_register() or something along the > lines of the sparse_keymap code on resume ?) > > anyway, I understand this patch is nowhere near ready for inclusion, but > I send it in order to see if it gives someone a clue to fix this > longstanding issue with toshiba backlights. Does this still affect current kernels? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130712150836.ga23...@inutil.org
Processed: reassign 631567 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 631567 src:linux Bug #631567 [linux-2.6] radeon may crash if CONFIG_VIDEO_OUTPUT_CONTROL disabled Bug reassigned from package 'linux-2.6' to 'src:linux'. No longer marked as found in versions linux-2.6/2.6.39-2. Ignoring request to alter fixed versions of bug #631567 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 631567: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631567 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.137364197224752.transcr...@bugs.debian.org
Bug#584830: marked as done (linux-image-2.6.32-5-amd64: USB 3.0 / xhci prevents suspend)
Your message dated Fri, 12 Jul 2013 17:08:49 +0200 with message-id <20130712150849.gc23...@inutil.org> and subject line Re: Fixed in recent kernel versions has caused the Debian Bug report #584830, regarding linux-image-2.6.32-5-amd64: USB 3.0 / xhci prevents suspend 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.) -- 584830: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584830 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.32-15 Severity: normal My motherboard includes a USB 3.0 controller, handled by the xhci module. When the xhci module is loaded, the system fails to suspend with the following log messages: [ 458.601622] pm_op(): usb_dev_suspend+0x0/0xa [usbcore] returns -2 [ 458.601624] PM: Device usb2 failed to suspend: error -2 When I unload the xhci module, the system suspends just fine, without this message. Relevant `lsusb -v` and dmesg output parts follow: # lsusb -v [ ... ] Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 3.00 bDeviceClass9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 3 bMaxPacketSize0 9 idVendor 0x1d6b Linux Foundation idProduct 0x0003 3.0 root hub bcdDevice2.06 iManufacturer 3 Linux 2.6.32-5-amd64 xhci_hcd iProduct2 xHCI Host Controller iSerial 1 :04:00.0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 12 Hub Descriptor: bLength 9 bDescriptorType 41 nNbrPorts 4 wHubCharacteristic 0x0009 Per-port power switching Per-port overcurrent protection TT think time 8 FS bits bPwrOn2PwrGood 10 * 2 milli seconds bHubContrCurrent 0 milli Ampere DeviceRemovable0x00 PortPwrCtrlMask0xff Hub Port Status: Port 1: .0100 power Port 2: .0100 power Port 3: .0100 power Port 4: .0100 power Device Status: 0x0003 Self Powered Remote Wakeup Enabled # pm-suspend # dmesg [ ... ] [ 457.630373] PM: Syncing filesystems ... done. [ 457.744997] PM: Preparing system for mem sleep [ 457.747218] Freezing user space processes ... (elapsed 0.00 seconds) done. [ 457.747607] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done. [ 457.747642] PM: Entering mem sleep [ 457.747653] Suspending console(s) (use no_console_suspend to debug) [ 457.812103] sd 3:0:0:0: [sdb] Synchronizing SCSI cache [ 457.812321] sd 3:0:0:0: [sdb] Stopping disk [ 458.225455] sd 2:0:0:0: [sda] Synchronizing SCSI cache [ 458.240627] sd 2:0:0:0: [sda] Stopping disk [ 458.601622] pm_op(): usb_dev_suspend+0x0/0xa [usbcore] returns -2 [ 458.601624] PM: Device usb2 failed to suspend: error -2 [ 458.601626] PM: Some devices failed to suspend [ 458.822063] sd 2:0:0:0: [sda] Starting disk [ 460.874188] sd 3:0:0:0: [sdb] Starting disk [ 465.811159] PM: Finishing wakeup. [ 465.811160] Restarting tasks ... done. # modprobe -r xhci # pm-suspend -- Suspend then works without a problem. dmesg output is, as one would expect, full of what looks to me like routine device suspend, later resume, log messages. The USB 3.0 controller doesn't appear in the USB device list reportbug added below since the module has been unloaded. It appears in the PCI device list, though, in case that helps. -- Package-specific info: ** Version: Linux version 2.6.32-5-amd64 (Debian 2.6.32-15) (b...@decadent.org.uk) (gcc version 4.3.
Processed: Re: [PATCH] toshiba_acpi: backlight broken after resume.
Processing commands for cont...@bugs.debian.org: > reassign 599768 src:linux Bug #599768 [linux-2.6] linux-image-2.6.32-5-686: backlight control fails after resume from suspend (toshiba r700-155) Bug reassigned from package 'linux-2.6' to 'src:linux'. No longer marked as found in versions linux-2.6/3.0.0~rc6-1~experimental.1, 3.1.0-1, 2.6.32-23, and 2.6.32-25. Ignoring request to alter fixed versions of bug #599768 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 599768: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599768 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.137364192824431.transcr...@bugs.debian.org
Processed: reassign 673511 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 673511 src:linux Bug #673511 [linux-2.6] brcmsmacs: mode IBSS not implemented for Broadcom Wirless LAN controllers Bug reassigned from package 'linux-2.6' to 'src:linux'. No longer marked as found in versions 3.2.17-1. Ignoring request to alter fixed versions of bug #673511 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 673511: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673511 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.137364196724703.transcr...@bugs.debian.org
Bug#677655: 3.4-trunk-486: kernel oops: EIP is at __destroy_inode+0x56/0x8d
It still does with 3.2 in stable, but not with 3.9 in testing. Martin-Éric 2013/7/12 Moritz Muehlenhoff > reassign 677655 src:linux > thanks > > On Sat, Jun 16, 2012 at 03:48:45AM -0500, Jonathan Nieder wrote: > > Martin-Éric Racine wrote: > > > > > Yup, this issue returns every now and then on the exact same host > > > (which was recently migrated from Ubuntu to Debian, now that Ubuntu > > > stopped supporting anything older than non-PAE 686 hardware), whenever > > > someone touches the inode code again. The nice thing, this time, is > > > that it has become non-fatal; the kernel simply reports the oops and > > > continues operating. > > > > Thanks for the background. That would have indeed been useful context > > in the original report (though perhaps it had been long enough since > > the last appearance that you had forgotten). > > > > If I have any more questions, I'll ask them upstream. > > Does this still occur with current kernels? > > Cheers, > Moritz >
Bug#677655: 3.4-trunk-486: kernel oops: EIP is at __destroy_inode+0x56/0x8d
reassign 677655 src:linux thanks On Sat, Jun 16, 2012 at 03:48:45AM -0500, Jonathan Nieder wrote: > Martin-Éric Racine wrote: > > > Yup, this issue returns every now and then on the exact same host > > (which was recently migrated from Ubuntu to Debian, now that Ubuntu > > stopped supporting anything older than non-PAE 686 hardware), whenever > > someone touches the inode code again. The nice thing, this time, is > > that it has become non-fatal; the kernel simply reports the oops and > > continues operating. > > Thanks for the background. That would have indeed been useful context > in the original report (though perhaps it had been long enough since > the last appearance that you had forgotten). > > If I have any more questions, I'll ask them upstream. Does this still occur with current kernels? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130712074654.ga3...@inutil.org
Processed: Re: 3.4-trunk-486: kernel oops: EIP is at __destroy_inode+0x56/0x8d
Processing commands for cont...@bugs.debian.org: > reassign 677655 src:linux Bug #677655 [linux-2.6] 3.4-trunk-486: kernel oops: EIP is at __destroy_inode+0x56/0x8d Bug reassigned from package 'linux-2.6' to 'src:linux'. No longer marked as found in versions 3.4.1-1~experimental.1. Ignoring request to alter fixed versions of bug #677655 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 677655: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677655 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.137361542517344.transcr...@bugs.debian.org
