Processed: closing 600064
Processing commands for cont...@bugs.debian.org: close 600064 Bug#600064: linux-image-2.6.32-5-xen-amd64: machine reboots during dom0 bootup if Intel TXT enabled 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Linus van Geuns li...@vangeuns.name thanks Stopping processing here. Please contact me if you need assistance. -- 600064: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600064 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.130518219030787.transcr...@bugs.debian.org
Bug#626189: linux-image-2.6.32-5-xen-686: kernel BUG (invalid opcode) on reboot -f
On Mon, 2011-05-09 at 19:55 +0200, Ferenc Wagner wrote: Package: linux-image-2.6.32-5-xen-686 Version: 2.6.32-31 Severity: normal Hi, As a STONITH measure, I issued reboot -f on a Xen dom0 while several domUs were running. This didn't kill the machine but resulted in the BUGs below, and made further interaction impossible, although the kernel was running and some firewall logs even made it through the syslog daemon. Of course I didn't try to reproduce the issue (it's a production system in active/backup HA), but I'm willing to do further experiments that don't risk further data loss if needed. This happened on a perfectly stock and up-to-date squeeze Xen system running several PV guests. 2.6.32-34 (in stable-proposed-updates) contains fixes to vmalloc syncing and vunmap which can both have an impact on both LVM and XFS. I think it would be worth trying that updated kernel. Cheers, Ian. -- Ian Campbell I am currently transitioning to a new OpenPGP key, please see: http://www.hellion.org.uk/key-transition-2011-04-27-2F6BCD59-to-79074FA8.txt Oh, that sound of male ego. You travel halfway across the galaxy and it's still the same song. -- Eve McHuron, Mudd's Women, stardate 1330.1 signature.asc Description: This is a digitally signed message part
Re: linux-2.6_2.6.38-5_m68k.changes ACCEPTED
On Thu, 12 May 2011, Geert Uytterhoeven wrote: Do we really want to compile wireless on m68k? AFAIK we don't have any. http://marc.info/?l=linux-m68km=128628785718187w=2 I suspect this list is also applicable to atari and amiga (?) Finn -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/alpine.OSX.2.00.1105121719490.218@ibook.intranet
Re: linux-2.6_2.6.38-5_m68k.changes ACCEPTED
Ben Hutchings dixit: Anyway, I don't think the TPM drivers could be used on most non-x86 architectures. We should just disable them. Yes, these are good candidates for being left out. WLAN devices probably as well, but I’ll leave that to the platform experts to decide. (Most TPMs are included in the chipset anyway, but there _may_ be some externally addressed ones, yet I don’t know if they have ever been used on non-i386 (or amd64, I suppose) machines.) drivers/net/lib8390.c:256: warning: '__ei_tx_timeout' defined but not used There’s an ongoing discussion about the 8390-using network drivers, they’re working on fixing it. WARNING: modpost: Found 1 section mismatch(es). To see full details build your kernel with: 'make CONFIG_DEBUG_SECTION_MISMATCH=y' Don't know; do what it says if you care. OK, will do that. Will they show up when cross-compiling? Thanks for looking into it, I hope the respective code gurus can/will fix the issues. bye, //mirabilos -- If Harry Potter gets a splitting headache in his scar when he’s near Tom Riddle (aka Voldemort), does Tom get pain in the arse when Harry is near him? -- me, wondering why it’s not Jerry Potter……… -- 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/pine.bsm.4.64l.1105120727490.17...@herc.mirbsd.org
Bug#626446: initramfs-tools: [Patch] Option to enable xz compression for initrd
On Thu, May 12, 2011 at 12:08:17PM +0800, Steven Shiau wrote: Since the linux kernel (e.g. linux-image-2.6.38-2-686) on Debian Sid has enabled XZ initrd option, i.e. CONFIG_RD_XZ=y, it would be great to have an option to use XZ initrd. This is specially useful to Debian live, the size could be smaller. Attached please find the patch to enable it. My 2 cents. this is already done and will be uploaded soonest. http://git.debian.org/?p=kernel/initramfs-tools.git;a=summary next time care to check upstream repository, my 2 cents. see docs for dev http://git.debian.org/?p=kernel/initramfs-tools.git;a=blob_plain;f=docs/maintainer-notes.html;hb=HEAD happy hacking -- maks -- 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/20110512075058.gi4...@vostochny.stro.at
Re: linux-2.6_2.6.38-5_m68k.changes ACCEPTED
On Thu, May 12, 2011 at 09:31, Thorsten Glaser t...@mirbsd.de wrote:
WARNING: modpost: Found 1 section mismatch(es).
To see full details build your kernel with:
'make CONFIG_DEBUG_SECTION_MISMATCH=y'
Don't know; do what it says if you care.
OK, will do that. Will they show up when cross-compiling?
Yes they do. I just haven't got to fixing them.
Patches are accepted :-)
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say programmer or something like that.
-- Linus Torvalds
--
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/BANLkTi=+hvdfcs4juh_pv6ym5xqa7jn...@mail.gmail.com
Re: linux-2.6_2.6.38-5_m68k.changes ACCEPTED
On Thu, May 12, 2011 at 09:24, Finn Thain fth...@telegraphics.com.au wrote:
On Thu, 12 May 2011, Geert Uytterhoeven wrote:
Do we really want to compile wireless on m68k? AFAIK we don't have any.
http://marc.info/?l=linux-m68km=128628785718187w=2
I suspect this list is also applicable to atari and amiga (?)
Yeah, I should look into updating the defconfigs again.
Haven't done that anymore since the concept of minimal defconfigs was
introduced, as I'm still a bit worried if I can trust them or not (options not
mentioned in the minimal defconfig may silently change their value
depending on Kconfig logic; with the full ones I would immeditaly notice).
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say programmer or something like that.
-- Linus Torvalds
--
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/BANLkTi=fz_wt3j_ceqwjdqbprxlkasq...@mail.gmail.com
Re: linux-2.6_2.6.38-5_m68k.changes ACCEPTED
Geert Uytterhoeven dixit: I suspect this list is also applicable to atari and amiga (?) Yeah, I should look into updating the defconfigs again. Mh. Debian provides their own configs as well though, I think Wouter/Stephen/cts should have a look at them. (You should have seen the comments by one about why I would want to disable CONFIG_STAGING although that was already in the 2.6.32 tree…) bye, //mirabilos -- [00:02] Vutral gecko: benutzt du emacs ? [00:03] gecko nö [00:03] gecko nur n normalen mac [00:04] Vutral argl [00:04] Vutral ne den editor -- Vutral und gecko2 in #deutsch (NB: Editor? Betriebssystem.) -- 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/pine.bsm.4.64l.1105120750500.17...@herc.mirbsd.org
Re: linux-2.6_2.6.38-5_m68k.changes ACCEPTED
On Thu, May 12, 2011 at 07:38:22AM +0200, Geert Uytterhoeven wrote: Do we really want to compile wireless on m68k? AFAIK we don't have any. I don't think we have any drivers working right now, but if we ever fix PCMCIA support for real on any of the systems with slots we could get the orinoco_cs driver working. I don't have the time, but I do have a PowerBook 190 and some PCMCIA cards to try out. It's on the very long list of things I'd like to look at eventually. Brad Boyer f...@allandria.com -- 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/20110512071514.ga7...@cynthia.pants.nu
Bug#625217: xen-linux-system-2.6.32-5-xen-amd64: Heavy load on domU causes dom0 to run out of memory
Hi Sebastian, Thanks for your report. On Mon, 2011-05-02 at 16:50 +0200, Sebastian Hofmann wrote: Package: xen-linux-system-2.6.32-5-xen-amd64 Version: 2.6.32-31 Severity: critical Justification: breaks the whole system Hi, I have 64 bit xen kernel from squeeze installed on a dual xeon maschine. Usually everything runs fine until it comes to heavy load on a domU with high I/O and memory consumption. This causes the dom0 to run out of memory and to kill several processes (see log below). As a consequence of this, the whole system becomes unusable. I tried several things like assign dedicated memory to dom0, disable balloning, increase scheduler domain weights and assigned dedicated CPUs to dom0 as described in http://wiki.xensource.com/xenwiki/XenBestPractices but had no success. I think a domU should never break the whole system, so this might be a bug. Please let me know if you need further information. Thanks Sebastian May 2 16:05:26 hercules kernel: [ 1768.319877] nrpe invoked oom-killer: gfp_mask=0x200da, order=0, oom_adj=0 May 2 16:05:26 hercules kernel: [ 1768.319883] nrpe cpuset=/ mems_allowed=0 May 2 16:05:26 hercules kernel: [ 1768.319886] Pid: 2118, comm: nrpe Not tainted 2.6.32-5-xen-amd64 #1 Am I right that nrpe is part of nagios? (it's probably just the unluck process so tells us nothing really) What sort of load are the domUs experiencing? i.e. CPU, network, disk etc. What does your storage stack look like? (are you using LVM, iSCSI, DRDB, SW RAID, filesystems etc). Are you running anything interesting in domain 0 other than the Xen toolstack, nagios, sshd etc? What does /proc/meminfo look like after a fresh boot? Lastly, please can you provide a dmesg log of the initial bootup. Cheers, Ian. -- Ian Campbell Current Noise: Behemoth - Alas, Lord Is Upon Me To stay young requires unceasing cultivation of the ability to unlearn old falsehoods. -- Lazarus Long, Time Enough For Love -- 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/1305188425.26692.471.ca...@zakaz.uk.xensource.com
Bug#626446: initramfs-tools: [Patch] Option to enable xz compression for initrd
this is already done and will be uploaded soonest. http://git.debian.org/?p=kernel/initramfs-tools.git;a=summary next time care to check upstream repository, my 2 cents. Very cool. Almost on the same day... Definitely! I will. see docs for dev http://git.debian.org/?p=kernel/initramfs-tools.git;a=blob_plain;f=docs/maintainer-notes.html;hb=HEAD Sure, thanks! happy hacking -- Steven Shiau steven _at_ nchc org tw steven _at_ stevenshiau org National Center for High-performance Computing, Taiwan. http://www.nchc.org.tw Public Key Server PGP Key ID: 1024D/9762755A Fingerprint: A2A1 08B7 C22C 3D06 34DB F4BC 08B3 E3D7 9762 755A -- 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/4dcb9dac.30...@nchc.org.tw
Bug#622967: marked as done (linux-2.6: [INTL:nl] Dutch po-debconf translation)
Your message dated Thu, 12 May 2011 09:39:38 +
with message-id e1qksms-0003cp...@franck.debian.org
and subject line Bug#622967: fixed in linux-2.6 2.6.39~rc7-1~experimental.1
has caused the Debian Bug report #622967,
regarding linux-2.6: [INTL:nl] Dutch po-debconf translation
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.)
--
622967: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622967
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Severity: wishlist
Tags: l10n patch
Please find attached the Dutch po-debconf translation for linux-2.6
Willem Kuyn
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.38-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash# Dutch translation of linux-2.6 po-debconf templates.
# Copyright (C) 2011 THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the linux-2.6 package.
# Willem Kuyn willemk...@gmail.com, 2011.
#
msgid
msgstr
Project-Id-Version: linux-2.6\n
Report-Msgid-Bugs-To: linux-...@packages.debian.org\n
POT-Creation-Date: 2011-03-30 10:34+0200\n
PO-Revision-Date: 2011-04-02 20:07+0100\n
Last-Translator: willem kuyn willemk...@gmail.com\n
Language-Team: Debian-Dutch debian-l10n-du...@lists.debian.org\n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=UTF-8\n
Content-Transfer-Encoding: 8bit\n
#. Type: boolean
#. Description
#: ../templates/temp.image.plain/templates:2001
msgid Abort installation after depmod error?
msgstr Installatie afbreken na depmod fout?
#. Type: boolean
#. Description
#: ../templates/temp.image.plain/templates:2001
msgid The 'depmod' command exited with the exit code ${exit_value} (${SIGNAL}${CORE}).
msgstr De 'depmod' opdracht stopte met foutcode ${exit_value} (${SIGNAL}${CORE}).
#. Type: boolean
#. Description
#: ../templates/temp.image.plain/templates:2001
msgid Since this image uses initrd, the ${modules_base}/=V/modules.dep file will not be deleted, even though it may be invalid.
msgstr Omdat deze afbeelding initrd gebruikt, zal het ${modules_base}/=V/modules.dep bestand niet verwijderd worden, ook al is het niet correct.
#. Type: boolean
#. Description
#: ../templates/temp.image.plain/templates:2001
msgid You should abort the installation and fix the errors in depmod, or regenerate the initrd image with a known good modules.dep file. If you don't abort the installation, there is a danger that the system will fail to boot.
msgstr U zou de installatie moeten afbreken en de fouten in depmod herstellen, of het initrd bestand opnieuw moeten genereren met een correct modules.dep bestand. Als u de installatie niet afbreekt dan bestaat het gevaar dat het systeem niet zal starten.
#. Type: boolean
#. Description
#: ../templates/temp.image.plain/templates:3001
msgid Abort kernel removal?
msgstr Het verwijderen van de kernel afbreken?
#. Type: boolean
#. Description
#: ../templates/temp.image.plain/templates:3001
msgid You are running a kernel (version ${running}) and attempting to remove the same version.
msgstr U gebruikt kernel (versie ${running}) en probeert de zelfde versie te verwijderen.
#. Type: boolean
#. Description
#: ../templates/temp.image.plain/templates:3001
msgid This can make the system unbootable as it will remove /boot/vmlinuz-${running} and all modules under the directory /lib/modules/${running}. This can only be fixed with a copy of the kernel image and the corresponding modules.
msgstr Het resultaat kan zijn dat het systeem niet start omdat het /boot/vmlinuz-${running} en alle modules onder /lib/modules/${running} verwijdert. Dit kan alleen gerepareerd worden met een kopie van het kernel bestand en de bijbehorende modules.
#. Type: boolean
#. Description
#: ../templates/temp.image.plain/templates:3001
msgid It is highly recommended to abort the kernel removal unless you are prepared to fix the system after removal.
msgstr Het wordt ten sterkste aanbevolen om het verwijderen van de kernel af te breken tenzij u bent voorbereid om het systeem te repareren na het verwijderen.
#. Type: note
#. Description
#: ../templates/temp.image.plain/templates:4001
msgid Required firmware files may be missing
msgstr De vereiste firmware bestanden kunnen ontbreken
#. Type: note
#. Description
#: ../templates/temp.image.plain/templates:4001
msgid This system is currently running Linux ${runningversion} and you are installing Linux ${version}. In the new version some of the drivers used on
Bug#625613: marked as done (linux-2.6: Please enable CONFIG_RTL8192CU)
Your message dated Thu, 12 May 2011 09:39:38 + with message-id e1qksms-0003cu...@franck.debian.org and subject line Bug#625613: fixed in linux-2.6 2.6.39~rc7-1~experimental.1 has caused the Debian Bug report #625613, regarding linux-2.6: Please enable CONFIG_RTL8192CU 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.) -- 625613: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625613 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.39~rc5-1~experimental.1 Severity: wishlist Hi, Please consider enabling CONFIG_RTL8192CU (Realtek RTL8192CU/RTL8188CU USB Wireless Network Adapter) as a module, for support of Realtek RTL8188CE-VAU, RTL8188CUS and RTL8192CU USB 802.11n wireless LAN chipsets. This mac80211 driver was added in Linux 2.6.39. As rtl8192cu uses non-free firmware, I will open an additional wishlist bug against firmware-realtek for its possible inclusion. Geoff -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.39-rc5-686-pae (SMP w/1 CPU core) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.39~rc7-1~experimental.1 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: linux-2.6_2.6.39~rc7-1~experimental.1.diff.gz to main/l/linux-2.6/linux-2.6_2.6.39~rc7-1~experimental.1.diff.gz linux-2.6_2.6.39~rc7-1~experimental.1.dsc to main/l/linux-2.6/linux-2.6_2.6.39~rc7-1~experimental.1.dsc linux-2.6_2.6.39~rc7.orig.tar.gz to main/l/linux-2.6/linux-2.6_2.6.39~rc7.orig.tar.gz linux-doc-2.6.39_2.6.39~rc7-1~experimental.1_all.deb to main/l/linux-2.6/linux-doc-2.6.39_2.6.39~rc7-1~experimental.1_all.deb linux-headers-2.6.39-rc7-all-amd64_2.6.39~rc7-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-headers-2.6.39-rc7-all-amd64_2.6.39~rc7-1~experimental.1_amd64.deb linux-headers-2.6.39-rc7-all_2.6.39~rc7-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-headers-2.6.39-rc7-all_2.6.39~rc7-1~experimental.1_amd64.deb linux-headers-2.6.39-rc7-amd64_2.6.39~rc7-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-headers-2.6.39-rc7-amd64_2.6.39~rc7-1~experimental.1_amd64.deb linux-headers-2.6.39-rc7-common_2.6.39~rc7-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-headers-2.6.39-rc7-common_2.6.39~rc7-1~experimental.1_amd64.deb linux-image-2.6.39-rc7-amd64-dbg_2.6.39~rc7-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-image-2.6.39-rc7-amd64-dbg_2.6.39~rc7-1~experimental.1_amd64.deb linux-image-2.6.39-rc7-amd64_2.6.39~rc7-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-image-2.6.39-rc7-amd64_2.6.39~rc7-1~experimental.1_amd64.deb linux-libc-dev_2.6.39~rc7-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-libc-dev_2.6.39~rc7-1~experimental.1_amd64.deb linux-manual-2.6.39_2.6.39~rc7-1~experimental.1_all.deb to main/l/linux-2.6/linux-manual-2.6.39_2.6.39~rc7-1~experimental.1_all.deb linux-patch-debian-2.6.39_2.6.39~rc7-1~experimental.1_all.deb to main/l/linux-2.6/linux-patch-debian-2.6.39_2.6.39~rc7-1~experimental.1_all.deb linux-source-2.6.39_2.6.39~rc7-1~experimental.1_all.deb to main/l/linux-2.6/linux-source-2.6.39_2.6.39~rc7-1~experimental.1_all.deb linux-support-2.6.39-rc7_2.6.39~rc7-1~experimental.1_all.deb to main/l/linux-2.6/linux-support-2.6.39-rc7_2.6.39~rc7-1~experimental.1_all.deb linux-tools-2.6.39_2.6.39~rc7-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-tools-2.6.39_2.6.39~rc7-1~experimental.1_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 625...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. maximilian attems m...@debian.org (supplier of updated linux-2.6 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 10 May 2011 15:11:00 +0200 Source: linux-2.6 Binary: linux-tools-2.6.39 linux-source-2.6.39 linux-doc-2.6.39 linux-manual-2.6.39 linux-patch-debian-2.6.39 linux-support-2.6.39-rc7 linux-libc-dev linux-headers-2.6.39-rc7-all
Bug#626141: marked as done (Missing CONFIG_EEEPC_WMI, needed for hotkey support)
Your message dated Thu, 12 May 2011 09:39:38 + with message-id e1qksms-0003cx...@franck.debian.org and subject line Bug#626141: fixed in linux-2.6 2.6.39~rc7-1~experimental.1 has caused the Debian Bug report #626141, regarding Missing CONFIG_EEEPC_WMI, needed for hotkey support 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.) -- 626141: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626141 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.39~rc6-1~experimental.1 Severity: normal In the 2.6.39-rc* series of kernels, CONFIG_EEEPC_WMI seems to have gone away. This module is needed to support hotkeys on the Eee PC. $ grep CONFIG_EEE /boot/config-2.6.38-2-amd64 /boot/config-2.6.39-rc*-amd64 /boot/config-2.6.38-2-amd64:CONFIG_EEEPC_LAPTOP=m /boot/config-2.6.38-2-amd64:CONFIG_EEEPC_WMI=m /boot/config-2.6.39-rc5-amd64:CONFIG_EEEPC_LAPTOP=m /boot/config-2.6.39-rc6-amd64:CONFIG_EEEPC_LAPTOP=m Thanks, Ben -- Package-specific info: ** Version: Linux version 2.6.39-rc6-amd64 (Debian 2.6.39~rc6-1~experimental.1) (m...@debian.org) (gcc version 4.4.5 (Debian 4.4.5-12) ) #1 SMP Sun May 8 13:50:44 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.39-rc5-amd64 root=UUID=b7d082d8-c134-477f-8b6d-1fbadd46fad7 ro quiet kexec_jump_back_entry=0x88007a28e450 ** Not tainted ** Kernel log: [3.613127] usb 1-6: Manufacturer: Azurewave [3.613135] usb 1-6: SerialNumber: 200901010001 [3.864090] usb 2-1: new low speed USB device number 2 using uhci_hcd [4.041306] usb 2-1: New USB device found, idVendor=046d, idProduct=c521 [4.041325] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [4.041339] usb 2-1: Product: USB Receiver [4.041350] usb 2-1: Manufacturer: Logitech [4.132558] input: Logitech USB Receiver as /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.0/input/input1 [4.132983] generic-usb 0003:046D:C521.0001: input,hidraw0: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-:00:1d.0-1/input0 [4.164846] input: Logitech USB Receiver as /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.1/input/input2 [4.165343] generic-usb 0003:046D:C521.0002: input,hiddev0,hidraw1: USB HID v1.11 Device [Logitech USB Receiver] on usb-:00:1d.0-1/input1 [4.166233] usbcore: registered new interface driver usbhid [4.166246] usbhid: USB HID core driver [4.337845] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [4.688206] udevd[253]: starting version 168 [4.991695] input: Lid Switch as /devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input3 [5.024548] ACPI: Lid Switch [LID] [5.024898] input: Sleep Button as /devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input4 [5.024925] ACPI: Sleep Button [SLPB] [5.025238] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input5 [5.025261] ACPI: Power Button [PWRB] [5.025569] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input6 [5.025592] ACPI: Power Button [PWRF] [5.055593] wmi: Mapper loaded [5.066006] ACPI: AC Adapter [AC0] (on-line) [5.093747] ACPI: acpi_idle registered with cpuidle [5.109513] Monitor-Mwait will be used to enter C-1 state [5.109664] Monitor-Mwait will be used to enter C-2 state [5.109701] Marking TSC unstable due to TSC halts in idle [5.110387] Switching to clocksource hpet [5.202939] ACPI: Battery Slot [BAT0] (battery present) [5.877748] [drm] Initialized drm 1.1.0 20060810 [5.938739] cfg80211: Calling CRDA to update world regulatory domain [6.060745] Linux video capture interface: v2.00 [6.261685] uvcvideo: Found UVC 1.00 device USB2.0 UVC VGA WebCam (13d3:5702) [6.281756] input: USB2.0 UVC VGA WebCam as /devices/pci:00/:00:1d.7/usb1/1-6/1-6:1.0/input/input7 [6.282049] usbcore: registered new interface driver uvcvideo [6.282061] USB Video Class driver (v1.0.0) [6.451248] i915 :00:02.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [6.451269] i915 :00:02.0: setting latency timer to 64 [6.514567] ath9k :02:00.0: PCI INT A - GSI 17 (level, low) - IRQ 17 [6.514596] ath9k :02:00.0: setting latency timer to 64 [6.567354] ath: EEPROM regdomain: 0x60 [6.567367] ath: EEPROM indicates we should expect a direct regpair map [6.567384] ath: Country alpha2 being used: 00 [6.567393] ath: Regpair used: 0x60 [6.587036] i915 :00:02.0: irq 44 for MSI/MSI-X [6.587061] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [6.587073] [drm]
linux-2.6_2.6.39~rc7-1~experimental.1_amd64.changes ACCEPTED into experimental
Accepted: linux-2.6_2.6.39~rc7-1~experimental.1.diff.gz to main/l/linux-2.6/linux-2.6_2.6.39~rc7-1~experimental.1.diff.gz linux-2.6_2.6.39~rc7-1~experimental.1.dsc to main/l/linux-2.6/linux-2.6_2.6.39~rc7-1~experimental.1.dsc linux-2.6_2.6.39~rc7.orig.tar.gz to main/l/linux-2.6/linux-2.6_2.6.39~rc7.orig.tar.gz linux-doc-2.6.39_2.6.39~rc7-1~experimental.1_all.deb to main/l/linux-2.6/linux-doc-2.6.39_2.6.39~rc7-1~experimental.1_all.deb linux-headers-2.6.39-rc7-all-amd64_2.6.39~rc7-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-headers-2.6.39-rc7-all-amd64_2.6.39~rc7-1~experimental.1_amd64.deb linux-headers-2.6.39-rc7-all_2.6.39~rc7-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-headers-2.6.39-rc7-all_2.6.39~rc7-1~experimental.1_amd64.deb linux-headers-2.6.39-rc7-amd64_2.6.39~rc7-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-headers-2.6.39-rc7-amd64_2.6.39~rc7-1~experimental.1_amd64.deb linux-headers-2.6.39-rc7-common_2.6.39~rc7-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-headers-2.6.39-rc7-common_2.6.39~rc7-1~experimental.1_amd64.deb linux-image-2.6.39-rc7-amd64-dbg_2.6.39~rc7-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-image-2.6.39-rc7-amd64-dbg_2.6.39~rc7-1~experimental.1_amd64.deb linux-image-2.6.39-rc7-amd64_2.6.39~rc7-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-image-2.6.39-rc7-amd64_2.6.39~rc7-1~experimental.1_amd64.deb linux-libc-dev_2.6.39~rc7-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-libc-dev_2.6.39~rc7-1~experimental.1_amd64.deb linux-manual-2.6.39_2.6.39~rc7-1~experimental.1_all.deb to main/l/linux-2.6/linux-manual-2.6.39_2.6.39~rc7-1~experimental.1_all.deb linux-patch-debian-2.6.39_2.6.39~rc7-1~experimental.1_all.deb to main/l/linux-2.6/linux-patch-debian-2.6.39_2.6.39~rc7-1~experimental.1_all.deb linux-source-2.6.39_2.6.39~rc7-1~experimental.1_all.deb to main/l/linux-2.6/linux-source-2.6.39_2.6.39~rc7-1~experimental.1_all.deb linux-support-2.6.39-rc7_2.6.39~rc7-1~experimental.1_all.deb to main/l/linux-2.6/linux-support-2.6.39-rc7_2.6.39~rc7-1~experimental.1_all.deb linux-tools-2.6.39_2.6.39~rc7-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-tools-2.6.39_2.6.39~rc7-1~experimental.1_amd64.deb Override entries for your package: linux-2.6_2.6.39~rc7-1~experimental.1.dsc - source devel linux-doc-2.6.39_2.6.39~rc7-1~experimental.1_all.deb - optional doc linux-headers-2.6.39-rc7-all-amd64_2.6.39~rc7-1~experimental.1_amd64.deb - optional kernel linux-headers-2.6.39-rc7-all_2.6.39~rc7-1~experimental.1_amd64.deb - optional kernel linux-headers-2.6.39-rc7-amd64_2.6.39~rc7-1~experimental.1_amd64.deb - optional kernel linux-headers-2.6.39-rc7-common_2.6.39~rc7-1~experimental.1_amd64.deb - optional kernel linux-image-2.6.39-rc7-amd64-dbg_2.6.39~rc7-1~experimental.1_amd64.deb - extra debug linux-image-2.6.39-rc7-amd64_2.6.39~rc7-1~experimental.1_amd64.deb - optional kernel linux-libc-dev_2.6.39~rc7-1~experimental.1_amd64.deb - optional devel linux-manual-2.6.39_2.6.39~rc7-1~experimental.1_all.deb - optional doc linux-patch-debian-2.6.39_2.6.39~rc7-1~experimental.1_all.deb - optional kernel linux-source-2.6.39_2.6.39~rc7-1~experimental.1_all.deb - optional kernel linux-support-2.6.39-rc7_2.6.39~rc7-1~experimental.1_all.deb - optional devel linux-tools-2.6.39_2.6.39~rc7-1~experimental.1_amd64.deb - optional kernel Announcing to debian-devel-chan...@lists.debian.org Closing bugs: 622967 625613 626141 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/e1qksmr-0003ci...@franck.debian.org
Bug#626478: nfs-common: Please build mount.nfs with libmount support
Package: nfs-common Version: 1:1.2.3-1 Severity: normal Hi, With mount (util-linux) 2.19.1 in experimental, libmount.so.1 is provided for use by mount helpers such as mount.nfs. [the next upload will include proper libmount-dev and libmount1 packages; it's currently in util-linux] It would be great if mount.nfs could be built with libmount support. This is needed for removal of /etc/mtab (symlink to /proc/mounts) and r/o root. While I don't follow upstream development too closely, the patches were posted to the list, and are in use in Fedora. You can find them here: http://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commitdiff;h=c01e5ca6179b8f5b041605d9bbd75a0f76812d54 http://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commitdiff;h=a99269230a0e77e7bed4fa31c9547f0d61c7f206 Once util-linux gains the libmount-dev package, it would be great if we could have nfs-utils building against it with --enable-libmount-mount; experimental would be fine for testing purposes since that's where util-linux is the for the time being. Thanks, Roger -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (550, 'unstable'), (500, 'testing'), (400, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-2-amd64 (SMP w/4 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 nfs-common depends on: ii adduser3.112+nmu2add and remove users and groups ii initscripts2.88dsf-13.5 scripts for initializing and shutt ii libc6 2.13-2Embedded GNU C Library: Shared lib ii libcap21:2.20-1 support for getting/setting POSIX. ii libcomerr2 1.41.12-4 common error description library pn libevent-1.4-2 none(no description available) ii libgssapi-krb5-2 1.9+dfsg-1+b1 MIT Kerberos runtime libraries - k pn libgssglue1none(no description available) ii libk5crypto3 1.9+dfsg-1+b1 MIT Kerberos runtime libraries - C ii libkrb5-3 1.9+dfsg-1+b1 MIT Kerberos runtime libraries pn libnfsidmap2 none(no description available) pn libtirpc1 none(no description available) ii libwrap0 7.6.q-19 Wietse Venema's TCP wrappers libra ii lsb-base 3.2-27Linux Standard Base 3.2 init scrip ii netbase4.45 Basic TCP/IP networking system pn rpcbind | portmap none(no description available) ii ucf3.0025+nmu2 Update Configuration File: preserv Versions of packages nfs-common recommends: ii python2.6.6-14 interactive high-level object-orie nfs-common suggests no packages. -- 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/20110512093019.10479.48868.report...@ravenclaw.codelibre.net
Bug#534964: Any updates on this BUG?
On Wed, May 11, 2011 at 12:08:10PM +, maximilian attems wrote: On Wed, May 11, 2011 at 11:33:31AM +, maximilian attems wrote: On Wed, May 11, 2011 at 04:43:06PM +0530, Balbir Singh wrote: bal...@linux.vnet.ibm.com wrote: Hi, Ben, We've made significant progress in reducing the overhead of memory cgroup subsystem. I'd request you to try it and enable it. If there are some concerns, we could always address them. There are more interesting changes on the way as well. could you point to the relevant commits? so unless this information comes along soon, I'll revert my change. cheers -- maks -- 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/20110512115325.gc3...@vostochny.stro.at
Processed: tagging 626446
Processing commands for cont...@bugs.debian.org: tags 626446 + pending Bug #626446 [initramfs-tools] initramfs-tools: [Patch] Option to enable xz compression for initrd Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 626446: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626446 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.130520282326219.transcr...@bugs.debian.org
Processed: tagging 594189
Processing commands for cont...@bugs.debian.org: tags 594189 + pending Bug #594189 [initramfs-tools] initramfs-tools: environment variable to disable run_bootloader Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 594189: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594189 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.130520298326897.transcr...@bugs.debian.org
Processed: tagging 603858
Processing commands for cont...@bugs.debian.org: tags 603858 + pending Bug #603858 [initramfs-tools] Mount options for proc conflict with /etc/fstab breaking /etc/init.d/mountall.sh Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 603858: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603858 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.130520300926929.transcr...@bugs.debian.org
Processed: tagging 620924
Processing commands for cont...@bugs.debian.org: tags 620924 + pending Bug #620924 [initramfs-tools] Please drop dead usplash code Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 620924: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620924 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.130520309727265.transcr...@bugs.debian.org
Processed: tagging 624702
Processing commands for cont...@bugs.debian.org: tags 624702 - moreinfo Bug #624702 [initramfs-tools] initramfs-tools: mkinitramfs doesn't honor setting of BOOTDIR when searching for config-... files Removed tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 624702: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624702 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.130520327528118.transcr...@bugs.debian.org
Bug#626451: linux-image: mremap returns useless pages moving anonymous shared mmap, access causes SIGBUS
On Thu, 2011-05-12 at 00:03 -0500, Michael Joshua Ryan wrote: Package: linux-image Severity: normal one-line summary: mremap yields unusable pages when growing an ANONYMOUS SHARED mmap with MAYMOVE. [...] This problem arose in a discussion in comp.unix.programmer which began with the message: 6e42b7e2-8f29-4c41-98eb-3caa4108f...@m10g2000yqd.googlegroups.com or http://groups.google.com/group/comp.unix.programmer/browse_thread/thread/9a8c963aedc91ca2# I can be contacted at mijo...@yahoo.com or in the newsgroup thread. Please raise this on LKML and cc the bug address 626...@bugs.debian.org. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#624131: linux-image-2.6.39-rc4-686-pae: Can somewhat reliably produce kernel panic in btrfs code
Processing commands for cont...@bugs.debian.org: reassign 624131 linux-2.6 Bug #624131 [linux-image-2.6.39-rc4-686-pae] linux-image-2.6.39-rc4-686-pae: Can somewhat reliably produce kernel panic in btrfs code Warning: Unknown package 'linux-image-2.6.39-rc4-686-pae' Bug reassigned from package 'linux-image-2.6.39-rc4-686-pae' to 'linux-2.6'. Bug No longer marked as found in versions linux-2.6/2.6.39~rc4-1~experimental.1. -- Stopping processing here. Please contact me if you need assistance. -- 624131: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624131 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.13052067597358.transcr...@bugs.debian.org
Bug#603858: Mount options for proc conflict with /etc/fstab breaking /etc/init.d/mountall.sh
Ben Hutchings b...@decadent.org.uk writes: On Wed, May 11, 2011 at 05:40:52PM +0100, rleigh wrote: [...] The fix for this is straightforward: by making initramfs-tools use the same options as initscripts and any additional user entries in /etc/fstab (which will naturally use the same options as the scripts in order to be functional), mount failures are prevented and existing user configuration is preserved and functional. How is that supposed to work when initramfs-tools mounts directories before /etc/fstab is accessible? Ben. The quick way is to just fix the hardcoded name to match what everything else uses. For the more flexible way the /etc/fstab is accessible when the initramfs is generated. Access it then. That means it still breaks when the user changes the entry or adds an incompatible entry without generating a new initaramfs but that can't be helped. MfG Goswin -- 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/87r583gbm0.fsf@frosties.localnet
Bug#590105: debian arm lsproduo nas
hi debian and pals (benj+anton) Can you link the related opened bugs ? I also own a LS-WTGL/R1 aka LSPRO duo that one has 2 usb ports and 2 SATA disks which can be configured as RAID0 or RAID1 I used debian in chroot for years now, until it was screwed (maybe a a bad chroot / ) Also there are some debian ports known as freespire ... I wish I can install debian ove If it helps I collected various infos at : http://rzr.online.fr/q/raid I can provide more ... ps: http://merkel.debian.org/~tbm/tmp/kernel/ls-wsgl/ is down .. -- 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/20110512182151.1c0ca...@nrv.homelinux.org
[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 #624549 (http://bugs.debian.org/624549) # * https://bugs.freedesktop.org/show_bug.cgi?id=37040 # * remote status changed: (?) - NEW usertags 624549 + status-NEW # remote status report for #624549 (http://bugs.debian.org/624549) # * https://bugs.freedesktop.org/show_bug.cgi?id=37040 # * remote status changed: (?) - NEW usertags 624549 + status-NEW 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/20110512163807.7047.5409.btsl...@busoni.debian.org
Bug#603858: Mount options for proc conflict with /etc/fstab breaking /etc/init.d/mountall.sh
On Thu, May 12, 2011 at 05:52:23PM +0200, Goswin von Brederlow wrote: Ben Hutchings b...@decadent.org.uk writes: On Wed, May 11, 2011 at 05:40:52PM +0100, rleigh wrote: [...] The fix for this is straightforward: by making initramfs-tools use the same options as initscripts and any additional user entries in /etc/fstab (which will naturally use the same options as the scripts in order to be functional), mount failures are prevented and existing user configuration is preserved and functional. How is that supposed to work when initramfs-tools mounts directories before /etc/fstab is accessible? Ben. The quick way is to just fix the hardcoded name to match what everything else uses. What, in this context, is everything else? At this point in time, initscripts is installed on every Debian system out there. As a result, any customised fstab files will /have/ to use the same names as those in the initscripts unless you edit both /etc/init.d/mount* /and/ fstab. So unless you've taken extraordinary measures, the hardcoded policy /is/ what is in use, and when it comes to changing it we do need to bear in mind that all of the filesystems in question could be in /etc/fstab and if we change it, we break things. Consider the breakage that would result on upgrades, for example. Now, of all the filesystems, only /proc is in /etc/fstab by default, so it's less risky to alter the others, particularly the newer additions such as /run. For the more flexible way the /etc/fstab is accessible when the initramfs is generated. Access it then. That means it still breaks when the user changes the entry or adds an incompatible entry without generating a new initaramfs but that can't be helped. This is getting far too complex. Ensuring that all the names are consistent fixes the immediate problem which you reported. The actual problem is that mount (rightly) checks mnt_fsname when it checks if a filesystem is already mounted; if they differ, they aren't the same filesystem. /However/, when it comes to special filesystems which don't have a block device as a backing store, the name /might/ be irrelevant--proc is proc, no matter where you mount it, and the same applies to devpts and sysfs. Maybe the real solution here is that mount should disregard different mnt_fsname for these special kernel filesystems. tmpfs filesystems are different; here they /do/ differ in the sense that /run, /run/lock, /lib/init/rw etc. /are/ separate unique instances of tmpfs. Here, it might make sense to give them a name other than none or tmpfs in order to distinguish between them--that is to say, the tmpfs instance, rather than the mountpoint. So names such as run, runlock, would provide a unique key for /etc/fstab in addition to the mountpoint. But this is mostly cosmetic, and if we do make such a change we'll need to ensure that it's coordinated between initscripts and initramfs-tools. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/ `-GPG Public Key: 0x25BFB848 Please GPG sign your mail. signature.asc Description: Digital signature
Bug#603858: Mount options for proc conflict with /etc/fstab breaking /etc/init.d/mountall.sh
rleigh rle...@codelibre.net writes: On Thu, May 12, 2011 at 05:52:23PM +0200, Goswin von Brederlow wrote: Ben Hutchings b...@decadent.org.uk writes: On Wed, May 11, 2011 at 05:40:52PM +0100, rleigh wrote: [...] The fix for this is straightforward: by making initramfs-tools use the same options as initscripts and any additional user entries in /etc/fstab (which will naturally use the same options as the scripts in order to be functional), mount failures are prevented and existing user configuration is preserved and functional. How is that supposed to work when initramfs-tools mounts directories before /etc/fstab is accessible? Ben. The quick way is to just fix the hardcoded name to match what everything else uses. What, in this context, is everything else? The entry historically used in /etc/fstab, the initscripts, the Debian Installer (which puts the initial entry into /etc/fstab). The only thing that uses a different device is intramfs. At this point in time, initscripts is installed on every Debian system out there. As a result, any customised fstab files will /have/ to use the same names as those in the initscripts unless you edit both /etc/init.d/mount* /and/ fstab. So unless you've taken extraordinary measures, the hardcoded policy /is/ what is in use, and when it comes to changing it we do need to bear in mind that all of the filesystems in question could be in /etc/fstab and if we change it, we break things. Consider the breakage that would result on upgrades, for example. Now, of all the filesystems, only /proc is in /etc/fstab by default, so it's less risky to alter the others, particularly the newer additions such as /run. And /proc is what I was concerned about. Although I do have /sys in there too on most systems. For the more flexible way the /etc/fstab is accessible when the initramfs is generated. Access it then. That means it still breaks when the user changes the entry or adds an incompatible entry without generating a new initaramfs but that can't be helped. This is getting far too complex. Ensuring that all the names are consistent fixes the immediate problem which you reported. Indeed. We can expect a well formed entry in /etc/fstab. There is no good reason why the user would want to change the pseudo device used there. It is enough if initramfs just uses the same device name as everything else expects. The actual problem is that mount (rightly) checks mnt_fsname when it checks if a filesystem is already mounted; if they differ, they aren't the same filesystem. /However/, when it comes to special filesystems which don't have a block device as a backing store, the name /might/ be irrelevant--proc is proc, no matter where you mount it, and the same applies to devpts and sysfs. Maybe the real solution here is that mount should disregard different mnt_fsname for these special kernel filesystems. Having mount ignore the device name when it is a pseudo device sounds feasable. I still would like all packages to use the same device name just for consistencies sake. Also mount might not be the only thing comparing /etc/fstab to /proc/mounts. tmpfs filesystems are different; here they /do/ differ in the sense that /run, /run/lock, /lib/init/rw etc. /are/ separate unique instances of tmpfs. Here, it might make sense to give them a name other than none or tmpfs in order to distinguish between them--that is to say, the tmpfs instance, rather than the mountpoint. So names such as run, runlock, would provide a unique key for /etc/fstab in addition to the mountpoint. But this is mostly cosmetic, and if we do make such a change we'll need to ensure that it's coordinated between initscripts and initramfs-tools. It really doesn't matter what it is as long as it is consitent. Given that /run and /run/lock aren't yet in use in Debian now would be the time to pick a name and then stick with it. Using run and runlock sounds good, go with that. Since /run and /run/lock don't usualy have fstab entries it shouldn't be a problem to change the name for those that have the experimental initscripts installed or for a transition period when initscritps and initramfs disagree on the name. So I don't think any depends/breaks should be needed. MfG Goswin -- 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/8762pfhhm9.fsf@frosties.localnet
Bug#603858: Mount options for proc conflict with /etc/fstab breaking /etc/init.d/mountall.sh
On Thu, May 12, 2011 at 08:57:18PM +0200, Goswin von Brederlow wrote: rleigh rle...@codelibre.net writes: [...] tmpfs filesystems are different; here they /do/ differ in the sense that /run, /run/lock, /lib/init/rw etc. /are/ separate unique instances of tmpfs. Here, it might make sense to give them a name other than none or tmpfs in order to distinguish between them--that is to say, the tmpfs instance, rather than the mountpoint. So names such as run, runlock, would provide a unique key for /etc/fstab in addition to the mountpoint. But this is mostly cosmetic, and if we do make such a change we'll need to ensure that it's coordinated between initscripts and initramfs-tools. It really doesn't matter what it is as long as it is consitent. Given that /run and /run/lock aren't yet in use in Debian now would be the time to pick a name and then stick with it. Using run and runlock sounds good, go with that. [...] It does matter, as this is not just a matter for initramfs-tools and initscripts. We also need to agree with systemd and that is cross- distribution. 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/20110512192754.gr2...@decadent.org.uk
Bug#580661: bug can be marked as close, with arrival of 2.6.38
On Mon, Feb 28, 2011 at 08:19:43AM +0100, Gijs Hillenius wrote: I think this bug can be marked closed? KMS will work, once kernel 2.6.38 is installed? See also bug #614566. 2.6.38 is available in testing, did you verify that it fixes your problem? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110512200017.ga21...@inutil.org
Bug#515172: marked as done ([linux-image-2.6-amd64] system briefly lockup with messages: CE: hpet increasing min_delta_ns to 15000 nsec)
Your message dated Thu, 12 May 2011 22:00:48 +0200 with message-id 20110512200048.ge21...@inutil.org and subject line Re: [linux-image-2.6-amd64] system briefly lockup with messages: CE: hpet increasing min_delta_ns to 15000 nsec has caused the Debian Bug report #515172, regarding [linux-image-2.6-amd64] system briefly lockup with messages: CE: hpet increasing min_delta_ns to 15000 nsec 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.) -- 515172: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=515172 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6-amd64 Version: 2.6.26-13 Severity: important --- Please enter the report below this line. --- i have these lockup issues while using kde 4.2 on Debian Sid + 2.6.26 AMD64 + nvidia 180.22 Processor 2x Intel(R) Core(TM)2 Duo CPU P7350 @ 2.00GHz some times i get a message from kde that it is disabling compositing for things to work properly. but not all the times. see my laptop hardware list: http://wiki.debian.org/InstallingDebianOn/HP/Pavilion_dv7 /var/log/messages: 2009-02-12 10:49:57 CE hpet increasing min_delta_ns to 22500 nsec 2009-02-12 10:57:51 CE hpet increasing min_delta_ns to 33750 nsec 2009-02-12 11:28:25 CE hpet increasing min_delta_ns to 50624 nsec please see already reported bug at ubuntu's bugzilla: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/270798 --- System information. --- Architecture: amd64 Kernel: Linux 2.6.26-1-amd64 Debian Release: 5.0 500 unstablewww.debian-multimedia.org 500 unstablesnapshots.ekiga.net 500 unstablemirror.isoc.org.il 500 testing security.debian.org 1 experimentalmirror.isoc.org.il --- Package information. --- Depends (Version) | Installed =-+-=== linux-image-2.6.26-1-amd64| 2.6.26-13 ---End Message--- ---BeginMessage--- On Sun, May 02, 2010 at 08:48:45PM +0200, Moritz Muehlenhoff wrote: tags 515172 moreinfo thanks On Sat, Feb 14, 2009 at 12:28:59PM +0200, Nadav Kavalerchik wrote: Package: linux-image-2.6-amd64 Version: 2.6.26-13 Severity: important --- Please enter the report below this line. --- i have these lockup issues while using kde 4.2 on Debian Sid + 2.6.26 AMD64 + nvidia 180.22 Processor 2x Intel(R) Core(TM)2 Duo CPU P7350 @ 2.00GHz some times i get a message from kde that it is disabling compositing for things to work properly. but not all the times. see my laptop hardware list: http://wiki.debian.org/InstallingDebianOn/HP/Pavilion_dv7 /var/log/messages: 2009-02-12 10:49:57 CE hpet increasing min_delta_ns to 22500 nsec 2009-02-12 10:57:51 CE hpet increasing min_delta_ns to 33750 nsec 2009-02-12 11:28:25 CE hpet increasing min_delta_ns to 50624 nsec Hi, Sorry for the late followup. The next release of Debian (6.0, code name Squeeze) will be based on 2.6.32. Please test the current 2.6.32 from unstable/testing and tell us whether the problem persists. If so, we should report it upstream to the kernel.org developers. The 2.6.32 kernel is available from packages.debian.org and can be installed in both Debian stable, testing and unstable installations. No further feedback, closing the bug. Cheers, Moritz ---End Message---
Bug#579830: marked as done (linux-image-2.6.32-4-amd64: Session dying after a few seconds when using nouveau)
Your message dated Thu, 12 May 2011 22:00:34 +0200 with message-id 20110512200034.gc21...@inutil.org and subject line Re: Bug#579830: linux-image-2.6.32-4-amd64: Session dying after a few, seconds when using nouveau has caused the Debian Bug report #579830, regarding linux-image-2.6.32-4-amd64: Session dying after a few seconds when using nouveau 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.) -- 579830: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=579830 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-11 Severity: important This is a regression from 2.6.32-10. I have gdm set to autostart my session and with 2.6.32-11 the session dies after a few seconds and I'm brought back to the gdm login screen. Reverting the kernel to 2.6.32-10 fixes the issue. Using 2.6.32-11 with nv works fine too. Please tell me if you need me to attach any additional information. Thank you, Jérôme -- Package-specific info: ** Version: Linux version 2.6.32-4-amd64 (Debian 2.6.32-11) (m...@debian.org) (gcc version 4.3.4 (Debian 4.3.4-8) ) #1 SMP Mon Apr 5 21:14:10 UTC 2010 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-4-amd64 root=UUID=27abb9d8-db41-43c9-a475-c6edbe1d00a1 ro quiet ** Not tainted ** Kernel log: [7.002691] name_count maxed, losing inode data: dev=00:07, inode=4682 [7.002693] name_count maxed, losing inode data: dev=00:07, inode=4821 [7.002696] name_count maxed, losing inode data: dev=00:07, inode=4821 [7.002701] name_count maxed, losing inode data: dev=00:07, inode=4821 [7.002704] name_count maxed, losing inode data: dev=00:07, inode=4821 [7.002706] name_count maxed, losing inode data: dev=00:07, inode=4682 [7.002709] name_count maxed, losing inode data: dev=00:07, inode=4826 [7.002711] name_count maxed, losing inode data: dev=00:07, inode=4826 [7.002716] name_count maxed, losing inode data: dev=00:07, inode=4826 [7.002718] name_count maxed, losing inode data: dev=00:07, inode=4826 [7.002721] name_count maxed, losing inode data: dev=00:07, inode=4682 [7.002727] name_count maxed, losing inode data: dev=00:07, inode=4831 [7.002730] name_count maxed, losing inode data: dev=00:07, inode=4831 [7.002737] name_count maxed, losing inode data: dev=00:07, inode=4831 [7.002739] name_count maxed, losing inode data: dev=00:07, inode=4831 [7.010442] EXT4-fs (sdb1): mounted filesystem with ordered data mode [7.648054] fuse init (API version 7.13) [9.564384] lp: driver loaded but no devices found [9.594611] ppdev: user-space parallel port driver [ 13.889146] iwl3945 :06:00.0: firmware: requesting iwlwifi-3945-2.ucode [ 14.035593] iwl3945 :06:00.0: loaded firmware version 15.32.2.9 [ 14.111216] Registered led device: iwl-phy0::radio [ 14.111342] Registered led device: iwl-phy0::assoc [ 14.111382] Registered led device: iwl-phy0::RX [ 14.112152] Registered led device: iwl-phy0::TX [ 14.122471] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 14.133555] r8169: eth0: link down [ 14.133997] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 17.788158] [drm] Initialized drm 1.1.0 20060810 [ 18.026830] nouveau :01:00.0: power state changed by ACPI to D0 [ 18.026843] nouveau :01:00.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [ 18.026850] nouveau :01:00.0: setting latency timer to 64 [ 18.028701] name_count maxed, losing inode data: dev=00:05, inode=6095 [ 18.028705] name_count maxed, losing inode data: dev=00:05, inode=6095 [ 18.028710] name_count maxed, losing inode data: dev=00:05, inode=6095 [ 18.028772] name_count maxed, losing inode data: dev=00:07, inode=6068 [ 18.028776] name_count maxed, losing inode data: dev=00:07, inode=6097 [ 18.028780] name_count maxed, losing inode data: dev=00:07, inode=6097 [ 18.028784] name_count maxed, losing inode data: dev=00:07, inode=6097 [ 18.028787] name_count maxed, losing inode data: dev=00:07, inode=6097 [ 18.028790] name_count maxed, losing inode data: dev=00:07, inode=6097 [ 18.028799] name_count maxed, losing inode data: dev=00:07, inode=6097 [ 18.028802] name_count maxed, losing inode data: dev=00:07, inode=6097 [ 18.028805] name_count maxed, losing inode data: dev=00:07, inode=6097 [ 18.028815] name_count maxed, losing inode data: dev=00:05, inode=6095 [ 18.028819] name_count maxed, losing inode data: dev=00:05, inode=6095 [ 18.029627] [drm] nouveau :01:00.0: failed to evaluate _DSM: 5 [ 18.030147] [drm] nouveau :01:00.0: Detected an NV50 generation card (0x086500a2) [
Bug#603631: marked as done (smbfs: smbmount renders system when logged on with unprivileged user. Even reboot is not possible)
Your message dated Thu, 12 May 2011 22:00:24 +0200 with message-id 20110512200024.gb21...@inutil.org and subject line Re: Bug#603631: smbfs: smbmount renders system when logged on with unprivileged user. Even reboot is not possible has caused the Debian Bug report #603631, regarding smbfs: smbmount renders system when logged on with unprivileged user. Even reboot is not possible 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.) -- 603631: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603631 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: smbfs Version: 2:3.2.5-4lenny13 Severity: critical Tags: security Justification: breaks unrelated software 1. sudo apt-get install smbfs 2. sudo /usr/sbin/adduser nagios 3. sudo /usr/sbin/usermod -a -G nagios nagios 4. while true; do mkdir -p /tmp/mnt_10.0.0.2/test$ smbmount //10.0.0.2/test$ /tmp/mnt_10.0.0.2/test$ -o password=asdfasdf,uid=nagios,gid=nagios,ro /dev/null done 5. wait approximately 10 seconds 6. Strg+C 7. ps aux (You will see lots of processes called /sbin/mount.cifs.) 8. you can.t reboot system Solution is to install linux-image-amd64 (=2.6.32+25) from deb http://www.backports.org/debian lenny-backports main contrib non-free -- System Information: Debian Release: 5.0.6 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-2-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages smbfs depends on: ii libc6 2.7-18lenny6 GNU C Library: Shared libraries ii libcomerr2 1.41.3-1 common error description library ii libkeyutils11.2-9Linux Key Management Utilities (li ii libkrb531.6.dfsg.4~beta1-5lenny4 MIT Kerberos runtime libraries ii libldap-2.4-2 2.4.11-1+lenny2 OpenLDAP libraries ii libpopt01.14-4 lib for parsing cmdline parameters ii libtalloc1 1.2.0~git20080616-1 hierarchical pool based memory all ii libwbclient02:3.2.5-4lenny13 client library for interfacing wit ii netbase 4.34 Basic TCP/IP networking system ii samba-common2:3.2.5-4lenny13 Samba common files used by both th smbfs recommends no packages. Versions of packages smbfs suggests: pn smbclient none (no description available) -- no debconf information ---End Message--- ---BeginMessage--- Version: 2.6.32-25 On Thu, Nov 25, 2010 at 11:51:02PM -0600, Steve Langasek wrote: reassign 603631 linux-2.6 severity 603631 important thanks On Mon, Nov 15, 2010 at 05:17:13PM +0100, christianha wrote: Package: smbfs Version: 2:3.2.5-4lenny13 Severity: critical Tags: security Justification: breaks unrelated software 1. sudo apt-get install smbfs 2. sudo /usr/sbin/adduser nagios 3. sudo /usr/sbin/usermod -a -G nagios nagios 4. while true; do mkdir -p /tmp/mnt_10.0.0.2/test$ smbmount //10.0.0.2/test$ /tmp/mnt_10.0.0.2/test$ -o password=asdfasdf,uid=nagios,gid=nagios,ro /dev/null done 5. wait approximately 10 seconds 6. Strg+C 7. ps aux (You will see lots of processes called /sbin/mount.cifs.) 8. you can.t reboot system This last indicates a kernel problem, not a problem in the smbfs package. Solution is to install linux-image-amd64 (=2.6.32+25) from deb http://www.backports.org/debian lenny-backports main contrib non-free And this confirms it. Marking the Squeeze kernel as fixed. Cheers, Moritz ---End Message---
Bug#626427: linux-image-2.6.38-2-686: Horrible Time Skew, Eventual Near-zero Responsiveness
On 11 May 2011, at 23:54, maximilian attems wrote: On Wed, May 11, 2011 at 10:55:13PM +0100, Sabahattin Gucukoglu wrote: Package: linux-2.6 Version: 2.6.38-5 Severity: important (reportbug script died, hope you've got everything.) The machine runs with *HORRIBLE* clock drift (see text). Eventually, the system will slow right down, so that new processes or threads will not start. It *seems* to be related to the use of BRLTTY. See this thread: http://www.mail-archive.com/brltty@mielke.cc/msg05352.html And, yes, it's annoying having to hard-reboot the box every so often. It would seem that after some period of time, touching my display or the physical console triggers the lockup. I don't think this is a coincidence, even though on the surface there are two different problems. The kernel upgrade was sufficient to begin these issues. can you try newer 2.6.39-rcX from experimental, is it fixed there? Done (RC6). No. :-( Cheers, Sabahattin -- 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/0e6448e2-912d-4096-8bfa-be6fa8b85...@users.sourceforge.net
Bug#626427: linux-image-2.6.38-2-686: Horrible Time Skew, Eventual Near-zero Responsiveness
On Thu, May 12, 2011 at 09:11:30PM +0100, Sabahattin Gucukoglu wrote: On 11 May 2011, at 23:54, maximilian attems wrote: On Wed, May 11, 2011 at 10:55:13PM +0100, Sabahattin Gucukoglu wrote: Package: linux-2.6 Version: 2.6.38-5 Severity: important (reportbug script died, hope you've got everything.) The machine runs with *HORRIBLE* clock drift (see text). Eventually, the system will slow right down, so that new processes or threads will not start. It *seems* to be related to the use of BRLTTY. See this thread: http://www.mail-archive.com/brltty@mielke.cc/msg05352.html And, yes, it's annoying having to hard-reboot the box every so often. It would seem that after some period of time, touching my display or the physical console triggers the lockup. I don't think this is a coincidence, even though on the surface there are two different problems. The kernel upgrade was sufficient to begin these issues. can you try newer 2.6.39-rcX from experimental, is it fixed there? Done (RC6). No. :-( did it ever work? if yes please how correct boot dmesg of the working linux-2.6. if no please report upstream to the brltty upstream. thanks -- maks -- 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/20110512211504.gd3...@vostochny.stro.at
Processed: tagging 626427
Processing commands for cont...@bugs.debian.org: tags 626427 + moreinfo Bug #626427 [linux-2.6] linux-image-2.6.38-2-686: Horrible Time Skew, Eventual Near-zero Responsiveness Ignoring request to alter tags of bug #626427 to the same tags previously set thanks Stopping processing here. Please contact me if you need assistance. -- 626427: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626427 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.13052353305308.transcr...@bugs.debian.org
Bug#626427: linux-image-2.6.38-2-686: Horrible Time Skew, Eventual Near-zero Responsiveness
On Thu, May 12, 2011 at 09:15:04PM +, maximilian attems wrote: On Thu, May 12, 2011 at 09:11:30PM +0100, Sabahattin Gucukoglu wrote: On 11 May 2011, at 23:54, maximilian attems wrote: On Wed, May 11, 2011 at 10:55:13PM +0100, Sabahattin Gucukoglu wrote: Package: linux-2.6 Version: 2.6.38-5 Severity: important (reportbug script died, hope you've got everything.) The machine runs with *HORRIBLE* clock drift (see text). Eventually, the system will slow right down, so that new processes or threads will not start. It *seems* to be related to the use of BRLTTY. See this thread: http://www.mail-archive.com/brltty@mielke.cc/msg05352.html And, yes, it's annoying having to hard-reboot the box every so often. It would seem that after some period of time, touching my display or the physical console triggers the lockup. I don't think this is a coincidence, even though on the surface there are two different problems. The kernel upgrade was sufficient to begin these issues. can you try newer 2.6.39-rcX from experimental, is it fixed there? Done (RC6). No. :-( did it ever work? if yes please how correct boot dmesg of the working linux-2.6. if no please report upstream to the brltty upstream. Max, brltty is a userland component. I think this has to be a kernel bug (or a BIOS bug that the kernel has to work around). 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/20110512213017.gs2...@decadent.org.uk
Bug#625914: [Bridge] Bug#625914: linux-image-2.6.38-2-amd64: bridging is not interacting well with multicast in 2.6.38-4
From: Noah Meyerhans no...@debian.org Date: Tue, 10 May 2011 16:35:40 -0700 On Tue, May 10, 2011 at 03:11:00PM -0700, Stephen Hemminger wrote: There were two more follow on commits in stable related to this. I recommend merging 2.6.38.6 which includes these. The problem still exists in the current 2.6.38.6. Backing out 5f1c356a still solves the problem there. I have not yet tried anything outside the stable-2.6.38.y tree, but it seems like these same changes are present there, and it's unlikely that other releases will work any better. So the issue is that if we back out that change, we get crashes. Aparently there is a code path where whatever is existing in the SKB ip options block matters, and needs to be maintained. Someone needs to audit all of this and figure out how to fix the problem properly. -- 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/20110512.155916.115945119.da...@davemloft.net
Bug#625914: [Bridge] Bug#625914: linux-image-2.6.38-2-amd64: bridging is not interacting well with multicast in 2.6.38-4
On Thu, 12 May 2011 15:59:16 -0700 (PDT) David Miller da...@davemloft.net wrote: From: Noah Meyerhans no...@debian.org Date: Tue, 10 May 2011 16:35:40 -0700 On Tue, May 10, 2011 at 03:11:00PM -0700, Stephen Hemminger wrote: There were two more follow on commits in stable related to this. I recommend merging 2.6.38.6 which includes these. The problem still exists in the current 2.6.38.6. Backing out 5f1c356a still solves the problem there. I have not yet tried anything outside the stable-2.6.38.y tree, but it seems like these same changes are present there, and it's unlikely that other releases will work any better. So the issue is that if we back out that change, we get crashes. Aparently there is a code path where whatever is existing in the SKB ip options block matters, and needs to be maintained. Someone needs to audit all of this and figure out how to fix the problem properly. -- To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html I suspect tuntap is part of the problem. The skb may not be allocated with enough padding or something like that. No guarantees but will do some investigation. -- -- 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/20110512162810.34b8d55a@nehalam
Bug#625914: [Bridge] Bug#625914: linux-image-2.6.38-2-amd64: bridging is not interacting well with multicast in 2.6.38-4
On Tue, 10 May 2011 16:35:40 -0700
Noah Meyerhans no...@debian.org wrote:
On Tue, May 10, 2011 at 03:11:00PM -0700, Stephen Hemminger wrote:
There were two more follow on commits in stable related to this.
I recommend merging 2.6.38.6 which includes these.
The problem still exists in the current 2.6.38.6. Backing out 5f1c356a
still solves the problem there.
I have not yet tried anything outside the stable-2.6.38.y tree, but it
seems like these same changes are present there, and it's unlikely that
other releases will work any better.
Does this fix the problem? The tap driver allocates an skb and throws
it into the receive path, but the skb does not have the same padding
as normal skb's received.
--- a/drivers/net/tun.c 2011-05-12 16:36:15.231347935 -0700
+++ b/drivers/net/tun.c 2011-05-12 16:36:38.503464573 -0700
@@ -614,7 +614,7 @@ static __inline__ ssize_t tun_get_user(s
}
if ((tun-flags TUN_TYPE_MASK) == TUN_TAP_DEV) {
- align = NET_IP_ALIGN;
+ align = NET_IP_ALIGN + NET_SKB_PAD;
if (unlikely(len ETH_HLEN ||
(gso.hdr_len gso.hdr_len ETH_HLEN)))
return -EINVAL;
--
--
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/20110512164322.45626683@nehalam
Bug#626562: linux-image-2.6.39-rc7: s5h1409/mt2131 read/writereg errors with dvb tuner
found 626562 2.6.38-5 Also, I did install linux 2.6.38-2-amd64 from unstable. This bug is also present in that earlier release. -- 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/20110513013645.ga3...@robocomp.net
Bug#626441: general: When first logging in, usb wireless keyboard/mouse is not working
On Fri, 2011-05-13 at 01:10 +, Peter . wrote: Attached dmesg output. More info about the bug I mentioned here - https://bugzilla.redhat.com/show_bug.cgi?id=582642 Probably a different bug. Not seeing where that workaround to prevent usb devices to be recognized as audio cards is, but I'm sure I found that while trying to get GeForce220 hdmi sound with a workaround via manually adding snd_hda_intel to /etc/modules One other probably not related note is that I blacklist nouveau to enable x to work properly on my monitor - it was still occurring with vesa though. Let me know if you need any other information - I'm happy to help any way I can as time allows. I don't see any errors in the kernel log. Seems like the USB devices are detected straight away. Did these devices work any better with any earlier kernel version? Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#624131: marked as done (linux-image-2.6.39-rc4-686-pae: Can somewhat reliably produce kernel panic in btrfs code)
Your message dated Fri, 13 May 2011 05:07:42 +0100 with message-id 1305259662.4065.406.camel@localhost and subject line Re: Bug#624131: linux-image-2.6.39-rc4-686-pae: Can somewhat reliably produce kernel panic in btrfs code has caused the Debian Bug report #624131, regarding linux-image-2.6.39-rc4-686-pae: Can somewhat reliably produce kernel panic in btrfs code 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.) -- 624131: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624131 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.39-rc4-686-pae Version: 2.6.39~rc4-1~experimental.1 Severity: normal Tags: experimental By simply stressing the system with some I/O, I can make it crash within seconds. I'm not setting a higher severity because the bug is in an experimental file system in an experimental kernel. Here's the important bits (by my guess) I have on screen from the kernel panic: Bug at fs/btrfs/free-space-cache.c:1246 Bug type: invalid opcode: Kernel not tainted, running on an ASUSTek 1005HAG EIP is at btrfs_add_free_space+0x285/0x39a [btrfs] ---End Message--- ---BeginMessage--- Version: 2.6.39~rc5-1~experimental.1 On Thu, 2011-05-12 at 14:00 +0200, Maik Zumstrull wrote: On Tue, Apr 26, 2011 at 05:59, Ben Hutchings b...@decadent.org.uk wrote: This fix doesn't seem to be in your for-linux branch yet. Please can you ensure that this (or an alternate fix) is included in 2.6.39. It seems to be in. I also haven't noticed panics with rc5/rc6. Just in case you want to close this one. Thanks for letting us know. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part ---End Message---
Re: linux-2.6_2.6.38-5_m68k.changes ACCEPTED
On Thu, 12 May 2011, Geert Uytterhoeven wrote:
On Thu, May 12, 2011 at 09:24, Finn Thain fth...@telegraphics.com.au
wrote:
On Thu, 12 May 2011, Geert Uytterhoeven wrote:
Do we really want to compile wireless on m68k? AFAIK we don't have
any.
http://marc.info/?l=linux-m68km=128628785718187w=2
I suspect this list is also applicable to atari and amiga (?)
Excepting the PS2 mouse I should add. (And is there PCMCIA on
atari/amiga?)
Yeah, I should look into updating the defconfigs again.
Haven't done that anymore since the concept of minimal defconfigs was
introduced, as I'm still a bit worried if I can trust them or not
Fair enough.
(options not mentioned in the minimal defconfig may silently change
their value depending on Kconfig logic; with the full ones I would
immeditaly notice).
One solution is to fix the cruft in the Debian configs and then push those
upstream (that is, after running them through a mainline make oldconfig
to filter out the stuff that Debian's patches have introduced).
The upstream defconfigs aren't really needed by upstream developers except
for smoke testing the build. Downstream configs are useful for that too
and would also be useful to have in the mainline for end users who need to
build mainline kernels (which has been helpful for mac68k driver updates
in the past).
Finn
Gr{oetje,eeting}s,
Geert
Bug#534964: Any updates on this BUG?
On Thu, 2011-05-12 at 11:53 +, maximilian attems wrote: On Wed, May 11, 2011 at 12:08:10PM +, maximilian attems wrote: On Wed, May 11, 2011 at 11:33:31AM +, maximilian attems wrote: On Wed, May 11, 2011 at 04:43:06PM +0530, Balbir Singh wrote: bal...@linux.vnet.ibm.com wrote: Hi, Ben, We've made significant progress in reducing the overhead of memory cgroup subsystem. I'd request you to try it and enable it. If there are some concerns, we could always address them. There are more interesting changes on the way as well. could you point to the relevant commits? so unless this information comes along soon, I'll revert my change. I prepared a patch to make memory cgroups built-in but disabled by default (message #31). The overhead then should be very small, but I still haven't spent the time to measure it. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Re: linux-2.6_2.6.38-5_m68k.changes ACCEPTED
On Thu, 2011-05-12 at 03:36 +0100, Ben Hutchings wrote: [...] warning: (NETFILTER_XT_MATCH_REALM) selects NET_CLS_ROUTE which has unmet direct dependencies (NET NET_SCHED) The dependencies for NETFILTER_XT_MATCH_REALM should be fixed. But why is NET_SCHED disabled on m68k, anyway? Fixed in 2.6.39. [...] drivers/char/tpm/tpm_tis.c:96: warning: 'is_itpm' defined but not used The definition of this function should be conditional on CONFIG_PNP. Anyway, I don't think the TPM drivers could be used on most non-x86 architectures. We should just disable them. Disabled on trunk. [...] CC [M] drivers/net/zorro8390.o drivers/net/lib8390.c:256: warning: '__ei_tx_timeout' defined but not used drivers/net/lib8390.c:302: warning: '__ei_start_xmit' defined but not used drivers/net/lib8390.c:526: warning: '__ei_poll' defined but not used drivers/net/lib8390.c:879: warning: '__ei_get_stats' defined but not used drivers/net/lib8390.c:981: warning: '__ei_set_multicast_list' defined but not used drivers/net/lib8390.c:1016: warning: 'alloc_ei_netdev' defined but not used It looks like zorro8390.c should be using these functions instead of the corresponding functions without the double-underscore prefixes. At the moment it's using some functions built from the #included lib8390.c using the special definition of EI_SHIFT (from zorro8390.c), and some functions exported from the 8390 module, which are built with the default definition of EI_SHIFT (from 8390.h). CC [M] drivers/net/hydra.o drivers/net/lib8390.c:256: warning: '__ei_tx_timeout' defined but not used drivers/net/lib8390.c:302: warning: '__ei_start_xmit' defined but not used drivers/net/lib8390.c:526: warning: '__ei_poll' defined but not used drivers/net/lib8390.c:879: warning: '__ei_get_stats' defined but not used drivers/net/lib8390.c:981: warning: '__ei_set_multicast_list' defined but not used drivers/net/lib8390.c:1016: warning: 'alloc_ei_netdev' defined but not used Similar issue in hydra.c. Both fixed by Geert in net-2.6 and cc'd to stable. [...] drivers/video/mb862xx/mb862xxfb.c:326: warning: 'mb862xxfb_init_fbinfo' defined but not used drivers/video/mb862xx/mb862xxfb.c:464: warning: 'dev_attr_dispregs' defined but not used Bug in the Kconfig. This driver should not be built on non-PCI machines. [...] I've sent a patch to the video maintainer. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Processed: tagging 596626
Processing commands for cont...@bugs.debian.org:
# Automatically generated email from bts, devscripts version 2.10.35lenny7
tags 596626 + pending
Bug #596626 {Done: maximilian attems m...@stro.at} [linux-2.6]
linux-image-2.6: Please support Linksys WUSB600N v2 WiFi USB stick
Added tag(s) pending.
End of message, stopping processing here.
Please contact me if you need assistance.
--
596626: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596626
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.130526231224169.transcr...@bugs.debian.org
Bug#596626: [gsimm...@gsimmons.org: Bug#596626: Please support Linksys WUSB600N v2 WiFi USB stick]
On Wed, 2011-05-11 at 09:25 -0700, Walter Goldens wrote: As mentioned by Jan, the device contains a RT3572 chipset. Its entry could moved into the section for known RT35XX devices (i.e. #ifdef CONFIG_RT2800USB_RT35XX) as an alternative. Geoff This has already been done: http://git.kernel.org/?p=linux/kernel/git/ivd/rt2x00.git;a=commitdiff;h=ce2919c9fffe2aa52f9c3e327176d03764dbf9b5 That's all very well, but that isn't going to get into a stable release for another 3 months! Device ID updates that don't require new supporting code should be sent upstream straight away (and cc'd to sta...@kernel.org). I've cherry-picked this and the other two updates in rt2800usb that aren't in Linus's tree, but that doesn't help the users of other distributions that would benefit from them. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#625914: [Bridge] Bug#625914: linux-image-2.6.38-2-amd64: bridging is not interacting well with multicast in 2.6.38-4
On Thu, May 12, 2011 at 04:43:22PM -0700, Stephen Hemminger wrote:
There were two more follow on commits in stable related to this.
I recommend merging 2.6.38.6 which includes these.
The problem still exists in the current 2.6.38.6. Backing out 5f1c356a
still solves the problem there.
I have not yet tried anything outside the stable-2.6.38.y tree, but it
seems like these same changes are present there, and it's unlikely that
other releases will work any better.
Does this fix the problem? The tap driver allocates an skb and throws
it into the receive path, but the skb does not have the same padding
as normal skb's received.
--- a/drivers/net/tun.c 2011-05-12 16:36:15.231347935 -0700
+++ b/drivers/net/tun.c 2011-05-12 16:36:38.503464573 -0700
@@ -614,7 +614,7 @@ static __inline__ ssize_t tun_get_user(s
}
if ((tun-flags TUN_TYPE_MASK) == TUN_TAP_DEV) {
- align = NET_IP_ALIGN;
+ align = NET_IP_ALIGN + NET_SKB_PAD;
if (unlikely(len ETH_HLEN ||
(gso.hdr_len gso.hdr_len ETH_HLEN)))
return -EINVAL;
Sorry, this does not fix the problem.
noah
signature.asc
Description: Digital signature
Re: linux-2.6_2.6.38-5_m68k.changes ACCEPTED
On Fri, May 13, 2011 at 06:13, Finn Thain fth...@telegraphics.com.au wrote:
On Thu, 12 May 2011, Geert Uytterhoeven wrote:
On Thu, May 12, 2011 at 09:24, Finn Thain fth...@telegraphics.com.au
wrote:
On Thu, 12 May 2011, Geert Uytterhoeven wrote:
Do we really want to compile wireless on m68k? AFAIK we don't have
any.
http://marc.info/?l=linux-m68km=128628785718187w=2
I suspect this list is also applicable to atari and amiga (?)
Excepting the PS2 mouse I should add. (And is there PCMCIA on
atari/amiga?)
Yes, so far used only by the apne network driver.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say programmer or something like that.
-- Linus Torvalds
--
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/banlktinjt3njr3cpmzbkvhrduw6zczo...@mail.gmail.com
