Processed: found 518812 in 2.6.26-13, fixed 518812 in 2.6.32-9
Processing commands for cont...@bugs.debian.org: > found 518812 2.6.26-13 Bug #518812 [linux-2.6] I/O errors with 3w- and 8Gb ram There is no source info for the package 'linux-2.6' at version '2.6.26-13' with architecture '' Unable to make a source version for version '2.6.26-13' Bug Marked as found in versions 2.6.26-13. > fixed 518812 2.6.32-9 Bug #518812 [linux-2.6] I/O errors with 3w- and 8Gb ram There is no source info for the package 'linux-2.6' at version '2.6.32-9' with architecture '' Unable to make a source version for version '2.6.32-9' Bug Marked as fixed in versions 2.6.32-9. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- 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.12717201655593.transcr...@bugs.debian.org
Processed: tagging 578398
Processing commands for cont...@bugs.debian.org: > # Automatically generated email from bts, devscripts version 2.10.35lenny7 > tags 578398 + pending Bug #578398 [linux-2.6] megasas: Failed to copy out to user sense data Added tag(s) pending. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- 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.12717200984937.transcr...@bugs.debian.org
Processed: tagging 576929
Processing commands for cont...@bugs.debian.org: > # Automatically generated email from bts, devscripts version 2.10.35lenny7 > tags 576929 + pending Bug #576929 [linux-image-2.6.26-2-686] rndis_host fails to handle 2Wire HomePortal 1000SW Added tag(s) pending. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- 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.127171859625284.transcr...@bugs.debian.org
Bug#576929: rndis_host handles 2Wire HomePortal 1000SW
Forwarded Message From: Mark Glassberg To: Ben Hutchings Subject: rndis_host handles 2Wire HomePortal 1000SW Date: Mon, 19 Apr 2010 11:56:46 -0400 On Sun, Apr 18, 2010 at 06:09:53PM +0100, Ben Hutchings wrote: > It appears to me that the rndis_host driver is working now and you just > need to update the iptables firewall configuration. Absolutely! Thanks a million. Mark -- 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/1271716449.2197.0.ca...@localhost
[bts-link] source package linux-2.6
# # bts-link upstream status pull for source package linux-2.6 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #574598 (http://bugs.debian.org/574598) # * http://bugzilla.openvz.org/show_bug.cgi?id=1461 # * remote status changed: NEW -> RESOLVED # * remote resolution changed: (?) -> FIXED # * closed upstream tags 574598 + fixed-upstream usertags 574598 - status-NEW usertags 574598 + status-RESOLVED resolution-FIXED thanks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100419165926.5896.9306.btsl...@merkel.debian.org
Processed: [bts-link] source package linux-2.6
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package linux-2.6 > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). > # remote status report for #574598 (http://bugs.debian.org/574598) > # * http://bugzilla.openvz.org/show_bug.cgi?id=1461 > # * remote status changed: NEW -> RESOLVED > # * remote resolution changed: (?) -> FIXED > # * closed upstream > tags 574598 + fixed-upstream Bug #574598 [linux-image-2.6.32-4-openvz-amd64] openvz kernel doesn't work and spams into dmesg: NULL exec env (timr->it_process->ve_task_info.owner_env) Added tag(s) fixed-upstream. > usertags 574598 - status-NEW Bug#574598: openvz kernel doesn't work and spams into dmesg: NULL exec env (timr->it_process->ve_task_info.owner_env) Usertags were: status-NEW. Usertags are now: . > usertags 574598 + status-RESOLVED resolution-FIXED Bug#574598: openvz kernel doesn't work and spams into dmesg: NULL exec env (timr->it_process->ve_task_info.owner_env) There were no usertags set. Usertags are now: status-RESOLVED resolution-FIXED. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- 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.127169636914976.transcr...@bugs.debian.org
Bug#578398: megasas: Failed to copy out to user sense data
Package: linux-2.6 Version: 2.6.32-9 Severity: normal The kernel 2.6.32 is affected by the following bug: http://bugzilla.kernel.org/show_bug.cgi?id=15001 The issue is caused by a 32 bit application (omreport - from Dell Open Manage suite) with a 64 bit OS. The fix is already available upstream, with this commit: commit b3dc1a212e5167984616445990c76056034f8eeb Author: Tomas Henzl Date: Thu Feb 11 18:01:50 2010 +0100 [SCSI] megaraid_sas: fix for 32bit apps Is it possible to backport the patch to Debian kernel? -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: Dell Inc. product_name: PowerEdge 2900 product_version: chassis_vendor: Dell Inc. chassis_version: bios_vendor: Dell Inc. bios_version: 2.5.0 board_vendor: Dell Inc. board_name: 0YM158 board_version: A02 ** PCI devices: [cut - not really relevant] 02:0e.0 RAID bus controller [0104]: Dell PowerEdge Expandable RAID controller 5 [1028:0015] Subsystem: Dell PERC 5/i Integrated RAID Controller [1028:1f03] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr+ Stepping+ SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: megaraid_sas Kernel modules: megaraid_sas ** USB devices: Bus 003 Device 002: ID 0624:0294 Avocent Corp. Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 003: ID 04b4:6560 Cypress Semiconductor Corp. CY7C65640 USB-2.0 "TetraHub" Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub -- System Information: Debian Release: 5.0.4 APT prefers stable APT policy: (990, 'stable'), (500, 'oldstable'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-3-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/bash Versions of packages linux-image-2.6.32-3-amd64 depends on: ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy ii initramfs-tools [linux-initra 0.92o tools for generating an initramfs ii module-init-tools 3.4-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.32-3-amd64 recommends: ii firmware-linux-free 2.6.32-10 Binary firmware for various driver Versions of packages linux-image-2.6.32-3-amd64 suggests: ii grub 0.97-47lenny2 GRand Unified Bootloader (Legacy v pn linux-doc-2.6.32 (no description available) Versions of packages linux-image-2.6.32-3-amd64 is related to: ii firmware-bnx2 0.23 Binary firmware for Broadcom NetXt pn firmware-bnx2x (no description available) pn firmware-ipw2x00 (no description available) pn firmware-ivtv (no description available) pn firmware-iwlwifi (no description available) pn firmware-linux (no description available) ii firmware-linux-nonfree0.23 Binary firmware for various driver pn firmware-qlogic(no description available) pn firmware-ralink(no description available) -- debconf information excluded -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100419152347.31639.40892.report...@serverbio.elet.polimi.it
Bug#518812: I/O errors with 3w-xxxx and 8Gb ram
* Moritz Muehlenhoff [2010 02 23, 19:45]: > The next release of Debian (6.0, code name Squeeze) will be based > on 2.6.32. Please test the current 2.6.32 from unstable/testing and tell > us whether the problem persists. If so, we should report it upstream > to the kernel.org developers. Hello, I tested the 2.6.32 kernel from unstable as suggested, while at the moment I am running linux-image-2.6.32-bpo.3-amd64 from backports: both kernels work fine, even if the device driver version shown by dmesg is still 1.26.02.002. Best regards -- Gpg key fingerprint = CC24 F753 5198 857F 8A68 749B BC94 DD24 FFBF 6A0A -- 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/20100419141544.ga6...@discovery
Re: [LCFC] templates://linux-2.6/{linux-base.templates,templates/temp.image.plain/templates}
On Mon, Apr 19, 2010 at 07:16:05AM +0200, Christian PERRIER wrote: > Quoting Christian PERRIER (bubu...@debian.org): > > > From what you write, it seems that we then need to add something to > > say more firmly that users *really* should let this action be perfomed > > or be prepared to have serious trouble at next reboot. > > > > Something like: > > > > The new Linux kernel version provides different drivers for some > > PATA (IDE) controllers. The names of some hard disk, CD-ROM, and > > tape devices may change. > > . > > It is now recommended to identify disk devices in configuration files > > by label or UUID (unique identifier) rather than by device name, > > which will work with both old and new kernel versions. > > . > > If you choose to not update the system configuration automatically, > > you must update device IDs yourself before the next system reboot > > or the system may become unbootable. > > > As I got no further comment, this is what will now go in the bug > report I'll send in a few seconds. > > In case someone want to comment, I suggest commenting in the bug > report itself now. Please note that I intend to jump into a formal > call for translations in 2 days, so comments need to come soon as, > once the call is sent, changing the phrasing of what's being > translated becomes much more complicated. thanks for the added explanation, very fine with me. -- 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/20100419140328.go10...@baikonur.stro.at
Bug#578272: linux-image-2.6.32-3-686: Enabling Host Protected Area leads to LVM failure
On Mon, Apr 19, 2010 at 12:02:54AM +0100, Ben Hutchings wrote: > On Sun, 2010-04-18 at 22:10 +0200, Michael Banck wrote: > > Hi, > > > > On Sun, Apr 18, 2010 at 05:37:58PM +0100, Ben Hutchings wrote: > > > On Sun, 2010-04-18 at 16:17 +0200, Michael Banck wrote: > > > > Package: linux-2.6 > > > > Version: 2.6.32-9 > > > > Severity: normal > > > > > > > > Hi, > > > > > > > > Going from 2.6.30 to 2.6.32, I can no longer mount my LVM-based > > > > partition on my secondary harddisk, I get the following error when I try > > > > to run e.g. vgchange: > > > > > > > > nighthawk~$ LANG=C sudo vgchange -a y > > > > 2 logical volume(s) in volume group "nighthawk" now active > > > > device-mapper: resume ioctl failed: Invalid argument > > > > Unable to resume data-data (254:3) > > > > 1 logical volume(s) in volume group "data" now active > > > > nighthawk~$ sudo mount /dev/mapper/data-data /mnt > > > > mount: /dev/mapper/data-data already mounted or /mnt busy > > > > > > > > This is the corresponding kernel error in syslog: > > > > > > > > Apr 18 15:17:02 nighthawk kernel: [ 20.713326] device-mapper: table: > > > > 254:3: hdc too small for target: start=384, len=78135296, > > > > dev_size=71762930 > > > > > > > > It turns out this is because contrary to linux-image-2.6.30-2-686, > > > > 2.6.32 does not disable HPA: > > > [...] > > > > > > Is there a partition table on /dev/hdc? > > > > No, it seems to be a direct LVM image/partition which spans the whole > > disk. > > Then I don't know why the HPA was disabled previously. It should not be > disabled by default as some BIOSes will overwrite data in the HPA in > some circumstances (possibly only on matched HDs). There is a > workaround for cases where an HD was partitioned while the HPA was > disabled: if a partition is found to extend into the HPA then it will > automatically be disabled. > > You should be able to disable the HPA for this disk by following these > steps: > > 1. Create a file under /etc/modprobe.d containing the lines: >options ide_core nohpa=1.0 >options libata ignore_hpa=1 > 2. Run 'update-initramfs -u -k 2.6.32-3-686' > 3. Reboot Thanks, that has worked fine. I guess it was my fault to create the PV without caring about the partitioning, but this was a standard ThinkPad harddisk I wanted to put into use as a secondary harddrive and which I just ran lvm2 on - I didn't expect HPA to intefere (nor did I know what it was). Michael -- 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/20100419135032.ga5...@nighthawk.chemicalconnection.dyndns.org
Bug#572084: marked as done (linux-image-2.6.32-2-orion5x: NFS kernel daemon support disabled?)
Your message dated Mon, 19 Apr 2010 14:02:28 +
with message-id
and subject line Bug#550153: fixed in nfs-utils 1:1.1.2-6lenny2
has caused the Debian Bug report #550153,
regarding linux-image-2.6.32-2-orion5x: NFS kernel daemon support disabled?
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.)
--
550153: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=550153
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-2.6
Version: 2.6.32-8
Severity: normal
After upgrading its kernel from 2.6.30-2-orion5x to 2.6.32-2-orion5x, I
cannot mount NFS v4 filesystems exported by my QNAP-409. When attempting
to restart nfs-kernel-server, I get the warning "Not starting NFS kernel
daemon: no support in current kernel. (warning)."
Looking at /boot/config-2.6.3{0,2}-2-orion5x, I notice that there are no
differences in the NFS defines, so the issue may be elsewhere:
$ diff config-2.6.30-2-orion5x config-2.6.32-2-orion5x | grep NFS
> # CONFIG_NFS_V4_1 is not set
Best regards,
Marco
-- Package-specific info:
** Version:
Linux version 2.6.32-2-orion5x (Debian 2.6.32-8) (b...@decadent.org.uk) (gcc
version 4.3.4 (Debian 4.3.4-6) ) #1 Fri Feb 12 18:12:26 UTC 2010
** Command line:
console=ttyS0,115200n8 root=/dev/ram rw initrd=0x80,0x3f
** Not tainted
** Kernel log:
[ 15.807260] disk 1, o:1, dev:sdb4
[ 15.810657] disk 2, o:1, dev:sdc4
[ 15.814053] disk 3, o:1, dev:sdd4
[ 15.817761] md3: detected capacity change from 0 to 2968503189504
[ 15.827266] md3: unknown partition table
[ 16.200899] device-mapper: uevent: version 1.0.3
[ 16.213670] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised:
dm-de...@redhat.com
[ 16.734575] kjournald starting. Commit interval 5 seconds
[ 16.776991] EXT3 FS on md1, internal journal
[ 16.781283] EXT3-fs: mounted filesystem with ordered data mode.
[ 19.760494] udevd version 125 started
[ 28.303276] input: gpio-keys as /devices/platform/gpio-keys/input/input0
[ 28.440151] MV-643xx 10/100/1000 ethernet driver version 1.4
[ 28.452110] mv643xx_eth smi: probed
[ 28.517926] net eth0: port 0 with MAC address 00:08:9b:ad:18:00
[ 28.780462] usbcore: registered new interface driver usbfs
[ 28.824341] usbcore: registered new interface driver hub
[ 28.856461] usbcore: registered new device driver usb
[ 28.977325] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 28.983933] orion-ehci orion-ehci.0: Marvell Orion EHCI
[ 29.013854] orion-ehci orion-ehci.0: new USB bus registered, assigned bus
number 1
[ 29.066231] orion-ehci orion-ehci.0: irq 17, io mem 0xf105
[ 29.086167] orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
[ 29.092196] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 29.099128] usb usb1: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 29.106365] usb usb1: Product: Marvell Orion EHCI
[ 29.111066] usb usb1: Manufacturer: Linux 2.6.32-2-orion5x ehci_hcd
[ 29.117347] usb usb1: SerialNumber: orion-ehci.0
[ 29.197741] usb usb1: configuration #1 chosen from 1 choice
[ 29.225771] hub 1-0:1.0: USB hub found
[ 29.229664] hub 1-0:1.0: 1 port detected
[ 29.546139] usb 1-1: new high speed USB device using orion-ehci and address 2
[ 29.717864] usb 1-1: New USB device found, idVendor=05e3, idProduct=0607
[ 29.724560] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 29.731729] usb 1-1: Product: USB2.0 Hub
[ 29.796155] usb 1-1: configuration #1 chosen from 1 choice
[ 29.828269] hub 1-1:1.0: USB hub found
[ 29.856115] hub 1-1:1.0: 4 ports detected
[ 30.146656] usb 1-1.2: new low speed USB device using orion-ehci and address
3
[ 30.370289] usb 1-1.2: New USB device found, idVendor=051d, idProduct=0002
[ 30.377206] usb 1-1.2: New USB device strings: Mfr=3, Product=1,
SerialNumber=2
[ 30.384498] usb 1-1.2: Product: Back-UPS CS 500 FW:808.q8.I USB FW:q8
[ 30.391003] usb 1-1.2: Manufacturer: American Power Conversion
[ 30.396852] usb 1-1.2: SerialNumber: 4B0827P61177
[ 30.504601] usb 1-1.2: configuration #1 chosen from 1 choice
[ 31.872575] usbcore: registered new interface driver hiddev
[ 33.480348] generic-usb 0003:051D:0002.0001: hiddev0,hidraw0: USB HID v1.10
Device [American Power Conversion Back-UPS CS 500 FW:808.q8.I USB FW:q8] on
usb-orion-ehci.0-1.2/input0
[ 33.500871] usbcore: registered new interface driver usbhid
[ 33.512864] usbhid: v2.6:USB HID core driver
[ 35.064935] Adding 489848k swap on /dev/md2. Priority:-1 extents:1
across:489848k
[ 35.836959] EXT3 FS on md1, internal j
Bug#554508: marked as done (nfs-kernel-server: init script incompatible with kernel 2.6.32)
Your message dated Mon, 19 Apr 2010 14:02:28 + with message-id and subject line Bug#550153: fixed in nfs-utils 1:1.1.2-6lenny2 has caused the Debian Bug report #550153, regarding nfs-kernel-server: init script incompatible with kernel 2.6.32 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.) -- 550153: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=550153 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nfs-kernel-server Version: 1:1.2.0-4 Severity: important /etc/init.d/nfs-kernel-server currently includes the following test: if [ -f /proc/kallsyms ] && ! grep -qE 'init_nf(sd|)' /proc/kallsyms; then log_warning_msg "Not starting $DESC: no support in current kernel." exit 0 fi But with that test it fails to start with kernel 2.6.32-rc6, even though nfs (both v3 and v4) support is available: Starting NFS common utilities: idmapd. Not starting NFS kernel daemon: no support in current kernel. ... (warning). If I just comment out the test, nfs-kernel-server starts without any problems and clients can connect. A grep on /proc/kallsyms shows that apparently the init_nfsd symbols have been dropped. Not sure what other symbol is most suitable to replace the current test. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: armel (armv5tel) Kernel: Linux 2.6.32-rc6 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nfs-kernel-server depends on: ii libblkid12.16.1-4block device id library ii libc62.10.1-3GNU C Library: Shared libraries ii libcomerr2 1.41.9-1common error description library ii libgssapi-krb5-2 1.7dfsg~beta3-1 MIT Kerberos runtime libraries - k ii libgssglue1 0.1-4 mechanism-switch gssapi library ii libk5crypto3 1.7dfsg~beta3-1 MIT Kerberos runtime libraries - C ii libkrb5-31.7dfsg~beta3-1 MIT Kerberos runtime libraries ii libnfsidmap2 0.22-2 An nfs idmapping library ii librpcsecgss30.19-2 allows secure rpc communication us ii libwrap0 7.6.q-18Wietse Venema's TCP wrappers libra ii lsb-base 3.2-23 Linux Standard Base 3.2 init scrip ii nfs-common 1:1.2.0-4 NFS support files common to client ii ucf 3.0024 Update Configuration File: preserv nfs-kernel-server recommends no packages. nfs-kernel-server suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: nfs-utils Source-Version: 1:1.1.2-6lenny2 We believe that the bug you reported is fixed in the latest version of nfs-utils, which is due to be installed in the Debian FTP archive: nfs-common_1.1.2-6lenny2_i386.deb to main/n/nfs-utils/nfs-common_1.1.2-6lenny2_i386.deb nfs-kernel-server_1.1.2-6lenny2_i386.deb to main/n/nfs-utils/nfs-kernel-server_1.1.2-6lenny2_i386.deb nfs-utils_1.1.2-6lenny2.diff.gz to main/n/nfs-utils/nfs-utils_1.1.2-6lenny2.diff.gz nfs-utils_1.1.2-6lenny2.dsc to main/n/nfs-utils/nfs-utils_1.1.2-6lenny2.dsc 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 550...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings (supplier of updated nfs-utils package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 18 Apr 2010 12:31:00 +0100 Source: nfs-utils Binary: nfs-kernel-server nfs-common Architecture: i386 source Version: 1:1.1.2-6lenny2 Distribution: stable Urgency: low Maintainer: Debian kernel team Changed-By: Ben Hutchings Closes: 550153 Description: nfs-common - NFS support files common to client and server nfs-kernel-server - support for NFS kernel server Changes: nfs-utils (1:1.1.2-6lenny2) stable; urgency=low . * Update maintainers and uploaders to match unstable * Fix test for NFS kernel server support in init script (Closes: #550153) Checksums-Sha1: 8c8115dce254ebe2e26dfb4ec4b2ded70697d0af 1978 nfs-utils_1.1.2-6lenny2.dsc 81c337cf260bca1e1f0589d5b2392
Bug#550153: marked as done (/proc/kallsyms does not contain init_nfsd on 2.6.32-rc3)
Your message dated Mon, 19 Apr 2010 14:02:28 + with message-id and subject line Bug#550153: fixed in nfs-utils 1:1.1.2-6lenny2 has caused the Debian Bug report #550153, regarding /proc/kallsyms does not contain init_nfsd on 2.6.32-rc3 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.) -- 550153: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=550153 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nfs-kernel-server Version: 1:1.2.0-4 Hello, nfs-kernel-server startup script fails to start on my 2.6.32-rc3 with modular nfsd, saying that kernel does not support nfsd: petr-dev3:/usr/src/git/linux-2.6/fs/nfsd# /etc/init.d/nfs-kernel-server start Not starting NFS kernel daemon: no support in current kernel. ... (warning). Apparently init method is no longer listed with its name in exported symbols, most probably due to symbols in __init section being dropped. petr-dev3:/usr/src/git/linux-2.6/fs/nfsd# grep nfsd /proc/kallsyms | grep init a0382400 t svc_export_init [nfsd] a0383d60 t expkey_init [nfsd] a03aac38 b nfs4_init[nfsd] a039d4d0 t ent_init [nfsd] a039f1d0 t init_state [nfsd] a03bb1f0 b rec_dir_init [nfsd] a039e610 t nfsd_idmap_init [nfsd] a03871a0 t nfsd_stat_init [nfsd] a0386080 t nfsd_reply_cache_init[nfsd] a03991b0 t nfs4_state_init [nfsd] a0384760 t nfsd_export_init [nfsd] a037e520 t nfsd_racache_init[nfsd] a0385950 t nfsd_lockd_init [nfsd] a03a0560 t nfsd4_init_recdir[nfsd] Testing presence of /proc/fs/nfs/exports seems to work on that kernel - though I have no idea how far back (and into the future) that works... # See if our running kernel supports the NFS kernel server if [ ! -f /proc/fs/nfs/exports ]; then log_warning_msg "Not starting $DESC: no support in current kernel." exit 0 fi Thanks, Petr Vandrovec --- End Message --- --- Begin Message --- Source: nfs-utils Source-Version: 1:1.1.2-6lenny2 We believe that the bug you reported is fixed in the latest version of nfs-utils, which is due to be installed in the Debian FTP archive: nfs-common_1.1.2-6lenny2_i386.deb to main/n/nfs-utils/nfs-common_1.1.2-6lenny2_i386.deb nfs-kernel-server_1.1.2-6lenny2_i386.deb to main/n/nfs-utils/nfs-kernel-server_1.1.2-6lenny2_i386.deb nfs-utils_1.1.2-6lenny2.diff.gz to main/n/nfs-utils/nfs-utils_1.1.2-6lenny2.diff.gz nfs-utils_1.1.2-6lenny2.dsc to main/n/nfs-utils/nfs-utils_1.1.2-6lenny2.dsc 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 550...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings (supplier of updated nfs-utils package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 18 Apr 2010 12:31:00 +0100 Source: nfs-utils Binary: nfs-kernel-server nfs-common Architecture: i386 source Version: 1:1.1.2-6lenny2 Distribution: stable Urgency: low Maintainer: Debian kernel team Changed-By: Ben Hutchings Closes: 550153 Description: nfs-common - NFS support files common to client and server nfs-kernel-server - support for NFS kernel server Changes: nfs-utils (1:1.1.2-6lenny2) stable; urgency=low . * Update maintainers and uploaders to match unstable * Fix test for NFS kernel server support in init script (Closes: #550153) Checksums-Sha1: 8c8115dce254ebe2e26dfb4ec4b2ded70697d0af 1978 nfs-utils_1.1.2-6lenny2.dsc 81c337cf260bca1e1f0589d5b239216ed59e8cef 35554 nfs-utils_1.1.2-6lenny2.diff.gz 2bf046150c80c227d9c4425546b02999f62d8f25 150086 nfs-kernel-server_1.1.2-6lenny2_i386.deb eda8a122b2823d4f0cde34e264648a35378d128d 189552 nfs-common_1.1.2-6lenny2_i386.deb Checksums-Sha256: f963540c014fc6e1531f6c9c5960dd4ed8258ac5b2d389090582c9b91c647517 1978 nfs-utils_1.1.2-6lenny2.dsc ec4025fb60f145c1b8f57771cedb40b8c3810193f284dbaba7f3cc7a87e935f6 35554 nfs-utils_1.1.2-6lenny2.diff.gz 61a333cd3a33bb76dbbd6b53a9af26d8c9000539272cc3d88d7111b3915924e1 150086 nfs-kernel-server_1.1.2-6lenny2_i386.deb 1d17ce33dcac6cc8298de1aad55e3967ab10531a5ebf948f745f8
nfs-utils_1.1.2-6lenny2_multi.changes ACCEPTED
Notes: Mapping stable to proposed-updates. Accepted: nfs-common_1.1.2-6lenny2_i386.deb to main/n/nfs-utils/nfs-common_1.1.2-6lenny2_i386.deb nfs-kernel-server_1.1.2-6lenny2_i386.deb to main/n/nfs-utils/nfs-kernel-server_1.1.2-6lenny2_i386.deb nfs-utils_1.1.2-6lenny2.diff.gz to main/n/nfs-utils/nfs-utils_1.1.2-6lenny2.diff.gz nfs-utils_1.1.2-6lenny2.dsc to main/n/nfs-utils/nfs-utils_1.1.2-6lenny2.dsc Override entries for your package: nfs-common_1.1.2-6lenny2_i386.deb - standard net nfs-kernel-server_1.1.2-6lenny2_i386.deb - optional net nfs-utils_1.1.2-6lenny2.dsc - source net Announcing to debian-chan...@lists.debian.org Closing bugs: 550153 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/e1o3rys-0004ca...@ries.debian.org
Bug#577747: linux-image-2.6.32-4-686: corrupted SSH connection little time after boot with the atl1e driver on a Eeepc 1002HA
Hello Ben, Le Sat, 17 Apr 2010 16:24:00 +0100, Ben Hutchings a écrit : > OK, I think I can generally trust bnx2. > > As I understand it, you are doing this: > 1. Run ssh on Eeepc, connecting to server > 2. Run iceweasel on server with X forwarding over ssh > 3. ssh on Eeepc fails with this error message, indicating it received > corrupt data Yes, it's what I do. > If we can trust the server's driver and hardware, this implies that a > received packet has been corrupted after its CRC and TCP/IP checksums > were verified by the Eeepc's network controller. > > Based on the bug reports at bugzilla.kernel.org I believe this is a > hardware fault and there is unlikely to be any way to fix this in > software. However you may be able to work around it by disabling RX > checksum offload via ethtool. I thought it could be a driver problem, perhaps a faulty initialization or something related… People using also Windows often say they don't have problem with same hardware on this system (I don't use it). I'll try to test your suggestion with ethtool, thanks for the tip. Fred. -- 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/20100419141646.38837...@prem6s
Bug#578349: linux-2.6: [debconf_rewrite] Debconf templates and debian/control review
Package: linux-2.6
Version: N/A
Severity: normal
Tags: patch
Dear Debian maintainer,
On Monday, April 19, 2010, I notified you of the beginning of a review process
concerning debconf templates for linux-2.6.
The debian-l10n-english contributors have now reviewed these templates,
and the proposed changes are attached to this bug report.
Please review the suggested changes, and if you have any
objections, let me know in the next 3 days.
However, please try to avoid uploading linux-2.6 with these changes
right now.
The second phase of this process will begin on Thursday, April 22, 2010, when I
will
coordinate updates to translations of debconf templates.
The existing translators will be notified of the changes: they will
receive an updated PO file for their language.
Simultaneously, a general call for new translations will be sent to
the debian-i18n mailing list.
Both these calls for translations will request updates to be sent as
individual bug reports. That will probably trigger a lot of bug
reports against your package, but these should be easier to deal with.
The call for translation updates and new translations will run until
about Thursday, May 13, 2010. Please avoid uploading a package with fixed or
changed
debconf templates and/or translation updates in the meantime. Of
course, other changes are safe.
Please note that this is an approximative delay, which depends on my
own availability to process this work and is influenced by the fact
that I simultaneously work on many packages.
Around Friday, May 14, 2010, I will contact you again and will send a final
patch
summarizing all the updates (changes to debconf templates,
updates to debconf translations and new debconf translations).
Again, thanks for your attention and cooperation.
--- linux-2.6.old/debian/linux-base.templates 2010-03-31 07:33:05.952958142
+0200
+++ linux-2.6/debian/linux-base.templates 2010-04-19 07:12:17.707893653
+0200
@@ -1,20 +1,34 @@
+# These templates have been reviewed by the debian-l10n-english
+# team
+#
+# If modifications/additions/rewording are needed, please ask
+# debian-l10n-engl...@lists.debian.org for advice.
+#
+# Even minor modifications require translation updates and such
+# changes should be coordinated with translators and reviewers.
+
Template: linux-base/disk-id-convert-auto
Type: boolean
Default: true
-_Description: Update disk device ids in system configuration?
- The new Linux kernel version provides different drivers for some
- PATA (IDE) controllers. The names of some hard disk, CD-ROM and
- tape devices may change.
+_Description: Update disk device IDs in system configuration?
+
+ The new Linux kernel version provides different drivers for some PATA
+ (IDE) controllers. The names of some hard disk, CD-ROM, and tape
+ devices may change.
.
- You are recommended to identify disk devices in configuration files
+ It is now recommended to identify disk devices in configuration files
by label or UUID (unique identifier) rather than by device name,
- which will work with both old and new kernel versions. Your system
- configuration can be updated automatically in most cases.
+ which will work with both old and new kernel versions.
+ .
+ If you choose to not update the system configuration automatically,
+ you must update device IDs yourself before the next system reboot or
+ the system may become unbootable.
Template: linux-base/disk-id-convert-plan
Type: boolean
Default: true
-_Description: Apply these configuration changes to disk device ids?
+#flag:translate!:3,5,7
+_Description: Apply configuration changes to disk device IDs?
These devices will be assigned UUIDs or labels:
.
${relabel}
@@ -23,38 +37,41 @@
.
${files}
.
- The device ids will be changed as follows:
+ The device IDs will be changed as follows:
.
${id_map}
Template: linux-base/disk-id-convert-plan-no-relabel
Type: boolean
Default: true
-_Description: Apply these configuration changes to disk device ids?
+#flag:translate!:3,5
+_Description: Apply configuration changes to disk device IDs?
These configuration files will be updated:
.
${files}
.
- The device ids will be changed as follows:
+ The device IDs will be changed as follows:
.
${id_map}
Template: linux-base/disk-id-manual
-Type: note
-_Description: Please check these configuration files before rebooting
- These configuration files still use some device names that may
+Type: error
+#flag:translate!:3
+_Description: Configuration files still contain deprecated device names
+ The following configuration files still use some device names that may
change when using the new kernel:
.
${unconverted}
Template: linux-base/disk-id-manual-boot-loader
-Type: note
-_Description: Check the boot loader configuration before rebooting
- The boot loader configuration for this system was not recognised. These
+Type: error
+_Description: Boot loader configuration check needed
+ The boot loader configuration for this system
