Bug#502845: (no subject)
Forwarding this:
https://groups.google.com/group/open-iscsi/browse_thread/thread/7b44b4b57f01eb70?hl=en#
Since I'm not sure how long it takes google groups to update, i'll go
ahead and paste the patch here as well below.
If you apply the first patch from the above link, the second patch below
is not needed. It is only required for a 32bit userspace to talk to an
unpatched 32bit kernel. The first patch allows for 64/64, 32/32, and 32/64
user/kernel setups.
I'm not sure sure if you want to patch the kernel and userspace at the
same time, or patch userspace and sunset the below patches on the next
convenient patch window.
Thanks,
~Lisa M
diff --git a/include/iscsi_if.h b/include/iscsi_if.h
index dad9fd8..db97332 100644
--- a/include/iscsi_if.h
+++ b/include/iscsi_if.h
@@ -3,6 +3,7 @@
*
* Copyright (C) 2005 Dmitry Yusupov
* Copyright (C) 2005 Alex Aizman
+ * Copyright (C) 2012 Lisa Maginnis
* maintained by open-is...@googlegroups.com
*
* This program is free software; you can redistribute it and/or modify
@@ -106,6 +107,14 @@ struct iscsi_uevent {
uint32_t iferror; /* carries interface or resource errors */
uint64_t transport_handle;
+ /* Structs in this union can differ on size between 32bit and 64bit
+* systems. This will break systems running a 32bit userspace with a
+ * 64bit kernel. It is important to specify an alignment for the
+ * struct(s) so that their sizes match on both in both 32 and 64bit
+* systems. Currently the two largest structs are:
+* msg_bind_conn: 20 bytes, 24 aligned to the sizeof(uint64_t)
+* stop_conn: 20 bytes, 24 aligned to the sizeof(uint64_t)
+*/
union {
/* messages u - k */
struct msg_create_session {
@@ -131,7 +140,7 @@ struct iscsi_uevent {
uint32_tcid;
uint64_ttransport_eph;
uint32_tis_leading;
- } b_conn;
+ } b_conn __attribute__((aligned (sizeof(uint64_t;
struct msg_destroy_conn {
uint32_tsid;
uint32_tcid;
@@ -157,7 +166,7 @@ struct iscsi_uevent {
uint32_tcid;
uint64_tconn_handle;
uint32_tflag;
- } stop_conn;
+ } stop_conn __attribute__((aligned (sizeof(uint64_t;
struct msg_get_stats {
uint32_tsid;
uint32_tcid;
diff --git a/usr/iscsi_netlink.h b/usr/iscsi_netlink.h
index 25b41db..6b482ad 100644
--- a/usr/iscsi_netlink.h
+++ b/usr/iscsi_netlink.h
@@ -2,6 +2,7 @@
* iSCSI Netlink attr helpers
*
* Copyright (C) 2011 Red Hat, Inc. All rights reserved.
+ * Copyright (C) 2012 Lisa Maginnis
*
* This program is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Public License as published
@@ -30,4 +31,10 @@ struct iovec;
extern struct nlattr *iscsi_nla_alloc(uint16_t type, uint16_t len);
+#ifdef __i386__
+int fix_32bit_kernel_structs; /* If set to 1, will cause reads from the kernel
to be
+ * padded with an extra 4 bytes between
iscsi_uevent.u and
+ * iscsi_uevent.r */
+#endif
+
#endif
diff --git a/usr/iscsid.c b/usr/iscsid.c
index b4bb65b..53381bf 100644
--- a/usr/iscsid.c
+++ b/usr/iscsid.c
@@ -4,6 +4,7 @@
* Copyright (C) 2004 Dmitry Yusupov, Alex Aizman
* Copyright (C) 2006 Mike Christie
* Copyright (C) 2006 Red Hat, Inc. All rights reserved.
+ * Copyright (C) 2012 Lisa Maginnis
* maintained by open-is...@googlegroups.com
*
@@ -52,6 +53,10 @@
#include iscsid_req.h
#include iscsi_err.h
+#ifdef __i386__
+extern int fix_32bit_kernel_structs; /* For i386 compatibility. */
+#endif
+
/* global config info */
struct iscsi_daemon_config daemon_config;
struct iscsi_daemon_config *dconfig = daemon_config;
@@ -336,6 +341,28 @@ static void missing_iname_warn(char *initiatorname_file)
ignored.\n, initiatorname_file, initiatorname_file);
}
+#ifdef __i386__
+/* check_kernel_compatibility()
+ * This function detects when we are built in i386 and running a x86_64 (64bit) kernel and
+ * sets a flag. This flag is used to to signal the nlpayload_read() and nl_read() functions
+ * in netlink.c
+ */
+void check_kernel_compatibility()
+{
+ struct utsname uname_data;
+ fix_32bit_kernel_structs = 0;
+
+ /* Get our kernel and machine type for compatibility */
+ uname(uname_data);
+
+ /* If we are not running a x86_64 kernel, enable the kernel struct fix.
+ * TODO: When/if kernel patches are made, a kernel version check should be
done here. */
+ if(strcmp(uname_data.machine, x86_64) != 0) {
+fix_32bit_kernel_structs = 1;
+ }
+}
+#endif
+
int main(int argc, char *argv[])
{
struct
Processed: Re: Bug#691977: please add be2iscsi module to d-i image
Processing commands for cont...@bugs.debian.org: reassign 691977 linux Bug #691977 [debian-installer] please add be2iscsi module to d-i image Bug reassigned from package 'debian-installer' to 'linux'. Ignoring request to alter found versions of bug #691977 to the same values previously set Ignoring request to alter fixed versions of bug #691977 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 691977: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691977 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.13517566889251.transcr...@bugs.debian.org
Bug#502845: open-iscsi: login fails using 64-bit kernel with 32-bit userland
Hi Lisa, Lisa Marie wrote: [Subject: (no subject)] Please keep in mind that these appear as emails in a crowded inbox, where a subject line can be very useful for providing context. Forwarding this: https://groups.google.com/group/open-iscsi/browse_thread/thread/7b44b4b57f01eb70?hl=en# Since I'm not sure how long it takes google groups to update, i'll go ahead and paste the patch here as well below. If you apply the first patch from the above link, the second patch below is not needed. It is only required for a 32bit userspace to talk to an unpatched 32bit kernel. The first patch allows for 64/64, 32/32, and 32/64 user/kernel setups. Thanks for working on this! Your patches have no effect in the 64bit case (good). In the 32bit case, they break ABI, so they are a no-go, unfortunately. The userspace patch is especially dangerous, since it would make this bug impossible to fix properly later. Userspace processes using iscsi start by creating a netlink socket with socket(PF_NETLINK, SOCK_RAW, NETLINK_ISCSI) and binding to it. Afterwards, they use sendmsg and recvmsg as appropriate to send and receive events. We need to use a different message format when interacting with 32bit tasks. Kernel commit 1dacc76d0014 (net/compat/wext: send different messages to compat tasks, 2009-07-01) can provide some inspiration. In the send path, the way to do this is to set frag_list to the 32bit version of the structure, like so: #ifdef CONFIG_COMPAT compat_skb = alloc_skb(len, GFP_ATOMIC); ... fill compat_skb ... skb_shinfo(skb)-frag_list = compat_skb; #endif Then on a 64bit kernel, 32bit processes will receive compat_skb instead of skb. No ABI breakage! So much for broadcast. When receiving messages from userspace, we want to know whether a 32bit process sent the message. The netlink API doesn't tell us. The patch [1] (netlink: store MSG_CMSG_COMPAT flag in netlink_skb_parms) is simple and something similar would be likely to be accepted once there's a caller using it. Hope that helps, Jonathan [1] http://thread.gmane.org/gmane.linux.network/157118/focus=157119 -- 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/20121101082535.GA25940@elie.Belkin
Bug#691902: [squeeze-wheezy regression] Unable to shutdown via normal means
Hi sorry but I have a problem I cannot remember if I installed the nvidia binary driver (installer from Nvidia site) or nvidia from nonfree repo... I have a spare hard drive that I can swap in and install wheezy, would that be ok? That way we would be testing stock wheezy against this hardware BR -Janne On Wed, Oct 31, 2012 at 10:00 PM, Jonathan Nieder jrnie...@gmail.com wrote: Janne Boman wrote: ouput attached. Thanks. Can you reproduce this using nouveau instead of nvidia? (Testing this would require disabling uvesafb temporarily.) If it works with nouveau, we can pass this on to the maintainers of the nvidia proprietary driver. If it fails with nouveau, too, that will help us bring this up with linux-kernel upstream. So either result is progress. Hope that helps, Jonathan -- 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/CAAiCWgkNCs807t1txmuMw9TUcBb3TXxfn=xnvzcqg6h1pcy...@mail.gmail.com
Bug#691902: [squeeze-wheezy regression] Unable to shutdown via normal means
Janne Boman wrote: I have a spare hard drive that I can swap in and install wheezy, would that be ok? That way we would be testing stock wheezy against this hardware That would be great. If you have time for it, don't forget to file an installation report: http://www.debian.org/releases/wheezy/amd64/apas04.html Thanks, Jonathan -- 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/20121101084443.GB25940@elie.Belkin
Processed: Re: open-iscsi: login fails using 64-bit kernel with 32-bit userland
Processing commands for cont...@bugs.debian.org: affects 502845 + open-iscsi Bug #502845 [linux-2.6] open-iscsi: login fails using 64-bit kernel with 32-bit userland Added indication that 502845 affects open-iscsi End of message, stopping processing here. Please contact me if you need assistance. -- 502845: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=502845 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.135175995231204.transcr...@bugs.debian.org
Bug#691902: [squeeze-wheezy regression] Unable to shutdown via normal means
Ok, I'm going with this image: debian-wheezy-DI-b3-amd64-CD-1.iso (http://cdimage.debian.org/cdimage/wheezy_di_beta3/amd64/iso-cd/) On Thu, Nov 1, 2012 at 10:44 AM, Jonathan Nieder jrnie...@gmail.com wrote: That would be great. If you have time for it, don't forget to file an installation report: http://www.debian.org/releases/wheezy/amd64/apas04.html Thanks, Jonathan -- 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/caaicwgnz_fpfeohcajjf_tb8zv9+ixhtu9tphnfu7lpuomw...@mail.gmail.com
Bug#690814: [3.1-3.2.y regression] disk activity provokes lockups on VIA EPIA CL-6000
--- On Tue, 10/30/12, Jonathan Nieder jrnie...@gmail.com wrote: Thanks! To recap: 3.1.8-2 works fine 3.2.1-1 hung at Loading, please wait... once, worked fine twice 3.2.23-1 reliably hangs (though not always right away) Could you try 3.2~rc4-1~experimental.1, to narrow down the range a little? (If it doesn't hang, that would be great, but I suspect it will hang, too.) 3.2~rc4-1~experimental.1 seems to work fine i.e. I booted it several times and didn't encounter a problem. Also booted 3.2.1-1 again and it also booted fine (it has been running fine for a week or so). Also tried 3.2.23-1 again but it got stuck at Activating swap..., thus I think that reliably hangs states it correctly. I also tried linux-image-3.2.0-2-486_3.2.19-1_i386.deb. It seems to boot fine (3 tests) and I left it running for now to see if it locks up while it is in use.
Bug#692024: zram module is missing
Package: linux-image-3.6-trunk-amd64 Version: 3.6.4-1~experimental.1 Severity: important zram module is missing. -- 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/e4086f19e7af12649fdf0c798d4748a9.squir...@webmail.on.nl
Bug#692025: linux: internet connection refused after new route
Package: linux Version: linux-image Severity: important Tags: upstream When one lan interface is connected and you try to connect an other one, often you can't connect to the Internet after that. You need to retry the connection. I suspect this bug is when a task (i.e. ntp, virus updater, ...) tries to connect to the Internet through a socket using the first interface, holds it open, the kernel won't reroute to the new one and you need try to again. Example: When a openvpn connection is made and initiation is okey, but you can't connect to the Internet, through the openvpn-connection. Retrying it and you can connect. Example: When one wlan connection is up and you try to connect throught an other one, you need to retry. I have tested both examples with lftp trying to connect to an IP-address and you cant' connect as long as lftp's socket is in effect. -- System Information: Debian Release: 6.0.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121101125833.3766.58520.reportbug@debian
Bug#502845: open-iscsi: login fails using 64-bit kernel with 32-bit userland
Your patches have no effect in the 64bit case (good). In the 32bit case, they break ABI, so they are a no-go, unfortunately. The userspace patch is especially dangerous, since it would make this bug impossible to fix properly later. The 2nd patch is set up to not break the ABI for 32bit userspace, the first patch would indeed break the ABI (and hence the need for the 2nd one). On Thu, 1 Nov 2012, Jonathan Nieder wrote: Date: Thu, 1 Nov 2012 01:25:35 -0700 From: Jonathan Nieder jrnie...@gmail.com To: Lisa Marie nullo...@sdf.org Cc: 502...@bugs.debian.org, open-is...@packages.debian.org Subject: Re: open-iscsi: login fails using 64-bit kernel with 32-bit userland Hi Lisa, Lisa Marie wrote: [Subject: (no subject)] Please keep in mind that these appear as emails in a crowded inbox, where a subject line can be very useful for providing context. Forwarding this: https://groups.google.com/group/open-iscsi/browse_thread/thread/7b44b4b57f01eb70?hl=en# Since I'm not sure how long it takes google groups to update, i'll go ahead and paste the patch here as well below. If you apply the first patch from the above link, the second patch below is not needed. It is only required for a 32bit userspace to talk to an unpatched 32bit kernel. The first patch allows for 64/64, 32/32, and 32/64 user/kernel setups. Thanks for working on this! Your patches have no effect in the 64bit case (good). In the 32bit case, they break ABI, so they are a no-go, unfortunately. The userspace patch is especially dangerous, since it would make this bug impossible to fix properly later. Userspace processes using iscsi start by creating a netlink socket with socket(PF_NETLINK, SOCK_RAW, NETLINK_ISCSI) and binding to it. Afterwards, they use sendmsg and recvmsg as appropriate to send and receive events. We need to use a different message format when interacting with 32bit tasks. Kernel commit 1dacc76d0014 (net/compat/wext: send different messages to compat tasks, 2009-07-01) can provide some inspiration. In the send path, the way to do this is to set frag_list to the 32bit version of the structure, like so: #ifdef CONFIG_COMPAT compat_skb = alloc_skb(len, GFP_ATOMIC); ... fill compat_skb ... skb_shinfo(skb)-frag_list = compat_skb; #endif Then on a 64bit kernel, 32bit processes will receive compat_skb instead of skb. No ABI breakage! So much for broadcast. When receiving messages from userspace, we want to know whether a 32bit process sent the message. The netlink API doesn't tell us. The patch [1] (netlink: store MSG_CMSG_COMPAT flag in netlink_skb_parms) is simple and something similar would be likely to be accepted once there's a caller using it. Hope that helps, Jonathan [1] http://thread.gmane.org/gmane.linux.network/157118/focus=157119 nullo...@sdf.org SDF Public Access UNIX System - http://sdf.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/alpine.neb.2.02.1211010909440.2...@iceland.freeshell.org
Bug#692025: linux: internet connection refused after new route
On Thu, 2012-11-01 at 13:58 +0100, Patrik Nilsson wrote: Package: linux Version: linux-image Can we have a real version number please? (/proc/version will show the Debian package version for the running kernel). Severity: important Tags: upstream When one lan interface is connected and you try to connect an other one, often you can't connect to the Internet after that. You need to retry the connection. I suspect this bug is when a task (i.e. ntp, virus updater, ...) tries to connect to the Internet through a socket using the first interface, holds it open, the kernel won't reroute to the new one and you need try to again. Example: When a openvpn connection is made and initiation is okey, but you can't connect to the Internet, through the openvpn-connection. Retrying it and you can connect. Example: When one wlan connection is up and you try to connect throught an other one, you need to retry. I have tested both examples with lftp trying to connect to an IP-address and you cant' connect as long as lftp's socket is in effect. Please explain in more detail what you're doing: - All the commands you run to reconfigure and use the network - The routing table (as shown by 'ip r') after each reconfiguration Ben. -- Ben Hutchings I'm always amazed by the number of people who take up solipsism because they heard someone else explain it. - E*Borg on alt.fan.pratchett signature.asc Description: This is a digitally signed message part
Processed: tagging 692024
Processing commands for cont...@bugs.debian.org: tags 692024 + pending Bug #692024 [linux-image-3.6-trunk-amd64] zram module is missing Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 692024: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692024 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.13517796257816.transcr...@bugs.debian.org
Processed: tagging 692025
Processing commands for cont...@bugs.debian.org: tags 692025 + moreinfo Bug #692025 [linux] linux: internet connection refused after new route Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 692025: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692025 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.13517796428209.transcr...@bugs.debian.org
Bug#692043: net: do not disable sg for packets requiring no checksum
Package: src:linux
Version: 3.2.23-1
Severity: important
Dear Maintainer,
A regression appearing upstream after 2.6.38 (so not in squeeze) appears
in wheezy. The fix is in the upstream 3.2.y stable Linux kernel maintained
by Ben Hutchings, so it's probably on its way into wheezy, but I didn't
see any bug for it, so I figured I'd reach out.
Here is the commit from 3.2.y, with the changelog describing the user
impact, felt most keenly by debian users who download the open source aoe
driver directly from coraid.com. It includes the simple fix.
commit 9d222e395fc51081a77bac4168141e289dff2d4b
Author: Ed Cashin ecas...@coraid.com
Date: Wed Sep 19 15:49:00 2012 +
net: do not disable sg for packets requiring no checksum
[ Upstream commit c0d680e577ff171e7b37dbdb1b1bf5451e851f04 ]
A change in a series of VLAN-related changes appears to have
inadvertently disabled the use of the scatter gather feature of
network cards for transmission of non-IP ethernet protocols like ATA
over Ethernet (AoE). Below is a reference to the commit that
introduces a harmonize_features function that turns off scatter
gather when the NIC does not support hardware checksumming for the
ethernet protocol of an sk buff.
commit f01a5236bd4b140198fbcc550f085e8361fd73fa
Author: Jesse Gross je...@nicira.com
Date: Sun Jan 9 06:23:31 2011 +
net offloading: Generalize netif_get_vlan_features().
The can_checksum_protocol function is not equipped to consider a
protocol that does not require checksumming. Calling it for a
protocol that requires no checksum is inappropriate.
The patch below has harmonize_features call can_checksum_protocol when
the protocol needs a checksum, so that the network layer is not forced
to perform unnecessary skb linearization on the transmission of AoE
packets. Unnecessary linearization results in decreased performance
and increased memory pressure, as reported here:
http://www.spinics.net/lists/linux-mm/msg15184.html
The problem has probably not been widely experienced yet, because
only recently has the kernel.org-distributed aoe driver acquired the
ability to use payloads of over a page in size, with the patchset
recently included in the mm tree:
https://lkml.org/lkml/2012/8/28/140
The coraid.com-distributed aoe driver already could use payloads of
greater than a page in size, but its users generally do not use the
newest kernels.
Signed-off-by: Ed Cashin ecas...@coraid.com
Signed-off-by: David S. Miller da...@davemloft.net
Signed-off-by: Ben Hutchings b...@decadent.org.uk
diff --git a/net/core/dev.c b/net/core/dev.c
index 611294a..abe1147 100644
--- a/net/core/dev.c
+++ b/net/core/dev.c
@@ -2108,7 +2108,8 @@ static bool can_checksum_protocol(unsigned long features,
__be16 protocol)
static u32 harmonize_features(struct sk_buff *skb, __be16 protocol, u32
features)
{
- if (!can_checksum_protocol(features, protocol)) {
+ if (skb-ip_summed != CHECKSUM_NONE
+ !can_checksum_protocol(features, protocol)) {
features = ~NETIF_F_ALL_CSUM;
features = ~NETIF_F_SG;
} else if (illegal_highdma(skb-dev, skb)) {
-- Package-specific info:
** Version:
Linux version 3.2.0-3-amd64 (Debian 3.2.23-1) (debian-kernel@lists.debian.org)
(gcc version 4.6.3 (Debian 4.6.3-8) ) #1 SMP Mon Jul 23 02:45:17 UTC 2012
** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.2.0-3-amd64
root=UUID=4cb7446d-c561-4184-b8ec-486ef365455b ro quiet
** Not tainted
** Kernel log:
[0.801610] acpiphp: Slot [30] registered
[0.801693] acpiphp: Slot [31] registered
[0.802476] intel_idle: does not run on family 6 model 15
[0.802532] ERST: Table is not found!
[0.802535] GHES: HEST is not enabled!
[0.802660] xen: -- pirq=22 - irq=28 (gsi=28)
[0.802666] xen-platform-pci :00:03.0: PCI INT A - GSI 28 (level, low)
- IRQ 28
[0.804744] Grant table initialized
[0.809132] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[0.839167] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[0.894633] 00:0a: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[0.904439] Linux agpgart interface v0.103
[0.904599] i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at
0x60,0x64 irq 1,12
[0.906591] serio: i8042 KBD port at 0x60,0x64 irq 1
[0.906603] serio: i8042 AUX port at 0x60,0x64 irq 12
[0.906968] mousedev: PS/2 mouse device common for all mice
[0.907810] input: AT Translated Set 2 keyboard as
/devices/platform/i8042/serio0/input/input0
[0.908587] rtc_cmos 00:05: rtc core: registered rtc_cmos as rtc0
[0.908630] rtc0: alarms up to one day, 114 bytes nvram
[0.908645] cpuidle: using governor ladder
[0.908648] cpuidle: using governor menu
[0.908933] TCP cubic registered
[0.909141] NET: Registered protocol family
Bug#692043: marked as done (net: do not disable sg for packets requiring no checksum)
Your message dated Thu, 1 Nov 2012 09:12:46 -0700
with message-id 20121101161246.GB5595@elie.Belkin
and subject line Re: net: do not disable sg for packets requiring no checksum
has caused the Debian Bug report #692043,
regarding net: do not disable sg for packets requiring no checksum
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.)
--
692043: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692043
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: src:linux
Version: 3.2.23-1
Severity: important
Dear Maintainer,
A regression appearing upstream after 2.6.38 (so not in squeeze) appears
in wheezy. The fix is in the upstream 3.2.y stable Linux kernel maintained
by Ben Hutchings, so it's probably on its way into wheezy, but I didn't
see any bug for it, so I figured I'd reach out.
Here is the commit from 3.2.y, with the changelog describing the user
impact, felt most keenly by debian users who download the open source aoe
driver directly from coraid.com. It includes the simple fix.
commit 9d222e395fc51081a77bac4168141e289dff2d4b
Author: Ed Cashin ecas...@coraid.com
Date: Wed Sep 19 15:49:00 2012 +
net: do not disable sg for packets requiring no checksum
[ Upstream commit c0d680e577ff171e7b37dbdb1b1bf5451e851f04 ]
A change in a series of VLAN-related changes appears to have
inadvertently disabled the use of the scatter gather feature of
network cards for transmission of non-IP ethernet protocols like ATA
over Ethernet (AoE). Below is a reference to the commit that
introduces a harmonize_features function that turns off scatter
gather when the NIC does not support hardware checksumming for the
ethernet protocol of an sk buff.
commit f01a5236bd4b140198fbcc550f085e8361fd73fa
Author: Jesse Gross je...@nicira.com
Date: Sun Jan 9 06:23:31 2011 +
net offloading: Generalize netif_get_vlan_features().
The can_checksum_protocol function is not equipped to consider a
protocol that does not require checksumming. Calling it for a
protocol that requires no checksum is inappropriate.
The patch below has harmonize_features call can_checksum_protocol when
the protocol needs a checksum, so that the network layer is not forced
to perform unnecessary skb linearization on the transmission of AoE
packets. Unnecessary linearization results in decreased performance
and increased memory pressure, as reported here:
http://www.spinics.net/lists/linux-mm/msg15184.html
The problem has probably not been widely experienced yet, because
only recently has the kernel.org-distributed aoe driver acquired the
ability to use payloads of over a page in size, with the patchset
recently included in the mm tree:
https://lkml.org/lkml/2012/8/28/140
The coraid.com-distributed aoe driver already could use payloads of
greater than a page in size, but its users generally do not use the
newest kernels.
Signed-off-by: Ed Cashin ecas...@coraid.com
Signed-off-by: David S. Miller da...@davemloft.net
Signed-off-by: Ben Hutchings b...@decadent.org.uk
diff --git a/net/core/dev.c b/net/core/dev.c
index 611294a..abe1147 100644
--- a/net/core/dev.c
+++ b/net/core/dev.c
@@ -2108,7 +2108,8 @@ static bool can_checksum_protocol(unsigned long features,
__be16 protocol)
static u32 harmonize_features(struct sk_buff *skb, __be16 protocol, u32
features)
{
- if (!can_checksum_protocol(features, protocol)) {
+ if (skb-ip_summed != CHECKSUM_NONE
+ !can_checksum_protocol(features, protocol)) {
features = ~NETIF_F_ALL_CSUM;
features = ~NETIF_F_SG;
} else if (illegal_highdma(skb-dev, skb)) {
-- Package-specific info:
** Version:
Linux version 3.2.0-3-amd64 (Debian 3.2.23-1) (debian-kernel@lists.debian.org)
(gcc version 4.6.3 (Debian 4.6.3-8) ) #1 SMP Mon Jul 23 02:45:17 UTC 2012
** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.2.0-3-amd64
root=UUID=4cb7446d-c561-4184-b8ec-486ef365455b ro quiet
** Not tainted
** Kernel log:
[0.801610] acpiphp: Slot [30] registered
[0.801693] acpiphp: Slot [31] registered
[0.802476] intel_idle: does not run on family 6 model 15
[0.802532] ERST: Table is not found!
[0.802535] GHES: HEST is not enabled!
[0.802660] xen: -- pirq=22 - irq=28 (gsi=28)
[0.802666] xen-platform-pci :00:03.0: PCI INT A - GSI 28 (level, low)
- IRQ 28
[0.804744] Grant table initialized
[0.809132] Serial: 8250/16550 driver, 4
Bug#692025: linux: internet connection refused after new route
On 11/01/2012 03:13 PM, Ben Hutchings wrote: On Thu, 2012-11-01 at 13:58 +0100, Patrik Nilsson wrote: Package: linux Version: linux-image Can we have a real version number please? (/proc/version will show the Debian package version for the running kernel). Linux version 2.6.32-5-686 (Debian 2.6.32-46) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Sun Sep 23 09:49:36 UTC 2012 Severity: important Tags: upstream When one lan interface is connected and you try to connect an other one, often you can't connect to the Internet after that. You need to retry the connection. I suspect this bug is when a task (i.e. ntp, virus updater, ...) tries to connect to the Internet through a socket using the first interface, holds it open, the kernel won't reroute to the new one and you need try to again. Example: When a openvpn connection is made and initiation is okey, but you can't connect to the Internet, through the openvpn-connection. Retrying it and you can connect. Example: When one wlan connection is up and you try to connect throught an other one, you need to retry. I have tested both examples with lftp trying to connect to an IP-address and you cant' connect as long as lftp's socket is in effect. Please explain in more detail what you're doing: - All the commands you run to reconfigure and use the network - The routing table (as shown by 'ip r') after each reconfiguration Openvpn reconfigurates the routing by itself, and no warnings are issued about the route or the connection. Everything seems to be okay. Example Openvpn: 1) Connect to an openvpn server using: /usr/sbin/openvpn --config $config --auth-user-pass account.txt --mute-replay-warnings 2) Almost every time the first connection attempt fails, and I need to retry the connection. Example WLAN: 1) Connect WLAN from your computer to a router 1 2) run lftp 192.168.0.123 -e set ssl:verify-certificate no;set dns:fatal-timeout 1m; set net:idle 30s; set net:max-retries 10; set net:reconnect-interval-multiplier 1; set net:timeout 30s; set xfer:disk-full-fatal true; set net:reconnect-interval-base 5; cd \test\; mkdir -p \test\; set cmd:fail-exit yes; put -E -c \test\ -o \test\; quit 3) Connect WLAN to router 2 I have a script that does this for me. When the script is running, the connection change fails. Of course it didn't do it when I tried to get the bug showing from the command line. Ben. -- 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/5092a39f.4090...@gmail.com
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 #384922 (http://bugs.debian.org/384922) # Bug title: Please support squash_gids option for NFS # * http://bugzilla.kernel.org/show_bug.cgi?id=14295 # * remote status changed: NEW - RESOLVED # * remote resolution changed: (?) - WILL-NOT-FIX # * closed upstream tags 384922 + fixed-upstream Bug #384922 [linux-2.6] Please support squash_gids option for NFS Added tag(s) fixed-upstream. usertags 384922 - status-NEW Usertags were: status-NEW. Usertags are now: . usertags 384922 + status-RESOLVED resolution-WILL-NOT-FIX There were no usertags set. Usertags are now: status-RESOLVED resolution-WILL-NOT-FIX. # remote status report for #425250 (http://bugs.debian.org/425250) # Bug title: linux-source-2.6.18 : make pdfdocs in the linux-source-2.6.18 fails. # * http://bugzilla.kernel.org/show_bug.cgi?id=11084 # * remote status changed: NEW - RESOLVED # * remote resolution changed: (?) - OBSOLETE # * closed upstream tags 425250 + fixed-upstream Bug #425250 [linux-2.6] linux-source-2.6.18 : make pdfdocs in the linux-source-2.6.18 fails. Added tag(s) fixed-upstream. usertags 425250 - status-NEW Usertags were: status-NEW. Usertags are now: . usertags 425250 + status-RESOLVED resolution-OBSOLETE There were no usertags set. Usertags are now: status-RESOLVED resolution-OBSOLETE. # remote status report for #490903 (http://bugs.debian.org/490903) # Bug title: regression: kernel panic on boot with megaraid_mbox driver # * http://bugzilla.kernel.org/show_bug.cgi?id=11194 # * remote status changed: NEW - RESOLVED # * remote resolution changed: (?) - OBSOLETE # * closed upstream tags 490903 + fixed-upstream Bug #490903 [linux-2.6] regression: kernel panic on boot with megaraid_mbox driver Added tag(s) fixed-upstream. usertags 490903 - status-NEW Usertags were: status-NEW. Usertags are now: . usertags 490903 + status-RESOLVED resolution-OBSOLETE There were no usertags set. Usertags are now: status-RESOLVED resolution-OBSOLETE. # remote status report for #584724 (http://bugs.debian.org/584724) # Bug title: linux-image-2.6.32-5-amd64: NETDEV WATCHDOG: (via-rhine): transmit queue 0 timed out # * http://bugzilla.kernel.org/show_bug.cgi?id=11663 # * remote status changed: NEW - RESOLVED # * remote resolution changed: (?) - OBSOLETE # * closed upstream tags 584724 + fixed-upstream Bug #584724 [linux-2.6] linux-image-2.6.32-5-amd64: NETDEV WATCHDOG: (via-rhine): transmit queue 0 timed out Added tag(s) fixed-upstream. usertags 584724 - status-NEW Usertags were: status-NEW. Usertags are now: . usertags 584724 + status-RESOLVED resolution-OBSOLETE There were no usertags set. Usertags are now: status-RESOLVED resolution-OBSOLETE. # remote status report for #599262 (http://bugs.debian.org/599262) # Bug title: usbip: After detach remote usb device the system is unusable # * http://bugzilla.kernel.org/show_bug.cgi?id=13054 # * remote status changed: NEW - RESOLVED # * remote resolution changed: (?) - OBSOLETE # * closed upstream tags 599262 + fixed-upstream Bug #599262 [linux-2.6] usbip: After detach remote usb device the system is unusable Added tag(s) fixed-upstream. usertags 599262 - status-NEW Usertags were: status-NEW. Usertags are now: . usertags 599262 + status-RESOLVED resolution-OBSOLETE There were no usertags set. Usertags are now: status-RESOLVED resolution-OBSOLETE. thanks Stopping processing here. Please contact me if you need assistance. -- 384922: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=384922 425250: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=425250 490903: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=490903 584724: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584724 599262: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599262 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.135179366514631.transcr...@bugs.debian.org
[bts-link] source package src:linux-2.6
# # bts-link upstream status pull for source package src: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 #508866 (http://bugs.debian.org/508866) # Bug title: linux-image-2.6.26-1-amd64: NFS going stale for stat() for renamed files like .Xauthority # * http://bugzilla.kernel.org/show_bug.cgi?id=12557 # * remote status changed: REOPENED - CLOSED # * remote resolution changed: (?) - DOCUMENTED usertags 508866 - status-REOPENED usertags 508866 + status-CLOSED resolution-DOCUMENTED 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/20121101181125.13035.20562.btsl...@sonntag.debian.org
[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 #384922 (http://bugs.debian.org/384922) # Bug title: Please support squash_gids option for NFS # * http://bugzilla.kernel.org/show_bug.cgi?id=14295 # * remote status changed: NEW - RESOLVED # * remote resolution changed: (?) - WILL-NOT-FIX # * closed upstream tags 384922 + fixed-upstream usertags 384922 - status-NEW usertags 384922 + status-RESOLVED resolution-WILL-NOT-FIX # remote status report for #425250 (http://bugs.debian.org/425250) # Bug title: linux-source-2.6.18 : make pdfdocs in the linux-source-2.6.18 fails. # * http://bugzilla.kernel.org/show_bug.cgi?id=11084 # * remote status changed: NEW - RESOLVED # * remote resolution changed: (?) - OBSOLETE # * closed upstream tags 425250 + fixed-upstream usertags 425250 - status-NEW usertags 425250 + status-RESOLVED resolution-OBSOLETE # remote status report for #490903 (http://bugs.debian.org/490903) # Bug title: regression: kernel panic on boot with megaraid_mbox driver # * http://bugzilla.kernel.org/show_bug.cgi?id=11194 # * remote status changed: NEW - RESOLVED # * remote resolution changed: (?) - OBSOLETE # * closed upstream tags 490903 + fixed-upstream usertags 490903 - status-NEW usertags 490903 + status-RESOLVED resolution-OBSOLETE # remote status report for #584724 (http://bugs.debian.org/584724) # Bug title: linux-image-2.6.32-5-amd64: NETDEV WATCHDOG: (via-rhine): transmit queue 0 timed out # * http://bugzilla.kernel.org/show_bug.cgi?id=11663 # * remote status changed: NEW - RESOLVED # * remote resolution changed: (?) - OBSOLETE # * closed upstream tags 584724 + fixed-upstream usertags 584724 - status-NEW usertags 584724 + status-RESOLVED resolution-OBSOLETE # remote status report for #599262 (http://bugs.debian.org/599262) # Bug title: usbip: After detach remote usb device the system is unusable # * http://bugzilla.kernel.org/show_bug.cgi?id=13054 # * remote status changed: NEW - RESOLVED # * remote resolution changed: (?) - OBSOLETE # * closed upstream tags 599262 + fixed-upstream usertags 599262 - status-NEW usertags 599262 + status-RESOLVED resolution-OBSOLETE 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/20121101181125.13035.99343.btsl...@sonntag.debian.org
Processed: Re: linux: internet connection refused after new route
Processing commands for cont...@bugs.debian.org: reassign 692025 src:linux-2.6 2.6.32-46 Bug #692025 [linux] linux: internet connection refused after new route Bug reassigned from package 'linux' to 'src:linux-2.6'. No longer marked as found in versions linux-image. Ignoring request to alter fixed versions of bug #692025 to the same values previously set Bug #692025 [src:linux-2.6] linux: internet connection refused after new route Marked as found in versions linux-2.6/2.6.32-46. End of message, stopping processing here. Please contact me if you need assistance. -- 692025: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692025 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.135179558028180.transcr...@bugs.debian.org
Bug#384922: NFS insecure without support for squashing multiple groups
reassign 384922 src:linux linux-2.6/2.6.12-1 found 384922 linux/3.2.32-1 tags 384922 - fixed-upstream + wontfix upstream quit Hi again, In February, Paul Szabo wrote: Do I understand correctly that you are requesting an export or mountd option filter_gid, which would behave like --manage-gids except it transforms the effective gid to anongid when the specified gid is not a group the user belongs to? I haven't carefully looked over the protocol specs but at first glance that seems sensible. Yes, my exact wish. It still seems like a sensible request, but nobody is working on this, so I'm marking it accordingly. Please keep the upstream report updated if you make progress. Regards, Jonathan -- 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/20121101185606.GA6580@elie.Belkin
Processed: Re: NFS insecure without support for squashing multiple groups
Processing commands for cont...@bugs.debian.org: reassign 384922 src:linux linux-2.6/2.6.12-1 Bug #384922 [linux-2.6] Please support squash_gids option for NFS Bug reassigned from package 'linux-2.6' to 'src:linux'. Ignoring request to alter found versions of bug #384922 to the same values previously set Ignoring request to alter fixed versions of bug #384922 to the same values previously set Bug #384922 [src:linux] Please support squash_gids option for NFS Marked as found in versions linux-2.6/2.6.12-1. found 384922 linux/3.2.32-1 Bug #384922 [src:linux] Please support squash_gids option for NFS Marked as found in versions linux/3.2.32-1. tags 384922 - fixed-upstream + wontfix upstream Bug #384922 [src:linux] Please support squash_gids option for NFS Removed tag(s) fixed-upstream. Bug #384922 [src:linux] Please support squash_gids option for NFS Added tag(s) upstream and wontfix. quit Stopping processing here. Please contact me if you need assistance. -- 384922: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=384922 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.1351796183736.transcr...@bugs.debian.org
Bug#686640: marked as done (linux/snd_hda_intel: no master volume control since 3.4)
Your message dated Thu, 1 Nov 2012 12:07:29 -0700 with message-id 20121101190729.GA8737@elie.Belkin and subject line Re: [3.3-3.4 regression] snd_hda_intel: no master volume control has caused the Debian Bug report #686640, regarding linux/snd_hda_intel: no master volume control since 3.4 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.) -- 686640: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686640 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src Version: 3.4.4-1~experimental.1 Severity: important Tags: upstream Since Linux 3.4 there's no real Master volume control here, only the Mute switch. The issue has been reported few times on internet already; however after inspecting upstream changesets between 3.3 and 3.4 I fail to find one which causes this odd behaviour (probably, bisect is needed). Linux 3.5 currently demonstrates the same issue. Simple mixer control 'Master',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Simple mixer control 'PCM',0 Capabilities: pvolume pswitch penum Playback channels: Front Left - Front Right Limits: Playback 0 - 31 Mono: Front Left: Playback 24 [77%] [-10.50dB] [on] Front Right: Playback 24 [77%] [-10.50dB] [on] Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [off] Simple mixer control 'IEC958 Default PCM',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Simple mixer control 'Capture',0 Capabilities: cvolume cswitch penum Capture channels: Front Left - Front Right Limits: Capture 0 - 15 Front Left: Capture 15 [100%] [22.50dB] [on] Front Right: Capture 15 [100%] [22.50dB] [on] Simple mixer control 'Digital',0 Capabilities: cvolume penum Capture channels: Front Left - Front Right Limits: Capture 0 - 120 Front Left: Capture 60 [50%] [0.00dB] Front Right: Capture 60 [50%] [0.00dB] Simple mixer control 'Input Source',0 Capabilities: cenum Items: 'Internal Mic' 'Mic' Item0: 'Internal Mic' Simple mixer control 'Mux',0 Capabilities: cvolume penum Capture channels: Front Left - Front Right Limits: Capture 0 - 4 Front Left: Capture 0 [0%] [0.00dB] Front Right: Capture 0 [0%] [0.00dB] -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information not available ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub [8086:27a0] (rev 03) Subsystem: Dell Device [1028:01c2] 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 Capabilities: access denied Kernel driver in use: agpgart-intel 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:01c2] 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 Interrupt: pin A routed to IRQ 16 Region 0: Memory at eff0 (32-bit, non-prefetchable) [size=512K] Region 1: I/O ports at eff8 [size=8] Region 2: Memory at d000 (32-bit, prefetchable) [size=256M] Region 3: Memory at efec (32-bit, non-prefetchable) [size=256K] Expansion ROM at unassigned [disabled] Capabilities: access denied Kernel driver in use: i915 00:02.1 Display controller [0380]: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [8086:27a6] (rev 03) Subsystem: Dell Device [1028:01c2] 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 Region 0: Memory at eff8 (32-bit, non-prefetchable) [size=512K] Capabilities: access denied 00:1b.0 Audio device [0403]: Intel Corporation N10/ICH 7 Family High Definition Audio Controller [8086:27d8] (rev 01) Subsystem: Dell Device [1028:01c2] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Bug#690011: [PATCH] linux-tools: update to 3.6
Jonathan Nieder wrote: The following patch updates linux-tools trunk to 3.6 and works fine for me. Thanks for applying it. Ok to upload? There have been a couple of requests for a linux-tools-3.6 package in experimental, and fixing #573483 means we need linux-kbuild-3.6. Hope that helps, Jonathan -- 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/20121101193304.GA7833@elie.Belkin
Bug#684666: R: Bug#684666: AMI BIOS detected: BIOS may corrupt low RAM, working around it.
Hi, The second (B) bank of the 8gB set is working fine. uptime is: 20:54:53 up 5 days, 9:18, 7 users, load average: 0.68, 0.56, 0.53 and i had no crashes, and right now i 've just tested also file transfer (via tar + nc), to see if i have md5sums inconsistencies and it works good , no data has been corrupted . :) So i think the problem could be in the other bank (A) i unsuccessfully used last time. Now i'm going to memtest it (A) with memtest86+ for some hours, to see if it's the root of all the problems. ciao, Asdrubale -- 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/27615090.8858801351801457093.JavaMail.defaultUser@defaultHost
Bug#692067: linux-image-3.6-trunk-amd64: Early panic with 3.6.4 on amd64
Package: src:linux Version: 3.6.4-1~experimental.1 Severity: normal Dear Maintainer, When booting linux-image-3.6-trunk-amd64, I get the following: PANIC: early exception 0f rip 10:8136438d error 0 cr 2 0 $ addr2line -fe /usr/lib/debug/boot/vmlinux-3.6-trunk-amd64 8136438d arch_local_irq_enable /build/buildd- linux_3.6.4-1~experimental.1-amd64-QnAy6j/linux-3.6.4/kernel/panic.c:176 The system boots and runs fine with linux-image-3.5-trunk-amd64 -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: To be filled by O.E.M. product_name: To be filled by O.E.M. product_version: To be filled by O.E.M. chassis_vendor: To Be Filled By O.E.M. chassis_version: To Be Filled By O.E.M. bios_vendor: American Megatrends Inc. bios_version: 1208 board_vendor: ASUSTeK COMPUTER INC. board_name: M5A99X EVO board_version: Rev 1.xx ** PCI devices: 00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] nee ATI RD890 PCI to PCI bridge (external gfx0 port B) [1002:5a14] (rev 02) Subsystem: Advanced Micro Devices [AMD] nee ATI RD890 PCI to PCI bridge (external gfx0 port B) [1002:5a14] 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- Capabilities: access denied 00:02.0 PCI bridge [0604]: Advanced Micro Devices [AMD] nee ATI RD890 PCI to PCI bridge (PCI express gpp port B) [1002:5a16] (prog-if 00 [Normal decode]) 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, Cache Line Size: 64 bytes Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: e000-efff Memory behind bridge: fc00-fe0f Prefetchable memory behind bridge: d000-dbff Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- BridgeCtl: Parity- SERR- NoISA- VGA+ MAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: access denied Kernel driver in use: pcieport 00:04.0 PCI bridge [0604]: Advanced Micro Devices [AMD] nee ATI RD890 PCI to PCI bridge (PCI express gpp port D) [1002:5a18] (prog-if 00 [Normal decode]) 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, Cache Line Size: 64 bytes Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 I/O behind bridge: d000-dfff Prefetchable memory behind bridge: dc10-dc1f Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: access denied Kernel driver in use: pcieport 00:05.0 PCI bridge [0604]: Advanced Micro Devices [AMD] nee ATI RD890 PCI to PCI bridge (PCI express gpp port E) [1002:5a19] (prog-if 00 [Normal decode]) 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, Cache Line Size: 64 bytes Bus: primary=00, secondary=03, subordinate=03, sec-latency=0 Memory behind bridge: fe50-fe5f Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: access denied Kernel driver in use: pcieport 00:06.0 PCI bridge [0604]: Advanced Micro Devices [AMD] nee ATI RD890 PCI to PCI bridge (PCI express gpp port F) [1002:5a1a] (prog-if 00 [Normal decode]) 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, Cache Line Size: 64 bytes Bus: primary=00, secondary=04, subordinate=04, sec-latency=0 I/O behind bridge: c000-cfff Memory behind bridge: fe40-fe4f Prefetchable memory behind bridge: dc00-dc0f Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- Reset- FastB2B-
Bug#684240: [wheezy] lenovo t61 laptop fails to shutdown
I followed your instructions below and again got to a black screen and an unresponsive laptop. I had to use a recover disk to go back to the previous configuration. Would the /var/log/messages file be useful? Regards, Luis Could you try nouveau again using this information? This experiment would be using the usual 3.2.y-based kernel from sid or wheezy. It works like this: 1. Run update-alternatives --config glx and choose mesa. 2. Temporarily comment out the uvesafb line in /etc/initramfs-tools/modules. 3. Move /etc/X11/xorg.conf, /etc/modprobe.d/nvidia-kernel-common.conf, and /etc/modprobe.d/uvesafb.conf temporarily out of the way. 4. Blacklist nvidia in /etc/modprobe.d. 5. Reboot. To restore your old settings: 4^-1. Unblacklist nvidia in /etc/modprobe.d. 3^-1. Move /etc/X11/xorg.conf, /etc/modprobe.d/nvidia-kernel-common.conf, and uvesafb.conf back into place. 2^-1. Uncomment uvesafb in /etc/initramfs-tools/modules. 5^-1. Reboot. 1^-1. update-alternatives --config glx again. Curious, Jonathan -- o W. Luis Mochán, | tel:(52)(777)329-1734 /(*) Instituto de Ciencias Físicas, UNAM | fax:(52)(777)317-5388 `/ /\ Apdo. Postal 48-3, 62251 | (*)/\/ \ Cuernavaca, Morelos, México | moc...@fis.unam.mx /\_/\__/ O ascii ribbon campaign - stop html mail - www.asciiribbon.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/20121101215232.gi30...@em.fis.unam.mx
Bug#684240: [wheezy] lenovo t61 laptop fails to shutdown
Luis Mochan wrote: I followed your instructions below and again got to a black screen and an unresponsive laptop. I had to use a recover disk to go back to the previous configuration. Would the /var/log/messages file be useful? Yes, a kernel log of that boot would be useful. Thanks, Jonathan -- 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/20121101223317.GF6213@elie.Belkin
Bug#692043: marked as done (net: do not disable sg for packets requiring no checksum)
Your message dated Thu, 1 Nov 2012 22:51:41 +
with message-id 20121101225141.gj13...@decadent.org.uk
and subject line Re: Bug#692043: net: do not disable sg for packets requiring
no checksum
has caused the Debian Bug report #692043,
regarding net: do not disable sg for packets requiring no checksum
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.)
--
692043: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692043
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: src:linux
Version: 3.2.23-1
Severity: important
Dear Maintainer,
A regression appearing upstream after 2.6.38 (so not in squeeze) appears
in wheezy. The fix is in the upstream 3.2.y stable Linux kernel maintained
by Ben Hutchings, so it's probably on its way into wheezy, but I didn't
see any bug for it, so I figured I'd reach out.
Here is the commit from 3.2.y, with the changelog describing the user
impact, felt most keenly by debian users who download the open source aoe
driver directly from coraid.com. It includes the simple fix.
commit 9d222e395fc51081a77bac4168141e289dff2d4b
Author: Ed Cashin ecas...@coraid.com
Date: Wed Sep 19 15:49:00 2012 +
net: do not disable sg for packets requiring no checksum
[ Upstream commit c0d680e577ff171e7b37dbdb1b1bf5451e851f04 ]
A change in a series of VLAN-related changes appears to have
inadvertently disabled the use of the scatter gather feature of
network cards for transmission of non-IP ethernet protocols like ATA
over Ethernet (AoE). Below is a reference to the commit that
introduces a harmonize_features function that turns off scatter
gather when the NIC does not support hardware checksumming for the
ethernet protocol of an sk buff.
commit f01a5236bd4b140198fbcc550f085e8361fd73fa
Author: Jesse Gross je...@nicira.com
Date: Sun Jan 9 06:23:31 2011 +
net offloading: Generalize netif_get_vlan_features().
The can_checksum_protocol function is not equipped to consider a
protocol that does not require checksumming. Calling it for a
protocol that requires no checksum is inappropriate.
The patch below has harmonize_features call can_checksum_protocol when
the protocol needs a checksum, so that the network layer is not forced
to perform unnecessary skb linearization on the transmission of AoE
packets. Unnecessary linearization results in decreased performance
and increased memory pressure, as reported here:
http://www.spinics.net/lists/linux-mm/msg15184.html
The problem has probably not been widely experienced yet, because
only recently has the kernel.org-distributed aoe driver acquired the
ability to use payloads of over a page in size, with the patchset
recently included in the mm tree:
https://lkml.org/lkml/2012/8/28/140
The coraid.com-distributed aoe driver already could use payloads of
greater than a page in size, but its users generally do not use the
newest kernels.
Signed-off-by: Ed Cashin ecas...@coraid.com
Signed-off-by: David S. Miller da...@davemloft.net
Signed-off-by: Ben Hutchings b...@decadent.org.uk
diff --git a/net/core/dev.c b/net/core/dev.c
index 611294a..abe1147 100644
--- a/net/core/dev.c
+++ b/net/core/dev.c
@@ -2108,7 +2108,8 @@ static bool can_checksum_protocol(unsigned long features,
__be16 protocol)
static u32 harmonize_features(struct sk_buff *skb, __be16 protocol, u32
features)
{
- if (!can_checksum_protocol(features, protocol)) {
+ if (skb-ip_summed != CHECKSUM_NONE
+ !can_checksum_protocol(features, protocol)) {
features = ~NETIF_F_ALL_CSUM;
features = ~NETIF_F_SG;
} else if (illegal_highdma(skb-dev, skb)) {
-- Package-specific info:
** Version:
Linux version 3.2.0-3-amd64 (Debian 3.2.23-1) (debian-kernel@lists.debian.org)
(gcc version 4.6.3 (Debian 4.6.3-8) ) #1 SMP Mon Jul 23 02:45:17 UTC 2012
** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.2.0-3-amd64
root=UUID=4cb7446d-c561-4184-b8ec-486ef365455b ro quiet
** Not tainted
** Kernel log:
[0.801610] acpiphp: Slot [30] registered
[0.801693] acpiphp: Slot [31] registered
[0.802476] intel_idle: does not run on family 6 model 15
[0.802532] ERST: Table is not found!
[0.802535] GHES: HEST is not enabled!
[0.802660] xen: -- pirq=22 - irq=28 (gsi=28)
[0.802666] xen-platform-pci :00:03.0: PCI INT A - GSI 28 (level, low)
- IRQ 28
[0.804744] Grant table initialized
[0.809132] Serial:
Bug#692043: closed by Ben Hutchings b...@decadent.org.uk (Re: Bug#692043: net: do not disable sg for packets requiring no checksum)
On Nov 1, 2012, at 6:54 PM, Debian Bug Tracking System wrote: The above version has this fix and should be unblocked to enter testing in the next few days. Great. Thanks for the update and for your help in polishing the fix a few weeks ago. -- Ed Cashin ecas...@coraid.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/64c87611-5fde-4a9f-b0c3-6cd81f0e9...@coraid.com
Bug#684240: [wheezy] lenovo t61 laptop fails to shutdown
Luis Mochan wrote: I followed your instructions below and again got to a black screen and an unresponsive laptop. I had to use a recover disk to go back to the previous configuration. Would the /var/log/messages file be useful? To avoid wasting the round-trip: 1. Yes, a kernel log from the failing boot would be very helpful, since then we might learn something about why it failed. :) 2. Testing 3.6.y from experimental as well using the nouveau driver with uvesafb disabled would be nice. Thanks, Jonathan -- 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/20121102005719.GA2984@elie.Belkin
Bug#692067: [3.5.5-3.6.4 regression] Early panic with 3.6.4 on amd64
# regression severity 692067 important quit Hi Robert, Robert Keevil wrote: When booting linux-image-3.6-trunk-amd64, I get the following: PANIC: early exception 0f rip 10:8136438d error 0 cr 2 0 Thanks for reporting it. If you pass mem=4G on the kernel command line, does that change anything? Thanks and sorry for the trouble, Jonathan -- 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/20121102011051.GB2984@elie.Belkin
Processed: Re: [3.5.5-3.6.4 regression] Early panic with 3.6.4 on amd64
Processing commands for cont...@bugs.debian.org: # regression severity 692067 important Bug #692067 [src:linux] linux-image-3.6-trunk-amd64: Early panic with 3.6.4 on amd64 Severity set to 'important' from 'normal' quit Stopping processing here. Please contact me if you need assistance. -- 692067: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692067 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.135181866122881.transcr...@bugs.debian.org
Bug#692067: [3.5.5-3.6.4 regression] Early panic with 3.6.4 on amd64
On 01/11/12 20:10, Jonathan Nieder wrote: Thanks for reporting it. If you pass mem=4G on the kernel command line, does that change anything? Thanks and sorry for the trouble, Jonathan It boots and runs fine with that option. Thanks Robert -- 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/50932981.1040...@gmail.com
Bug#692067: [3.5.5-3.6.4 regression] Early panic with 3.6.4 on amd64
tags 692067 + upstream fixed-upstream quit Robert Keevil wrote: On 01/11/12 20:10, Jonathan Nieder wrote: Thanks for reporting it. If you pass mem=4G on the kernel command line, does that change anything? Thanks and sorry for the trouble, Jonathan It boots and runs fine with that option. Yay, thanks for the quick response. I suspect this is fixed by 844ab6f993b1 x86, mm: Find_early_table_space based on ranges that are actually being mapped which is part of 3.6.5. -- 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/20121102021402.GA5371@elie.Belkin
Processed: Re: [3.5.5-3.6.4 regression] Early panic with 3.6.4 on amd64
Processing commands for cont...@bugs.debian.org: tags 692067 + upstream fixed-upstream Bug #692067 [src:linux] linux-image-3.6-trunk-amd64: Early panic with 3.6.4 on amd64 Added tag(s) upstream and fixed-upstream. quit Stopping processing here. Please contact me if you need assistance. -- 692067: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692067 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.135182245620960.transcr...@bugs.debian.org
Processed: Re: NFS going stale for stat() for renamed files like .Xauthority
Processing commands for cont...@bugs.debian.org: reassign 508866 src:linux linux-2.6/2.6.26-10 Bug #508866 [src:linux-2.6] linux-image-2.6.26-1-amd64: NFS going stale for stat() for renamed files like .Xauthority Bug reassigned from package 'src:linux-2.6' to 'src:linux'. No longer marked as found in versions linux-2.6/2.6.26-10. Ignoring request to alter fixed versions of bug #508866 to the same values previously set Bug #508866 [src:linux] linux-image-2.6.26-1-amd64: NFS going stale for stat() for renamed files like .Xauthority Marked as found in versions linux-2.6/2.6.26-10. found 508866 linux-2.6/3.2.1-1, linux-2.6/3.2.9-1 Bug #508866 [src:linux] linux-image-2.6.26-1-amd64: NFS going stale for stat() for renamed files like .Xauthority Marked as found in versions linux-2.6/3.2.1-1 and linux-2.6/3.2.9-1. tags 508866 - patch fixed-upstream Bug #508866 [src:linux] linux-image-2.6.26-1-amd64: NFS going stale for stat() for renamed files like .Xauthority Removed tag(s) fixed-upstream and patch. forwarded 508866 http://thread.gmane.org/gmane.linux.kernel/1383596 Bug #508866 [src:linux] linux-image-2.6.26-1-amd64: NFS going stale for stat() for renamed files like .Xauthority Changed Bug forwarded-to-address to 'http://thread.gmane.org/gmane.linux.kernel/1383596' from 'http://bugzilla.kernel.org/show_bug.cgi?id=12557' # difficult severity 508866 wishlist Bug #508866 [src:linux] linux-image-2.6.26-1-amd64: NFS going stale for stat() for renamed files like .Xauthority Severity set to 'wishlist' from 'normal' End of message, stopping processing here. Please contact me if you need assistance. -- 508866: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=508866 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.13518244521703.transcr...@bugs.debian.org
Bug#599262: usbip: After detach remote usb device the system is unusable
Hi, willem kuyn wrote: [Subject: test information for linux-2.6.38-2] The freeze is not longer occurring in the latest kernel but after loading the module vhci_hcd there are a lot of messages in the kernel log. INFO: task vhci_rx:xx blocked for more than 120 seconds. and INFO: task vhci_tx:xx blocked for more than 120 seconds. What can I do to solve this problem? I dunno. :) What kernel are you using now, and is it affected? Thanks, Jonathan -- 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/20121102025418.GA28645@elie.Belkin
Processed: Re: usbip: After detach remote usb device the system is unusable
Processing commands for cont...@bugs.debian.org: tags 599262 - fixed-upstream + moreinfo Bug #599262 [linux-2.6] usbip: After detach remote usb device the system is unusable Removed tag(s) fixed-upstream. Bug #599262 [linux-2.6] usbip: After detach remote usb device the system is unusable Added tag(s) moreinfo. # usb folks hate bugzilla, I'm told notforwarded 599262 Bug #599262 [linux-2.6] usbip: After detach remote usb device the system is unusable Unset Bug forwarded-to-address End of message, stopping processing here. Please contact me if you need assistance. -- 599262: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599262 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.13518249304895.transcr...@bugs.debian.org
Bug#684240: [wheezy] lenovo t61 laptop fails to shutdown
I guess I made some mistake, as there are messages labeled uvesafb in all the boot attempts this afternoon. Maybe I should have blacklisted uvesafb besides commenting it out from /etc/initramfs-tools/modules. I'll try this during the weekend later. Regards, Luis On Thu, Nov 01, 2012 at 05:57:19PM -0700, Jonathan Nieder wrote: Luis Mochan wrote: I followed your instructions below and again got to a black screen and an unresponsive laptop. I had to use a recover disk to go back to the previous configuration. Would the /var/log/messages file be useful? To avoid wasting the round-trip: 1. Yes, a kernel log from the failing boot would be very helpful, since then we might learn something about why it failed. :) 2. Testing 3.6.y from experimental as well using the nouveau driver with uvesafb disabled would be nice. Thanks, Jonathan -- o W. Luis Mochán, | tel:(52)(777)329-1734 /(*) Instituto de Ciencias Físicas, UNAM | fax:(52)(777)317-5388 `/ /\ Apdo. Postal 48-3, 62251 | (*)/\/ \ Cuernavaca, Morelos, México | moc...@fis.unam.mx /\_/\__/ O ascii ribbon campaign - stop html mail - www.asciiribbon.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/20121102031717.gf2...@em.fis.unam.mx
Bug#684240: [wheezy] lenovo t61 laptop fails to shutdown
Luis Mochan wrote: I guess I made some mistake, as there are messages labeled uvesafb in all the boot attempts this afternoon. Ah, I know what step I left out now. :/ It's update-initramfs -u -k all Sorry about that. -- 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/20121102031902.GD5371@elie.Belkin
Bug#691902: [squeeze-wheezy regression] Unable to shutdown via normal means
Got hit by this on the way... http://forums.debian.net/viewtopic.php?f=17t=60881 Testing halted until this is resolved On Nov 1, 2012 11:04 AM, Janne Boman janne.m.bo...@gmail.com wrote: Ok, I'm going with this image: debian-wheezy-DI-b3-amd64-CD-1.iso (http://cdimage.debian.org/cdimage/wheezy_di_beta3/amd64/iso-cd/) On Thu, Nov 1, 2012 at 10:44 AM, Jonathan Nieder jrnie...@gmail.com wrote: That would be great. If you have time for it, don't forget to file an installation report: http://www.debian.org/releases/wheezy/amd64/apas04.html Thanks, Jonathan
Bug#689420: Re: Linux does not boot on Intel Core i7-3720QM Processor (2.60GHz Turbo)
On Fri, 2012-11-02 at 02:53 +0400, jaakov jaakov wrote: [...] Alas, boot_delay=1000 does not slow down printing. Sorry, I misunderstood where things were going wrong. Apparently the kernel itself is booting just fine, but things go wrong later in the boot sequence. It just introduces a pause right after blanking the screen at boot, but before quickly printing pages of information. Thus, to get usable screenshots from a failing boot, I have to do some preparation. I have two kernels installed, one from testing (linux-image-3.2.0-3-amd64, version 3.2.23-1), and the other from unstable (linux-image-3.2.0-4-amd64, version 3.2.32-1). Both can be run with or without acpi=off, with or without quiet, with or without elevator=noop (currently used, since an SSD is inside), with or without boot_delay=1000, normally or in a repair mode. E. g., attached is a screenshot of a boot of kernel 3.2.0-4, with acpi=off quiet elevator=noop. The machine in the state you see does not boot further but remains responsive to Ctrl+Alt+Del, which performs a reboot. [...] For further testing, please do not use acpi=off. We need to make the normal configuration work, and acpi=off may introduce new and different problems! The interesting thing I see there is the last boot progress message, which is 'Enabling power management...' Is this always the last line of boot progress? If so, please can you edit /etc/init.d/acpi-support, changing the first line from: #!/bin/sh to: #!/bin/sh -x This should make it show the progress of this step in detail. Then take a new screenshot when the boot process hangs again. Also, when the boot process is hung, please do this: 1. Hold down Alt. 2. Press PrtSc and then W. This should produce the message 'SysRq : Show Blocked State'. 3. Release Alt. Assuming that the system log is still working at this point, on the next successful boot you should find some debugging information in /var/log/messages starting with the line 'SysRq : Show Blocked State'. Please send that information. Ben. -- Ben Hutchings I'm always amazed by the number of people who take up solipsism because they heard someone else explain it. - E*Borg on alt.fan.pratchett signature.asc Description: This is a digitally signed message part
Bug#692025: linux: internet connection refused after new route
You haven't sent this: - The routing table (as shown by 'ip r') after each reconfiguration Ben. -- Ben Hutchings I'm always amazed by the number of people who take up solipsism because they heard someone else explain it. - E*Borg on alt.fan.pratchett signature.asc Description: This is a digitally signed message part
ZFS on Linux Support in initramfs-tools
GRUB 2.00 has support for ZFS-on-Linux (the out-of-tree kernel module,
as opposed to the ZFS FUSE implementation). I wrote some of the code
that was added in 2.00; so that is where I fit into all this.
When booting off a ZFS root filesystem, GRUB sets this:
root=ZFS=pool_name/dataset/path
For a real world example, following Solaris's convention, this is what I
use in my HOWTO:
root=ZFS=rpool/ROOT/ubuntu
Darik Horn is doing a wonderful job maintaining ZFS-on-Linux support in
an Ubuntu PPA. With regard to Debian, he's been taking care to keep the
PPA compatible with Debian, and he's working to learn how to get
packages in Debian itself. See the last email on:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686447
initramfs-tools is nicely extensible via boot=foo, where the foo
scripts will then be loaded. Darik has used this for ZFS. However,
boot=zfs still has to be set manually in the GRUB config (or he has to
ship a patched GRUB package). As more things have been upstreamed, we're
getting close to the goal of not needing any modified packages (only the
addition of ZFS packages) for things to work out of the box.
Accordingly, I propose this patch to initramfs-tools:
diff --git a/init b/init
index cb832ff..01210ae 100755
--- a/init
+++ b/init
@@ -103,6 +103,9 @@ for x in $(cat /proc/cmdline); do
/dev/nfs)
[ -z ${BOOT} ] BOOT=nfs
;;
+ ZFS=*)
+ [ -z ${BOOT} ] BOOT=zfs
+ ;;
esac
;;
rootflags=*)
--
Richard
signature.asc
Description: This is a digitally signed message part
Processed: tagging 692067
Processing commands for cont...@bugs.debian.org: tags 692067 + pending Bug #692067 [src:linux] linux-image-3.6-trunk-amd64: Early panic with 3.6.4 on amd64 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 692067: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692067 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.13518345088918.transcr...@bugs.debian.org
