Bug#696406: IP_MTU socket option value doesn't restored after 10 minutes.
Package: src:linux Version: 3.2.35-2 Severity: normal IP_MTU socket option is not updated after 10 minutes of waiting for SOCK_STREAM sockets when the value of socket option IP_MTU_DISCOVER is IP_PMTUDISC_DO or IP_PMTUDISC_WANT. This can be reproduced with 3 hosts configuration. Let it be the hosts: host_A, host_B and host _C. host_A via interface eth1 connected with host_B via intefaces eth1. Let host_C via interface eth1 connected with host_B via interface eth2. Also Lets address 10.0.1.1/24 is assigned to eth1 on host_A; 10.0.1.2/24 is assigned to eth1 on host_B; 10.0.2.1/24 is assigned to eth2 on host_B; 10.0.2.2/24 is assigned to eth1 on host_C. Also there are two routes: 10.0.2.2 via 10.0.1.2 dev eth1 on host_A and 10.0.1.1 via 10.0.2.1 dev eth1 on host_C. Also forwarding is on on host_B. So we have the following picture: host_A-eth1(10.0.1.1)--(10.0.1.2)eth1-host_B-eth2(10.0.2.1)--(10.0.2.2)eth1-host_C MTU is equal to 1500 on all involved interfaces. Then we make the followign steps: on host_A: 1. socket(SOCK_STREAM) - 6 2. bind(6, 10.0.1.1:25630) - 0 3. listen(6, 1) - 0 on host_C: 4. socket(SOCK_STREAM) - 5 5. bind(5, 10.0.2.2:25631) - 0 6. connect(5, 10.0.1.1:25630) - 0 on host_A: 7. accept(6) - 7 8. close(6) - 0 9. getsockopt(7,IP_MTU) - 0 // Returns that MTU is 1500 10. getsockopt(7,IP_MTU_DISCOVER) - 0 // Returns that default value is IP_PMTUDISC_WANT On eth2 on host_B and on eth1 on host_C change MTU from 1500 to 750. Wait for a while. 11. send(7, lenght=1400) - 1400 On host_C: 12. recv(6) - 1400 On host_A 13. sleep(5); 14. getsockopt(7,IP_MTU) - 0 // Returns that MTU is 750 On eth2 on host_B and on eth1 on host_C change MTU from 750 to 1500. Wait for a while. Repeat the steps 15-18 for 20 minutes: On host_A: 15. send(7, lenght=650) - 650 On host_C: 16. recv(6) - 650 On host_A: 17. sleep(60) 18. getsockopt(7,IP_MTU) - 0 // Always returns that MTU is 750 So the value of IP_MTU socket option is not restored to 1500 even after 20 minutes. There is the same picture if IP_MTU_DISCOVER is set to IP_PMTUDISC_DO at step 10. -- Package-specific info: ** Version: Linux version 3.2.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.35-2 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-amd64 root=UUID=204ee0f7-e3ae-4285-a32d-58d583dca0e9 ro console=tty1 console=ttyS2,115200n8 nomodeset intel_iommu=on ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [ 50.943835] sfc :02:00.1: eth2: initialising TX queue 4 [ 50.943837] sfc :02:00.1: eth2: mapping special buffer 22 at fffde000 [ 50.943840] sfc :02:00.1: eth2: mapping special buffer 23 at fffdf000 [ 50.943843] sfc :02:00.1: eth2: initialising TX queue 5 [ 50.943846] sfc :02:00.1: eth2: mapping special buffer 24 at fffdc000 [ 50.943848] sfc :02:00.1: eth2: mapping special buffer 25 at fffdd000 [ 50.943851] sfc :02:00.1: eth2: initialising RX queue 2 [ 50.943854] sfc :02:00.1: eth2: RX queue 2 ring in special buffers 26-27 [ 50.943857] sfc :02:00.1: eth2: mapping special buffer 26 at fffda000 [ 50.943859] sfc :02:00.1: eth2: mapping special buffer 27 at fffdb000 [ 50.943862] sfc :02:00.1: eth2: initialising TX queue 6 [ 50.943865] sfc :02:00.1: eth2: mapping special buffer 8 at fffee000 [ 50.943868] sfc :02:00.1: eth2: mapping special buffer 9 at fffef000 [ 50.943871] sfc :02:00.1: eth2: initialising TX queue 7 [ 50.943873] sfc :02:00.1: eth2: mapping special buffer 10 at fffec000 [ 50.943876] sfc :02:00.1: eth2: mapping special buffer 11 at fffed000 [ 50.943879] sfc :02:00.1: eth2: initialising RX queue 3 [ 50.943882] sfc :02:00.1: eth2: RX queue 3 ring in special buffers 12-13 [ 50.943884] sfc :02:00.1: eth2: mapping special buffer 12 at fffea000 [ 50.943887] sfc :02:00.1: eth2: mapping special buffer 13 at fffeb000 [ 51.911402] sfc :02:00.0: eth1: channel 0 triggered interrupt on CPU 0 [ 51.911407] sfc :02:00.0: eth1: channel 1 triggered interrupt on CPU 1 [ 51.911410] sfc :02:00.0: eth1: channel 2 triggered interrupt on CPU 2 [ 51.911412] sfc :02:00.0: eth1: channel 3 triggered interrupt on CPU 3 [ 51.939376] sfc :02:00.1: eth2: channel 0 triggered interrupt on CPU 0 [ 51.939381] sfc :02:00.1: eth2: channel 1 triggered interrupt on CPU 1 [ 51.939384] sfc :02:00.1: eth2: channel 2 triggered interrupt on CPU 2 [ 51.939387] sfc :02:00.1: eth2: channel 3 triggered interrupt on CPU 3 [ 60.934649] eth1: no IPv6 routers present [ 61.83] eth2: no IPv6 routers present [ 1280.130227] sfc :02:00.1: eth2: closing on CPU 0 [ 1280.130302] sfc :02:00.1: eth2: stop port [ 1280.130470] sfc :02:00.1: eth2: successfully flushed all queues [ 1280.130475] sfc :02:00.1: eth2: chan 0 stop event queue [ 1280.130478] sfc :02:00.1: eth2: chan 0 start event queue [ 1280.130481] sfc
Linux 3.2: backports some features from mainline kernel (3.7)?
Hi, I already asked this question on debian-security@ mailing list, but Mr Cyril Brulebois suggested, that a better place to ask this question is a debian-kernel@ mailing list. It is pretty the same question - just copied. Kernel 3.7 is officially out. This Linux release includes many improvements practically in every aspect. Many changes also concerns security. Very interesting are: Cryptographically-signed kernel modules and - long awaited - symlink and hardlink restrictions (already in Linux 3.6), but it broke some programs, so it has been disabled by default, right? Those features/changes are very interesting from security point of view. With signed kernel modules, various distributions can lock down their kernels. symlink and hardlink are just a long-standing, much needed class of security. I would like to ask, if some of 3.7 kernel features (such as those mentioned) will be backported to Testing kernel (3.2)? I know Wheezy has now been frozen and in consequences this means that no more new features will be added etc. But there is still some time to official release and those features, could be tested very well. Are there any plans to do this? Best regards!
[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 #627372 (http://bugs.debian.org/627372) # Bug title: linux-image-2.6.38-2-686: Console turns black during boot # * https://bugs.freedesktop.org/show_bug.cgi?id=44156 # * remote status changed: NEEDINFO - NEW usertags 627372 - status-NEEDINFO usertags 627372 + status-NEW # remote status report for #627372 (http://bugs.debian.org/627372) # Bug title: linux-image-2.6.38-2-686: Console turns black during boot # * https://bugs.freedesktop.org/show_bug.cgi?id=44156 # * remote status changed: NEEDINFO - NEW usertags 627372 - status-NEEDINFO usertags 627372 + status-NEW 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/20121220164756.22107.71571.btsl...@sonntag.debian.org
Bug#677472: [3.1-3.2 regression] Immediate wake on suspend, associated with OHCI on MCP51
Am 19.12.2012 20:35, schrieb Alan Stern: On Wed, 19 Dec 2012, [ISO-8859-1] Frank Sch�fer wrote: I can confirm that MCP55 has this bug and it should be safe to add MCP65-78S, too, because MCP79 still has the bug. By the way, you mentioned that runtime suspend seemed to work okay, right? It might be worthwhile testing this again, just to be certain. In particular, I'd like to see what lspci -vv shows for the controller while it is runtime suspended with a device attached. As far as the OHCI hardware is concerned, there shouldn't be any difference between runtime suspend and system suspend. This strongly suggests that the bug doesn't lie in the controller itself but in the firmware (BIOS or ACPI). Alan Stern Yes runtime suspend works (tested with a mouse) and lspci -vv doesn't change. With /sys/devices/pci:00/:00:02.0/usb2/2-9/power: control = on runtime_status = active 00:02.0 USB controller: NVIDIA Corporation MCP61 USB 1.1 Controller (rev a2) (prog-if 10 [OHCI]) Subsystem: ASUSTeK Computer Inc. Device 8234 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 (750ns min, 250ns max) Interrupt: pin A routed to IRQ 23 Region 0: Memory at fe02f000 (32-bit, non-prefetchable) [size=4K] Capabilities: [44] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: ohci_hcd = set control to 'auto' runtime_status = active 00:02.0 USB controller: NVIDIA Corporation MCP61 USB 1.1 Controller (rev a2) (prog-if 10 [OHCI]) Subsystem: ASUSTeK Computer Inc. Device 8234 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 (750ns min, 250ns max) Interrupt: pin A routed to IRQ 23 Region 0: Memory at fe02f000 (32-bit, non-prefetchable) [size=4K] Capabilities: [44] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: ohci_hcd = after ~2s the device suspends runtime_status = suspended 00:02.0 USB controller: NVIDIA Corporation MCP61 USB 1.1 Controller (rev a2) (prog-if 10 [OHCI]) Subsystem: ASUSTeK Computer Inc. Device 8234 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 (750ns min, 250ns max) Interrupt: pin A routed to IRQ 23 Region 0: Memory at fe02f000 (32-bit, non-prefetchable) [size=4K] Capabilities: [44] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: ohci_hcd -- 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/50d34c2d.2010...@googlemail.com
Re: Linux 3.2: backports some features from mainline kernel (3.7)?
On Thu, Dec 20, 2012 at 03:46:14PM +0100, daniel curtis wrote: Hi, I already asked this question on debian-security@ mailing list, but Mr Cyril Brulebois suggested, that a better place to ask this question is a debian-kernel@ mailing list. It is pretty the same question - just copied. Kernel 3.7 is officially out. This Linux release includes many improvements practically in every aspect. Many changes also concerns security. Very interesting are: Cryptographically-signed kernel modules This seems to be too big a change to make now. And there is already 'sysctl kernel.modules_disabled=1'. That provides the same or greater security, though it is not as convenient (you have to load all the modules you may need first). and - long awaited - symlink and hardlink restrictions (already in Linux 3.6), but it broke some programs, so it has been disabled by default, right? [...] Already backported and enabled by default in the Debian package. Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121220175906.gq13...@decadent.org.uk
Bug#677472: [3.1-3.2 regression] Immediate wake on suspend, associated with OHCI on MCP51
Am 20.12.2012 18:34, schrieb Frank Schäfer: Am 19.12.2012 20:35, schrieb Alan Stern: On Wed, 19 Dec 2012, [ISO-8859-1] Frank Sch�fer wrote: I can confirm that MCP55 has this bug and it should be safe to add MCP65-78S, too, because MCP79 still has the bug. By the way, you mentioned that runtime suspend seemed to work okay, right? It might be worthwhile testing this again, just to be certain. In particular, I'd like to see what lspci -vv shows for the controller while it is runtime suspended with a device attached. As far as the OHCI hardware is concerned, there shouldn't be any difference between runtime suspend and system suspend. This strongly suggests that the bug doesn't lie in the controller itself but in the firmware (BIOS or ACPI). Alan Stern Yes runtime suspend works (tested with a mouse) and lspci -vv doesn't change. With /sys/devices/pci:00/:00:02.0/usb2/2-9/power: control = on runtime_status = active 00:02.0 USB controller: NVIDIA Corporation MCP61 USB 1.1 Controller (rev a2) (prog-if 10 [OHCI]) Subsystem: ASUSTeK Computer Inc. Device 8234 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 (750ns min, 250ns max) Interrupt: pin A routed to IRQ 23 Region 0: Memory at fe02f000 (32-bit, non-prefetchable) [size=4K] Capabilities: [44] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: ohci_hcd = set control to 'auto' runtime_status = active 00:02.0 USB controller: NVIDIA Corporation MCP61 USB 1.1 Controller (rev a2) (prog-if 10 [OHCI]) Subsystem: ASUSTeK Computer Inc. Device 8234 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 (750ns min, 250ns max) Interrupt: pin A routed to IRQ 23 Region 0: Memory at fe02f000 (32-bit, non-prefetchable) [size=4K] Capabilities: [44] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: ohci_hcd = after ~2s the device suspends runtime_status = suspended 00:02.0 USB controller: NVIDIA Corporation MCP61 USB 1.1 Controller (rev a2) (prog-if 10 [OHCI]) Subsystem: ASUSTeK Computer Inc. Device 8234 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 (750ns min, 250ns max) Interrupt: pin A routed to IRQ 23 Region 0: Memory at fe02f000 (32-bit, non-prefetchable) [size=4K] Capabilities: [44] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: ohci_hcd Of course I checked that the host controller suspends, too. I also checked if lspci changes after unplugging the mouse, but that's not the case. Regards, Frank -- 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/50d3544c.5030...@googlemail.com
Bug#696431: nfs-common can't be installed with rpcbind but w/o portmap
Package: nfs-common Version: 1:1.2.2-4squeeze2 Severity: important portmap is not installed, rpcbind is installed instead. Installing nfs-common will geve the following error: insserv: Service portmap has to be enabled to start service nfs-common insserv: exiting now! update-rc.d: error: insserv rejected the script header dpkg: error processing nfs-common (--configure): subprocess installed post-installation script returned error exit status 1 -- System Information: Debian Release: 6.0.6 APT prefers stable APT policy: (500, 'stable'), (25, 'testing'), (20, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.6.5-linode47 (SMP w/4 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 nfs-common depends on: ii adduser3.112+nmu2add and remove users and groups ii initscripts2.88dsf-13.1+squeeze1 scripts for initializing and shutt ii libc6 2.11.3-4 Embedded GNU C Library: Shared lib ii libcap21:2.19-3 support for getting/setting POSIX. ii libcomerr2 1.41.12-4stable1 common error description library ii libevent-1.4-2 1.4.13-stable-1 An asynchronous event notification ii libgssapi-krb5-2 1.8.3+dfsg-4squeeze6 MIT Kerberos runtime libraries - k ii libgssglue10.1-4 mechanism-switch gssapi library ii libk5crypto3 1.8.3+dfsg-4squeeze6 MIT Kerberos runtime libraries - C ii libkrb5-3 1.8.3+dfsg-4squeeze6 MIT Kerberos runtime libraries ii libnfsidmap2 0.23-2An nfs idmapping library ii librpcsecgss3 0.19-2allows secure rpc communication us ii libwrap0 7.6.q-19 Wietse Venema's TCP wrappers libra ii lsb-base 3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip ii netbase4.45 Basic TCP/IP networking system ii rpcbind [portmap] 0.2.0-4.1 converts RPC program numbers into ii ucf3.0025+nmu1 Update Configuration File: preserv nfs-common recommends no packages. nfs-common suggests no packages. -- no debconf information -- 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/20121220181801.5563.55861.reportbug@li130-98
Bug#696431: marked as done (nfs-common can't be installed with rpcbind but w/o portmap)
Your message dated Thu, 20 Dec 2012 19:27:38 +0100 with message-id 50d3589a.40...@debian.org and subject line Re: Bug#696431: nfs-common can't be installed with rpcbind but w/o portmap has caused the Debian Bug report #696431, regarding nfs-common can't be installed with rpcbind but w/o portmap 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.) -- 696431: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696431 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: nfs-common Version: 1:1.2.2-4squeeze2 Severity: important portmap is not installed, rpcbind is installed instead. Installing nfs-common will geve the following error: insserv: Service portmap has to be enabled to start service nfs-common insserv: exiting now! update-rc.d: error: insserv rejected the script header dpkg: error processing nfs-common (--configure): subprocess installed post-installation script returned error exit status 1 -- System Information: Debian Release: 6.0.6 APT prefers stable APT policy: (500, 'stable'), (25, 'testing'), (20, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.6.5-linode47 (SMP w/4 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 nfs-common depends on: ii adduser3.112+nmu2add and remove users and groups ii initscripts2.88dsf-13.1+squeeze1 scripts for initializing and shutt ii libc6 2.11.3-4 Embedded GNU C Library: Shared lib ii libcap21:2.19-3 support for getting/setting POSIX. ii libcomerr2 1.41.12-4stable1 common error description library ii libevent-1.4-2 1.4.13-stable-1 An asynchronous event notification ii libgssapi-krb5-2 1.8.3+dfsg-4squeeze6 MIT Kerberos runtime libraries - k ii libgssglue10.1-4 mechanism-switch gssapi library ii libk5crypto3 1.8.3+dfsg-4squeeze6 MIT Kerberos runtime libraries - C ii libkrb5-3 1.8.3+dfsg-4squeeze6 MIT Kerberos runtime libraries ii libnfsidmap2 0.23-2An nfs idmapping library ii librpcsecgss3 0.19-2allows secure rpc communication us ii libwrap0 7.6.q-19 Wietse Venema's TCP wrappers libra ii lsb-base 3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip ii netbase4.45 Basic TCP/IP networking system ii rpcbind [portmap] 0.2.0-4.1 converts RPC program numbers into ii ucf3.0025+nmu1 Update Configuration File: preserv nfs-common recommends no packages. nfs-common suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Hi You have to either use backports or to use portmap instead of rpcbind with the version in Squeeze. Cheers Luk On 12/20/2012 07:18 PM, Dmitry wrote: Package: nfs-common Version: 1:1.2.2-4squeeze2 Severity: important portmap is not installed, rpcbind is installed instead. Installing nfs-common will geve the following error: insserv: Service portmap has to be enabled to start service nfs-common insserv: exiting now! update-rc.d: error: insserv rejected the script header dpkg: error processing nfs-common (--configure): subprocess installed post-installation script returned error exit status 1 -- System Information: Debian Release: 6.0.6 APT prefers stable APT policy: (500, 'stable'), (25, 'testing'), (20, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.6.5-linode47 (SMP w/4 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 nfs-common depends on: ii adduser3.112+nmu2add and remove users and groups ii initscripts2.88dsf-13.1+squeeze1 scripts for initializing and shutt ii libc6 2.11.3-4 Embedded GNU C Library: Shared lib ii libcap21:2.19-3 support for getting/setting POSIX. ii libcomerr2 1.41.12-4stable1 common error description library ii libevent-1.4-2 1.4.13-stable-1 An asynchronous event notification ii libgssapi-krb5-2 1.8.3+dfsg-4squeeze6 MIT Kerberos runtime libraries - k ii libgssglue10.1-4 mechanism-switch gssapi library ii libk5crypto3 1.8.3+dfsg-4squeeze6 MIT Kerberos runtime libraries - C ii libkrb5-3 1.8.3+dfsg-4squeeze6 MIT Kerberos runtime libraries ii libnfsidmap2 0.23-2
Bug#696438: linux-image-3.6-trunk-amd64: uname shows incorrent version number
Package: src:linux Version: 3.6.9-1~experimental.1 Severity: minor Dear Maintainer, uname -a shows: Linux sbux 3.6-trunk-amd64 #1 SMP Debian 3.6.4-1~experimental.1 x86_64 GNU/Linux but shouldn't it be 3.6.9 as is the package/kernel version? -- Package-specific info: ** Version: Linux version 3.6-trunk-amd64 (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-1) ) #1 SMP Debian 3.6.4-1~experimental.1 ** Command line: BOOT_IMAGE=/vmlinuz-3.6-trunk-amd64 root=/dev/mapper/sbux-root ro quiet ** Not tainted ** Kernel log: [179910.818470] sdhci-pci :05:00.2: Will use DMA mode even though HW doesn't fully claim to support it. [179910.878464] sdhci-pci :05:00.2: Will use DMA mode even though HW doesn't fully claim to support it. [179910.940227] sdhci-pci :05:00.2: Will use DMA mode even though HW doesn't fully claim to support it. [179911.002339] sdhci-pci :05:00.2: Will use DMA mode even though HW doesn't fully claim to support it. [182079.735140] PM: Syncing filesystems ... done. [182079.741368] PM: Preparing system for mem sleep [182080.031044] Freezing user space processes ... (elapsed 0.01 seconds) done. [182080.044093] Freezing remaining freezable tasks ... (elapsed 3.60 seconds) done. [182083.644113] PM: Entering mem sleep [182083.644153] Suspending console(s) (use no_console_suspend to debug) [182083.660493] sd 0:0:0:0: [sda] Synchronizing SCSI cache [182083.660561] sd 0:0:0:0: [sda] Stopping disk [182083.676714] pciehp :00:1c.1:pcie04: pciehp_suspend ENTRY [182083.676716] pciehp :00:1c.0:pcie04: pciehp_suspend ENTRY [182083.692094] i915 :00:02.0: power state changed by ACPI to D3hot [182083.916582] e1000e :00:19.0: wake-up capability enabled by ACPI [182084.076126] PM: suspend of devices complete after 415.773 msecs [182084.076267] PM: late suspend of devices complete after 0.138 msecs [182084.092226] ehci_hcd :00:1d.7: wake-up capability enabled by ACPI [182084.108028] ehci_hcd :00:1d.7: power state changed by ACPI to D3hot [182084.108127] uhci_hcd :00:1d.1: wake-up capability enabled by ACPI [182084.148033] uhci_hcd :00:1d.0: wake-up capability enabled by ACPI [182084.148037] uhci_hcd :00:1d.0: power state changed by ACPI to D2 [182084.148306] ehci_hcd :00:1a.7: wake-up capability enabled by ACPI [182084.164031] ehci_hcd :00:1a.7: power state changed by ACPI to D3hot [182084.164123] uhci_hcd :00:1a.1: wake-up capability enabled by ACPI [182084.164127] uhci_hcd :00:1a.1: power state changed by ACPI to D2 [182084.164200] uhci_hcd :00:1a.0: wake-up capability enabled by ACPI [182084.164252] PM: noirq suspend of devices complete after 87.981 msecs [182084.164694] ACPI: Preparing to enter system sleep state S3 [182084.336058] PM: Saving platform NVS memory [182084.336339] Disabling non-boot CPUs ... [182084.440050] smpboot: CPU 1 is now offline [182084.440640] Extended CMOS year: 2000 [182084.440640] ACPI: Low-level resume complete [182084.440640] PM: Restoring platform NVS memory [182084.440640] Extended CMOS year: 2000 [182084.440640] Enabling non-boot CPUs ... [182084.440640] smpboot: Booting Node 0 Processor 1 APIC 0x1 [182084.484114] CPU1 is up [182084.486189] ACPI: Waking up from system sleep state S3 [182084.904200] i915 :00:02.0: power state changed by ACPI to D0 [182084.936275] uhci_hcd :00:1a.0: wake-up capability disabled by ACPI [182084.936280] uhci_hcd :00:1a.1: power state changed by ACPI to D0 [182084.936357] uhci_hcd :00:1a.1: wake-up capability disabled by ACPI [182084.936361] ehci_hcd :00:1a.7: power state changed by ACPI to D0 [182084.952186] ehci_hcd :00:1a.7: wake-up capability disabled by ACPI [182084.968401] uhci_hcd :00:1d.0: power state changed by ACPI to D0 [182085.008104] uhci_hcd :00:1d.0: wake-up capability disabled by ACPI [182085.008200] uhci_hcd :00:1d.1: wake-up capability disabled by ACPI [182085.008204] ehci_hcd :00:1d.7: power state changed by ACPI to D0 [182085.024181] ehci_hcd :00:1d.7: wake-up capability disabled by ACPI [182085.072381] PM: noirq resume of devices complete after 168.257 msecs [182085.072506] PM: early resume of devices complete after 0.072 msecs [182085.072560] i915 :00:02.0: setting latency timer to 64 [182085.072584] e1000e :00:19.0: wake-up capability disabled by ACPI [182085.077280] e1000e :00:19.0: irq 42 for MSI/MSI-X [182085.087722] uhci_hcd :00:1a.0: setting latency timer to 64 [182085.087751] usb usb3: root hub lost power or was reset [182085.087770] uhci_hcd :00:1a.1: setting latency timer to 64 [182085.087797] usb usb4: root hub lost power or was reset [182085.087818] ehci_hcd :00:1a.7: setting latency timer to 64 [182085.087898] snd_hda_intel :00:1b.0: irq 46 for MSI/MSI-X [182085.087950] pciehp :00:1c.0:pcie04: pciehp_resume ENTRY [182085.087962] pciehp :00:1c.1:pcie04: pciehp_resume ENTRY [182085.087973] uhci_hcd :00:1d.0: setting latency timer to 64
Bug#696438: marked as done (linux-image-3.6-trunk-amd64: uname shows incorrent version number)
Your message dated Thu, 20 Dec 2012 20:20:25 + with message-id 20121220202025.gr13...@decadent.org.uk and subject line Re: Bug#696438: linux-image-3.6-trunk-amd64: uname shows incorrent version number has caused the Debian Bug report #696438, regarding linux-image-3.6-trunk-amd64: uname shows incorrent version number 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.) -- 696438: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696438 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:linux Version: 3.6.9-1~experimental.1 Severity: minor Dear Maintainer, uname -a shows: Linux sbux 3.6-trunk-amd64 #1 SMP Debian 3.6.4-1~experimental.1 x86_64 GNU/Linux but shouldn't it be 3.6.9 as is the package/kernel version? -- Package-specific info: ** Version: Linux version 3.6-trunk-amd64 (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-1) ) #1 SMP Debian 3.6.4-1~experimental.1 ** Command line: BOOT_IMAGE=/vmlinuz-3.6-trunk-amd64 root=/dev/mapper/sbux-root ro quiet ** Not tainted ** Kernel log: [179910.818470] sdhci-pci :05:00.2: Will use DMA mode even though HW doesn't fully claim to support it. [179910.878464] sdhci-pci :05:00.2: Will use DMA mode even though HW doesn't fully claim to support it. [179910.940227] sdhci-pci :05:00.2: Will use DMA mode even though HW doesn't fully claim to support it. [179911.002339] sdhci-pci :05:00.2: Will use DMA mode even though HW doesn't fully claim to support it. [182079.735140] PM: Syncing filesystems ... done. [182079.741368] PM: Preparing system for mem sleep [182080.031044] Freezing user space processes ... (elapsed 0.01 seconds) done. [182080.044093] Freezing remaining freezable tasks ... (elapsed 3.60 seconds) done. [182083.644113] PM: Entering mem sleep [182083.644153] Suspending console(s) (use no_console_suspend to debug) [182083.660493] sd 0:0:0:0: [sda] Synchronizing SCSI cache [182083.660561] sd 0:0:0:0: [sda] Stopping disk [182083.676714] pciehp :00:1c.1:pcie04: pciehp_suspend ENTRY [182083.676716] pciehp :00:1c.0:pcie04: pciehp_suspend ENTRY [182083.692094] i915 :00:02.0: power state changed by ACPI to D3hot [182083.916582] e1000e :00:19.0: wake-up capability enabled by ACPI [182084.076126] PM: suspend of devices complete after 415.773 msecs [182084.076267] PM: late suspend of devices complete after 0.138 msecs [182084.092226] ehci_hcd :00:1d.7: wake-up capability enabled by ACPI [182084.108028] ehci_hcd :00:1d.7: power state changed by ACPI to D3hot [182084.108127] uhci_hcd :00:1d.1: wake-up capability enabled by ACPI [182084.148033] uhci_hcd :00:1d.0: wake-up capability enabled by ACPI [182084.148037] uhci_hcd :00:1d.0: power state changed by ACPI to D2 [182084.148306] ehci_hcd :00:1a.7: wake-up capability enabled by ACPI [182084.164031] ehci_hcd :00:1a.7: power state changed by ACPI to D3hot [182084.164123] uhci_hcd :00:1a.1: wake-up capability enabled by ACPI [182084.164127] uhci_hcd :00:1a.1: power state changed by ACPI to D2 [182084.164200] uhci_hcd :00:1a.0: wake-up capability enabled by ACPI [182084.164252] PM: noirq suspend of devices complete after 87.981 msecs [182084.164694] ACPI: Preparing to enter system sleep state S3 [182084.336058] PM: Saving platform NVS memory [182084.336339] Disabling non-boot CPUs ... [182084.440050] smpboot: CPU 1 is now offline [182084.440640] Extended CMOS year: 2000 [182084.440640] ACPI: Low-level resume complete [182084.440640] PM: Restoring platform NVS memory [182084.440640] Extended CMOS year: 2000 [182084.440640] Enabling non-boot CPUs ... [182084.440640] smpboot: Booting Node 0 Processor 1 APIC 0x1 [182084.484114] CPU1 is up [182084.486189] ACPI: Waking up from system sleep state S3 [182084.904200] i915 :00:02.0: power state changed by ACPI to D0 [182084.936275] uhci_hcd :00:1a.0: wake-up capability disabled by ACPI [182084.936280] uhci_hcd :00:1a.1: power state changed by ACPI to D0 [182084.936357] uhci_hcd :00:1a.1: wake-up capability disabled by ACPI [182084.936361] ehci_hcd :00:1a.7: power state changed by ACPI to D0 [182084.952186] ehci_hcd :00:1a.7: wake-up capability disabled by ACPI [182084.968401] uhci_hcd :00:1d.0: power state changed by ACPI to D0 [182085.008104] uhci_hcd :00:1d.0: wake-up capability disabled by ACPI [182085.008200] uhci_hcd :00:1d.1: wake-up capability disabled by ACPI [182085.008204] ehci_hcd :00:1d.7: power state changed by ACPI to D0 [182085.024181] ehci_hcd :00:1d.7: wake-up capability disabled by ACPI
Processed: Re: Bug#696425: qla2xxx: qla2xxx driver with QLE2562MMF yields Mid-layer underflow detected errors Package: linux-image-3.2.0-0.bpo.4-amd64
Processing commands for cont...@bugs.debian.org: reassign 696425 src:linux Bug #696425 [linux-image-3.2.0-0.bpo.4-amd64 (qla2xxx)] qla2xxx: qla2xxx driver with QLE2562MMF yields Mid-layer underflow detected errors Package: linux-image-3.2.0-0.bpo.4-amd64 Warning: Unknown package 'linux-image-3.2.0-0.bpo.4-amd64' Warning: Unknown package 'qla2xxx' Bug reassigned from package 'linux-image-3.2.0-0.bpo.4-amd64 (qla2xxx)' to 'src:linux'. Ignoring request to alter found versions of bug #696425 to the same values previously set Ignoring request to alter fixed versions of bug #696425 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 696425: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696425 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.135603720225128.transcr...@bugs.debian.org
Bug#683111: linux-image-3.2.0-4-ixp4xx: same WARNING on armel (linux-3.2.32/block/genhd.c:1573 disk_clear_events+0xc8/0x110()) Followup-For: Bug #683111 Package: src:linux Version: 3.2.32-1
I'm seeing an OOPS from the same line of code on armel. You can see the backtrace in the dmesg output below. This is from an NSLU2, where the root filesystem is on a 2GiB USB stick, and the machine has 32MiB of RAM and a 265BogoMIPS XScale-IXP42x CPU. Regards, --dkg -- Package-specific info: ** Version: Linux version 3.2.0-4-ixp4xx (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-9) ) #1 Debian 3.2.32-1 ** Command line: console=ttyS0,115200 noirqdebug ** Tainted: W (512) * Taint on warning. ** Kernel log: [3.487706] hub 1-0:1.0: 5 ports detected [3.923091] usb 1-2: new high-speed USB device number 3 using ehci_hcd [4.074175] usb 1-2: New USB device found, idVendor=0781, idProduct=5406 [4.080986] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [4.088294] usb 1-2: Product: U3 Cruzer Micro [4.092747] usb 1-2: Manufacturer: SanDisk [4.096913] usb 1-2: SerialNumber: 08782307B150EF77 [4.246588] SCSI subsystem initialized [4.264784] usbcore: registered new interface driver uas [4.290730] Initializing USB Mass Storage driver... [4.296806] scsi0 : usb-storage 1-2:1.0 [4.307533] usbcore: registered new interface driver usb-storage [4.313759] USB Mass Storage support registered. [5.305988] scsi 0:0:0:0: Direct-Access SanDisk U3 Cruzer Micro 8.02 PQ: 0 ANSI: 0 CCS [5.316201] scsi 0:0:0:1: CD-ROMSanDisk U3 Cruzer Micro 8.02 PQ: 0 ANSI: 0 [5.475288] sd 0:0:0:0: [sda] 3907583 512-byte logical blocks: (2.00 GB/1.86 GiB) [5.503782] sd 0:0:0:0: [sda] Write Protect is off [5.508677] sd 0:0:0:0: [sda] Mode Sense: 45 00 00 08 [5.512609] sd 0:0:0:0: [sda] No Caching mode page present [5.518196] sd 0:0:0:0: [sda] Assuming drive cache: write through [5.535757] sd 0:0:0:0: [sda] No Caching mode page present [5.541347] sd 0:0:0:0: [sda] Assuming drive cache: write through [5.555094] sda: sda1 sda2 sda5 [5.571007] sd 0:0:0:0: [sda] No Caching mode page present [5.576699] sd 0:0:0:0: [sda] Assuming drive cache: write through [5.582925] sd 0:0:0:0: [sda] Attached SCSI removable disk [6.325444] [ cut here ] [6.330219] WARNING: at /build/buildd-linux_3.2.32-1-armel-KUCrxS/linux-3.2.32/block/genhd.c:1573 disk_clear_events+0xc8/0x110() [6.341920] Modules linked in: sd_mod crc_t10dif usb_storage uas scsi_mod ehci_hcd usbcore usb_common [6.351373] [c00137ac] (unwind_backtrace+0x0/0xe0) from [c0026f18] (warn_slowpath_common+0x4c/0x64) [6.360921] [c0026f18] (warn_slowpath_common+0x4c/0x64) from [c0026f48] (warn_slowpath_null+0x18/0x1c) [6.370733] [c0026f48] (warn_slowpath_null+0x18/0x1c) from [c015af4c] (disk_clear_events+0xc8/0x110) [6.380375] [c015af4c] (disk_clear_events+0xc8/0x110) from [c00ecc48] (check_disk_change+0x18/0x50) [6.389985] [c00ecc48] (check_disk_change+0x18/0x50) from [bf08d478] (sd_open+0x7c/0x138 [sd_mod]) [6.399495] [bf08d478] (sd_open+0x7c/0x138 [sd_mod]) from [c00edce4] (__blkdev_get+0x284/0x3a8) [6.408689] [c00edce4] (__blkdev_get+0x284/0x3a8) from [c00edf98] (blkdev_get+0x190/0x28c) [6.417451] [c00edf98] (blkdev_get+0x190/0x28c) from [c00c1300] (__dentry_open+0x224/0x33c) [6.426293] [c00c1300] (__dentry_open+0x224/0x33c) from [c00c2228] (nameidata_to_filp+0x50/0x5c) [6.435583] [c00c2228] (nameidata_to_filp+0x50/0x5c) from [c00cec50] (do_last.isra.26+0x670/0x6a8) [6.445043] [c00cec50] (do_last.isra.26+0x670/0x6a8) from [c00ced64] (path_openat+0xb4/0x3e0) [6.454062] [c00ced64] (path_openat+0xb4/0x3e0) from [c00cf174] (do_filp_open+0x2c/0x78) [6.462641] [c00cf174] (do_filp_open+0x2c/0x78) from [c00c2318] (do_sys_open+0xe4/0x17c) [6.471237] [c00c2318] (do_sys_open+0xe4/0x17c) from [c000dea0] (ret_fast_syscall+0x0/0x2c) [6.480049] ---[ end trace fb8a3c5ed96fd8b7 ]--- [6.839330] kjournald starting. Commit interval 5 seconds [6.845203] EXT3-fs (sda1): mounted filesystem with ordered data mode [ 10.362348] udevd[254]: starting version 175 [ 11.498005] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 11.643850] ohci_hcd :00:01.0: OHCI Host Controller [ 11.695488] ohci_hcd :00:01.0: new USB bus registered, assigned bus number 2 [ 11.789395] ohci_hcd :00:01.0: irq 28, io mem 0x4800 [ 11.884793] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001 [ 11.891695] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 11.899149] usb usb2: Product: OHCI Host Controller [ 11.904142] usb usb2: Manufacturer: Linux 3.2.0-4-ixp4xx ohci_hcd [ 11.910346] usb usb2: SerialNumber: :00:01.0 [ 11.976445] input: ixp4xx beeper as /devices/platform/ixp4xx-beeper.4/input/input0 [ 12.155663] IXP4xx Queue Manager initialized. [ 12.235505] hub 2-0:1.0: USB hub found [ 12.279355] hub 2-0:1.0: 3 ports detected [ 12.334303] ohci_hcd :00:01.1: OHCI Host Controller [
