Bug#575051: marked as done (page allocation failures with radeon/KMS)
Your message dated Sat, 14 Jan 2012 22:53:09 -0600 with message-id <20120115045309.GC6018@burratino> and subject line Re: page allocation failures with radeon/KMS has caused the Debian Bug report #575051, regarding page allocation failures with radeon/KMS 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.) -- 575051: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=575051 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.32-10 Severity: normal File: /boot/vmlinuz-2.6.32-4-686 Hi, as you can see from the attached dmesg log, I get page allocation failures in compiz with radeon/KMS. If I disable compiz/compositing, I don't see such messages in the kernel log. I get those messsages regularly although I don't have a specific way to trigger them. I think though, that it only happens when the system is under high load/memory pressure. My hardware is a Radeon Mobility 9200 and I use latest Xorg package with xserver-xorg-video-radeon and KMS enabled. Cheers, Michael -- Package-specific info: ** Version: Linux version 2.6.32-4-686 (Debian 2.6.32-10) (m...@debian.org) (gcc version 4.3.4 (Debian 4.3.4-8) ) #1 SMP Wed Mar 17 17:16:41 UTC 2010 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-4-686 root=UUID=60a26179-e292-48e5-ae26-eb0a20ed9f34 ro quiet ** Not tainted ** Kernel log: [8.801015] [drm] Initialized radeon 2.0.0 20080528 for :01:00.0 on minor 0 [9.444048] intel8x0_measure_ac97_clock: measured 55383 usecs (2668 samples) [9.444053] intel8x0: clocking to 48000 [9.445505] Intel ICH Modem :00:1f.6: PCI INT B -> Link[C0C3] -> GSI 10 (level, low) -> IRQ 10 [9.445528] Intel ICH Modem :00:1f.6: setting latency timer to 64 [ 10.077237] Adding 995988k swap on /dev/sda5. Priority:-1 extents:1 across:995988k [ 10.701346] device-mapper: uevent: version 1.0.3 [ 10.702000] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-de...@redhat.com [ 11.625754] EXT4-fs (sda7): mounted filesystem with ordered data mode [ 11.740627] fuse init (API version 7.13) [ 14.812820] vboxdrv: Trying to deactivate the NMI watchdog permanently... [ 14.812825] vboxdrv: Successfully done. [ 14.812827] vboxdrv: Found 1 processor cores. [ 14.813719] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'. [ 14.813722] vboxdrv: Successfully loaded version 3.1.4_OSE (interface 0x0011). [ 17.850690] ttyS2: LSR safety check engaged! [ 17.858042] ttyS0: LSR safety check engaged! [ 18.350007] eth0: link down [ 18.350631] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 19.606257] lib80211_crypt: registered algorithm 'CCMP' [ 19.714536] padlock: VIA PadLock not detected. [ 19.810200] lib80211_crypt: registered algorithm 'TKIP' [ 20.656251] Bluetooth: L2CAP ver 2.14 [ 20.656255] Bluetooth: L2CAP socket layer initialized [ 20.720510] Bluetooth: RFCOMM TTY layer initialized [ 20.720516] Bluetooth: RFCOMM socket layer initialized [ 20.720519] Bluetooth: RFCOMM ver 1.11 [ 20.747471] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 20.747475] Bluetooth: BNEP filters: protocol multicast [ 20.791864] Bridge firewalling registered [ 20.993267] Bluetooth: SCO (Voice Link) ver 0.6 [ 20.993276] Bluetooth: SCO socket layer initialized [ 22.017714] lp0: using parport0 (interrupt-driven). [ 22.089872] ppdev: user-space parallel port driver [ 28.472043] wlan0: no IPv6 routers present [ 352.930248] EXT4-fs (sda8): mounted filesystem with ordered data mode [ 1913.764218] compiz: page allocation failure. order:1, mode:0x50d0 [ 1913.764225] Pid: 1864, comm: compiz Not tainted 2.6.32-4-686 #1 [ 1913.764228] Call Trace: [ 1913.764243] [] ? __alloc_pages_nodemask+0x476/0x4e0 [ 1913.764250] [] ? alloc_slab_page+0x18/0x1b [ 1913.764254] [] ? __slab_alloc+0x13f/0x431 [ 1913.764259] [] ? __kmalloc+0xd1/0x128 [ 1913.764266] [] ? agp_alloc_page_array+0x22/0x3c [ 1913.764270] [] ? __kmalloc+0x11c/0x128 [ 1913.764274] [] ? agp_alloc_page_array+0x22/0x3c [ 1913.764307] [] ? agp_alloc_page_array+0x22/0x3c [ 1913.764311] [] ? agp_generic_alloc_user+0x61/0xc3 [ 1913.764318] [] ? agp_allocate_memory+0x35/0xb3 [ 1913.764333] [] ? ttm_agp_populate+0x18/0x53 [ttm] [ 1913.764341] [] ? ttm_tt_populate+0x4d/0x5b [ttm] [ 1913.764347] [] ? ttm_tt_set_caching+0x1e/0x8a [ttm] [ 1913.764355] [] ? ttm_bo_handle_move_mem+0xec/0x286 [ttm] [ 1913.764362] [] ? ttm_mem_evict_first+0x36c/0x3de [ttm] [ 1913.764373] [] ? psmouse_handle_byte+0x9/0xdf [psmouse] [ 1913.764381] [] ? ttm_bo_mem_space+0x3c6/0x43e [ttm] [ 1913
Bug#575051: page allocation failures with radeon/KMS
On 15.01.2012 02:11, Jonathan Nieder wrote: > Jonathan Nieder wrote: >> Michael Biebl wrote: >>> >>> My hardware is a Radeon Mobility 9200 and I use latest Xorg package with >>> xserver-xorg-video-radeon and KMS enabled. >> >> Sorry for the long silence. Could you test 3.0 or later from sid and >> if it still exhibits the same problem > > Do you still have this hardware? I don't. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#655944: Kernel threads use significant amount of CPU
Hi James, James Tocknell wrote: > At the suggestion of a friend, I looked at the contents of > /sys/firmware/acpi/interrupts/, and noticed that gpe18 was rising at about > 10 a second. [...] > ACPI Error: No handler or method for GPE[18], disabling event A little background: [1] Is this a regression? (I.e., did earlier kernels behave differently?) Please attach full "dmesg" output from booting and "acpidump" output. If you get a chance to try v3.2-rc7 from experimental, that would be interesting, too. Thanks for a pleasant report. Ciao, Jonathan [1] http://mjg59.livejournal.com/117532.html -- 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/20120115043027.GB6018@burratino
Bug#655944: linux-image-3.1.0-1-amd64: Kernel threads use significant amount of CPU
Package: linux-2.6 Version: 3.1.8-2 Severity: normal On my laptop, kernel threads use somewhere between 25% - 80% of one of the CPUs, even on idle. At the suggestion of a friend, I looked at the contents of /sys/firmware/acpi/interrupts/, and noticed that gpe18 was rising at about 10 a second. Searching through the standard logfiles didn't show anything related to gpe18, however looking through the installation logs, I found this line ACPI Error: No handler or method for GPE[18], disabling event (20090903/evgpe-706) which suggested that the issue was with ACPI. Decompiling the dsdt table and then recompiling according to http://en.gentoo- wiki.com/wiki/ACPI/Fix_common_problems in order to try to guess what hardware was the issue, gave me the three following errors: dsdt.dsl 2124: 0x, // Length Error4122 - ^ Invalid combination of Length and Min/Max fixed flags dsdt.dsl 2131: 0x07E0, // Length Error4118 - ^ Length is not equal to fixed Min/Max window dsdt.dsl 2138: 0x0F00, // Length Error4118 - ^ Length is not equal to fixed Min/Max window Is there any other information that would be useful in finding out why the CPU usage is so high? -- Package-specific info: ** Version: Linux version 3.1.0-1-amd64 (Debian 3.1.8-2) (b...@decadent.org.uk) (gcc version 4.6.2 (Debian 4.6.2-11) ) #1 SMP Tue Jan 10 05:01:58 UTC 2012 ** Command line: BOOT_IMAGE=/vmlinuz-3.1.0-1-amd64 root=/dev/mapper/pandora-root ro quiet ** Not tainted ** Kernel log: [5.369898] ATOM BIOS: Lenovo [5.369958] radeon :01:00.0: VRAM: 1024M 0x - 0x3FFF (1024M used) [5.369962] radeon :01:00.0: GTT: 512M 0x4000 - 0x5FFF [5.377902] iwlagn :03:00.0: device EEPROM VER=0x15d, CALIB=0x6 [5.377906] iwlagn :03:00.0: Device SKU: 0X50 [5.377909] iwlagn :03:00.0: Valid Tx ant: 0X1, Valid Rx ant: 0X3 [5.381232] iwlagn :03:00.0: Tunable channels: 13 802.11bg, 0 802.11a channels [5.381236] [drm] Detected VRAM RAM=1024M, BAR=256M [5.381239] [drm] RAM width 128bits DDR [5.381294] [TTM] Zone kernel: Available graphics memory: 4089264 kiB. [5.381296] [TTM] Zone dma32: Available graphics memory: 2097152 kiB. [5.381298] [TTM] Initializing pool allocator. [5.381323] [drm] radeon: 1024M of VRAM memory ready [5.381325] [drm] radeon: 512M of GTT memory ready. [5.381342] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [5.381344] [drm] Driver supports precise vblank timestamp query. [5.381355] iwlagn :03:00.0: RF_KILL bit toggled to disable radio. [5.381434] radeon :01:00.0: irq 44 for MSI/MSI-X [5.381442] radeon :01:00.0: radeon: using MSI. [5.381489] [drm] radeon: irq initialized. [5.381495] [drm] GART: num cpu pages 131072, num gpu pages 131072 [5.382093] [drm] Loading REDWOOD Microcode [5.386113] iwlagn :03:00.0: loaded firmware version 39.31.5.1 build 35138 [5.386225] Registered led device: phy0-led [5.389763] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs' [5.393030] radeon :01:00.0: WB enabled [5.398958] input: Ideapad extra buttons as /devices/platform/ideapad/input/input8 [5.409318] [drm] ring test succeeded in 1 usecs [5.409449] [drm] radeon: ib pool ready. [5.409515] [drm] ib test succeeded in 0 usecs [5.409521] failed to evaluate ATIF got AE_BAD_PARAMETER [5.409913] [drm] Radeon Display Connectors [5.409916] [drm] Connector 0: [5.409918] [drm] LVDS [5.409921] [drm] DDC: 0x6560 0x6560 0x6564 0x6564 0x6568 0x6568 0x656c 0x656c [5.409923] [drm] Encoders: [5.409925] [drm] LCD1: INTERNAL_UNIPHY [5.409927] [drm] Connector 1: [5.409929] [drm] HDMI-A [5.409931] [drm] HPD1 [5.409934] [drm] DDC: 0x6430 0x6430 0x6434 0x6434 0x6438 0x6438 0x643c 0x643c [5.409936] [drm] Encoders: [5.409938] [drm] DFP1: INTERNAL_UNIPHY1 [5.409940] [drm] Connector 2: [5.409942] [drm] VGA [5.409945] [drm] DDC: 0x64d8 0x64d8 0x64dc 0x64dc 0x64e0 0x64e0 0x64e4 0x64e4 [5.409947] [drm] Encoders: [5.409949] [drm] CRT1: INTERNAL_KLDSCP_DAC1 [5.419121] hda_codec: ALC272: BIOS auto-probing. [5.420993] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/input/input9 [5.423385] input: HDA Intel PCH Mic as /devices/pci:00/:00:1b.0/sound/card0/input10 [5.423457] input: HDA Intel PCH Headphone as /devices/pci:00/:00:1b.0/sound/card0/input11 [5.791097] input: PS/2 Generic Mouse as /devices/platform/i8042/serio3/input/input12 [5.890320] [drm] Radeon display connector LVDS-1: No monitor connected or invalid EDID [5.902185] [drm] Radeon display connector HDMI-A-1: No monitor connected or inv
Bug#579005: XFS internal error xfs_da_do_buf(2) at line 2085 of file fs/xfs/xfs_da_btree.c.
On Sat, 2012-01-14 at 13:58 -0600, Jonathan Nieder wrote: > Jonathan Nieder wrote: > > > Interesting. So this might be a case of the kernel not coping well > > with previous filesystem corruption. > > Some reading: [1] > > >From similar symptoms at [2]: > > | This indicates filesystem corruption, which may be caused by a > hardware/media > | fault. > | > | I suggest you run xfs_repair and then xfs_db to dump any inodes that may > have > | problems. > | > | Also check smartctl, dmesg etc for any hardware errors. > | > | This class of fault is typically very hard to track down, the corruption > | (whether caused by software or hardware) may have happened a week ago and > | its only now you have read that part of the filesystem again. > > Apparently one cause of this in olden days was [3] (probably not > what's happening here, since that got fixed a while ago). Another was > running with write cache enabled but without barriers which didn't > work over the device mapper. > > In any case, I think reporting "XFS internal error" rather than > something more enlightening like "magic number is wrong - filesystem > is probably corrupt" is a bug in itself. So it would be nice to > figure out what happened and at least fix this that much. [...] Also, filesystems should generally be considered untrusted data and therefore the possibility for a corrupted filesystem to trigger a crash can be considered a security vulnerability. The XFS developers would probably be interested to know about it even if the corruption itself is due to a hardware fault. Ben. -- Ben Hutchings When in doubt, use brute force. - Ken Thompson signature.asc Description: This is a digitally signed message part
Bug#655941: iwlagn: my wifi card doesn't works - Intel Corporation Centrino Wireless-N 1000 [8086:0084]
Hi On Sunday 15 January 2012, Jonathan Nieder wrote: [...] > apt-get install iw iproute for completeness, you need wpasupplicant as well for the 3rd stanza of /etc/network/interfaces to work (and you want crda (>= wheezy) to access channel 11-13/ most of the 5 GHz band): # apt-get install iw iproute wpasupplicant crda > ip link set wlan0 up > iw dev wlan0 scan > iw dev wlan0 connect -w myfavoriteaccesspoint > cat >>/etc/network/interfaces <<-\EOF > iface library inet dhcp > wireless-essid CPLWIFI > > iface home inet dhcp > wireless-essid Elephant > wireless-key Mouse > > iface cafe inet dhcp Small syntax fix > wpa-driver nl This should read wpa-driver nl80211 the only valid choices here are: - nl80211 all modern mac80211 based drivers. - wext legacy and staging drivers - don't use, unless you have to. it's preferred to just leave out wpa-driver over hardcoding it to wext, because staging drivers will switch to nl80211, once they leave staging. - wired only for encrypted wired ethernet, basically not used in practice. Setting wpa-driver explicitly is no longer necessary since wpasupplicant 0.7.x (>= wheezy), it will default to nl80211 and fall back to wext as needed). However it was needed for wpasupplicant <=0.6.x from squeeze and earlier (well, at least lenny and squeeze). > wpa-ssid Cafe Foo Bar > wpa-psk secretsecretpassword > EOF > ip link set wlan0 down > ifup wlan0=cafe While I have no personal experience with iwlagn/ iwlwifi, it might help to load the module with "11n_disable=1", as there've been a couple of problems with both the firmware and the kernel module in recent times. Regards Stefan Lippers-Hollmann -- 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/201201150410.30984.s@gmx.de
Processed: Re: iwlagn: my wifi card doesn't works - Intel Corporation Centrino Wireless-N 1000 [8086:0084]
Processing commands for cont...@bugs.debian.org: > tags 655941 + moreinfo Bug #655941 [linux-2.6] iwlagn: my wifi card doesn't works - Intel Corporation Centrino Wireless-N 1000 [8086:0084] Added tag(s) moreinfo. > quit Stopping processing here. Please contact me if you need assistance. -- 655941: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655941 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.132659466813158.transcr...@bugs.debian.org
Bug#655941: iwlagn: my wifi card doesn't works - Intel Corporation Centrino Wireless-N 1000 [8086:0084]
tags 655941 + moreinfo quit Hi Andrey, Andrey--k wrote: > ~$ sudo iwlist wlan0 scan > wlan0 Interface doesn't support scanning : Network is down apt-get install iw iproute ip link set wlan0 up iw dev wlan0 scan iw dev wlan0 connect -w myfavoriteaccesspoint cat >>/etc/network/interfaces <<-\EOF iface library inet dhcp wireless-essid CPLWIFI iface home inet dhcp wireless-essid Elephant wireless-key Mouse iface cafe inet dhcp wpa-driver nl wpa-ssid Cafe Foo Bar wpa-psk secretsecretpassword EOF ip link set wlan0 down ifup wlan0=cafe -- 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/20120115023054.GA6018@burratino
Bug#655941: iwlagn: my wifi card doesn't works - Intel Corporation Centrino Wireless-N 1000 [8086:0084]
Package: linux-2.6 Version: 3.1.8-2 Severity: normal File: iwlagn Dear Maintainer, After installing system my wifi-card didn't rise up. Ive tried stable version also. It doesn't works. If Am pressing in menu switch ON wifi - nothing happens. hardware switch is in ON position, software keyboard combination also tested some console tests: ~$ lspci -nn | grep Net 03:00.0 Network controller [0280]: Intel Corporation Centrino Wireless-N 1000 [8086:0084] ~$ sudo iwconfig wlan0 wlan0 IEEE 802.11bgn ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=14 dBm Retry long limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off ~$ sudo iwlist wlan0 scan wlan0 Interface doesn't support scanning : Network is down ~$ sudo ifconfig wlan0 up ~$ sudo iwlist wlan0 scan wlan0 Scan completed : Cell 01 - Address: ouput cuted off, networks were shown - -- Package-specific info: ** Version: Linux version 3.1.0-1-amd64 (Debian 3.1.8-2) (b...@decadent.org.uk) (gcc version 4.6.2 (Debian 4.6.2-11) ) #1 SMP Tue Jan 10 05:01:58 UTC 2012 ** Command line: BOOT_IMAGE=/vmlinuz-3.1.0-1-amd64 root=UUID=5b1926d0-656a-49a9-9d93-91ac2e7bac4b ro quiet ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [ 10.469246] [drm] nouveau :01:00.0: 0: memory 135MHz core 50MHz shader 101MHz voltage 830mV timing 4 [ 10.469250] [drm] nouveau :01:00.0: 1: memory 324MHz core 202MHz shader 405MHz voltage 830mV timing 5 [ 10.469253] [drm] nouveau :01:00.0: 3: memory 900MHz core 672MHz shader 1344MHz voltage 980mV timing 6 [ 10.472100] [TTM] Zone kernel: Available graphics memory: 4056274 kiB. [ 10.472102] [TTM] Zone dma32: Available graphics memory: 2097152 kiB. [ 10.472104] [TTM] Initializing pool allocator. [ 10.472116] [drm] nouveau :01:00.0: Detected 1024MiB VRAM [ 10.475142] [drm] nouveau :01:00.0: 512 MiB GART (aperture) [ 10.480282] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [ 10.480284] [drm] No driver support for vblank timestamp query. [ 10.530078] [drm] nouveau :01:00.0: allocated 1024x768 fb: 0xc, bo 880233a37400 [ 10.550902] Console: switching to colour frame buffer device 128x48 [ 10.553505] fb0: nouveaufb frame buffer device [ 10.553506] drm: registered panic notifier [ 10.553511] [drm] Initialized nouveau 0.0.16 20090420 for :01:00.0 on minor 0 [ 10.553545] snd_hda_intel :01:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17 [ 10.553552] hda_intel: Disabling MSI [ 10.553594] snd_hda_intel :01:00.1: setting latency timer to 64 [ 10.584383] i915 :00:02.0: irq 45 for MSI/MSI-X [ 10.584389] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [ 10.584390] [drm] Driver supports precise vblank timestamp query. [ 10.584450] [drm:intel_dsm_platform_mux_info] *ERROR* MUX INFO call failed [ 10.584524] [drm:intel_dsm_platform_mux_info] *ERROR* MUX INFO call failed [ 10.584584] vgaarb: device changed decodes: PCI::01:00.0,olddecodes=io+mem,decodes=none:owns=none [ 10.584588] vgaarb: device changed decodes: PCI::00:02.0,olddecodes=io+mem,decodes=none:owns=io+mem [ 11.110049] HDMI status: Codec=0 Pin=5 Presence_Detect=0 ELD_Valid=0 [ 11.190488] fbcon: inteldrmfb (fb1) is primary device [ 11.190491] fbcon: Remapping primary device, fb1, to tty 1-63 [ 11.213972] HDMI status: Codec=1 Pin=5 Presence_Detect=0 ELD_Valid=0 [ 11.317855] HDMI status: Codec=2 Pin=5 Presence_Detect=0 ELD_Valid=0 [ 11.421740] HDMI status: Codec=3 Pin=5 Presence_Detect=0 ELD_Valid=0 [ 11.759967] fb1: inteldrmfb frame buffer device [ 11.760199] ACPI Warning: For \_SB_.PCI0.PEG0.PEGP._DOD: Return type mismatch - found Integer, expected Package (20110623/nspredef-1060) [ 11.760205] ACPI Exception: AE_OK, Invalid _DOD data (20110623/video-1153) [ 11.763022] ACPI Error: Current brightness invalid (20110623/video-376) [ 11.763160] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:35/LNXVIDEO:00/input/input12 [ 11.763216] ACPI: Video Device [PEGP] (multi-head: yes rom: yes post: no) [ 11.824845] ACPI Error: Current brightness invalid (20110623/video-376) [ 11.825091] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:01/input/input13 [ 11.825142] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) [ 11.825193] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 1 [ 12.469235] input: HDA NVidia HDMI/DP as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input14 [ 12.469408] input: HDA NVidia HDMI/DP as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input15 [ 12.469579] input: HDA NVidia HDMI/DP as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input16 [ 12.469760] input: HDA NVidia HDMI/DP as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input17 [ 13.00662
Processed: Re: [radeon RS690] resume fails when radeon firmware is not available
Processing commands for cont...@bugs.debian.org: > reassign 655934 src:linux-2.6 3.1.8-2 Bug #655934 [linux-2.6] [radeon RS690] resume fails when radeon firmware is not available Bug reassigned from package 'linux-2.6' to 'src:linux-2.6'. Bug No longer marked as found in versions 3.1.8-2. Bug #655934 [src:linux-2.6] [radeon RS690] resume fails when radeon firmware is not available Bug Marked as found in versions linux-2.6/3.1.8-2. > reassign 607471 src:linux-2.6 2.6.32-29 Bug #607471 [linux-2.6] linux-image-2.6.32-5-686: resume from ram won't work on T42 with radeon driver Bug reassigned from package 'linux-2.6' to 'src:linux-2.6'. Bug No longer marked as found in versions 2.6.32-29. Bug #607471 [src:linux-2.6] linux-image-2.6.32-5-686: resume from ram won't work on T42 with radeon driver Bug Marked as found in versions linux-2.6/2.6.32-29. > reassign 627497 src:linux-2.6 2.6.38-3 Bug #627497 [linux-2.6] linux-headers-2.6.38-bpo.2-amd64: "Unable to handle kernel paging request" with radeon KMS without non-free firmware Bug reassigned from package 'linux-2.6' to 'src:linux-2.6'. Bug No longer marked as found in versions 2.6.38-3~bpo60+1. Bug #627497 [src:linux-2.6] linux-headers-2.6.38-bpo.2-amd64: "Unable to handle kernel paging request" with radeon KMS without non-free firmware Bug Marked as found in versions linux-2.6/2.6.38-3. > reassign 637943 src:linux-2.6 3.0.0-1 Bug #637943 [linux-2.6] RV635 [Radeon HD 3600 series]: white, grey, and black stripes with snow on bottom unless firmware is loaded Bug reassigned from package 'linux-2.6' to 'src:linux-2.6'. Bug No longer marked as found in versions linux-2.6/3.0.0-1. Bug #637943 [src:linux-2.6] RV635 [Radeon HD 3600 series]: white, grey, and black stripes with snow on bottom unless firmware is loaded Bug Marked as found in versions linux-2.6/3.0.0-1. > merge 607194 607471 627497 637943 649448 655934 Bug#607194: radeon: random general protection faults when RV620 firmware not installed Bug#607471: linux-image-2.6.32-5-686: resume from ram won't work on T42 with radeon driver Bug#627497: linux-headers-2.6.38-bpo.2-amd64: "Unable to handle kernel paging request" with radeon KMS without non-free firmware Bug#637943: RV635 [Radeon HD 3600 series]: white, grey, and black stripes with snow on bottom unless firmware is loaded Bug#649448: radeon (evergreen): random-looking pattern of pixels when firmware not installed Bug#655934: [radeon RS690] resume fails when radeon firmware is not available Bug#610851: radeon: memory corruption after modesetting when RV770 microcode not installed Bug#632212: linux-image-2.6.39-2-686-pae: kernel locks up when starting udev, upon graphics mode switch Merged 607194 607471 610851 627497 632212 637943 649448 655934. > quit Stopping processing here. Please contact me if you need assistance. -- 655934: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655934 627497: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627497 632212: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632212 607471: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607471 610851: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=610851 607194: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607194 649448: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649448 637943: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637943 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.1326591441494.transcr...@bugs.debian.org
Bug#655934: [radeon RS690] resume fails when radeon firmware is not available
reassign 655934 src:linux-2.6 3.1.8-2 reassign 607471 src:linux-2.6 2.6.32-29 reassign 627497 src:linux-2.6 2.6.38-3 reassign 637943 src:linux-2.6 3.0.0-1 merge 607194 607471 627497 637943 649448 655934 quit Paul Menzel wrote: > with `firmware-linux-nonfree` installed suspend and resume works just > fine. Thanks for confirming. > Am Sonntag, den 15.01.2012, 01:26 +0100 schrieb Paul Menzel: >> I imagine when booting in recovery mode with radeon.modeset=0 on the >> command line, suspend and resume works fine? >> >> I will try that too. > > … tomorrow. I hope I can leave `firmware-linux-nonfree` installed when > testing that. No, no need to bother. It was just another way to make sure that it is the radeon driver that is having trouble, but you've already demonstrated that by now. Merging with some other "radeon driver broken without firmware" bugs, even though I fully expect them not to all end up being fixed at the same time. As different causes are discovered (some have already but I'm too lazy to act on it :)) and patches written, the relevant reports can be unmerged. Thanks for your help. Cheers, 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/20120115013701.GA2458@burratino
Processed: Re: Another report for X radeon driver
Processing commands for cont...@bugs.debian.org: > forcemerge 601715 602366 Bug#601715: kernel errors after upgrade, X system left in a non-working state (radeon) Bug#602366: xserver-xorg-video-radeon: After last update, X stopped working completely Forcibly Merged 601715 602366. > End of message, stopping processing here. Please contact me if you need assistance. -- 602366: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602366 601715: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=601715 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.132659051128832.transcr...@bugs.debian.org
Processed: Re: page allocation failures with radeon/KMS
Processing commands for cont...@bugs.debian.org: > tags 575051 + moreinfo Bug #575051 [linux-2.6] page allocation failures with radeon/KMS Added tag(s) moreinfo. > quit Stopping processing here. Please contact me if you need assistance. -- 575051: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=575051 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.132658990226827.transcr...@bugs.debian.org
Bug#575051: page allocation failures with radeon/KMS
tags 575051 + moreinfo quit Hi again, Jonathan Nieder wrote: > Michael Biebl wrote: >> as you can see from the attached dmesg log, I get page allocation >> failures in compiz with radeon/KMS. >> >> If I disable compiz/compositing, I don't see such messages in the kernel >> log. I get those messsages regularly although I don't have a specific >> way to trigger them. I think though, that it only happens when the >> system is under high load/memory pressure. >> >> My hardware is a Radeon Mobility 9200 and I use latest Xorg package with >> xserver-xorg-video-radeon and KMS enabled. > > Sorry for the long silence. Could you test 3.0 or later from sid and > if it still exhibits the same problem Do you still have this hardware? -- 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/20120115011125.GA2768@burratino
Processed: Re: drmRadeonCmdBuffer: -12. Kernel failed to parse or rejected command stream
Processing commands for cont...@bugs.debian.org: > tags 551393 + moreinfo Bug #551393 [linux-2.6] drmRadeonCmdBuffer: -12. Kernel failed to parse or rejected command stream Added tag(s) moreinfo. > quit Stopping processing here. Please contact me if you need assistance. -- 551393: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=551393 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.132658971525562.transcr...@bugs.debian.org
Bug#551393: drmRadeonCmdBuffer: -12. Kernel failed to parse or rejected command stream
tags 551393 + moreinfo quit Hi Arthur, Andres Salomon wrote: > Arthur Marsh wrote: >> I attempted to run extremetuxracer on this machine with radeon9200se >> and radeon driver and received the following output: > > How reproducible is this? Does it occur every time you run tuxracer > (even after rebooting), or does it only happen every once in a while? Sorry for the long quiet. Do you still have the affected hardware? If so, does it still reproduce this bug? And if not, do you remember approximately when it was fixed? (/var/log/dpkg.log* might help) Curious, 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/20120115010817.GA2705@burratino
Processed: Re: ASUS M2A-VM (SB600): Resume not working
Processing commands for cont...@bugs.debian.org: > retitle 655934 [radeon RS690] resume fails when radeon firmware is not > available Bug #655934 [linux-2.6] linux-image-3.1.0-1-amd64: ASUS M2A-VM (SB600): Resume not working Changed Bug title to '[radeon RS690] resume fails when radeon firmware is not available' from 'linux-image-3.1.0-1-amd64: ASUS M2A-VM (SB600): Resume not working' > severity 655934 important Bug #655934 [linux-2.6] [radeon RS690] resume fails when radeon firmware is not available Severity set to 'important' from 'normal' > quit Stopping processing here. Please contact me if you need assistance. -- 655934: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655934 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.132658666512284.transcr...@bugs.debian.org
Bug#655934: ASUS M2A-VM (SB600): Resume not working
retitle 655934 [radeon RS690] resume fails when radeon firmware is not available severity 655934 important quit Hi Paul, Paul Menzel wrote: > with my ASUS M2A-VM [1] system suspend and resume does not work. The > system suspends fine but pressing the power button afterward the fans > start turning and the CD drives make noises but the screen does not > receive any signal and the system even cannot be pinged from another > system. Therefore I am left to cold reset(?) the system and even > netconsole does not print anything when resuming the system. > > The strange thing is, using the Debian based live system Grml 2011.12 > [2] suspend and resume works fine. The difference is that Grml loads the > Radeon graphics firmware(?) and I do not have `linux-firmware-nonfree` > installed. Yep, that's believable. I imagine when booting in recovery mode with radeon.modeset=0 on the command line, suspend and resume works fine? Please provide full "dmesg" output from booting up the affected system. 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/20120115001723.GA2192@burratino
Bug#631155: marked as done (ecryptfs-utils: I/O error while updating files through rsync)
Your message dated Sat, 14 Jan 2012 17:13:57 -0600 with message-id <20120114231357.GA1409@burratino> and subject line Re: ecryptfs-utils: I/O error while updating files through rsync has caused the Debian Bug report #631155, regarding ecryptfs-utils: I/O error while updating files through rsync 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.) -- 631155: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631155 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ecryptfs-utils Version: 83-4 Severity: important I wrote a bash script to rsync file from a directory to another - encrypted - one, through ssh. First, add "mount-wide passphrase" with ecryptfs-manager, and mount -i /my-ecryptfs-directory. Then, rsync files. For new files (that means, files that doesn't exist yet in ecryptfs directory), everything goes fine. But for files which should be updated, I get lot of "rsync: failed to open "/my_ecryptfs_dir/my_file", continuing: Input/output error (5)" through error output, in correlation with "Either the lower file is not in a valid eCryptfs format, or the key could not be retrieved. Plaintext passthrough mode is not enabled; returning -EIO" in /var/log/messages. Surprisingly, I get the very same behavior for "new files" with --partial option. I supposed it was related to the "0-length file bug" on ext filesystem, but specifying a "--partial-dir" outside the ecryptfs mount point doesn't help. For files affected by the "I/O error", they appear to be "corrupted" (can't cp, mv, ...) : the only solution is to remove them. -- System Information: Debian Release: 5.0.8 APT prefers oldstable APT policy: (500, 'oldstable'), (200, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-2-amd64 (SMP w/1 CPU core) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages ecryptfs-utils depends on: ii gettext-base0.17-4 GNU Internationalization utilities ii keyutils1.4-1Linux Key Management Utilities ii libc6 2.7-18lenny7 GNU C Library: Shared libraries ii libecryptfs083-4 ecryptfs cryptographic filesystem ii libgpg-error0 1.6-1library for common error values an ii libgpgme11 1.1.6-2 GPGME - GnuPG Made Easy ii libkeyutils11.4-1Linux Key Management Utilities (li ii libnss3-1d 3.12.3.1-0lenny4 Network Security Service libraries ii libpam-runtime 1.1.1-6.1Runtime support for the PAM librar ii libpam0g1.1.1-6.1Pluggable Authentication Modules l ecryptfs-utils recommends no packages. Versions of packages ecryptfs-utils suggests: pn cryptsetup (no description available) pn opencryptoki (no description available) -- no debconf information --- End Message --- --- Begin Message --- Version: 2.6.32-39 Sdkfz262 wrote: > No problem since Lenny to Squeeze update and 2.6.32 kernel > (ecryptfs-utils still in version 83-4). > > Could be considered as fixed. Thanks, Loic. Marking so. --- End Message ---
Bug#631155: ecryptfs-utils: I/O error while updating files through rsync
No problem since Lenny to Squeeze update and 2.6.32 kernel (ecryptfs-utils still in version 83-4). Could be considered as fixed. -- 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/4f120b01.5090...@yahoo.fr
Bug#579005: XFS internal error xfs_da_do_buf(2) at line 2085 of file fs/xfs/xfs_da_btree.c.
Jonathan Nieder wrote: > Interesting. So this might be a case of the kernel not coping well > with previous filesystem corruption. Some reading: [1] >From similar symptoms at [2]: | This indicates filesystem corruption, which may be caused by a hardware/media | fault. | | I suggest you run xfs_repair and then xfs_db to dump any inodes that may have | problems. | | Also check smartctl, dmesg etc for any hardware errors. | | This class of fault is typically very hard to track down, the corruption | (whether caused by software or hardware) may have happened a week ago and | its only now you have read that part of the filesystem again. Apparently one cause of this in olden days was [3] (probably not what's happening here, since that got fixed a while ago). Another was running with write cache enabled but without barriers which didn't work over the device mapper. In any case, I think reporting "XFS internal error" rather than something more enlightening like "magic number is wrong - filesystem is probably corrupt" is a bug in itself. So it would be nice to figure out what happened and at least fix this that much. Hope that helps, Jonathan [1] http://oss.sgi.com/bugzilla/buglist.cgi?field0-0-0=short_desc&type0-0-0=substring&value0-0-0=xfs_da_do_buf&field0-0-1=longdesc&type0-0-1=substring&value0-0-1=xfs_da_do_buf [2] http://oss.sgi.com/bugzilla/show_bug.cgi?id=736 [3] http://www.xfs.org/index.php/XFS_FAQ#Q:_What_is_the_issue_with_directory_corruption_in_Linux_2.6.17.3F -- 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/20120114195815.GF27850@burratino
Processed: reassign 644410 to src:linux-2.6
Processing commands for cont...@bugs.debian.org: > reassign 644410 src:linux-2.6 2.6.32-35squeeze2 Bug #644410 [linux-image-2.6.32-5-amd64_2.6.32-35squeeze2_amd64] linux-image-2.6.32-5-amd64_2.6.32-35squeeze2_amd64 module drbd.ko Warning: Unknown package 'linux-image-2.6.32-5-amd64_2.6.32-35squeeze2_amd64' Bug reassigned from package 'linux-image-2.6.32-5-amd64_2.6.32-35squeeze2_amd64' to 'src:linux-2.6'. Bug No longer marked as found in versions 2.6.32-35squeeze2. Bug #644410 [src:linux-2.6] linux-image-2.6.32-5-amd64_2.6.32-35squeeze2_amd64 module drbd.ko Bug Marked as found in versions linux-2.6/2.6.32-35squeeze2. > thanks Stopping processing here. Please contact me if you need assistance. -- 644410: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644410 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.13265704165388.transcr...@bugs.debian.org
Bug#653440: linux-image-3.1.0-1-686-pae: Fails to boot since 3.1, apparently in the md subsystem
On Wed, Dec 28, 2011 at 11:33:03AM +0100, Roland Mas wrote: > called triple-patte. The rest of the hard disks is used by a third > partition, and /dev/sd[ab]3 make up a two-device RAID1 array called > obelix. Are both members of this array marked as writemostly, by any chance? (You can check with mdadm -D.) I think you were hit by d2eb35a, same as me; I'll either comment here or file a new bug, depending on the case. -- udp - universal dropping of an pigeon -- 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/20120114192110.ga26...@fabul.fbriere.dyndns.org
Bug#579005: XFS internal error xfs_da_do_buf(2) at line 2085 of file fs/xfs/xfs_da_btree.c.
Rudy Gevaert wrote: > Hi Jonathan, thanks for getting back on this so quickly >> If this is reproducible, would you be able to test patches to debug >> this if provided? > > When I do something in a specific directory I get the backtrace. So > the current corruption (that I'm aware of) is limited to a specific > directory. Interesting. So this might be a case of the kernel not coping well with previous filesystem corruption. [...] > I can export this lun to an other server that is booted with the > newer kernel. I guess I'll have to do a repair when I remount the > lun. If the lun isn't damaged (or it is ver limited) I will need to > bring the service back online. > > (I can failover but the idea is to run not to long without a replica...) > > Also I will have to schedule a maintenance window for this as this > is production. Also normally I can't schedule a window now because > of university exam period... > > Your input is very much appreciated. Feel free to take your time; there's no hurry. Anyway, it's probably best to get in touch with the XFS maintainers first in case they have ideas for tracking it down more easily. Please send a summary of the symptoms so far to x...@oss.sgi.com, cc-ing either me or this bug log so we can track it. Be sure to mention: - what steps you perform to reproduce this, what happens, and how that differs from what you expected (should be easy in this example) - which kernel versions you have tried and results from each - "dmesg" output from booting up as an attachment, if you happen to have it - what kind of further debugging you would be able and not able to do - a link to this bug log, in case someone wants to read the full story If we are lucky, someone on that list might suggest commands to help diagnose it, which should make it easier for others to artificially reproduce, see if 3.x.y is affected, and make sure it is fixed in 3.x.y and 2.6.32.y. Thanks and hope that helps. 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/20120114193059.GE27850@burratino
Bug#650081: ACPI wakeup doesn't work on ASUS P8H67-M EVO
Eric Lavarde wrote: > I'm surely not experienced in these topics, but I thought that there > should be no difference for the BIOS / ACPI between a pure shutdown > and a suspend to disk. Nah, they are different. Suspend to disk happens with ACPI cooperation. [...] > Let me know if I can test / do anything further to solve the issue, It's possible your machine only supports wake from S4 and not S5, in which case the best bet would be to get your (out-of-tree?) driver to suspend to disk sanely. By the way, has there been any effort to get that out-of-tree driver merged upstream? Please file a bug describing the missing functionality it provides, and I can try working on that. All that said, I see no reason _in principle_ that a machine that can wake from S4 should not be able to wake from S5. It might be possible to debug this as an ACPI or RTC issue. Please test 3.2-rc7 from experimental without any out-of-tree drivers, and provide: i. full "dmesg" output from booting, setting the wakeup timer, hibernating with "echo disk >/sys/power/state", and waking up ii. information about what happens if you instead boot, set the wakeup time, shutdown with "shutdown -h now", and wake up Also, when you set the wakeup timer, is it visible from the CMOS menus? If it is, that might help in comparing what happens in cases (i) and (ii). 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/20120114163310.GA27850@burratino
Processed: tagging 655816
Processing commands for cont...@bugs.debian.org: > tags 655816 + pending Bug #655816 [src:linux-2.6] Changes from longterm 2.6.32.54 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 655816: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655816 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.132655157311922.transcr...@bugs.debian.org
Bug#650081: ACPI wakeup doesn't work on ASUS P8H67-M EVO
Hi, On 24/12/11 08:24, Jonathan Nieder wrote: forwarded 650081 http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure/42256 quit Eric Lavarde wrote: [ 581.247437] I2C timeout [ 581.247442] IRS 0001 [... hundreds of line of this type ...] Let's take this upstream, starting with this bit, under the principle "fix the most egregiously broken piece first". Many thanks, Jonathan Sorry for the delay and possibly for the confusion, but holiday and the VDR is in production so my users r my family doesn't like extensive test sessions (or they can't look TV ;-) ). Anyway, as already written in the answer to [1], I've now the possibility to do tests with a clean kernel and the result is exactly the same: waking up after a halt / poweroff does NOT work, waking up after a 'disk' suspend DOES work (even with latest Kernel linux-image-3.1.0-1-amd64 / 3.1.8-2). I'm surely not experienced in these topics, but I thought that there should be no difference for the BIOS / ACPI between a pure shutdown and a suspend to disk. Checking what is done differently in the kernel might tell us what the issue is, no?! Let me know if I can test / do anything further to solve the issue, I can possibly work around the other issues with suspend to disk (probably the right rmmod at the right place) but I'm not a big fan of suspend as I favor stability over speed of boot. Thanks, Eric [1] http://article.gmane.org/gmane.linux.drivers.video-input-infrastructure/42256 -- 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/4f118545.8090...@zorglub.s.bawue.de
Bug#650081: ACPI wakeup doesn't work on ASUS P8H67-M EVO
Hi, On 24/12/11 08:24, Jonathan Nieder wrote: forwarded 650081 http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure/42256 quit Eric Lavarde wrote: [ 581.247437] I2C timeout [ 581.247442] IRS 0001 [... hundreds of line of this type ...] Let's take this upstream, starting with this bit, under the principle "fix the most egregiously broken piece first". Many thanks, Jonathan Sorry for the delay and possibly for the confusion, but holiday and the VDR is in production so my users r my family doesn't like extensive test sessions (or they can't look TV ;-) ). Anyway, as already written in the answer to [1], I've now the possibility to do tests with a clean kernel and the result is exactly the same: waking up after a halt / poweroff does NOT work, waking up after a 'disk' suspend DOES work (even with latest Kernel linux-image-3.1.0-1-amd64 / 3.1.8-2). I'm surely not experienced in these topics, but I thought that there should be no difference for the BIOS / ACPI between a pure shutdown and a suspend to disk. Checking what is done differently in the kernel might tell us what the issue is, no?! Let me know if I can test / do anything further to solve the issue, I can possibly work around the other issues with suspend to disk (probably the right rmmod at the right place) but I'm not a big fan of suspend as I favor stability over speed of boot. Thanks, Eric [1] http://article.gmane.org/gmane.linux.drivers.video-input-infrastructure/42256 -- 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/4f11852e.90...@zorglub.s.bawue.de
Bug#622349: nfs-common: mount.nfs4 breaks with systemd and separate /usr partition
hi! is there any progresss on this issue? i'm also seeing this on an up2date debian squeeze. thanks, raoul -- DI (FH) Raoul Bhatia M.Sc. email. r.bha...@ipax.at Technischer Leiter IPAX - Aloy Bhatia Hava OG web. http://www.ipax.at Barawitzkagasse 10/2/2/11 email.off...@ipax.at 1190 Wien tel. +43 1 3670030 FN 277995t HG Wien fax.+43 1 3670030 15 -- 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/4f114abf.8040...@ipax.at
Bug#654681: [INTL:es] Spanish debconf template translation for linux-latest-2.6
El 13/01/12 15:31, Ben Hutchings escribió: On Thu, 2012-01-05 at 10:16 +0100, Slime Siabef wrote: Package: linux-latest-2.6 Version: 41 Severity: wishlist Tags: l10n patch Spanish debconf translation attached. Has this been reviewed? [sorry for mi english,] (?) This package was reviewed, isn't it? Let's see... ITT on 19/08 RFR on 19/08 LCFC on 05/09 BTS on 08/01 (... long time... I'll explain it (Slime Siabef is my brother, so :) ). It was his first translation and believed that he had already sent to BTS ... but he was wrong.) # linux-latest-2.6 po-debconf translation to Spanish # Copyright (C) 2012 Software in the Public Interest # This file is distributed under the same license as the linux-latest-2.6 package. # # Changes: # - Initial translation # Slime Siabef, 2012 # # - Updates # # # Traductores, si no conocen el formato PO, merece la pena leer la # documentación de gettext, especialmente las secciones dedicadas a este # formato, por ejemplo ejecutando: # info -n '(gettext)PO Files' # info -n '(gettext)Header Entry' # # Equipo de traducción al español, por favor lean antes de traducir # los siguientes documentos: # # - El proyecto de traducción de Debian al español # http://www.debian.org/intl/spanish/ # especialmente las notas y normas de traducción en # http://www.debian.org/intl/spanish/notas # # - La guía de traducción de po's de debconf: # /usr/share/doc/po-debconf/README-trans # o http://www.debian.org/intl/l10n/po-debconf/README-trans I don't think the above comments should be left in the PO file, should they? All of spanish deb-conf files have that lines. What's the problem? (?) Ben. msgid "" msgstr "" "Project-Id-Version: linux-latest-2.6_39\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2011-07-24 16:15+0200\n" "PO-Revision-Date:\n" "Last-Translator: Slime Siabef\n" "Language-Team: Debian Spanish\n" "Language: \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "X-Poedit-Language: Spanish\n" #. Type: error #. Description #: ../linux-image-686.templates:1001 msgid "This system requires a different kernel configuration" msgstr "El sistema requiere una configuración diferente del núcleo." #. Type: error #. Description #: ../linux-image-686.templates:1001 msgid "Debian's '686' kernel configuration has been replaced by the '686-pae' configuration, which uses PAE (Physical Address Extension). However, the CPU in this system does not support PAE." msgstr "La configuración del núcleo «686» de Debian ha sido reemplazada por la configuración «686-pae», que utiliza PAE (Extensión de dirección física). Sin embargo, la CPU del sistema no lo soporta." #. Type: error #. Description #: ../linux-image-686.templates:1001 msgid "You should install linux-image-486 and remove linux-image-686 and/or linux-image-2.6-686 if they are currently installed." msgstr "Se debería instalar linux-image-486 y eliminar linux-image-686 y/o linux-image-2.6-686 si estuviesen instalados." -- 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/4f11496f.1030...@gmail.com
