Bug#656899: Same problem too under SPARC64
hi Ben, Am 03.02.2012 um 04:45 schrieb Ben Hutchings: > > Does the attached patch fix this? This change should be in the longterm > update 2.6.32.56 and we can put it into a stable update pretty soon if > necessary. as you said, the patch changes nothing: == Booting = [...] [ 93.392382] scsi 1:0:1:0: Direct-Access FUJITSU MAY2073RCSUN72G 0601 PQ: 0 ANSI: 4 [ 93.522739] sd 1:0:1:0: [sdb] 143374738 512-byte logical blocks: (73.4 GB/68.3 GiB) [ 93.542647] sd 1:0:0:0: [sda] 143374738 512-byte logical blocks: (73.4 GB/68.3 GiB) [ 93.544892] sd 1:0:0:0: [sda] Write Protect is off [ 93.546724] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA [ 93.571398] sda: sda1 sda2 sda3 [ 93.944231] sd 1:0:1:0: [sdb] Write Protect is off [ 93.972728] sd 1:0:0:0: [sda] Attached SCSI disk [ 94.069324] sd 1:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 94.192651] sdb: sdb1 sdb2 sdb3 [ 94.252601] sd 1:0:1:0: [sdb] Attached SCSI disk Begin: Loading essential drivers[ 94.490764] mdadm: sending ioctl 20001261 to a partition! ... done. Begi[ 94.572794] mdadm: sending ioctl 20001261 to a partition! n: Running /scri[ 94.666140] md: md0 stopped. pts/init-premoun[ 94.715638] mdadm: sending ioctl 20001261 to a partition! t ... done. Beg[ 94.802768] mdadm: sending ioctl 20001261 to a partition! in: Mounting roo[ 94.891950] mdadm: sending ioctl 20001261 to a partition! t file system ..[ 94.978148] mdadm: sending ioctl 20001261 to a partition! . Begin: Running[ 95.066478] mdadm: sending ioctl 20001261 to a partition! /scripts/local-[ 95.153554] mdadm: sending ioctl 20001261 to a partition! top ... Begin: L[ 95.243853] md: bind oadingFailure: f[ 95.293958] md: bind ailed to load mo[ 95.348444] raid1: raid set md0 active with 2 out of 2 mirrors dule raid1. don[ 95.439125] md0: detected capacity change from 0 to 72899533824 e. Begin: Assem[ 95.535673] md0:bling all MD arr unknown partition table ays ... mdadm: d[ 95.623786] mdadm: sending ioctl 20001261 to a partition! evice 1 in /dev/[ 95.707595] mdadm: sending ioctl 20001261 to a partition! md/0 has wrong state in superblock, but /dev/sdb2 seems ok mdadm: /dev/md/0 has been started with 2 drives. Success: assembled all arrays. done. done. Begin: Running /scripts/local-premount ... done. [ 96.329438] EXT4-fs (dm-0): mounted filesystem with ordered data mode Begin: Running /scripts/local-bottom ... done. done. Begin: Running /scripts/init-bottom ... done. INIT: version 2.88 booting Using makefile-style concurrent boot in runlevel S. Starting the hotplug events dispatcher: udevd[ 97.163217] udev[272]: starting version 164 . Synthesizing the initial hotplug events...done. Waiting for /dev to be fully populated...[ 97.500481] mdadm: sending ioctl 20001261 to a partition! [ 97.571656] mdadm: sending ioctl 20001261 to a partition! done. Checking root file system...fsck from util-linux-ng 2.17.2 [ 98.109972] mdadm: sending ioctl 20001261 to a partition!8747/1220608 blocks done. Cleaning up ifupdown[ 98.208631] mdadm: sending ioctl 20001261 to a partition! [ 98.292584] mdadm: sending ioctl 20001261 to a partition! Setting up netwo[ 98.371654] mdadm: sending ioctl 20001261 to a partition! rking [ 98.453822] mdadm: sending ioctl 20001261 to a partition! [ 98.474271] loop: module loaded Loading kernel m[ 98.587144] mdadm: sending ioctl 20001261 to a partition! odules...done. [ 98.666444] mdadm: sending ioctl 20001261 to a partition! [ 98.754847] mdadm: sending ioctl 20001261 to a partition! [ 98.826007] mdadm: sending ioctl 20001261 to a partition! Generating udev [ 98.913101] mdadm: sending ioctl 20001261 to a partition! events for MD ar[ 98.993103] mdadm: sending ioctl 20001261 to a partition! rays...done. Setting up LVM Volume Groups Reading all physical volumes. This may take a while... Found volume group "root-vg" using metadata type lvm2 5 logical volume(s) in volume group "root-vg" now active . A[ 99.721865] Adding 3903472k swap on /dev/mapper/root--vg-swap_fs. Priority:-1 extents:1 across:3903472k ctivating lvm and md swap...done. Checking file systems...fsck from util-linux-ng 2.17.2 /dev/sda1: clean, 35/245280 files, 55661/489982 blocks /dev/mapper/root--vg-tmp_fs: clean, 13/60928 files, 8233/243712 blocks /dev/mapper/root--vg-var_fs: clean, 2182/244320 files, 101989/975872 [ 100.153260] EXT4-fs (dm-3): blocks done. Mmounted filesystem with ordered data modeounting local fi lesystems...[ 100.289830] EXT4-fs (dm-2): mounted filesystem with ordered data mode done. Activating swapfile swap...done. Cleaning up temporary files Setting kernel variables ...done. [...] === but one thing I've found: the remount to Read-Only from "/" didn't come from the mdadm, it comes from LXC if you shutdown a container
Processed: tagging as pending bugs that are closed by packages in NEW
Processing commands for cont...@bugs.debian.org:
> # Fri Feb 3 07:03:35 UTC 2012
> # Tagging as pending bugs that are closed by packages in NEW
> # http://ftp-master.debian.org/new.html
> #
> # Source package in NEW: linux-2.6
> tags 657112 + pending
Bug #657112 {Done: Ben Hutchings } [src:linux-2.6] Please
build linux-2.6 on Alpha with gcc-4.5
Added tag(s) pending.
> # Source package in NEW: linux-2.6
> tags 648996 + pending
Bug #648996 {Done: Ben Hutchings } [linux-2.6] linux-2.6:
FTBFS [m68k] in modpost: "strlen" [iscsi_target_mod.ko] undefined! (and others)
Added tag(s) pending.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
648996: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648996
657112: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657112
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.13282526267663.transcr...@bugs.debian.org
Bug#651199: iwlwifi: Connection lost on "WPA: Group rekeying"
This bug just got introduced into squeeze-backports with the inclusion of the 3.2-kernel. BR, Andreas mån 2012-01-23 klockan 14:40 +0100 skrev Marco d'Itri: > On Dec 16, Jonathan Nieder wrote: > > > There have been a few iwlwifi fixes upstream recently. Could you > > try[1] v3.2-rc5 or later? > The bug is still present in 3.2. > -- 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/1328252540.2215.0.ca...@neith.impressions.se
Re: cpufrequtils doesn't support new AMD cpus
On Fri, 2012-02-03 at 04:16 +0200, Touko Korpela wrote: > On Sat, Jan 07, 2012 at 03:30:04PM +0200, Touko Korpela wrote: > > I think you should also add family 18 (AMD Fusion Llano). > > http://www.phoronix.com/vr.php?view=16292 > > > > > > On Sat, Jan 07, 2012 at 12:06:05AM -0600, Robert Keevil wrote: > > > Package: cpufrequtils > > > Version: 007-2 > > > Severity: normal > > > Tags: patch > > > > > > /etc/init.d/loadcpufreq does not support AMD Bulldozer CPUs, which have a > > > CPU > > > family of 21. The processor is supported by the powernow_k8 module. > > > > > --- debian/cpufrequtils.loadcpufreq.init.dist 2012-01-06 > > > 23:35:24.867961318 -0600 > > > +++ debian/cpufrequtils.loadcpufreq.init 2012-01-06 23:35:32.759956550 > > > -0600 > > > @@ -119,7 +119,7 @@ > > > # K7 > > > MODULE=powernow-k7 > > > ;; > > > -15|16|17|20) > > > +15|16|17|20|21) > > > # K8 > > > MODULE=powernow-k8 > > > ;; > > I hope that you upload cpufrequtils with support for AMD processor families > 18 and 21 There has been some work to generate module aliases and uevents for x86 CPU features. This would allow udev to load cpufreq drivers just like any other device, removing the need for cpufrequtils to know which drivers handle which CPUs. It looks like this will be going into Linux 3.4 but I would be open to backporting this feature to 3.2 for wheezy. The changes I see in linux-next are: commit 644e9cbbe3fc032cc92d0936057e166a994dc246 Author: Andi Kleen Date: Thu Jan 26 00:09:05 2012 +0100 Add driver auto probing for x86 features v4 commit 3bd391f056df61e928de1680ff4a3e7e07e5b399 Author: Andi Kleen Date: Thu Jan 26 00:09:06 2012 +0100 crypto: Add support for x86 cpuid auto loading for x86 crypto drivers commit 267fc9788d0cdb77edafb506063f06961e1418f5 Author: Andi Kleen Date: Thu Jan 26 00:09:09 2012 +0100 HWMON: Convert via-cputemp to x86 cpuid autoprobing commit 9b38096fde5f9b93c3657911c3be7892cc155cbd Author: Andi Kleen Date: Thu Jan 26 00:09:10 2012 +0100 HWMON: Convert coretemp to x86 cpuid autoprobing commit fa8031aefec0cf7ea6c2387c93610d99d9659aa2 Author: Andi Kleen Date: Thu Jan 26 00:09:12 2012 +0100 cpufreq: Add support for x86 cpuinfo auto loading v4 (The crypto change should finally let us fix #568008.) Ben. -- Ben Hutchings Lowery's Law: If it jams, force it. If it breaks, it needed replacing anyway. signature.asc Description: This is a digitally signed message part
Bug#656899: Same problem too under SPARC64
On Fri, 2012-02-03 at 03:45 +, Ben Hutchings wrote: > On Thu, 2012-02-02 at 16:00 +0100, Denny Schierz wrote: > > hi, > > > > uname -a > > > > 2.6.32 #3 SMP Wed Feb 1 14:41:07 CET 2012 sparc64 GNU/Linux > > > > with self compiled kernel, but with Debian sources: > > > > linux-source-2.6.32 2.6.32-41 > > > > - > > [ 95.380528] mdadm: sending ioctl 20001261 to a partition! > > [ 95.451590] mdadm: sending ioctl 20001261 to a partition! > > [ 95.527711] mdadm: sending ioctl 20001261 to a partition! > > [ 95.598789] mdadm: sending ioctl 20001261 to a partition! > > [ 95.691778] mdadm: sending ioctl 20001261 to a partition! > > [ 95.772963] mdadm: sending ioctl 20001261 to a partition! > > -- > [...] > > Does the attached patch fix this? This change should be in the longterm > update 2.6.32.56 and we can put it into a stable update pretty soon if > necessary. Sorry, this patch probably isn't going to make any difference, as only processes *not* running as root are affected by the ioctl filtering. And the patch certainly won't remove the warning message. Denny, I suspect the RAID failure is due to an error condition that's detected at boot time and it would have showed up whenever you rebooted, regardless of any upgrade. You can probably check this by running an older version of the Debian installer in rescue mode. Ben. -- Ben Hutchings Lowery's Law: If it jams, force it. If it breaks, it needed replacing anyway. signature.asc Description: This is a digitally signed message part
Bug#656899: Same problem too under SPARC64
On Thu, 2012-02-02 at 16:00 +0100, Denny Schierz wrote: > hi, > > uname -a > > 2.6.32 #3 SMP Wed Feb 1 14:41:07 CET 2012 sparc64 GNU/Linux > > with self compiled kernel, but with Debian sources: > > linux-source-2.6.32 2.6.32-41 > > - > [ 95.380528] mdadm: sending ioctl 20001261 to a partition! > [ 95.451590] mdadm: sending ioctl 20001261 to a partition! > [ 95.527711] mdadm: sending ioctl 20001261 to a partition! > [ 95.598789] mdadm: sending ioctl 20001261 to a partition! > [ 95.691778] mdadm: sending ioctl 20001261 to a partition! > [ 95.772963] mdadm: sending ioctl 20001261 to a partition! > -- [...] Does the attached patch fix this? This change should be in the longterm update 2.6.32.56 and we can put it into a stable update pretty soon if necessary. Ben. -- Ben Hutchings Lowery's Law: If it jams, force it. If it breaks, it needed replacing anyway. diff -u b/drivers/scsi/sd.c b/drivers/scsi/sd.c --- b/drivers/scsi/sd.c +++ b/drivers/scsi/sd.c @@ -1004,7 +1004,7 @@ ret = scsi_verify_blk_ioctl(bdev, cmd); if (ret < 0) - return ret; + return -ENOIOCTLCMD; /* * If we are in the middle of error recovery, don't let anyone signature.asc Description: This is a digitally signed message part
Re: Allow building a subset of flavous in kernel/udeb build
On Thu, 2012-02-02 at 20:37 +, Ian Campbell wrote: > Hi, > > When doing kernel packaging bits work I often find it useful to hack the > package to only build a subset of the normal flavours (for speed etc). You can fairly easily build individual binary packages using the targets defined in debian/rules.gen. > However since udeb support was added this has stopped working (example > below for building only the kirkwood flavour on armel). The problem is > that we are still trying to build the udebs for flavours which are not > enabled and hence can't find the files. Right. And I would like to be able to test building udebs for just one flavour. That bit is definitely useful. [...] > Is it possible that the same issue exists for disabling featuresets? I > didn't look. Theoretically, but the installer never uses such a kernel configuration. Ben. -- Ben Hutchings Lowery's Law: If it jams, force it. If it breaks, it needed replacing anyway. signature.asc Description: This is a digitally signed message part
Re: Problem with it87 sensor in kernel 3.2.2 (sid).
On Thu, 2012-02-02 at 18:56 -0200, Sergio Cipolla wrote: > Hi, linux-image was updated today from 3.2.1 to 3.2.2 in sid and broke > sensors for it87 chip. > Before the update, messages said: > > > Feb 2 08:09:55 debian kernel: [ 11.269884] it87: Found IT8705F chip > at 0x290, revision 2 > Feb 2 08:09:55 debian kernel: [ 11.269895] it87: Beeping is > supported > Feb 2 08:09:55 debian kernel: [ 11.270045] it87 it87.656: Detected > broken BIOS defaults, disabling PWM interface > > > After the update: > > > Feb 2 13:01:54 debian kernel: [ 11.022946] it87: Found IT8705F chip > at 0x290, revision 2 > Feb 2 13:01:54 debian kernel: [ 11.022956] it87: Beeping is > supported > Feb 2 13:01:54 debian kernel: [ 11.023011] ACPI: resource it87 [io > 0x0295-0x0296] conflicts with ACPI region IP__ [io 0x295-0x296] > Feb 2 13:01:54 debian kernel: [ 11.023017] ACPI: If an ACPI driver > is available for this device, you should use it instead of the native > driver > > > > > So this is a regression as this problem used to happen in older > kernels and was solved > ( > http://www.lm-sensors.org/wiki/FAQ/Chapter3#Mysensorshavestoppedworkinginkernel2.6.31 > ). [...] No, you misunderstand. There was a deliberate change in Linux 2.6.31 that stops hwmon drivers from binding to devices that are used by the firmware (BIOS). It looks like that should have happened on this system as well, but for some reason did not. If you load the 'thermal' driver then you should be able to get the temperature (but unfortunately not fan or voltage) readings via the firmware. Ben. -- Ben Hutchings Lowery's Law: If it jams, force it. If it breaks, it needed replacing anyway. signature.asc Description: This is a digitally signed message part
Bug#658443: mkvmlinuz: [INTL:id] Indonesian debconf templates translation
Source: mkvmlinuz Version: 35 Severity: wishlist Tags: patch l10n -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear Maintainer, Please find attached an updated po-debconf translation of this package into indonesian. $ msgfmt --statistics -c -v -o /dev/null id.po id.po: 2 translated messages. Thanks. - -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (200, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-14-generic Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCAAGBQJPK0UyAAoJELmHbrCQs2xbfiAQAIyyThiV7MYdsvP7f/FsqzVH QXMIl+ISSWL7w5MNwmKuJq2dINBW7ub+eRsMLaOXFrNRLt5s9Fzd1nR/eKGrSvG5 Vo3MrRpgSoqgN7+z9Qhwc23tpKpCl4hah1tPJ5h+lOp8+g03OZAvh2M/yI7hdrF6 NtYJDpiLBqcI7A+uhZKmoxM+6aclbo39es9ikXMSl9/5nHP+mASNuJgMe8b3nmiV GQwXh2xnkpyUuu2eq7WCm3wyS6vr8cYCVSYR8bGEtpHyQuw+CQ0RAF8zjzogPAt1 qj/OsHI6DLo4Dg0SAB87TAipbhw8V2P3t5tIrc96KCSQB3FCpwdskB6HYfzmSM9X 09TfOeJ+tJQoaGkRFbHLD+2wqHegl2pBcjIbFWaxE5KnXY8GXjBSM/vNRdMnwT/T SiCGMbAvwTv/ba/URI0k+s6Sc7jtq1QrqRgy4VVP0KOD1QSsG9Ji6Y0Ao+UqeU5G 71AorVTPtG5RMn+vn9CguMI2PtKcnO6WkJiGEnrInO6VuKyppYPEeHJggFM/5NLY BM0AG1keHDPgTzt1ZHTEJ4nJzLiq4kHWyfB/qnrIJJsCrqD7VxS+/wjw/ULMXT6z VuB4spVtMXIaDzwKmHlOivRgChmlXxPkEJ+2lT8UuPCSt8IbrCI2ZETk++QyEz+2 NIz1VlE1le6c1BXXe7Po =2GFM -END PGP SIGNATURE- # #Translators, if you are not familiar with the PO format, gettext #documentation is worth reading, especially sections dedicated to #this format, e.g. by running: # info -n '(gettext)PO Files' # info -n '(gettext)Header Entry' # #Some information specific to po-debconf are available at #/usr/share/doc/po-debconf/README-trans # or http://www.debian.org/intl/l10n/po-debconf/README-trans # #Developers do not need to manually edit POT or PO files. # msgid "" msgstr "" "Project-Id-Version: mkvmlinuz 35\n" "Report-Msgid-Bugs-To: mkvmli...@packages.debian.org\n" "POT-Creation-Date: 2006-10-31 08:09+0100\n" "PO-Revision-Date: 2012-02-03 09:15+0700\n" "Last-Translator: Mahyuddin Susanto \n" "Language-Team: Debian Indonesia Translators \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "X-Poedit-Language: Indonesian\n" #. Type: select #. Description #: ../mkvmlinuz.templates:1001 msgid "Bootloader to use:" msgstr "Bootloader yang akan digunakan:" #. Type: select #. Description #: ../mkvmlinuz.templates:1001 msgid "Your PowerPC sub-architecture supports more than one bootloader, please select the one you want to use." msgstr "Sub-arsitektur PowerPC anda mendukung lebih dari satu bootloader, mohon pilih salah satu yang akan digunakan."
cpufrequtils doesn't support new AMD cpus
On Sat, Jan 07, 2012 at 03:30:04PM +0200, Touko Korpela wrote: > I think you should also add family 18 (AMD Fusion Llano). > http://www.phoronix.com/vr.php?view=16292 > > > On Sat, Jan 07, 2012 at 12:06:05AM -0600, Robert Keevil wrote: > > Package: cpufrequtils > > Version: 007-2 > > Severity: normal > > Tags: patch > > > > /etc/init.d/loadcpufreq does not support AMD Bulldozer CPUs, which have a > > CPU > > family of 21. The processor is supported by the powernow_k8 module. > > > --- debian/cpufrequtils.loadcpufreq.init.dist 2012-01-06 > > 23:35:24.867961318 -0600 > > +++ debian/cpufrequtils.loadcpufreq.init2012-01-06 23:35:32.759956550 > > -0600 > > @@ -119,7 +119,7 @@ > > # K7 > > MODULE=powernow-k7 > > ;; > > -15|16|17|20) > > +15|16|17|20|21) > > # K8 > > MODULE=powernow-k8 > > ;; I hope that you upload cpufrequtils with support for AMD processor families 18 and 21 -- 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/20120203021658.GA14357@tiikeri.vuoristo.local
Re: Bug#605090: Linux 3.2 in wheezy
On Fri, 3 Feb 2012, Christoph Anton Mitterer wrote: > Wasn't it once the case with PaX that packages have to be compiled > specially? Or some ELF headers added or so? Some shared libraries have code which can't be run without an executable stack, it's a small number of libraries that are written in assembler code. We want to allow running them but don't want to give all programs permission to execute code on the stack. From memory the GR Security option for this was to flag the rare executables that want an executable stack and are permitted to have it. The solution devised by libc/gcc upstream was to have a special assembly section in every shared object that doesn't require an executable stack and if an executable only loads shared objects that don't require it then the executable stack is disabled. Then we have SE Linux policy to prevent most programs from having an executable stack which means that if they are tricked into loading some of the rare libraries that need it then it doesn't do anything bad. The downside to the latter approach is that lots of shared objects which have some assembler code needed to be patched. The PaX approach involved less work. -- My Main Blog http://etbe.coker.com.au/ My Documents Bloghttp://doc.coker.com.au/ -- 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/201202031215.27866.russ...@coker.com.au
Re: Bug#658401: base: Atheros AR9285 Wi-Fi adapter not working on HP 630 notebook with Wheezy
reassign 658401 linux-2.6 thanks On Donnerstag, 2. Februar 2012, Illés Gábor wrote: > Package: base > Severity: important > > Dear Maintainer, > *** Please consider answering these questions, where appropriate *** > >* What led up to the situation? >* What exactly did you do (or not do) that was effective (or > ineffective)? >* What was the outcome of this action? >* What outcome did you expect instead? > > *** End of the template - remove these lines *** > > I have a fresh install of Wheezy on my new laptop, and noticed that my > Wi-Fi adapter doesn't work. I turned on and off several times the wireless > switch on the laptop's keyboard - no effect. Issued rfkill list command > shows that the switch does not do anything: phy0 is soft and hard blocked > too at all time (the hp-wifi Wireless LAN on the other way is stucked soft > - yes, hard - no state). I have Windows installed on a different > partition, haven't experienced any problem with the adapter. > > The device is showing at lspci list: > > 03:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless > Network Adapter (PCI-Express) (rev 01) > > > and the ath9k module are present: > lsmod: > > > mac80211 183047 1 ath9k > ath9k_common 12682 1 ath9k > ath9k_hw 281405 2 ath9k,ath9k_common > > > I have a wireless usb adapter - SMCWUSB-G type - and with the installation > of the appropriate package (zd1211) from the repo it had worked perfectly > - network manager and all that. > > Anyway, this is my first use of reportbug, so please excuse me, if i forget > something to add. > > > > -- System Information: > Debian Release: wheezy/sid > APT prefers testing > APT policy: (500, 'testing') > Architecture: amd64 (x86_64) > > Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores) > Locale: LANG=hu_HU.utf8, LC_CTYPE=hu_HU.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201202030133.05135.hol...@layer-acht.org
Re: Bug#605090: Linux 3.2 in wheezy
On Fri, 2012-02-03 at 00:34 +, Ben Hutchings wrote: > There is an easy way to benefit from it. Well still the user wouldn't know how to configure it... Actually I must admit that I haven't followed PaX/grsec now for some time (mainly due to the deb package being always out of date in sid). Wasn't it once the case with PaX that packages have to be compiled specially? Or some ELF headers added or so? And there were no execute features which are perhaps superseded to some extent (now that AMD64 has NX bit)... So what I mean in the end,... I'm surely not an expert with respect to the kernel, but at least I used to have my own .config since years,.. still it would mean quite some effort for me to get PaX/grsec running in a way that I for myself believe I've done it right. And this does not include tracing problems (I _very_ vaguely remember that one had to make exceptions e.g. for Java?) And that's why I think that such "special" frameworks like PaX/grsec, SElinux, Apparmor, Smack, etc. pp. make only sense if well supported by the distro, at least for some (blind guess:) 80-90% of all potential users. > You flatter us. General experience with kernel development does not > make someone an expert that is capable of understanding all the > implications of rebasing a patch or patch set that modifies many core > kernel features. Well come on Ben,.. you've already helped me so often with issues with the kernel,... you guys have at least some very good overview on everything! > > Well IMHO, at best, one should never need to rund anything from outside > > the Debian archives ;) > Wishing it so doesn't make it practically possible. Well.. so far I do :D Cheers, Chris. smime.p7s Description: S/MIME cryptographic signature
Processed: Re: Bug#658401: base: Atheros AR9285 Wi-Fi adapter not working on HP 630 notebook with Wheezy
Processing commands for cont...@bugs.debian.org: > reassign 658401 linux-2.6 Bug #658401 [base] base: Atheros AR9285 Wi-Fi adapter not working on HP 630 notebook with Wheezy Bug reassigned from package 'base' to 'linux-2.6'. > thanks Stopping processing here. Please contact me if you need assistance. -- 658401: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658401 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.132822919115395.transcr...@bugs.debian.org
Re: Bug#605090: Linux 3.2 in wheezy
On Fri, Feb 03, 2012 at 12:55:59AM +0100, Christoph Anton Mitterer wrote: > On Thu, 2012-02-02 at 12:18 +1100, Russell Coker wrote: > > The current approach of having a kernel patch package seems to work well. > Phew... well there are many people running at >stable... and for > them it does not... as the package seems more or less orphaned. > > Also,.. configuring something complex like grsec is probably nothing for > the end-user who, however, should have also an easy way to benefit from > it. There is an easy way to benefit from it. Download and build an official release. I assume 'make deb-pkg' works like in mainline Linux. > > It > > removes the need for involvement of the kernel and security teams > > (presumably > > security changes to the kernel will usually not require changes to the > > grsecurity patch) and allows the users to easily build their own kernels. > Well, even though it means [much] work for them,... wouldn't that > involvement be just the good thing? Having some real experts, looking > after everything?! You flatter us. General experience with kernel development does not make someone an expert that is capable of understanding all the implications of rebasing a patch or patch set that modifies many core kernel features. > > Spender suggested that people who want GRSecurity on Debian would be better > > off using a .deb he provides and working on user-space hardening. > Well IMHO, at best, one should never need to rund anything from outside > the Debian archives ;) Wishing it so doesn't make it practically possible. 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/20120203003410.gx12...@decadent.org.uk
Re: Bug#605090: Linux 3.2 in wheezy
On Thu, 2012-02-02 at 12:18 +1100, Russell Coker wrote: > The current approach of having a kernel patch package seems to work well. Phew... well there are many people running at >stable... and for them it does not... as the package seems more or less orphaned. Also,.. configuring something complex like grsec is probably nothing for the end-user who, however, should have also an easy way to benefit from it. > It > removes the need for involvement of the kernel and security teams (presumably > security changes to the kernel will usually not require changes to the > grsecurity patch) and allows the users to easily build their own kernels. Well, even though it means [much] work for them,... wouldn't that involvement be just the good thing? Having some real experts, looking after everything?! > Spender suggested that people who want GRSecurity on Debian would be better > off using a .deb he provides and working on user-space hardening. Well IMHO, at best, one should never need to rund anything from outside the Debian archives ;) Cheers, Chris. smime.p7s Description: S/MIME cryptographic signature
Processed: Re: [3.1.8 -> 3.2.1 regression] BUG: scheduling while atomic
Processing commands for cont...@bugs.debian.org: > found 656724 linux-2.6/3.2.2-1 Bug #656724 [linux-2.6] linux-image-3.2.0-1-amd64: After installing this kernel syslogd reports a call trace always the same: Code: c0 89 c5 ... Bug Marked as found in versions linux-2.6/3.2.2-1. > # regression > severity 656724 important Bug #656724 [linux-2.6] linux-image-3.2.0-1-amd64: After installing this kernel syslogd reports a call trace always the same: Code: c0 89 c5 ... Severity set to 'important' from 'normal' > merge 657526 656724 Bug#656724: linux-image-3.2.0-1-amd64: After installing this kernel syslogd reports a call trace always the same: Code: c0 89 c5 ... Bug#657526: linux-image-3.2.0-1-686-pae crashes after 50+ seconds Bug#657612: linux-image-3.2.0-1-amd64: scheduling while atomic: swapper/2/0/0x1100 Merged 656724 657526 657612. > quit Stopping processing here. Please contact me if you need assistance. -- 657526: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657526 657612: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657612 656724: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656724 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.132822007117776.transcr...@bugs.debian.org
Bug#656724: [3.1.8 -> 3.2.1 regression] BUG: scheduling while atomic
found 656724 linux-2.6/3.2.2-1 # regression severity 656724 important merge 657526 656724 quit Hi, Antonio-M. Corbi Bellot wrote: > [Subject: Bug#656724: bug still present with kernel 3.2.2-1] Please keep in mind that this appears as the subject line of an email in a crowded inbox, so it can be a good place to put valuable context. > I updated yesterday this faulty machine with latest > linux-image-3.2.0-1-amd64 (version 3.2.2-1) and I can confirm that this > bug is still present. Thanks! > Is there a boot option I can try to get rid of this messages and what > is causing them? Can you try this patch? http://bugs.debian.org/657612#17 Hope that helps, Jonathan -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120202220044.GE23410@burratino
Processed: Re: base: vmstat and /proc/loadavg disagree
Processing commands for cont...@bugs.debian.org: > found 620297 linux-2.6/2.6.32-30 Bug #620297 [linux-2.6] base: vmstat and /proc/loadavg disagree Bug Marked as found in versions linux-2.6/2.6.32-30. > found 620297 linux-2.6/2.6.32-36 Bug #620297 [linux-2.6] base: vmstat and /proc/loadavg disagree Bug Marked as found in versions linux-2.6/2.6.32-36. > tags 620297 + patch moreinfo Bug #620297 [linux-2.6] base: vmstat and /proc/loadavg disagree Added tag(s) moreinfo and patch. > quit Stopping processing here. Please contact me if you need assistance. -- 620297: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620297 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.13282190178730.transcr...@bugs.debian.org
Bug#620297: base: vmstat and /proc/loadavg disagree
found 620297 linux-2.6/2.6.32-30 found 620297 linux-2.6/2.6.32-36 tags 620297 + patch moreinfo quit Hi, Aman Gupta wrote: > The Ubuntu guys pulled the two upstream patches into their 2.6.32 > build, and the RedHat guys did the same in their 2.6.35 and 2.6.38 > builds. Is there anything preventing us from pulling in the patches > too? I'm coming in late; please forgive my ignorance. I assume the two patches in question are v2.6.35-rc1~521^2~16 (sched: Cure load average vs NO_HZ woes, 2010-08-22) v2.6.37-rc7~13^2~5 (sched: Cure more NO_HZ load average woes, 2010-11-30) The first does not apply cleanly to the 2.6.32.y tree but Lesław Kopeć backported it. The other applies cleanly on top (and can be retrieved in patch form with "git show v2.6.37-rc7~13^2~5"). So what would be most useful is: 1. Try a pristine 2.6.32.y kernel, to make sure it reproduces the problem. If you already have a git checkout of the kernel: cd linux git remote add stable \ git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git git fetch stable Otherwise: git clone -o stable \ git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git \ linux cd linux Then build and test: git checkout stable/linux-2.6.32.y cp /boot/config-$(uname -r) .config; # stock configuration make localmodconfig; # optional: minimize configuration make deb-pkg; # optionally with -j for parallel build dpkg -i ../ reboot 2. Try the patches, to make sure they fix it. cd linux git apply --index patch1 git apply --index patch2 make deb-pkg; # maybe with -j4 dpkg -i ../ reboot If the problem is reproducible with current 2.6.32.y and the patches fix it, we can submit them upstream so everyone benefits. Thanks and hope that helps, Jonathan -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120202214311.GB23410@burratino
Bug#629155: marked as done (Unable to scan anymore with a Fujitsu fi-4340C since squeeze update)
Your message dated Thu, 2 Feb 2012 15:21:35 -0600 with message-id <20120202212135.GA23410@burratino> and subject line Re: Unable to scan anymore with a Fujitsu fi-4340C since squeeze update has caused the Debian Bug report #629155, regarding Unable to scan anymore with a Fujitsu fi-4340C since squeeze update 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.) -- 629155: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629155 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sane-utils Version: 1.0.21-9 Severity: important Since I've updated my server on Debian Squeeze, my scanner Fujitsu fi-4340C stopped to work. I've tried to run with Debug option, and I get the following error when I use scanimage : [fujitsu] sane_open: start [fujitsu] sane_open: searching currently attached scanners [fujitsu] sane_open: device libusb:001:008 requested [fujitsu] sane_open: device libusb:001:008 found [fujitsu] connect_fd: start [fujitsu] connect_fd: opening USB device [sanei_usb] sanei_usb_open: trying to open device `libusb:001:008' USB error: could not set config 1: Connection timed out [sanei_usb] sanei_usb_open: libusb complained: could not set config 1: Connection timed out [fujitsu] connect_fd: could not open device: 4 [fujitsu] connect_fd: finish scanimage: open of device fujitsu:libusb:001:008 failed: Invalid argument [fujitsu] sane_exit: start [fujitsu] disconnect_fd: start [fujitsu] disconnect_fd: finish [fujitsu] sane_exit: finish The scan worked perfectly before with lenny, I've also tried to compile manually version 1.0.22 from debian unstable, compilation was a success, but scanimage give the same error. Thanks all for your help. Olivier. -- System Information: Debian Release: 6.0.1 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages sane-utils depends on: ii adduser3.112+nmu2add and remove users and groups ii debconf [debconf-2.0] 1.5.36.1 Debian configuration management sy ii libavahi-client3 0.6.27-2+squeeze1 Avahi client library ii libavahi-common3 0.6.27-2+squeeze1 Avahi common library ii libc6 2.11.2-10 Embedded GNU C Library: Shared lib ii libieee1284-3 0.2.11-6 cross-platform library for paralle ii libsane1.0.21-9 API library for scanners ii libusb-0.1-4 2:0.1.12-16 userspace USB programming library ii update-inetd 4.38+nmu1 inetd configuration file updater sane-utils recommends no packages. Versions of packages sane-utils suggests: ii avahi-daemon 0.6.27-2+squeeze1 Avahi mDNS/DNS-SD daemon pn unpaper(no description available) -- debconf information: sane-utils/saned_run: false sane-utils/saned_scanner_group: true --- End Message --- --- Begin Message --- Jonathan Nieder wrote: > Please provide: > > - version numbers for the newest kernel you know of that did work >(did not time out) and the oldest and newest kernels you know of >that didn't. Closing due to lack of response. But if you have time to work on this later, please feel free to let us know, and we'll be happy to reopen it. Thanks, Jonathan --- End Message ---
Problem with it87 sensor in kernel 3.2.2 (sid).
Hi, linux-image was updated today from 3.2.1 to 3.2.2 in sid and broke sensors for it87 chip. Before the update, messages said: Feb 2 08:09:55 debian kernel: [ 11.269884] it87: Found IT8705F chip at 0x290, revision 2 Feb 2 08:09:55 debian kernel: [ 11.269895] it87: Beeping is supported Feb 2 08:09:55 debian kernel: [ 11.270045] it87 it87.656: Detected broken BIOS defaults, disabling PWM interface After the update: Feb 2 13:01:54 debian kernel: [ 11.022946] it87: Found IT8705F chip at 0x290, revision 2 Feb 2 13:01:54 debian kernel: [ 11.022956] it87: Beeping is supported Feb 2 13:01:54 debian kernel: [ 11.023011] ACPI: resource it87 [io 0x0295-0x0296] conflicts with ACPI region IP__ [io 0x295-0x296] Feb 2 13:01:54 debian kernel: [ 11.023017] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver So this is a regression as this problem used to happen in older kernels and was solved ( http://www.lm-sensors.org/wiki/FAQ/Chapter3#Mysensorshavestoppedworkinginkernel2.6.31 ). I was about to open a bug report but reportbug was unable to connect to Debian BTS. So I would like to know if this is really a bug or if I should find some workaround for it. Thank you very much.
Allow building a subset of flavous in kernel/udeb build
Hi,
When doing kernel packaging bits work I often find it useful to hack the
package to only build a subset of the normal flavours (for speed etc).
However since udeb support was added this has stopped working (example
below for building only the kirkwood flavour on armel). The problem is
that we are still trying to build the udebs for flavours which are not
enabled and hence can't find the files.
The attached patches allow the kernel build to propagate the flavours it
is interested in to the kernel-wedge side of things and therefore avoid
attempting to build the uninteresting udebs.
I tried to make it such that it was a linux packaging only change but
that would seem to involve parsing the package names output by
gen-control in order to determine which are related to the flavours we
are actually building so we can include only those in the udeb_packages
list, which becomes $(PACKAGE_NAMES) in rules.gen. It seemed like it
would be a bit fragile, although I didn't actually build it.
Since this is a developer "feature" I don't think we particularly need
to bump the build deps for it.
Thoughts?
Is it possible that the same issue exists for disabling featuresets? I
didn't look.
Cheers,
Ian.
/usr/bin/make -f debian/rules.real install-udeb_armel ABINAME='3.2.0-1'
ABINAME_PART='-1' ARCH='armel' KERNEL_ARCH='arm'
SOURCEVERSION='3.2.1-2.1local2' UPSTREAMVERSION='3.2' VERSION='3.2'
PACKAGE_NAMES='kernel-image-3.2.0-1-iop32x-di [...dozens...]'
make[2]: Entering directory
`/local/scratch/ianc/devel/debian/linux-2.6-3.2.1'
dh_testdir
dh_prep
kernel-wedge install-files 3.2.0-1
could not find kernel image
at /usr/share/kernel-wedge/commands/install-files line 103, line
2.
make[2]: *** [install-udeb_armel] Error 2
make[2]: Leaving directory
`/local/scratch/ianc/devel/debian/linux-2.6-3.2.1'
make[1]: *** [binary-arch_armel] Error 2
make[1]: Leaving directory
`/local/scratch/ianc/devel/debian/linux-2.6-3.2.1'
make: *** [binary-arch] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-arch gave error
exit status 2
--
Ian Campbell
Be warned, I have a keyboard I can use to beat luser's heads
in, and then continue to use... (=:]
Mercury: Oh, an IBM. :)
diff -u linux-2.6-3.2.1/debian/rules.real linux-2.6-3.2.1/debian/rules.real
--- linux-2.6-3.2.1/debian/rules.real
+++ linux-2.6-3.2.1/debian/rules.real
@@ -467,6 +467,7 @@
install-udeb_$(ARCH): export KW_DEFCONFIG_DIR=debian/installer
install-udeb_$(ARCH): export KW_CONFIG_DIR=debian/installer/$(ARCH)
+install-udeb_$(ARCH): export KW_FLAVOURS=$(FLAVOURS)
install-udeb_$(ARCH): DH_OPTIONS=$(PACKAGE_NAMES:%=-p%)
install-udeb_$(ARCH):
dh_testdir
diff -u linux-2.6-3.2.1/debian/bin/gencontrol.py linux-2.6-3.2.1/debian/bin/gencontrol.py
--- linux-2.6-3.2.1/debian/bin/gencontrol.py
+++ linux-2.6-3.2.1/debian/bin/gencontrol.py
@@ -104,12 +104,17 @@
# Add udebs using kernel-wedge
installer_def_dir = 'debian/installer'
installer_arch_dir = os.path.join(installer_def_dir, arch)
+flavours = []
+for featureset in self.config['base', arch].get('featuresets', ()):
+for flavour in self.config['base', arch, featureset]['flavours']:
+if flavour not in flavours: flavours += [flavour]
if os.path.isdir(installer_arch_dir):
kw_env = os.environ.copy()
kw_env['KW_DEFCONFIG_DIR'] = installer_def_dir
kw_env['KW_CONFIG_DIR'] = installer_arch_dir
+kw_env['KW_FLAVOURS'] = ' '.join(flavours)
kw_proc = subprocess.Popen(
['kernel-wedge', 'gen-control',
self.abiname],
stdout=subprocess.PIPE,
env=kw_env)
@@ -126,9 +132,10 @@
makefile.add(
'binary-arch_%s' % arch,
cmds=["$(MAKE) -f debian/rules.real install-udeb_%s %s "
-"PACKAGE_NAMES='%s'" %
+"PACKAGE_NAMES='%s' FLAVOURS='%s'" %
(arch, makeflags,
- ' '.join(p['Package'] for p in udeb_packages))])
+ ' '.join(p['Package'] for p in udeb_packages),
+ ' '.join(flavours))])
def do_featureset_setup(self, vars, makeflags, arch, featureset, extra):
config_base = self.config.merge('base', arch, featureset)
diff --git a/commands/gen-control b/commands/gen-control
index afffa2d..9f3b68d 100755
--- a/commands/gen-control
+++ b/commands/gen-control
@@ -13,6 +13,7 @@ my %excluded;
my $defconfigdir = ($ENV{KW_DEFCONFIG_DIR} || '/usr/share/kernel-wedge');
my $configdir = ($ENV{KW_CONFIG_DIR} || '.');
+my @flavours = split(' ', $ENV{KW_FLAVOURS} || '');
my $fixkernelversion = $ARGV[0];
@@ -33,6 +34,8 @@ while () {
if (! length $arch || ! length $kernelversion || ! length $flavour) {
die "parse error";
}
+ next if ( @flavours && !grep { $_ eq $flavour} @flavours );
+
if (defined($fixkernelversion)) {
$ke
Bug#620297: base: vmstat and /proc/loadavg disagree
I'm seeing these issues as well. The Ubuntu guys pulled the two upstream patches into their 2.6.32 build, and the RedHat guys did the same in their 2.6.35 and 2.6.38 builds. Is there anything preventing us from pulling in the patches too? Aman -- 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/CAK=uwuzlojgy0bcwhyfpvtu5zmgjnkquw_v7dvdsff-0ywk...@mail.gmail.com
Processed: Re: Baud rate of FTDI USB-to-serial converter not initialized
Processing commands for cont...@bugs.debian.org: > tags 658164 + upstream patch fixed-upstream Bug #658164 [linux-2.6] linux-image-3.1.0-1-amd64: Baud rate of FTDI USB-to-serial converter not initialized Added tag(s) fixed-upstream and patch. > quit Stopping processing here. Please contact me if you need assistance. -- 658164: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658164 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.132820788432191.transcr...@bugs.debian.org
Bug#658164: Baud rate of FTDI USB-to-serial converter not initialized
tags 658164 + upstream patch fixed-upstream quit Andreas Fried wrote: > sorry for not coming back to you earlier, I did not have access to the > oscilloscope until now. The issue is resolved by the folowing commit to > the kernel: > > 108e02b12921078a59dcacd048079ece48a4a983 > (usb-ftdi_sio-fix-initial-baud-rate.patch) > > Applying this as a patch to the kernel solves the problem for me. Thanks. Just for the record, applying as a patch to which kernel version? Anyway, as you noticed, the patch in question is queued for 3.2.3. Thanks for finding it. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120202183734.GA19520@burratino
Bug#658164: Baud rate of FTDI USB-to-serial converter not initialized
Hello, sorry for not coming back to you earlier, I did not have access to the oscilloscope until now. The issue is resolved by the folowing commit to the kernel: 108e02b12921078a59dcacd048079ece48a4a983 (usb-ftdi_sio-fix-initial-baud-rate.patch) Applying this as a patch to the kernel solves the problem for me. Thank you very much for your time, Andreas -- 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/4f2acb58.2020...@0xaf.de
[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 #657302 (http://bugs.debian.org/657302) # Bug title: linux-image-3.2.0-1-amd64: No more sound # * http://bugzilla.kernel.org/show_bug.cgi?id=42588 # * remote status changed: (?) -> RESOLVED # * remote resolution changed: (?) -> CODE-FIX # * closed upstream tags 657302 + fixed-upstream usertags 657302 + status-RESOLVED resolution-CODE-FIX 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/20120202164203.31936.85640.btsl...@busoni.debian.org
Processed: [bts-link] source package linux-2.6
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package linux-2.6 > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). > # remote status report for #657302 (http://bugs.debian.org/657302) > # Bug title: linux-image-3.2.0-1-amd64: No more sound > # * http://bugzilla.kernel.org/show_bug.cgi?id=42588 > # * remote status changed: (?) -> RESOLVED > # * remote resolution changed: (?) -> CODE-FIX > # * closed upstream > tags 657302 + fixed-upstream Bug #657302 [linux-2.6] linux-image-3.2.0-1-amd64: No more sound Added tag(s) fixed-upstream. > usertags 657302 + status-RESOLVED resolution-CODE-FIX Bug#657302: linux-image-3.2.0-1-amd64: No more sound There were no usertags set. Usertags are now: resolution-CODE-FIX status-RESOLVED. > thanks Stopping processing here. Please contact me if you need assistance. -- 657302: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657302 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.132820092415190.transcr...@bugs.debian.org
Re: thoughts on Unix and how to overcome its shortcomings
On Thu, 2012-02-02 at 14:28 +0530, dE . wrote: [...] > Also you should discuss about this in the debian-project and > debian-desktop mailing lists -- you left these 2, they were the most > relevant. I think the most appropriate forum would be Nader's blog. Ben. -- Ben Hutchings Lowery's Law: If it jams, force it. If it breaks, it needed replacing anyway. signature.asc Description: This is a digitally signed message part
Bug#656899: Same problem too under SPARC64
hi, uname -a 2.6.32 #3 SMP Wed Feb 1 14:41:07 CET 2012 sparc64 GNU/Linux with self compiled kernel, but with Debian sources: linux-source-2.6.32 2.6.32-41 - [ 95.380528] mdadm: sending ioctl 20001261 to a partition! [ 95.451590] mdadm: sending ioctl 20001261 to a partition! [ 95.527711] mdadm: sending ioctl 20001261 to a partition! [ 95.598789] mdadm: sending ioctl 20001261 to a partition! [ 95.691778] mdadm: sending ioctl 20001261 to a partition! [ 95.772963] mdadm: sending ioctl 20001261 to a partition! -- # cat /proc/mdstat Personalities : [raid1] [raid10] [raid6] [raid5] [raid4] [multipath] md0 : active raid1 sda2[0] sdb2[1] 71190951 blocks super 1.2 [2/2] [UU] --- Disk /dev/sda (Sun disk label): 255 heads, 63 sectors, 8924 cylinders Units = cylinders of 16065 * 512 bytes Device FlagStart EndBlocks Id System /dev/sda1 061489982+ 1 Boot /dev/sda261 8924 71192047+ fd Linux raid autodetect /dev/sda3 0 8924 716820305 Whole disk Disk /dev/sdb (Sun disk label): 255 heads, 63 sectors, 8924 cylinders Units = cylinders of 16065 * 512 bytes Device FlagStart EndBlocks Id System /dev/sdb1 061489982+ 83 Linux native /dev/sdb261 8924 71192047+ fd Linux raid autodetect /dev/sdb3 0 8924 716820305 Whole disk --- syslog: Feb 2 06:26:08 mpt-statusd: detected non-optimal RAID status Feb 2 06:36:08 mpt-statusd: detected non-optimal RAID status Feb 2 06:46:08 mpt-statusd: detected non-optimal RAID status and the kernel remounted my "/" readonly ... but found nothing about that in the log. cu denny signature.asc Description: Message signed with OpenPGP using GPGMail
Bug#656724: bug still present with kernel 3.2.2-1
I updated yesterday this faulty machine with latest linux-image-3.2.0-1-amd64 (version 3.2.2-1) and I can confirm that this bug is still present. Is there a boot option I can try to get rid of this messages and what is causing them? TIA. Antonio Corbi -- 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/20120202160507.7bc7f...@pbell-acb.dlsi.ua.es
Bug#657302: [3.1.8 -> 3.2.1 regression] No more sound
On 02/02/12 01:08, Jonathan Nieder wrote: Guy Roussin wrote: I have a Dell laptop and i get the same bug : no more sound with kernel 3.2. Is the patch fix this problem on Dell laptop? No, it's for Asus machines only. Please file a separate bug. Thanks much, Jonathan No, it maybe the same chip and/or driver. This will help point out the problem. -- 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/4f2a5786.7070...@gmail.com
Re: thoughts on Unix and how to overcome its shortcomings
On 02/01/12 19:38, Nader wrote: Hello People: I am a present Linux user and a computer enthusiast of a long time. Through my long experience with computers and recently Linux I have come across some points that I firmly believe that can make a difference in Linux's popularity. I am attaching the small article that I have written hereto. Please read through it and let me know your feedback. I don't even mind if some of you find it totally useless as long as I get a feedback. I love Unix and all people associated with it by any means as long as they are working on or using a free GNU Unix type. That is why I wrote this article because I want to see it grow as you all do. So please read through it without bias and let me know if you find it of any value. Thanks for your time and interest. All the best Firstly, you should know the abbreviation of GNU -- GNU is not Unix. The no. 1 reason for bad popularity of Linux/BSD on the Desktops is difficult administration (or initial setup, this includes installation, tweaking the UI etc... etc... etc...). Second comes the DE -- Gnome 2 is dead, and with it, gnome as a whole too is dead Then comes the design -- Gnome 3/shell is a proof that Developers cant be designers. We need designers and psychologist as contributer too, but I don't think we have much of them in the community. The hardware compatibility -- AH! We need vendor support, and there're only going to support if there is *some* usage. And actually, the UI really doesnt matter to 90% of the the end users until it follows traditional norms (taskbar, correct WM, minimize, maximize buttons etc...). You might find the bad administration a disadvantage, but for many it's a good, and this's where the scope lies. ;-) Also you should discuss about this in the debian-project and debian-desktop mailing lists -- you left these 2, they were the most relevant. -- 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/4f2a5037.6030...@gmail.com
Processed: Re: [2.6.32 -> 2.6.37 regression] resume from disk reboots sometimes
Processing commands for cont...@bugs.debian.org: > tags 609926 + moreinfo Bug #609926 [linux-2.6] linux-image-2.6.37-trunk-686: resume from disk reboots sometimes Added tag(s) moreinfo. > End of message, stopping processing here. Please contact me if you need assistance. -- 609926: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609926 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.132818711814627.transcr...@bugs.debian.org
Processed: Re: 180-second hang loading ipmi_si module
Processing commands for cont...@bugs.debian.org: > tags 607533 + moreinfo Bug #607533 [linux-2.6] udev hangs at boot for 180 sec because of a "C$R570" bios version Added tag(s) moreinfo. > End of message, stopping processing here. Please contact me if you need assistance. -- 607533: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607533 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.132818678812687.transcr...@bugs.debian.org
Processed: Re: linux-image-2.6.32-5-686: Laptop won't resume after suspend to disk
Processing commands for cont...@bugs.debian.org: > tags 607288 + moreinfo Bug #607288 [linux-2.6] linux-image-2.6.32-5-686: Laptop won't resume after suspend to disk Added tag(s) moreinfo. > End of message, stopping processing here. Please contact me if you need assistance. -- 607288: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607288 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.132818671611471.transcr...@bugs.debian.org
Processed: Re: sysfs: cannot create duplicate filename
Processing commands for cont...@bugs.debian.org: > tags 605472 + moreinfo Bug #605472 [linux-2.6] sysfs: cannot create duplicate filename Added tag(s) moreinfo. > End of message, stopping processing here. Please contact me if you need assistance. -- 605472: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=605472 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.132818656510927.transcr...@bugs.debian.org
Processed: Re: linux-image-2.6.32-4-686: soft lockups with radeon KMS
Processing commands for cont...@bugs.debian.org: > found 578912 linux-2.6/2.6.32-21 Bug #578912 [linux-2.6] linux-image-2.6.32-4-686: soft lockups with radeon KMS Bug Marked as found in versions linux-2.6/2.6.32-21. > retitle 578912 [squeeze] [R520] soft lockups with radeon KMS Bug #578912 [linux-2.6] linux-image-2.6.32-4-686: soft lockups with radeon KMS Changed Bug title to '[squeeze] [R520] soft lockups with radeon KMS' from 'linux-image-2.6.32-4-686: soft lockups with radeon KMS' > End of message, stopping processing here. Please contact me if you need assistance. -- 578912: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=578912 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.132818644310443.transcr...@bugs.debian.org
