Bug#650081: ACPI wakeup doesn't work on ASUS P8H67-M EVO
Hi, On 17/01/12 20:40, Jonathan Nieder wrote: Eric Lavarde wrote: Could it be that the BIOS overwrites my command line entry at shutdown time, but not at suspend time? Sure, I can believe that. It's also possible that when you try to enter S5, something goes wrong and the machine ends up powering off completely and then the BIOS writes to the RTC at bootup. Here's an experiment to try: echo shutdown>/sys/power/disk echo disk>/sys/power/state It performs a suspend-to-disk but enters S5 instead of S4. Bingo! The PC doesn't come back up after this, so it's a difference between S4 and S5. Stupid question: do you know if it would be possible to shutdown (going through init and all this) into S4? After that: maybe RTC or ACPI folks can help (see the MAINTAINERS file[1], and please cc me or this bug log if contacting them so we can track it). But I'd be more inclined to work on getting Will do. Thanks a lot for your help so far! suspend-to-disk working without unloading the media capture driver first. I will also follow-up on this, fine with me, but I'm more a friend of clean shutdowns :-) so it'll be either as fallback strategy or for the community. Cheers, Eric [1] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=blob_plain;f=MAINTAINERS -- 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/4f17cd11.7010...@zorglub.s.bawue.de
linux-2.6_3.2.1-1_multi.changes ACCEPTED into unstable
Accepted: linux-2.6_3.2.1-1.diff.gz to main/l/linux-2.6/linux-2.6_3.2.1-1.diff.gz linux-2.6_3.2.1-1.dsc to main/l/linux-2.6/linux-2.6_3.2.1-1.dsc linux-2.6_3.2.1.orig.tar.gz to main/l/linux-2.6/linux-2.6_3.2.1.orig.tar.gz linux-doc-3.2_3.2.1-1_all.deb to main/l/linux-2.6/linux-doc-3.2_3.2.1-1_all.deb linux-manual-3.2_3.2.1-1_all.deb to main/l/linux-2.6/linux-manual-3.2_3.2.1-1_all.deb linux-patch-debian-3.2_3.2.1-1_all.deb to main/l/linux-2.6/linux-patch-debian-3.2_3.2.1-1_all.deb linux-source-3.2_3.2.1-1_all.deb to main/l/linux-2.6/linux-source-3.2_3.2.1-1_all.deb linux-support-3.2.0-1_3.2.1-1_all.deb to main/l/linux-2.6/linux-support-3.2.0-1_3.2.1-1_all.deb Override entries for your package: linux-2.6_3.2.1-1.dsc - source devel linux-doc-3.2_3.2.1-1_all.deb - optional doc linux-manual-3.2_3.2.1-1_all.deb - optional doc linux-patch-debian-3.2_3.2.1-1_all.deb - optional kernel linux-source-3.2_3.2.1-1_all.deb - optional kernel linux-support-3.2.0-1_3.2.1-1_all.deb - optional devel Announcing to debian-devel-chan...@lists.debian.org Closing bugs: 618422 647825 648207 653776 654800 655344 656328 Thank you for your contribution to Debian. -- 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/e1rnmk8-0002do...@franck.debian.org
linux-latest_42_multi.changes ACCEPTED into unstable
Accepted: linux-doc-2.6_3.2+42_all.deb to main/l/linux-latest/linux-doc-2.6_3.2+42_all.deb linux-doc_3.2+42_all.deb to main/l/linux-latest/linux-doc_3.2+42_all.deb linux-headers-2.6-486_3.2+42_i386.deb to main/l/linux-latest/linux-headers-2.6-486_3.2+42_i386.deb linux-headers-2.6-686-pae_3.2+42_i386.deb to main/l/linux-latest/linux-headers-2.6-686-pae_3.2+42_i386.deb linux-headers-2.6-amd64_3.2+42_i386.deb to main/l/linux-latest/linux-headers-2.6-amd64_3.2+42_i386.deb linux-headers-486_3.2+42_i386.deb to main/l/linux-latest/linux-headers-486_3.2+42_i386.deb linux-headers-686-pae_3.2+42_i386.deb to main/l/linux-latest/linux-headers-686-pae_3.2+42_i386.deb linux-headers-amd64_3.2+42_i386.deb to main/l/linux-latest/linux-headers-amd64_3.2+42_i386.deb linux-image-2.6-486_3.2+42_i386.deb to main/l/linux-latest/linux-image-2.6-486_3.2+42_i386.deb linux-image-2.6-686-bigmem_3.2+42_i386.deb to main/l/linux-latest/linux-image-2.6-686-bigmem_3.2+42_i386.deb linux-image-2.6-686-pae_3.2+42_i386.deb to main/l/linux-latest/linux-image-2.6-686-pae_3.2+42_i386.deb linux-image-2.6-686_3.2+42_i386.deb to main/l/linux-latest/linux-image-2.6-686_3.2+42_i386.deb linux-image-2.6-amd64_3.2+42_i386.deb to main/l/linux-latest/linux-image-2.6-amd64_3.2+42_i386.deb linux-image-486_3.2+42_i386.deb to main/l/linux-latest/linux-image-486_3.2+42_i386.deb linux-image-686-bigmem_3.2+42_i386.deb to main/l/linux-latest/linux-image-686-bigmem_3.2+42_i386.deb linux-image-686-pae_3.2+42_i386.deb to main/l/linux-latest/linux-image-686-pae_3.2+42_i386.deb linux-image-686_3.2+42_i386.deb to main/l/linux-latest/linux-image-686_3.2+42_i386.deb linux-image-amd64_3.2+42_i386.deb to main/l/linux-latest/linux-image-amd64_3.2+42_i386.deb linux-latest_42.dsc to main/l/linux-latest/linux-latest_42.dsc linux-latest_42.tar.gz to main/l/linux-latest/linux-latest_42.tar.gz linux-source-2.6_3.2+42_all.deb to main/l/linux-latest/linux-source-2.6_3.2+42_all.deb linux-source_3.2+42_all.deb to main/l/linux-latest/linux-source_3.2+42_all.deb linux-tools-2.6_3.2+42_all.deb to main/l/linux-latest/linux-tools-2.6_3.2+42_all.deb linux-tools_3.2+42_all.deb to main/l/linux-latest/linux-tools_3.2+42_all.deb xen-linux-system-2.6-xen-686_3.2+42_i386.deb to main/l/linux-latest/xen-linux-system-2.6-xen-686_3.2+42_i386.deb xen-linux-system-686-pae_3.2+42_i386.deb to main/l/linux-latest/xen-linux-system-686-pae_3.2+42_i386.deb xen-linux-system-amd64_3.2+42_i386.deb to main/l/linux-latest/xen-linux-system-amd64_3.2+42_i386.deb Override entries for your package: linux-doc-2.6_3.2+42_all.deb - optional kernel linux-doc_3.2+42_all.deb - optional kernel linux-headers-2.6-486_3.2+42_i386.deb - optional kernel linux-headers-2.6-686-pae_3.2+42_i386.deb - optional kernel linux-headers-2.6-amd64_3.2+42_i386.deb - optional kernel linux-headers-486_3.2+42_i386.deb - optional kernel linux-headers-686-pae_3.2+42_i386.deb - optional kernel linux-headers-amd64_3.2+42_i386.deb - optional kernel linux-image-2.6-486_3.2+42_i386.deb - optional kernel linux-image-2.6-686-bigmem_3.2+42_i386.deb - optional kernel linux-image-2.6-686-pae_3.2+42_i386.deb - optional kernel linux-image-2.6-686_3.2+42_i386.deb - optional kernel linux-image-2.6-amd64_3.2+42_i386.deb - optional kernel linux-image-486_3.2+42_i386.deb - optional kernel linux-image-686-bigmem_3.2+42_i386.deb - optional kernel linux-image-686-pae_3.2+42_i386.deb - optional kernel linux-image-686_3.2+42_i386.deb - optional kernel linux-image-amd64_3.2+42_i386.deb - optional kernel linux-latest_42.dsc - source kernel linux-source-2.6_3.2+42_all.deb - optional kernel linux-source_3.2+42_all.deb - optional kernel linux-tools-2.6_3.2+42_all.deb - optional kernel linux-tools_3.2+42_all.deb - optional kernel xen-linux-system-2.6-xen-686_3.2+42_i386.deb - optional kernel xen-linux-system-686-pae_3.2+42_i386.deb - optional kernel xen-linux-system-amd64_3.2+42_i386.deb - optional kernel Announcing to debian-devel-chan...@lists.debian.org Closing bugs: 635895 651123 652431 655687 Thank you for your contribution to Debian. -- 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/e1rnmkb-00031j...@franck.debian.org
Bug#656433: linux-image-3.1.0-1-amd64: Thinkpad X220 fails to wake up after hibernate-ram with kernel >3.1.5
Package: linux-2.6 Version: 3.1.5-1 Severity: important Dear Maintainer, * What led up to the situation? I upgraded from linux-image-3.1.0-1-amd64__3.1.5-1_amd64 to linux- image-3.1.0-1-amd64_3.1.6-1_amd64 (tried linux- image-3.1.0-1-amd64_3.1.8-1_amd64 and self compiled 3.2.1 from kernel.org as well) * What exactly did you do (or not do) that was effective (or ineffective)? I suspended my system with hibernate-ram. Opening the notebook later did not return me to my session (as desired). Instead after ~1 second I see the power LED turning off and hear the harddrive spin down. ~1 further second later, all LED light up (like they do if I turn the system on), the harddrive spins up shortly until everything shuts down again. Seems like the system is in a loop of turning on and off again every 2 seconds. The only way I found to exit this loop was removing the power supply and the battery (power button did not help). After downgrading to 3.1.5 the system wakes up as it should. -- Package-specific info: ** Version: Linux version 3.1.0-1-amd64 (Debian 3.1.5-1) (b...@decadent.org.uk) (gcc version 4.6.2 (Debian 4.6.2-7) ) #1 SMP Sun Dec 11 20:36:41 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.1.0-1-amd64 root=UUID=ebc375e1-477a-47ad-9cf9-eac4af133429 ro quiet ** Tainted: PO (4097) * Proprietary module has been loaded. * Out-of-tree module has been loaded. ** Kernel log: [4.269061] Registered led device: tpacpi::thinklight [4.269107] Registered led device: tpacpi::power [4.269130] Registered led device: tpacpi::standby [4.269155] Registered led device: tpacpi::thinkvantage [4.269251] thinkpad_acpi: Standard ACPI backlight interface available, not loading native one [4.269340] thinkpad_acpi: Console audio control enabled, mode: monitor (read only) [4.270665] input: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input6 [4.292429] iwlagn :03:00.0: loaded firmware version 17.168.5.3 build 42301 [4.292932] Registered led device: phy0-led [4.302262] Linux media interface: v0.10 [4.303959] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs' [4.305015] Linux video capture interface: v2.00 [4.306773] uvcvideo: Found UVC 1.00 device Integrated Camera (04f2:b217) [4.308460] input: Integrated Camera as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/input/input7 [4.308589] usbcore: registered new interface driver uvcvideo [4.308592] USB Video Class driver (1.1.1) [5.067992] Synaptics Touchpad, model: 1, fw: 8.0, id: 0x1e2b1, caps: 0xd001a3/0x940300/0x120c00 [5.067999] serio: Synaptics pass-through port at isa0060/serio1/input0 [5.118033] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input8 [5.297619] fbcon: inteldrmfb (fb0) is primary device [5.645907] Console: switching to colour frame buffer device 160x48 [5.648884] fb0: inteldrmfb frame buffer device [5.648885] drm: registered panic notifier [5.651366] acpi device:01: registered as cooling_device4 [5.651494] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input9 [5.651557] ACPI: Video Device [VID] (multi-head: yes rom: no post: no) [5.651626] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 [5.651674] snd_hda_intel :00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22 [5.651732] snd_hda_intel :00:1b.0: irq 46 for MSI/MSI-X [5.651762] snd_hda_intel :00:1b.0: setting latency timer to 64 [6.189378] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/input/input10 [6.192024] HDMI status: Codec=3 Pin=5 Presence_Detect=0 ELD_Valid=0 [6.192359] HDMI status: Codec=3 Pin=6 Presence_Detect=0 ELD_Valid=0 [6.192693] HDMI status: Codec=3 Pin=7 Presence_Detect=0 ELD_Valid=0 [6.195093] input: HDA Intel PCH HDMI/DP as /devices/pci:00/:00:1b.0/sound/card0/input11 [6.195158] input: HDA Intel PCH HDMI/DP as /devices/pci:00/:00:1b.0/sound/card0/input12 [6.195217] input: HDA Intel PCH HDMI/DP as /devices/pci:00/:00:1b.0/sound/card0/input13 [6.413647] EXT4-fs (sdb1): re-mounted. Opts: (null) [6.652564] EXT4-fs (sdb1): re-mounted. Opts: errors=remount-ro [6.669736] loop: module loaded [8.007313] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null) [8.069386] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [8.157080] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null) [8.838604] RPC: Registered named UNIX socket transport module. [8.838606] RPC: Registered udp transport module. [8.838608] RPC: Registered tcp transport module. [8.838609] RPC: Registered tcp NFSv4.1 backchannel transport module. [8.845684] FS-Cache: Loaded [8.856781] FS-Cache: Netfs 'nfs' registered for caching [8.862096] Installing knfsd (copyright (C) 1996 o...@mon
Bug#656433: [3.1.5 -> 3.1.6 regression] Thinkpad X220 fails to wake up after hibernate-ram
Hi, Paul Seyfert wrote: > I suspended my system with hibernate-ram. Opening the notebook later did not > return me to my session (as desired). Instead after ~1 second I see the power > LED turning off and hear the harddrive spin down. ~1 further second later, all > LED light up (like they do if I turn the system on), the harddrive spins up > shortly until everything shuts down again. Seems like the system is in a loop > of turning on and off again every 2 seconds. > > The only way I found to exit this loop was removing the power supply and the > battery (power button did not help). > After downgrading to 3.1.5 the system wakes up as it should. Can you bisect? It works like this: 0. Install relevant tools: apt-get install git build-essential 1. Grab the stable kernel. git clone -o stable \ git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git \ linux If you already have a clone of Linus's tree, just add the relevant branches to it instead. cd linux git remote add -f stable \ git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git 2. Make sure you can reproduce the bug with v3.1.6. git checkout v3.1.6 cp /boot/config-$(uname -r) .config; # current configuration make localmodconfig; # optional, minimize configuration make deb-pkg; # add -j to speed up by using multiple CPUs dpkg -i ../; reboot; test test test 3. Make sure you can reproduce the lack of bug with v3.1.5. git checkout v3.1.5 make silentoldconfig; # reuse configuration make deb-pkg; # optionally with -j dpkg -i ../; reboot; test test test 4. If v3.1.6 reproduced the problem and v3.1.5 did not, record that: git bisect start git bisect good v3.1.5 git bisect bad v3.1.6 Git checks out a revision halfway between to test. make silentoldconfig; # reuse configuration make deb-pkg dpkg -i ../; reboot; test test test cd ~/src/linux git bisect bad; # if it reproduces the problem git bisect good; # if suspend-to-ram works fine git bisect skip; # if some other problem makes it hard to test 5. Git checks out a revision halfway between to test. Rinse and repeat until it finds the "first bad commit" or until bored. At any step you can run "git bisect visualize" if the gitk package is installed to see the regression range narrowing. Even a few rounds can be very helpful in narrowing down which patch introduced the bug; one way to report partial results is to send "git bisect log" output. I'd also be interested in full "dmesg" output from booting an affected kernel and booting and suspending an unaffected one. By the way, is this reproducible without the virtualbox driver? Thanks for reporting. Sincerely, Jonathan -- 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/20120119105207.GB15386@burratino
Bug#630593: "Leopold Palomo-Avellaneda"
Hi, Accroding to http://lkml.indiana.edu/hypermail/linux/kernel/9901.2/1285.html, this bug could be solved more efficiently by directly probing the configuration regsiter to determine EPP state. Could you send the superio chips reference ? Bastien -- 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/cae2spay8cfcvgn6zpqwwvszzyvxkhrwsdtnkutkroghczaj...@mail.gmail.com
Bug#520622: Wifi does not work (AR242x)
Quoting "Jonathan Nieder" : Hmm, do you have the "crda" package installed these days? If we're lucky, removing it might render the bug reproducible again. This package is not installed, and probably never was. -- 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/20120119160036.20831ag7pljpe...@webmail.in-berlin.de
Bug#644174: Hook up with hot singles in your town.
Hook up with hot singles in your town. http://sfxy.me/a - If you would like to not be contacted from us in the future please press on the link below: http://sfxy.me/b or write to: P.O. Box 83, 25th St., Vancouver, Canada -- 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/20120119104121.26...@web002.nyc1.bluetie.com
Processed: [bts-link] source package linux-2.6
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package linux-2.6 > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). > # remote status report for #655385 (http://bugs.debian.org/655385) > # Bug title: linux-image-2.6.32-5-openvz-amd64: "Cannot allocate memory" when > doing "cat /proc/self/mountinfo" inside a vm > # * http://bugzilla.openvz.org/show_bug.cgi?id=2142 > # * remote status changed: (?) -> NEW > usertags 655385 + status-NEW Bug#655385: linux-image-2.6.32-5-openvz-amd64: "Cannot allocate memory" when doing "cat /proc/self/mountinfo" inside a vm There were no usertags set. Usertags are now: status-NEW. > # remote status report for #591622 (http://bugs.debian.org/591622) > # Bug title: linux-image-2.6.32-5-amd64: boot failure with acpi enabled > # * http://bugzilla.kernel.org/show_bug.cgi?id=18772 > # * remote status changed: NEEDINFO -> CLOSED > # * remote resolution changed: (?) -> INSUFFICIENT-DATA > # * closed upstream > tags 591622 + fixed-upstream Bug #591622 [linux-2.6] linux-image-2.6.32-5-amd64: boot failure with acpi enabled Added tag(s) fixed-upstream. > usertags 591622 - status-NEEDINFO Bug#591622: linux-image-2.6.32-5-amd64: boot failure with acpi enabled Usertags were: status-NEEDINFO. Usertags are now: . > usertags 591622 + status-CLOSED resolution-INSUFFICIENT-DATA Bug#591622: linux-image-2.6.32-5-amd64: boot failure with acpi enabled There were no usertags set. Usertags are now: resolution-INSUFFICIENT-DATA status-CLOSED. > # remote status report for #623514 (http://bugs.debian.org/623514) > # Bug title: pm-utils: fails to hibernate on Lenovo T500 > # * http://bugzilla.kernel.org/show_bug.cgi?id=41792 > # * remote status changed: NEW -> NEEDINFO > usertags 623514 - status-NEW Bug#623514: pm-utils: fails to hibernate on Lenovo T500 Usertags were: status-NEW. Usertags are now: . > usertags 623514 + status-NEEDINFO Bug#623514: pm-utils: fails to hibernate on Lenovo T500 There were no usertags set. Usertags are now: status-NEEDINFO. > # remote status report for #631597 (http://bugs.debian.org/631597) > # Bug title: linux-image-2.6.39-2-686-pae: Kernel fails to boot after reboot > # * http://bugzilla.kernel.org/show_bug.cgi?id=38262 > # * remote status changed: NEW -> NEEDINFO > usertags 631597 - status-NEW Bug#631597: linux-image-2.6.39-2-686-pae: Kernel fails to boot after reboot Usertags were: status-NEW. Usertags are now: . > usertags 631597 + status-NEEDINFO Bug#631597: linux-image-2.6.39-2-686-pae: Kernel fails to boot after reboot There were no usertags set. Usertags are now: status-NEEDINFO. > # remote status report for #631597 (http://bugs.debian.org/631597) > # Bug title: linux-image-2.6.39-2-686-pae: Kernel fails to boot after reboot > # * http://bugzilla.kernel.org/show_bug.cgi?id=38262 > # * remote status changed: NEW -> NEEDINFO > usertags 631597 - status-NEW Bug#631597: linux-image-2.6.39-2-686-pae: Kernel fails to boot after reboot Usertags were: status-NEEDINFO. Usertags are now: status-NEEDINFO. > usertags 631597 + status-NEEDINFO Bug#631597: linux-image-2.6.39-2-686-pae: Kernel fails to boot after reboot Usertags were: status-NEEDINFO. Usertags are now: status-NEEDINFO. > # remote status report for #631597 (http://bugs.debian.org/631597) > # Bug title: linux-image-2.6.39-2-686-pae: Kernel fails to boot after reboot > # * http://bugzilla.kernel.org/show_bug.cgi?id=38262 > # * remote status changed: NEW -> NEEDINFO > usertags 631597 - status-NEW Bug#631597: linux-image-2.6.39-2-686-pae: Kernel fails to boot after reboot Usertags were: status-NEEDINFO. Usertags are now: status-NEEDINFO. > usertags 631597 + status-NEEDINFO Bug#631597: linux-image-2.6.39-2-686-pae: Kernel fails to boot after reboot Usertags were: status-NEEDINFO. Usertags are now: status-NEEDINFO. > # remote status report for #649304 (http://bugs.debian.org/649304) > # Bug title: linux-image-3.1.0-1-686-pae: needed for > 686-pae kernels > # * http://bugzilla.kernel.org/show_bug.cgi?id=38262 > # * remote status changed: NEW -> NEEDINFO > usertags 649304 - status-NEW Bug#649304: linux-image-3.1.0-1-686-pae: needed for 686-pae kernels Usertags were: status-NEW. Usertags are now: . > usertags 649304 + status-NEEDINFO Bug#649304: linux-image-3.1.0-1-686-pae: needed for 686-pae kernels There were no usertags set. Usertags are now: status-NEEDINFO. > # remote status report for #641396 (http://bugs.debian.org/641396) > # Bug title: linux-image-686: sandforce ssd freezes after sleeping > # * http://bugzilla.kernel.org/show_bug.cgi?id=41022 > # * remote status changed: NEW -> NEEDINFO > usertags 641396 - status-NEW Bug#641396: linux-image-686: sandforce ssd freezes after sleeping Usertags were: status-NEW. Usertags are now: . > usertags 641396 + status-NEEDINFO
[bts-link] source package linux-2.6
# # bts-link upstream status pull for source package linux-2.6 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #655385 (http://bugs.debian.org/655385) # Bug title: linux-image-2.6.32-5-openvz-amd64: "Cannot allocate memory" when doing "cat /proc/self/mountinfo" inside a vm # * http://bugzilla.openvz.org/show_bug.cgi?id=2142 # * remote status changed: (?) -> NEW usertags 655385 + status-NEW # remote status report for #591622 (http://bugs.debian.org/591622) # Bug title: linux-image-2.6.32-5-amd64: boot failure with acpi enabled # * http://bugzilla.kernel.org/show_bug.cgi?id=18772 # * remote status changed: NEEDINFO -> CLOSED # * remote resolution changed: (?) -> INSUFFICIENT-DATA # * closed upstream tags 591622 + fixed-upstream usertags 591622 - status-NEEDINFO usertags 591622 + status-CLOSED resolution-INSUFFICIENT-DATA # remote status report for #623514 (http://bugs.debian.org/623514) # Bug title: pm-utils: fails to hibernate on Lenovo T500 # * http://bugzilla.kernel.org/show_bug.cgi?id=41792 # * remote status changed: NEW -> NEEDINFO usertags 623514 - status-NEW usertags 623514 + status-NEEDINFO # remote status report for #631597 (http://bugs.debian.org/631597) # Bug title: linux-image-2.6.39-2-686-pae: Kernel fails to boot after reboot # * http://bugzilla.kernel.org/show_bug.cgi?id=38262 # * remote status changed: NEW -> NEEDINFO usertags 631597 - status-NEW usertags 631597 + status-NEEDINFO # remote status report for #631597 (http://bugs.debian.org/631597) # Bug title: linux-image-2.6.39-2-686-pae: Kernel fails to boot after reboot # * http://bugzilla.kernel.org/show_bug.cgi?id=38262 # * remote status changed: NEW -> NEEDINFO usertags 631597 - status-NEW usertags 631597 + status-NEEDINFO # remote status report for #631597 (http://bugs.debian.org/631597) # Bug title: linux-image-2.6.39-2-686-pae: Kernel fails to boot after reboot # * http://bugzilla.kernel.org/show_bug.cgi?id=38262 # * remote status changed: NEW -> NEEDINFO usertags 631597 - status-NEW usertags 631597 + status-NEEDINFO # remote status report for #649304 (http://bugs.debian.org/649304) # Bug title: linux-image-3.1.0-1-686-pae: needed for 686-pae kernels # * http://bugzilla.kernel.org/show_bug.cgi?id=38262 # * remote status changed: NEW -> NEEDINFO usertags 649304 - status-NEW usertags 649304 + status-NEEDINFO # remote status report for #641396 (http://bugs.debian.org/641396) # Bug title: linux-image-686: sandforce ssd freezes after sleeping # * http://bugzilla.kernel.org/show_bug.cgi?id=41022 # * remote status changed: NEW -> NEEDINFO usertags 641396 - status-NEW usertags 641396 + status-NEEDINFO # remote status report for #649304 (http://bugs.debian.org/649304) # Bug title: linux-image-3.1.0-1-686-pae: needed for 686-pae kernels # * http://bugzilla.kernel.org/show_bug.cgi?id=38262 # * remote status changed: NEW -> NEEDINFO usertags 649304 - status-NEW usertags 649304 + status-NEEDINFO thanks -- 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/20120119163846.31071.98816.btsl...@busoni.debian.org
Bug#520622: Wifi does not work (AR242x)
retitle 520622 [ath5k] (intermittent?) noise floor calibration timeout still present in 2.6.33 # not affecting anyone severity 520622 normal tags 520622 = upstream patch unreproducible quit W. Martin Borgert wrote: > Quoting "Jonathan Nieder" : >> Hmm, do you have the "crda" package installed these days? If we're >> lucky, removing it might render the bug reproducible again. > > This package is not installed, and probably never was. Ok, I'm out of ideas so it's as you said --- if it happens again for either you or someone else, we will be ready, but otherwise we'll probably have to let this be an unsolved mystery. Retitling so heroes of bug reproduction know what to look for. Sorry we didn't figure this out earlier. If no one reports back soon, we can close it. -- 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/20120119181914.GA6344@burratino
Processed: Re: Wifi does not work (AR242x)
Processing commands for cont...@bugs.debian.org: > retitle 520622 [ath5k] (intermittent?) noise floor calibration timeout still > present in 2.6.33 Bug #520622 [linux-2.6] Wifi does not work (AR242x) Changed Bug title to '[ath5k] (intermittent?) noise floor calibration timeout still present in 2.6.33' from 'Wifi does not work (AR242x)' > # not affecting anyone > severity 520622 normal Bug #520622 [linux-2.6] [ath5k] (intermittent?) noise floor calibration timeout still present in 2.6.33 Severity set to 'normal' from 'important' > tags 520622 = upstream patch unreproducible Bug #520622 [linux-2.6] [ath5k] (intermittent?) noise floor calibration timeout still present in 2.6.33 Removed tag(s) moreinfo and fixed-upstream. > quit Stopping processing here. Please contact me if you need assistance. -- 520622: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=520622 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.132699717516889.transcr...@bugs.debian.org
Bug#591622: boot failure with acpi enabled
Hi Ian, Ian Goodacre wrote: >> On Wed, 2010-08-04 at 21:21 +1200, Ian Goodacre wrote: >>> Subject: linux-image-2.6.32-5-amd64: boot failure with acpi enabled [...] > OK - I reported this upstream: > https://bugzilla.kernel.org/show_bug.cgi?id=18772 The main detail learned upstream seems to be that init=/bin/bash avoids trouble, so maybe the responsible component is some module that is not loaded automatically by the initramfs. Doesn't seem to have gone anywhere aside from that, alas. Some questions: - do you still have access to this hardware? - are you still interested in pursuing debugging this, or are you sick of it? - please attach full "dmesg" output from a successful boot with ACPI enabled, if possible. - please attach output from "reportbug --template linux-image-$(uname -r)". - how are you coping these days? Does acpi=off still reliably work around it? If we can find a less invasive workaround, that would also have the side-effect of narrowing down which component is broken. - if you can get it, a log of the failure (if it shows up in /var/log/dmesg* in the next boot, or from a serial console or netconsole) would be very useful - please attach "acpidump" output - what versions have you tested? Was this a regression? Does 3.2.1 from sid still exhibit it? - any other clues or weird symptoms? Sorry for the long silence, and hope that helps, Sincerely, Jonathan -- 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/20120119184807.GA6631@burratino
Processed: CLOSED-INSUFFICIENT DATA != fixed
Processing commands for cont...@bugs.debian.org: > severity 591622 important Bug #591622 [linux-2.6] linux-image-2.6.32-5-amd64: boot failure with acpi enabled Severity set to 'important' from 'normal' > tags 591622 - fixed-upstream Bug #591622 [linux-2.6] linux-image-2.6.32-5-amd64: boot failure with acpi enabled Removed tag(s) fixed-upstream. > End of message, stopping processing here. Please contact me if you need assistance. -- 591622: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=591622 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.132699900728504.transcr...@bugs.debian.org
Bug#656341: KMS not enabled with ATI Radeon HD 6310 (but it works with Ubuntu 11.10)
Hi Jonathan, thanks for the quick reply! On Wed, 18 Jan 2012 13:17:17 -0600 Jonathan Nieder wrote: > Radeon KMS works fine for me. Could you say a little more about the > symptoms? Does the machine boot correctly with Debian kernels? Yes, the machine boots correctly, but it does not change to a high resolution terminal (font), as it does in Ubuntu, and when X starts it is supports neither xv video output (for scaling videos) nor 3D acceleration (glxinfo gives me "OpenGL renderer string: Software Rasterizer"). > > pn firmware-linux-nonfree 0.34 > > Hmm, so the Radeon firmware is not installed? Strange. # aptitude show firmware-linux-nonfree gives: Package: firmware-linux-nonfree New: yes State: installed Automatically installed: no Version: 0.34 > What does "ls -lR > /lib/firmware | grep radeon | head" give? drwxr-xr-x 2 root root 12288 Jan 4 21:43 radeon drwxr-xr-x 2 root root 4096 Jan 11 22:27 radeon /lib/firmware/3.2.0-rc7/radeon: /lib/firmware/radeon: The contents of "/lib/firmware/radeon" are identical to those in Ubuntu. "/lib/firmware/3.2.0-rc7/radeon" contains less files, and does not contain those my hardware should require. > Sorry for the trouble, and hope that helps, > Jonathan I have no idea what I'm doing wrong and I feel like I'm stupid because I don't get it to work. I'm still interested in having it supported, but since I could reduce my trouble with Ubuntu it is not very urgent for me anymore. Regards, Vlado -- 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/20120119201113.13870801@gula.ps42
Bug#656341: KMS not enabled with ATI Radeon HD 6310 (but it works with Ubuntu 11.10)
Vlado Plaga wrote: > Yes, the machine boots correctly, but it does not change to a high > resolution terminal (font), as it does in Ubuntu, and when X starts it > is supports neither xv video output (for scaling videos) nor 3D > acceleration (glxinfo gives me "OpenGL renderer string: Software > Rasterizer"). Ah, ok. Please attach full "dmesg" output from booting. [...] >>> pn firmware-linux-nonfree 0.34 >> >> Hmm, so the Radeon firmware is not installed? > > Strange. > > # aptitude show firmware-linux-nonfree > > gives: > > Package: firmware-linux-nonfree > New: yes > State: installed > Automatically installed: no > Version: 0.34 I guess I'd suggest "apt-get reinstall firmware-linux-nonfree", although since ... [...] > The contents of "/lib/firmware/radeon" are identical to those in > Ubuntu. ... it's not likely to help much. > "/lib/firmware/3.2.0-rc7/radeon" contains less files, and does > not contain those my hardware should require. What package does "dpkg-query -S /lib/firmware/3.2.0-rc7" indicate is responsible for those? Luckily I imagine udev can cope without being too distracted by such things. :) > P.S.: Only from this report I notice that "experimental" was my > preferred source - a mistake, I wanted it to be "unstable". Not related, but you can fix this with echo 'APT::Default-Release "sid";' >/etc/apt/apt.conf.d/80vp-prefers-sid See apt.conf(5) and /usr/share/doc/apt/examples/configure-index.gz for details. Thanks again. Jonathan -- 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/20120119192854.GB6344@burratino
Re: Renaming linux-2.6 source package, keeping bugs
On Wed, Aug 31, 2011 at 02:44:31PM +0100, Ben Hutchings wrote: > On Wed, 2011-08-31 at 14:13 +0100, Colin Watson wrote: > > On Wed, Aug 31, 2011 at 01:39:20PM +0100, Ben Hutchings wrote: > > > Since Linux 3.x is a continuation of the 2.6.x series and not a major > > > change, there was no need to create a new source package for it. > > > However, we should now rename the source package to 'linux'. > > > > > > Currently, most of our bugs are assigned to 'linux-2.6' or > > > 'src:linux-2.6' so that version-tracking works across binary package > > > name changes. But if we rename the source package as well, these bugs > > > will presumably be seen to apply only to versions before the name > > > change, or only after. How can we avoid this? > > > > The good news is that I don't think this should require fundamental > > redesign work in order to work gracefully. The bad news is that I think > > it is going to require some work. [...] > > We might need some work to make pkgreport.cgi?src=linux&dist=stable work > > gracefully. What I think ought to happen is that it should take the > > version record for linux and realise that it is descended from a source > > package called linux-2.6 that's still in stable, and look up the > > appropriate version for that; but I don't recall implementing anything > > that clever and I suspect that this does not yet work. > > > > We'll also need to consider what happens for users of stable who'll > > continue to report bugs and expect reportbug to be able to show them > > listings and so forth. [...] > > Given the number of bugs involved, perhaps we > > need to teach debbugs that "linux-2.6" should be considered as an alias > > for "linux" for the purposes of queries and of input to submit@ and > > control@. > > > > Ben, do you have any constraints on the timeline for this that we should > > know about? > > No rush. But it would be kind of nice to be able to rename the package before the wheezy freeze. > > Don, what do you think about all this? I think it's tractable, but it > > feels like a pretty solid weekend's work to me. Has any work been done on this, or are any BTS changes actually necessary? Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus -- 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/20120119212102.gd12...@decadent.org.uk
Processed: Re: KMS not enabled with ATI Radeon HD 6310 (but it works with Ubuntu 11.10)
Processing commands for cont...@bugs.debian.org: > notfound 656341 3.1.8-2 Bug #656341 [linux-2.6] linux-image-3.1.0-1-amd64: KMS not enabled with ATI Radeon HD 6310 (but it works with Ubuntu 11.10) There is no source info for the package 'linux-2.6' at version '3.1.8-2' with architecture '' Unable to make a source version for version '3.1.8-2' Bug No longer marked as found in versions 3.1.8-2. > quit Stopping processing here. Please contact me if you need assistance. -- 656341: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656341 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.132701097012479.transcr...@bugs.debian.org
Bug#656341: marked as done (linux-image-3.1.0-1-amd64: KMS not enabled with ATI Radeon HD 6310 (but it works with Ubuntu 11.10))
Your message dated Thu, 19 Jan 2012 16:09:02 -0600 with message-id <20120119220902.GA17461@burratino> and subject line Re: KMS not enabled with ATI Radeon HD 6310 (but it works with Ubuntu 11.10) has caused the Debian Bug report #656341, regarding linux-image-3.1.0-1-amd64: KMS not enabled with ATI Radeon HD 6310 (but it works with Ubuntu 11.10) 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.) -- 656341: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656341 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 3.1.8-2 Severity: important Dear Maintainer, this is a relatively new computer and since there are some problems with the first system I tried on it (Ubuntu 11.10, starting in beta) I thought I'd rather use Debian instead. So far I could not get KMS to work in Debian, although I tried different kernels (3.2.0-rc7 too) and even compiling my own kernel with Radeon firmware built-in (which failed to boot, though). Interestingly KMS does work in Ubuntu (kernel 3.0). I'd love to see it work in Debian too! Here are some lines from dmesg when running Ubuntu: [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 3.0.0-14-generic (buildd@allspice) (gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3) ) #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC 2011 (Ub untu 3.0.0-14.23-generic 3.0.9) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-3.0.0-14-generic root=UUID=8c1ac7a0-b122-42f7-b867-11e0f83c8b93 ro [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Centaur CentaurHauls [ ... ] [3.219046] sd 8:0:1:0: [sdb] Attached SCSI disk [3.225583] [drm] Initialized drm 1.1.0 20060810 [3.230478] firewire_ohci :05:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [3.251300] [drm] radeon defaulting to kernel modesetting. [3.251358] [drm] radeon kernel modesetting enabled. [3.251483] radeon :00:01.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 [3.251540] radeon :00:01.0: setting latency timer to 64 [3.254076] [drm] initializing kernel modesetting (PALM 0x1002:0x9802 0x1043:0x84A5). [3.254244] [drm] register mmio base: 0xFEB0 [3.254292] [drm] register mmio size: 262144 [3.254495] ATOM BIOS: AMD [3.254594] radeon :00:01.0: VRAM: 384M 0x - 0x17FF (384M used) [3.254656] radeon :00:01.0: GTT: 512M 0x1800 - 0x37FF [3.254889] [drm] Detected VRAM RAM=384M, BAR=256M [3.254947] [drm] RAM width 32bits DDR [3.257600] [TTM] Zone kernel: Available graphics memory: 1825632 kiB. [3.257660] [TTM] Initializing pool allocator. [3.257750] [drm] radeon: 384M of VRAM memory ready [3.257798] [drm] radeon: 512M of GTT memory ready. [3.257869] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [3.257919] [drm] Driver supports precise vblank timestamp query. [3.258028] radeon :00:01.0: irq 44 for MSI/MSI-X [3.258037] radeon :00:01.0: radeon: using MSI. [3.258132] [drm] radeon: irq initialized. [3.258186] [drm] GART: num cpu pages 131072, num gpu pages 131072 [3.260415] [drm] Loading PALM Microcode [3.268072] usb 4-5: new full speed USB device number 3 using ohci_hcd [3.274787] input: Microsoft Natural® Ergonomic Keyboard 4000 as /devices/pci:00/:00:12.0/usb4/4-4/4-4:1.0/input/input3 [3.275047] microsoft 0003:045E:00DB.0001: input,hidraw0: USB HID v1.11 Keyboard [Microsoft Natural® Ergonomic Keyboard 4000] on usb-:00:12.0-4/input0 [3.283313] radeon :00:01.0: WB enabled [3.290593] input: Microsoft Natural® Ergonomic Keyboard 4000 as /devices/pci:00/:00:12.0/usb4/4-4/4-4:1.1/input/input4 [3.290853] microsoft 0003:045E:00DB.0002: input,hidraw1: USB HID v1.11 Device [Microsoft Natural® Ergonomic Keyboard 4000] on usb-:00:12.0-4/input1 [3.300041] firewire_ohci: Added fw-ohci device :05:02.0, OHCI v1.10, 4 IR + 8 IT contexts, quirks 0x11 [3.300647] [drm] ring test succeeded in 1 usecs [3.300991] [drm] radeon: ib pool ready. [3.301157] [drm] ib test succeeded in 0 usecs Help would be appreciated! Regards, Vlado P.S.: Only from this report I notice that "experimental" was my preferred source - a mistake, I wanted it to be "unstable". But that should not affect KMS in any way, should it? -- Package-specific info: ** Version: Linux version 3.1.0-1-amd64 (Debian 3.1.8-2) (b...@
Bug#656341: KMS not enabled with ATI Radeon HD 6310 (but it works with Ubuntu 11.10)
On Thu, 19 Jan 2012 15:08:42 -0600 Jonathan Nieder wrote: > Please also attach output from > > grep . /etc/modprobe.d/* Oh, that's it! > /etc/modprobe.d/fglrx-driver.conf:# fglrx conflicts with the free > radeon module. /etc/modprobe.d/fglrx-driver.conf:blacklist radeon Yes, the damn proprietary drivers. I should have thought of them, should have thought of "modprobe radeon" (which I tried so often on my PPC with Ati graphics, some years ago)... Anyway: a big thank you for directing me to the source of the problem, Jonathan! Cheers, Vlado P.S.: I'm too tired now to figure out how to close this bug, please do it for me as well (or I can investigate more on Saturday). -- 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/20120119225710.7a48dff2@gula.ps42
Bug#656341: KMS not enabled with ATI Radeon HD 6310 (but it works with Ubuntu 11.10)
Vlado Plaga wrote: > Ok, I'm attaching even two: one is dmesg_debian_3.1_no_drm, from the > official Debian package, where it does not even seem to try loading the > firmware. Hm, what happens if you then "modprobe radeon"? Please also attach output from grep . /etc/modprobe.d/* -- 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/20120119210842.GA16999@burratino
Bug#581438: nfs-common: Permissions issue
tags 581438 = moreinfo security quit Hi John, John Lepikhin wrote: > Some user is the member of group "secure". I created a directory on > NFS share with owner "otheruser", group owner "secure", permissions > 707 (rwx---rwx). > > User can read this directory, but he is not "otheruser" and IS the > member of "secure" group. Ben was not able to reproduce this. Could you provide more details (for example, some demonstration commands with output showing the bug, a reproduction recipe, or logs)? Sorry for the trouble, Jonathan -- 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/20120119224335.GA17887@burratino
Processed: Re: [linux-2.6] Failed to upgrade to version 2.6.32-3-amd64
Processing commands for cont...@bugs.debian.org: > tags 574031 - unreproducible Bug #574031 [linux-2.6] linux-image-2.6.32-3-amd64: Failed to upgrade to version 2.6.32-3-amd64 Removed tag(s) unreproducible. > quit Stopping processing here. Please contact me if you need assistance. -- 574031: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574031 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.132701281326612.transcr...@bugs.debian.org
Processed: Re: nfs-common: Permissions issue
Processing commands for cont...@bugs.debian.org: > tags 581438 = moreinfo security Bug #581438 [linux-2.6] nfs-common: Permissions issue Removed tag(s) unreproducible. > quit Stopping processing here. Please contact me if you need assistance. -- 581438: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581438 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.132701318029473.transcr...@bugs.debian.org
Bug#574031: marked as done (linux-image-2.6.32-3-amd64: Failed to upgrade to version 2.6.32-3-amd64)
Your message dated Thu, 19 Jan 2012 16:39:49 -0600
with message-id <20120119223949.GA17841@burratino>
and subject line Re: [linux-2.6] Failed to upgrade to version 2.6.32-3-amd64
has caused the Debian Bug report #574031,
regarding linux-image-2.6.32-3-amd64: Failed to upgrade to version
2.6.32-3-amd64
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
574031: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574031
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-2.6
Version: 2.6.32-9
Severity: critical
Justification: breaks the whole system
Hi,
as you can see i have not rebooted my machine yet, which is reasonable because
my machine would
be probably left unbootable. During upgrade to kernel version 2.6.32-3, it
failed at generating grub.cfg .
So I decided to check postinst script but i found nothing in there. Then I
uncommented line with
atribute strict as it is mentioned in there to be usefull for debuging and I am
sending log to you.
Hopefully it will help you more than it did to me. :)
-- Package-specific info:
** Kernel log: boot messages should be attached
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages linux-image-2.6.32-3-amd64 depends on:
ii debconf [debconf-2.0]1.5.28 Debian configuration management sy
ii initramfs-tools [linux-initr 0.93.4 tools for generating an initramfs
ii module-init-tools3.12~pre1-1 tools for managing Linux kernel mo
Versions of packages linux-image-2.6.32-3-amd64 recommends:
ii firmware-linux-free 2.6.32-9 Binary firmware for various driver
Versions of packages linux-image-2.6.32-3-amd64 suggests:
pn grub | lilo(no description available)
pn linux-doc-2.6.32 (no description available)
Versions of packages linux-image-2.6.32-3-amd64 is related to:
pn firmware-bnx2 (no description available)
pn firmware-bnx2x (no description available)
pn firmware-ipw2x00 (no description available)
pn firmware-ivtv (no description available)
ii firmware-iwlwifi 0.23 Binary firmware for Intel Wireless
pn firmware-linux (no description available)
pn firmware-linux-nonfree (no description available)
pn firmware-qlogic(no description available)
pn firmware-ralink(no description available)
-- debconf information:
shared/kernel-image/really-run-bootloader: true
linux-image-2.6.32-3-amd64/prerm/removing-running-kernel-2.6.32-3-amd64: true
linux-image-2.6.32-3-amd64/postinst/bootloader-test-error-2.6.32-3-amd64:
linux-image-2.6.32-3-amd64/postinst/missing-firmware-2.6.32-3-amd64:
linux-image-2.6.32-3-amd64/prerm/would-invalidate-boot-loader-2.6.32-3-amd64:
true
linux-image-2.6.32-3-amd64/postinst/depmod-error-initrd-2.6.32-3-amd64: false
linux-image-2.6.32-3-amd64/postinst/bootloader-error-2.6.32-3-amd64:
Log from perl using strict atribute :
root@debian:~# aptitude safe-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Reading task descriptions... Done
The following packages have been kept back:
libmagickcore2-extra{a}
The following partially installed packages will be configured:
linux-image-2.6.32-3-amd64
0 packages upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 0B of archives. After unpacking 0B will be used.
Writing extended state information... Done
Setting up linux-image-2.6.32-3-amd64 (2.6.32-9) ...
Global symbol "$question" requires explicit package name at
/var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 635.
Global symbol "$question" requires explicit package name at
/var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 637.
Global symbol "$question" requires explicit package name at
/var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 638.
Global symbol "$question" requires explicit package name at
/var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 640.
Global symbol "$question" requires explicit package name at
/var/lib/dpkg/info/linux-image-2.6.32-3-amd64.postinst line 641.
Global symbol "$question" r
Processed: found 622231 in 3.2.1-1
Processing commands for cont...@bugs.debian.org: > found 622231 3.2.1-1 Bug #622231 [linux-2.6] xserver-xorg-input-synaptics: synaptics driver not always used There is no source info for the package 'linux-2.6' at version '3.2.1-1' with architecture '' Unable to make a source version for version '3.2.1-1' Bug Marked as found in versions 3.2.1-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 622231: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622231 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.132702895525064.transcr...@bugs.debian.org
Bug#615110: tpm_tis prevents suspend working more than once
On 19/01/12 01:48, Jonathan Nieder wrote: This is probably fixed by stable release 2.6.37.2 which will be included in Debian version 2.6.37-2 in the next day or two. So, was it? ;-) In suspense, Jonathan No. This bug is still present as of 3.2.0 Linux carbon 3.2.0-rc2+ #2 SMP Thu Dec 8 20:28:12 CET 2011 i686 GNU/Linux [ 295.064214] Suspending console(s) (use no_console_suspend to debug) [ 295.124146] legacy_suspend(): pnp_bus_suspend+0x0/0x57 returns 38 [ 295.124154] PM: Device 00:07 failed to suspend: error 38 [ 295.124160] PM: Some devices failed to suspend $ readlink /sys/devices/pnp0/00:07/driver ../../../bus/pnp/drivers/tpm_tis -- 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/4f19112d.4050...@calvaedi.com
Bug#649033: [PATCH] tpm_tis: add delay after aborting command
tags 649033 + upstream patch quit Jonathan Nieder wrote: > commit a927b8131794 > Author: Stefan Berger > Date: Fri Nov 11 12:57:06 2011 -0500 > > tpm_tis: add delay after aborting command Upstream, Jurij wrote: | With this patch I was able to perform 500 tpm_tis.ko module | insert/remove cycles without ever experiencing a hang. Without the | patch it's sufficient to do 5-10 cycles before modprobe hangs on | module insertion for a while. Thus, it looks like it is an | improvement, so please push it upstream. So it looks like this is fixed by v3.3-rc1~105^2^2~13^2~4 (tpm_tis: add delay after aborting command, 2011-11-11). Jurij, what kernel were you testing against? It would be nice to pass this to Greg for inclusion in 3.2.y and perhaps 3.0.y kernels. Do you know if 3.0.y is affected? (If this patch is tested against something close to upstream 3.0.y or 3.2.y, I'll be happy to submit it to stable@). Thanks, Jonathan -- 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/20120120071953.GA9311@burratino
Processed: Re: [PATCH] tpm_tis: add delay after aborting command
Processing commands for cont...@bugs.debian.org: > tags 649033 + upstream patch Bug #649033 [linux-2.6] tpm_tis: hang during initialization (udevd: timeout: killing '/sbin/modprobe -b acpi:SMO1200:PNP0C31:') Added tag(s) upstream and patch. > quit Stopping processing here. Please contact me if you need assistance. -- 649033: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649033 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.132704401618420.transcr...@bugs.debian.org
Bug#615110: tpm_tis prevents suspend working more than once
tags 615110 - moreinfo # extrapolating since there was no 3.2-rc2 package found 615110 linux-2.6/3.1.0-1~experimental.1 # [1] forwarded 615110 http://thread.gmane.org/gmane.linux.kernel/1119143/focus=1119476 quit Hi, John Hughes wrote: > This bug is still present as of 3.2.0 > > Linux carbon 3.2.0-rc2+ #2 SMP Thu Dec 8 20:28:12 CET 2011 i686 GNU/Linux > > [ 295.064214] Suspending console(s) (use no_console_suspend to debug) > [ 295.124146] legacy_suspend(): pnp_bus_suspend+0x0/0x57 returns 38 > [ 295.124154] PM: Device 00:07 failed to suspend: error 38 > [ 295.124160] PM: Some devices failed to suspend > > $ readlink /sys/devices/pnp0/00:07/driver > ../../../bus/pnp/drivers/tpm_tis Thanks. Do you know the commit id of this 3.2-rc2+ kernel? From [1] we learn: | Ok, so this error code means TPM_INVALID_POSTINIT (not a posix code) | and means that this command was received in the wrong sequence relative | to a TPM_Startup command. Well, what's supposed to be happening is this: | | When the machines (S3) suspends then the OS needs to send a | TPM_SaveState() to the TPM. This is done by the Linux driver. Once the | VM resumes, the BIOS is supposed to send a TPM_Startup(ST_STATE) to the TPM. | | Now the fun starts when a BIOS isn't doing that (even though the spec | says it's supposed to), which could very well be the case in your case | (don't know what broken BIOSes are out there... Did it ever work before | with the TPM driver in the kernel ?). I could try to send you a small | tool that you would have to run from user space upon resume so that we | can see that this error goes away. and there's a workaround in the same message you can try. [...] | The failure of the 2nd suspend then likely stems from the TPM not | accepting the TPM_SaveState() anymore since it hasn't seen the | TPM_Startup(ST_STATE) that we expected the BIOS to send. That thread also proposes an approach to fixing this: > - send a command to the TPM upon resume and if it returns with error > code 38 send TPM_Startup(ST_STATE) -> this masks the BIOS problem; log > this case; TPM stays usable; machine will suspend a 2nd time; a > colleague tells me it may not be 'safe' I don't know if anyone tried that. There have been some tpm fixes upstream recently, so results from testing v3.3-rc1 or later would be interesting. Jonathan -- 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/20120120074639.GB2779@burratino
Processed: Re: tpm_tis prevents suspend working more than once
Processing commands for cont...@bugs.debian.org: > tags 615110 - moreinfo Bug #615110 [linux-2.6] linux-image-2.6.37-1-686: tpm_tis prevents suspend working more than once Removed tag(s) moreinfo. > # extrapolating since there was no 3.2-rc2 package > found 615110 linux-2.6/3.1.0-1~experimental.1 Bug #615110 [linux-2.6] linux-image-2.6.37-1-686: tpm_tis prevents suspend working more than once Bug Marked as found in versions linux-2.6/3.1.0-1~experimental.1. > # [1] > forwarded 615110 > http://thread.gmane.org/gmane.linux.kernel/1119143/focus=1119476 Bug #615110 [linux-2.6] linux-image-2.6.37-1-686: tpm_tis prevents suspend working more than once Set Bug forwarded-to-address to 'http://thread.gmane.org/gmane.linux.kernel/1119143/focus=1119476'. > quit Stopping processing here. Please contact me if you need assistance. -- 615110: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=615110 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.132704561930639.transcr...@bugs.debian.org
