Bug#586491: marked as done (Broken symlinks created for package if /usr/src is a symlink)
Your message dated Sun, 20 Jun 2010 11:47:01 +0200 with message-id 20100620094701.ga15...@wavehammer.waldi.eu.org and subject line Re: Bug#586491: Broken symlinks created for package if /usr/src is a symlink has caused the Debian Bug report #586491, regarding Broken symlinks created for package if /usr/src is a symlink 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.) -- 586491: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586491 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-headers-2.6.32-5-common Version: 2.6.32-15 If /usr/src is symlinked to a different location, the symlinks within the package for 'Kbuild' and 'scripts' end up being broken since ../.. traverses from the actual location. This is likely a problem for all the versions of this package, as well as other versions of the kernel. Evan ---End Message--- ---BeginMessage--- On Sat, Jun 19, 2010 at 10:16:40PM -0500, Evan Harris wrote: If /usr/src is symlinked to a different location, the symlinks within the package for 'Kbuild' and 'scripts' end up being broken since ../.. traverses from the actual location. This behaviour is mandated by the policy, §10.5. Bastian -- Sometimes a man will tell his bartender things he'll never tell his doctor. -- Dr. Phillip Boyce, The Menagerie (The Cage), stardate unknown. ---End Message---
Bug#586536: linux-headers-2.6.26-2-486: Header-errors while compiling a kernel-module
Package: linux-headers-2.6.26-2-486 Version: 2.6.26-22lenny1 Severity: normal -- System Information: Debian Release: 5.0.4 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i586) Kernel: Linux 2.6.26-2-486 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 linux-headers-2.6.26-2-486 depends on: ii gcc-4.1 4.1.2-25The GNU C compiler ii linux-headers-2.6.26-2-c 2.6.26-22lenny1 Common header files for Linux 2.6. ii linux-kbuild-2.6.26 2.6.26-3Kbuild infrastructure for Linux 2. linux-headers-2.6.26-2-486 recommends no packages. linux-headers-2.6.26-2-486 suggests no packages. -- debconf-show failed Hello, i by a network card (ZX346q from Znyx http://www.znyx.com) and installed in my computer. I donwloaded the driver fom http://www.znyx.com/support/drivers/drivers/linux/x86/v2_2_23gcc3/ZNYXnb.linux.tgz I install the linux-header with srv:/usr/src# apt-get install linux-header-2.6.26-2-486 srv:/usr/src# ln -s linux-header-2.6.26-2-486 linux I change to the driver dirctory and start the compiling with srv:/usr/src/znyx346q/ZNYXnb# make module Then i see errors in header files. Wath is wrong here ? In file included from /usr/src/linux/include/linux/skbuff.h:17, from ./include/pdk_buf.h:38, from hal.c:58: /usr/src/linux/include/linux/kernel.h: In function ‘printk_needs_cpu’: /usr/src/linux/include/linux/kernel.h:220: error: parameter name omitted In file included from /usr/src/linux/include/asm/thread_info_64.h:24, from /usr/src/linux/include/asm/thread_info.h:5, from /usr/src/linux/include/linux/thread_info.h:47, from /usr/src/linux/include/linux/preempt.h:9, from /usr/src/linux/include/linux/spinlock.h:49, from /usr/src/linux/include/linux/seqlock.h:29, from /usr/src/linux/include/linux/time.h:8, from /usr/src/linux/include/linux/skbuff.h:19, from ./include/pdk_buf.h:38, from hal.c:58: /usr/src/linux/include/asm/processor.h: At top level: /usr/src/linux/include/asm/processor.h:112: error: ‘CONFIG_X86_L1_CACHE_SHIFT’ undeclared here (not in a function) /usr/src/linux/include/asm/processor.h:112: error: requested alignment is not a constant In file included from /usr/src/linux/include/asm/thread_info_64.h:24, from /usr/src/linux/include/asm/thread_info.h:5, from /usr/src/linux/include/linux/thread_info.h:47, from /usr/src/linux/include/linux/preempt.h:9, from /usr/src/linux/include/linux/spinlock.h:49, from /usr/src/linux/include/linux/seqlock.h:29, from /usr/src/linux/include/linux/time.h:8, from /usr/src/linux/include/linux/skbuff.h:19, from ./include/pdk_buf.h:38, from hal.c:58: /usr/src/linux/include/asm/processor.h:155:1: warning: cache_line_size redefined In file included from /usr/src/linux/include/linux/time.h:7, from /usr/src/linux/include/linux/skbuff.h:19, from ./include/pdk_buf.h:38, from hal.c:58: /usr/src/linux/include/linux/cache.h:64:1: warning: this is the location of the previous definition /usr/src/linux/include/asm/processor.h: In function ‘load_cr3’: /usr/src/linux/include/asm/processor.h:187: error: ‘CONFIG_PAGE_OFFSETUL’ undeclared (first use in this function) /usr/src/linux/include/asm/processor.h:187: error: (Each undeclared identifier is reported only once /usr/src/linux/include/asm/processor.h:187: error: for each function it appears in.) /usr/src/linux/include/asm/processor.h: At top level: /usr/src/linux/include/asm/processor.h:236: error: requested alignment is not a constant In file included from /usr/src/linux/include/asm/thread_info.h:5, from /usr/src/linux/include/linux/thread_info.h:47, from /usr/src/linux/include/linux/preempt.h:9, from /usr/src/linux/include/linux/spinlock.h:49, from /usr/src/linux/include/linux/seqlock.h:29, from /usr/src/linux/include/linux/time.h:8, from /usr/src/linux/include/linux/skbuff.h:19, from ./include/pdk_buf.h:38, from hal.c:58: /usr/src/linux/include/asm/thread_info_64.h: In function ‘current_thread_info’: /usr/src/linux/include/asm/thread_info_64.h:66: error: ‘THREAD_SIZE’ undeclared (first use in this function) /usr/src/linux/include/asm/thread_info_64.h: In function ‘stack_thread_info’: /usr/src/linux/include/asm/thread_info_64.h:74: error: ‘THREAD_SIZE’ undeclared (first use in this function) In file included from /usr/src/linux/include/linux/elf.h:7, from /usr/src/linux/include/linux/module.h:14, from
Processed: tagging 585790
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 585790 + pending Bug #585790 [linux-image-2.6.32-5-kirkwood] linux-image-2.6.32-5-kirkwood: Oops in mv_cesa Added tag(s) pending. End of message, stopping processing here. Please contact me if you need assistance. -- 585790: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=585790 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.12770406909273.transcr...@bugs.debian.org
Bug#585790: linux-image-2.6.32-5-kirkwood: Oops in mv_cesa
* Sebastian Andrzej Siewior sebast...@breakpoint.cc [2010-06-16 12:19]: I had the following patches on top: 750052dd2400cd09e0864d75b63c2c0bf605056f crypto: mv_cesa - Add sha1 and hmac(sha1) async hash drivers 0c5c6c4bae8fe9ae3d86b44c332eb1267df1ec99 crypto: mv_cesa - Support processing of data from previous requests f0d03deaad05d9cc99cd2ee0475c9ecd726c19ae crypto: mv_cesa - Make the copy-back of data optional a58094ac5f95d6969e5c52ff096d2fd2864542af crypto: mv_cesa - Execute some code via function pointers rathr than direct calls 7a5f691ef03f4c01d2703b5ec4ddd4c17e645dec crypto: mv_cesa - Rename a variable to a more suitable name 3b61a90502481045f56c1c41a2af35ee48ca8b80 crypto: mv_cesa - Enqueue generic async requests 15d4dd3594221f11a7730fcf2d5f9942b96cdd7e crypto: mv_cesa - Fix situations where the src sglist spans more data than the request asks for f565e67ec1b8f4a95d21550f9b879fe86b4132e0 crypto: mv_cesa - Fix situation where the dest sglist is organized differently than the source sglist 6bc6fcd609080461682c5cc0a1e3bf4345d6419d crypto: mv_cesa - Remove compiler warning in mv_cesa driver 0328ac267564089d9cedfb568f936d30a6debd21 crypto: mv_cesa - Invoke the user callback from a softirq context The patches until 0328ac267 to 15d4dd3 are probably required. All of these changes seem pretty self-contained, so I'd like to go ahead and apply all of them to Debian's 2.6.32 package. Do you see any problems with this? -- Martin Michlmayr http://www.cyrius.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/20100620132622.ge4...@jirafa.cyrius.com
Bug#586554: initramfs-tools fails to upgrade from 0.96.1 to 0.97
Package: initramfs-tools Version: 0.94.4 Severity: important Unpacking replacement initramfs-tools ... Processing triggers for man-db ... Setting up initramfs-tools (0.97) ... Installing new version of config file /etc/initramfs-tools/update- initramfs.conf ... Installing new version of config file /etc/initramfs-tools/initramfs.conf ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.34-0.slh.9-sidux-amd64 update-initramfs: failed for /boot/initrd.img-2.6.34-0.slh.9-sidux-amd64 dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: initramfs-tools E: Sub-process /usr/bin/dpkg returned an error code (1) This problem has been noteed with at least two other people using my (sidux) distro -- Package-specific info: -- /proc/cmdline root=UUID=91ed1f3b-835d-49ff-a27f-43d315cc9da3 ro quiet vga=791 -- /proc/filesystems cramfs ext3 vfat fuseblk -- lsmod Module Size Used by vboxnetadp 4593 0 vboxnetflt 13810 0 vboxdrv 1741768 2 vboxnetadp,vboxnetflt powernow_k811764 1 cpufreq_ondemand7981 1 cpufreq_stats 2968 0 freq_table 2355 3 powernow_k8,cpufreq_ondemand,cpufreq_stats cpufreq_conservative 9092 0 cpufreq_powersave926 0 cpufreq_performance 930 0 ppdev 5934 0 lp 9761 0 kvm_amd34542 0 kvm 183428 1 kvm_amd af_packet 19162 2 fuse 58584 1 nls_utf81224 3 nls_cp437 5825 3 vfat9852 3 fat48438 1 vfat snd_hda_codec_realtek 266078 1 snd_hda_intel 21330 2 snd_hda_codec 73946 2 snd_hda_codec_realtek,snd_hda_intel snd_hwdep 5852 1 snd_hda_codec snd_pcm_oss37251 0 snd_mixer_oss 14443 1 snd_pcm_oss snd_pcm68835 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss snd_seq_dummy 1335 0 snd_seq_oss26808 0 snd_seq_midi4656 0 snd_rawmidi17748 1 snd_seq_midi snd_seq_midi_event 5212 2 snd_seq_oss,snd_seq_midi snd_seq47805 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event snd_timer 18149 2 snd_pcm,snd_seq snd_seq_device 5013 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq snd52547 16 snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device usblp 10539 0 soundcore 5583 1 snd nvidia 10916536 38 snd_page_alloc 6833 2 snd_hda_intel,snd_pcm i2c_nforce2 5416 0 pcspkr 1755 0 k8temp 3243 0 psmouse52374 0 edac_core 33536 0 rtc_cmos8926 0 edac_mce_amd7057 0 evdev 8468 6 rtc_core 13125 1 rtc_cmos i2c_core 17614 2 nvidia,i2c_nforce2 serio_raw 4016 0 parport_pc 30844 1 rtc_lib 1841 1 rtc_core parport27939 3 ppdev,lp,parport_pc button 4610 0 processor 23822 1 powernow_k8 ext3 124342 22 jbd46903 1 ext3 mbcache 5586 1 ext3 sg 21016 0 sr_mod 13891 0 cdrom 34068 1 sr_mod sd_mod 29512 30 ohci_hcd 23081 0 ata_generic 2975 0 pata_acpi 3248 0 firewire_ohci 22678 0 ehci_hcd 36834 0 ssb45807 1 ohci_hcd pata_amd 10876 0 firewire_core 43855 1 firewire_ohci crc_itu_t 1299 1 firewire_core floppy 56506 0 usbcore 144245 4 usblp,ohci_hcd,ehci_hcd nls_base6641 5 nls_utf8,nls_cp437,vfat,fat,usbcore thermal11783 0 sata_nv21663 26 mmc_core 53435 1 ssb pcmcia 35362 1 ssb pcmcia_core12964 1 pcmcia forcedeth 52579 0 libata155315 4 ata_generic,pata_acpi,pata_amd,sata_nv scsi_mod 137899 4 sg,sr_mod,sd_mod,libata -- /etc/kernel-img.conf # Kernel Image management overrides # See kernel-img.conf(5) for details do_symlinks = Yes postinst_hook = /usr/sbin/update-grub postrm_hook = /usr/sbin/update-grub do_bootloader = no do_initrd = Yes relative_links = Yes -- /etc/initramfs-tools/initramfs.conf MODULES=most BUSYBOX=y KEYMAP=n COMPRESS=gzip
Bug#586536: marked as done (linux-headers-2.6.26-2-486: Header-errors while compiling a kernel-module)
Your message dated Sun, 20 Jun 2010 14:41:39 +0100 with message-id 1277041299.14011.874.ca...@localhost and subject line Re: Bug#586536: linux-headers-2.6.26-2-486: Header-errors while compiling a kernel-module has caused the Debian Bug report #586536, regarding linux-headers-2.6.26-2-486: Header-errors while compiling a kernel-module 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.) -- 586536: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586536 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-headers-2.6.26-2-486 Version: 2.6.26-22lenny1 Severity: normal -- System Information: Debian Release: 5.0.4 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i586) Kernel: Linux 2.6.26-2-486 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 linux-headers-2.6.26-2-486 depends on: ii gcc-4.1 4.1.2-25The GNU C compiler ii linux-headers-2.6.26-2-c 2.6.26-22lenny1 Common header files for Linux 2.6. ii linux-kbuild-2.6.26 2.6.26-3Kbuild infrastructure for Linux 2. linux-headers-2.6.26-2-486 recommends no packages. linux-headers-2.6.26-2-486 suggests no packages. -- debconf-show failed Hello, i by a network card (ZX346q from Znyx http://www.znyx.com) and installed in my computer. I donwloaded the driver fom http://www.znyx.com/support/drivers/drivers/linux/x86/v2_2_23gcc3/ZNYXnb.linux.tgz I install the linux-header with srv:/usr/src# apt-get install linux-header-2.6.26-2-486 srv:/usr/src# ln -s linux-header-2.6.26-2-486 linux I change to the driver dirctory and start the compiling with srv:/usr/src/znyx346q/ZNYXnb# make module Then i see errors in header files. Wath is wrong here ? In file included from /usr/src/linux/include/linux/skbuff.h:17, from ./include/pdk_buf.h:38, from hal.c:58: /usr/src/linux/include/linux/kernel.h: In function ‘printk_needs_cpu’: /usr/src/linux/include/linux/kernel.h:220: error: parameter name omitted In file included from /usr/src/linux/include/asm/thread_info_64.h:24, from /usr/src/linux/include/asm/thread_info.h:5, from /usr/src/linux/include/linux/thread_info.h:47, from /usr/src/linux/include/linux/preempt.h:9, from /usr/src/linux/include/linux/spinlock.h:49, from /usr/src/linux/include/linux/seqlock.h:29, from /usr/src/linux/include/linux/time.h:8, from /usr/src/linux/include/linux/skbuff.h:19, from ./include/pdk_buf.h:38, from hal.c:58: /usr/src/linux/include/asm/processor.h: At top level: /usr/src/linux/include/asm/processor.h:112: error: ‘CONFIG_X86_L1_CACHE_SHIFT’ undeclared here (not in a function) /usr/src/linux/include/asm/processor.h:112: error: requested alignment is not a constant In file included from /usr/src/linux/include/asm/thread_info_64.h:24, from /usr/src/linux/include/asm/thread_info.h:5, from /usr/src/linux/include/linux/thread_info.h:47, from /usr/src/linux/include/linux/preempt.h:9, from /usr/src/linux/include/linux/spinlock.h:49, from /usr/src/linux/include/linux/seqlock.h:29, from /usr/src/linux/include/linux/time.h:8, from /usr/src/linux/include/linux/skbuff.h:19, from ./include/pdk_buf.h:38, from hal.c:58: /usr/src/linux/include/asm/processor.h:155:1: warning: cache_line_size redefined In file included from /usr/src/linux/include/linux/time.h:7, from /usr/src/linux/include/linux/skbuff.h:19, from ./include/pdk_buf.h:38, from hal.c:58: /usr/src/linux/include/linux/cache.h:64:1: warning: this is the location of the previous definition /usr/src/linux/include/asm/processor.h: In function ‘load_cr3’: /usr/src/linux/include/asm/processor.h:187: error: ‘CONFIG_PAGE_OFFSETUL’ undeclared (first use in this function) /usr/src/linux/include/asm/processor.h:187: error: (Each undeclared identifier is reported only once /usr/src/linux/include/asm/processor.h:187: error: for each function it appears in.) /usr/src/linux/include/asm/processor.h: At top level: /usr/src/linux/include/asm/processor.h:236: error: requested alignment is not a constant In file included from /usr/src/linux/include/asm/thread_info.h:5, from /usr/src/linux/include/linux/thread_info.h:47, from
Bug#586557: linux-2.6 - btrfs module consideres device names stable
Source: linux-2.6 Version: 2.6.32-1 Severity: important Forwarded: https://bugzilla.kernel.org/show_bug.cgi?id=16259 btrfs uses a in-kernel uuid to device translation. This leads to a DoS in case of changed device names, which can happen all the time. | device fsid 6746742515f05f59-7702ee31ff5c53ac devid 1 transid 130 /dev/sde | open /dev/sdd failed | # file -s /dev/sde | /dev/sde: BTRFS Filesystem sectorsize 4096, nodesize 4096, leafsize 4096) | # file -s /dev/sdd | /dev/sdd: x86 boot sector; partition 1: ID=0x83, starthead 1, startsector 63, 625137282 sectors, extended partition table (last)\011, code offset 0x0 Bastian -- War is never imperative. -- McCoy, Balance of Terror, stardate 1709.2 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100620152227.ga20...@wavehammer.waldi.eu.org
Bug#586558: linux-2.6 - btrfs misses checks in acl set code
Source: linux-2.6 Version: 2.6.32-15 Severity: serious Tags: security The current btrfs code does not check if the user is allowed to change ACLs. This was fixed in mainline with 2f26afba46f0ebf155cf9be746496a0304a5b7cf. Bastian -- Too much of anything, even love, isn't necessarily a good thing. -- Kirk, The Trouble with Tribbles, stardate 4525.6 -- 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/20100620153310.ga20...@wavehammer.waldi.eu.org
Processed: tagging 586494
Processing commands for cont...@bugs.debian.org: tags 586494 moreinfo Bug #586494 [linux-2.6] linux-image-2.6.26-2-686: Dell PowerEdge 4200's don't work with 2.6.26 Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 586494: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586494 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.127704998524302.transcr...@bugs.debian.org
Bug#584259: initramfs-tools: breaks software suspend (hibernation)
On Sat, 2010-06-19 at 19:06 +0200, Willi Mann wrote: Hi! The problem can be traced to module hid_cherry. If it exists in the initrd, the resume works, otherwise it doesn't. This seems to indicate that hid_cherry doesn't fully reinitialise the device on resume. This would be a kernel bug, so I'm reassigning it. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#586558: [PATCH] Btrfs: should add a permission check for setfacl
This was commit 2f26afba46f0ebf155cf9be746496a0304a5b7cf.
From 2f26afba46f0ebf155cf9be746496a0304a5b7cf Mon Sep 17 00:00:00 2001
From: Shi Weihua sh...@cn.fujitsu.com
Date: Tue, 18 May 2010 00:50:32 +
Subject: [PATCH] Btrfs: should add a permission check for setfacl
On btrfs, do the following
--
# su user1
# cd btrfs-part/
# touch aaa
# getfacl aaa
# file: aaa
# owner: user1
# group: user1
user::rw-
group::rw-
other::r--
# su user2
# cd btrfs-part/
# setfacl -m u::rwx aaa
# getfacl aaa
# file: aaa
# owner: user1
# group: user1
user::rwx - successed to setfacl
group::rw-
other::r--
--
but we should prohibit it that user2 changing user1's acl.
In fact, on ext3 and other fs, a message occurs:
setfacl: aaa: Operation not permitted
This patch fixed it.
Signed-off-by: Shi Weihua sh...@cn.fujitsu.com
Signed-off-by: Chris Mason chris.ma...@oracle.com
---
fs/btrfs/acl.c |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/fs/btrfs/acl.c b/fs/btrfs/acl.c
index 6ef7b26..6b4d0cc 100644
--- a/fs/btrfs/acl.c
+++ b/fs/btrfs/acl.c
@@ -160,6 +160,9 @@ static int btrfs_xattr_acl_set(struct dentry *dentry, const
char *name,
int ret;
struct posix_acl *acl = NULL;
+ if (!is_owner_or_cap(dentry-d_inode))
+ return -EPERM;
+
if (value) {
acl = posix_acl_from_xattr(value, size);
if (acl == NULL) {
--
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/20100620163021.ga21...@wavehammer.waldi.eu.org
Processed: tagging 585677
Processing commands for cont...@bugs.debian.org: tags 585677 moreinfo Bug #585677 [linux-2.6] linux-image-2.6.32-5-486: impossible to mount partitions (except /) Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 585677: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=585677 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.12770519036494.transcr...@bugs.debian.org
Bug#586568: dosfslabel failed: 256 at /var/lib/dpkg/info/linux-base.postinst line 1059, STDIN line 10. Logical sector size is zero.
Package: linux-base Version: 2.6.32-15 Severity: normal -- System Information: Debian Release: 5.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.31-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages 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 147-4 /dev/ and hotplug management daemo ii util-linux2.16.1-4 Miscellaneous system utilities linux-base recommends no packages. linux-base suggests no packages. -- debconf information: linux-base/disk-id-manual-boot-loader: linux-base/disk-id-manual: linux-base/disk-id-convert-plan-no-relabel: true * linux-base/disk-id-convert-plan: true * linux-base/disk-id-convert-auto: true here is my partition table as shown by parted. Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End SizeType File system Flags 1 32.3kB 200GB 200GB primary ntfsboot 2 200GB 240GB 40.0GB primary ext3 3 240GB 1000GB 760GB extended lba 5 240GB 248GB 8000MB logical linux-swap(v1) 6 248GB 446GB 198GB logical ext3 I don't understand the Logical sector size is zero. message before dosfslabel failed: 256 at /var/lib/dpkg/info/linux-base.postinst line 1059, STDIN line 10. Any advise using dosfslabel on my system to diagnose more precisely the problem is welcome. I hope it's not because of any missusing of partition. -- 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/20100620163112.6605.11718.report...@ketch
Processed: tagging 586401
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 586401 + pending Bug #586401 [linux-libc-dev] linux-libc-dev: Please remove NEWS.Debian.gz Ignoring request to alter tags of bug #586401 to the same tags previously set End of message, stopping processing here. Please contact me if you need assistance. -- 586401: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586401 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.127705363620448.transcr...@bugs.debian.org
Processed: tagging 586401
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 586401 + pending Bug #586401 [linux-libc-dev] linux-libc-dev: Please remove NEWS.Debian.gz Added tag(s) pending. End of message, stopping processing here. Please contact me if you need assistance. -- 586401: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586401 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.127705363420425.transcr...@bugs.debian.org
Bug#509077: initramfs-tools: support alternate DHCP port and DHCP vendor-class-identifier
On Tue, 08 Jun 2010, Michael Prokop wrote: * Vagrant Cascadian vagrant+debianb...@freegeek.org [Mit Dez 17, 2008 at 07:01:51 -0800]: please consider the attached patch, which adds boot prompt parameters for two of ipconfig's commandline options in the configure_networking function: - using an alternate DHCP port (dhcpport=NNN, ipconfig -p NNN) - specifying the vendor-class-identifier (dhcpvci=XXX, ipconfig -i XXX) supporting these options gives additional flexibility in distinguishing thin clients from conventional workstations in a mixed network. Sorry that no one took care of your bugreport for so long, Vagrant. Patch looks fine to me. maks, any objections against inclusion of the patches? I had been dragging that patch as I do not like to add to many bootparams that are outside of documented upstream linux-2.6 handling and thus initramfs-tools specific. waited to see if a second voice would raise.. I do not see so much the point of setting ipconfig vendor class id. why would that be needed for booting? the alternate DHCP port looks indeed more interesting, but no idea how common that is in the wild? and if there is not a place in the ip= monster bootparam? thanks -- maks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100619164316.gc24...@stro.at
Bug#582776: initramfs-tools: pointless generation of an initrd for initrd-free custom kernels
On Wed, 09 Jun 2010, Michael Prokop wrote: How about giving people the chance to disable generation of initrds through e.g. /etc/default/initramfs-tools? well that would assume that you want *none* anywhere, which is often not the case as you may very well have a mixed setup. -- 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/20100619150627.gb24...@stro.at
Bug#586576: linux-image-2.6.32-5-686: apt-get/dpkg postinst update-initramfs fails for 2.6.32-5-686 but works on cmdline
Package: linux-2.6 Version: 2.6.32-15 Severity: normal update-initramfs fails for the dpkg task, but works from command line: maggie:~# apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 2 not fully installed or removed. After this operation, 0B of additional disk space will be used. Do you want to continue [Y/n]? y Setting up linux-image-2.6.32-5-686 (2.6.32-15) ... Running depmod. Running update-initramfs. update-initramfs: Generating /boot/initrd.img-2.6.32-5-686 initrd.img(/boot/initrd.img-2.6.32-5-686 ) points to /boot/initrd.img-2.6.32-5-686 (/boot/initrd.img-2.6.32-5-686) -- doing nothing at /var/lib/dpkg/info/linux-image-2.6.32-5-686.postinst line 400. vmlinuz(/boot/vmlinuz-2.6.32-5-686 ) points to /boot/vmlinuz-2.6.32-5-686 (/boot/vmlinuz-2.6.32-5-686) -- doing nothing at /var/lib/dpkg/info/linux-image-2.6.32-5-686.postinst line 400. Running update-grub. /usr/sbin/grub-probe: error: cannot find a device for / (is /dev mounted?). User postinst hook script [update-grub] exited with value 1 dpkg: error processing linux-image-2.6.32-5-686 (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of linux-image-2.6-686: linux-image-2.6-686 depends on linux-image-2.6.32-5-686; however: Package linux-image-2.6.32-5-686 is not configured yet. dpkg: error processing linux-image-2.6-686 (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: linux-image-2.6.32-5-686 linux-image-2.6-686 E: Sub-process /usr/bin/dpkg returned an error code (1) maggie:~# update-initramfs -k 2.6.32-5-686 -u update-initramfs: Generating /boot/initrd.img-2.6.32-5-686 maggie:~# Thanks. --mark-- -- Package-specific info: ** Version: Linux version 2.6.32-5-686 (Debian 2.6.32-15) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-1) ) #1 SMP Tue Jun 1 04:59:47 UTC 2010 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.32-5-686 root=/dev/mapper/sda7_crypt ro root=/dev/mapper/sda7_crypt ro heartbeat=300 rootdelay=4 quiet ** Not tainted ** Kernel log: [ 3476.620206] ehci_hcd :00:1d.7: restoring config space at offset 0x1 (was 0x2900106, writing 0x2900102) [ 3476.628066] ehci_hcd :00:1d.7: power state changed by ACPI to D0 [ 3476.636067] ehci_hcd :00:1d.7: power state changed by ACPI to D0 [ 3476.636130] pci :00:1e.0: restoring config space at offset 0x1 (was 0x15, writing 0x17) [ 3476.636352] ahci :00:1f.2: restoring config space at offset 0x1 (was 0x2b7, writing 0x2b00407) [ 3476.636651] iwl3945 :03:00.0: restoring config space at offset 0x1 (was 0x100106, writing 0x100506) [ 3476.652092] firewire_ohci :05:00.1: restoring config space at offset 0x3 (was 0x80, writing 0x804000) [ 3476.652106] firewire_ohci :05:00.1: restoring config space at offset 0x1 (was 0x210, writing 0x216) [ 3476.668090] sdhci-pci :05:00.2: restoring config space at offset 0x3 (was 0x80, writing 0x804000) [ 3476.668102] sdhci-pci :05:00.2: restoring config space at offset 0x1 (was 0x210, writing 0x216) [ 3476.728268] i915 :00:02.0: power state changed by ACPI to D0 [ 3476.728307] i915 :00:02.0: power state changed by ACPI to D0 [ 3476.728312] i915 :00:02.0: setting latency timer to 64 [ 3476.872255] e1000e :00:19.0: PCI INT A - GSI 20 (level, low) - IRQ 20 [ 3476.872263] e1000e :00:19.0: setting latency timer to 64 [ 3476.872273] e1000e :00:19.0: wake-up capability disabled by ACPI [ 3476.872281] e1000e :00:19.0: PME# disabled [ 3476.872357] e1000e :00:19.0: irq 26 for MSI/MSI-X [ 3477.186129] uhci_hcd :00:1a.0: PCI INT A - GSI 20 (level, low) - IRQ 20 [ 3477.186142] uhci_hcd :00:1a.0: setting latency timer to 64 [ 3477.186176] usb usb3: root hub lost power or was reset [ 3477.186425] uhci_hcd :00:1a.1: power state changed by ACPI to D0 [ 3477.186648] uhci_hcd :00:1a.1: power state changed by ACPI to D0 [ 3477.186658] uhci_hcd :00:1a.1: PCI INT B - GSI 21 (level, low) - IRQ 21 [ 3477.186674] uhci_hcd :00:1a.1: setting latency timer to 64 [ 3477.186714] usb usb4: root hub lost power or was reset [ 3477.186915] ehci_hcd :00:1a.7: power state changed by ACPI to D0 [ 3477.187118] ehci_hcd :00:1a.7: power state changed by ACPI to D0 [ 3477.187133] ehci_hcd :00:1a.7: PCI INT C - GSI 22 (level, low) - IRQ 22 [ 3477.187148] ehci_hcd :00:1a.7: setting latency timer to 64 [ 3477.187167] HDA Intel :00:1b.0: PCI INT B - GSI 17 (level, low) - IRQ 17 [ 3477.187183] HDA Intel :00:1b.0: setting latency timer to 64 [ 3477.187462] uhci_hcd :00:1d.0: power state changed by ACPI to D0 [ 3477.187690] uhci_hcd :00:1d.0: power state changed by ACPI to D0 [ 3477.187700] uhci_hcd :00:1d.0: PCI INT A - GSI 16 (level,
Bug#584259: initramfs-tools: breaks software suspend (hibernation)
Am 2010-06-20 18:10, schrieb Ben Hutchings: On Sat, 2010-06-19 at 19:06 +0200, Willi Mann wrote: Hi! The problem can be traced to module hid_cherry. If it exists in the initrd, the resume works, otherwise it doesn't. This seems to indicate that hid_cherry doesn't fully reinitialise the device on resume. This would be a kernel bug, so I'm reassigning it. I've now tested 2.6.34 from experimental. It works without hid_cherry in the initrd. So the bug only applies to the testing/unstable kernel. WM -- 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/4c1e54c9.70...@wm1.at
Bug#586576: linux-image-2.6.32-5-686: apt-get/dpkg postinst update-initramfs fails for 2.6.32-5-686 but works on cmdline
On Sun, 2010-06-20 at 10:40 -0700, Mark Hedges wrote: Package: linux-2.6 Version: 2.6.32-15 Severity: normal update-initramfs fails for the dpkg task, but works from command line: Read more carefully. It's grub that failed. I'm reassigning this accordingly. 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: reassign 586576 to src:grub
Processing commands for cont...@bugs.debian.org: reassign 586576 src:grub Bug #586576 [linux-2.6] linux-image-2.6.32-5-686: apt-get/dpkg postinst update-initramfs fails for 2.6.32-5-686 but works on cmdline Bug reassigned from package 'linux-2.6' to 'src:grub'. Bug No longer marked as found in versions 2.6.32-15. thanks Stopping processing here. Please contact me if you need assistance. -- 586576: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586576 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.127705778325277.transcr...@bugs.debian.org
Bug#586491: closed by Bastian Blank wa...@debian.org (Re: Bug#586491: Broken symlinks created for package if /usr/src is a symlink)
The issue is not fixed by simply quoting policy and taking no action to correct the problem. 10.5 specifies that In general, symbolic links within a top-level directory should be relative. It should be fairly easy to make a symlink that does work on the target system if it takes into account the actual location of the dir/file. Granted, that will make the symlink have to be dynamically created at installation, but that will neither break policy nor create broken links. In addition, the in general and should both suggest that 10.5 is a general guideline, and does not preclude exceptions if the result would otherwise be a broken package installation, as it is in this case. Evan On Sun, 20 Jun 2010, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the linux-headers-2.6.32-5-common package: #586491: Broken symlinks created for package if /usr/src is a symlink It has been closed by Bastian Blank wa...@debian.org. Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Bastian Blank wa...@debian.org by replying to this email. -- 586491: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586491 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/pine.lnx.4.64.1006201307510.14...@kinison.puremagic.com
looking for gfs2/lenny users
The kernel in proposed-updates (2.6.26-23) includes a couple of security fixes for the gfs2 filesystem. I've performed some smoke testing in a VM, but I'm looking for users who might have actual (non-production) clusters to do some pre-release testing. -- dann frazier -- 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/20100620192335.gg32...@lackof.org
Processed: tagging 505609
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 505609 + pending Bug #505609 [linux-2.6] Unbootable after kernel upgrade: Lilo can't load kernel Bug #535331 [linux-2.6] lilo not run after install/upgrade Ignoring request to alter tags of bug #505609 to the same tags previously set Ignoring request to alter tags of bug #535331 to the same tags previously set End of message, stopping processing here. Please contact me if you need assistance. -- 505609: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=505609 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.12770636212271.transcr...@bugs.debian.org
Bug#509077: initramfs-tools: support alternate DHCP port and DHCP vendor-class-identifier
On Sat, 2010-06-19 at 18:43 +0200, maximilian attems wrote: On Tue, 08 Jun 2010, Michael Prokop wrote: * Vagrant Cascadian vagrant+debianb...@freegeek.org [Mit Dez 17, 2008 at 07:01:51 -0800]: please consider the attached patch, which adds boot prompt parameters for two of ipconfig's commandline options in the configure_networking function: - using an alternate DHCP port (dhcpport=NNN, ipconfig -p NNN) - specifying the vendor-class-identifier (dhcpvci=XXX, ipconfig -i XXX) supporting these options gives additional flexibility in distinguishing thin clients from conventional workstations in a mixed network. Sorry that no one took care of your bugreport for so long, Vagrant. Patch looks fine to me. maks, any objections against inclusion of the patches? I had been dragging that patch as I do not like to add to many bootparams that are outside of documented upstream linux-2.6 handling and thus initramfs-tools specific. waited to see if a second voice would raise.. I do not see so much the point of setting ipconfig vendor class id. why would that be needed for booting? It would be used for selecting the boot image. the alternate DHCP port looks indeed more interesting, but no idea how common that is in the wild? and if there is not a place in the ip= monster bootparam? Using an alternate DHCP port sounds pretty crazy. Another possibility is to configure the switch(es) to put the thin clients on a separate VLAN. But I suppose people also want to use cheap switches with no VLAN support. 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#585677: linux-image-2.6.32-5-486: impossible to mount partitions (except /)
On Fri, 2010-06-18 at 13:47 +0200, Stéphane Blondon wrote: 2010/6/14 Ben Hutchings b...@decadent.org.uk: We'll need to see a more complete kernel log. Either use netconsole to capture the output, or send a photograph of the screen. I have rebooted on the failed kernel, plug an USB key and copy the dmesg and kernel.log files. I hope it helps. Do you need other data? I will update the system to see if change happens. Please try booting with 'break=premount' added to the kernel parameters. When the boot process stops you should get an '(initramfs)' prompt. At the prompt, please run 'blkid' and send the output. Feel free to abbreviate the UUIDs if you copy the output by hand. 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#586494: linux-image-2.6.26-2-686: Dell PowerEdge 4200's don't work with 2.6.26
On Sat, 2010-06-19 at 23:39 -0400, trouble daemon wrote: Package: linux-2.6 Version: 2.6.26-22lenny1 Severity: important I am using a pair of Dell PowerEdg 4200's that have been working with debian since 2002 or so, 100% perfectly. However, since testing out Lenny with a 2.6.26 kernel, it seems that both systems panic in an unbootable fashion with 2.6.26. On one (this) machine, I even removed the megaraid card, with the same scsi related crashing/panic. Wow, that log shows some serious trouble. My guess is that something has gone wrong with interrupt routing. Can you try adding 'acpi=noirq' to the kernel parameters? I have tried a recompile of 2.6.26 with the old aic7xxx module instead of the new one, but it doesn't seem to make a differece. This following 2 dmesg dumps are from a serial console that I recorded earlier and put on pastebin (permanent paste): - 2.6.26 kernel that panics (latest unmodified debian kernel): http://pastebin.ca/1886636 - 2.6.18 kernel that works (latest unmodified debian kernel): http://pastebin.ca/1886641 [...] If my first suggestion doesn't work, can you also try a more recent kernel version such as 2.6.32 (currently in testing) and 2.6.34 (currently 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
Bug#574555: BUG: scheduling while atomic: irq/11-b43/2018/0x00000101
On Fri, 2010-06-18 at 16:40 +0200, Arne Nordmark wrote:
My problem seems related to those in Ubuntu report #55
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/55. If I
unload the 3c59x module, I can no longer reproduce this problem, and
wireless is stable. With the 3c59x module loaded, b43 wireless is
essentially unusable, since the machine will reliably lock up.
I've attached two patches which together may fix this problem, but they
involve quite major changes to the driver. I do not have any hardware
of this type which I could use to test them.
Please could you follow the instructions at
http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official
to build a package with these changes included, then test whether these
changes fix the problem for you and keep the wired network card working.
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
From 9d21ef35e8ad9b51362533134518932a3a7b5f0e Mon Sep 17 00:00:00 2001
From: Ben Hutchings b...@decadent.org.uk
Date: Sun, 20 Jun 2010 21:09:01 +0100
Subject: [PATCH 1/2] 3c59x: Specify window explicitly for access to windowed registers
Currently much of the code assumes that a specific window has been
selected, while a few functions save and restore the window. This
makes it impossible to introduce fine-grained locking.
Make those assumptions explicit by introducing wrapper functions
to set the window and read/write a register. Use these everywhere
except vortex_interrupt(), vortex_start_xmit() and vortex_rx().
These set the window just once, or not at all in the case of
vortex_rx() as it should always be called from vortex_interrupt().
Cache the current window in struct vortex_private to avoid
unnecessary hardware writes.
---
drivers/net/3c59x.c | 289 +--
1 files changed, 140 insertions(+), 149 deletions(-)
diff --git a/drivers/net/3c59x.c b/drivers/net/3c59x.c
index 975e25b..95f6919 100644
--- a/drivers/net/3c59x.c
+++ b/drivers/net/3c59x.c
@@ -435,7 +435,6 @@ MODULE_DEVICE_TABLE(pci, vortex_pci_tbl);
First the windows. There are eight register windows, with the command
and status registers available in each.
*/
-#define EL3WINDOW(win_num) iowrite16(SelectWindow + (win_num), ioaddr + EL3_CMD)
#define EL3_CMD 0x0e
#define EL3_STATUS 0x0e
@@ -647,8 +646,35 @@ struct vortex_private {
u16 io_size; /* Size of PCI region (for release_region) */
spinlock_t lock; /* Serialise access to device its vortex_private */
struct mii_if_info mii;/* MII lib hooks/info */
+ int window; /* Register window */
};
+static void window_set(struct vortex_private *vp, int window)
+{
+ if (window != vp-window) {
+ iowrite16(SelectWindow + window, vp-ioaddr + EL3_CMD);
+ vp-window = window;
+ }
+}
+
+#define DEFINE_WINDOW_IO(size) \
+static u ## size \
+window_read ## size(struct vortex_private *vp, int window, int addr) \
+{ \
+ window_set(vp, window); \
+ return ioread ## size(vp-ioaddr + addr); \
+} \
+static void\
+window_write ## size(struct vortex_private *vp, u ## size value, \
+ int window, int addr)\
+{ \
+ window_set(vp, window); \
+ iowrite ## size(value, vp-ioaddr + addr); \
+}
+DEFINE_WINDOW_IO(8)
+DEFINE_WINDOW_IO(16)
+DEFINE_WINDOW_IO(32)
+
#ifdef CONFIG_PCI
#define DEVICE_PCI(dev) (((dev)-bus == pci_bus_type) ? to_pci_dev((dev)) : NULL)
#else
@@ -711,7 +737,7 @@ static int vortex_probe1(struct device *gendev, void __iomem *ioaddr, int irq,
static int vortex_up(struct net_device *dev);
static void vortex_down(struct net_device *dev, int final);
static int vortex_open(struct net_device *dev);
-static void mdio_sync(void __iomem *ioaddr, int bits);
+static void mdio_sync(struct vortex_private *vp, int bits);
static int mdio_read(struct net_device *dev, int phy_id, int location);
static void mdio_write(struct net_device *vp, int phy_id, int location, int value);
static void vortex_timer(unsigned long arg);
@@ -1119,6 +1145,7 @@ static int __devinit vortex_probe1(struct device *gendev,
vp-has_nway = (vci-drv_flags HAS_NWAY) ? 1 : 0;
vp-io_size = vci-io_size;
vp-card_idx = card_idx;
+ vp-window = -1;
/* module list only for Compaq device */
if (gendev == NULL) {
@@ -1205,7 +1232,6 @@ static int __devinit vortex_probe1(struct device *gendev,
vp-mii.force_media = vp-full_duplex;
vp-options = option;
/* Read the station address from the EEPROM. */
- EL3WINDOW(0);
{
int base;
@@ -1218,14 +1244,15 @@ static int __devinit vortex_probe1(struct device *gendev,
for (i = 0; i 0x40; i++) {
int timer;
- iowrite16(base + i, ioaddr + Wn0EepromCmd);
+ window_write16(vp, base + i, 0, Wn0EepromCmd);
/* Pause for at least 162 us. for the read to take place. */
for (timer = 10; timer = 0; timer--) {
udelay(162);
-if ((ioread16(ioaddr + Wn0EepromCmd) 0x8000) == 0)
+if
Processed: reassign 584259 to linux-2.6
Processing commands for cont...@bugs.debian.org: reassign 584259 linux-2.6 2.6.33-1~experimental.5 Bug #584259 [initramfs-tools] initramfs-tools: breaks software suspend (hibernation) Bug reassigned from package 'initramfs-tools' to 'linux-2.6'. Bug No longer marked as found in versions initramfs-tools/0.95.1. Bug #584259 [linux-2.6] initramfs-tools: breaks software suspend (hibernation) There is no source info for the package 'linux-2.6' at version '2.6.33-1~experimental.5' with architecture '' Unable to make a source version for version '2.6.33-1~experimental.5' Bug Marked as found in versions 2.6.33-1~experimental.5. thanks Stopping processing here. Please contact me if you need assistance. -- 584259: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584259 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.1277070331708.transcr...@bugs.debian.org
Processed: tagging 574555
Processing commands for cont...@bugs.debian.org: tags 574555 patch moreinfo Bug #574555 [linux-2.6] linux-image-2.6.32-3-amd64: 2.6.32 kernel oops: Pid: 1700, comm: irq/21-b43 Not tainted 2.6.32-3-amd64 Added tag(s) moreinfo and patch. thanks Stopping processing here. Please contact me if you need assistance. -- 574555: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574555 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.1277070332778.transcr...@bugs.debian.org
Bug#586568: marked as done (dosfslabel failed: 256 at /var/lib/dpkg/info/linux-base.postinst line 1059, STDIN line 10. Logical sector size is zero.)
Your message dated Sun, 20 Jun 2010 18:11:05 +0100 with message-id 1277053865.14011.900.ca...@localhost and subject line Re: Bug#586568: dosfslabel failed: 256 at /var/lib/dpkg/info/linux-base.postinst line 1059, STDIN line 10. Logical sector size is zero. has caused the Debian Bug report #586568, regarding dosfslabel failed: 256 at /var/lib/dpkg/info/linux-base.postinst line 1059, STDIN line 10. Logical sector size is zero. 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.) -- 586568: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586568 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-base Version: 2.6.32-15 Severity: normal -- System Information: Debian Release: 5.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.31-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages 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 147-4 /dev/ and hotplug management daemo ii util-linux2.16.1-4 Miscellaneous system utilities linux-base recommends no packages. linux-base suggests no packages. -- debconf information: linux-base/disk-id-manual-boot-loader: linux-base/disk-id-manual: linux-base/disk-id-convert-plan-no-relabel: true * linux-base/disk-id-convert-plan: true * linux-base/disk-id-convert-auto: true here is my partition table as shown by parted. Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End SizeType File system Flags 1 32.3kB 200GB 200GB primary ntfsboot 2 200GB 240GB 40.0GB primary ext3 3 240GB 1000GB 760GB extended lba 5 240GB 248GB 8000MB logical linux-swap(v1) 6 248GB 446GB 198GB logical ext3 I don't understand the Logical sector size is zero. message before dosfslabel failed: 256 at /var/lib/dpkg/info/linux-base.postinst line 1059, STDIN line 10. Any advise using dosfslabel on my system to diagnose more precisely the problem is welcome. I hope it's not because of any missusing of partition. ---End Message--- ---BeginMessage--- On Sun, 2010-06-20 at 18:31 +0200, pitamila wrote: [...] here is my partition table as shown by parted. Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End SizeType File system Flags 1 32.3kB 200GB 200GB primary ntfsboot 2 200GB 240GB 40.0GB primary ext3 3 240GB 1000GB 760GB extended lba 5 240GB 248GB 8000MB logical linux-swap(v1) 6 248GB 446GB 198GB logical ext3 I don't understand the Logical sector size is zero. message before dosfslabel failed: 256 at /var/lib/dpkg/info/linux-base.postinst line 1059, STDIN line 10. Any advise using dosfslabel on my system to diagnose more precisely the problem is welcome. I hope it's not because of any missusing of partition. You have a line in /etc/fstab that refers to a disk or partition with filesystem type 'vfat' or 'msdos', while the disk/partition actually uses some other type. You should remove or correct this line, then run 'dpkg --configure --pending' to retry the upgrade. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part ---End Message---
Bug#575924: linux-image-2.6.32-4-amd64: fuse module oops on boot
On Fri, 2010-06-18 at 09:44 -0400, Denis Laxalde wrote: Hi, Le lundi 12 avril 2010 à 01:18 +0100, Ben Hutchings a écrit : On Sun, 2010-04-11 at 18:23 -0400, Denis Laxalde wrote: forwarded 575924 https://bugzilla.kernel.org/show_bug.cgi?id=14347 thanks On Sun, 11 Apr 2010 16:05:57 +0100, Ben Hutchings wrote: On Sat, 2010-04-10 at 23:05 -0400, Denis Laxalde wrote: Hi, On Sun, 11 Apr 2010 00:28:24 +0100, Ben Hutchings wrote: The more serious error messages suggest memory corruption. Have you tested the RAM with memtest86+ yet? Yes, I've just run a pretty long test with memtest86+ and there was no error reported. OK, so we can be fairly sure this is a kernel bug. Please report this at https://bugzilla.kernel.org. It is hard to know where the bug may be, but try submitting it under product 'Memory Management', component 'Slab Allocator'. Let us know the bug number so we can track it. The above bug report looks similar, so I just added comments and dmesgs there. Maybe the bug should be retitled ? I'm not convinced that these are the same bug. Let's see what the response is. There was no response so far and, since boot failures still happen from time to time (once a week or so), I may open a new bug upstream... Please do. 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#586494: linux-image-2.6.26-2-686: Dell PowerEdge 4200's don't work with 2.6.26
On Sun, 2010-06-20 at 17:47 -0400, trouble daemon wrote: Ben, My guess is that something has gone wrong with interrupt routing. Can you try adding 'acpi=noirq' to the kernel parameters? Okay, I tied acpi=noirq with the stock lenny 2.6.26 kernel, and it looks like the same exact problem still. I can capture a dmesg for that as well if you want though, but I didn't have the connected serial machine up at the time. Another option that may be worth trying is 'noapic'. If my first suggestion doesn't work, can you also try a more recent kernel version such as 2.6.32 (currently in testing) and 2.6.34 (currently in experimental)? Ok, I am currently compiling the 2.6.32 debianized kernel with the config from the lenny package. I tried to manually install the .deb, but there were too many dependency differences in it to pull in, so I opted to just recompile. [...] You need to get the corresponding linux-base package from testing or experimental, but the other dependencies should be satisfiable in lenny. 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#586494: linux-image-2.6.26-2-686: Dell PowerEdge 4200's don't work with 2.6.26
Ben, My guess is that something has gone wrong with interrupt routing. Can you try adding 'acpi=noirq' to the kernel parameters? Okay, I tied acpi=noirq with the stock lenny 2.6.26 kernel, and it looks like the same exact problem still. I can capture a dmesg for that as well if you want though, but I didn't have the connected serial machine up at the time. If my first suggestion doesn't work, can you also try a more recent kernel version such as 2.6.32 (currently in testing) and 2.6.34 (currently in experimental)? Ok, I am currently compiling the 2.6.32 debianized kernel with the config from the lenny package. I tried to manually install the .deb, but there were too many dependency differences in it to pull in, so I opted to just recompile. It will take a few hours, so rather than email you back after I try it, I will try 2.6.32 with stock config with and without acpi=noirq, the 2.6.34 from experimental with and without noirq, and a vanilla set of kernels hand tuned to the exact hardware the system has, and then get back to you. Unless I hear back from you sooner of course. Dan -- 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/aanlktim-ydgvait9juengdx_mjxxczl0ynf6dtnv5...@mail.gmail.com
Processing of linux-2.6_2.6.26-24_amd64.changes
linux-2.6_2.6.26-24_amd64.changes uploaded successfully to localhost along with the files: linux-2.6_2.6.26-24.dsc linux-2.6_2.6.26-24.diff.gz linux-doc-2.6.26_2.6.26-24_all.deb linux-manual-2.6.26_2.6.26-24_all.deb linux-patch-debian-2.6.26_2.6.26-24_all.deb linux-source-2.6.26_2.6.26-24_all.deb linux-support-2.6.26-2_2.6.26-24_all.deb linux-tree-2.6.26_2.6.26-24_all.deb linux-image-2.6.26-2-amd64_2.6.26-24_amd64.deb linux-headers-2.6.26-2-amd64_2.6.26-24_amd64.deb linux-headers-2.6.26-2-common_2.6.26-24_amd64.deb linux-image-2.6.26-2-openvz-amd64_2.6.26-24_amd64.deb linux-headers-2.6.26-2-openvz-amd64_2.6.26-24_amd64.deb linux-headers-2.6.26-2-common-openvz_2.6.26-24_amd64.deb linux-headers-2.6.26-2-all_2.6.26-24_amd64.deb linux-headers-2.6.26-2-all-amd64_2.6.26-24_amd64.deb linux-libc-dev_2.6.26-24_amd64.deb linux-image-2.6.26-2-vserver-amd64_2.6.26-24_amd64.deb linux-headers-2.6.26-2-vserver-amd64_2.6.26-24_amd64.deb linux-headers-2.6.26-2-common-vserver_2.6.26-24_amd64.deb linux-image-2.6.26-2-xen-amd64_2.6.26-24_amd64.deb linux-modules-2.6.26-2-xen-amd64_2.6.26-24_amd64.deb linux-headers-2.6.26-2-xen-amd64_2.6.26-24_amd64.deb xen-linux-system-2.6.26-2-xen-amd64_2.6.26-24_amd64.deb linux-headers-2.6.26-2-common-xen_2.6.26-24_amd64.deb Greetings, Your Debian queue daemon (running on host ries.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/e1oqsfq-0003x6...@ries.debian.org
Bug#586494: linux-image-2.6.26-2-686: Dell PowerEdge 4200's don't work with 2.6.26
Ok, I am currently compiling the 2.6.32 debianized kernel with the config from the lenny package. Ooops, small correction. What I meant to say was that I am compiling the 2.6.32 source from squeeze using the squeeze config in the .deb, not the lenny config. ie: it should end up effectively a squeeze (testing) kernel. My apologies. Dan -- 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/aanlktinbc8fbfmttvmdl4gbpq8po80q4ihhem4tr5...@mail.gmail.com
Bug#520468: Incorporate fixes for WUSB54GS support from 2.6.33
On Fri, 2010-06-18 at 00:55 +0100, Luís Picciochi Oliveira wrote: As I told you I would, I tested WUSB54GS support on the kernels shipped by Debian: 2.6.32 (2.6.32-15) from Squeeze and 2.6.34 (2.6.34-1~experimental.2) from sid. Unfortunately, none of them worked. :( I'm attaching the output at syslog with network-manager and with an /etc/network/interfaces file (and no n-m installed). Perhaps there's some patch missing that I didn't point out... I'm sorry but I can't tell what can it be now. I'm using the vanilla 2.6.33-rc1 kernel again, which works. Or possibly this bug fix is bad for that device: debian/patches/bugfix/all/rndis_host-Poll-status-channel-before-control-channel.patch Could you try reverting that in either of the Debian kernel packages? 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#576635: Acknowledgement (Unable to access an encrypted root partition after a failed resume)
I finally got around to looking at the image I took. The encryption seems to be perfectly fine: there's a LUKS header in the block device, and I can open it up using cryptsetup. The trouble seems to be that it's not recognized as a physical LVM volume. Comparing it to a working physical volume, I notice that the working volume starts off with 0x200 NULs, then LABELONE followed by LVM2 001, 32 random alphanumeric characters, and then some binary data, followed by lots of NULs. At 0x1004, the working volume contains the string LVM2 x[5A%r0N* followed by a bit more binary data; at 0x1200, there's what appears to be a volume group configuration. On the broken volume, LABELONE and the first occurrence of LVM2 001 are missing. However, I do see LVM2 x[5A%r0N* at 0x1004 and what appears to be volume group configuration at 0x1200. My hunch is that the physical volume's information is still present, but the magic strings that LVM uses to recognize it as a physical volume have gone missing. It almost looks like the first 4096 (0x1000) bytes of the partition were overwritten with garbage. I might be able to recover everything if I can just create a correct PV header at the front of the device. Is there any documentation on what the format of a PV header is? I couldn't find anything online. Also, any suggestions about how to identify the culprit that was responsible for the overwrite? The first few lines of the hexdump are: ff ff ff ff ff ff ff ff 00 00 00 00 00 00 00 00 || * 0020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 || * 0040 08 00 00 00 04 00 00 00 e1 7a 54 3f f6 28 5c 3f |.zT?.(\?| 0050 80 30 4f f5 ae 7f 00 00 10 00 00 00 04 00 00 00 |.0O.| 0060 9a 99 59 3f ae 47 61 3f 80 30 4f f5 ae 7f 00 00 |..Y?.Ga?.0O.| 0070 20 00 00 00 04 00 00 00 c1 ca 61 3f c3 f5 68 3f | .a?..h?| 0080 80 30 4f f5 ae 7f 00 00 30 00 00 00 08 00 00 00 |.0O.0...| 0090 b8 1e 65 3f 83 c0 6a 3f 90 30 4f f5 ae 7f 00 00 |..e?..j?.0O.| 00a0 40 00 00 00 08 00 00 00 a8 c6 6b 3f d7 a3 70 3f |@.k?..p?| It repeats like that for several pages. I did find some references to the --restorefile option to pvcreate; it sounds like I could maybe recover the physical volume using that option, assuming that the metadata I extracted from the volume is correct. I've saved the first megabyte of the unencrypted device in its broken state for future reference, in case it's useful for diagnosing what happened. Daniel -- 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/20100620213433.ga20...@emurlahn.burrows.local
Processed: Re: Bug#576635: Acknowledgement (Unable to access an encrypted root partition after a failed resume)
Processing commands for cont...@bugs.debian.org:
reassign 576635 linux-2.6
Bug #576635 {Done: Moritz Muehlenhoff j...@inutil.org}
[linux-image-2.6.32-3-amd64] Unable to access an encrypted root partition after
a failed resume
Warning: Unknown package 'linux-image-2.6.32-3-amd64'
Bug reassigned from package 'linux-image-2.6.32-3-amd64' to 'linux-2.6'.
Bug No longer marked as found in versions linux-2.6/2.6.32-9.
Bug No longer marked as fixed in versions 2.6.32-15.
--
Stopping processing here.
Please contact me if you need assistance.
--
576635: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576635
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.127707342922450.transcr...@bugs.debian.org
Bug#584906: nfs-kernel-server: nfs stop working suddenly
On Tue, 2010-06-08 at 10:30 +0200, Leopold Palomo-Avellaneda wrote: A Dimarts 08 Juny 2010, Ben Hutchings va escriure: On Mon, 2010-06-07 at 15:34 +0200, Leopold Palomo wrote: Package: nfs-kernel-server Version: 1:1.1.2-6lenny1 Severity: important In this server nfs have been working perfectly one year and half. However, lately we have have some serious issues with the nfs. Simply, the service stop and the _only_ way to repair the service is restarting the service. In the logs the only reference that we have is: orion mountd[4905]: couldn't open /var/lib/nfs/etab It's a bit annoying because our little network depends on that service. Do you have any idea why /var/lib/nfs/etab might be deleted or made unreadable? no ... the filesystem is consistent and when it works, works normally. I have not seen no important messages referring to nfs. Some idea to get information about this? If you install inotify-tools you can then use 'inotifywait -m /var/lib/nfs' to monitor changes in this directory. (It should be possible to get a timestamp for every change, but this feature seems to be broken.) The other option is to use auditd. This should be able to give you more detail, but would be more complex to set up. 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#584881: Lockups under heavy disk IO; md (RAID) resync/check implicated
On Mon, 2010-06-07 at 10:53 +0100, Ian Jackson wrote: Package: linux-image-2.6.26-2-686-bigmem Version: 2.6.26-21lenny4 I keep getting soft lockups; the symptoms appear to be that user processes become deadlocked when they try to access the disk, but the kernel doesn't notice that anything is wrong. [...] We really need to see the kernel messages reporting soft-lockup. Note that your disk configuration is unusual and probably not well-tested by others. It is unlikely that anyone in the kernel team will be able to debug this as I don't think any of us have particular expertise in this area. If you have the opportunity, it would be helpful if you could test a newer kernel version. This would give us a clue as to whether the bug has subsequently been fixed upstream, and if not then it would be the basis for an upstream 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
Processed: tagging 584259, tagging 503310, tagging 583082, tagging 583390, closing 582906
Processing commands for cont...@bugs.debian.org: tags 584259 - moreinfo Bug #584259 [linux-2.6] initramfs-tools: breaks software suspend (hibernation) Removed tag(s) moreinfo. tags 503310 - moreinfo Bug #503310 [nfs-common] mount.nfs: np-1b:/vol/dev_src failed, security flavor not supported Removed tag(s) moreinfo. tags 583082 - moreinfo Bug #583082 [linux-2.6] kernel: khubd crash Removed tag(s) moreinfo. tags 583390 - sid Bug #583390 [linux-2.6] linux-image-2.6.32-5-686: Hangs with ata frozen on boot Removed tag(s) sid. # submitter said it could be closed close 582906 Bug#582906: 2.6.32-5-686: iwl3945_request_scan( ) - kernel NULL pointer dereference 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Sedat Dilek sedat.di...@googlemail.com thanks Stopping processing here. Please contact me if you need assistance. -- 582906: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582906 583390: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583390 503310: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=503310 583082: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583082 584259: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584259 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.12770758057126.transcr...@bugs.debian.org
Bug#551101: still exists
On Mon, 2010-05-17 at 13:27 +0200, martin f krafft wrote: I am running 2.6.32 and am faced by exactly this problem on a machine I cannot just reboot: % ps aux | egrep -c '\D\.+vgdisplay' 37821 lsof or strace on existing processes don't show anything, but strace on a new vgdisplay process shows that it blocks on opening /dev/cdrom, which seems to be defective. Was this a version before or after the libata transition? 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 580149
Processing commands for cont...@bugs.debian.org: tags 580149 - moreinfo Bug #580149 [linux-2.6] linux-image-2.6.32-trunk-amd64: usb - sata Sense not available Removed tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 580149: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580149 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.12770760888595.transcr...@bugs.debian.org
linux-2.6_2.6.26-24_amd64.changes ACCEPTED
Notes: Mapping stable to proposed-updates. Accepted: linux-2.6_2.6.26-24.diff.gz to main/l/linux-2.6/linux-2.6_2.6.26-24.diff.gz linux-2.6_2.6.26-24.dsc to main/l/linux-2.6/linux-2.6_2.6.26-24.dsc linux-doc-2.6.26_2.6.26-24_all.deb to main/l/linux-2.6/linux-doc-2.6.26_2.6.26-24_all.deb linux-headers-2.6.26-2-all-amd64_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-all-amd64_2.6.26-24_amd64.deb linux-headers-2.6.26-2-all_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-all_2.6.26-24_amd64.deb linux-headers-2.6.26-2-amd64_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-amd64_2.6.26-24_amd64.deb linux-headers-2.6.26-2-common-openvz_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common-openvz_2.6.26-24_amd64.deb linux-headers-2.6.26-2-common-vserver_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common-vserver_2.6.26-24_amd64.deb linux-headers-2.6.26-2-common-xen_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common-xen_2.6.26-24_amd64.deb linux-headers-2.6.26-2-common_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common_2.6.26-24_amd64.deb linux-headers-2.6.26-2-openvz-amd64_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-openvz-amd64_2.6.26-24_amd64.deb linux-headers-2.6.26-2-vserver-amd64_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-vserver-amd64_2.6.26-24_amd64.deb linux-headers-2.6.26-2-xen-amd64_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-xen-amd64_2.6.26-24_amd64.deb linux-image-2.6.26-2-amd64_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-image-2.6.26-2-amd64_2.6.26-24_amd64.deb linux-image-2.6.26-2-openvz-amd64_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-image-2.6.26-2-openvz-amd64_2.6.26-24_amd64.deb linux-image-2.6.26-2-vserver-amd64_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-image-2.6.26-2-vserver-amd64_2.6.26-24_amd64.deb linux-image-2.6.26-2-xen-amd64_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-image-2.6.26-2-xen-amd64_2.6.26-24_amd64.deb linux-libc-dev_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-libc-dev_2.6.26-24_amd64.deb linux-manual-2.6.26_2.6.26-24_all.deb to main/l/linux-2.6/linux-manual-2.6.26_2.6.26-24_all.deb linux-modules-2.6.26-2-xen-amd64_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-modules-2.6.26-2-xen-amd64_2.6.26-24_amd64.deb linux-patch-debian-2.6.26_2.6.26-24_all.deb to main/l/linux-2.6/linux-patch-debian-2.6.26_2.6.26-24_all.deb linux-source-2.6.26_2.6.26-24_all.deb to main/l/linux-2.6/linux-source-2.6.26_2.6.26-24_all.deb linux-support-2.6.26-2_2.6.26-24_all.deb to main/l/linux-2.6/linux-support-2.6.26-2_2.6.26-24_all.deb linux-tree-2.6.26_2.6.26-24_all.deb to main/l/linux-2.6/linux-tree-2.6.26_2.6.26-24_all.deb xen-linux-system-2.6.26-2-xen-amd64_2.6.26-24_amd64.deb to main/l/linux-2.6/xen-linux-system-2.6.26-2-xen-amd64_2.6.26-24_amd64.deb Override entries for your package: linux-2.6_2.6.26-24.dsc - source devel linux-doc-2.6.26_2.6.26-24_all.deb - optional doc linux-headers-2.6.26-2-all-amd64_2.6.26-24_amd64.deb - optional devel linux-headers-2.6.26-2-all_2.6.26-24_amd64.deb - optional devel linux-headers-2.6.26-2-amd64_2.6.26-24_amd64.deb - optional devel linux-headers-2.6.26-2-common-openvz_2.6.26-24_amd64.deb - optional devel linux-headers-2.6.26-2-common-vserver_2.6.26-24_amd64.deb - optional devel linux-headers-2.6.26-2-common-xen_2.6.26-24_amd64.deb - optional devel linux-headers-2.6.26-2-common_2.6.26-24_amd64.deb - optional devel linux-headers-2.6.26-2-openvz-amd64_2.6.26-24_amd64.deb - optional devel linux-headers-2.6.26-2-vserver-amd64_2.6.26-24_amd64.deb - optional devel linux-headers-2.6.26-2-xen-amd64_2.6.26-24_amd64.deb - optional devel linux-image-2.6.26-2-amd64_2.6.26-24_amd64.deb - optional admin linux-image-2.6.26-2-openvz-amd64_2.6.26-24_amd64.deb - optional admin linux-image-2.6.26-2-vserver-amd64_2.6.26-24_amd64.deb - optional admin linux-image-2.6.26-2-xen-amd64_2.6.26-24_amd64.deb - optional admin linux-libc-dev_2.6.26-24_amd64.deb - optional devel linux-manual-2.6.26_2.6.26-24_all.deb - optional doc linux-modules-2.6.26-2-xen-amd64_2.6.26-24_amd64.deb - optional admin linux-patch-debian-2.6.26_2.6.26-24_all.deb - optional devel linux-source-2.6.26_2.6.26-24_all.deb - optional devel linux-support-2.6.26-2_2.6.26-24_all.deb - optional devel linux-tree-2.6.26_2.6.26-24_all.deb - optional devel xen-linux-system-2.6.26-2-xen-amd64_2.6.26-24_amd64.deb - extra admin Announcing to debian-chan...@lists.debian.org Closing bugs: 505609 511892 583139 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/e1oqwce-0003od...@ries.debian.org
Bug#505609: marked as done (Unbootable after kernel upgrade: Lilo can't load kernel)
Your message dated Mon, 21 Jun 2010 01:53:10 + with message-id e1oqwce-0003oj...@ries.debian.org and subject line Bug#505609: fixed in linux-2.6 2.6.26-24 has caused the Debian Bug report #505609, regarding Unbootable after kernel upgrade: Lilo can't load kernel 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.) -- 505609: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=505609 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-10 Severity: critical I've did an upgrade on 2008-11-09, on a new installed system, upgrading kernel 2.6.26-09 to 2.6.26.10. Apt was also upgraded. I've seen nothing strange during upgrade and in the apt and dpkg logs. The system is entirely on LVM partitions. When reboting I obtain this message from Lilo: Loading LinuxEBDA is big; kernel setup stack overlaps LILO second stage. and the computer halt. regards -- Xavier xav...@alternatif.org ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.26-24 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: linux-2.6_2.6.26-24.diff.gz to main/l/linux-2.6/linux-2.6_2.6.26-24.diff.gz linux-2.6_2.6.26-24.dsc to main/l/linux-2.6/linux-2.6_2.6.26-24.dsc linux-doc-2.6.26_2.6.26-24_all.deb to main/l/linux-2.6/linux-doc-2.6.26_2.6.26-24_all.deb linux-headers-2.6.26-2-all-amd64_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-all-amd64_2.6.26-24_amd64.deb linux-headers-2.6.26-2-all_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-all_2.6.26-24_amd64.deb linux-headers-2.6.26-2-amd64_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-amd64_2.6.26-24_amd64.deb linux-headers-2.6.26-2-common-openvz_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common-openvz_2.6.26-24_amd64.deb linux-headers-2.6.26-2-common-vserver_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common-vserver_2.6.26-24_amd64.deb linux-headers-2.6.26-2-common-xen_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common-xen_2.6.26-24_amd64.deb linux-headers-2.6.26-2-common_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common_2.6.26-24_amd64.deb linux-headers-2.6.26-2-openvz-amd64_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-openvz-amd64_2.6.26-24_amd64.deb linux-headers-2.6.26-2-vserver-amd64_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-vserver-amd64_2.6.26-24_amd64.deb linux-headers-2.6.26-2-xen-amd64_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-xen-amd64_2.6.26-24_amd64.deb linux-image-2.6.26-2-amd64_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-image-2.6.26-2-amd64_2.6.26-24_amd64.deb linux-image-2.6.26-2-openvz-amd64_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-image-2.6.26-2-openvz-amd64_2.6.26-24_amd64.deb linux-image-2.6.26-2-vserver-amd64_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-image-2.6.26-2-vserver-amd64_2.6.26-24_amd64.deb linux-image-2.6.26-2-xen-amd64_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-image-2.6.26-2-xen-amd64_2.6.26-24_amd64.deb linux-libc-dev_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-libc-dev_2.6.26-24_amd64.deb linux-manual-2.6.26_2.6.26-24_all.deb to main/l/linux-2.6/linux-manual-2.6.26_2.6.26-24_all.deb linux-modules-2.6.26-2-xen-amd64_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-modules-2.6.26-2-xen-amd64_2.6.26-24_amd64.deb linux-patch-debian-2.6.26_2.6.26-24_all.deb to main/l/linux-2.6/linux-patch-debian-2.6.26_2.6.26-24_all.deb linux-source-2.6.26_2.6.26-24_all.deb to main/l/linux-2.6/linux-source-2.6.26_2.6.26-24_all.deb linux-support-2.6.26-2_2.6.26-24_all.deb to main/l/linux-2.6/linux-support-2.6.26-2_2.6.26-24_all.deb linux-tree-2.6.26_2.6.26-24_all.deb to main/l/linux-2.6/linux-tree-2.6.26_2.6.26-24_all.deb xen-linux-system-2.6.26-2-xen-amd64_2.6.26-24_amd64.deb to main/l/linux-2.6/xen-linux-system-2.6.26-2-xen-amd64_2.6.26-24_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 505...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. dann frazier da...@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
Bug#535331: marked as done (lilo not run after install/upgrade)
Your message dated Mon, 21 Jun 2010 01:53:10 + with message-id e1oqwce-0003oj...@ries.debian.org and subject line Bug#505609: fixed in linux-2.6 2.6.26-24 has caused the Debian Bug report #505609, regarding lilo not run after install/upgrade 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.) -- 505609: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=505609 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-2-686 Version: 2.6.26-17 Hello, after installing linux image the lilo is not being called, which results into system not being bootable after upgrade. I've tried without kernel-img.conf also with it, containing do_bootloader = Yes, nothing helped. If lilo isn't supported (oh, please, no), it should be mentioned somewhere... -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. Save the whales. Collect the whole set. ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.26-24 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: linux-2.6_2.6.26-24.diff.gz to main/l/linux-2.6/linux-2.6_2.6.26-24.diff.gz linux-2.6_2.6.26-24.dsc to main/l/linux-2.6/linux-2.6_2.6.26-24.dsc linux-doc-2.6.26_2.6.26-24_all.deb to main/l/linux-2.6/linux-doc-2.6.26_2.6.26-24_all.deb linux-headers-2.6.26-2-all-amd64_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-all-amd64_2.6.26-24_amd64.deb linux-headers-2.6.26-2-all_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-all_2.6.26-24_amd64.deb linux-headers-2.6.26-2-amd64_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-amd64_2.6.26-24_amd64.deb linux-headers-2.6.26-2-common-openvz_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common-openvz_2.6.26-24_amd64.deb linux-headers-2.6.26-2-common-vserver_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common-vserver_2.6.26-24_amd64.deb linux-headers-2.6.26-2-common-xen_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common-xen_2.6.26-24_amd64.deb linux-headers-2.6.26-2-common_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common_2.6.26-24_amd64.deb linux-headers-2.6.26-2-openvz-amd64_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-openvz-amd64_2.6.26-24_amd64.deb linux-headers-2.6.26-2-vserver-amd64_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-vserver-amd64_2.6.26-24_amd64.deb linux-headers-2.6.26-2-xen-amd64_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-xen-amd64_2.6.26-24_amd64.deb linux-image-2.6.26-2-amd64_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-image-2.6.26-2-amd64_2.6.26-24_amd64.deb linux-image-2.6.26-2-openvz-amd64_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-image-2.6.26-2-openvz-amd64_2.6.26-24_amd64.deb linux-image-2.6.26-2-vserver-amd64_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-image-2.6.26-2-vserver-amd64_2.6.26-24_amd64.deb linux-image-2.6.26-2-xen-amd64_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-image-2.6.26-2-xen-amd64_2.6.26-24_amd64.deb linux-libc-dev_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-libc-dev_2.6.26-24_amd64.deb linux-manual-2.6.26_2.6.26-24_all.deb to main/l/linux-2.6/linux-manual-2.6.26_2.6.26-24_all.deb linux-modules-2.6.26-2-xen-amd64_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-modules-2.6.26-2-xen-amd64_2.6.26-24_amd64.deb linux-patch-debian-2.6.26_2.6.26-24_all.deb to main/l/linux-2.6/linux-patch-debian-2.6.26_2.6.26-24_all.deb linux-source-2.6.26_2.6.26-24_all.deb to main/l/linux-2.6/linux-source-2.6.26_2.6.26-24_all.deb linux-support-2.6.26-2_2.6.26-24_all.deb to main/l/linux-2.6/linux-support-2.6.26-2_2.6.26-24_all.deb linux-tree-2.6.26_2.6.26-24_all.deb to main/l/linux-2.6/linux-tree-2.6.26_2.6.26-24_all.deb xen-linux-system-2.6.26-2-xen-amd64_2.6.26-24_amd64.deb to main/l/linux-2.6/xen-linux-system-2.6.26-2-xen-amd64_2.6.26-24_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 505...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. dann frazier da...@debian.org (supplier of updated linux-2.6 package) (This message was generated automatically at their
Bug#583139: marked as done (linux-2.6: no DHCP offers on r8169)
Your message dated Mon, 21 Jun 2010 01:53:10 + with message-id e1oqwce-0003os...@ries.debian.org and subject line Bug#583139: fixed in linux-2.6 2.6.26-24 has caused the Debian Bug report #583139, regarding linux-2.6: no DHCP offers on r8169 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.) -- 583139: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583139 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.26-22lenny1 Severity: important Hi, I get no DHCP offers on the r8169 device since the upgrade to 2.6.26-22lenny1. Reverting to 2.6.26-22 does not fix the problem. Reverting to 2.6.26-21lenny4 *does* fix the problem. Please contact me for more info. Alex -- System Information: Debian Release: 5.0.4 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-2-openvz-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.26-24 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: linux-2.6_2.6.26-24.diff.gz to main/l/linux-2.6/linux-2.6_2.6.26-24.diff.gz linux-2.6_2.6.26-24.dsc to main/l/linux-2.6/linux-2.6_2.6.26-24.dsc linux-doc-2.6.26_2.6.26-24_all.deb to main/l/linux-2.6/linux-doc-2.6.26_2.6.26-24_all.deb linux-headers-2.6.26-2-all-amd64_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-all-amd64_2.6.26-24_amd64.deb linux-headers-2.6.26-2-all_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-all_2.6.26-24_amd64.deb linux-headers-2.6.26-2-amd64_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-amd64_2.6.26-24_amd64.deb linux-headers-2.6.26-2-common-openvz_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common-openvz_2.6.26-24_amd64.deb linux-headers-2.6.26-2-common-vserver_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common-vserver_2.6.26-24_amd64.deb linux-headers-2.6.26-2-common-xen_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common-xen_2.6.26-24_amd64.deb linux-headers-2.6.26-2-common_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-common_2.6.26-24_amd64.deb linux-headers-2.6.26-2-openvz-amd64_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-openvz-amd64_2.6.26-24_amd64.deb linux-headers-2.6.26-2-vserver-amd64_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-vserver-amd64_2.6.26-24_amd64.deb linux-headers-2.6.26-2-xen-amd64_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-headers-2.6.26-2-xen-amd64_2.6.26-24_amd64.deb linux-image-2.6.26-2-amd64_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-image-2.6.26-2-amd64_2.6.26-24_amd64.deb linux-image-2.6.26-2-openvz-amd64_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-image-2.6.26-2-openvz-amd64_2.6.26-24_amd64.deb linux-image-2.6.26-2-vserver-amd64_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-image-2.6.26-2-vserver-amd64_2.6.26-24_amd64.deb linux-image-2.6.26-2-xen-amd64_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-image-2.6.26-2-xen-amd64_2.6.26-24_amd64.deb linux-libc-dev_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-libc-dev_2.6.26-24_amd64.deb linux-manual-2.6.26_2.6.26-24_all.deb to main/l/linux-2.6/linux-manual-2.6.26_2.6.26-24_all.deb linux-modules-2.6.26-2-xen-amd64_2.6.26-24_amd64.deb to main/l/linux-2.6/linux-modules-2.6.26-2-xen-amd64_2.6.26-24_amd64.deb linux-patch-debian-2.6.26_2.6.26-24_all.deb to main/l/linux-2.6/linux-patch-debian-2.6.26_2.6.26-24_all.deb linux-source-2.6.26_2.6.26-24_all.deb to main/l/linux-2.6/linux-source-2.6.26_2.6.26-24_all.deb linux-support-2.6.26-2_2.6.26-24_all.deb to main/l/linux-2.6/linux-support-2.6.26-2_2.6.26-24_all.deb linux-tree-2.6.26_2.6.26-24_all.deb to main/l/linux-2.6/linux-tree-2.6.26_2.6.26-24_all.deb xen-linux-system-2.6.26-2-xen-amd64_2.6.26-24_amd64.deb to main/l/linux-2.6/xen-linux-system-2.6.26-2-xen-amd64_2.6.26-24_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 583...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. dann frazier da...@debian.org (supplier of updated linux-2.6 package) (This message was generated automatically at their request; if you believe that
Bug#574510: #574510: statd running as root after remove/install
Package: nfs-common Followup-For: Bug #574510 this patch partially addresses the issue by ensuring that the files are owned by statd no matter what version is installed, even if a previous version was installed. --- nfs-common.postinst.orig2010-06-20 18:29:11.0 -0700 +++ nfs-common.postinst 2010-06-20 18:28:44.0 -0700 @@ -23,7 +23,6 @@ rmdir --ignore-fail-on-non-empty /home/statd fi fi - if [ $2 = ] || dpkg --compare-versions $2 lt 1:1.0.7-16; then chown statd /var/lib/nfs/sm \ /var/lib/nfs/sm.bak \ /var/lib/nfs/rpc_pipefs \ @@ -31,7 +30,6 @@ if [ -f /var/lib/nfs/state ]; then chown statd /var/lib/nfs/state fi - fi if [ $2 != ] || dpkg --compare-versions $2 lt 1:1.1.0-14; then if dpkg-statoverride --list /sbin/mount.nfs /dev/null 21; then it looks like the comparison with an empty $2 argument works for an initial install, but not when a package was removed and later re-installed, as postinst will be called with the previously installed version as an argument. other parts of the postinst may be affected by similar uses of tests against $2. 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/20100621020413.go9...@claws.fglan
Bug#509077: initramfs-tools: support alternate DHCP port and DHCP vendor-class-identifier
On Sat, Jun 19, 2010 at 06:43:16PM +0200, maximilian attems wrote: On Tue, 08 Jun 2010, Michael Prokop wrote: * Vagrant Cascadian vagrant+debianb...@freegeek.org [Mit Dez 17, 2008 at 07:01:51 -0800]: please consider the attached patch, which adds boot prompt parameters for two of ipconfig's commandline options in the configure_networking function: - using an alternate DHCP port (dhcpport=NNN, ipconfig -p NNN) - specifying the vendor-class-identifier (dhcpvci=XXX, ipconfig -i XXX) supporting these options gives additional flexibility in distinguishing thin clients from conventional workstations in a mixed network. Sorry that no one took care of your bugreport for so long, Vagrant. Patch looks fine to me. maks, any objections against inclusion of the patches? I had been dragging that patch as I do not like to add to many bootparams that are outside of documented upstream linux-2.6 handling and thus initramfs-tools specific. waited to see if a second voice would raise.. understandable. perhaps it would be better to rewrite in such a way that ipconfig could be passed arbitrary arguments? of course, if it ever switched away from ipconfig to some other dhcp client, it'd be nice to not have to change syntax or configuration names... I do not see so much the point of setting ipconfig vendor class id. why would that be needed for booting? in order to distinguish a machine that's doing network boot for debian-installer, LTSP or PXE. for example, in each case, you might want to hand it a different dhcp filename option. pxe should get pxelinux.0, d-i gets a preseeding URL, and ltsp could get a configuration file... the alternate DHCP port looks indeed more interesting, but no idea how common that is in the wild? i don't know that it's incredibly common, but is not infrequently asked for in LTSP environments, though there are other alternatives using dnsmasq's dhcp proxy support now, so it's maybe less important. and if there is not a place in the ip= monster bootparam? don't believe so. 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/20100621021141.gp9...@claws.fglan
Bug#541073: 152d:2338 JMicron USA Technology Corp. JM20337 Hi-Speed USB to SATA PATA Combo Bridge
zh do I take it correctly you connect your converter to a VIA Chip card? zh Did you try to connect it to a motherboard USB? All I now is I first turn on the AC power, put in the CDROM disk, then attach USB. zh (Maybe ata/66/100 cable, I suppose your drive is not udma/133) They are CD/DVD players. zh (Take a look at the 580149 bug report) All I know is both 05e3:0701 Genesys Logic, Inc. USB 2.0 IDE Adapter 152d:2338 JMicron Technology Corp. / JMicron USA Technology Corp. JM20337 Hi-Speed USB to SATA PATA Combo Bridge work using # mount -t iso9660 /dev/sr1 /mnt/usb/cdrom/ when scsi 4:0:0:0: CD-ROM PHILIPS DVDR1648P1 P1.2 PQ: 0 ANSI: 0 is attached, on (lshw): description: Notebook product: 1834NV1 vendor: IBM version: ThinkPad R50e Maybe next month when I go back to where I have the other device, I will try adjusting the master/slave jumper and see if it helps. -- 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/87k4ptuivi@jidanni.org
