Bug#621737: linux-image-2.6.32-5-powerpc: ath ignores regulatory domain setting
On 04/10/11 00:55, Ben Hutchings wrote: On Fri, 2011-04-08 at 13:39 +0100, Anton Ivanov wrote: Package: linux-2.6 Version: 2.6.32-30 Severity: minor ath driver ignores reg domain setting passed via cfg80211 and uses one from EEPROM instead. This setting a lot of cheap cards is CN. As a result the reg domain is set incorrectly (and for some countries illegally). [...] What do you mean by 'passed via cfg80211'? Are you setting the ieee80211_regdom module parameter? Ben. Yes. No effect. ath still reads from eeprom. -- Understanding is a three-edged sword: your side, their side, and the truth. --Kosh Naranek A. R. Ivanov E-mail: aiva...@sigsegv.cx WWW: http://www.sigsegv.cx/ pub 1024D/DDE5E715 2002-03-03 Anton R. Ivanovai...@sigsegv.cx Fingerprint: C824 CBD7 EE4B D7F8 5331 89D5 FCDA 572E DDE5 E715 -- 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/4da14eb0.10...@sigsegv.cx
Bug#622085: marked as done (nfs-common: nfs mount inpossible)
Your message dated Sun, 10 Apr 2011 09:43:15 +0200 with message-id 4da15f93.9010...@debian.org and subject line Re: nfs-common: nfs mount inpossible has caused the Debian Bug report #622085, regarding nfs-common: nfs mount inpossible 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.) -- 622085: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622085 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: nfs-common Version: 1:1.2.3-1 Severity: normal uname -a Linux jive 2.6.32-5-amd64 #1 SMP Mon Mar 7 21:35:22 UTC 2011 x86_64 GNU/Linux -- Package-specific info: -- rpcinfo -- program vers proto port 102 tcp111 portmapper 102 udp111 portmapper -- /etc/default/nfs-common -- NEED_STATD= STATDOPTS= NEED_IDMAPD= NEED_GSSD= -- /etc/idmapd.conf -- [General] Verbosity = 0 Pipefs-Directory = /var/lib/nfs/rpc_pipefs Domain = localdomain [Mapping] Nobody-User = nobody Nobody-Group = nogroup -- /etc/fstab -- chacha:/data/data nfs ro,auto,vers=3,nolock00 -- /proc/mounts -- nfsd /proc/fs/nfsd nfsd rw,relatime 0 0 -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nfs-common depends on: ii adduser 3.112+nmu2 add and remove users and groups ii initscripts 2.88dsf-13.1scripts for initializing and shutt ii libc62.11.2-11 Embedded GNU C Library: Shared lib ii libcap2 1:2.20-1support for getting/setting POSIX. ii libcomerr2 1.41.12-2 common error description library ii libevent-1.4-2 1.4.13-stable-1 An asynchronous event notification ii libgssapi-krb5-2 1.9+dfsg-1 MIT Kerberos runtime libraries - k ii libgssglue1 0.1-4 mechanism-switch gssapi library ii libk5crypto3 1.9+dfsg-1 MIT Kerberos runtime libraries - C ii libkrb5-31.9+dfsg-1 MIT Kerberos runtime libraries ii libnfsidmap2 0.24-1 An nfs idmapping library ii libtirpc10.2.1-1 transport-independent RPC library ii libwrap0 7.6.q-19Wietse Venema's TCP wrappers libra ii lsb-base 3.2-27 Linux Standard Base 3.2 init scrip ii netbase 4.45Basic TCP/IP networking system ii portmap 6.0.0-3 RPC port mapper ii ucf 3.0025+nmu1 Update Configuration File: preserv Versions of packages nfs-common recommends: ii python2.6.6-12 interactive high-level object-orie nfs-common suggests no packages. Versions of packages nfs-kernel-server depends on: ii libblkid12.17.2-9.1 block device id library ii libc62.11.2-11 Embedded GNU C Library: Shared lib ii libcomerr2 1.41.12-2 common error description library ii libgssapi-krb5-2 1.9+dfsg-1 MIT Kerberos runtime libraries - k ii libgssglue1 0.1-4 mechanism-switch gssapi library ii libk5crypto3 1.9+dfsg-1 MIT Kerberos runtime libraries - C ii libkrb5-31.9+dfsg-1 MIT Kerberos runtime libraries ii libnfsidmap2 0.24-1 An nfs idmapping library ii libtirpc10.2.1-1 transport-independent RPC library ii libwrap0 7.6.q-19Wietse Venema's TCP wrappers libra ii lsb-base 3.2-27 Linux Standard Base 3.2 init scrip ii ucf 3.0025+nmu1 Update Configuration File: preserv -- no debconf information ---End Message--- ---BeginMessage--- Version: 1:1.2.3-2 Hi Please install rpcbind and restart nfs-common and report back if that does not solve it. Cheers Luk ---End Message---
Bug#582212: Sorry, but I believe this bug was more of a misconfiguration.
On Sat, Apr 09, 2011 at 07:46:33PM +0200, Santiago Garcia Mantinan wrote: At least on my case I was blacklisting quite a few kernel modules on my guest of things I didn't want supported to save some memory, in the end it resulted that one of the modules (evdev I believe, I'll check it out for sure as soon as I have access to the machines, but I'm almost sure it was that one) was needed for acpi power button to be routed to the guest's acpid. Yes. Such button presses are reported via the input system in the meantime, not longer via the acpi special handling. So you need evdev. Bastian -- Where there's no emotion, there's no motive for violence. -- Spock, Dagger of the Mind, stardate 2715.1 -- 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/20110410080304.gb28...@wavehammer.waldi.eu.org
Bug#622085: Unusable system
Hi, I have the same problem with nfs-common that is mentioned in several bug reports (#622085, #621918, #562737, #621027). I don't know how much they are connected or which one is the real issue, but the system is definitely unusable since it cannot boot up normally. It hangs on the message Starting NFS common utilities and nothing helps except hardware reset. After the new start system boots up with nfs-common: failed message but next try after power-off and on booting hangs again. So I tried to install rpcbind (and remove portmap) and now nfs-common seems to be working fine - thanks for that tip. I think this is really critical bug and the fix should be delivered to the Wheeze asap or the last update (that caused this situation) should be taken back. It was not easy to detect what is wrong and find this solution. Pavel -- 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/20110410113935.105ca...@atlas.cz
Bug#582212: Sorry, but I believe this bug was more of a misconfiguration.
Hi, evdev is loaded and doesn't matter. I've set up several KVM systems without manual modifications, all the same. The problem is still present with 2.6.32-bpo.5-amd64. Regards, -- .''`. Philipp Huebner debala...@debian.org : :' : pgp fp: 6719 25C5 B8CD E74A 5225 3DF9 E5CA 8C49 25E4 205F `. `'` HP: http://www.debalance.de, Skype: philipp-huebner `- ICQ: 235-524-440, Jabber: der_scha...@jabber.org signature.asc Description: OpenPGP digital signature
Bug#622118: linux-base: [INTL:sk] Slovak po-debconf translation
Package: linux-base Severity: wishlist Tags: l10n patch Version: 3.2 sk.po attached regards -- Slavko http://slavino.sk # Slovak translations for linux-base package # Slovenské preklady pre balÃk linux-base. # Copyright (C) 2011 THE linux-base'S COPYRIGHT HOLDER # This file is distributed under the same license as the linux-base package. # Automatically generated, 2011. # Slavko li...@slavino.sk, 2011. # msgid msgstr Project-Id-Version: linux-base 3.2\n Report-Msgid-Bugs-To: linux-b...@packages.debian.org\n POT-Creation-Date: 2011-03-12 08:45+\n PO-Revision-Date: 2011-04-10 13:15+0200\n Last-Translator: Slavko li...@slavino.sk\n Language-Team: Slovak nomail\n Language: sk\n MIME-Version: 1.0\n Content-Type: text/plain; charset=UTF-8\n Content-Transfer-Encoding: 8bit\n Plural-Forms: nplurals=3; plural=(n==1) ? 0 : (n=2 n=4) ? 1 : 2;\n #. Type: boolean #. Description #: ../templates:2001 msgid Update disk device IDs in system configuration? msgstr AktualizovaÅ¥ ID diskových zariadenà v nastavenà systému? #. Type: boolean #. Description #: ../templates:2001 msgid The new Linux kernel version provides different drivers for some PATA (IDE) controllers. The names of some hard disk, CD-ROM, and tape devices may change. msgstr Nové verzia jadra Linuxu poskytujú iné ovládaÄe niektorých radiÄov PATA (IDE). Mená niektorých pevných diskov, CD-ROM a páskových zariadenà môžu byÅ¥ zmenené. #. Type: boolean #. Description #: ../templates:2001 msgid It is now recommended to identify disk devices in configuration files by label or UUID (unique identifier) rather than by device name, which will work with both old and new kernel versions. msgstr Teraz je odporúÄané udávaÅ¥ diskové zariadenia v konfiguraÄných súboroch pomocou ich menovky alebo UUID (jedineÄný identifikátor) namiesto mena zariadenia, ktoré je funkÄné ako so starými, tak i s novými verziami jadra. #. Type: boolean #. Description #: ../templates:2001 msgid If you choose to not update the system configuration automatically, you must update device IDs yourself before the next system reboot or the system may become unbootable. msgstr Ak si vyberiete neaktualizovaÅ¥ automaticky systémové nastavenie, budete musieÅ¥ aktualizovaÅ¥ ID zariadenà sami, eÅ¡te pred nasledujúcim reÅ¡tartom systému, inak sa systém môže staÅ¥ nezavediteľným. #. Type: boolean #. Description #. Type: boolean #. Description #: ../templates:3001 ../templates:4001 msgid Apply configuration changes to disk device IDs? msgstr PoužiÅ¥ zmeny konfigurácie ID diskových zariadenÃ? #. Type: boolean #. Description #: ../templates:3001 msgid These devices will be assigned UUIDs or labels: msgstr Týmto zariadeniam budú priradené UUID alebo menovky: #. Type: boolean #. Description #. Type: boolean #. Description #: ../templates:3001 ../templates:4001 msgid These configuration files will be updated: msgstr Tieto konfiguraÄné súbory budú aktualizované: #. Type: boolean #. Description #. Type: boolean #. Description #: ../templates:3001 ../templates:4001 msgid The device IDs will be changed as follows: msgstr ID zariadenà budú zmenené takto: #. Type: error #. Description #: ../templates:5001 msgid Configuration files still contain deprecated device names msgstr KonfiguraÄné súbory stále obsahujú zastarané mená zariadenà #. Type: error #. Description #: ../templates:5001 msgid The following configuration files still use some device names that may change when using the new kernel: msgstr Nasledujúce konfiguraÄné súbory stále použÃvajú mená zariadenÃ, ktoré asi bude treba pri použità nového jadra zmeniÅ¥: #. Type: error #. Description #: ../templates:6001 msgid Boot loader configuration check needed msgstr Je potrebná kontrola nastavenia zavádzaÄa #. Type: error #. Description #: ../templates:6001 msgid The boot loader configuration for this system was not recognized. These settings in the configuration may need to be updated: msgstr Konfigurácia zavádzaÄa tohoto systému nebola rozpoznaná. V konfigurácii asi bude treba aktualizovaÅ¥ tieto nastavenia: #. Type: error #. Description #: ../templates:6001 msgid * The root device ID passed as a kernel parameter;\n * The boot device ID used to install and update the boot loader. msgstr * ID koreÅového zariadenia, predávané ako parameter jadra;\n * ID zavádzacieho zariadenia, použitého na inÅ¡taláciu a aktualizáciu zavádzaÄa. #. Type: error #. Description #: ../templates:6001 msgid You should generally identify these devices by UUID or label. However, on MIPS systems the root device must be identified by name. msgstr Tieto zariadenia by ste mali oznaÄovaÅ¥ ich UUID Äi menovkou. Na systémoch MIPS vÅ¡ak musà byÅ¥ koreÅové zariadenie oznaÄené menom. #. Type: error #. Description #: ../templates:8001 msgid Boot loader may need to be upgraded msgstr ZavádzaÄ asi treba aktualizovaÅ¥ #. Type: error #.
Bug#621918: closed by Ben Hutchings b...@decadent.org.uk (Re: Bug#621918: nfs-common: nfs mount inpossible)
On Sun, 10 Apr 2011 03:24:35 + ow...@bugs.debian.org (Debian Bug Tracking System) wrote: You need to install rpcbind and the above version of nfs-common. Thanks, Done that, but the problem still exists. It is not so critical, hence I use sshfs as a backup solution. ii nfs-common 1:1.2.3-1 ... ii rpcbind 0.2.0-6 still I get: sm-notify[2521]: Already notifying clients; Exiting -- Levente Kovacs http://levente.logonex.eu -- 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/20110410131930.64bc4...@jive.levalinux.org
Re: Dropping unversioned kernel links/copies; adding linux-version command
On 01.04.2011 14:04, Ben Hutchings wrote: There isn't an official spec. However the source and unit tests for the DebianLinux Perl module (added to linux-base to support this command) explain the rules I came up with. I don't feel that this is enough. I wanted something that we could agree on, so this could be pulled upstream and eventually also become guideline for other distros. Also having a spec has a benefic effect of clearness and it would also serve as guideline for choosing the version names for uploads. -- Regards Vladimir 'φ-coder/phcoder' Serbinenko signature.asc Description: OpenPGP digital signature
Bug#622122: linux-image-2.6.38-2-amd64: kernel 2.6.38-2 reports Hardware errors about cache and copyback
I don't think so beacuse I bought it last year and I've never seen errors like this in kernel 2.6.32-amd64. Ernesto -- 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/1302443538.14790.2.ca...@debook.homenet.telecomitalia.it
Bug#622118: linux-base: [INTL:sk] Slovak po-debconf translation
Hi, Dňa Sun, 10 Apr 2011 14:01:49 +0200 maximilian attems m...@stro.at napísal: this confuses me there is already a sk.po in newer linux-base, is this an update? and this confused me :-) the linux-base source package in sid (3.2) do not contain debconf's sk.po file and here is not bug filled (nor archived) for it, then i know nothing about contained file now. can you send to me (directly) this sk.po, to i can make proper decision, please? -- Slavko http://slavino.sk signature.asc Description: PGP signature
Bug#622122: linux-image-2.6.38-2-amd64: kernel 2.6.38-2 reports Hardware errors about cache and copyback
On Sun, Apr 10, 2011 at 01:49:12PM +0200, Ernesto Cuconato wrote: [ 2906.788016] [Hardware Error]: Instruction Cache Error: Parity error during data load. [ 2906.788019] [Hardware Error]: cache level: L1, tx: INSN, mem-tx: IRD [ 3187.948018] [Hardware Error]: MC0_STATUS[-|CE|-|-|AddrV|CECC]: 0x943ac136 [ 3187.948022] [Hardware Error]: Data Cache Error: during L1 linefill from L2. [ 3187.948025] [Hardware Error]: cache level: L2, tx: DATA, mem-tx: DRD [ 3187.948029] mce_notify_irq: 1 callbacks suppressed [ 3187.948031] [Hardware Error]: Machine check events logged [ 3262.924013] [Hardware Error]: MC2_STATUS[-|CE|-|-|AddrV|CECC]: 0x9400417a [ 3262.924017] [Hardware Error]: Bus Unit Error: EV error during data copyback. [ 3262.924020] [Hardware Error]: cache level: L2, tx: GEN, mem-tx: EV [ 3262.924024] [Hardware Error]: Machine check events logged Replace your hardware. It is faulty. Bastian -- Warp 7 -- It's a law we can live with. -- 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/20110410134133.ga...@wavehammer.waldi.eu.org
Re: Dropping unversioned kernel links/copies; adding linux-version command
On Sun, 2011-04-10 at 14:15 +0200, Vladimir 'φ-coder/phcoder' Serbinenko wrote: On 01.04.2011 14:04, Ben Hutchings wrote: There isn't an official spec. However the source and unit tests for the DebianLinux Perl module (added to linux-base to support this command) explain the rules I came up with. I don't feel that this is enough. I wanted something that we could agree on, so this could be pulled upstream and eventually also become guideline for other distros. Also having a spec has a benefic effect of clearness and it would also serve as guideline for choosing the version names for uploads. Then *you* can write a spec. Don't tell me what extra work I should be doing. 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: Dropping unversioned kernel links/copies; adding linux-version command
On Sun, 2011-04-10 at 15:32 +0100, Ben Hutchings wrote: On Sun, 2011-04-10 at 14:15 +0200, Vladimir 'φ-coder/phcoder' Serbinenko wrote: On 01.04.2011 14:04, Ben Hutchings wrote: There isn't an official spec. However the source and unit tests for the DebianLinux Perl module (added to linux-base to support this command) explain the rules I came up with. I don't feel that this is enough. I wanted something that we could agree on, so this could be pulled upstream and eventually also become guideline for other distros. Also having a spec has a benefic effect of clearness and it would also serve as guideline for choosing the version names for uploads. Then *you* can write a spec. Don't tell me what extra work I should be doing. For the avoidance of doubt, this still applies: If there are any remaining reasons to continue using the unversioned links, or additional features you think linux-version should provide, please let us know. However Vladimir's demand was out of scope. 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#621027: Invalid shell option in start-statd
On Tue, 2011-04-05 at 02:33 +0200, Jörg Sommer wrote: Package: nfs-common Version: 1:1.2.3-1 Severity: important % head -n1 =start-statd #!/bin/sh -p % /bin/sh -p -c true /bin/sh: Illegal option -p % ls -l =sh lrwxrwxrwx 1 root root 4 17. Dez 18:49 /bin/sh - dash The option -p is not a valid option for dash, that's the default for sh. This script is only used if statd is not started (e.g. because we didn't set correct dependencies!). If statd is not started then the admin may not want it to be started automatically. I think we should remove 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
Bug#621737: linux-image-2.6.32-5-powerpc: ath ignores regulatory domain setting
Hi On Sunday 10 April 2011, Anton Ivanov wrote: On 04/10/11 00:55, Ben Hutchings wrote: On Fri, 2011-04-08 at 13:39 +0100, Anton Ivanov wrote: [...] ath driver ignores reg domain setting passed via cfg80211 and uses one from EEPROM instead. This setting a lot of cheap cards is CN. As a result the reg domain is set incorrectly (and for some countries illegally). [...] What do you mean by 'passed via cfg80211'? Are you setting the ieee80211_regdom module parameter? [...] Yes. No effect. ath still reads from eeprom. The EEPROM settings are authoritative, you can only restrict the regulatory settings further to aid regulatory compliance in different regions, but never relax them. Tools like crda always intersect the EEPROM's (OTP in newer chipset generations) with the chosen regulatory domain as provided by wireless-regdb or the in-kernel regdb; regulatory hints like IEEE 802.11d may also restrict the allowed frequencies even further. http://wireless.kernel.org/en/users/Drivers/ath#Regulatory This is intended beaviour and required for FCC compliance (keep in mind that calibration data is also only validated for the given regdomain), not a bug. 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/201104101723.38192.s@gmx.de
Bug#622118: linux-base: [INTL:sk] Slovak po-debconf translation
On Sun, 2011-04-10 at 14:18 +0200, Slavko wrote: Hi, Dňa Sun, 10 Apr 2011 14:01:49 +0200 maximilian attems m...@stro.at napísal: this confuses me there is already a sk.po in newer linux-base, is this an update? and this confused me :-) the linux-base source package in sid (3.2) do not contain debconf's sk.po file and here is not bug filled (nor archived) for it, then i know nothing about contained file now. can you send to me (directly) this sk.po, to i can make proper decision, please? I don't know what Max is talking about; there has never been an sk.po in linux-base or linux-2.6 (which linux-base was split from). 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#622118: linux-base: [INTL:sk] Slovak po-debconf translation
Ahoj, Dňa Sun, 10 Apr 2011 15:36:47 +0100 Ben Hutchings b...@decadent.org.uk napísal: I don't know what Max is talking about; there has never been an sk.po in linux-base or linux-2.6 (which linux-base was split from). perhaps he is talking about this: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=608684 -- Slavko http://slavino.sk signature.asc Description: PGP signature
Bug#622146: nfs-common: compatibility between squeeze and sid broken
Package: nfs-common Version: 1:1.2.2-4 Severity: normal Tags: ipv6 After installing nfs-common 1:1.2.3-2 on clients (unstable) the nfs-kernel- server in squeeze denies access for kerberized nfs exports. syslog on the server (squeeze) gives: rpc.svcgssd[1049]: ERROR: prepare_krb5_rfc_cfx_buffer: not implemented rpc.svcgssd[1049]: ERROR: failed serializing krb5 context for kernel rpc.svcgssd[1049]: WARNING: handle_nullreq: serialize_context_for_kernel failed and qword_eol: fflush failed: errno 38 (Function not implemented) A workaround is to upgrade servers version of nfs-kernel-server and nfs-common to 1:1.2.3-2 and linux-image to 2.6.38, but these packages are not part of squeeze. -- System Information: Debian Release: wheezy/sid APT prefers oldstable APT policy: (500, 'oldstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages nfs-common depends on: ii adduser 3.112+nmu2 add and remove users and groups ii initscripts 2.88dsf-13.1scripts for initializing and shutt ii libc62.11.2-13 Embedded GNU C Library: Shared lib ii libcap2 1:2.20-1support for getting/setting POSIX. ii libcomerr2 1.41.12-2 common error description library ii libevent-1.4-2 1.4.13-stable-1 An asynchronous event notification ii libgssapi-krb5-2 1.9+dfsg-1 MIT Kerberos runtime libraries - k ii libgssglue1 0.2-2 mechanism-switch gssapi library ii libk5crypto3 1.9+dfsg-1 MIT Kerberos runtime libraries - C ii libkrb5-31.9+dfsg-1 MIT Kerberos runtime libraries ii libnfsidmap2 0.24-1 An nfs idmapping library ii librpcsecgss30.19-2 allows secure rpc communication us ii libwrap0 7.6.q-19Wietse Venema's TCP wrappers libra ii lsb-base 3.2-27 Linux Standard Base 3.2 init scrip ii netbase 4.45Basic TCP/IP networking system ii rpcbind [portmap]0.2.0-6 converts RPC program numbers into ii ucf 3.0025+nmu1 Update Configuration File: preserv nfs-common recommends no packages. nfs-common suggests no packages. -- no debconf information -- 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/20110410154857.4047.2124.reportbug@pinguin.deutsches-haus
Bug#622118: linux-base: [INTL:sk] Slovak po-debconf translation
On Sun, Apr 10, 2011 at 04:45:39PM +0200, Slavko wrote: Ahoj, Dňa Sun, 10 Apr 2011 15:36:47 +0100 Ben Hutchings b...@decadent.org.uk napísal: I don't know what Max is talking about; there has never been an sk.po in linux-base or linux-2.6 (which linux-base was split from). there is in the squeeze repository of linux-2.6 no problem ;-) anybody sometime make a mistake... you submitted it (: #608684, landed in 2.6.32-31 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/20110410153232.ga19...@vostochny.stro.at
Re: security impact of nfsd4_op_flags
On Sun, Mar 27, 2011 at 03:09:37PM -0600, dann frazier wrote: Mi, We were wondering if you could help us define the security impact (if any) of your fix for nfsd4_op_flags, commit 5ece3ca upstream. If it does have a security impact, we can work with MITRE to get a CVE ID assigned. Apologies, but I don't have an immediate answer off the top of my head, or time to trace through it. --b. -- 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/20110410161932.ga26...@fieldses.org
Bug#614326: bug still appears in 2.6.38-2
On Mon, 2011-04-04 at 08:16 -0400, Ken Yee wrote: FYI, bug still happens with the latest 2.6.38.-2 kernel, so it definitely doesn't seem kernel related: [...] Try using a *Debian* (not aptosid) kernel without VirtualBox. 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#617511: udev didn't create new device node when plug a memory card
On Wed, 2011-03-09 at 21:17 +0700, vietnq wrote: Package: udev Version: 166-1 Severity: normal I have a Dell Inspiron 1464. When I plug a memory card into the internal card reader, a device node sdc1 is created. Do you mean that this happened when running Debian 5.0 'lenny'? But after doing dist-upgrade, no new one is created. If I keep the card plugged and reboot the computer, the node is just there as normal. Can you test Linux 2.6.38, now available in sid? You would need to upgrade linux-base and install linux-image-2.6.38-2-686. 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#620848: linux-image-2.6.32-5-amd64: unable to enumerate usb device 6
On Mon, 2011-04-04 at 18:36 +0200, Hans-J. Ullrich wrote: [...] Dear kernel team, as discussed by some German users on the lists, I got the same problem after the last update. Which version did you upgrade from? This is NOT a hardware problem, as my hardware is brandnew! Although most people are telling, the hardware is defektiv, it is definately NOT! The problem is caused by the ohci-usb module, and the message-spam appears as soon it is loaded. There was a previous workaround by unloding ehci-usb module, but this does not fix it. [...] When did you use this 'previous workaround'? 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#620996: linux-image-2.6.38-1-amd64: Kernel Oops During Resume From Hibernate
On Tue, 2011-04-05 at 20:24 +0200, Michael Ott wrote: Package: linux-2.6 Version: 2.6.38-1 Severity: normal [...] This may be the same bug as #620284, which was fixed in version 2.6.38-3. Please can you try that 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#622118: linux-base: [INTL:sk] Slovak po-debconf translation
On Sun, 2011-04-10 at 15:32 +, maximilian attems wrote: On Sun, Apr 10, 2011 at 04:45:39PM +0200, Slavko wrote: Ahoj, Dňa Sun, 10 Apr 2011 15:36:47 +0100 Ben Hutchings b...@decadent.org.uk napísal: I don't know what Max is talking about; there has never been an sk.po in linux-base or linux-2.6 (which linux-base was split from). there is in the squeeze repository of linux-2.6 no problem ;-) anybody sometime make a mistake... you submitted it (: #608684, landed in 2.6.32-31 You should have added it to sid/trunk at the same time, Max. 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#622146: nfs-common: compatibility between squeeze and sid broken
On Sun, 2011-04-10 at 17:48 +0200, Rico Rommel wrote: Package: nfs-common Version: 1:1.2.2-4 Severity: normal Tags: ipv6 [...] Why ipv6? 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 620996
Processing commands for cont...@bugs.debian.org: tags 620996 + moreinfo Bug #620996 [linux-2.6] linux-image-2.6.38-1-amd64: Kernel Oops During Resume From Hibernate Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 620996: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620996 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.130245669820349.transcr...@bugs.debian.org
Bug#615148: marked as done (BCM4313: brcm80211 module needs to be blacklisted to correctly suspend)
Your message dated Sun, 10 Apr 2011 16:47:20 +0100 with message-id 1302450440.5282.124.camel@localhost and subject line Re: BCM4313: brcm80211 module needs to be blacklisted to correctly suspend has caused the Debian Bug report #615148, regarding BCM4313: brcm80211 module needs to be blacklisted to correctly suspend to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 615148: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=615148 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: firmware-brcm80211 Version: 0.28 Severity: normal Add /etc/pm/config.d/50-suspend with SUSPEND_MODULES=brcm80211. -- System Information: Debian Release: 6.0 APT prefers squeeze-updates APT policy: (500, 'squeeze-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to it_IT.UTF-8) Shell: /bin/sh linked to /bin/dash firmware-brcm80211 depends on no packages. firmware-brcm80211 recommends no packages. Versions of packages firmware-brcm80211 suggests: ii initramfs-tools 0.98.8 tools for generating an initramfs ii linux-image-2.6.32-5-amd64 [l 2.6.32-30 Linux 2.6.32 for 64-bit PCs -- no debconf information ---End Message--- ---BeginMessage--- On Sat, 2011-02-26 at 04:14 +0100, Pier Paolo wrote: Package: firmware-brcm80211 Version: 0.28 Severity: normal Add /etc/pm/config.d/50-suspend with SUSPEND_MODULES=brcm80211. This is a driver bug, not a firmware bug. Probably the same as #600769 and #604802, which were fixed in linux-2.6 version 2.6.32-31. 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: security impact of nfsd4_op_flags
On Sun, Apr 10, 2011 at 12:19:32PM -0400, J. Bruce Fields wrote: On Sun, Mar 27, 2011 at 03:09:37PM -0600, dann frazier wrote: Mi, We were wondering if you could help us define the security impact (if any) of your fix for nfsd4_op_flags, commit 5ece3ca upstream. If it does have a security impact, we can work with MITRE to get a CVE ID assigned. Apologies, but I don't have an immediate answer off the top of my head, or time to trace through it. No problem, thanks for taking the time to reply. -- 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/20110410172202.ga6...@dannf.org
Processed: tagging 622146
Processing commands for cont...@bugs.debian.org: tags 622146 - ipv6 Bug #622146 [nfs-common] nfs-common: compatibility between squeeze and sid broken Removed tag(s) ipv6. thanks Stopping processing here. Please contact me if you need assistance. -- 622146: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622146 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.130245789226012.transcr...@bugs.debian.org
Bug#622118: linux-base: [INTL:sk] Slovak po-debconf translation
On Sun, 10 Apr 2011, Slavko wrote: Package: linux-base Severity: wishlist Tags: l10n patch Version: 3.2 sk.po attached this confuses me there is already a sk.po in newer linux-base, is this an update? regards thank you. -- 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/20110410120149.gc11...@stro.at
Bug#622146: nfs-common: compatibility between squeeze and sid broken
On 04/10/2011 06:10 PM, Rico Rommel wrote: Am Sonntag, 10. April 2011, 17:57:11 schrieb Ben Hutchings: On Sun, 2011-04-10 at 17:48 +0200, Rico Rommel wrote: Package: nfs-common Version: 1:1.2.2-4 Severity: normal Tags: ipv6 [...] Why ipv6? Ben. I noticed, that nfs-common doesn't depend on librpcsecgss3 anymore and tried a rebuild using librpcsecgss3. But librpcsecgss3 conflicts with the now used libtirpc1, which provides ipv6 support to nfs. (as i understood) Does removing librpcsecgss3 solve the problem? Cheers Luk -- 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/4da1f260.6090...@debian.org
Bug#621737: linux-image-2.6.32-5-powerpc: ath ignores regulatory domain setting
On 04/10/11 16:23, Stefan Lippers-Hollmann wrote: Hi On Sunday 10 April 2011, Anton Ivanov wrote: On 04/10/11 00:55, Ben Hutchings wrote: On Fri, 2011-04-08 at 13:39 +0100, Anton Ivanov wrote: [...] ath driver ignores reg domain setting passed via cfg80211 and uses one from EEPROM instead. This setting a lot of cheap cards is CN. As a result the reg domain is set incorrectly (and for some countries illegally). [...] What do you mean by 'passed via cfg80211'? Are you setting the ieee80211_regdom module parameter? [...] Yes. No effect. ath still reads from eeprom. The EEPROM settings are authoritative, you can only restrict the regulatory settings further to aid regulatory compliance in different regions, but never relax them. Tools like crda always intersect the EEPROM's (OTP in newer chipset generations) with the chosen regulatory domain as provided by wireless-regdb or the in-kernel regdb; regulatory hints like IEEE 802.11d may also restrict the allowed frequencies even further. http://wireless.kernel.org/en/users/Drivers/ath#Regulatory This is intended beaviour and required for FCC compliance (keep in mind that calibration data is also only validated for the given regdomain), not a bug. So a card that returns only CN from EEPROM is basically intended to be sold _ONLY_ in China. Right? Brgds, Regards Stefan Lippers-Hollmann -- Understanding is a three-edged sword: your side, their side, and the truth. --Kosh Naranek A. R. Ivanov E-mail: aiva...@sigsegv.cx WWW: http://www.sigsegv.cx/ pub 1024D/DDE5E715 2002-03-03 Anton R. Ivanovai...@sigsegv.cx Fingerprint: C824 CBD7 EE4B D7F8 5331 89D5 FCDA 572E DDE5 E715 -- 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/4da1f416.9000...@sigsegv.cx
Bug#622146: nfs-common: compatibility between squeeze and sid broken
Am Sonntag, 10. April 2011, 20:09:36 schrieb Luk Claes: On 04/10/2011 06:10 PM, Rico Rommel wrote: Am Sonntag, 10. April 2011, 17:57:11 schrieb Ben Hutchings: On Sun, 2011-04-10 at 17:48 +0200, Rico Rommel wrote: Package: nfs-common Version: 1:1.2.2-4 Severity: normal Tags: ipv6 [...] Why ipv6? Ben. I noticed, that nfs-common doesn't depend on librpcsecgss3 anymore and tried a rebuild using librpcsecgss3. But librpcsecgss3 conflicts with the now used libtirpc1, which provides ipv6 support to nfs. (as i understood) Does removing librpcsecgss3 solve the problem? No, it doesn't make any difference. librpcsecgss3 isn't used by nfs-common 1.2.3-2 Rico signature.asc Description: This is a digitally signed message part.
Bug#621737: linux-image-2.6.32-5-powerpc: ath ignores regulatory domain setting
On Sun, 2011-04-10 at 19:16 +0100, Anton Ivanov wrote: On 04/10/11 16:23, Stefan Lippers-Hollmann wrote: Hi On Sunday 10 April 2011, Anton Ivanov wrote: On 04/10/11 00:55, Ben Hutchings wrote: On Fri, 2011-04-08 at 13:39 +0100, Anton Ivanov wrote: [...] ath driver ignores reg domain setting passed via cfg80211 and uses one from EEPROM instead. This setting a lot of cheap cards is CN. As a result the reg domain is set incorrectly (and for some countries illegally). [...] What do you mean by 'passed via cfg80211'? Are you setting the ieee80211_regdom module parameter? [...] Yes. No effect. ath still reads from eeprom. The EEPROM settings are authoritative, you can only restrict the regulatory settings further to aid regulatory compliance in different regions, but never relax them. Tools like crda always intersect the EEPROM's (OTP in newer chipset generations) with the chosen regulatory domain as provided by wireless-regdb or the in-kernel regdb; regulatory hints like IEEE 802.11d may also restrict the allowed frequencies even further. http://wireless.kernel.org/en/users/Drivers/ath#Regulatory This is intended beaviour and required for FCC compliance (keep in mind that calibration data is also only validated for the given regdomain), not a bug. So a card that returns only CN from EEPROM is basically intended to be sold _ONLY_ in China. Right? Yes. It is probably illegal to sell these cards in some countries. 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#621737: linux-image-2.6.32-5-powerpc: ath ignores regulatory domain setting
Hi On Sunday 10 April 2011, Anton Ivanov wrote: On 04/10/11 16:23, Stefan Lippers-Hollmann wrote: Hi On Sunday 10 April 2011, Anton Ivanov wrote: On 04/10/11 00:55, Ben Hutchings wrote: On Fri, 2011-04-08 at 13:39 +0100, Anton Ivanov wrote: [...] Yes. No effect. ath still reads from eeprom. The EEPROM settings are authoritative, you can only restrict the regulatory settings further to aid regulatory compliance in different regions, but never relax them. Tools like crda always intersect the EEPROM's (OTP in newer chipset generations) with the chosen regulatory domain as provided by wireless-regdb or the in-kernel regdb; regulatory hints like IEEE 802.11d may also restrict the allowed frequencies even further. http://wireless.kernel.org/en/users/Drivers/ath#Regulatory This is intended beaviour and required for FCC compliance (keep in mind that calibration data is also only validated for the given regdomain), not a bug. So a card that returns only CN from EEPROM is basically intended to be sold _ONLY_ in China. Right? [...] Correct, it's arguably even illegal to sell in ETSI regions. Although it's technically a little more complex as Atheros groups regdom regions with identical mappings together[1], which makes reading the EEPROM based regulatory domain code a bit strange (the alphabetically first match corresponding to the regdom group gets printed to dmesg). In your particular case, with a 2.4 GHz-only AR2417 PHY, 0x52 (APL1_WORLD vs ETSI1_WORLD, GB) doesn't actually do any harm, as 'CN' allows channel 1-13 just as well as the most permissive regdomains (ch14 in Japan is only allowed for CSMA/CA == 11 MBit/s, not the more common OFDM rates (= 54 MBit/s)). So even though your device is wrongly programmed, it doesn't actually limit your abilities (unless you'd add an additional 5 GHz capable card, which would suffer from an 'unfortunate' intersection) - and neither allows you to access non-public frequency bands. This situation would be seriously worse (both technically and legally) for 5 GHz operations, but your device doesn't support that anyways. country CN: (2402 - 2482 @ 40), (N/A, 20) (5735 - 5835 @ 40), (N/A, 30) country GB: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5710 @ 40), (N/A, 27), DFS However I'm aware of the sad truth that most commonly sold cards are wrongly programmed for CN or (worse for 2.4 GHz operations) US... Regards Stefan Lippers-Hollmann [1] http://wireless.kernel.org/en/users/Drivers/ath#line-28 -- 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/201104102108.14911.s@gmx.de
Bug#621737: linux-image-2.6.32-5-powerpc: ath ignores regulatory domain setting
OK, cool, thanks, you can close the bug. I agree - thankfully it is not a 5GHz part so no harm done from it reporting CN. Brgds, On 04/10/11 20:08, Stefan Lippers-Hollmann wrote: Hi On Sunday 10 April 2011, Anton Ivanov wrote: On 04/10/11 16:23, Stefan Lippers-Hollmann wrote: Hi On Sunday 10 April 2011, Anton Ivanov wrote: On 04/10/11 00:55, Ben Hutchings wrote: On Fri, 2011-04-08 at 13:39 +0100, Anton Ivanov wrote: [...] Yes. No effect. ath still reads from eeprom. The EEPROM settings are authoritative, you can only restrict the regulatory settings further to aid regulatory compliance in different regions, but never relax them. Tools like crda always intersect the EEPROM's (OTP in newer chipset generations) with the chosen regulatory domain as provided by wireless-regdb or the in-kernel regdb; regulatory hints like IEEE 802.11d may also restrict the allowed frequencies even further. http://wireless.kernel.org/en/users/Drivers/ath#Regulatory This is intended beaviour and required for FCC compliance (keep in mind that calibration data is also only validated for the given regdomain), not a bug. So a card that returns only CN from EEPROM is basically intended to be sold _ONLY_ in China. Right? [...] Correct, it's arguably even illegal to sell in ETSI regions. Although it's technically a little more complex as Atheros groups regdom regions with identical mappings together[1], which makes reading the EEPROM based regulatory domain code a bit strange (the alphabetically first match corresponding to the regdom group gets printed to dmesg). In your particular case, with a 2.4 GHz-only AR2417 PHY, 0x52 (APL1_WORLD vs ETSI1_WORLD, GB) doesn't actually do any harm, as 'CN' allows channel 1-13 just as well as the most permissive regdomains (ch14 in Japan is only allowed for CSMA/CA == 11 MBit/s, not the more common OFDM rates (= 54 MBit/s)). So even though your device is wrongly programmed, it doesn't actually limit your abilities (unless you'd add an additional 5 GHz capable card, which would suffer from an 'unfortunate' intersection) - and neither allows you to access non-public frequency bands. This situation would be seriously worse (both technically and legally) for 5 GHz operations, but your device doesn't support that anyways. country CN: (2402 - 2482 @ 40), (N/A, 20) (5735 - 5835 @ 40), (N/A, 30) country GB: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5710 @ 40), (N/A, 27), DFS However I'm aware of the sad truth that most commonly sold cards are wrongly programmed for CN or (worse for 2.4 GHz operations) US... Regards Stefan Lippers-Hollmann [1] http://wireless.kernel.org/en/users/Drivers/ath#line-28 -- Understanding is a three-edged sword: your side, their side, and the truth. --Kosh Naranek A. R. Ivanov E-mail: aiva...@sigsegv.cx WWW: http://www.sigsegv.cx/ pub 1024D/DDE5E715 2002-03-03 Anton R. Ivanovai...@sigsegv.cx Fingerprint: C824 CBD7 EE4B D7F8 5331 89D5 FCDA 572E DDE5 E715 -- 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/4da20b48.4070...@sigsegv.cx
Bug#621737: marked as done (linux-image-2.6.32-5-powerpc: ath ignores regulatory domain setting)
Your message dated Sun, 10 Apr 2011 22:04:45 +0100 with message-id 1302469485.5282.343.camel@localhost and subject line Re: Bug#621737: linux-image-2.6.32-5-powerpc: ath ignores regulatory domain setting has caused the Debian Bug report #621737, regarding linux-image-2.6.32-5-powerpc: ath ignores regulatory domain setting 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.) -- 621737: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621737 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-30 Severity: minor ath driver ignores reg domain setting passed via cfg80211 and uses one from EEPROM instead. This setting a lot of cheap cards is CN. As a result the reg domain is set incorrectly (and for some countries illegally). dmesg selfexplanatory. -- Package-specific info: ** Version: Linux version 2.6.32-5-powerpc (Debian 2.6.32-30) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 Wed Jan 12 04:47:03 UTC 2011 ** Command line: root=/dev/hda4 ro ** Tainted: W (512) * Taint on warning. ** Kernel log: [37906.170686] PHY ID: 2060e1, addr: 0 [37908.211322] eth1: Airport waking up [37908.659045] hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4 [37908.659178] adb: starting probe task... [37908.660207] hda: UDMA/66 mode selected [37908.664146] hdc: host max PIO4 wanted PIO255(auto-tune) selected PIO4 [37908.664517] hdc: MWDMA2 mode selected [37908.907906] adb devices: [2]: 2 c4 [3]: 3 1 [7]: 7 1f [37908.913808] ADB keyboard at 2, handler 1 [37908.928828] ADB mouse at 3, handler set to 4 (trackpad) [37908.987527] adb: finished probe task... [37909.512236] PM: Finishing wakeup. [37909.512244] Restarting tasks ... done. [37909.986288] ath5k 0001:11:00.0: enabling device ( - 0002) [37909.986396] ath5k 0001:11:00.0: registered as 'phy1' [37910.772036] ath: EEPROM regdomain: 0x809c [37910.772046] ath: EEPROM indicates we should expect a country code [37910.772054] ath: doing EEPROM country-regdmn map search [37910.772061] ath: country maps to regdmn code: 0x52 [37910.772069] ath: Country alpha2 being used: CN [37910.772075] ath: Regpair used: 0x52 [37910.847157] agpgart-uninorth :00:0b.0: putting AGP V2 device into 4x mode [37910.847179] radeonfb :00:10.0: putting AGP V2 device into 4x mode [37910.874578] phy1: Selected rate control algorithm 'minstrel' [37910.878605] ath5k phy1: Atheros AR2417 chip found (MAC: 0xf0, PHY: 0x70) [37910.878634] cfg80211: Calling CRDA for country: CN [37912.612186] ondemand governor failed, too long transition latency of HW, fallback to performance governor [37988.110403] ondemand governor failed, too long transition latency of HW, fallback to performance governor [37988.359273] hda: host max PIO4 wanted PIO0 selected PIO0 [38096.963649] ADDRCONF(NETDEV_UP): wlan0: link is not ready [38102.988503] ADDRCONF(NETDEV_UP): wlan0: link is not ready [38103.192041] ADDRCONF(NETDEV_UP): eth0: link is not ready [38103.454283] ADDRCONF(NETDEV_UP): wlan0: link is not ready [38106.938822] wlan0: direct probe to AP 00:90:4c:91:00:03 (try 1) [38106.940456] wlan0: direct probe responded [38106.940465] wlan0: authenticate with AP 00:90:4c:91:00:03 (try 1) [38106.942155] wlan0: authenticated [38106.942187] wlan0: associate with AP 00:90:4c:91:00:03 (try 1) [38106.98] wlan0: RX AssocResp from 00:90:4c:91:00:03 (capab=0x411 status=0 aid=5) [38106.944457] wlan0: associated [38106.945747] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [38153.913695] tun0: Disabled Privacy Extensions [38513.727694] pcmcia_socket pcmcia_socket0: pccard: card ejected from slot 0 [38513.763178] wlan0: deauthenticating from 00:90:4c:91:00:03 by local choice (reason=3) [38513.808570] ath5k phy1: failed to wakeup the MAC Chip [38514.658638] ADDRCONF(NETDEV_UP): eth0: link is not ready [38582.438927] cfg80211: Using static regulatory domain info [38582.438937] cfg80211: Regulatory domain: EU [38582.438941] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [38582.438949] (2402000 KHz - 2482000 KHz @ 4 KHz), (600 mBi, 2000 mBm) [38582.438956] (517 KHz - 519 KHz @ 4 KHz), (600 mBi, 2300 mBm) [38582.438964] (519 KHz - 521 KHz @ 4 KHz), (600 mBi, 2300 mBm) [38582.438971] (521 KHz - 523 KHz @ 4 KHz), (600 mBi, 2300 mBm) [38582.438978] (523 KHz - 533 KHz @ 4 KHz), (600 mBi, 2000 mBm) [38582.438985] (549 KHz - 571 KHz @ 4 KHz), (600 mBi, 3000 mBm) [38582.442195] cfg80211: Calling CRDA for country: EU [38582.442360] cfg80211: Calling CRDA for country: EU
Re: Problems with brcm80211 driver
On Sun, 2011-04-10 at 23:29 +0200, Wenceslao González-Viñas wrote: Dear all, Don't spam the BTS. I got an Inspiron 1120, and I am not even able to install anything of Debian from network because the driver brcm80211 (supposedly BCM4313) is not working. First I got the error failed to load firmware brcm/bcm43xx-0.fw and I found this bug. So I took the information from Ben in http://svn.debian.org/wsvn/kernel/dists/trunk/firmware-nonfree/brcm80211/brcm/ Now, at least the driver detects the device and it appear a wlan0 ... But when I list the channels (iwlist wlan0 channel) I get only 11. This reminds me another previous problem with another machine (which is now fixed): Bug#594561 Don't use iwlist, use 'iw reg get'. How can I put my device into work in 2.472 GHz? You should be able to do this by setting the cfg80211 module parameter ieee80211_regdom=EU. Although now I see that this won't work without crda. I'll reenable the built-in regulatory information. And then see why the hell crda *still* isn't in the archive. 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: Uploading linux-2.6 (2.6.38-3)
On Tue, 2011-04-05 at 23:35 +0100, Ben Hutchings wrote: Version 2.6.38-2 had build failures on a couple of architectures. We now have fixes for those, and a few other bugs. There is no pending stable update for 2.6.38, so I intend to upload this in about 24 hours' time if there are no objections. 2.6.38-3 migrated to testing during tonight's britney run. Regards, Adam -- 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/1302474427.4931.9285.ca...@hathi.jungle.funky-badger.org
Bug#607301: Installation-Report: No Boot with Silicon Image SiI 3114 SATA/Raid Controller + single SATA disk drive and GNU/Linux Debian 6.0.0 i386 New install. No raid array used.
Miguel Figueiredo wrote If I understood correctly: Using a Sil 3114 Sata raid controller you are only able to boot sucessfully in rescue mode. My appologies Miguel, I have not made myself clear. My fault. In response to your question Miguel, my short answer is 'no'. I cannot 'rescue - boot' the newly installed pc debian system with, or from, rescue mode, with the aid of the 'rescue cdrom' disk and it's Grub GNU/Linux 'Boot Command List'. The 'rescue cdrom' disk, boots itself in the pc OK ! Having booted the rescue-disk itself, I cannot use the running rescue disk's GNU/Linux 'Command List' to 'rescue - boot' the debian system previously installed on hard disk. McTech wrote at Message #27 received at 607...@bugs.debian.org Subject: No boot with Debian sid, unstable grub-rescue-pc 1.99~rc1-3 i386, SATA, SiI 3114 Date: 06.03.2011. Fails to boot with Debian sid, unstable grub-rescue-pc 1.99~rc1-3 i386, The rescue disk boots itself ok, but it does not rescue the machine. The pc does not boot in conjunction with the rescue disk, after succesfully installing from, (except auto booting) versions of :- Debian 6.0.0, wheezy weekly build , unstable-20.02.2011 and also experimemtal-20.02.2011, and experimental-04.03.2011. After I set the rescue-disk-pc GNU/Linux parameters to :- set params 'GNU/Linux' (as it comes, a blank line here) set root=(hd0,1) linux /boot/vmlinux-2.6.37-2-486 root=/dev/sda1 initrd /boot/initrd.img-2.6.37-2-486 The rescue-disk-pc Boot Symptom is :- error: hd0 cannot get c/h/s values error: you need to load the kernel first. press any key to continue grub ls (cd) (cd,msdos1) (fd0) Today, 10.04.2011, I can see Ubuntu's https://launchpad.net/ubuntu/natty/+source/grub2/1.99~rc1-10ubuntu1 I can also see the following Debian link is there at http://packages.debian.org/changelogs/pool/main/g/grub2/grub2_1.99~rc1-10/changelog but no Debian web site, Grub rc1-10 changelog text yet. http://packages.debian.org/changelogs/pool/main/g/grub2/ no rc1-10 entry yet. I will wait a while. --- Minor corrections to errors I made in my previous 04.04.2011 posting:- Using debian-rescue-cdrom Grub 1.99~rc1-6 should be Using Debian grub-rescue-cdrom 1.99~rc1-6 issue suappears should be issue appears . root@grml / # /dev/sda0(just to see) should be root@grml / # ls /dev/sda0 (just to see) ls: cannot access /dev/sda0 : No such file or directory. Again, thank your help Miguel. It is appreciated. Regards, McTech. I am progressing this potential grub symptom in help-g...@gnu.org I am not sure how I specify specific message or bug numbers, or join / link up the seperate entries there at help-grub. -- 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/banlktimngjoda_bbq1jpkxvw_jcirje...@mail.gmail.com
Bug#621707: nfs-common fails to start during boot
Hey Jean, Had the same problem. Solved it removing nfs-common and portmap and reinstalling nfs-common. Then, portmap was not reinstalled but instead rpcbind was. This worked out perfectly for me as well. Problem fixed, thanks. Adnan On Sat, Apr 9, 2011 at 1:49 PM, Jean Baptiste FAVRE debian...@jbfavre.org wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, Had the same problem. Solved it removing nfs-common and portmap and reinstalling nfs-common. Then, portmap was not reinstalled but instead rpcbind was. Regards, JB On 08/04/2011 04:46, Adnan Hodzic wrote: Ben, Why yes, of course. Lines concerning nfs-common that fail during boot process have following output: Starting NFS common utilities: statd failed! ... Startpar: service(s) returned failure: nfs-common ... failed! ... Starting NFS common utilities: statd failed! ... Startpar: service(s) returned failure: nfs-common failed! Hope this helps and let me know if you need anything else, Adnan On Fri, Apr 8, 2011 at 4:26 AM, Ben Hutchings b...@decadent.org.uk wrote: On Fri, 2011-04-08 at 03:34 +0200, Adnan Hodzic wrote: Package: nfs-common Version: 1:1.2.3-1 Severity: normal During boot I get numerous errors regarding NFS and particulary on nfs-commons failing to start. There was a just recent bug (~March 16th) regarding inability to install/reinstall nfs-commons and that this problem was fixed with latest nfs-common package. Unfortunately I still have this problem, and if I try to reinstall it I will be unable to do so. Perhaps you should tell us what the errors are. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2gR8YACgkQM2eZoKJfKd1PRQCeK+g+L/UXSsjjnfJvuM8c47WO SS4AnRWHEK+pQ+QXCq/uEgcfVMInXHwV =TMIc -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/BANLkTimT0Z48=mftmoaq5uwxwf7vkiy...@mail.gmail.com
Bug#622218: linux-image-2.6.38-2-amd64: Btrfs fails on first mount due to in-kernel NULL pointer dereference
Package: linux-2.6 Version: 2.6.38-3 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 System boots, but many of my file systems are now btrfs and they do not end up mounted. I'm now in Squeeze kernel to send this report. I should be able to get the kernel traceback tomorrow. Definitely happening during the btrfs mount of my /opt file system which is almost empty. Running btrfsck against that file system reports no errors; mounts fine under Squeeze kernel, and under the previous version of 2.6.38 -- failure happened today after I updated kernel and tried to reboot. Error was unable to handle kernel NULL pointer deference. Last sysfs file touched ended in something like btrfs/uevent-1. Will further reply with boot messages from 2.6.28 (currently sending this from Squeeze kernel). - -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: TYAN Computer Corp product_name: S2895 product_version: TYAN Thunder K8WE S2895 chassis_vendor: TYAN Computer Corp chassis_version: bios_vendor: Phoenix Technologies Ltd. bios_version: 2004Q3 board_vendor: Tyan Computer Corp board_name: S2895 board_version: TYAN Thunder K8WE S2895 ** Network interface configuration: auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp hwaddress ether 00:04:4B:FA:CA:DE hostname monster iface eth1 inet dhcp hwaddress ether 00:04:4B:EF:FA:CE hostname monster ** PCI devices: 00:00.0 Memory controller [0580]: nVidia Corporation CK804 Memory Controller [10de:005e] (rev a3) Subsystem: Tyan Computer Device [10f1:2895] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Capabilities: access denied 00:01.0 ISA bridge [0601]: nVidia Corporation CK804 ISA Bridge [10de:0051] (rev a3) Subsystem: Tyan Computer Device [10f1:2895] Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Region 0: I/O ports at 8c00 [size=1K] 00:01.1 SMBus [0c05]: nVidia Corporation CK804 SMBus [10de:0052] (rev a2) Subsystem: Tyan Computer Device [10f1:2895] Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Interrupt: pin A routed to IRQ 0 Region 0: I/O ports at 1080 [size=32] Region 4: I/O ports at 1000 [size=64] Region 5: I/O ports at 1040 [size=64] Capabilities: access denied Kernel driver in use: nForce2_smbus Kernel modules: i2c-nforce2 00:02.0 USB Controller [0c03]: nVidia Corporation CK804 USB Controller [10de:005a] (rev a2) (prog-if 10 [OHCI]) Subsystem: Tyan Computer Device [10f1:2895] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 (750ns min, 250ns max) Interrupt: pin A routed to IRQ 23 Region 0: Memory at a000 (32-bit, non-prefetchable) [size=4K] Capabilities: access denied Kernel driver in use: ohci_hcd Kernel modules: ohci-hcd 00:02.1 USB Controller [0c03]: nVidia Corporation CK804 USB Controller [10de:005b] (rev a3) (prog-if 20 [EHCI]) Subsystem: Tyan Computer Device [10f1:2895] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 (750ns min, 250ns max) Interrupt: pin B routed to IRQ 20 Region 0: Memory at a0001000 (32-bit, non-prefetchable) [size=256] Capabilities: access denied Kernel driver in use: ehci_hcd Kernel modules: ehci-hcd 00:04.0 Multimedia audio controller [0401]: nVidia Corporation CK804 AC'97 Audio Controller [10de:0059] (rev a2) Subsystem: Tyan Computer Device [10f1:2895] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 (500ns min, 1250ns max) Interrupt: pin A routed to IRQ 22 Region 0: I/O ports at 1800 [size=256] Region 1: I/O ports at 1400 [size=256] Region 2: Memory at a0002000 (32-bit, non-prefetchable) [size=4K] Capabilities: access denied Kernel driver in use: Intel ICH Kernel modules:
