[PATCH]: linux-2.6: use string operators instead of numeric ones for string concatenation
Revision 16224 of svn://svn.debian.org/svn/kernel/dists/trunk/linux-2.6
enabled use strict; and use warnings; for the perl based maintainer
scripts of linux-ima...@upstreamversion@@abiname@@localversion@, this in
turn exposed that the numeric '+=' operator is used to concatenate
$message and $dir_message variables; this patch fixes this by using the
string operator '.='.
Argument Module sub-directories were detected.\n isn't numeric in addition
(+) at /var/lib/dpkg/tmp.ci/preinst line 100.
Argument isn't numeric in addition (+) at /var/lib/dpkg/tmp.ci/preinst line
100.
Signed-off-by: Stefan Lippers-Hollmann s@gmx.de
---
debian/templates/temp.image.plain/preinst |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff -Nrup a/debian/templates/temp.image.plain/preinst
b/debian/templates/temp.image.plain/preinst
--- a/debian/templates/temp.image.plain/preinst
+++ b/debian/templates/temp.image.plain/preinst
@@ -97,7 +97,7 @@ sub check {
unless $dir_message;
}
}
-$message += $dir_message if $dir_message;
+$message .= $dir_message if $dir_message;
}
my @links = grep { -l $lib_modules/$_ } @children;
@@ -108,10 +108,10 @@ sub check {
next if ($link =~ /^source$/);
$links_message = Symbolic links were detected in
$modules_base/$version.\n;
}
-$message += $links_message if $links_message;
+$message .= $links_message if $links_message;
}
my @files = grep { -f $lib_modules/$_ } @children;
- $message += Additional files also exist in $modules_base/$version.\n
+ $message .= Additional files also exist in $modules_base/$version.\n
if ($#files -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/201009030942.20493.s@gmx.de
[Fwd: [Maverick] [PATCH 0/4] KMS Disablement for i8xx]
Forwarded Message From: leann.ogasaw...@canonical.com To: kernel-t...@lists.ubuntu.com Cc: christopher.halse.rog...@canonical.com Subject: [Maverick] [PATCH 0/4] KMS Disablement for i8xx Date: Tue, 31 Aug 2010 09:13:12 -0700 In Lucid, we were carrying the following 4 patches to disable KMS for a known set of broken devices, specifically some i8xx chipsets [1]. We purposely didn't carry these SAUCE patches forward to Maverick in hopes that this would no longer be an issue. Unfortunately, this does not appear to be the case. I'll be re-applying the following 4 patches to Maverick. Thanks, Leann [1] https://wiki.ubuntu.com/X/Bugs/Lucidi8xxFreezes Andy Whitcroft (4): UBUNTU: SAUCE: i915 KMS -- support disabling KMS for known broken devices UBUNTU: SAUCE: i915 KMS -- blacklist i830 UBUNTU: SAUCE: i915 KMS -- blacklist i845g UBUNTU: SAUCE: i915 KMS -- blacklist i855 drivers/gpu/drm/i915/i915_drv.c | 16 1 files changed, 16 insertions(+), 0 deletions(-) -- kernel-team mailing list kernel-t...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kernel-team signature.asc Description: This is a digitally signed message part
[Fwd: Re: [Maverick] [PATCH 0/4] KMS Disablement for i8xx]
Forwarded Message From: Leann Ogasawara leann.ogasaw...@canonical.com To: Christopher James Halse Rogers christopher.halse.rog...@canonical.com Cc: kernel-t...@lists.ubuntu.com Subject: Re: [Maverick] [PATCH 0/4] KMS Disablement for i8xx Date: Thu, 02 Sep 2010 17:10:11 -0700 On Fri, 2010-09-03 at 09:52 +1000, Christopher James Halse Rogers wrote: On Thu, 2010-09-02 at 14:25 -0400, Steven wrote: Dear Kernel Team, Please do NOT reapply these patches. UMS causes the majority of 8xx cards to boot to a black screen on Lucid and forward. I spent at least a month fixing probably a hundred different peoples' install problems after Lucid was released because of these patches. The situation in Maverick is different. In Lucid, we had the 2.9.1 Intel X driver, which still had a UMS codepath. In Maverick, we have 2.12, which does not have any UMS code. The Intel driver in Maverick will not load without KMS. Disabling KMS on these cards in Lucid resulted in them using the UMS codepaths of the Intel X driver, and in many cases failing. Disabling KMS on these cards in Maverick will result in them using the VESA X driver, which has been reported to work on the various i8xx bugs. If you do decide to reapply these, PLEASE consider paying especially close attention to bugs related to this change, at the very least. I will. Chris, thanks for the follow up and the clarification. Based on your feedback, I'll go ahead and re-apply these patches. Thanks, Leann -- kernel-team mailing list kernel-t...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kernel-team signature.asc Description: This is a digitally signed message part
Bug#595364: Assumes /etc/fstab exists (it doesn't in cdebootstrap).
Package: linux-base Version: 2.6.34-1~experimental.2 Severity: minor I had cdebootstrap generate a squeeze chroot, and installed a kernel into it. When I then ran dpkg-reconfigure -a -plow in the chroot, this package borked the dpkg-reconfigure run because /etc/fstab doesn't exist. + chroot cdebootstrap-amd64 dpkg-reconfigure -a -plow [...] ifupdown.postinst: Warning: No 'iface lo' definition found in /etc/network/interfaces ifupdown.postinst: Warning: No 'auto lo' statement found in /etc/network/interfaces update-initramfs: Generating /boot/initrd.img-2.6.32-5-amd64 df: Warning: cannot read table of mounted file systems: No such file or directory warning: can't open /etc/mtab: No such file or directory egrep: /etc/fstab: No such file or directory egrep: /etc/fstab: No such file or directory No such file or directory at /var/lib/dpkg/info/linux-base.postinst line 1207, STDIN line 1. This is an unusual case and I can work around it by creating an empty fstab before running dpkg-reconfigure, but you might want to consider adding a test for /etc/fstab's existence. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.35 (SMP w/2 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-base depends on: ii debconf [debconf-2.0] 1.5.35 Debian configuration management sy ii libapt-pkg-perl 0.1.24+b1 Perl interface to libapt-pkg ii libuuid-perl 0.02-4 Perl extension for using UUID inte ii udev 161-1 /dev/ and hotplug management daemo ii util-linux2.17.2-3.1 Miscellaneous system utilities linux-base recommends no packages. linux-base suggests no packages. -- debconf information excluded -- 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/20100903133402.10985.59938.report...@dali
Bug#488566: bug
the problem still remains on linux-image version 2.6.32+28 bye. -- 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/blu0-smtp1960ef7459069dc73205ff0c1...@phx.gbl
Bug#571035: [squeeze alpha1] installationsreport: grub2: machine doesn't boot
Hello, On Sun, Aug 29, 2010 at 5:24 PM, Holger Wansing li...@wansing-online.de wrote: http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/debian-testing-i386-netinst.iso We need to know the date of it ;-) -- 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/aanlktimk8zs+r-dhy14m=mi6elmpts=cri7-bdh=1...@mail.gmail.com
Bug#594089: keyboard-configuration: caps lock keycode problem
On 09/02/2010 03:46 PM, Samuel Thibault wrote: Hello, Tom Vier, le Thu 02 Sep 2010 15:11:49 -0400, a écrit : It says UNICODE mode and the codes for caps lock are: press: 0x3a 0xe0 0x66 repeat: 0x3a release: 0xba 0xe0 0x 0xe6 I guess? Yes. I also just discovered the right shift key goes back a page in iceweasel. Here are the right-shift codes: showkey -s: press: 0x36 0xe0 0x6a repeat: 0x36 release: 0xb6 0xe0 0xea All this looks like one of the few keyboard glitches that linux-2.6 fixes for some keyboards known to be bogus, while other keyboards do use these scancodes to report e.g. multimedia keys. Could you try showkey -s with the older, working kernel? Samuel Stable (2.6.26) which worked fine gives the same as Testing (2.6.32): press: 0x3a 0xe0 0x66 repeat: 0x3a release: 0xba 0xe0 0xe6 ...which makes me think it's an xorg problem, but I'm not familiar with how the whole keyboard stack works. I tried a different usb keyboard (a Dell) under Testing and it works normally with iceweasel: press: 0x3a repeat: 0x3a release: 0x3b I wonder why the logitech generates so many codes. -- Tom Vier t...@triadsys.com Senior Net/Sys Admin Triad Systems Engineering, Inc. 703-956-1535 office 703-984-9093 cell 703-404-0308 helpdesk -- 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/4c815c23.2070...@triadsys.com
Re: [PATCH]: linux-2.6: use string operators instead of numeric ones for string concatenation
On Fri, 2010-09-03 at 09:42 +0200, Stefan Lippers-Hollmann wrote: Revision 16224 of svn://svn.debian.org/svn/kernel/dists/trunk/linux-2.6 enabled use strict; and use warnings; for the perl based maintainer scripts of linux-ima...@upstreamversion@@abiname@@localversion@, this in turn exposed that the numeric '+=' operator is used to concatenate $message and $dir_message variables; this patch fixes this by using the string operator '.='. Thanks for testing and reporting this. This sort of stupid bug is exactly why we need those directives. However, given that this bug was introduced by: kernel-package (10.037) unstable; urgency=medium ... * Vy popular demand, we toned down the checks for overwriting previously installed kernels. Instead of checking for /lib/modules/$version, we only check is /lib/modules/$version/kernel exists. This means that third party modules shall not trigger any interactions with the user; it is up to the users to handle incompatibilites between previously installed third party modules and the new kernel. No check on official kernel images -- any incompatibilities should result in an ABI number change. -- Manoj Srivastava sriva...@debian.org Wed, 22 Mar 2006 14:24:16 -0600 and makes the check() subroutine completely useless, and no-one seems to have complained, I think we could just remove it. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Re: netxen_nic support for unified firmware images
On Thu, 2010-09-02 at 17:20 -0600, dann frazier wrote: I'd like to propose we add support for unified firmware images for netxen nics for squeeze. HP ships servers with netxen controllers, and we've seen problems with old firmware/new driver combinations - basically the network runs ridiculously slow, causing network installs to take many hours. Flashing to the latest firmware resolves the issues - but flashing a system (or 50) before install can be a pain (once you've finally identified firmware as the problem). There's an online flash tool you can use post-install but, as of this writing, it is not very Debian friendly (distributed in an RPM, needs out of tree driver, script has incompatible paths/bashisms). netxen_nic can load updated firmware via request_firmware, and recently a firmware blob got accepted into the linux-firmware tree w/ a non-free-compatible license, specifically for this reason. However, this blob is in a newer unified format that the 2.6.32 driver didn't yet support. This patch cherry picks the change to add support for the unified rom image, as well as several fixes that came after. I prefer to deal with individual patches as it's easier to compare them with the upstream version that way. I'm not sure how much that matters here. In addition, I'd like to also package the firmware blob. The blob alone is 1.7 MB, whereas the entire contents of firmware-linux-nonfree is 940K. That implies to me that it should be a new binary package, but I don't feel strongly about that. It should be. Any objections to these changes? AFAIK only HP shipped many of these NICs so if you (wearing your HP hat) are happy with the changes then that's good enough for me. 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 594561
Processing commands for cont...@bugs.debian.org: tags 594561 - moreinfo Bug #594561 [linux-2.6] firmware-ralink: fails to detect APs at frequency 2.472GHz Removed tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 594561: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594561 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.128355469225439.transcr...@bugs.debian.org
Bug#595265: linux-image-2.6.32-5-686: Nerwork card fails to come up again after suspend
On Thu, 2010-09-02 at 11:43 -0400, Arnout Boelens wrote: Package: linux-2.6 Version: 2.6.32-21 Severity: normal After suspending my laptop my network card fails to come back up again. As workaround I unload the kernel module for my card (r8169) and reload it again. Can you send a kernel log covering the time when you suspend and resume? The log section included in your original report is full of firewall warnings. 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#595223: linux-image-2.6-xen-amd64: channel scanning with b2c2-flexcop-pci
On Thu, 2010-09-02 at 07:36 +, Kloana wrote: Package: linux-image-2.6-xen-amd64 Version: 2.6.32+28 Severity: normal Hi, with debian squeeze kernel my Sky2PC/SkyStar 2 DVB-S rev 2.6 is not able to scan for channels. It's the same in arch i386 and amd64. When i use the stable Lenny kernel everything is ok. The modules are loaded sucessfully, but i'm not able to scan for channels. Attached you can find the output of dmesg, lspci-vv and scan. Can you test whether this works when using the ordinary kernel (linux-image-2.6.32-5-amd64) rather than under Xen? 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#592750: lm-sensors: fan not active after sleep/hibernate
On Fri, 2010-08-20 at 11:19 +0100, Philip Ashmore wrote: I should explain that I uninstalled the package and tried the version from Squeeze - same problem. I then uninstalled the package - same problem. Perhaps this should be re-assigned to linux-image-2.6.32-trunk-amd64. Perhaps you should test linux-image-2.6.32-5-amd64 rather than running that old kernel version. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Processed: tagging 592750
Processing commands for cont...@bugs.debian.org: tags 592750 + moreinfo Bug #592750 [linux-2.6] linux-2.6: fan not active after sleep/hibernate Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 592750: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=592750 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.128355579432492.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-08-30 at 14:48 +0100, Ben Hutchings wrote: On Mon, 2010-08-30 at 17:34 +1000, Russell Stuart wrote: The problem disappears in linux-image-2.6.35-trunk-amd64_2.6.35-1~experimental.2. Yes, as I expected. Can you please test the attached patch against the version in unstable? Directions for rebuilding an official kernel package are at http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official. Applied that. It changed the problem. Before I got a nice repeatable BUG. Now the openvpn instance unconditionally segfaults and normally nothing appears on the console or in kern.log. Once I got lucky and this appeared on the console: Message from sysl...@toby at Sep 4 09:11:57 ... kernel:[52062.327222] [ cut here ] Message from sysl...@toby at Sep 4 09:11:57 ... kernel:[52062.329577] invalid opcode: [#1] SMP Message from sysl...@toby at Sep 4 09:11:57 ... kernel:[52062.330671] last sysfs file: /sys/devices/virtual/misc/tun/uevent Message from sysl...@toby at Sep 4 09:11:57 ... kernel:[52062.330671] Stack: Message from sysl...@toby at Sep 4 09:11:57 ... kernel:[52062.330671] Call Trace: Message from sysl...@toby at Sep 4 09:11:57 ... kernel:[52062.330671] Code: 74 0f 48 89 ef e8 24 07 00 00 eb 05 bb fe ff ff ff 89 d8 5b 5d 41 5c c3 48 85 ff 74 0e 48 8b 7f 30 48 85 ff 74 05 48 85 f6 75 04 0f 0b eb fe ba 02 00 00 00 e9 5d ff ff ff 55 53 48 89 fb 48 c7 The machine appears to freeze in various ways - eg you can't get a login prompt to have a sniff around and the first command you type at an existing shell prompt that requires disk IO freezes, and a sleep 300; sudo reboot -f doesn't do anything. On the other hand a for f in $(seq 1000); do echo $f; sleep 1; done continues on as though nothing has happened. Disk IO is probably borked. -- 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/1283556425.23992.14.ca...@russell-laptop
Re: Bug#586967: (no subject)
On Tue, 2010-08-31 at 04:12 +0200, Jens Schüßler wrote: Hi Bob, What is the exact model you have (use lspci -nn -d 10b7:)? 00:0b.0 Ethernet controller [0200]: 3Com Corporation 3c595 100BaseTX [Vortex] [10b7:5950] Also can you try enabling some debug logging: rmmod 3c59x modprobe 3c59x debug=3 Then run dmesg to get the logged messages, and send them back. There are not much, even if I set debug=7 , | [ 72.752091] See Documentation/networking/vortex.txt | [ 72.752098] :00:0b.0: 3Com PCI 3c595 Vortex 100baseTx at 00018800. | [ 72.772890] 00:a0:24:43:dd:fd, IRQ 11 | [ 72.780517] product code 4255 rev 00.0 date 12-02-95 | [ 72.780527] 64K word-wide RAM 1:1 Rx:Tx split, autoselect/10baseT interface. | [ 72.780533] :00:0b.0: scatter/gather disabled. h/w checksums disabledo | ` and thats all. That at least lets me see how it's different from the card I have here. Dialin to a my ISP works (card is connected to a DSL-Modem), but if there are comes traffic I just done a 'links www.google.de' and everything freezes totally, but I saw , | Refresh [ 76.79933] eth0 vortex_error(), status=0xe091 ` on the terminal at this moment. That message is *precisely* what I needed to find the bug, thanks. Booting to my parallel installed Ubuntu, also with kernel 2.6.32, everything is alright. Could I be the only one with this problem, and should I better file a new bug? This is a new bug, introduced by my fix for the previous bug. However, this driver supports a wide range of cards and this new bug only affects some of them. Please do make a new bug report. 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#594089: keyboard-configuration: caps lock keycode problem
Tom Vier, le Fri 03 Sep 2010 16:35:47 -0400, a écrit : On 09/02/2010 03:46 PM, Samuel Thibault wrote: Hello, Tom Vier, le Thu 02 Sep 2010 15:11:49 -0400, a écrit : It says UNICODE mode and the codes for caps lock are: press: 0x3a 0xe0 0x66 repeat: 0x3a release: 0xba 0xe0 0x 0xe6 I guess? Yes. I also just discovered the right shift key goes back a page in iceweasel. Here are the right-shift codes: showkey -s: press: 0x36 0xe0 0x6a repeat: 0x36 release: 0xb6 0xe0 0xea All this looks like one of the few keyboard glitches that linux-2.6 fixes for some keyboards known to be bogus, while other keyboards do use these scancodes to report e.g. multimedia keys. Could you try showkey -s with the older, working kernel? Stable (2.6.26) which worked fine gives the same as Testing (2.6.32): When you say Stable, you mean both kernel and Xorg? Could you also run xev on your stable box? press: 0x3a 0xe0 0x66 repeat: 0x3a release: 0xba 0xe0 0xe6 ...which makes me think it's an xorg problem, but I'm not familiar with how the whole keyboard stack works. It's a big mess :) I wonder why the logitech generates so many codes. It looks to me like a keyboard bug. Do you see any pattern, e.g. does the left shift key produce one too? Do the keys which do produce extra scancodes form any particular shape on the keyboard? Such bug should probably be fixed in the kernel, just like it is already in atkbd.c for some keyboards. Samuel -- 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/20100903234552.gk5...@const
Bug#594089: keyboard-configuration: caps lock keycode problem
Tom, le Mon 23 Aug 2010 11:43:53 -0400, a écrit : The model name is logimel, which is set in both /etc/default/keyboard and /etc/X11/xorg.conf. Which explains why Xorg has the behavior you describe: the logimel model includes the logitech base, which includes the common navigation keys, which makes XF86Back from 0xe0 0x6a, and XF86Favorites from 0xe0 0x66. Do you actually have navigation keys on your keyboard? I'm afraid we'll just have to blacklist it in the usb driver according to the usb ID. Samuel -- 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/20100903235540.ga9...@const
