Bug#642911: linux-image-2.6.32-5-686: Network connection fails under heavy load.
Ben Hutchings wrote: Please test version 2.6.32-36 from stable-proposed-updates. Ben. Hi Ben, I tested version 2.6.32-37. The network seems to be more stable, but I still have connection timeouts. There are no more dmesg lines for eth0: link up but my ssh connection still terminates from time to time. Do you need any more log files ? Gerd. -- 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/4e82c0b5.1050...@wolke7.net
Processed: reassign 379339 linux-image-686
Processing commands for cont...@bugs.debian.org: reassign 379339 linux-image-686 Bug #379339 [uswsusp] s2ram/s2disk: potential problems with HPA (host protected area) Bug reassigned from package 'uswsusp' to 'linux-image-686'. Bug No longer marked as found in versions uswsusp/0.2-1. thanks Stopping processing here. Please contact me if you need assistance. -- 379339: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=379339 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.13171973679789.transcr...@bugs.debian.org
Bug#643629: linux-image-2.6.39-bpo.2-amd64: in syslog is a kernel BUG reported
Package: linux-2.6 Version: 2.6.39-3~bpo60+1 Severity: normal This kernel BUG shown in the syslog, and i don't know how critical it is for my file server. google also don't know anything about this bug. -- Package-specific info: ** Version: Linux version 2.6.39-bpo.2-amd64 (Debian 2.6.39-3~bpo60+1) (norb...@tretkowski.de) (gcc version 4.4.5 (Debian 4.4.5-8) ) #1 SMP Tue Jul 26 10:35:23 UTC 2011 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.39-bpo.2-amd64 root=/dev/mapper/atsambas1hg-root ro quiet ** Tainted: D (128) * Kernel has oopsed before. ** Kernel log: [345440.323118] ocfs2: Unmounting device (147,1) on (node 0) [345552.315417] o2dlm: Nodes in domain B5E583B70A5F4EB4AA24A21924F31D25: 0 [345552.557444] ocfs2: Mounting device (147,1) on (node 0, slot 0) with writeback data mode. [345570.309183] ocfs2: Unmounting device (147,1) on (node 0) [345596.619186] ocfs2: Unregistered cluster interface o2cb [345622.701066] OCFS2 Node Manager 1.5.0 [345622.769391] OCFS2 DLM 1.5.0 [345622.771106] ocfs2: Registered cluster interface o2cb [345622.780612] OCFS2 DLMFS 1.5.0 [345622.780750] OCFS2 User DLM kernel interface loaded [345632.645613] OCFS2 1.5.0 [345632.728529] o2dlm: Nodes in domain B5E583B70A5F4EB4AA24A21924F31D25: 0 [345632.811743] ocfs2: Mounting device (147,1) on (node 0, slot 0) with writeback data mode. [345849.580515] o2net: accepted connection from node atsambas1umb (num 1) at 10.43.202.57: [345853.728557] o2dlm: Node 1 joins domain B5E583B70A5F4EB4AA24A21924F31D25 [345853.728561] o2dlm: Nodes in domain B5E583B70A5F4EB4AA24A21924F31D25: 0 1 [349851.770879] svc: failed to register lockdv1 RPC service (errno 97). [349851.770923] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory [349851.777649] NFSD: starting 90-second grace period [502217.997960] o2dlm: Node 1 leaves domain B5E583B70A5F4EB4AA24A21924F31D25 [502218.005748] o2dlm: Nodes in domain B5E583B70A5F4EB4AA24A21924F31D25: 0 [502219.633035] o2net: connection to node atsambas1umb (num 1) at 10.43.202.57: shutdown, state 8 [502219.633069] o2net: no longer connected to node atsambas1umb (num 1) at 10.43.202.57: [502401.628983] nfsd: last server has exited, flushing export cache [502413.189084] ocfs2: Unmounting device (147,1) on (node 0) [502465.599503] o2dlm: Nodes in domain B5E583B70A5F4EB4AA24A21924F31D25: 0 [517372.514655] o2dlm: Nodes in domain B5E583B70A5F4EB4AA24A21924F31D25: 0 [517372.629262] ocfs2: Mounting device (147,1) on (node 0, slot 0) with writeback data mode. [517386.090971] o2net: accepted connection from node atsambas1umb (num 1) at 10.43.202.57: [517390.137223] o2dlm: Node 1 joins domain B5E583B70A5F4EB4AA24A21924F31D25 [517390.137226] o2dlm: Nodes in domain B5E583B70A5F4EB4AA24A21924F31D25: 0 1 [517436.066849] svc: failed to register lockdv1 RPC service (errno 97). [517436.066956] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory [517436.074355] NFSD: starting 90-second grace period [606232.120297] usb 2-1: USB disconnect, device number 2 [673265.851132] CIFS VFS: Server 10.43.28.102 has not responded in 300 seconds. Reconnecting... [673265.851226] CIFS VFS: Unexpected lookup error -112 [673285.841033] CIFS VFS: Unexpected lookup error -112 [673305.830989] CIFS VFS: Unexpected lookup error -112 [673325.820957] CIFS VFS: Unexpected lookup error -112 [673345.810915] CIFS VFS: Unexpected lookup error -112 [673365.800912] CIFS VFS: Unexpected lookup error -112 [673385.790844] CIFS VFS: Unexpected lookup error -112 [673405.780807] CIFS VFS: Unexpected lookup error -112 [673425.770768] CIFS VFS: Unexpected lookup error -112 [673445.760736] CIFS VFS: Unexpected lookup error -112 [673465.750691] CIFS VFS: Unexpected lookup error -112 [673485.740683] CIFS VFS: Unexpected lookup error -112 [942581.750153] CIFS VFS: Unexpected lookup error -112 [942611.791039] CIFS VFS: Unexpected lookup error -112 [942621.899688] CIFS VFS: Unexpected lookup error -112 [942651.883038] CIFS VFS: Unexpected lookup error -112 [942681.867940] CIFS VFS: Unexpected lookup error -112 [942711.852940] CIFS VFS: Unexpected lookup error -112 [944538.385523] igb: eth1 NIC Link is Down [944538.481312] bonding: bond0: link status down for interface eth1, disabling it in 100 ms. [944538.581263] bonding: bond0: link status definitely down for interface eth1, disabling it [944551.667174] igb: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [944551.674752] bonding: bond0: link status up for interface eth1, enabling it in 1000 ms. [944552.674189] bonding: bond0: link status definitely up for interface eth1, 1000 Mbps full duplex. [1094151.458960] [ cut here ] [1094151.458993] kernel BUG at /tmp/buildd/linux-2.6-2.6.39/debian/build/source_amd64_none/fs/jbd2/transaction.c:1086! [1094151.459048] invalid opcode: [#1] SMP [1094151.459080] last sysfs file: /sys/devices/virtual/bdi/cifs-1258/uevent [1094151.459112] CPU 0 [1094151.459120] Modules
Bug#643629: linux-image-2.6.39-bpo.2-amd64: BUG at fs/jbd2/transaction.c:1086
Hi Nico,
nico wrote:
kernel BUG at [...]/fs/jbd2/transaction.c:1086!
[...]
Call Trace:
[a059b82d] ? ocfs2_journal_dirty+0x47/0x58 [ocfs2]
[a057e3b1] ? __ocfs2_add_entry+0x78d/0x88d [ocfs2]
[a03a1cb4] ? jbd2_journal_put_journal_head+0x19/0x4e [jbd2]
[a039b9b4] ? jbd2_journal_get_write_access+0x2d/0x38 [jbd2]
[a05a5e37] ? ocfs2_link+0x55e/0x7ac [ocfs2]
[a058fd4e] ? ocfs2_permission+0xec/0xf9 [ocfs2]
[81104701] ? vfs_link+0xc3/0x126
[81107084] ? sys_linkat+0x11d/0x179
[810ff09c] ? sys_newstat+0x24/0x2d
[81339392] ? system_call_fastpath+0x16/0x1b
Code: 48 8b 13 f7 c2 00 00 10 00 75 f3 f0 0f ba 2b 14 19 d2 85 d2 75 e8 83 7d
10 00 75 19 c7 45 10 01 00 00 00 41 8b 55 08 85 d2 7f 04 0f 0b eb fe ff ca
41 89 55 08 48 39 45 28 75 11 83 7d 0c 01 75
RIP [a039b05e] jbd2_journal_dirty_metadata+0x5d/0xe3 [jbd2]
The tripped assertion is
if (jh-b_modified == 0) {
/*
* This buffer's got modified and becoming part
* of the transaction. This needs to be done
* once a transaction -bzzz
*/
jh-b_modified = 1;
J_ASSERT_JH(jh, handle-h_buffer_credits 0);
handle-h_buffer_credits--;
}
Is this reproducible? If so, could you try a 3.x kernel from sid or
experimental? (There have been some fixes for bugs like this in ext3
and ext4 but I don't see any similar change to ocfs2. Even so, it
seems worth a try before contacting upstream about this.)
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/20110928090707.GB21870@elie
Bug#642409: linux-2.6: suspend from gnome shutdown fails when krb5/nfs4 user logged in
On 27/09/11 20:27, Jeff Layton wrote: On Mon, 26 Sep 2011 14:31:32 -0400 Jeff Laytonjlay...@redhat.com wrote: Not sure what happened here. Looks like the freeze phase of the suspend worked. My inclination is to think that this is not due to my patch. What might be helpful is to try suspending without NFS being mounted. If that doesn't work either, then maybe back out the patch and try again without any NFS mounts. Yeah, after looking over the code I really think the instant wakeup thing is an unrelated problem. This patchset is really intended to fix the problem where the freezer is unable to freeze tasks that are stuck waiting on replies from NFS and CIFS servers. If you aren't seeing these sorts of errors when trying to suspend, then this is probably a different problem: https://bugzilla.redhat.com/show_bug.cgi?id=717735#c0 It would be nice to have some successful tests with this set though before I propose it, but that might not be possible given the general fragility of the userspace suspend code :-/ I'm testing away. I think you're right about the problems now being userspace. I feel that the hang after thaw problems I'm seeing are caused by krb5 - it seems to like to get itself into a situation where it has no krb5 ticket so it can't access my home directory which prevents the unlock window popping up so it can't get my password and ask for a new krb5 ticket. If I log on on another screen or serial terminal then the unlock dialogue pops up. I'm going to continue testing today but so far my feeling is that the patch works as advertised - nfs4 shares no longer prevent suspend from working. John would you be able to test the things I mentioned in my prior reply? In particular, seeing whether you're able to suspend consistently without nfs mounts and without those patches in place? If that doesn't work either, then I'll be inclined to think that this is unrelated. So far (I'll confirm tomorrow) 1. I can suspend without nfs mounts 2. I can suspend with nfs mounts if they are not my home directory 3. suspending with nfs mounts of the home directory using echo mem /sys/power/state works 4. suspending with nfs mounts of the home directory using pm-suspend usualy works 5. suspending with nfs mounts of the home directory using gnome shutdown/suspend menu item often hangs. The problems are much more visible on my klunky old Optiplex GX270 systems (2.6GHz P4) than my nice new Optiplex 390 (Core I3). -- 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/4e82e44d.5010...@calva.com
Bug#643629: linux-image-2.6.39-bpo.2-amd64: BUG at fs/jbd2/transaction.c:1086
(just cc-ing the bug log) Nico Giefing wrote: I'm not sure if its possible to try a 3.x kernel, i have to check that. its not reproduable, the symptoms happened now the second time, which are: no access to the file system and not killable processes. i will restart now the machine and let you know if 3.x is possible. Thanks, Nico. 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/20110928093550.GD21870@elie
Bug#642409: linux-2.6: suspend from gnome shutdown fails when krb5/nfs4 user logged in
On Wed, 28 Sep 2011 11:09:33 +0200 John Hughes j...@calva.com wrote: On 27/09/11 20:27, Jeff Layton wrote: On Mon, 26 Sep 2011 14:31:32 -0400 Jeff Laytonjlay...@redhat.com wrote: Not sure what happened here. Looks like the freeze phase of the suspend worked. My inclination is to think that this is not due to my patch. What might be helpful is to try suspending without NFS being mounted. If that doesn't work either, then maybe back out the patch and try again without any NFS mounts. Yeah, after looking over the code I really think the instant wakeup thing is an unrelated problem. This patchset is really intended to fix the problem where the freezer is unable to freeze tasks that are stuck waiting on replies from NFS and CIFS servers. If you aren't seeing these sorts of errors when trying to suspend, then this is probably a different problem: https://bugzilla.redhat.com/show_bug.cgi?id=717735#c0 It would be nice to have some successful tests with this set though before I propose it, but that might not be possible given the general fragility of the userspace suspend code :-/ I'm testing away. I think you're right about the problems now being userspace. I feel that the hang after thaw problems I'm seeing are caused by krb5 - it seems to like to get itself into a situation where it has no krb5 ticket so it can't access my home directory which prevents the unlock window popping up so it can't get my password and ask for a new krb5 ticket. Maybe... krb5 tickets are usually stored in /tmp, so it's probably not the lack of that. It is however likely that the GUI requires access to some files in your homedir, which might be problematic. Still though, it seems like as long as you have a valid ticket, the resume ought to work (assuming that rpc.gssd is back up and running). If I log on on another screen or serial terminal then the unlock dialogue pops up. That certainly sounds like you're needing to reestablish your credcache. Are you putting the krb5 credcache in the keyring or memory or something? I'm going to continue testing today but so far my feeling is that the patch works as advertised - nfs4 shares no longer prevent suspend from working. John would you be able to test the things I mentioned in my prior reply? In particular, seeing whether you're able to suspend consistently without nfs mounts and without those patches in place? If that doesn't work either, then I'll be inclined to think that this is unrelated. So far (I'll confirm tomorrow) 1. I can suspend without nfs mounts 2. I can suspend with nfs mounts if they are not my home directory 3. suspending with nfs mounts of the home directory using echo mem /sys/power/state works 4. suspending with nfs mounts of the home directory using pm-suspend usualy works 5. suspending with nfs mounts of the home directory using gnome shutdown/suspend menu item often hangs. The problems are much more visible on my klunky old Optiplex GX270 systems (2.6GHz P4) than my nice new Optiplex 390 (Core I3). Nice, thanks for testing it. I'll go ahead and send these out later today. -- Jeff Layton jlay...@redhat.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/20110928071209.1d16e...@corrin.poochiereds.net
Processed: reassign 379339 to linux-2.6
Processing commands for cont...@bugs.debian.org: reassign 379339 linux-2.6 Bug #379339 [linux-image-686] s2ram/s2disk: potential problems with HPA (host protected area) Bug reassigned from package 'linux-image-686' to 'linux-2.6'. thanks Stopping processing here. Please contact me if you need assistance. -- 379339: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=379339 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.131721657119858.transcr...@bugs.debian.org
Bug#379339: marked as done (s2ram/s2disk: potential problems with HPA (host protected area))
Your message dated Wed, 28 Sep 2011 14:31:32 +0100
with message-id 1317216693.4068.9.camel@deadeye
and subject line Re: s2ram/s2disk: potential problems with HPA (host protected
area)
has caused the Debian Bug report #379339,
regarding s2ram/s2disk: potential problems with HPA (host protected area)
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.)
--
379339: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=379339
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: uswsusp
Version: 0.2-1
Severity: important
Machine: IBM Thinkpad R50p
I recognized following issues concerning s2ram/s2disk/s2both:
- calling s2ram works fine, resuming from RAM works
- after having resumed and calling s2disk the machine hangs with
heavy HD load
- it's not possible to terminate or kill any process with SysRq+E/I
- following messgages appears again and again if SysRq+E is pressed:
hda: task_out_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_out_intr: status=0x10 { SectorIdNotFound }, \
LBAsect=110561486, sector=110561486
hda: failed opcode was: unknown
where 'LBAsect' and 'sector' will have values above 1100 each
time the behaviour is reproduced
After having disabled the so called IBM Predesktop Area in the BIOS
everything works (in the BIOS setup: Security - IBM Predesktop Area -
Current Setting: Disabled).
As far as I know this IBM Predesktop Area is located in a HPA.
I'm not sure, if this is really a bug (and if so, if it is related to
uswsusp).
Hope anyone will find out.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (700, 'unstable'), (650, 'testing'), (600, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-1-686
Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15)
Versions of packages uswsusp depends on:
ii debconf [debconf-2.0] 1.5.2 Debian configuration
management sy
ii libc6 2.3.6-15 GNU C Library: Shared
libraries
Versions of packages uswsusp recommends:
ii initramfs-tools 0.70b tools for generating an
initramfs
-- debconf information excluded
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
---End Message---
---BeginMessage---
Version: 2.6.32-13
On Sat, 2006-07-22 at 23:09 +0200, Daniel Philipp wrote:
Package: uswsusp
Version: 0.2-1
Severity: important
Machine: IBM Thinkpad R50p
I recognized following issues concerning s2ram/s2disk/s2both:
- calling s2ram works fine, resuming from RAM works
- after having resumed and calling s2disk the machine hangs with
heavy HD load
- it's not possible to terminate or kill any process with SysRq+E/I
- following messgages appears again and again if SysRq+E is pressed:
hda: task_out_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_out_intr: status=0x10 { SectorIdNotFound }, \
LBAsect=110561486, sector=110561486
hda: failed opcode was: unknown
where 'LBAsect' and 'sector' will have values above 1100 each
time the behaviour is reproduced
After having disabled the so called IBM Predesktop Area in the BIOS
everything works (in the BIOS setup: Security - IBM Predesktop Area -
Current Setting: Disabled).
As far as I know this IBM Predesktop Area is located in a HPA.
I'm not sure, if this is really a bug (and if so, if it is related to
uswsusp).
Hope anyone will find out.
[...]
I believe this was finally fixed in kernel version 2.6.32-13 by the
patch libata: Disable HPA if it is only enabled after suspend.
Ben.
--
Ben Hutchings
Everything should be made as simple as possible, but not simpler.
- Albert Einstein
signature.asc
Description: This is a digitally signed message part
---End Message---
Bug#643612: marked as done (linux-base: Please add linux-tools to Depends)
Your message dated Wed, 28 Sep 2011 14:28:19 +0100
with message-id 1317216508.4068.7.camel@deadeye
and subject line Re: Bug#643612: linux-base: Please add linux-tools to Depends
has caused the Debian Bug report #643612,
regarding linux-base: Please add linux-tools to Depends
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.)
--
643612: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643612
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-base
Version: 3.3
Severity: wishlist
Tags: patch
Hi,
/usr/bin/perf is provided in linux-base.
However, since linux-tools is not specified by a dependency, it does not work.
-
$ perf
/usr/bin/perf: line 7: exec: perf_3.1.0: not found
E: linux-tools-3.1.0 is not installed.
-
Since linux-tools is not installed by this error message, it turns out
that it does not work.
Would you put linux-tools into Depends?
Best regards,
Nobuhiro
--
Nobuhiro Iwamatsu
iwamatsu at {nigauri.org / debian.org}
GPG ID: 40AD1FA6
diff -Nru linux-base-3.3/debian/control linux-base-3.3+nmu1/debian/control
--- linux-base-3.3/debian/control 2011-07-04 13:10:30.0 +0900
+++ linux-base-3.3+nmu1/debian/control 2011-09-28 12:49:45.0 +0900
@@ -10,7 +10,7 @@
Package: linux-base
Architecture: all
-Depends: libuuid-perl, ${misc:Depends}, util-linux (= 2.16-1) | udev ( 146-1)
+Depends: libuuid-perl, ${misc:Depends}, util-linux (= 2.16-1) | udev ( 146-1), linux-tools
Description: Linux image base package
This package contains files and support scripts for all Linux
images.
---End Message---
---BeginMessage---
On Wed, 2011-09-28 at 12:59 +0900, Nobuhiro Iwamatsu wrote:
Package: linux-base
Version: 3.3
Severity: wishlist
Tags: patch
Hi,
/usr/bin/perf is provided in linux-base.
However, since linux-tools is not specified by a dependency, it does not work.
-
$ perf
/usr/bin/perf: line 7: exec: perf_3.1.0: not found
E: linux-tools-3.1.0 is not installed.
-
Since linux-tools is not installed by this error message, it turns out
that it does not work.
Would you put linux-tools into Depends?
The required package depends on the running kernel. There is no way to
write this as a dependency.
Further, linux-base is used by all linux-image packages. They should
not depend on linux-tools packages.
Ben.
--
Ben Hutchings
Everything should be made as simple as possible, but not simpler.
- Albert Einstein
signature.asc
Description: This is a digitally signed message part
---End Message---
Bug#643301: [johnmoha...@gmail.com: Re: linux-image-3.0.0-1-rt-amd64: Suspend to ram hangs]
On Tue, 27 Sep 2011 14:59:53 +0200 Uwe Kleine-König u.kleine-koe...@pengutronix.de wrote: Hi John, On Tue, 27 Sep 2011 00:45:01 -0500 Jonathan Nieder jrnie...@gmail.com wrote: [...] 3. Since hey, one can be lucky sometimes: is it possible to catch the failure as it happens, for example by not suspending the console and suspending everything else? See https://raw.github.com/torvalds/linux/master/Documentation/power/basic-pm-debugging.txt https://raw.github.com/torvalds/linux/master/Documentation/networking/netconsole.txt (or the analagously named files in the linux-doc-3.0.0 package) for hints in that direction. This is a little out of my comfort zone, but I did follow the procedure in the first link, running the sequential tests with /sys/power/pm_test. freezer, devices and platform tests all work, the failure occurs with processors, both for STR and STD. IFACT from the link, this means the problem is not with a driver but with processor states? But my laptop only has a single processor (even though in /sys/devices/system/cpu/ there is cpu0 and cpu1, only the latter has a file online mentioned in the link, is this relevant?). Did you try adding no_console_suspend to the kernel commandline? I have now: for STR, the screen goes blank so if the freeze occurs I don't get to see any messages. For STD, all messages are normal up to and including the one that says the image is being saved (didn't note the exact wording), and there it stops. 4. Does Alt+Sysrq work in the broken state? If so, the following could be useful. No, totally frozen. That means you tried Alt+Sysrq+b and nothing happend? But sysrq works before the crash? Yes, and yes. [...] Is it possible to reproduce this without brcmsmac? E.g., does the b43 driver support your card (I haven't checked)? With this kernel AFAIK I can only use brcmsmac, but I can unload it and still reproduce the problem. Better don't load it at all. I don't think it's responsible for the problem but ruling this out should be easy enough. [...] OK, now I have tried it with brcmsmac blacklisted so it doesn't get loaded, the behaviour is the same. As Jonathan has advised, I tried the Sid rt kernel and got the same results. I would add though that the behaviour is not as consistent as it seemed yesterday: sometimes (today) I can suspend successfully several times in a row, sometimes there are many consecutive failures. It _seems_ to be more likely when biggish programs are running, although yesterday it failed in processors test mode every time (maybe ten times) even in single user mode. Hard to say, too, if the unstable kernel behaves a little differently or not. Seems to be random, but without doing hundreds of tests (and hard shutdowns and kernel swaps) I can't be sure. Should I go ahead with a report to linux-rt-users as Jonathan has advised? Best regards, John -- 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/20110929000438.1729759d0e560ae036cdc...@gmail.com
Kernel 3.0 Makefile
Hi i have a problem with the make file from the kernel in wheezy/sid. /usr/src/linux/Makefile: VERSION = 2 PATCHLEVEL = 6 MAKEARGS := -C /usr/src/linux-headers-3.0.0-1-common O=/usr/src/linux-headers-3.0.0-1-amd64 MAKEFLAGS += --no-print-directory why ? i can not make with this makefile build modules ... the vanilla makefile : VERSION = 3 PATCHLEVEL = 0 SUBLEVEL = 0 EXTRAVERSION = NAME = Sneaky Weasel -- 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/4e83321d.2080...@googlemail.com
Processing of kernel-handbook_1.0.12_multi.changes
kernel-handbook_1.0.12_multi.changes uploaded successfully to localhost along with the files: kernel-handbook_1.0.12.dsc kernel-handbook_1.0.12.tar.gz debian-kernel-handbook_1.0.12_all.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1r8vds-00050t...@franck.debian.org
Bug#640972: linux-image-2.6.32-5-amd64: SATA errors every ~30sec ata##: hard resetting link... SATA link down (SStatus 0 SControl 300/310)... EH Complete
Am I correct in observing that these errors are for SATA channels that aren't connected to anything inside the ExpressCard? (This is a sealed ExpressCard SSD.) If so, is there a way to tell the kernel to ignore them? It does appear that the card works significantly (say 20%) slower on Linux than on Win7. Could the time spent resetting the device be related to this slowdown? (I would do further testing on the Windows side, but I don't have Win7 installed any longer; I had installed it to do a BIOS update.) -- 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/ca+8+cat4da9sfajhbkqtzn+8o0ufobikdahh1ypzmhaf0ot...@mail.gmail.com
kernel-handbook_1.0.12_multi.changes ACCEPTED into unstable
Accepted: debian-kernel-handbook_1.0.12_all.deb to main/k/kernel-handbook/debian-kernel-handbook_1.0.12_all.deb kernel-handbook_1.0.12.dsc to main/k/kernel-handbook/kernel-handbook_1.0.12.dsc kernel-handbook_1.0.12.tar.gz to main/k/kernel-handbook/kernel-handbook_1.0.12.tar.gz Override entries for your package: debian-kernel-handbook_1.0.12_all.deb - extra doc kernel-handbook_1.0.12.dsc - source doc Announcing to debian-devel-chan...@lists.debian.org Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1r8wdg-00067x...@franck.debian.org
Bug#640391: linux-image-3.0.0-1-686-pae: ark3116 driver regression
2011/9/21 ael law_ence@ntlworld.com: I have just done another test. This because that garmin odd connector often fails to make proper contact. So in this case I first verified that I could use gpsbabel successfully with the old kernel, so confirming a proper connection. Then I just used $ gpsbabel -w -i garmin -f /dev/ttyUSB0 -o gpx -F test.gpx [ERROR] GPS_Packet_Read: Timeout. No data received. GARMIN:Can't init /dev/ttyUSB0 Hi ael, I finally managed to find some time to test this on my own hardware on 2.6.38. I do not have a garmin gps, so I connect my ark3116 to a second serial interface. I used the same gpsbabel command as you to connect to my ark3116, and I could see data coming in on the second port and if I sent a reply the other way, it is received by gpsbabel. In short, everything seems to work as it should, which is not helping. Your traces show that gpsbabel never receives anything in your case, so somehow something is behaving different. I am running out of ideas. Would it be possible for you to do a similar experiment with a second serial port? That way we might learn if data actually makes it to the serial output when sending or if data is received on the serial input but not forwarded to the USB bus. Another thing to try could be to use picoterm or some other terminal program to send some characters to the gps (9600N8), to see what happens, and then directly afterwards try the gpsbabel command again. If the underlying problem has to do with somekind of timing mismatch, or initialisation problem, this might help. Thanks. Groeten, Bart -- Bart Hartgers - New e-mail: bart.hartg...@gmail.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/cak7h4ydudcvb0jtvt9h1ivaes6jtxppvctkq+ad+hwmesvr...@mail.gmail.com
Bug#640391: linux-image-3.0.0-1-686-pae: ark3116 driver regression
On Wed, Sep 28, 2011 at 08:55:40PM +0200, Bart Hartgers wrote: 2011/9/21 ael law_ence@ntlworld.com: I have just done another test. This because that garmin odd connector often fails to make proper contact. So in this case I first verified that I could use gpsbabel successfully with the old kernel, so confirming a proper connection. Then I just used $ gpsbabel -w -i garmin -f /dev/ttyUSB0 -o gpx -F test.gpx [ERROR] GPS_Packet_Read: Timeout. No data received. GARMIN:Can't init /dev/ttyUSB0 Hi ael, I finally managed to find some time to test this on my own hardware on 2.6.38. I do not have a garmin gps, so I connect my ark3116 to a second serial interface. I used the same gpsbabel command as you to connect to my ark3116, and I could see data coming in on the second port and if I sent a reply the other way, it is received by gpsbabel. In short, everything seems to work as it should, which is not helping. Your traces show that gpsbabel never receives anything in your case, so somehow something is behaving different. I am running out of ideas. Would it be possible for you to do a similar experiment with a second serial port? That way we might learn if data actually makes it to the serial output when sending or if data is received on the serial input but not forwarded to the USB bus. I have a real RS232 port on a desktop (back at home now), so I guess I could connect from the netbook USB - ark3116 - RS232 desktop. I will have to see what cables I have, but I think I have a very old RS232 breakout box somewhere, so I can probably fix something up. I suppose I could use picoterm or similar to view the incoming data on the desktop: it is a while since I looked at those programs. I could also use a multimeter or whatever to see how those four wires on the garmin are connected to the 9-pin RS232 plug in case that throws any light on handshaking, if any. I might need a bit of hand holding since my serial knowledge is now rather rusty. It may take a day or two to find time to try all of this. I could also perhaps put an oscilloscope onto the RS232 breakout box to see what at least a couple of the signals are doing, but I will need to clear some bench space which is in very short supply! I guess that might also throw some light on what happens when connected to the garmin. That said, trying to follow serial signals on a 'scope isn't always straight forward: now if I had a logic analyser available, it might be much easier :-) If I do go to the 'scope, I guess a comparison between the old working kernel talking to the garmin and the latest problem version might help. But I suspect triggering properly might make that pretty difficult. ael -- 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/20110928194809.GA4926@elf.conquest
Bug#605395: JMicron Technology JMB362 JMB363 SError: { DevExch } ExpressCard, sometimes fails to boot
tags 605395 + moreinfo
quit
Hi again,
Jonathan Nieder wrote:
Orson wrote:
If booting to a command prompt, the messages just keep filling up the
terminal
every few seconds, making it really difficult to work this way.
ata3: irq_stat 0x0040, connection status changed
[ 54.038441] ata3: SError: { DevExch }
[...]
Sometimes this happens at boot, and just stays in a loop, displaying this
same
error on screen, removing the expresscard and reset solves the problem.
[...]
I don't see any relevant fixes upstream unfortunately, but JMB363 is
supposed to work. If you get a chance, please test a recent v3.x
version from unstable, letting us know the result, and if that fails
then describe the symptoms to linux-...@vger.kernel.org, cc-ing Aries
Lee aries...@jmicron.com and this bug log.
Orson, did you get a chance to try this (or any other news)? To be
clear, I meant that it would be useful to try installing a
linux-image-3.foo package, along with linux-base and initramfs-tools
from sid or squeeze-backports, keeping the rest of the system as is.
If you're just short on time recently, that's fine, but if e.g. you no
longer have access to the hardware then we should know so we can stop
tracking it.
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/20110928212253.GA3004@elie
Processed: Re: JMicron Technology JMB362 JMB363 SError: { DevExch } ExpressCard, sometimes fails to boot
Processing commands for cont...@bugs.debian.org:
tags 605395 + moreinfo
Bug #605395 [linux-2.6] linux-image-2.6.32-5-amd64: JMicron Technology JMB362
JMB363 SError: { DevExch } ExpressCard, sometimes fails to boot
Added tag(s) moreinfo.
quit
Stopping processing here.
Please contact me if you need assistance.
--
605395: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=605395
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.13172450127044.transcr...@bugs.debian.org
Bug#640972: linux-image-2.6.32-5-amd64: SATA errors every ~30sec ata##: hard resetting link... SATA link down (SStatus 0 SControl 300/310)... EH Complete
Hi Thomas,
Thomas Shanks wrote:
[ 2411.101196] ata10: SATA link down (SStatus 0 SControl 310)
[ 2411.101209] ata10: EH complete
[ 2411.718853] ata10: exception Emask 0x10 SAct 0x0 SErr 0x404 action 0xe
frozen
[ 2411.718857] ata10: irq_stat 0x0040, connection status changed
[ 2411.718862] ata10: SError: { CommWake DevExch }
[ 2411.718873] ata10: limiting SATA link speed to 1.5 Gbps
[ 2411.718876] ata10: hard resetting link
[ 2412.950097] ata10: SATA link down (SStatus 0 SControl 310)
[...]
Thanks, and sorry for the slow response. Your other reply contains
interesting questions, but before starting to investigate I'd be
interested in the following:
- please send a copy of the kernel messages from bootup, so we
can see which controller ata10 is (and any other misc info it
shows during initialization).
- please test recent v3.x version from sid or experimental and
let us know the result. If that fails, we should take this
upstream, and if it succeeds, we can look for the fix to backport.
This shouldn't require upgrading any additional packages except
for linux-base and initramfs-tools.
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/20110928211132.GA2876@elie
Bug#642911: linux-image-2.6.32-5-686: Network connection fails under heavy load.
On Wed, 2011-09-28 at 08:37 +0200, boos...@wolke7.net wrote: Ben Hutchings wrote: Please test version 2.6.32-36 from stable-proposed-updates. Ben. Hi Ben, I tested version 2.6.32-37. The network seems to be more stable, but I still have connection timeouts. There are no more dmesg lines for eth0: link up but my ssh connection still terminates from time to time. So you still see WARNING: at ... dev_watchdog? Do you need any more log files ? They may be helpful. Ben. -- Ben Hutchings Everything should be made as simple as possible, but not simpler. - Albert Einstein signature.asc Description: This is a digitally signed message part
Uploading linux-2.6 (3.0.0-5)
I intend to upload linux-2.6 version 3.0.0-5 to unstable later this week. This will include stable update 3.0.5 and may require an ABI change (I haven't checked yet). It should fix the FTBFS on some architectures in 3.0.0-4 (but other changes may introduce new failures). Assuming that we don't find any more problems with the changes in experimental to use kernel-wedge, I will apply those to unstable as well. I'll need to upload kernel-wedge yet again with Joey's fix for the bug that affected s390. Ben. -- Ben Hutchings Everything should be made as simple as possible, but not simpler. - Albert Einstein signature.asc Description: This is a digitally signed message part
