Bug#595711: linux-image-2.6.26-2-xen-686: Wrong free memory values for xen kernel with xenballoon use
On Mon, 2010-09-06 at 04:03 +0400, George Shuklin wrote:
I belive, this somehow related to difference in drivers/xen/balloon.c,
gentoo/SUSE version have some lines like
totalram_pages--;
(in balloon_append() function)
and
totalram_pages++;
(in balloon_retrieve() function)
Those lines are in Gentoo kernel (linux-2.6.34-xen) but absent in
Debian (linux-image-2.6.26-2-xen-686)
Is the Gentoo kernel pvops or classic-Xen patches?
Are you sure you are using the classic-Xen
(linux-image-...-xen-{686,amd}) kernel rather than the pvops one
(linux-image-...-686-bigmem, no 64 bit pvops in Lenny)?
I wasn't aware that it applied to the classic-Xen case but the
difference you describe sounds like this commit from upstream pvops:
http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commit;h=3d65c9488cadd2f11bd4d60c7266e639ece5d0d6
Probably for a 2.6.26 classic-Xen kernel you'd need to adjust the path
to drivers/xen/balloon/balloon.c and perhaps tweak some context a bit
but the concept should still apply.
Ian.
--
Ian Campbell
Never laugh at live dragons.
-- Bilbo Baggins [J.R.R. Tolkien, The Hobbit]
signature.asc
Description: This is a digitally signed message part
Bug#595521: bug 595521
On Mon, 6 Sep 2010, Borden Rhodes wrote: Yes. We'll sort things out before release, but from KMS is not a critical kernel bug. Well it's critical that our computers return to a _bootable_ state and not locking up where everything, including the keyboard, is unresponsive. May we at least get a workaround until the higher brains decide what to do? I'd suggest either downgrading the kernel or forcing the vesa driver if you can live without accelerated video. Put this in /etc/X11/xorg.conf: Section Device Identifier foo Driver vesa EndSection -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/alpine.deb.2.00.1009060913510.21...@pandora.retrosnub.co.uk
tgt_1.0.4-2_multi.changes ACCEPTED
Accepted: tgt_1.0.4-2.debian.tar.gz to main/t/tgt/tgt_1.0.4-2.debian.tar.gz tgt_1.0.4-2.dsc to main/t/tgt/tgt_1.0.4-2.dsc tgt_1.0.4-2_i386.deb to main/t/tgt/tgt_1.0.4-2_i386.deb Override entries for your package: tgt_1.0.4-2.dsc - source net tgt_1.0.4-2_i386.deb - optional net Announcing to debian-devel-chan...@lists.debian.org Closing bugs: 589716 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1osx7l-0001gf...@franck.debian.org
Bug#589716: marked as done (tgtd target will not start unless it's configured with allow-in-use yes)
Your message dated Mon, 06 Sep 2010 08:32:21 +
with message-id e1osx7l-0001gl...@franck.debian.org
and subject line Bug#589716: fixed in tgt 1:1.0.4-2
has caused the Debian Bug report #589716,
regarding tgtd target will not start unless it's configured with allow-in-use
yes
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.)
--
589716: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589716
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: tgt
Version: 1:1.0.4-1
Severity: important
tgt-admin will not start a target unless we specify the allow-in-use
yes directive in the target declaration. It complains that the device
is in use, although I am positive it is not. Specifying allow-in-use
yes is not recommended, and doing so is not really satisfactory.
This appears to have been caused by a faulty system call which appears
to be corrected by the below patch.
Thanks,
Chris
--- tgt-1.0.4/scripts/tgt-admin 2010-04-29 01:16:34.0 -0500
+++ tgt-1.0.4/scripts/tgt-admin 2010-07-20 04:32:55.603760363 -0500
@@ -1166,7 +1166,7 @@
# Check if userspace uses this device
my $lsof_check = check_exe(lsof);
if ($lsof_check ne 1) {
- system(lsof $backing_store /dev/null);
+ system(lsof $backing_store /dev/null 21);
my $exit_value = $? 8;
if ($exit_value eq 0) {
execute(# Device $backing_store is used (already tgtd
target?).);
---End Message---
---BeginMessage---
Source: tgt
Source-Version: 1:1.0.4-2
We believe that the bug you reported is fixed in the latest version of
tgt, which is due to be installed in the Debian FTP archive:
tgt_1.0.4-2.debian.tar.gz
to main/t/tgt/tgt_1.0.4-2.debian.tar.gz
tgt_1.0.4-2.dsc
to main/t/tgt/tgt_1.0.4-2.dsc
tgt_1.0.4-2_i386.deb
to main/t/tgt/tgt_1.0.4-2_i386.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 589...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ben Hutchings b...@decadent.org.uk (supplier of updated tgt package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 05 Sep 2010 22:13:52 +0100
Source: tgt
Binary: tgt
Architecture: i386 source
Version: 1:1.0.4-2
Distribution: unstable
Urgency: low
Maintainer: Debian Kernel Team debian-kernel@lists.debian.org
Changed-By: Ben Hutchings b...@decadent.org.uk
Closes: 589716
Description:
tgt- Linux SCSI target user-space tools
Changes:
tgt (1:1.0.4-2) unstable; urgency=low
.
* Fix bashism in tgt-admin, thanks to Chris Cheney (Closes: #589716)
Checksums-Sha1:
2a8d8c70bbaf9ec491144e07678e9c6c4a15ac63 1735 tgt_1.0.4-2.dsc
52c98d2f42a84655b039974cfbef01483ce9a8f2 3963 tgt_1.0.4-2.debian.tar.gz
d91ea26959e3920b4bcab4c9e8f95b2ba458887b 24 tgt_1.0.4-2_i386.deb
Checksums-Sha256:
8a6320464a0d04eeb474881db980073edec1323fc433826f385dfd594a1bdff0 1735
tgt_1.0.4-2.dsc
2d5256746e4013bdd6e286387a3bbcba9ba61fb80b2c2f304f32d44712f4c4c9 3963
tgt_1.0.4-2.debian.tar.gz
aa8e895cb32961250b2e34a9ca4531b6914f9af4e2d6178a6a5db32e6351bb89 24
tgt_1.0.4-2_i386.deb
Files:
5ae12ccb4204c35666f179439bea9ce3 1735 net optional tgt_1.0.4-2.dsc
463a19bb0002399ec5fac0e2c8cd4fb8 3963 net optional tgt_1.0.4-2.debian.tar.gz
3f781054861cad76e46712000b93e268 24 net optional tgt_1.0.4-2_i386.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
iQIVAwUBTIQMaue/yOyVhhEJAQoCyQ/9HMTLWrgZvc2E42HTRUzQhAChOxzUUJ3u
VlJ+X0MunBZsyHEJRCMcgO9nwoo1M6YsNN6zYhcPMnZNPg531z5jSjzG5nzz1eAX
W4AZr2OBRtFO7lOR43aWXQAKNrS73XBl3COKozyZB+z531FG1i/i764z4xyah++l
EiV5drmFv7N4t7lThzt2oIV4pcMmC64mNdh5jCxwFQ3sXAKdlOo2FwWNyDfZ6wC9
HpiNXOvEZXnEFbM7WlWbULpk3c/uleFhnkBCWy1cjzKrygSwgNG325MtdIaTPJoC
pbx2i1bRN3zxg4y6Ray9obgfB69FVSaN0G2FvpJVJGKhFZ6MGgp+aoTKHDoZAsEv
YkZR8TJ/bEjtbWQ/YnQU+dKXjBP/qnrBZqJ4S8+2jeN2ZaMgQ5PSqFDA2AHcq5uf
YRYA0BGqk+Lhi45XCJuLD6yj9+1N3WMHcVCl28mMHlofXD3xYSLvDUSw4Gl92TvP
SXf7iENbDXnYFn4F1UmB+xMIf1FhwYwzEjlXefKgGA7dQkU7Tb7vMsPO/c1QdBjb
ugW2L1UvKXN4Yeom1NKS5gsEelzFcVhfDzk7/GQCR9nTNsRVZIvtgvquN5r2pVfN
bQ5Q8SbeoyTQfA0ojra0w5pLwZAVtxLupjAeaFMcgnNLXZAeR5VTLhnD3bRrDSxA
/+iAPPP7CUk=
=al5F
-END PGP SIGNATURE-
---End Message---
please suck in 2.6.32-dobrovolskiy.1
Hi guys, Could you please get the latest 2.6.32-dobrovolskiy.1 kernel from git.kernel.org? It is based on latest -stable (i.e. 2.6.32.21) and, among the other things, includes a feature that should help fixing Debian bug #576227. Thanks, Kir. -- 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/4c84a9ab.6010...@openvz.org
google-chrome again, Re: kernel bug (?)
hi list, hi Ben, this is a followup to the message I posted in March, see http://lists.debian.org/debian-kernel/2010/03/msg00667.html With the latest update of the linux kernel and google-chrome, namely linux-image-2.6.26-2-openvz-amd64 2.6.26-25 google-chrome-stable 6.0.472.53-r57914 the bug has changed. Now when I try to start google-chrome, it immediatly dies, printing Failed to move to new PID namespace: File exist and the following backtrace appears in the kernel log, [15268.091684] kobject_add_internal failed for lo with -EEXIST, don't try to register things with the same name in the same directory. [15268.091693] Pid: 14873, comm: chrome-sandbox Tainted: P 2.6.26-2-openvz-amd64 #1 [15268.091696] [15268.091698] Call Trace: [15268.091715] [8030fc29] kobject_add_internal+0x13f/0x17e [15268.091721] [80310066] kobject_add+0x74/0x7c [15268.091733] [8029f654] percpu_populate+0x77/0x9e [15268.091738] [8030e7e5] __next_cpu+0x19/0x26 [15268.091742] [8030fa80] kobject_get+0x12/0x17 [15268.091748] [80377e35] get_device+0x17/0x1f [15268.091752] [80378456] device_add+0x9b/0x53f [15268.091757] [8030f872] kobject_init_internal+0x12/0x2c [15268.091764] [803b1f3a] register_netdevice+0x282/0x358 [15268.091769] [803b2049] register_netdev+0x39/0x46 [15268.091775] [8037eb71] loopback_net_init+0x3e/0x75 [15268.091781] [803ae61a] setup_net+0x85/0xe6 [15268.091787] [803aee28] copy_net_ns+0x49/0xb5 [15268.091793] [8024ae29] create_new_namespaces+0x125/0x1da [15268.091800] [8024b0d2] copy_namespaces+0x66/0x9c [15268.091807] [80233759] copy_process+0xa05/0x11fc [15268.091818] [8023404d] do_fork_pid+0xfd/0x2aa [15268.091822] [80221f52] do_page_fault+0x5c9/0x9ab [15268.091828] [8042350a] thread_return+0xc6/0x107 [15268.091836] [8020c00a] system_call_after_swapgs+0x8a/0x8f [15268.091840] [8023420b] do_fork+0x11/0x13 [15268.091844] [8020c397] ptregscall_common+0x67/0xb0 If I use the command line $ google-chrome -no-sandbox then chrome starts fine (altough it complains about less security) a. ps: please CC me, I am not on the list -- 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/20100906102636.ga13...@tonelli.sns.it
Processed: Re: Bug#595502 closed by Ben Hutchings b...@decadent.org.uk (Re: Bug#595502: linux-image-2.6.32-5-mckinley: panics while loading INIT, IOMMU out of mapping resources)
Processing commands for cont...@bugs.debian.org:
reopen 595502
Bug #595502 {Done: Ben Hutchings b...@decadent.org.uk}
[linux-image-2.6.32-5-mckinley] linux-image-2.6.32-5-mckinley: panics while
loading INIT, IOMMU out of mapping resources
'reopen' may be inappropriate when a bug has been closed with a version;
you may need to use 'found' to remove fixed versions.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
595502: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595502
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.12837732339948.transcr...@bugs.debian.org
Re: google-chrome again, Re: kernel bug (?)
On Mon, 2010-09-06 at 12:26 +0200, A Mennucc wrote: hi list, hi Ben, this is a followup to the message I posted in March, see http://lists.debian.org/debian-kernel/2010/03/msg00667.html With the latest update of the linux kernel and google-chrome, namely linux-image-2.6.26-2-openvz-amd64 2.6.26-25 google-chrome-stable 6.0.472.53-r57914 the bug has changed. Now when I try to start google-chrome, it immediatly dies, printing Failed to move to new PID namespace: File exist and the following backtrace appears in the kernel log, [15268.091684] kobject_add_internal failed for lo with -EEXIST, don't try to register things with the same name in the same directory. [15268.091693] Pid: 14873, comm: chrome-sandbox Tainted: P 2.6.26-2-openvz-amd64 #1 [15268.091696] [15268.091698] Call Trace: [15268.091715] [8030fc29] kobject_add_internal+0x13f/0x17e [15268.091721] [80310066] kobject_add+0x74/0x7c [15268.091733] [8029f654] percpu_populate+0x77/0x9e [15268.091738] [8030e7e5] __next_cpu+0x19/0x26 [15268.091742] [8030fa80] kobject_get+0x12/0x17 [15268.091748] [80377e35] get_device+0x17/0x1f [15268.091752] [80378456] device_add+0x9b/0x53f [15268.091757] [8030f872] kobject_init_internal+0x12/0x2c [15268.091764] [803b1f3a] register_netdevice+0x282/0x358 [15268.091769] [803b2049] register_netdev+0x39/0x46 [15268.091775] [8037eb71] loopback_net_init+0x3e/0x75 [15268.091781] [803ae61a] setup_net+0x85/0xe6 [...] This is OpenVZ-specific broken-ness. NET_NS is not enabled in the regular kernel, for good reasons. 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#594845: Acknowledgement (linux-image-2.6.32-5-amd64: kernel BUG at /build/buildd-linux-2.6_2.6.32-20-amd64-lNUT1p/..../fs/sysfs/file.c:539)
On Sun, 2010-09-05 at 01:45 +0100, Ben Hutchings wrote: Are you quite sure you used the modified kernel? Nope. 'cat /proc/version' will tell you for sure which version you are running. $ cat /proc/version Linux version 2.6.32-5-amd64 (Debian 2.6.32-20.2) (russell-deb...@stuart.id.au) (gcc version 4.3.5 (Debian 4.3.5-2) ) #1 SMP Mon Sep 6 09:14:09 EST 2010 So that looks like I am running the right kernel. But because the symptoms didn't change overly I had my doubts from the beginning, and thus have been trying to prove I was running the kernel with your patch applied. Doing that in various ways is why it took me a while to respond to your request to test the patch. One way I tried to confirm it by adding trace: --- x/linux-2.6-2.6.32/drivers/net/tun.c2009-12-03 13:51:21.0 +1000 +++ linux-2.6-2.6.32/drivers/net/tun.c 2010-09-06 08:09:44.068458190 +1000 @@ -36,7 +36,7 @@ #define DRV_NAME tun #define DRV_VERSION1.6 -#define DRV_DESCRIPTIONUniversal TUN/TAP device driver +#define DRV_DESCRIPTIONUniversal TUN/TAP device driver + 0001-tun-Don-t-add-sysfs-attributes-to-devices-without-sy.patch applied #define DRV_COPYRIGHT (C) 1999-2004 Max Krasnyansky m...@qualcomm.com #include linux/module.h @@ -1006,7 +1006,9 @@ if (err 0) goto err_free_sk; - if (device_create_file(tun-dev-dev, dev_attr_tun_flags) || + printk(KERN_INFO 0001-tun-Don-t-add-sysfs-attributes-to-devices-without-sy.patch\n); + if (!net_eq(dev_net(tun-dev), init_net) || + device_create_file(tun-dev-dev, dev_attr_tun_flags) || device_create_file(tun-dev-dev, dev_attr_owner) || device_create_file(tun-dev-dev, dev_attr_group)) printk(KERN_ERR Failed to create tun sysfs files\n); None of the trace is ever appears in /var/log/kern.log, which is to say grep 0001-tun /var/log/kern.log prints nothing. Yet I am evidently running a different kernel as I don't ever hit the BUG the buildd kernel generates. I don't have a clue what is going on. The steps I used to generate the kernel are: $ apt-get source linux-2.6 $ cd linux-2.6-2.6.32 $ fakeroot debian/rules source $ fakeroot debian/rules setup $ patch -p1 .../0001-tun-Don-t-add-sysfs-attributes-to-devices-without-sy.patch $ ed drivers/net/tun.c # add trace $ ed debian/changelog # add rev 2.6.30-20.2 $ fakeroot debian/rules binary $ sudo dpkg -i ../linux-image-2.6.32-5-amd64_2.6.32-20.2_amd64.deb $ sudo ed /boot/grub/grub.cfg # set the default kernel $ sudo reboot -f -- 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/1283773622.4264.65.ca...@russell-laptop
Bug#595502: closed by Ben Hutchings b...@decadent.org.uk (Re: Bug#595502: linux-image-2.6.32-5-mckinley: panics while loading INIT, IOMMU out of mapping resources)
Thibaut VARENE vare...@debian.org writes: Please find attached the dmesg pertaining to this wonderful disaster. What it doesn't show is the fact that I also saw the endless /sys/devices enumeration during this boot. That's probably an unrelated bug in mdadm: http://bugs.debian.org/594418 Fixed in mdadm/3.1.4-1 Bjørn -- 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/877hizf5mc@nemi.mork.no
Bug#571035: [squeeze alpha1] installationsreport: grub2: machine doesn't boot
Hello, On Sun, Sep 5, 2010 at 6:15 PM, Holger Wansing li...@wansing-online.de wrote: 2. the second is a debian-installer kernel. I copied the kernel and initrd from a debian-installer netinst cd (the same cd which was used to perform the test installation, leading to this bugreport #571035, an debian-testing daily build from 23. Aug 2010. That kernel boots fine!!! You might try to use the installer and chroot into /target and install the latest 486 kernel and see if it boots. -- Otavio Salvador O.S. Systems E-mail: ota...@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br -- 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/aanlktike4+=x3xkcrkbatk6tj92c-wugi52dgrdsq...@mail.gmail.com
Bug#593421: More info, change of severity
2010/9/5 Steve Langasek vor...@debian.org: [snip] I'm sorry for the difficulty you're experiencing, but that does not meet the definition of a 'grave' bug. A grave bug is when the package is unusable *in general*, not when it is unusable on a particular piece of hardware. Sorry for the inconveniences then, and thanks for the clarification :-) -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktinccef40e-oth5onrh505bm1t01joj0oykzn...@mail.gmail.com
Processing of linux-2.6_2.6.35-1~experimental.3_amd64.changes
linux-2.6_2.6.35-1~experimental.3_amd64.changes uploaded successfully to localhost along with the files: linux-2.6_2.6.35-1~experimental.3.dsc linux-2.6_2.6.35-1~experimental.3.diff.gz linux-doc-2.6.35_2.6.35-1~experimental.3_all.deb linux-manual-2.6.35_2.6.35-1~experimental.3_all.deb linux-patch-debian-2.6.35_2.6.35-1~experimental.3_all.deb linux-source-2.6.35_2.6.35-1~experimental.3_all.deb linux-support-2.6.35-trunk_2.6.35-1~experimental.3_all.deb firmware-linux-free_2.6.35-1~experimental.3_all.deb linux-base_2.6.35-1~experimental.3_all.deb linux-image-2.6.35-trunk-amd64_2.6.35-1~experimental.3_amd64.deb linux-image-2.6.35-trunk-amd64-dbg_2.6.35-1~experimental.3_amd64.deb linux-headers-2.6.35-trunk-amd64_2.6.35-1~experimental.3_amd64.deb linux-headers-2.6.35-trunk-common_2.6.35-1~experimental.3_amd64.deb linux-headers-2.6.35-trunk-all_2.6.35-1~experimental.3_amd64.deb linux-headers-2.6.35-trunk-all-amd64_2.6.35-1~experimental.3_amd64.deb linux-libc-dev_2.6.35-1~experimental.3_amd64.deb linux-tools-2.6.35_2.6.35-1~experimental.3_amd64.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- 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/e1osejw-0004ql...@franck.debian.org
linux-2.6_2.6.35-1~experimental.3_amd64.changes ACCEPTED
Accepted: firmware-linux-free_2.6.35-1~experimental.3_all.deb to main/l/linux-2.6/firmware-linux-free_2.6.35-1~experimental.3_all.deb linux-2.6_2.6.35-1~experimental.3.diff.gz to main/l/linux-2.6/linux-2.6_2.6.35-1~experimental.3.diff.gz linux-2.6_2.6.35-1~experimental.3.dsc to main/l/linux-2.6/linux-2.6_2.6.35-1~experimental.3.dsc linux-base_2.6.35-1~experimental.3_all.deb to main/l/linux-2.6/linux-base_2.6.35-1~experimental.3_all.deb linux-doc-2.6.35_2.6.35-1~experimental.3_all.deb to main/l/linux-2.6/linux-doc-2.6.35_2.6.35-1~experimental.3_all.deb linux-headers-2.6.35-trunk-all-amd64_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux-headers-2.6.35-trunk-all-amd64_2.6.35-1~experimental.3_amd64.deb linux-headers-2.6.35-trunk-all_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux-headers-2.6.35-trunk-all_2.6.35-1~experimental.3_amd64.deb linux-headers-2.6.35-trunk-amd64_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux-headers-2.6.35-trunk-amd64_2.6.35-1~experimental.3_amd64.deb linux-headers-2.6.35-trunk-common_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux-headers-2.6.35-trunk-common_2.6.35-1~experimental.3_amd64.deb linux-image-2.6.35-trunk-amd64-dbg_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux-image-2.6.35-trunk-amd64-dbg_2.6.35-1~experimental.3_amd64.deb linux-image-2.6.35-trunk-amd64_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux-image-2.6.35-trunk-amd64_2.6.35-1~experimental.3_amd64.deb linux-libc-dev_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux-libc-dev_2.6.35-1~experimental.3_amd64.deb linux-manual-2.6.35_2.6.35-1~experimental.3_all.deb to main/l/linux-2.6/linux-manual-2.6.35_2.6.35-1~experimental.3_all.deb linux-patch-debian-2.6.35_2.6.35-1~experimental.3_all.deb to main/l/linux-2.6/linux-patch-debian-2.6.35_2.6.35-1~experimental.3_all.deb linux-source-2.6.35_2.6.35-1~experimental.3_all.deb to main/l/linux-2.6/linux-source-2.6.35_2.6.35-1~experimental.3_all.deb linux-support-2.6.35-trunk_2.6.35-1~experimental.3_all.deb to main/l/linux-2.6/linux-support-2.6.35-trunk_2.6.35-1~experimental.3_all.deb linux-tools-2.6.35_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux-tools-2.6.35_2.6.35-1~experimental.3_amd64.deb Override entries for your package: firmware-linux-free_2.6.35-1~experimental.3_all.deb - optional kernel linux-2.6_2.6.35-1~experimental.3.dsc - source devel linux-base_2.6.35-1~experimental.3_all.deb - optional kernel linux-doc-2.6.35_2.6.35-1~experimental.3_all.deb - optional doc linux-headers-2.6.35-trunk-all-amd64_2.6.35-1~experimental.3_amd64.deb - optional kernel linux-headers-2.6.35-trunk-all_2.6.35-1~experimental.3_amd64.deb - optional kernel linux-headers-2.6.35-trunk-amd64_2.6.35-1~experimental.3_amd64.deb - optional kernel linux-headers-2.6.35-trunk-common_2.6.35-1~experimental.3_amd64.deb - optional kernel linux-image-2.6.35-trunk-amd64-dbg_2.6.35-1~experimental.3_amd64.deb - extra debug linux-image-2.6.35-trunk-amd64_2.6.35-1~experimental.3_amd64.deb - optional kernel linux-libc-dev_2.6.35-1~experimental.3_amd64.deb - optional devel linux-manual-2.6.35_2.6.35-1~experimental.3_all.deb - optional doc linux-patch-debian-2.6.35_2.6.35-1~experimental.3_all.deb - optional kernel linux-source-2.6.35_2.6.35-1~experimental.3_all.deb - optional kernel linux-support-2.6.35-trunk_2.6.35-1~experimental.3_all.deb - optional devel linux-tools-2.6.35_2.6.35-1~experimental.3_amd64.deb - optional kernel Announcing to debian-devel-chan...@lists.debian.org Closing bugs: 49 574243 589996 590546 590557 591149 591241 592045 592226 593720 594642 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1osewj-0003is...@franck.debian.org
Bug#555549: marked as done (adding .gnu_debuglink section in kernel modules)
Your message dated Mon, 06 Sep 2010 16:26:37 + with message-id e1osewj-0003iy...@franck.debian.org and subject line Bug#49: fixed in linux-2.6 2.6.35-1~experimental.3 has caused the Debian Bug report #49, regarding adding .gnu_debuglink section in kernel modules 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.) -- 49: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=49 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libdw1 Version: 0.143-1 Severity: normal Currently libdw1 tries to append .debug to module name to find debug information. This fails with make-kpkg because debug info for kernel modules is installed under /usr/lib/debug/lib/modules/VER/... without appending .debug extension. It would be good if libdw1 could check for files without .debug extension. Alternatively make-kpkg can be changed to append the extension, but it will be against Best practices for debug packages from Developers References (6.7.9), and other debug packages in Debian do not append this extension (it looks like it is Fedora's policy to add .debug). According to strace, systemtap now looks for debug information for module snd.ko in the following locations: /lib/modules/2.6.32-rc6/kernel/sound/core/snd.ko /usr/lib/debug/.build-id/8d/19f404d7db2242e69c87419b8fd32f67fca584.debug /lib/modules/2.6.32-rc6/kernel/sound/core/snd.ko.debug /lib/modules/2.6.32-rc6/kernel/sound/core/.debug/snd.ko.debug /usr/lib/debug/lib/modules/2.6.32-rc6/kernel/sound/core/snd.ko.debug /lib/modules/2.6.32-rc6/kernel/sound/core/build/snd.ko.debug but it can be found here: /lib/modules/2.6.32-rc6/kernel/sound/core/snd.ko -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-rc6 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=uk_UA.UTF-8, LC_CTYPE=uk_UA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libdw1 depends on: ii libbz2-1.0 1.0.5-3 high-quality block-sorting file co ii libc6 2.10.1-6 GNU C Library: Shared libraries ii libelf10.143-1 library to read and write ELF file ii zlib1g 1:1.2.3.3.dfsg-15 compression library - runtime libdw1 recommends no packages. libdw1 suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.35-1~experimental.3 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: firmware-linux-free_2.6.35-1~experimental.3_all.deb to main/l/linux-2.6/firmware-linux-free_2.6.35-1~experimental.3_all.deb linux-2.6_2.6.35-1~experimental.3.diff.gz to main/l/linux-2.6/linux-2.6_2.6.35-1~experimental.3.diff.gz linux-2.6_2.6.35-1~experimental.3.dsc to main/l/linux-2.6/linux-2.6_2.6.35-1~experimental.3.dsc linux-base_2.6.35-1~experimental.3_all.deb to main/l/linux-2.6/linux-base_2.6.35-1~experimental.3_all.deb linux-doc-2.6.35_2.6.35-1~experimental.3_all.deb to main/l/linux-2.6/linux-doc-2.6.35_2.6.35-1~experimental.3_all.deb linux-headers-2.6.35-trunk-all-amd64_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux-headers-2.6.35-trunk-all-amd64_2.6.35-1~experimental.3_amd64.deb linux-headers-2.6.35-trunk-all_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux-headers-2.6.35-trunk-all_2.6.35-1~experimental.3_amd64.deb linux-headers-2.6.35-trunk-amd64_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux-headers-2.6.35-trunk-amd64_2.6.35-1~experimental.3_amd64.deb linux-headers-2.6.35-trunk-common_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux-headers-2.6.35-trunk-common_2.6.35-1~experimental.3_amd64.deb linux-image-2.6.35-trunk-amd64-dbg_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux-image-2.6.35-trunk-amd64-dbg_2.6.35-1~experimental.3_amd64.deb linux-image-2.6.35-trunk-amd64_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux-image-2.6.35-trunk-amd64_2.6.35-1~experimental.3_amd64.deb linux-libc-dev_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux-libc-dev_2.6.35-1~experimental.3_amd64.deb linux-manual-2.6.35_2.6.35-1~experimental.3_all.deb to main/l/linux-2.6/linux-manual-2.6.35_2.6.35-1~experimental.3_all.deb linux-patch-debian-2.6.35_2.6.35-1~experimental.3_all.deb to main/l/linux-2.6/linux-patch-debian-2.6.35_2.6.35-1~experimental.3_all.deb
Bug#574243: marked as done (please restore Sun XVR video drivers, and add the latest one [was Re: Debian Sparc 5.4 on Sun blade 2500])
Your message dated Mon, 06 Sep 2010 16:26:37 + with message-id e1osewj-0003j4...@franck.debian.org and subject line Bug#574243: fixed in linux-2.6 2.6.35-1~experimental.3 has caused the Debian Bug report #574243, regarding please restore Sun XVR video drivers, and add the latest one [was Re: Debian Sparc 5.4 on Sun blade 2500] 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.) -- 574243: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574243 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-9 On Tue, Mar 16, 2010 at 03:24:37PM -0700, David Miller wrote: Josip, please make sure this gets fixed, please get my sunxvr1000 driver added (attached) and then add: CONFIG_FB_XVR500=y CONFIG_FB_XVR2500=y CONFIG_FB_XVR1000=y to the config for sparc64. Ok, further checking shows that lenny has XVR500 and XVR2500 enabled (doing a test install with a XVR-500 card right now) but testing doesn't. Indeed, they seem to have gone missing somehow from debian/config/sparc/config where there's just: # CONFIG_FB_LEO is not set # CONFIG_FB_S1D13XXX is not set whereas in the same source we have arch/sparc/configs/sparc64_defconfig where there's: # CONFIG_FB_LEO is not set CONFIG_FB_XVR500=y CONFIG_FB_XVR2500=y # CONFIG_FB_S1D13XXX is not set I'm filing a bug report with this message, thanks for the exact hint. As for the new driver that Dave mentioned as an attachment, it's already in mainline at: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=2d378b9179881b46a0faf11430efb421fe03ddd8 That should apply pretty easily to .32 stable. I'm not sure offhand what the Debian policy is about tracking linux-stable vs. adding new code, but either way this seems pretty uncontroversial - it's a separate new driver which won't hurt any existing users, because its OF match of SUNW,gfb simply does not overlap with anything else in drivers/video/. -- 2. That which causes joy or happiness. ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.35-1~experimental.3 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: firmware-linux-free_2.6.35-1~experimental.3_all.deb to main/l/linux-2.6/firmware-linux-free_2.6.35-1~experimental.3_all.deb linux-2.6_2.6.35-1~experimental.3.diff.gz to main/l/linux-2.6/linux-2.6_2.6.35-1~experimental.3.diff.gz linux-2.6_2.6.35-1~experimental.3.dsc to main/l/linux-2.6/linux-2.6_2.6.35-1~experimental.3.dsc linux-base_2.6.35-1~experimental.3_all.deb to main/l/linux-2.6/linux-base_2.6.35-1~experimental.3_all.deb linux-doc-2.6.35_2.6.35-1~experimental.3_all.deb to main/l/linux-2.6/linux-doc-2.6.35_2.6.35-1~experimental.3_all.deb linux-headers-2.6.35-trunk-all-amd64_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux-headers-2.6.35-trunk-all-amd64_2.6.35-1~experimental.3_amd64.deb linux-headers-2.6.35-trunk-all_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux-headers-2.6.35-trunk-all_2.6.35-1~experimental.3_amd64.deb linux-headers-2.6.35-trunk-amd64_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux-headers-2.6.35-trunk-amd64_2.6.35-1~experimental.3_amd64.deb linux-headers-2.6.35-trunk-common_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux-headers-2.6.35-trunk-common_2.6.35-1~experimental.3_amd64.deb linux-image-2.6.35-trunk-amd64-dbg_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux-image-2.6.35-trunk-amd64-dbg_2.6.35-1~experimental.3_amd64.deb linux-image-2.6.35-trunk-amd64_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux-image-2.6.35-trunk-amd64_2.6.35-1~experimental.3_amd64.deb linux-libc-dev_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux-libc-dev_2.6.35-1~experimental.3_amd64.deb linux-manual-2.6.35_2.6.35-1~experimental.3_all.deb to main/l/linux-2.6/linux-manual-2.6.35_2.6.35-1~experimental.3_all.deb linux-patch-debian-2.6.35_2.6.35-1~experimental.3_all.deb to main/l/linux-2.6/linux-patch-debian-2.6.35_2.6.35-1~experimental.3_all.deb linux-source-2.6.35_2.6.35-1~experimental.3_all.deb to main/l/linux-2.6/linux-source-2.6.35_2.6.35-1~experimental.3_all.deb linux-support-2.6.35-trunk_2.6.35-1~experimental.3_all.deb to main/l/linux-2.6/linux-support-2.6.35-trunk_2.6.35-1~experimental.3_all.deb linux-tools-2.6.35_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux-tools-2.6.35_2.6.35-1~experimental.3_amd64.deb A summary of the changes between this version and the previous one
Bug#589996: marked as done (Insane dependency on apt causes kernel to be removed on update)
Your message dated Mon, 06 Sep 2010 16:26:37 +
with message-id e1osewj-0003j7...@franck.debian.org
and subject line Bug#589996: fixed in linux-2.6 2.6.35-1~experimental.3
has caused the Debian Bug report #589996,
regarding Insane dependency on apt causes kernel to be removed on 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.)
--
589996: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589996
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-base
Version: 2.6.32-17
Severity: important
Hi,
in the linux-image packages there is now a dependency chain from
linux-image-2.6... - linux-base - libapt-pkg-perl -
libapt-pkg-libc6.9-6-4.8. Which is the virtual package provided by apt
to signal the ABI of its library and binary caches. In effect the
kernels are locked to a specific ABI version of apt. The problem is
that the ABI changes from time to time and every time it does an
update of apt will now remove the kernel for the duration of the
transition. For an example try installing apt from experimental.
Well, that is life you might say. That is what is called a library
transition.
But here comes the insane part. The 1637 line long perl postinst
script of linux-base only depends on apt because of this code at the
end:
sub compare_versions {
return $AptPkg::Config::_config-system-versioning-compare(@_);
}
if ($ARGV[0] eq 'reconfigure' || defined($ENV{DEBCONF_RECONFIGURE}) ||
(!is_fresh_installation()
compare_versions($ARGV[1], $libata_transition_ver) 0)) {
DebianKernel::DiskId::transition();
}
Could I suggest replacing this with a call to
system('dpkg', '--compare-versions', $ARGV[1], '', $libata_transition_ver)
That way the dependency on apt can be droped completly.
MfG
Goswin
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.31.6-xen-2010.02.18 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Versions of packages linux-base depends on:
ii debconf [debconf-2.0] 1.5.32 Debian configuration management sy
ii libapt-pkg-perl 0.1.24 Perl interface to libapt-pkg
ii libuuid-perl 0.02-3+b1 Perl extension for using UUID inte
ii udev 157-1 /dev/ and hotplug management daemo
ii util-linux2.17.2-3 Miscellaneous system utilities
linux-base recommends no packages.
linux-base suggests no packages.
-- debconf information excluded
---End Message---
---BeginMessage---
Source: linux-2.6
Source-Version: 2.6.35-1~experimental.3
We believe that the bug you reported is fixed in the latest version of
linux-2.6, which is due to be installed in the Debian FTP archive:
firmware-linux-free_2.6.35-1~experimental.3_all.deb
to main/l/linux-2.6/firmware-linux-free_2.6.35-1~experimental.3_all.deb
linux-2.6_2.6.35-1~experimental.3.diff.gz
to main/l/linux-2.6/linux-2.6_2.6.35-1~experimental.3.diff.gz
linux-2.6_2.6.35-1~experimental.3.dsc
to main/l/linux-2.6/linux-2.6_2.6.35-1~experimental.3.dsc
linux-base_2.6.35-1~experimental.3_all.deb
to main/l/linux-2.6/linux-base_2.6.35-1~experimental.3_all.deb
linux-doc-2.6.35_2.6.35-1~experimental.3_all.deb
to main/l/linux-2.6/linux-doc-2.6.35_2.6.35-1~experimental.3_all.deb
linux-headers-2.6.35-trunk-all-amd64_2.6.35-1~experimental.3_amd64.deb
to
main/l/linux-2.6/linux-headers-2.6.35-trunk-all-amd64_2.6.35-1~experimental.3_amd64.deb
linux-headers-2.6.35-trunk-all_2.6.35-1~experimental.3_amd64.deb
to
main/l/linux-2.6/linux-headers-2.6.35-trunk-all_2.6.35-1~experimental.3_amd64.deb
linux-headers-2.6.35-trunk-amd64_2.6.35-1~experimental.3_amd64.deb
to
main/l/linux-2.6/linux-headers-2.6.35-trunk-amd64_2.6.35-1~experimental.3_amd64.deb
linux-headers-2.6.35-trunk-common_2.6.35-1~experimental.3_amd64.deb
to
main/l/linux-2.6/linux-headers-2.6.35-trunk-common_2.6.35-1~experimental.3_amd64.deb
linux-image-2.6.35-trunk-amd64-dbg_2.6.35-1~experimental.3_amd64.deb
to
main/l/linux-2.6/linux-image-2.6.35-trunk-amd64-dbg_2.6.35-1~experimental.3_amd64.deb
linux-image-2.6.35-trunk-amd64_2.6.35-1~experimental.3_amd64.deb
to
main/l/linux-2.6/linux-image-2.6.35-trunk-amd64_2.6.35-1~experimental.3_amd64.deb
linux-libc-dev_2.6.35-1~experimental.3_amd64.deb
to main/l/linux-2.6/linux-libc-dev_2.6.35-1~experimental.3_amd64.deb
linux-manual-2.6.35_2.6.35-1~experimental.3_all.deb
to
Bug#590557: marked as done (linux-2.6: [INTL:pt] Updated Portuguese translation for debconf messages)
Your message dated Mon, 06 Sep 2010 16:26:37 + with message-id e1osewj-0003jd...@franck.debian.org and subject line Bug#590557: fixed in linux-2.6 2.6.35-1~experimental.3 has caused the Debian Bug report #590557, regarding linux-2.6: [INTL:pt] Updated Portuguese translation for debconf messages 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.) -- 590557: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=590557 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-18 Tags: l10n, patch Severity: wishlist Updated Portuguese translation for linux-2.6's debconf messages. Translator: Américo Monteiro a_monte...@netcabo.pt Feel free to use it. For translation updates please contact 'Last Translator' or the Portuguese Translation Team traduz at debianpt.org. -- Best regards, Américo Monteiro Traduz - Portuguese Translation Team http://www.DebianPT.org # Translation of linux-2.6 debconf messages to Portuguese # Copyright (C) 2010 the linux-2.6's copyright holder # This file is distributed under the same license as the linux-2.6 package. # # Américo Monteiro a_monte...@netcabo.pt, 2010. msgid msgstr Project-Id-Version: linux-2.6 2.6.32-18\n Report-Msgid-Bugs-To: \n POT-Creation-Date: 2010-07-25 10:32+0200\n PO-Revision-Date: 2010-07-27 10:33+0100\n Last-Translator: Américo Monteiro a_monte...@netcabo.pt\n Language-Team: Portuguese tra...@debianpt.org\n MIME-Version: 1.0\n Content-Type: text/plain; charset=UTF-8\n Content-Transfer-Encoding: 8bit\n Language: pt\n X-Generator: Lokalize 1.0\n Plural-Forms: nplurals=2; plural=(n != 1);\n #. Type: boolean #. Description #: ../linux-base.templates:2001 msgid Update disk device IDs in system configuration? msgstr Actualizar os IDs dos dispositivos de disco na configuração do sistema? #. Type: boolean #. Description #: ../linux-base.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 A nova versão de kernel Linux disponibiliza drivers diferentes para alguns controladores PATA (IDE). Os nomes de alguns discos rígidos, CD-ROM e dispositivos de fita magnética poderão mudar. #. Type: boolean #. Description #: ../linux-base.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 Agora é recomendado identificar os dispositivos de discos nos ficheiros de configuração pela etiqueta ou UUID (identificador único) em vez do nome de dispositivo, o qual irá funcionar com ambas versões de kernel antiga e nova. #. Type: boolean #. Description #: ../linux-base.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 Se escolher não actualizar a configuração do sistema automaticamente, você tem de actualizar os IDs dos dispositivos antes de reiniciar o sistema ou o sistema pode não arrancar. #. Type: boolean #. Description #. Type: boolean #. Description #: ../linux-base.templates:3001 ../linux-base.templates:4001 msgid Apply configuration changes to disk device IDs? msgstr Aplicar estas alterações de configuração aos IDs de dispositivos de discos? #. Type: boolean #. Description #: ../linux-base.templates:3001 msgid These devices will be assigned UUIDs or labels: msgstr A estes dispositivos serão atribuídos UUIDs ou etiquetas: #. Type: boolean #. Description #. Type: boolean #. Description #: ../linux-base.templates:3001 ../linux-base.templates:4001 msgid These configuration files will be updated: msgstr Estes ficheiros de configuração irão ser actualizados: #. Type: boolean #. Description #. Type: boolean #. Description #: ../linux-base.templates:3001 ../linux-base.templates:4001 msgid The device IDs will be changed as follows: msgstr Os IDs de dispositivos irão ser alterados de acordo com o seguinte: #. Type: error #. Description #: ../linux-base.templates:5001 msgid Configuration files still contain deprecated device names msgstr Os ficheiros de configuração ainda contêm nomes obsoletos de dispositivos #. Type: error #. Description #: ../linux-base.templates:5001 msgid The following configuration files still use some device names that may change when using the new kernel: msgstr Os seguintes ficheiros de configuração ainda usam alguns nomes de dispositivos que podem ser
Bug#591149: marked as done (linux-2.6: [INTL:fr] French debconf templates translation update)
Your message dated Mon, 06 Sep 2010 16:26:37 + with message-id e1osewj-0003jm...@franck.debian.org and subject line Bug#591149: fixed in linux-2.6 2.6.35-1~experimental.3 has caused the Debian Bug report #591149, regarding linux-2.6: [INTL:fr] French debconf templates translation 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.) -- 591149: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=591149 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: N/A Severity: wishlist Tags: l10n patch Please find attached the French debconf templates translation updated, proofread by the debian-l10n-french mailing list contributors. This file should be put as debian/po/fr.po in your package build tree. Regards David fr.po.gz Description: GNU Zip compressed data signature.asc Description: OpenPGP digital signature ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.35-1~experimental.3 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: firmware-linux-free_2.6.35-1~experimental.3_all.deb to main/l/linux-2.6/firmware-linux-free_2.6.35-1~experimental.3_all.deb linux-2.6_2.6.35-1~experimental.3.diff.gz to main/l/linux-2.6/linux-2.6_2.6.35-1~experimental.3.diff.gz linux-2.6_2.6.35-1~experimental.3.dsc to main/l/linux-2.6/linux-2.6_2.6.35-1~experimental.3.dsc linux-base_2.6.35-1~experimental.3_all.deb to main/l/linux-2.6/linux-base_2.6.35-1~experimental.3_all.deb linux-doc-2.6.35_2.6.35-1~experimental.3_all.deb to main/l/linux-2.6/linux-doc-2.6.35_2.6.35-1~experimental.3_all.deb linux-headers-2.6.35-trunk-all-amd64_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux-headers-2.6.35-trunk-all-amd64_2.6.35-1~experimental.3_amd64.deb linux-headers-2.6.35-trunk-all_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux-headers-2.6.35-trunk-all_2.6.35-1~experimental.3_amd64.deb linux-headers-2.6.35-trunk-amd64_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux-headers-2.6.35-trunk-amd64_2.6.35-1~experimental.3_amd64.deb linux-headers-2.6.35-trunk-common_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux-headers-2.6.35-trunk-common_2.6.35-1~experimental.3_amd64.deb linux-image-2.6.35-trunk-amd64-dbg_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux-image-2.6.35-trunk-amd64-dbg_2.6.35-1~experimental.3_amd64.deb linux-image-2.6.35-trunk-amd64_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux-image-2.6.35-trunk-amd64_2.6.35-1~experimental.3_amd64.deb linux-libc-dev_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux-libc-dev_2.6.35-1~experimental.3_amd64.deb linux-manual-2.6.35_2.6.35-1~experimental.3_all.deb to main/l/linux-2.6/linux-manual-2.6.35_2.6.35-1~experimental.3_all.deb linux-patch-debian-2.6.35_2.6.35-1~experimental.3_all.deb to main/l/linux-2.6/linux-patch-debian-2.6.35_2.6.35-1~experimental.3_all.deb linux-source-2.6.35_2.6.35-1~experimental.3_all.deb to main/l/linux-2.6/linux-source-2.6.35_2.6.35-1~experimental.3_all.deb linux-support-2.6.35-trunk_2.6.35-1~experimental.3_all.deb to main/l/linux-2.6/linux-support-2.6.35-trunk_2.6.35-1~experimental.3_all.deb linux-tools-2.6.35_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux-tools-2.6.35_2.6.35-1~experimental.3_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 591...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. maximilian attems m...@debian.org (supplier of updated linux-2.6 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 06 Sep 2010 15:16:17 +0200 Source: linux-2.6 Binary: linux-tools-2.6.35 linux-source-2.6.35 linux-doc-2.6.35 linux-manual-2.6.35 linux-patch-debian-2.6.35 firmware-linux-free linux-support-2.6.35-trunk linux-base linux-libc-dev linux-headers-2.6.35-trunk-all linux-headers-2.6.35-trunk-all-alpha linux-headers-2.6.35-trunk-common linux-image-2.6.35-trunk-alpha-generic linux-headers-2.6.35-trunk-alpha-generic linux-image-2.6.35-trunk-alpha-smp linux-headers-2.6.35-trunk-alpha-smp linux-image-2.6.35-trunk-alpha-legacy
Bug#590546: marked as done ([l10n:cs] Updated Czech translation of PO debconf template for package linux-2.6 2.6.32-18)
Your message dated Mon, 06 Sep 2010 16:26:37 + with message-id e1osewj-0003ja...@franck.debian.org and subject line Bug#590546: fixed in linux-2.6 2.6.35-1~experimental.3 has caused the Debian Bug report #590546, regarding [l10n:cs] Updated Czech translation of PO debconf template for package linux-2.6 2.6.32-18 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.) -- 590546: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=590546 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-18 Severity: wishlist Tags: l10n, patch In attachment there is updated Czech translation of PO debconf template (cs.po) for package linux-2.6, please include it. -- Michal Šimůnek # Czech PO debconf template translation of linux-2.6. # Copyright (C) 2010 Michal Simunek michal.simu...@gmail.com # This file is distributed under the same license as the linux-2.6 package. # Michal Simunek michal.simu...@gmail.com, 2010. # msgid msgstr Project-Id-Version: linux-2.6 2.6.32-18\n Report-Msgid-Bugs-To: \n POT-Creation-Date: 2010-07-25 10:32+0200\n PO-Revision-Date: 2010-07-26 18:02+0200\n Last-Translator: Michal Simunek michal.simu...@gmail.com\n Language-Team: Czech debian-l10n-cz...@lists.debian.org\n MIME-Version: 1.0\n Content-Type: text/plain; charset=utf-8\n Content-Transfer-Encoding: 8bit\n Language: cs\n #. Type: boolean #. Description #: ../linux-base.templates:2001 msgid Update disk device IDs in system configuration? msgstr Aktualizovat v nastavení systému ID diskových zařízení? #. Type: boolean #. Description #: ../linux-base.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á verze Linuxového jádra přináší pro některé PATA (IDE) řadiče jiné ovladače. Názvy u některých pevných disků, CD-ROM a páskových mechanik se mohly změnit. #. Type: boolean #. Description #: ../linux-base.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 Nyní je doporučeno v konfiguračních souborech označovat disková zařízení spíše než názvem zařízení raději popiskem či UUID (unikátním identifikátorem), což funguje jak se starou, tak i s novou verzí jádra. #. Type: boolean #. Description #: ../linux-base.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 Pokud se rozhodnete, že nechcete aktualizovat nastavení systému automaticky, musíte před příštím restartem systému ručně aktualizovat ID zařízení, jinak se systém může stát nezaveditelným. #. Type: boolean #. Description #. Type: boolean #. Description #: ../linux-base.templates:3001 ../linux-base.templates:4001 msgid Apply configuration changes to disk device IDs? msgstr Použít změny v nastavení ID diskových zařízení? #. Type: boolean #. Description #: ../linux-base.templates:3001 msgid These devices will be assigned UUIDs or labels: msgstr Těmto zařízením bude přiřazeno UUID či popisek: #. Type: boolean #. Description #. Type: boolean #. Description #: ../linux-base.templates:3001 ../linux-base.templates:4001 msgid These configuration files will be updated: msgstr Tyto konfigurační soubory budou aktualizovány: #. Type: boolean #. Description #. Type: boolean #. Description #: ../linux-base.templates:3001 ../linux-base.templates:4001 msgid The device IDs will be changed as follows: msgstr ID diskových zařízení se změní následovně: #. Type: error #. Description #: ../linux-base.templates:5001 msgid Configuration files still contain deprecated device names msgstr Konfigurační soubory stále obsahují zastaralé názvy zařízení #. Type: error #. Description #: ../linux-base.templates:5001 msgid The following configuration files still use some device names that may change when using the new kernel: msgstr Následující konfigurační soubory stále používají názvy zařízení, které je při používání nového jádra třeba změnit: #. Type: error #. Description #: ../linux-base.templates:6001 msgid Boot loader configuration check needed msgstr Je vyžadováno ověření nastavení zavaděče #. Type: error #. Description #: ../linux-base.templates:6001 msgid The boot loader configuration for this system was not recognized. These settings in the configuration may need to be updated: msgstr Nastavení
Bug#591241: marked as done (linux-2.6: [INTL:ru] Russian debconf templates translation update)
Your message dated Mon, 06 Sep 2010 16:26:37 + with message-id e1osewj-0003jr...@franck.debian.org and subject line Bug#591241: fixed in linux-2.6 2.6.35-1~experimental.3 has caused the Debian Bug report #591241, regarding linux-2.6: [INTL:ru] Russian debconf templates translation 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.) -- 591241: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=591241 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-18 Severity: wishlist Tags: l10n patch Russian debconf templates translation update is attached. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash # translation of ru.po to Russian # Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER # This file is distributed under the same license as the linux-2.6 package. # # Yuri Kozlov yu...@komyakino.ru, 2010. msgid msgstr Project-Id-Version: linux-2.6 2.6.32-18\n Report-Msgid-Bugs-To: \n POT-Creation-Date: 2010-07-25 10:32+0200\n PO-Revision-Date: 2010-08-01 17:11+0400\n Last-Translator: Yuri Kozlov yu...@komyakino.ru\n Language-Team: Russian debian-l10n-russ...@lists.debian.org\n MIME-Version: 1.0\n Content-Type: text/plain; charset=UTF-8\n Content-Transfer-Encoding: 8bit\n Language: ru\n X-Generator: Lokalize 1.0\n Plural-Forms: nplurals=3; plural=(n%10==1 n%100!=11 ? 0 : n%10=2 n%10=4 (n%10010 || n%100=20) ? 1 : 2);\n #. Type: boolean #. Description #: ../linux-base.templates:2001 msgid Update disk device IDs in system configuration? msgstr Обновить идентификаторы дисковых устройств в настройках системы? #. Type: boolean #. Description #: ../linux-base.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 Новая версия ядра Linux предоставляет другие драйверы для некоторых контроллеров PATA (IDE), в следствие чего могут измениться имена некоторых жёстких дисков, CD-ROM и ленточных накопителей. #. Type: boolean #. Description #: ../linux-base.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 Теперь рекомендуется указывать дисковые устройства в файлах настроек в виде меток и UUID (уникальных идентификаторов), а не имён устройств. Это будет работать и в старых и в новых версиях ядер. #. Type: boolean #. Description #: ../linux-base.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 Если вы не выберете автоматическое обновление системных настроек, то должны обновить идентификаторы устройств самостоятельно до следующей перезагрузки, иначе система не запустится. #. Type: boolean #. Description #. Type: boolean #. Description #: ../linux-base.templates:3001 ../linux-base.templates:4001 msgid Apply configuration changes to disk device IDs? msgstr Применить изменение настроек для идентификаторов дисковых устройств? #. Type: boolean #. Description #: ../linux-base.templates:3001 msgid These devices will be assigned UUIDs or labels: msgstr Следующим устройствам будут назначены UUID или метки: #. Type: boolean #. Description #. Type: boolean #. Description #: ../linux-base.templates:3001 ../linux-base.templates:4001 msgid These configuration files will be updated: msgstr Следующие файлы настройки будут обновлены: #. Type: boolean #. Description #. Type: boolean #. Description #: ../linux-base.templates:3001 ../linux-base.templates:4001 msgid The device IDs will be changed as follows: msgstr Идентификаторы устройств будут изменены следующим образом: #. Type: error #. Description #: ../linux-base.templates:5001 msgid Configuration files still contain deprecated device names msgstr Файлы настройки всё ещё содержат устаревшие имена устройств #. Type: error #. Description #: ../linux-base.templates:5001 msgid The following configuration files still use some device names that may change when using the new kernel: msgstr В следующих файлах настройки всё ещё используются некоторые имена устройств, которые могут измениться при использовании нового ядра: #. Type: error #. Description
Bug#592045: marked as done ([INTL:sv] Swedish (sv) debconf translation for linux-2.6)
Your message dated Mon, 06 Sep 2010 16:26:37 + with message-id e1osewj-0003jw...@franck.debian.org and subject line Bug#592045: fixed in linux-2.6 2.6.35-1~experimental.3 has caused the Debian Bug report #592045, regarding [INTL:sv] Swedish (sv) debconf translation for linux-2.6 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.) -- 592045: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=592045 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- package: linux-2.6 severity: wishlist tags: patch l10n Please find the attached Swedish (sv) translation for Xlinux-2.6 debconf messages. -- brother # Translation of linux-2.6 debconf template to Swedish # Copyright (C) 2010 Martin Bagge brot...@bsnet.se # This file is distributed under the same license as the linux-2.6 package. # # Martin Bagge brot...@bsnet.se, 2010 msgid msgstr Project-Id-Version: linux-2.6\n Report-Msgid-Bugs-To: \n POT-Creation-Date: 2010-07-25 10:32+0200\n PO-Revision-Date: 2010-08-07 05:01+0100\n Last-Translator: Martin Bagge / brother brot...@bsnet.se\n Language-Team: Swedish debian-l10n-swed...@lists.debian.org\n MIME-Version: 1.0\n Content-Type: text/plain; charset=utf-8\n Content-Transfer-Encoding: 8bit\n Language: sv\n X-Poedit-Language: Swedish\n X-Poedit-Country: Sweden\n #. Type: boolean #. Description #: ../linux-base.templates:2001 msgid Update disk device IDs in system configuration? msgstr Uppdatera diskenheters ID i systeminställningar? #. Type: boolean #. Description #: ../linux-base.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 Den nya versionen av Linuxkärnan tillhandahåller olika drivrutiner för några PATA(IDE)-kontroller. Namnen på en del hårddiskar, CD-Rom- och band-enheter kan ändras. #. Type: boolean #. Description #: ../linux-base.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 Det är rekomenderat att identifiera diskenheter i konfigurationsfiler med ettikett eller UUID (unik identifierare) snarare än efter enhetsnamn. Ettikett och UUID fungerar både med nya och äldre verisioner av kärnan. #. Type: boolean #. Description #: ../linux-base.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 Om du väljer att inte uppdatera systeminställningarna automatiskt måste du uppdatera enhets-ID själv innan nästa omstart av systemet annars kan systemet bli ostartbart. #. Type: boolean #. Description #. Type: boolean #. Description #: ../linux-base.templates:3001 ../linux-base.templates:4001 msgid Apply configuration changes to disk device IDs? msgstr Genomför förändring av enheternas ID? #. Type: boolean #. Description #: ../linux-base.templates:3001 msgid These devices will be assigned UUIDs or labels: msgstr Dessa enheter kommer att få UUID eller ettiketter: #. Type: boolean #. Description #. Type: boolean #. Description #: ../linux-base.templates:3001 ../linux-base.templates:4001 msgid These configuration files will be updated: msgstr Dessa konfigurationsfiler kommer att uppdateras: #. Type: boolean #. Description #. Type: boolean #. Description #: ../linux-base.templates:3001 ../linux-base.templates:4001 msgid The device IDs will be changed as follows: msgstr Enhets-ID kommer att anges som följer: #. Type: error #. Description #: ../linux-base.templates:5001 msgid Configuration files still contain deprecated device names msgstr Konfigurationsfiler innehåller fortfarande utfasade enhetsnamn #. Type: error #. Description #: ../linux-base.templates:5001 msgid The following configuration files still use some device names that may change when using the new kernel: msgstr Följande konfigurationsfiler använder fortfarande några enhetsnamn som kan komma att ändras med den nya kärnan: #. Type: error #. Description #: ../linux-base.templates:6001 msgid Boot loader configuration check needed msgstr Kontroll av konfigurationen i uppstartshanteraren behövs #. Type: error #. Description #: ../linux-base.templates:6001 msgid The boot loader configuration for this system was not recognized. These settings in the configuration may need to be updated: msgstr Inställningarna för uppstartshanteraren i det här systemet kunde inte kännas igen. Dessa
Bug#592226: marked as done (linux-2.6: updated german debconf translation)
Your message dated Mon, 06 Sep 2010 16:26:38 + with message-id e1osewk-0003jb...@franck.debian.org and subject line Bug#592226: fixed in linux-2.6 2.6.35-1~experimental.3 has caused the Debian Bug report #592226, regarding linux-2.6: updated german debconf translation to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 592226: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=592226 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Severity: wishlist, patch Attached you will find the updated german debconf translation for linux-2.6 2.6.32-19. Thanks for your i18n efforts. Greetings Holger -- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = Created with Sylpheed 2.5.0 under DEBIAN GNU/LINUX 5.0.0 - L e n n y Registered LinuxUser #311290 - http://counter.li.org/ = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = linux-2.6_2.6.32-19_de.po.gz Description: Binary data ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.35-1~experimental.3 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: firmware-linux-free_2.6.35-1~experimental.3_all.deb to main/l/linux-2.6/firmware-linux-free_2.6.35-1~experimental.3_all.deb linux-2.6_2.6.35-1~experimental.3.diff.gz to main/l/linux-2.6/linux-2.6_2.6.35-1~experimental.3.diff.gz linux-2.6_2.6.35-1~experimental.3.dsc to main/l/linux-2.6/linux-2.6_2.6.35-1~experimental.3.dsc linux-base_2.6.35-1~experimental.3_all.deb to main/l/linux-2.6/linux-base_2.6.35-1~experimental.3_all.deb linux-doc-2.6.35_2.6.35-1~experimental.3_all.deb to main/l/linux-2.6/linux-doc-2.6.35_2.6.35-1~experimental.3_all.deb linux-headers-2.6.35-trunk-all-amd64_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux-headers-2.6.35-trunk-all-amd64_2.6.35-1~experimental.3_amd64.deb linux-headers-2.6.35-trunk-all_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux-headers-2.6.35-trunk-all_2.6.35-1~experimental.3_amd64.deb linux-headers-2.6.35-trunk-amd64_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux-headers-2.6.35-trunk-amd64_2.6.35-1~experimental.3_amd64.deb linux-headers-2.6.35-trunk-common_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux-headers-2.6.35-trunk-common_2.6.35-1~experimental.3_amd64.deb linux-image-2.6.35-trunk-amd64-dbg_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux-image-2.6.35-trunk-amd64-dbg_2.6.35-1~experimental.3_amd64.deb linux-image-2.6.35-trunk-amd64_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux-image-2.6.35-trunk-amd64_2.6.35-1~experimental.3_amd64.deb linux-libc-dev_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux-libc-dev_2.6.35-1~experimental.3_amd64.deb linux-manual-2.6.35_2.6.35-1~experimental.3_all.deb to main/l/linux-2.6/linux-manual-2.6.35_2.6.35-1~experimental.3_all.deb linux-patch-debian-2.6.35_2.6.35-1~experimental.3_all.deb to main/l/linux-2.6/linux-patch-debian-2.6.35_2.6.35-1~experimental.3_all.deb linux-source-2.6.35_2.6.35-1~experimental.3_all.deb to main/l/linux-2.6/linux-source-2.6.35_2.6.35-1~experimental.3_all.deb linux-support-2.6.35-trunk_2.6.35-1~experimental.3_all.deb to main/l/linux-2.6/linux-support-2.6.35-trunk_2.6.35-1~experimental.3_all.deb linux-tools-2.6.35_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux-tools-2.6.35_2.6.35-1~experimental.3_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 592...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. maximilian attems m...@debian.org (supplier of updated linux-2.6 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 06 Sep 2010 15:16:17 +0200 Source: linux-2.6 Binary: linux-tools-2.6.35 linux-source-2.6.35 linux-doc-2.6.35 linux-manual-2.6.35 linux-patch-debian-2.6.35 firmware-linux-free linux-support-2.6.35-trunk linux-base linux-libc-dev linux-headers-2.6.35-trunk-all linux-headers-2.6.35-trunk-all-alpha linux-headers-2.6.35-trunk-common linux-image-2.6.35-trunk-alpha-generic linux-headers-2.6.35-trunk-alpha-generic linux-image-2.6.35-trunk-alpha-smp
Bug#593720: marked as done (Fwd: Deadline as default scheduler?)
Your message dated Mon, 06 Sep 2010 16:26:38 + with message-id e1osewk-0003jg...@franck.debian.org and subject line Bug#593720: fixed in linux-2.6 2.6.35-1~experimental.3 has caused the Debian Bug report #593720, regarding Fwd: Deadline as default scheduler? 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.) -- 593720: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593720 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.35-1~experimental.2 Severity: normal This bug report is just a reminder that comes from a message i sent on d-k mailing list: appended inline my initial message and the reply from Ben Hutchings. The original message was about 2.6.35-1~experimental.1, but in experimental.2 the CFQ scheduler is yet configured as module and deadline is the default scheduler (with evident negative impact on responsiveness, at least on my not so young Pentium M 1,6 GHz). Cesare. Original Message Subject: Deadline as default scheduler? Date: Tue, 10 Aug 2010 00:04:44 +0200 From: Cesare Leonardi celeo...@gmail.com To: debian-kernel@lists.debian.org Hi all. I've noted some changes in the scheduler configuration of 2.6.35-trunk-686 and i wonder if they are erroneous or not, since their effect are rather evident and i've seen no discussion on d-k. I was filing a bug but i preferred to ask on the mailing list first. --- /boot/config-2.6.35-rc6-686 2010-07-26 13:09:56.0 +0200 +++ /boot/config-2.6.35-trunk-686 2010-08-06 18:13:52.0 +0200 @@ -221,11 +222,12 @@ # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_DEADLINE=y -CONFIG_IOSCHED_CFQ=y -# CONFIG_DEFAULT_DEADLINE is not set -CONFIG_DEFAULT_CFQ=y +CONFIG_IOSCHED_CFQ=m +CONFIG_CFQ_GROUP_IOSCHED=y +CONFIG_DEFAULT_DEADLINE=y +# CONFIG_DEFAULT_CFQ is not set # CONFIG_DEFAULT_NOOP is not set -CONFIG_DEFAULT_IOSCHED=cfq +CONFIG_DEFAULT_IOSCHED=deadline Why setting deadline as default scheduler? And why configuring cfq as module? In a desktop usage, with a pentium M 1,6 GHz and 1 GB ram, the system is clearly worse in responsiveness, a bit jerky in particular when i type on the keyboard: occasionaly i can see the effect of what i type with a delay of some tenth of second. Are there other distros not using cfq as default scheduler? Ciao. Cesare. Reply from Ben Subject: Re: Deadline as default scheduler? Date: Tue, 10 Aug 2010 01:58:14 +0100 From: Ben Hutchings b...@decadent.org.uk To: Cesare Leonardi celeo...@gmail.com, Maximilian Attems matt...@hep.itp.tuwien.ac.at CC: debian-kernel@lists.debian.org [...] Why setting deadline as default scheduler? And why configuring cfq as module? This is due to enabling BLK_CGROUP: config IOSCHED_CFQ tristate CFQ I/O scheduler # If BLK_CGROUP is a module, CFQ has to be built as module. depends on (BLK_CGROUP=m m) || !BLK_CGROUP || BLK_CGROUP=y Max, we have to make BLK_CGROUP=y or disable it completely. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.35-1~experimental.3 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: firmware-linux-free_2.6.35-1~experimental.3_all.deb to main/l/linux-2.6/firmware-linux-free_2.6.35-1~experimental.3_all.deb linux-2.6_2.6.35-1~experimental.3.diff.gz to main/l/linux-2.6/linux-2.6_2.6.35-1~experimental.3.diff.gz linux-2.6_2.6.35-1~experimental.3.dsc to main/l/linux-2.6/linux-2.6_2.6.35-1~experimental.3.dsc linux-base_2.6.35-1~experimental.3_all.deb to main/l/linux-2.6/linux-base_2.6.35-1~experimental.3_all.deb linux-doc-2.6.35_2.6.35-1~experimental.3_all.deb to main/l/linux-2.6/linux-doc-2.6.35_2.6.35-1~experimental.3_all.deb linux-headers-2.6.35-trunk-all-amd64_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux-headers-2.6.35-trunk-all-amd64_2.6.35-1~experimental.3_amd64.deb linux-headers-2.6.35-trunk-all_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux-headers-2.6.35-trunk-all_2.6.35-1~experimental.3_amd64.deb linux-headers-2.6.35-trunk-amd64_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux-headers-2.6.35-trunk-amd64_2.6.35-1~experimental.3_amd64.deb linux-headers-2.6.35-trunk-common_2.6.35-1~experimental.3_amd64.deb to main/l/linux-2.6/linux-headers-2.6.35-trunk-common_2.6.35-1~experimental.3_amd64.deb linux-image-2.6.35-trunk-amd64-dbg_2.6.35-1~experimental.3_amd64.deb to
Bug#594642: marked as done (linux-image: add sm7xx (Staging driver))
Your message dated Mon, 06 Sep 2010 16:26:38 + with message-id e1osewk-0003jl...@franck.debian.org and subject line Bug#594642: fixed in linux-2.6 2.6.35-1~experimental.3 has caused the Debian Bug report #594642, regarding linux-image: add sm7xx (Staging driver) 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.) -- 594642: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594642 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.35-1~experimental.2 Severity: wishlist *** Please type your report below this line *** The Lemote YeeLoong is a MIPS-based netbook: http://wiki.gnewsense.org/Projects/Lemote#toc17 The display adapter shows in lspci as: 00:08.0 VGA compatible controller [0300]: Silicon Motion, Inc. SM712 LynxEM+ [126f:0712] (rev b0) Kernel driver in use: smtcfb In order to have frame-buffer support in it, it seems that the Staging driver sm7xx is needed. With it I get a working console and FB-based X. What would be required to get this driver included in the Debian kernel package? -- Package-specific info: ** Version: Linux version 2.6.35-trunk-loongson-2f (Debian 2.6.35-1~experimental.2) (m...@debian.org) (gcc version 4.4.5 20100728 (prerelease) (Debian 4.4.4-8) ) #1 Tue Aug 17 21:45:32 UTC 2010 ** Command line: console=tty root=/dev/sda1 PMON_VER=LM8089-1.4.5 EC_VER=PQ1D20 machtype=lemote-yeeloong-2f-8.9inches ** Not tainted ** Kernel log: [4.412000] usb usb1: Product: EHCI Host Controller [4.412000] usb usb1: Manufacturer: Linux 2.6.35-trunk-loongson-2f ehci_hcd [4.412000] usb usb1: SerialNumber: :00:09.1 [4.412000] hub 1-0:1.0: USB hub found [4.412000] hub 1-0:1.0: 2 ports detected [4.412000] PCI: Setting latency timer of device :00:0e.5 to 64 [4.412000] ehci_hcd :00:0e.5: EHCI Host Controller [4.412000] ehci_hcd :00:0e.5: new USB bus registered, assigned bus number 2 [4.436000] ehci_hcd :00:0e.5: irq 11, io mem 0x41022000 [4.448000] ehci_hcd :00:0e.5: USB 0.0 started, EHCI 1.00 [4.448000] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002 [4.448000] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [4.448000] usb usb2: Product: EHCI Host Controller [4.448000] usb usb2: Manufacturer: Linux 2.6.35-trunk-loongson-2f ehci_hcd [4.448000] usb usb2: SerialNumber: :00:0e.5 [4.448000] hub 2-0:1.0: USB hub found [4.448000] hub 2-0:1.0: 4 ports detected [4.508000] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [4.508000] PCI: Enabling device :00:09.0 (0140 - 0142) [4.508000] ohci_hcd :00:09.0: OHCI Host Controller [4.508000] ohci_hcd :00:09.0: new USB bus registered, assigned bus number 3 [4.508000] ohci_hcd :00:09.0: irq 39, io mem 0x4102 [4.564000] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001 [4.564000] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [4.564000] usb usb3: Product: OHCI Host Controller [4.564000] usb usb3: Manufacturer: Linux 2.6.35-trunk-loongson-2f ohci_hcd [4.564000] usb usb3: SerialNumber: :00:09.0 [4.564000] hub 3-0:1.0: USB hub found [4.564000] hub 3-0:1.0: 2 ports detected [4.564000] PCI: Enabling device :00:0e.4 ( - 0002) [4.564000] PCI: Setting latency timer of device :00:0e.4 to 64 [4.564000] ohci_hcd :00:0e.4: OHCI Host Controller [4.564000] ohci_hcd :00:0e.4: new USB bus registered, assigned bus number 4 [4.564000] ohci_hcd :00:0e.4: irq 11, io mem 0x41021000 [4.692000] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001 [4.692000] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [4.692000] usb usb4: Product: OHCI Host Controller [4.692000] usb usb4: Manufacturer: Linux 2.6.35-trunk-loongson-2f ohci_hcd [4.692000] usb usb4: SerialNumber: :00:0e.4 [4.696000] hub 4-0:1.0: USB hub found [4.696000] hub 4-0:1.0: 4 ports detected [4.724000] usb 1-1: new high speed USB device using ehci_hcd and address 2 [4.896000] usb 1-1: New USB device found, idVendor=064e, idProduct=a114 [4.896000] usb 1-1: New USB device strings: Mfr=2, Product=1, SerialNumber=3 [4.896000] usb 1-1: Product: USB 2.0 Camera [4.896000] usb 1-1: Manufacturer: SuYin [4.896000] usb 1-1: SerialNumber: CN0317-S30C-MC03-VS-B20081113 [5.044000] usb 2-1: new high speed USB device using ehci_hcd and address 2 [5.188000] usb 2-1: New USB device found, idVendor=0bda, idProduct=0158 [
Bug#595711: linux-image-2.6.26-2-xen-686: Wrong free memory values for xen kernel with xenballoon use
В Пнд, 06/09/2010 в 07:59 +0100, Ian Campbell пишет:
On Mon, 2010-09-06 at 04:03 +0400, George Shuklin wrote:
I belive, this somehow related to difference in drivers/xen/balloon.c,
gentoo/SUSE version have some lines like
totalram_pages--;
(in balloon_append() function)
and
totalram_pages++;
(in balloon_retrieve() function)
Those lines are in Gentoo kernel (linux-2.6.34-xen) but absent in
Debian (linux-image-2.6.26-2-xen-686)
Is the Gentoo kernel pvops or classic-Xen patches?
Are you sure you are using the classic-Xen
(linux-image-...-xen-{686,amd}) kernel rather than the pvops one
(linux-image-...-686-bigmem, no 64 bit pvops in Lenny)?
I wasn't aware that it applied to the classic-Xen case but the
difference you describe sounds like this commit from upstream pvops:
http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commit;h=3d65c9488cadd2f11bd4d60c7266e639ece5d0d6
Probably for a 2.6.26 classic-Xen kernel you'd need to adjust the path
to drivers/xen/balloon/balloon.c and perhaps tweak some context a bit
but the concept should still apply.
Classic Xen (xen-686). pv_ops does not support preinflated ballooning
(maxmem mem), so I stuck with classic xen.
I think, balloon code does not differ (principally) in pv_ops and
classic xen.
And, in any way, this bug exists. And it really suck: application ask
memory, one part of kernel (or libc?) thinking of free memory, kernel
found 'no memory left' and start OOM killer. It walking and killing some
random applications (include init).
I'm testing kernel with with patch right now and it seems work fine -
memory reporting correctly and oom kills only most bloated application
requesting tons of memory.
Ian.
--
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/1283798194.27572.17.ca...@home.desunote.ru
Bug#595711: linux-image-2.6.26-2-xen-686: Wrong free memory values for xen kernel with xenballoon use
On Mon, 2010-09-06 at 22:36 +0400, George Shuklin wrote:
В Пнд, 06/09/2010 в 07:59 +0100, Ian Campbell пишет:
On Mon, 2010-09-06 at 04:03 +0400, George Shuklin wrote:
I belive, this somehow related to difference in drivers/xen/balloon.c,
gentoo/SUSE version have some lines like
totalram_pages--;
(in balloon_append() function)
and
totalram_pages++;
(in balloon_retrieve() function)
Those lines are in Gentoo kernel (linux-2.6.34-xen) but absent in
Debian (linux-image-2.6.26-2-xen-686)
Is the Gentoo kernel pvops or classic-Xen patches?
Are you sure you are using the classic-Xen
(linux-image-...-xen-{686,amd}) kernel rather than the pvops one
(linux-image-...-686-bigmem, no 64 bit pvops in Lenny)?
I wasn't aware that it applied to the classic-Xen case but the
difference you describe sounds like this commit from upstream pvops:
http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commit;h=3d65c9488cadd2f11bd4d60c7266e639ece5d0d6
Probably for a 2.6.26 classic-Xen kernel you'd need to adjust the path
to drivers/xen/balloon/balloon.c and perhaps tweak some context a bit
but the concept should still apply.
Classic Xen (xen-686). pv_ops does not support preinflated ballooning
(maxmem mem), so I stuck with classic xen.
I think, balloon code does not differ (principally) in pv_ops and
classic xen.
And, in any way, this bug exists. And it really suck: application ask
memory, one part of kernel (or libc?) thinking of free memory, kernel
found 'no memory left' and start OOM killer. It walking and killing some
random applications (include init).
I'm testing kernel with with patch right now and it seems work fine -
memory reporting correctly and oom kills only most bloated application
requesting tons of memory.
Great, thanks for testing, this confirms that the issue is resolved by
this patch.
Dann, Is it OK to commit a backport of this changeset as the start of
2.6.26-26?
Ian.
--
Ian Campbell
Keep on keepin' on.
signature.asc
Description: This is a digitally signed message part
Bug#595802: linux-2.6: spins forever on loading hostap-pci module in 2.6.32-5-486 rev 19,20,21
Package: linux-2.6 Version: 2.6.32-21 Severity: normal When I load the hostap-pci module on my laptop, it spins forever with the not very informative message __ratelimit: 123456 callbacks suppressed over and over. (that number obviously varies but is usually 6 digits). The laptop is crusoe-based, hence the -486 kernel. It works properly in 2.6.32-5-486 rev 15,17,18 and experimental's 2.6.35; it started breaking in this way w/ 2.6.32-5-486 rev 19. Neither keyboard nor ACPI events are parsed while spinning. This seems to be the same as archlinux bug 20726. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i586) Kernel: Linux 2.6.35-trunk-486 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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/e1osgwq-0005pv...@aryx.eamp.org
Bug#595187: linux-2.6: lots of OOPses on resume (NULL pointer dereference in file_ra_state_init)
Package: linux-2.6 Version: 2.6.32-21 i'm experiencing very similar issues, although also with earlier versions of linux-image-2.6.32-5-686. i first started having this problem after upgrading to squeeze from lenny, although i was running the exact same linux-image-2.6.32-* directly on lenny for quite some time without problems. i had been using uswsusp, but after experiencing this problem several times, i purged uswsusp and switched to using the in-kernel resume with pm-hibernate. an example OOPS below, if it's at all useful: Sep 5 19:00:35 mneme kernel: [ 7750.522234] BUG: unable to handle kernel NULL pointer dereference at 0010 Sep 5 19:00:35 mneme kernel: [ 7750.522243] IP: [c108cdc7] file_ra_state_init+0x3/0x18 Sep 5 19:00:35 mneme kernel: [ 7750.522256] *pde = Sep 5 19:00:35 mneme kernel: [ 7750.522261] Oops: [#3] SMP Sep 5 19:00:35 mneme kernel: [ 7750.522266] last sysfs file: /sys/devices/system/cpu/cpu1/cache/index2/shared_cpu_map Sep 5 19:00:35 mneme kernel: [ 7750.522272] Modules linked in: mct_u232 usbserial tun ip6table_filter ip6_tables iptable_filter ip_tables x_tables parport_pc ppdev lp parport sco bridge stp bnep rfcomm l2cap crc16 bluetooth acpi_cpufreq cpufreq_stats cpufreq_powersave cpufreq_conservative cpufreq_userspace kvm_intel kvm uinput fuse firewire_sbp2 loop snd_hda_codec_idt snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq i915 snd_timer drm_kms_helper joydev snd_seq_device arc4 ecb drm b43 snd yenta_socket soundcore i2c_i801 i2c_algo_bit psmouse snd_page_alloc rsrc_nonstatic mac80211 dell_laptop i2c_core rng_core serio_raw evdev dcdbas video cfg80211 output button processor battery ac rfkill ext3 jbd mbcache sha256_generic aes_i586 aes_generic cbc dm_crypt dm_mod sd_mod crc_t10dif ata_generic ssb sdhci_pci sdhci ata_piix mmc_core firewire_ohci tg3 libata pcmcia thermal uhci_hcd led_class firewire_core crc_itu_t libphy scsi_mod ehci_hcd therma Sep 5 19:00:35 mneme kernel: l_sys pcmcia_core usbcore nls_base [last unloaded: scsi_wait_scan] Sep 5 19:00:35 mneme kernel: [ 7750.522412] Sep 5 19:00:35 mneme kernel: [ 7750.522418] Pid: 10665, comm: x-terminal-emul Tainted: G D(2.6.32-5-686 #1) Latitude D420 Sep 5 19:00:35 mneme kernel: [ 7750.522424] EIP: 0060:[c108cdc7] EFLAGS: 00210202 CPU: 1 Sep 5 19:00:35 mneme kernel: [ 7750.522429] EIP is at file_ra_state_init+0x3/0x18 Sep 5 19:00:35 mneme kernel: [ 7750.522434] EAX: ef7f45c8 EBX: ECX: d5699800 EDX: Sep 5 19:00:35 mneme kernel: [ 7750.522438] ESI: ef7f4580 EDI: EBP: f6f73b18 ESP: c49a3ea0 Sep 5 19:00:35 mneme kernel: [ 7750.522443] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 Sep 5 19:00:35 mneme kernel: [ 7750.522448] Process x-terminal-emul (pid: 10665, ti=c49a2000 task=efaa1100 task.ti=c49a2000) Sep 5 19:00:35 mneme kernel: [ 7750.522452] Stack: Sep 5 19:00:35 mneme kernel: [ 7750.522455] c10b114b f6f28080 f68bb220 c49a3f00 ef7f4580 c49a3f00 c49a3f00 0003 Sep 5 19:00:35 mneme kernel: [ 7750.522465] 0 c10b12ac ef7f4580 c10b4c40 f6cdfe80 c49a3f00 c10bb254 Sep 5 19:00:35 mneme kernel: [ 7750.522476] 0 0002 efa7a000 ff9c c1c7cbc0 b7112000 fffa0844 ef992898 Sep 5 19:00:35 mneme kernel: [ 7750.522488] Call Trace: Sep 5 19:00:35 mneme kernel: [ 7750.522495] [c10b114b] ? __dentry_open+0x176/0x246 Sep 5 19:00:35 mneme kernel: [ 7750.522502] [c10b12ac] ? nameidata_to_filp+0x29/0x3c Sep 5 19:00:35 mneme kernel: [ 7750.522509] [c10b4c40] ? chrdev_open+0x0/0x116 Sep 5 19:00:35 mneme kernel: [ 7750.522516] [c10bb254] ? do_filp_open+0x43f/0x802 Sep 5 19:00:35 mneme kernel: [ 7750.522524] [c10c2f65] ? alloc_fd+0x52/0xb7 Sep 5 19:00:35 mneme kernel: [ 7750.522530] [c10b0ee3] ? do_sys_open+0x4c/0xdf Sep 5 19:00:35 mneme kernel: [ 7750.522536] [c10b0fba] ? sys_open+0x1e/0x23 Sep 5 19:00:35 mneme kernel: [ 7750.522543] [c10030fb] ? sysenter_do_call+0x12/0x28 Sep 5 19:00:35 mneme kernel: [ 7750.522547] Code: c3 53 89 d3 ff 74 24 0c ff 74 24 0c e8 0e 93 fa ff 5a 59 85 c0 75 0e 85 db 74 0a c7 05 34 fc 4a c1 00 00 00 00 5b c3 90 8b 52 40 8b 52 10 c7 40 14 ff ff ff ff c7 40 18 ff ff ff ff 89 50 0c c3 Sep 5 19:00:35 mneme kernel: [ 7750.522607] EIP: [c108cdc7] file_ra_state_init+0x3/0x18 SS:ESP 0068:c49a3ea0 Sep 5 19:00:35 mneme kernel: [ 7750.522616] CR2: 0010 Sep 5 19:00:35 mneme kernel: [ 7750.522620] ---[ end trace f383376f90ced1d2 ]--- live well, vagrant -- Package-specific info: ** Version: Linux version 2.6.32-5-686 (Debian 2.6.32-21) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-2) ) #1 SMP Wed Aug 25 14:28:12 UTC 2010 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.32-5-686 root=/dev/mapper/mneme-rwt ro quiet ** Not tainted ** Kernel log: [ 5400.080272] CPU: Physical Processor ID: 0 [ 5400.080272] CPU: Processor Core ID: 1 [ 5400.080272] CPU1:
Bug#571035: [squeeze alpha1] installationsreport: grub2: machine doesn't boot
Hello, Ben Hutchings b...@decadent.org.uk wrote: On Sun, 2010-09-05 at 23:15 +0200, Holger Wansing wrote: 2. the second is a debian-installer kernel. I copied the kernel and initrd from a debian-installer netinst cd (the same cd which was used to perform the test installation, leading to this bugreport #571035, an debian-testing daily build from 23. Aug 2010. That kernel boots fine!!! So what's the version of that kernel (from /proc/version)? ~ # cat /proc/version Linux version 2.6.32-5-486 (Debian 2.6.32-15) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-1) ) #1 Tue Jun 1 04:27:25 UTC 2010 Be aware, that this is a debian-installer kernel (booting that kernel brings up the debian installation process). That might have another config? Holger -- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = Created with Sylpheed 2.5.0 under DEBIAN GNU/LINUX 5.0.0 - L e n n y Registered LinuxUser #311290 - http://counter.li.org/ = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -- 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/20100906220421.cfffb575.li...@wansing-online.de
Bug#520468: Incorporate fixes for WUSB54GS support from 2.6.33
Hi, I just tested the status of the support for this card using the Debian kernel packages. Here are the updated results: - Squeeze's kernel (2.6.32-5-686 / 2.6.32-21): It still does not work, either with network-manager or without it. - Kernel at experimental (2.6.35-trunk-686 / 2.6.35-1~experimental.2): It *is* working. If I use if/iwconfig (with n-m disabled/uninstalled), a backtrace is still printed to the syslog, but the adapter seems to be working. The driver doesn't seem to be crashing when I plug in the device anymore. The problems now only occur when I try to configure it. Please see the attached logs for more details. Best regards, Pitxyoki Kernel currently at the squeeze repositories (linux-image-2.6.32-5-686 / 2.6.32-21): Without network-manager: 1. Plugged in the device: Sep 6 12:42:50 C-5 kernel: [ 600.568024] usb 2-2: new full speed USB device using uhci_hcd and address 3 Sep 6 12:42:50 C-5 kernel: [ 600.743785] usb 2-2: New USB device found, idVendor=13b1, idProduct=000e Sep 6 12:42:50 C-5 kernel: [ 600.743790] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Sep 6 12:42:50 C-5 kernel: [ 600.743794] usb 2-2: Product: Linksys Wireless-G USB Network Adapter with SpeedBooster Sep 6 12:42:50 C-5 kernel: [ 600.743797] usb 2-2: Manufacturer: Cisco-Linksys Sep 6 12:42:50 C-5 kernel: [ 600.743800] usb 2-2: SerialNumber: Sep 6 12:42:50 C-5 kernel: [ 600.743927] usb 2-2: configuration #1 chosen from 1 choice Sep 6 12:42:50 C-5 kernel: [ 600.840076] usbcore: registered new interface driver cdc_ether Sep 6 12:42:50 C-5 kernel: [ 600.977837] usbcore: registered new interface driver rndis_host Sep 6 12:42:50 C-5 kernel: [ 601.031500] cfg80211: Using static regulatory domain info Sep 6 12:42:50 C-5 kernel: [ 601.031506] cfg80211: Regulatory domain: US Sep 6 12:42:50 C-5 kernel: [ 601.031509] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) Sep 6 12:42:50 C-5 kernel: [ 601.031515] (2402000 KHz - 2472000 KHz @ 4 KHz), (600 mBi, 2700 mBm) Sep 6 12:42:50 C-5 kernel: [ 601.031520] (517 KHz - 519 KHz @ 4 KHz), (600 mBi, 2300 mBm) Sep 6 12:42:50 C-5 kernel: [ 601.031525] (519 KHz - 521 KHz @ 4 KHz), (600 mBi, 2300 mBm) Sep 6 12:42:50 C-5 kernel: [ 601.031536] (521 KHz - 523 KHz @ 4 KHz), (600 mBi, 2300 mBm) Sep 6 12:42:50 C-5 kernel: [ 601.031536] (523 KHz - 533 KHz @ 4 KHz), (600 mBi, 2300 mBm) Sep 6 12:42:50 C-5 kernel: [ 601.031538] (5735000 KHz - 5835000 KHz @ 4 KHz), (600 mBi, 3000 mBm) Sep 6 12:42:50 C-5 kernel: [ 601.031890] cfg80211: Calling CRDA for country: US Sep 6 12:42:50 C-5 kernel: [ 601.097776] usb%d: media disconnect Sep 6 12:42:50 C-5 kernel: [ 601.283712] wlan0: register 'rndis_wlan' at usb-:00:1d.1-2, Wireless RNDIS device, BCM4320a based, 00:12:17:a0:b9:7c Sep 6 12:42:50 C-5 kernel: [ 601.283742] usbcore: registered new interface driver rndis_wlan 2. [13:09:20] C-5:~# iwconfig wlan0 essid MYESSID [13:09:41] C-5:~# iwconfig wlan0 key XX [13:09:44] C-5:~# dhclient wlan0 Sep 6 13:09:53 C-5 kernel: [ 114.730225] ADDRCONF(NETDEV_UP): wlan0: link is not ready Sep 6 13:09:53 C-5 kernel: [ 114.731999] wlan0: couldn't set packet filter: 000d Sep 6 13:09:53 C-5 kernel: [ 114.733999] wlan0: couldn't set packet filter: 000d Sep 6 13:09:53 C-5 kernel: [ 114.735997] wlan0: setting infra mode failed (FFEA) Sep 6 13:09:53 C-5 kernel: [ 114.737998] wlan0: setting infra mode failed (FFEA) Sep 6 13:09:53 C-5 kernel: [ 114.738995] wlan0: setting SSID failed (FFEA) Sep 6 13:09:53 C-5 kernel: [ 114.741018] wlan0: couldn't set packet filter: 000d Sep 6 13:09:53 C-5 kernel: [ 114.743002] wlan0: couldn't set packet filter: 000d Sep 6 13:09:54 C-5 dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67 Sep 6 13:10:00 C-5 dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67 Sep 6 13:10:07 C-5 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7 Sep 6 13:10:14 C-5 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15 Sep 6 13:10:29 C-5 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9 Sep 6 13:10:38 C-5 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11 Sep 6 13:10:49 C-5 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11 Sep 6 13:11:00 C-5 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8 Sep 6 13:11:08 C-5 dhclient: No DHCPOFFERS received. Sep 6 13:11:08 C-5 dhclient: Trying recorded lease 192.168.2.115 Sep 6 13:11:08 C-5 kernel: [ 189.560861] wlan0: couldn't set packet filter: 000d Sep 6 13:11:08 C-5 kernel: [ 189.563076] wlan0: couldn't set packet filter: 000d Sep 6 13:11:11 C-5 dhclient: No working leases in persistent database - sleeping. Sep 6 13:11:11 C-5 kernel: [ 192.585036] wlan0: couldn't set
Bug#595821: linux-image-2.6.32-5-xen-amd64: IPv6 ping rtt increased by 12 ms when using xen version of kernel
Package: linux-2.6 Version: 2.6.32-21 Severity: normal Tags: ipv6 When using the xen version of the kernel, ping rtt increases by about 12ms compared to the same system running the non xen version of the kernel. The ping rtt was measured between two hosts on different IPv6 sites. Output of ping6 running while rebooting the machine from non xen kernel to xen kernel: 64 bytes from 2a01:4f8:x:4442::1: icmp_seq=6 ttl=58 time=19.6 ms 64 bytes from 2a01:4f8:x:4442::1: icmp_seq=7 ttl=58 time=20.1 ms 64 bytes from 2a01:4f8:x:4442::1: icmp_seq=8 ttl=58 time=19.5 ms 64 bytes from 2a01:4f8:x:4442::1: icmp_seq=9 ttl=58 time=19.8 ms 64 bytes from 2a01:4f8:x:4442::1: icmp_seq=10 ttl=58 time=32.2 ms 64 bytes from 2a01:4f8:x:4442::1: icmp_seq=78 ttl=58 time=36.4 ms 64 bytes from 2a01:4f8:x:4442::1: icmp_seq=79 ttl=58 time=33.0 ms 64 bytes from 2a01:4f8:x:4442::1: icmp_seq=80 ttl=58 time=32.6 ms The situation kept the same with several reboots of the different kernel versions. rtt with the -xen kernel was always about 12ms higher than with non xen kernel. -- Package-specific info: ** Version: Linux version 2.6.32-5-xen-amd64 (Debian 2.6.32-21) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-2) ) #1 SMP Wed Aug 25 16:02:22 UTC 2010 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.32-5-xen-amd64 root=UUID=92490bb2-c590-4b89-9c01-779a680672b2 ro quiet ** Not tainted ** Kernel log: [4.705067] raid6: sse2x48910 MB/s [4.705070] raid6: using algorithm sse2x4 (8910 MB/s) [4.708012] md: raid6 personality registered for level 6 [4.708014] md: raid5 personality registered for level 5 [4.708015] md: raid4 personality registered for level 4 [4.711778] md: raid10 personality registered for level 10 [4.713651] 3ware Storage Controller device driver for Linux v1.26.02.002. [4.715746] 3ware 9000 Storage Controller device driver for Linux v2.26.02.012. [4.718356] Adaptec aacraid driver 1.1-5[2461]-ms [4.772169] md: md0 stopped. [4.777425] md: bindsdb1 [4.777638] md: bindsda1 [4.779014] raid1: raid set md0 active with 2 out of 2 mirrors [4.779028] md0: detected capacity change from 0 to 4299751424 [4.779703] md0: [4.781581] md: md1 stopped. [4.789488] md: bindsdb2 [4.789844] md: bindsda2 [4.790981] raid1: raid set md1 active with 2 out of 2 mirrors [4.791003] md1: detected capacity change from 0 to 2154954752 [4.791855] md1: unknown partition table [4.809110] unknown partition table [4.811064] md: md2 stopped. [4.881164] md: bindsdb3 [4.889153] md: bindsda3 [4.890434] raid1: raid set md2 active with 2 out of 2 mirrors [4.890456] md2: detected capacity change from 0 to 8011317248 [4.891343] md2: unknown partition table [4.905595] md: md3 stopped. [4.935003] md: bindsdb4 [4.935315] md: bindsda4 [4.936824] raid1: md3 is not clean -- starting background reconstruction [4.936826] raid1: raid set md3 active with 2 out of 2 mirrors [4.936840] md3: detected capacity change from 0 to 1485830946816 [4.937482] md3: unknown partition table [4.942279] device-mapper: uevent: version 1.0.3 [4.942423] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-de...@redhat.com [ 15.128684] PM: Starting manual resume from disk [ 15.128687] PM: Resume from partition 8:1 [ 15.128688] PM: Checking hibernation image. [ 15.211558] PM: Error -22 checking image file [ 15.211560] PM: Resume from disk failed. [ 15.364873] kjournald starting. Commit interval 5 seconds [ 15.364884] EXT3-fs: mounted filesystem with ordered data mode. [ 16.168636] udev: starting version 160 [ 16.426855] ACPI: WMI: Mapper loaded [ 16.456353] input: PC Speaker as /devices/platform/pcspkr/input/input2 [ 16.459547] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3 [ 16.459550] ACPI: Power Button [PWRB] [ 16.459591] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4 [ 16.459594] ACPI: Power Button [PWRF] [ 16.666150] i801_smbus :00:1f.3: PCI INT C - GSI 18 (level, low) - IRQ 18 [ 16.719570] [drm] Initialized drm 1.1.0 20060810 [ 16.735998] Error: Driver 'pcspkr' is already registered, aborting... [ 16.758454] nouveau :02:00.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [ 16.758458] nouveau :02:00.0: setting latency timer to 64 [ 16.760295] [drm] nouveau :02:00.0: Detected an NV50 generation card (0x298200a2) [ 16.761035] [drm] nouveau :02:00.0: Attempting to load BIOS image from PRAMIN [ 16.810019] [drm] nouveau :02:00.0: ... appears to be valid [ 16.810022] [drm] nouveau :02:00.0: BIT BIOS found [ 16.810024] [drm] nouveau :02:00.0: Bios version 62.98.71.00 [ 16.810026] [drm] nouveau :02:00.0: TMDS table revision 2.0 not currently supported [
Bug#595821: Acknowledgement (linux-image-2.6.32-5-xen-amd64: IPv6 ping rtt increased by 12 ms when using xen version of kernel)
I think it wasn't clear in the first report: IPv4 is not affected. -- 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/4c856a90.7090...@nvbi.de
Bug#595827: initramfs-tools: Add hid-cherry and hid-logitech to initramfs
Package: initramfs-tools
Version: 0.98.1
Severity: important
Tags: patch
Both a Cherry and a Logitech keyboard I own cannot be used at early boot time
unless one also adds the hid-cherry / the hid-logitech module to the initramfs.
The attached patch adds those two modules to hook-functions.
For the Cherry keyboard, kernels up to 2.6.32-3 are not affected, from 2.6.32-5
(squeeze default) onwards all tested kernels were affected. Didn't do detailed
checks for the Logitech keyboard.
The used devices that exhibit this problem are:
ID 046d:c30a Logitech, Inc. iTouch Composite
ID 046a:0023 Cherry GmbH CyMotion Master Linux Keyboard
Severity level important, since this makes booting with encrypted root
partition impossible using those keyboards.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (600, 'testing'), (500, 'lucid'), (400, 'experimental'), (400,
'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.35-trunk-686 (SMP w/2 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 initramfs-tools depends on:
ii cpio 2.11-4 GNU cpio -- a program to manage ar
ii findutils 4.4.2-1utilities for finding files--find,
ii klibc-utils 1.5.20-1 small utilities built with klibc f
ii module-init-tools 3.12-1 tools for managing Linux kernel mo
ii udev 161-1 /dev/ and hotplug management daemo
Versions of packages initramfs-tools recommends:
ii busybox 1:1.17.1-4 Tiny utilities for small and embed
Versions of packages initramfs-tools suggests:
ii bash-completion 1:1.2-2programmable completion for the ba
-- no debconf information
diff --git a/hook-functions b/hook-functions
index 9d63d58..0684296 100644
--- a/hook-functions
+++ b/hook-functions
@@ -394,7 +394,7 @@ auto_add_modules()
case ${1:-} in
base)
for x in ehci-hcd ohci-hcd uhci-hcd usbhid xhci hid-apple \
- hid-microsoft \
+ hid-cherry hid-logitech hid-microsoft \
btrfs ext2 ext3 ext4 ext4dev isofs jfs nfs reiserfs udf xfs \
af_packet atkbd i8042 virtio_pci; do
manual_add_modules ${x}
Bug#595187: linux-2.6: lots of OOPses on resume (NULL pointer dereference in file_ra_state_init)
On Mon, 2010-09-06 at 12:27 -0700, Vagrant Cascadian wrote: Package: linux-2.6 Version: 2.6.32-21 i'm experiencing very similar issues, although also with earlier versions of linux-image-2.6.32-5-686. i first started having this problem after upgrading to squeeze from lenny, although i was running the exact same linux-image-2.6.32-* directly on lenny for quite some time without problems. i had been using uswsusp, but after experiencing this problem several times, i purged uswsusp and switched to using the in-kernel resume with pm-hibernate. [...] And did that make any difference? 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#595802: linux-2.6: spins forever on loading hostap-pci module in 2.6.32-5-486 rev 19,20,21
On Mon, 2010-09-06 at 15:01 -0400, Robert Jacobs wrote: Package: linux-2.6 Version: 2.6.32-21 Severity: normal When I load the hostap-pci module on my laptop, it spins forever with the not very informative message __ratelimit: 123456 callbacks suppressed over and over. (that number obviously varies but is usually 6 digits). [...] And what is the message before that? 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 595802
Processing commands for cont...@bugs.debian.org: tags 595802 + moreinfo Bug #595802 [linux-2.6] linux-2.6: spins forever on loading hostap-pci module in 2.6.32-5-486 rev 19,20,21 Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 595802: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595802 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.128381492715348.transcr...@bugs.debian.org
Bug#594845: Acknowledgement (linux-image-2.6.32-5-amd64: kernel BUG at /build/buildd-linux-2.6_2.6.32-20-amd64-lNUT1p/..../fs/sysfs/file.c:539)
On Mon, 2010-09-06 at 21:47 +1000, Russell Stuart wrote: [...] The steps I used to generate the kernel are: $ apt-get source linux-2.6 $ cd linux-2.6-2.6.32 $ fakeroot debian/rules source $ fakeroot debian/rules setup $ patch -p1 .../0001-tun-Don-t-add-sysfs-attributes-to-devices-without-sy.patch $ ed drivers/net/tun.c # add trace [...] You are editing in the wrong place. The patch needs to be applied in debian/build/source_amd64_none. The debian/bin/test-patches script can handle this all for you. 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#595502: closed by Ben Hutchings b...@decadent.org.uk (Re: Bug#595502: linux-image-2.6.32-5-mckinley: panics while loading INIT, IOMMU out of mapping resources)
On Mon, 2010-09-06 at 13:40 +0200, Thibaut VARENE wrote: reopen 595502 thanks Version: 2.6.32-21 Please, explain to me how changing a Panic into a Warning without effectively fixing the root cause of the bug fixes anything? And, oh, if by graceful failure you mean: it will blow up your raid devices and kill your filesystems, then yes, the failure has been very graceful for me, thankyouverymuch. I could have lived with a little less gracefulness, though ;-/ [...] There's no need to take your frustration out on me. I know nothing about IA64 and have to assume that upstream developers know what they are doing. Please test Linux 2.6.35 as packaged in experimental. 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 595821
Processing commands for cont...@bugs.debian.org: # This tag means missing IPv6 support tags 595821 - ipv6 Bug #595821 [linux-2.6] linux-image-2.6.32-5-xen-amd64: IPv6 ping rtt increased by 12 ms when using xen version of kernel Removed tag(s) ipv6. thanks Stopping processing here. Please contact me if you need assistance. -- 595821: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595821 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.128381522317677.transcr...@bugs.debian.org
Bug#595502: closed by Ben Hutchings b...@decadent.org.uk (Re: Bug#595502: linux-image-2.6.32-5-mckinley: panics while loading INIT, IOMMU out of mapping resources)
Le 7 sept. 10 à 01:18, Ben Hutchings a écrit : On Mon, 2010-09-06 at 13:40 +0200, Thibaut VARENE wrote: reopen 595502 thanks Version: 2.6.32-21 Please, explain to me how changing a Panic into a Warning without effectively fixing the root cause of the bug fixes anything? And, oh, if by graceful failure you mean: it will blow up your raid devices and kill your filesystems, then yes, the failure has been very graceful for me, thankyouverymuch. I could have lived with a little less gracefulness, though ;-/ [...] There's no need to take your frustration out on me. I know nothing I don't think I've taken out my frustration on you, I would have been a lot less ironic and a lot more postal if I had been to take the frustration resulting from the pain this caused me on anyone... I must say tho I'm quite frustrated that incremental kernel upgrades to the now frozen next stable release introduce *regressions*... about IA64 and have to assume that upstream developers know what they are doing. That remains an open question ;P Please test Linux 2.6.35 as packaged in experimental. I'm afraid this is absolutely not happening, this machine is a webserver and I've just spent enough time bringing it back to life... Besides squeeze is not shipping with 2.6.35, right? I'm hoping you plan on releasing a working kernel for the upcoming stable release? One thing I don't get is why the need to break a perfectly working kernel (2.6.32-9)? Can't the specific change that introduced this bug be simply reverted? -- 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/f4598a54-3601-4127-a645-434ade77d...@debian.org
Bug#595187: linux-2.6: lots of OOPses on resume (NULL pointer dereference in file_ra_state_init)
On Tue, Sep 07, 2010 at 12:10:09AM +0100, Ben Hutchings wrote: On Mon, 2010-09-06 at 12:27 -0700, Vagrant Cascadian wrote: Package: linux-2.6 Version: 2.6.32-21 i'm experiencing very similar issues, although also with earlier versions of linux-image-2.6.32-5-686. i first started having this problem after upgrading to squeeze from lenny, although i was running the exact same linux-image-2.6.32-* directly on lenny for quite some time without problems. i had been using uswsusp, but after experiencing this problem several times, i purged uswsusp and switched to using the in-kernel resume with pm-hibernate. [...] And did that make any difference? heh. sorry for being unclear :) unfortunately, no, it's still Oops'ing after resume. i also didn't mention, largely because i'm pretty unsure if it's really the case, but the issue *seems* to occur more reliably when hibernating (to disk) while on battery, but i'm really unsure of that. i'll see if i can more reliably trigger the same problem on a clean squeeze install on the same hardware in another partition... where i'm not as worried about crashing. live well, vagrant -- 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/20100907000545.gx28...@claws.fglan
Bug#595554: 3c59x hangs on Vortex cards
* Ben Hutchings b...@decadent.org.uk wrote: Please can you test my attempted fix for this - either: 1. Get the fixed module http://people.debian.org/~benh/3c59x.ko and the signature file http://people.debian.org/~benh/3c59x.ko.asc, verify my signature with gpg, and then load the module: rmmod 3c59x insmod 3c59x.ko Hi Ben, done this, and I'm now online over my Vortex with this module, seems like it works, though the message , | eth0: vortex_error(), status=0xe091 ` is still printed in syslog if I turn on debugging. Thanks Jens -- 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/20100907004651.ga29...@sge.kicks-ass.org
Bug#595554: 3c59x hangs on Vortex cards
On Tue, 2010-09-07 at 02:46 +0200, Jens Schüßler wrote: * Ben Hutchings b...@decadent.org.uk wrote: Please can you test my attempted fix for this - either: 1. Get the fixed module http://people.debian.org/~benh/3c59x.ko and the signature file http://people.debian.org/~benh/3c59x.ko.asc, verify my signature with gpg, and then load the module: rmmod 3c59x insmod 3c59x.ko Hi Ben, done this, and I'm now online over my Vortex with this module, seems like it works, Good! I'll add this patch to the next version of the kernel package. though the message , | eth0: vortex_error(), status=0xe091 ` is still printed in syslog if I turn on debugging. vortex_error() is also called for some conditions that aren't errors. 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 595554
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 595554 + pending Bug #595554 [linux-2.6] 3c59x hangs on Vortex cards Added tag(s) pending. End of message, stopping processing here. Please contact me if you need assistance. -- 595554: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595554 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.12838223032768.transcr...@bugs.debian.org
Bug#595554: [PATCH net-2.6] 3c59x: Fix deadlock in vortex_error()
This fixes a bug introduced in commit
de847272149365363a6043a963a6f42fb91566e2
3c59x: Use fine-grained locks for MII and windowed register access.
vortex_interrupt() holds vp-window_lock over multiple register
accesses to reduce locking overhead. However it also needs to call
vortex_error() sometimes, and that uses the regular functions for
access to windowed registers, which will try to acquire window_lock
again.
Therefore, drop window_lock around the call to vortex_error() and set
the window afterward reacquiring the lock. Since vortex_error() may
call vortex_rx(), which *does* require its caller to hold window_lock,
lift that call up into vortex_interrupt(). This also removes the
potential for calling vortex_rx() on a later-generation NIC.
Reported-and-tested-by: Jens Schüßler j...@trash.net [in Debian's 2.6.32]
Signed-off-by: Ben Hutchings b...@decadent.org.uk
---
Dave,
This is the regression I mentioned before. 3c59x should be good after
this.
Ben.
drivers/net/3c59x.c | 10 +++---
1 files changed, 7 insertions(+), 3 deletions(-)
diff --git a/drivers/net/3c59x.c b/drivers/net/3c59x.c
index a045559..85671ad 100644
--- a/drivers/net/3c59x.c
+++ b/drivers/net/3c59x.c
@@ -1994,10 +1994,9 @@ vortex_error(struct net_device *dev, int status)
}
}
- if (status RxEarly) { /* Rx early is unused.
*/
- vortex_rx(dev);
+ if (status RxEarly) /* Rx early is unused.
*/
iowrite16(AckIntr | RxEarly, ioaddr + EL3_CMD);
- }
+
if (status StatsFull) { /* Empty statistics. */
static int DoneDidThat;
if (vortex_debug 4)
@@ -2298,7 +2297,12 @@ vortex_interrupt(int irq, void *dev_id)
if (status (HostError | RxEarly | StatsFull | TxComplete |
IntReq)) {
if (status == 0x)
break;
+ if (status RxEarly)
+ vortex_rx(dev);
+ spin_unlock(vp-window_lock);
vortex_error(dev, status);
+ spin_lock(vp-window_lock);
+ window_set(vp, 7);
}
if (--work_done 0) {
--
1.7.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/1283822830.5323.562.ca...@localhost
Bug#595554: [PATCH net-2.6] 3c59x: Fix deadlock in vortex_error()
From: Ben Hutchings b...@decadent.org.uk Date: Tue, 07 Sep 2010 02:27:10 +0100 This is the regression I mentioned before. 3c59x should be good after this. Excellent, applied, 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/20100906.182908.200386818.da...@davemloft.net
