Fwd: Web subscription for linux package
Hi everybody, I'm subscribed in the linux package, and hope to help. Thank you. Geyslan Gregório Bem http://hackingbits.com -- Forwarded message -- From: ow...@packages.qa.debian.org Date: 2013/1/27 Subject: Re: Web subscription for linux package To: geys...@gmail.com Processing commands for p...@qa.debian.org: Subject: Web subscription for linux package subscribe linux geys...@gmail.com A confirmation mail has been sent to geys...@gmail.com. keyword linux geys...@gmail.com = bts bts-control upload-source katie-other summary default cvs ddtp derivatives derivatives-bugs contact buildd Here's the new list of accepted keywords associated to package linux for geys...@gmail.com : * default * bts * bts-control * cvs * summary * ddtp * upload-source * katie-other * derivatives * derivatives-bugs * contact * buildd
Bug#687442: Bug#692234: Processed: severity of 689268 is important
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 26.01.2013 23:37, schrieb Ben Hutchings: Julien Cristau prepared some packages for testing before we make this change. Here's how you would install them with APT: gpg --no-default-keyring --keyring /usr/share/keyrings/debian-keyring.gpg --export 310180050905E40C | apt-key add - echo deb http://people.debian.org/~jcristau/wheezy-drm34/ ./ /etc/apt/sources.list.d/jcristau-wheezy-drm34.list apt-get update apt-get install linux-image-3.2.0-4.drm-amd64 # or -486, or -686-pae Please test and send your results (good or bad) to 687...@bugs.debian.org I already posted here several weeks ago: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692234#433 that I cannot test without the matching linux-header package! This headers are still missing in his repo. I'll test as soon as headers are available - please let me know. /Ingo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlEFDI8ACgkQx2YcFfrwLxMAUACfQ/9YomlVoJk1V1+YBfrMo+Op AckAnA1XiU/xGlRnoT+LV3cGhOtpK6XV =I+mX -END PGP SIGNATURE- -- 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/51050cb2.2030...@gmx.net
Re: Re: include/linux/version.h missing in 3.7
Thanks for your answer! VMware needs to be updated. Okay. Then I'm going to patch vmware ;-( Bye -- 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/510517c9.8090...@gmx.de
Bug#692234: Processed: severity of 689268 is important
On Sun, 2013-01-27 at 12:17 +0100, Ingo wrote: Am 26.01.2013 23:37, schrieb Ben Hutchings: Julien Cristau prepared some packages for testing before we make this change. Here's how you would install them with APT: gpg --no-default-keyring --keyring /usr/share/keyrings/debian-keyring.gpg --export 310180050905E40C | apt-key add - echo deb http://people.debian.org/~jcristau/wheezy-drm34/ ./ /etc/apt/sources.list.d/jcristau-wheezy-drm34.list apt-get update apt-get install linux-image-3.2.0-4.drm-amd64 # or -486, or -686-pae Please test and send your results (good or bad) to 687...@bugs.debian.org I already posted here several weeks ago: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692234#433 that I cannot test without the matching linux-header package! This headers are still missing in his repo. I'll test as soon as headers are available - please let me know. The ABI should be the same as for 3.2.0-4, except for the DRM (which it appears is not used by any out-of-tree module). So you can just copy the VirtualBox modules from /lib/modules/3.2.0-4-amd4/extra to /lib/modules/3.2.0-4.drm-amd64/extra Ben. -- Ben Hutchings Experience is what causes a person to make new mistakes instead of old ones. signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#699091: linux-image-3.2.0-4-amd64: kernel BUG: Bad page map in process udevd
Processing control commands: tag -1 moreinfo Bug #699091 [src:linux] linux-image-3.2.0-4-amd64: kernel BUG: Bad page map in process udevd Added tag(s) moreinfo. -- 699091: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699091 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.b699091.135929115124149.transcr...@bugs.debian.org
Bug#699091: linux-image-3.2.0-4-amd64: kernel BUG: Bad page map in process udevd
Control: tag -1 moreinfo On Sun, 2013-01-27 at 12:37 +, Jules Villard wrote: Package: src:linux Version: 3.2.35-2 Severity: normal Dear Maintainer, I hit a few BUGs at the end of boot time (see dmesg). They do not seem to visibly affect the stability of the system. There's also a swap_free: Bad swap offset entry 7fffc4010a6aa0 in the mix... [...] Please use memtest86+ to test the memory in this system. Ben. -- Ben Hutchings Experience is what causes a person to make new mistakes instead of old ones. signature.asc Description: This is a digitally signed message part
Bug#699091: linux-image-3.2.0-4-amd64: kernel BUG: Bad page map in process udevd
On Sun, 27 Jan 2013 12:52:26 +, Ben Hutchings wrote: On Sun, 2013-01-27 at 12:37 +, Jules Villard wrote: Package: src:linux Version: 3.2.35-2 Severity: normal Dear Maintainer, I hit a few BUGs at the end of boot time (see dmesg). They do not seem to visibly affect the stability of the system. There's also a swap_free: Bad swap offset entry 7fffc4010a6aa0 in the mix... [...] Please use memtest86+ to test the memory in this system. No errors in 1 pass. I will test again more thoroughly tonight. Cheers, Jules -- 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/20130127141049.ga3...@roquette.roquette.dyndns.org
Bug#699056: linux-image-3.2.0-4-amd64: kernel BUG at /build/buildd-linux_3.2.35-2-amd64-v9djlH/linux-3.2.35/fs/locks.c:2104!
On Sun, 27 Jan 2013, Ben Hutchings wrote: tracking the bug. The bad thing is, that I don't have direct access to the console of the system, a 48-core machine with 512 GB main memory. How about netconsole or an IPMI serial console? The IPMI console is unreliable (connections are closed after a while; if the computer is stalled, it is just black). I just did not know the netconsole and started this now and will provide more information, if (when) the next Bug appears. After rebooting, the following error is found in kern.log: Jan 26 15:19:19 prost kernel: [798028.655254] [ cut here ] Jan 26 15:19:19 prost kernel: [798028.659193] kernel BUG at /build/buildd-linux_3.2.35-2-amd64-v9djlH/linux-3.2.35/fs/locks.c:2104! Jan 26 15:19:19 prost kernel: [798028.659193] invalid opcode: [#1] SMP Jan 26 15:19:19 prost kernel: [798028.659193] CPU 0 [...] That's all it says? Nothing more before the next boot messages? nothing. Thank you, Erik -- 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.1301271623050.24948@kule.heimat
Bug#699056: linux-image-3.2.0-4-amd64: kernel BUG at /build/buildd-linux_3.2.35-2-amd64-v9djlH/linux-3.2.35/fs/locks.c:2104!
Control: tag -1 moreinfo On Sun, 2013-01-27 at 16:33 +0100, Erik Braun wrote: On Sun, 27 Jan 2013, Ben Hutchings wrote: tracking the bug. The bad thing is, that I don't have direct access to the console of the system, a 48-core machine with 512 GB main memory. How about netconsole or an IPMI serial console? The IPMI console is unreliable (connections are closed after a while; if the computer is stalled, it is just black). I just did not know the netconsole and started this now and will provide more information, if (when) the next Bug appears. Thanks. After rebooting, the following error is found in kern.log: Jan 26 15:19:19 prost kernel: [798028.655254] [ cut here ] Jan 26 15:19:19 prost kernel: [798028.659193] kernel BUG at /build/buildd-linux_3.2.35-2-amd64-v9djlH/linux-3.2.35/fs/locks.c:2104! Jan 26 15:19:19 prost kernel: [798028.659193] invalid opcode: [#1] SMP Jan 26 15:19:19 prost kernel: [798028.659193] CPU 0 [...] That's all it says? Nothing more before the next boot messages? nothing. I'm going to leave this until you get a more complete crash log from netconsole. Ben. -- Ben Hutchings Experience is what causes a person to make new mistakes instead of old ones. signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#699056: linux-image-3.2.0-4-amd64: kernel BUG at /build/buildd-linux_3.2.35-2-amd64-v9djlH/linux-3.2.35/fs/locks.c:2104!
Processing control commands: tag -1 moreinfo Bug #699056 [src:linux] linux-image-3.2.0-4-amd64: kernel BUG at /build/buildd-linux_3.2.35-2-amd64-v9djlH/linux-3.2.35/fs/locks.c:2104! Added tag(s) moreinfo. -- 699056: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699056 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.b699056.135930305718223.transcr...@bugs.debian.org
Bug#698917: [wheezy] cpu overheat and shutdown after suspend/resume cycle on Thinkpad T410
Hi, On Fri, Jan 25, 2013 at 01:45:21PM -0800, Jonathan Nieder wrote: Yikes. Has this machine always behaved this way, or did it start happening with a kernel update? If the latter, which update? Does 3.7.y from experimental exhibit the same symptoms? If so, please report this at http://bugzilla.kernel.org/, product Power Management, component Hibernation/Suspend and let us know the bug number so we can track it. Same with 3.7.3 from experimental - Ran it for a day - this morning resume - Worked for nearly an hour - Emergency Shutdown Opened a bug in the Kernel Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=53101 Jan 26 00:43:03 p2 kernel: imklog 5.8.11, log source = /proc/kmsg started. Jan 26 00:43:03 p2 kernel: [0.00] Initializing cgroup subsys cpuset Jan 26 00:43:03 p2 kernel: [0.00] Initializing cgroup subsys cpu Jan 26 00:43:03 p2 kernel: [0.00] Linux version 3.7-trunk-amd64 (debian-kernel@lists.debian.org) (gcc version 4.7.2 (Debian 4.7.2-5) ) #1 SMP Debian 3.7.3-1~experimental.1 Jan 26 00:43:03 p2 kernel: [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.7-trunk-amd64 root=/dev/mapper/p2-root ro Jan 26 00:43:03 p2 kernel: [0.00] e820: BIOS-provided physical RAM map: Jan 26 00:43:03 p2 kernel: [0.00] BIOS-e820: [mem 0x-0x0009e7ff] usable Jan 26 00:43:03 p2 kernel: [0.00] BIOS-e820: [mem 0x0009e800-0x0009] reserved Jan 26 00:43:03 p2 kernel: [0.00] BIOS-e820: [mem 0x000d2000-0x000d3fff] reserved Jan 26 00:43:03 p2 kernel: [0.00] BIOS-e820: [mem 0x000dc000-0x000f] reserved Jan 26 00:43:03 p2 kernel: [0.00] BIOS-e820: [mem 0x0010-0xbb27bfff] usable [...] Jan 27 14:11:27 p2 kernel: [ 4087.016757] usbcore: registered new interface driver usbhid Jan 27 14:11:27 p2 kernel: [ 4087.016763] usbhid: USB HID core driver Jan 27 14:11:27 p2 kernel: [ 4087.245163] input: HID 062a: as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/input/input17 Jan 27 14:11:27 p2 kernel: [ 4087.245447] hid-generic 0003:062A:.0001: input,hidraw0: USB HID v1.10 Mouse [HID 062a:] on usb-:00:1a.0-1.1/input0 Jan 27 15:00:41 p2 kernel: [ 7034.297238] thermal_sys: Critical temperature reached (100 C), shutting down Jan 27 15:00:43 p2 kernel: [ 7036.212853] nfsd: last server has exited, flushing export cache Jan 27 15:00:43 p2 kernel: [ 7036.262334] CPU2: Core temperature above threshold, cpu clock throttled (total events = 1) Jan 27 15:00:43 p2 kernel: [ 7036.262336] CPU3: Core temperature above threshold, cpu clock throttled (total events = 1) Jan 27 15:00:43 p2 kernel: [ 7036.265429] CPU2: Core temperature/speed normal Jan 27 15:00:43 p2 kernel: [ 7036.265431] CPU3: Core temperature/speed normal Jan 27 15:00:44 p2 kernel: [ 7036.456924] e1000e :00:19.0: irq 46 for MSI/MSI-X Jan 27 15:00:44 p2 kernel: [ 7036.492898] Bridge firewalling registered Jan 27 15:00:44 p2 kernel: [ 7036.518914] fuse exit Jan 27 15:01:46 p2 kernel: [0.00] Initializing cgroup subsys cpuset Jan 27 15:01:46 p2 kernel: [0.00] Initializing cgroup subsys cpu Jan 27 15:01:46 p2 kernel: [0.00] Linux version 3.7-trunk-amd64 (debian-kernel@lists.debian.org) (gcc version 4.7.2 (Debian 4.7.2-5) ) #1 SMP Debian 3.7.3-1~experimental.1 Jan 27 15:01:46 p2 kernel: [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.7-trunk-amd64 root=/dev/mapper/p2-root ro Jan 27 15:01:46 p2 kernel: [0.00] e820: BIOS-provided physical RAM map: Jan 27 15:01:46 p2 kernel: [0.00] BIOS-e820: [mem 0x-0x0009e7ff] usable Flo -- Florian Lohoff f...@zz.de signature.asc Description: Digital signature
Processed: tagging 698917, bug 698917 is forwarded to https://bugzilla.kernel.org/show_bug.cgi?id=53101
Processing commands for cont...@bugs.debian.org: tags 698917 - moreinfo Bug #698917 [src:linux] linux-image-3.2.0-4-amd64: cpu overheat and shutdown after suspend/resume cycle on Thinkpad T410 Removed tag(s) moreinfo. forwarded 698917 https://bugzilla.kernel.org/show_bug.cgi?id=53101 Bug #698917 [src:linux] linux-image-3.2.0-4-amd64: cpu overheat and shutdown after suspend/resume cycle on Thinkpad T410 Set Bug forwarded-to-address to 'https://bugzilla.kernel.org/show_bug.cgi?id=53101'. thanks Stopping processing here. Please contact me if you need assistance. -- 698917: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698917 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.135930661912284.transcr...@bugs.debian.org
Bug#696650: fsync() on read-only RAID triggers BUG
On Sat, Jan 26, 2013 at 07:44:40PM +, Ben Hutchings wrote: I applied this on top of 3.2.37 and it certainly fixes the crash. However I wonder whether fsync() should fail or should immediately succeed. I don't know whether the installer expects it to succeed. It should succeed. -- 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/20130127163942.ga28...@infradead.org
Bug#687442: Julien Cristau wheezy-drm34
Hi Julien, Ben: Standard kernel 3.2 in wheezy is unusuable for me in this laptop (ASUS A55V, core i7 3rd gen.). The machine boots and works ok for a while (minutes)...but suddenly it hard freezes. If I'm listening to music...the music stays in a loop when it freezes. Kernels 3.2 made this machine work OK...until 3.7.x from experimental. I attach the lspci and lsusb of this machine. I read yesterday in pdo the post from Ben Hutchings and decided to give a try to kernel-3.2 prepared by Julien. It seems this kernel has the right patches applied, at least for me. The laptop is working OK for 3hours, and suspend and resume seem to work. I still detect a pair of minor glitches with this kernel: 1) The sd-card reader in the laptop is not detected, even kernel 3.7.x can't detect it. 2) The function keys for screen brightness adjustment are not detected...I checked that kernel 3.7.x could detect them and worked as expected. I don't know if these bits could be backported. So thanks to all the people working to make wheezy a great version! A. Corbi. -- 00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09) Subsystem: ASUSTeK Computer Inc. Device 1457 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- INTx- Latency: 0 Capabilities: access denied Kernel driver in use: agpgart-intel 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: e000-efff Memory behind bridge: f600-f70f Prefetchable memory behind bridge: e000-e9ff Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: access denied Kernel driver in use: pcieport 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device 1457 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 47 Region 0: Memory at f740 (64-bit, non-prefetchable) [size=4M] Region 2: Memory at d000 (64-bit, prefetchable) [size=256M] Region 4: I/O ports at f000 [size=64] Expansion ROM at unassigned [disabled] Capabilities: access denied Kernel driver in use: i915 00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04) (prog-if 30 [XHCI]) Subsystem: ASUSTeK Computer Inc. Device 1457 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 48 Region 0: Memory at f7a0 (64-bit, non-prefetchable) [size=64K] Capabilities: access denied Kernel driver in use: xhci_hcd 00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04) Subsystem: ASUSTeK Computer Inc. Device 1457 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx+ Latency: 0 Interrupt: pin A routed to IRQ 11 Region 0: Memory at f7a1a000 (64-bit, non-prefetchable) [size=16] Capabilities: access denied 00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04) (prog-if 20 [EHCI]) Subsystem: ASUSTeK Computer Inc. Device 1457 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 16 Region 0: Memory at f7a18000 (32-bit, non-prefetchable) [size=1K] Capabilities:
Bug#699112: Regression in timekeeping causes some programs to run slowly
Package: src:linux-2.6 Version: 2.6.32-47 Severity: important Tags: patch upstream It was reported on the stable mailing list that one of the timekeeping fixes in 2.6.32.60 causes some programs to sleep for longer than they should. Romain Francoise rom...@orebokech.com wrote: [...] There are two separate workloads that are affected by this issue: - one is a pretty typical whole-distribution build, which gets 1.5x to 2x slower with v2.6.32.60 - the other is a code simulator, which is basically a bunch of processes communicating together using POSIX message queues (mq_timedsend() and mq_timedreceive()). It runs approximately 10x slower, but doesn't seem to use more CPU, it just sits there doing pretty much nothing. I managed to narrow the second workload down to a single test case, which runs in approximately 0.7s in v2.6.32.59 and 8s (!) in v2.6.32.60. Having a simple test case allowed me to do a full bisection in a test VM, and it ends on commit 61b76840ddee647c0c223365378c3f394355b7d7 (time: Avoid making adjustments if we haven't accumulated anything). [...] John Stultz, who made the upstream change and backported it to 2.6.32, said this fix could be reverted as unsuitable for 2.6.32 and not that important, though it may be possible to fix it up. Ben. -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 3.2.0-4.drm-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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/20130127184154.28469.13266.report...@deadeye.wl.decadent.org.uk
Processed: tagging 699112
Processing commands for cont...@bugs.debian.org: tags 699112 + pending Bug #699112 [src:linux-2.6] Regression in timekeeping causes some programs to run slowly Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 699112: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699112 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.135931263222966.transcr...@bugs.debian.org
Processed: retitle 699129 to alx driver for Atheros AR8161/AR8162 is not included
Processing commands for cont...@bugs.debian.org: retitle 699129 alx driver for Atheros AR8161/AR8162 is not included Bug #699129 [linux-image-3.2.0-4-amd64] AR8161 Gigabit Ethernet not detected by Debian Wheezy Changed Bug title to 'alx driver for Atheros AR8161/AR8162 is not included' from 'AR8161 Gigabit Ethernet not detected by Debian Wheezy' thanks Stopping processing here. Please contact me if you need assistance. -- 699129: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699129 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.13593281976850.transcr...@bugs.debian.org
Processed: affects 699112
Processing commands for cont...@bugs.debian.org: affects 699112 + release.debian.org Bug #699112 [src:linux-2.6] Regression in timekeeping causes some programs to run slowly Added indication that 699112 affects release.debian.org thanks Stopping processing here. Please contact me if you need assistance. -- 699112: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699112 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.135932999721803.transcr...@bugs.debian.org
Processed: severity of 699129 is important
Processing commands for cont...@bugs.debian.org: # hardware support is important severity 699129 important Bug #699129 [linux-image-3.2.0-4-amd64] alx driver for Atheros AR8161/AR8162 is not included Severity set to 'important' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 699129: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699129 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.135933074727413.transcr...@bugs.debian.org
Processed: tagging 699129
Processing commands for cont...@bugs.debian.org: tags 699129 + pending Bug #699129 [linux-image-3.2.0-4-amd64] alx driver for Atheros AR8161/AR8162 is not included Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 699129: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699129 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.135933256510630.transcr...@bugs.debian.org
Bug#699140: Linux as of 3.8-rc5 doesn't support NCT6779D hw sensor
Package: src:linux-2.6 Severity: normal Tags: upstream patch Some newer desktop motherboards, including my ASUS P8Z77-V LE and at least some other ASUS Z77-based ones, contain a NCT6779D sensor which isn't supported by the w83627ehf driver or any other kernel driver. There is a working driver at https://github.com/groeck/nct6775 (last time submitted for reviewing at http://lists.lm-sensors.org/pipermail/lm- sensors/2012-December/037817.html ). It will replace the w83627ehf driver for NCT6775F and NCT6776F, and provides support for NCT6779D. Here is its output on my system: nct6779-isa-0290 Adapter: ISA adapter in0:+0.94 V (min = +0.00 V, max = +1.74 V) in1:+1.01 V (min = +0.00 V, max = +0.00 V) ALARM in2:+3.41 V (min = +0.00 V, max = +0.00 V) ALARM in3:+3.41 V (min = +0.00 V, max = +0.00 V) ALARM in4:+1.02 V (min = +0.00 V, max = +0.00 V) ALARM in5:+2.04 V (min = +0.00 V, max = +0.00 V) ALARM in6:+0.29 V (min = +0.00 V, max = +0.00 V) ALARM in7:+3.42 V (min = +0.00 V, max = +0.00 V) ALARM in8:+3.38 V (min = +0.00 V, max = +0.00 V) ALARM in9:+1.06 V (min = +0.00 V, max = +0.00 V) ALARM in10: +0.22 V (min = +0.00 V, max = +0.00 V) ALARM in11: +0.18 V (min = +0.00 V, max = +0.00 V) ALARM in12: +0.18 V (min = +0.00 V, max = +0.00 V) ALARM in13: +0.18 V (min = +0.00 V, max = +0.00 V) ALARM in14: +0.18 V (min = +0.00 V, max = +0.00 V) ALARM fan1: 873 RPM (min =0 RPM) fan2: 581 RPM (min =0 RPM) fan3: 0 RPM (min =0 RPM) fan4: 0 RPM (min =0 RPM) fan5: 0 RPM (min =0 RPM) SYSTIN: +32.0°C (high = +0.0°C, hyst = +0.0°C) ALARM sensor = thermistor CPUTIN: +36.5°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor AUXTIN0: +102.0°Csensor = thermistor AUXTIN1: +102.0°Csensor = thermistor AUXTIN2: +102.0°Csensor = thermistor AUXTIN3: +8.0°Csensor = thermal diode PCH_CHIP_CPU_MAX_TEMP: +0.0°C PCH_CHIP_TEMP: +0.0°C PCH_CPU_TEMP:+0.0°C PCH_MCH_TEMP:+0.0°C cpu0_vid: +0.000 V intrusion0:ALARM intrusion1:ALARM See also e.g. http://lists.lm-sensors.org/pipermail/lm- sensors/2012-May/036187.html and http://lists.lm-sensors.org/pipermail/lm- sensors/2012-June/036285.html -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8.0-rc3-wrar-1+ (SMP w/4 CPU cores; PREEMPT) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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/20130128013725.8159.77153.report...@belkar.wrar.name
Bug#697035: installer: kb and mouse don't work on a decTop (NSC geode processor)
Ben Hutchings b...@decadent.org.uk (07/01/2013): As I suspected - this wants the special hid-ezkey driver, and we are not including this in the installer. I'll add that and check for other special HID keyboard/mouse drivers at the same time. Thanks, Ben. For those following at home (like I do :p), it's been reassigned to the linux kernel and marked pending. Probably getting fixed in rc2. Mraw, KiBi. signature.asc Description: Digital signature
Processed: Re: Bug#699138: general: Tor, opera, chrom(ium), others lock up gnome on Acer 722. Can not access other CLI terminals.
Processing control commands: reassign -1 src:linux 3.2.35-2 Bug #699138 [general] general: Tor, opera, chrom(ium), others lock up gnome on Acer 722. Can not access other CLI terminals. Bug reassigned from package 'general' to 'src:linux'. Ignoring request to alter found versions of bug #699138 to the same values previously set Ignoring request to alter fixed versions of bug #699138 to the same values previously set Bug #699138 [src:linux] general: Tor, opera, chrom(ium), others lock up gnome on Acer 722. Can not access other CLI terminals. Marked as found in versions linux/3.2.35-2. -- 699138: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699138 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.b699138.135934619022128.transcr...@bugs.debian.org
Processed: reassign 699140 to src:linux, found 699140 in 3.7.3-1~experimental.1, tagging 699140
Processing commands for cont...@bugs.debian.org: reassign 699140 src:linux 3.2.35-2 Bug #699140 [src:linux-2.6] Linux as of 3.8-rc5 doesn't support NCT6779D hw sensor Bug reassigned from package 'src:linux-2.6' to 'src:linux'. Ignoring request to alter found versions of bug #699140 to the same values previously set Ignoring request to alter fixed versions of bug #699140 to the same values previously set Bug #699140 [src:linux] Linux as of 3.8-rc5 doesn't support NCT6779D hw sensor Marked as found in versions linux/3.2.35-2. found 699140 3.7.3-1~experimental.1 Bug #699140 [src:linux] Linux as of 3.8-rc5 doesn't support NCT6779D hw sensor Marked as found in versions linux/3.7.3-1~experimental.1. # Author doesn't seem to think this is quite ready yet tags 699140 - patch Bug #699140 [src:linux] Linux as of 3.8-rc5 doesn't support NCT6779D hw sensor Removed tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 699140: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699140 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.135934671926215.transcr...@bugs.debian.org
Processed: tagging 693997
Processing commands for cont...@bugs.debian.org: tags 693997 + pending Bug #693997 [src:linux] drivers/rtc/rtc-s35390a.c: add wakealarm support for rtc-s35390A rtc chip Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 693997: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693997 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.135934732830028.transcr...@bugs.debian.org
Processed: Re: kernel swap after upgrade to 3.2.23-1~bpo60+2
Processing control commands: tag -1 moreinfo Bug #698829 [src:linux] kernel swap after upgrade to 3.2.23-1~bpo60+2 Added tag(s) moreinfo. -- 698829: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698829 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.b698829.13593481765027.transcr...@bugs.debian.org
Bug#698829: kernel swap after upgrade to 3.2.23-1~bpo60+2
Control: tag -1 moreinfo On Thu, 2013-01-24 at 09:11 +0100, Daniele Melosi wrote: Package: linux-image-3.2.0-0.bpo.3-amd64 Version: 3.2.23-1~bpo60+2 This is quite a few months out of date and there have been many bug fixes since then. Please upgrade to linux-image-3.2.0-0.bpo.4-amd64 version 3.2.35-2~bpo60+1 and report whether the bug remains. In a linux web server (a LAMP architecture) after upgrade the kernel version to the backport one, the system start swapping after a week of utilization. In /proc/slapinfo the main difference is in size-192: after reboot: size-1923363 3980192 201 : tunables 120 60 8 : slabdata199199209 after 2 weeks: size-192 39806000 39806000192 201 : tunables 120 608 : slabdata 1990300 1990300131 A fairly clear memory leak, but sadly it's not obvious what is leaking. Please send the output of: - lsmod - lspci - dmesg I'm using debian 6.0.2 with backported kernel (3.2.23-1~bpo60+2) and libc6 2.11.3-3. Ben. -- Ben Hutchings If more than one person is responsible for a bug, no one is at fault. signature.asc Description: This is a digitally signed message part
Processed: unmerging 625727, bug 625727 is not forwarded, tagging 625727
Processing commands for cont...@bugs.debian.org: # This is a diferent model that does not appear to have been quirked yet unmerge 625727 Bug #625727 [linux-2.6] linux-image-2.6.38-2-amd64: Console turns black during boot, backlight turns off Bug #627372 [linux-2.6] linux-image-2.6.38-2-686: Console turns black during boot Disconnected #625727 from all other report(s). notforwarded 625727 Bug #625727 [linux-2.6] linux-image-2.6.38-2-amd64: Console turns black during boot, backlight turns off Unset Bug forwarded-to-address tags 625727 - patch fixed-upstream Bug #625727 [linux-2.6] linux-image-2.6.38-2-amd64: Console turns black during boot, backlight turns off Removed tag(s) fixed-upstream. thanks Stopping processing here. Please contact me if you need assistance. -- 625727: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625727 627372: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627372 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.135935022619044.transcr...@bugs.debian.org
Processed: tagging 627372
Processing commands for cont...@bugs.debian.org: tags 627372 + pending Bug #627372 [linux-2.6] linux-image-2.6.38-2-686: Console turns black during boot Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 627372: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627372 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.135935028719785.transcr...@bugs.debian.org
Processed: tagging 627372
Processing commands for cont...@bugs.debian.org: tags 627372 + pending Bug #627372 [linux-2.6] linux-image-2.6.38-2-686: Console turns black during boot Ignoring request to alter tags of bug #627372 to the same tags previously set thanks Stopping processing here. Please contact me if you need assistance. -- 627372: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627372 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.135935051521141.transcr...@bugs.debian.org
Processed: tagging 680737
Processing commands for cont...@bugs.debian.org: tags 680737 + pending Bug #680737 [src:linux] linux-image-3.2.0-2-amd64: Intel i915: black display after boot Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 680737: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680737 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.135935051921169.transcr...@bugs.debian.org
Bug#695182: [PATCH] Subtract min_free_kbytes from dirtyable memory
On Fri, Jan 25, 2013 at 08:53:24PM +1100, paul.sz...@sydney.edu.au wrote: Dear Minchan, So what's the effect for user? ... It seems you saw old kernel. ... Current kernel includes ... So I think we don't need this patch. As I understand now, my patch is right and needed for older kernels; for newer kernels, the issue has been fixed in equivalent ways; it was an oversight that the change was not backported; and any justification you need, you can get from those later better patches. I don't know your problem because you didn't write down your problem in changelog. Anyway, If you want to apply it into older kernel, please read Documentation/stable_kernel_rules.txt. In summary, 1. Define your problem. 2. Apply your fix to see the problem goes away in older kernel. 3. If so, write the problem and effect in changelog 4. Send it to stable maintainers and mm maintainer That's all. I asked: A question: what is the use or significance of vm_highmem_is_dirtyable? It seems odd that it would be used in setting limits or threshholds, but not used in decisions where to put dirty things. Is that so, is that as should be? What is the recommended setting of highmem_is_dirtyable? The silence is deafening. I guess highmem_is_dirtyable is an aberration. I hope this helps you find primary reason of your problem. git show 195cf453 Thanks, Paul Paul Szabo p...@maths.usyd.edu.au http://www.maths.usyd.edu.au/u/psz/ School of Mathematics and Statistics University of SydneyAustralia -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majord...@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: a href=mailto:d...@kvack.org; em...@kvack.org /a -- Kind regards, Minchan Kim -- 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/20130128062316.GI3321@blaptop
