Re: Bug#865153: reportbug: please include kernel taint flags
Hello Adam, On Mon, Jun 19, 2017 at 12:48 PM Adam Borowski wrote: > > Package: reportbug > Version: 7.1.7 > Severity: wishlist > > Hi! > The "System Information" part of reportbug's output doesn't currently > mention the kernel's taint state. A bunch of these flags show that > something on the system is going pretty badly, thus they're definitely > of interest to someone reading such a bug report. > > The state can be read via /proc/sys/kernel/tainted which provides a decimal > integer value, with bits meaning the following: > >'P',/* TAINT_PROPRIETARY_MODULE */ >'F',/* TAINT_FORCED_MODULE */ >'S',/* TAINT_CPU_OUT_OF_SPEC */ >'R',/* TAINT_FORCED_RMMOD */ >'M',/* TAINT_MACHINE_CHECK */ >'B',/* TAINT_BAD_PAGE */ >'U',/* TAINT_USER */ >'D',/* TAINT_DIE */ >'A',/* TAINT_OVERRIDDEN_ACPI_TABLE */ >'W',/* TAINT_WARN */ >'C',/* TAINT_CRAP */ >'I',/* TAINT_FIRMWARE_WORKAROUND */ >'O',/* TAINT_OOT_MODULE */ >'E',/* TAINT_UNSIGNED_MODULE */ >'L',/* TAINT_SOFTLOCKUP */ >'K',/* TAINT_LIVEPATCH */ this seems to be defined at https://github.com/torvalds/linux/blob/master/include/linux/kernel.h#L549 which saw 2 lines added 2 months ago, and one 7 months ago (ok it's not much, as previous changes were 4 years ago, but still since you can install a custom kernel in stable, it means reportbug will not be able to report correct information). i'm kinda at uneasy to add the decoding of the bit string in reportbug if this will change often. i think it would be ok to have an external tool that could produce the tainted information parsing the header files and the tainted file, and then include this tool output in reportbug systems information section. adding debian-kernel@l.d.o to gather some of their insight on the matter too -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi G+: https://plus.google.com/u/0/+SandroTosi
Squeeze backport of 3.8.13
Hello, do you have any plan to backport 3.8.13 kernel package to squeeze-backports? we'd love to use it on our squeeze system, but we lack the knowledge/time to backport it ourselves. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- 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/CAB4XWXzFhPOTj=xmefa-mb6i8x2jddn-yfbpjzwwhpncd++...@mail.gmail.com
Bug#698829: kernel swap after upgrade to 3.2.23-1~bpo60+2
Hello Jonathan, On Sat, Apr 20, 2013 at 11:45 PM, Jonathan Nieder wrote: > If you can run a "reverse bisect" to find which commit or > configuration change fixed it, then I'd be happy to review the patch > that that finds and propose it if appropriate for upstream inclusion. I don't know how affordable that is: we're only able to replicate it on production env (not exactly the best place to run tests) and after at least 7/10 days of live traffic; the time it will take to get to change fixing the behavior could be huge. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- 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/CAB4XWXydbJiZv9u_nGy=NZ-1gbkHT8E=+Qtc1_N=vytj0ud...@mail.gmail.com
Bug#698829: kernel swap after upgrade to 3.2.23-1~bpo60+2
Hello Ben, On Thu, Apr 18, 2013 at 7:09 AM, Ben Hutchings wrote: > On Tue, 2013-04-02 at 10:59 +0200, Sandro Tosi wrote: >> Hello Ben, >> i'm a collegue of Daniele and I'd like to add some more information on >> this issue, which we're still facing with 3.2.35-2~bpo60+1 . > [...] >> Please let us know if you need more information, if we can run some >> diagnostics or try some solutions, it's really important for us to get >> that fixed. > > Sorry, I can't afford to spend any more time on this bug. Thanks for your honest reply. We reached you also because you're the current maintainer of upstream 3.2 branch and because we didn't want Wheezy to release with this bug. We're testing a custom-built 3.7.10 kernel and the slab memory leak seems to be gone (but we're facing with system freezes). Can you please propose what would be the best way for us (and for Debian) to have this problem fixed? Thanks in advance, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- 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/CAB4XWXwXyiMs7o3_aj7sf6S+c1bOKcSoWYOd_ODU=yvtzw8...@mail.gmail.com
Bug#698829: kernel swap after upgrade to 3.2.23-1~bpo60+2
Hello Ben, i'm a collegue of Daniele and I'd like to add some more information on this issue, which we're still facing with 3.2.35-2~bpo60+1 . First of all, we saw there's a new version for bpo, do you want us to update and see if it fixes? We don't want to keep changing the platform (if not under your request) as it might introduce a variability that won't allow to pin-point the problem. About the bind-mounts : yes, we're a heavy clients of bind-mounts :) And while it's true they increase over time, we have a huge spike of mounts in the first period of operation of the node (after reboot, restarting the web service won't umount them), and when it reaches the "balance" the number of mounts increases very slowly over time. We have >300K bind-mounts and 1K per mount it means >300Mb of memory usage, but we've seen even 10GB of slab usage. Now, for example, on a machine up since 8 days I see: OBJS ACTIVE USE OBJ SIZE SLABS OBJ/SLAB CACHE SIZE NAME 7269540 7269516 99%0.19K 363477 20 1453908K size-192 2564196 2324737 90%0.98K 6410494 2564196K nfs_inode_cache while I can see why we have the nfs_inode_cache high in the slabtop (we use intensively NFS mounts), we still observe the size-192 using quite a bit of memory , more than expected with the 1K-per-mount rules. Please let us know if you need more information, if we can run some diagnostics or try some solutions, it's really important for us to get that fixed. cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- 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/CAB4XWXyRnSrs9PE5=Z=xsc7tzig-2md0i7y9c1foxvwn_sy...@mail.gmail.com
Bug#638984: BUG: soft lockup - CPU#1 stuck for 61s! [kswapd0:188]
On Sat, Dec 3, 2011 at 02:01, Jonathan Nieder wrote: > Hi, > > Sandro Tosi wrote: >> On Wed, Aug 24, 2011 at 04:32, Ben Hutchings wrote: > >>> Unfortunately your log shows almost no useful information; the call >>> traces have been lost. The only function that is mentioned in your log >>> is find_get_pages(), which is not present in any of the call traces in >>> the Red Hat bug report. >> >> Oh I see - of course it would have been too easy :) >> >>> It may be that serial logging will be more reliable; could you enable a >>> serial console and try to capture the error log on another system? >> >> We've started the process to enable the serial console logging on the >> involved machines > > Any luck? Sadly no :( we weren't able to configure a serial console but the frequency of the crashes has slightly reduced, but still present. I'll try to revamp the internal discussion and hopefully bring some result back to Debian. -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- 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/CAPdtAj3u0u3hqGvtsjgYMH3ynCpSQ_bPFi=x+8pwzsazk0p...@mail.gmail.com
Bug#638984: BUG: soft lockup - CPU#1 stuck for 61s! [kswapd0:188]
Hi Ben, thanks for the quick reply! On Wed, Aug 24, 2011 at 04:32, Ben Hutchings wrote: > On Tue, 2011-08-23 at 16:17 +0200, Sandro Tosi wrote: >> Package: linux-2.6 >> Version: 2.6.32-35 >> Severity: important >> >> Hello, >> we've had several server-class machine (G6 and G7 HP Proliant blades) >> affected >> by the kernel bug mentioned in the subject. >> >> On the console we can see several several instances of the message: >> >> BUG: soft lockup - CPU#1 stuck for 61s! [kswapd0:188] >> >> and then the machine is freezed and need a hard reset. >> >> I've cut&pasted what's left from the kern.log (remotely logged on another >> machine) since I don't have access anymore to those files (plus a bit of >> anonymization about the network :)). >> >> It's an high priority for us to get it fixed so we can provide all the help >> you >> might need: just ask about it. >> >> I've googled a bit about the problem and found these references: >> >> http://kerneltrap.org/mailarchive/linux-kernel/2010/11/16/4646082/thread >> https://bugzilla.redhat.com/show_bug.cgi?id=649694 > [...] > > The error message you are seeing is not at all specific, so we should > not assume it has anything to do with the Red Hat bug report. > > Unfortunately your log shows almost no useful information; the call > traces have been lost. The only function that is mentioned in your log > is find_get_pages(), which is not present in any of the call traces in > the Red Hat bug report. Oh I see - of course it would have been too easy :) > It may be that serial logging will be more reliable; could you enable a > serial console and try to capture the error log on another system? We've started the process to enable the serial console logging on the involved machines: do you have any tips that can speed up our operations team to enable it (in particular a way that could get us the messages we need)? Thank in advance, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- 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/capdtaj0xjzw__q5q0o4ov+2owxu8t-wnpcpmd0j-q3jpag5...@mail.gmail.com
Bug#638956: include-network bug script doesn't work in case of bonding
On Tue, Aug 23, 2011 at 12:15, Sandro Tosi wrote: > Package: linux-2.6 > Version: 2.6.32-30 dunno how those pkg name & version came out, I was referring to linux-image-2.6.32-5-amd64 > File: /usr/share/bug/linux-image-2.6.32-5-amd64/include-network -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- 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/capdtaj0+nwbpd86rwsgwgazxbi+mhqsuueohxdht9wjicwj...@mail.gmail.com
Bug#638956: include-network bug script doesn't work in case of bonding
Package: linux-2.6 Version: 2.6.32-30 Severity: minor File: /usr/share/bug/linux-image-2.6.32-5-amd64/include-network include-network does a for dir in /sys/class/net/*; do ... cat "$dir"/features >&3 but when bonding is active, there's also a file 'bonding_masters' under /sys/class/net/ and so the 'cat' fails. I've just replaced that line with [ -f "$dir"/features ] && cat "$dir"/features >&3 and it works. Cheers, Sandro -- System Information: Debian Release: 6.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.37-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-image-2.6.32-5-amd64 depends on: ii debconf [debconf 1.5.37 Debian configuration management sy ii initramfs-tools 0.98.7 tools for generating an initramfs ii linux-base 2.6.37-1~experimental.1 Linux image base package ii module-init-tool 3.12-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.32-5-amd64 recommends: ii firmware-linux-f 2.6.37-1~experimental.1 Binary firmware for various driver Versions of packages linux-image-2.6.32-5-amd64 suggests: pn grub | lilo(no description available) pn linux-doc-2.6.32 (no description available) Versions of packages linux-image-2.6.32-5-amd64 is related to: pn firmware-bnx2 (no description available) pn firmware-bnx2x (no description available) pn firmware-ipw2x00 (no description available) pn firmware-ivtv (no description available) ii firmware-iwlwifi 0.28 Binary firmware for Intel Wireless ii firmware-linux0.28 Binary firmware for various driver ii firmware-linux-nonfree0.28 Binary firmware for various driver pn firmware-qlogic(no description available) pn firmware-ralink(no description available) pn xen-hypervisor (no description available) -- debconf information excluded -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110823101552.9175.75576.report...@sandrotosi.register.it
Bug#613172: reportbug: samba/kswapd0/ext4 moving large files or causing high systemload cause kernel panic/system freeze
reassign 613172 linux-2.6 found 613172 2.6.32-30 severity 613172 important tags 613172 -lfs thanks On Sun, Feb 13, 2011 at 12:09, Barry Schut wrote: > Package: reportbug sorry, wrong package. > Version: 4.12.6 > Severity: critical > Tags: lfs why this tag? removed. > When i try to put the system under quite some load by either compiling with > make -j3 (dualcore system) > or move a +40GB file through samba on an ext4 fs using a 1Gbit NIC the kernel > throws a trace and > freezes, compiling my own kernel (2.6.37) enabled me to do a regular reboot > now, but it is rendered > unusable from there on after untill i reboot the machine. > > I have been unable to trace the problem to one specific thing, it might be > kernel related as this and > the debian squeeze kernels are newer then the one i used before. I have trace > information and system > information at the ready for anyone who wishes to view them. > > Kernel/Debian developers can use my system to debug if needed. I'm reassigning to the kernel, since it seems a better place than reportbug. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- 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/AANLkTikf3+K7-Tfdenw2hRf4Ku=mqlmny4pdhcnbs...@mail.gmail.com
Bug#587960: [Debian] Where can I find rtl81638d-2.fw firmware for Realtek 8168D NIC?
Package: firmware-nonfree On Fri, Jul 2, 2010 at 22:13, Ben Hutchings wrote: > On Fri, 2010-07-02 at 09:48 +0200, Sandro Tosi wrote: >> Hello Ben, >> sorry to disturb you with this, but you might be my salvation :) > > Well, don't just ask me. You should use the debian-kernel list or the > BTS for firmware-nonfree. ah indeed, sorry: I wrote to you personally since I saw several replies from you on the topic. Submitting the request on BTS with this email. >> I recently bought a laptop (HP dv6-2193el) which has an unfortunate >> NIC: Realtek 8168D. That's the nic that requires the firmware >> rtl81638d-2.fw to work. > > Does it actually require that? I think that that image is a patch that > fixes a bug in the original firmware. Currently the driver will still > allow you to use the NIC if the firmware image is not available. well, the NIC leds blink, but I can't connect to the other host, nor doing any other network operation. Ehm, what image are you referring to? squeeze alpha1 installer? >> Now, I saw some request for inclusion in firmware-linux-nonfree, but >> you said it's not possible since we still don't have a clear licence >> that allows for redistribution. >> >> What I'm actually asking you is: where can I get that firmware? I >> googled a lot without success, and also trying with some different >> net-installers (lenny, testing dailies @ 2010-06-26, squeeze alpha 1) >> none of them was able to correctly detect and enable the NIC, and >> without that, I can't go on with Debian installation. > > You would need to convert the array that was removed from > rtl8168d_2_hw_phy_config() here to a binary: > > http://git.debian.org/?p=kernel/linux-2.6.git;a=commitdiff;h=c8d71d6cd4746c075387b689506adb7256b3221a#patch10 if only I know how :) Thanks in advance, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- 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/aanlktimgpa_rubhbqflreih2dk-nlqzgqsgj71nnk...@mail.gmail.com
Bug#499198: linux-image-2.6.26-1-amd64: complete system freeze
> - on servers at work, while running lenny kernel (at last point > release), I don't face this problem (either because I access trhu ssh, > they don't have X, different/specific hardware). just faced now, in 2 situations: - iLO on a proliant server: I typed 'reboot', it appears 'reboot' - during installer, in particular when switching to VT-2 (alt+f2) to fix grup, typing "grub-install '(hd0)'" often several character '9' or '0' are printed. Installer is 5.0.3 with point release kernel. So yes, the bug is still there. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#499198: linux-image-2.6.26-1-amd64: complete system freeze
On Wed, Sep 9, 2009 at 21:00, Moritz Muehlenhoff wrote: > On Sun, Sep 21, 2008 at 04:34:15PM +0200, Sandro Tosi wrote: >> Hello Maximilian, >> I'm not quite happy with your downgrade of #499198 to important since >> this (together with #499046 and #498328) is a clear regretion from >> 2.6.25 and caused my data loss (hence it qualifies for severity >> grave). >> >> I'm on >> >> $ uname -a >> Linux zion 2.6.25-2-amd64 #1 SMP Mon Jul 14 11:05:23 UTC 2008 x86_64 >> GNU/Linux >> >> since more than 4 days, and none of the above problem ever happened: >> >> - the system runs fine, without any "mtrr: type mismatch", partial >> freeze (#499046) or complete freeze (#499198) >> - when typing, there are not char repetition or strange behavior (#498328) >> - I'm running since 1day the long-running task mentioned in (#498328) >> and it's using 100% of all 4 cores, without me even noticing it. >> >> At last: those are all important bug and I believe #499198 to be RC. >> >> I renew my willing to help you, just tell me how; but if the only >> interaction you want to have with my bugs is via control server to >> downgrade their severity, then I'll find other way to let my concerns >> be known. > > What is the status? well, I don't know, you tell me :) > Does this still affect the final Lenny kernel? > > Did you try a more recent kernel from backports.org? I don't know and I didn't try the backport kernel: - on my machine I jump to 2.6.30 quite a long ago - on servers at work, while running lenny kernel (at last point release), I don't face this problem (either because I access trhu ssh, they don't have X, different/specific hardware). I don't know what to do with this report, probably you can close it (even though the note about not "brutally" downgrade still applies). Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Processed: Bug#543815: Establishing a "Severity" rating
On Tue, Sep 1, 2009 at 18:25, Moritz Muehlenhoff wrote: > On Tue, Sep 01, 2009 at 12:03:55PM +0200, Sandro Tosi wrote: >> Hello, >> >> On Tue, Sep 1, 2009 at 00:06, Debian Bug Tracking >> System wrote: >> > Processing commands for cont...@bugs.debian.org: >> > >> >> clone 543815 -1 >> > Bug#543815: initramfs-tools: Having "/lib64" in /etc/ld.so.conf results in >> > unusable initrd image >> > Bug 543815 cloned as bug 544485. >> > >> >> reassign -1 reportbug >> > Bug #544485 [initramfs-tools] initramfs-tools: Having "/lib64" in >> > /etc/ld.so.conf results in unusable initrd image >> > Bug reassigned from package 'initramfs-tools' to 'reportbug'. >> > Bug No longer marked as found in versions initramfs-tools/0.85i. >> >> retitle -1 overinflated linux-2.6 bug reports >> > Bug #544485 [reportbug] initramfs-tools: Having "/lib64" in >> > /etc/ld.so.conf results in unusable initrd image >> > Changed Bug title to 'overinflated linux-2.6 bug reports' from >> > 'initramfs-tools: Having "/lib64" in /etc/ld.so.conf results in unusable >> > initrd image' >> >> stop >> > Stopping processing here. >> >> We are using the same text for severities as from BTS website [1] >> >> [1] http://www.debian.org/Bugs/Developer#severities >> >> If there is a problem with that wording, it should be fixed there >> first (and then notify us of teh change, just to fast sync the info). >> >> Please either close this bug (it's invalid for reportbug) or reassing >> it to b.d.o , as you prefer. > > The problem is that the standard severities cannot be mapped 1:1 on > the kernel package. Since the kernel is the core component of 99% > of all Debian systems, it's in the nature of the beast that any > problem which makes a system unbootable renders the package unusable > for the person filing the bug and the default descriptions lead bug > reporters to believe that grave or above is the correct severity. Yeah, I agree, but I also like Julien's suggestion of a 'presubj' script: do you think it's feasible to add one to kernel package? > Since this is a common mistake, it might be a good idea to display > different descriptions when filing a bug against the linux-2.6 > source package. This is what Maks's bug report is about. Thanks for clarifying :) Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Processed: Bug#543815: Establishing a "Severity" rating
Hello, On Tue, Sep 1, 2009 at 00:06, Debian Bug Tracking System wrote: > Processing commands for cont...@bugs.debian.org: > >> clone 543815 -1 > Bug#543815: initramfs-tools: Having "/lib64" in /etc/ld.so.conf results in > unusable initrd image > Bug 543815 cloned as bug 544485. > >> reassign -1 reportbug > Bug #544485 [initramfs-tools] initramfs-tools: Having "/lib64" in > /etc/ld.so.conf results in unusable initrd image > Bug reassigned from package 'initramfs-tools' to 'reportbug'. > Bug No longer marked as found in versions initramfs-tools/0.85i. >> retitle -1 overinflated linux-2.6 bug reports > Bug #544485 [reportbug] initramfs-tools: Having "/lib64" in /etc/ld.so.conf > results in unusable initrd image > Changed Bug title to 'overinflated linux-2.6 bug reports' from > 'initramfs-tools: Having "/lib64" in /etc/ld.so.conf results in unusable > initrd image' >> stop > Stopping processing here. We are using the same text for severities as from BTS website [1] [1] http://www.debian.org/Bugs/Developer#severities If there is a problem with that wording, it should be fixed there first (and then notify us of teh change, just to fast sync the info). Please either close this bug (it's invalid for reportbug) or reassing it to b.d.o , as you prefer. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#498328: linux-image-2.6.26-1-amd64: nice is not "fair": mouse jumps and chars repeated in terminal
Hi Havis, I'm forwarding your reply to the bug log, so the maintainer can have a better idea of the situation. Given your workaround (I'm not going to replicate) it's even more clearer a bug in the kernel needing to be fixed before Lenny release. Sandro On Tue, Sep 23, 2008 at 12:18, Havis <[EMAIL PROTECTED]> wrote: > Hi, I have same problems like you. > I have Debian Lenny with 2.6.26-1-686 kernel > I have been running boinc for a long time > and these issues appeard on my PC after > I started using kernels with CFS scheduler (2.6.24+) > my hw is: > CPU: Pentium 4 2.8GHz HT > RAM: 2GB DDR 400MHz > MB: ABIT IC7-G > HDD: Hitachi 500GB, Hitachi 250GB, Maxtor 120GB (all 7200rpm) > > A solution for me was to turn off HyperThreading in BIOS. > I think that -nice 19 processes have too high priority > and that -nice 19 behavior should be changed > so that these tasks get only _free_ (not used) CPU clocks. > > > Sandro Tosi wrote: >> severity 498328 important >> thanks >> >> On Tue, Sep 9, 2008 at 09:24, Sandro Tosi <[EMAIL PROTECTED]> wrote: >> > Package: linux-image-2.6.26-1-amd64 >> > Version: 2.6.26-4 >> > Severity: normal >> > >> > Hello, >> > I updated 2 days ago to this kernel, and I start notice pretty soon this >> > problem: when I execute a program of mine (even with nice -n 19), with 4 >> > parallel thread (it's cpu bound), the system completely slow down, the >> > mouse >> > starts jumping (not a smooth movement), switching to other application is >> > really slow and the programs starts repeating input chars randomly >> > (verified >> > with amsn and gnome-terminal): this is what I came out trying a "ls >> > /proc...": >> > >> > $ s >> > /pro/2808 >> >> Today the situation was much more worst (after 3 days of uptime): >> while trying to access to mysql from terminal, I start typing 'm' char >> and then the drama begins: the 'm' char was repeating forever (and >> it's not a faulty keyboard, since I remove the battery and the flow >> kept going) in every window I choose, both terminals, xchat, >> iceweasel, etc. in the current virtual desktop and in others >> >> After a while, the whole machine start "ranting": switching to other >> virtual desktop result in freezed windows, trying to exit from the DE >> (xfce in this case) was not possible since xfce-panel was not >> responding, and not even ssh from another pc worked!! >> >> Please treat this as a grave bug (I didn't raise the severity to that >> level because I still don't know if it's RC or not). I renew my offer >> to support you in any way to debug & fix it. I saw a -5 was released: >> I'll try it but from changelog it doesn't seem to address this >> problem. -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#499198: linux-image-2.6.26-1-amd64: complete system freeze
Hello Maximilian, I'm not quite happy with your downgrade of #499198 to important since this (together with #499046 and #498328) is a clear regretion from 2.6.25 and caused my data loss (hence it qualifies for severity grave). I'm on $ uname -a Linux zion 2.6.25-2-amd64 #1 SMP Mon Jul 14 11:05:23 UTC 2008 x86_64 GNU/Linux since more than 4 days, and none of the above problem ever happened: - the system runs fine, without any "mtrr: type mismatch", partial freeze (#499046) or complete freeze (#499198) - when typing, there are not char repetition or strange behavior (#498328) - I'm running since 1day the long-running task mentioned in (#498328) and it's using 100% of all 4 cores, without me even noticing it. At last: those are all important bug and I believe #499198 to be RC. I renew my willing to help you, just tell me how; but if the only interaction you want to have with my bugs is via control server to downgrade their severity, then I'll find other way to let my concerns be known. Kindly, Sandro -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#499198: xorg: No input possible after upgrade
Hello Antoon & XOrg maint, I'm experiencing a similar issue since the last week or so, see #499198. I gave the reason to a kernel problem, since not even a remote access via SSH is possible, and nothing is written to system logs (so it's something "bigger" than xorg). Sandro -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#499198: linux-image-2.6.26-1-amd64: complete system freeze
Package: linux-image-2.6.26-1-amd64
Version: 2.6.26-5
Severity: grave
Hello,
this bug is somewhat related to #499046 and #498328: with the above kernel
version, after about 3 days of uptime the system completely freeze, without
writing anything in /var/log/{messages,kern.log,syslog}. Usually it's
anticipated by a crazy char repetition (like in #498328) or somethings by a
system slowdown until freeze.
This usually happen when I do something particular "heavy": like restarting a
service like mysql, or "apt-get"-ing something.
I cannot no anything; something the situation resolve like in #499046, so after
a couple of minutes I have access back to my workstation, other times I'm not
so lucky and the machine completely freezes, not even ssh remote access is
allowed.
I'm available to do tests, if needed, and now I'm forced back to 2.6.25, hoping
the situation with this kernel will be better.
The machine is an up-to-date sid.
Thanks,
Sandro
-- Package-specific info:
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.25-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages linux-image-2.6.26-1-amd64 depends on:
ii debconf [debconf-2.0] 1.5.23 Debian configuration management sy
ii initramfs-tools [linux-initra 0.92j tools for generating an initramfs
ii module-init-tools 3.4-1 tools for managing Linux kernel mo
linux-image-2.6.26-1-amd64 recommends no packages.
Versions of packages linux-image-2.6.26-1-amd64 suggests:
ii lilo 1:22.8-6 LInux LOader - The Classic OS load
pn linux-doc-2.6.26 (no description available)
-- debconf information:
linux-image-2.6.26-1-amd64/preinst/bootloader-initrd-2.6.26-1-amd64: true
linux-image-2.6.26-1-amd64/postinst/old-initrd-link-2.6.26-1-amd64: true
linux-image-2.6.26-1-amd64/postinst/old-system-map-link-2.6.26-1-amd64: true
linux-image-2.6.26-1-amd64/preinst/overwriting-modules-2.6.26-1-amd64: true
linux-image-2.6.26-1-amd64/preinst/lilo-initrd-2.6.26-1-amd64: true
linux-image-2.6.26-1-amd64/prerm/removing-running-kernel-2.6.26-1-amd64: true
linux-image-2.6.26-1-amd64/prerm/would-invalidate-boot-loader-2.6.26-1-amd64:
true
linux-image-2.6.26-1-amd64/postinst/bootloader-test-error-2.6.26-1-amd64:
linux-image-2.6.26-1-amd64/preinst/lilo-has-ramdisk:
linux-image-2.6.26-1-amd64/postinst/old-dir-initrd-link-2.6.26-1-amd64: true
linux-image-2.6.26-1-amd64/preinst/failed-to-move-modules-2.6.26-1-amd64:
linux-image-2.6.26-1-amd64/postinst/create-kimage-link-2.6.26-1-amd64: true
shared/kernel-image/really-run-bootloader: true
linux-image-2.6.26-1-amd64/postinst/kimage-is-a-directory:
linux-image-2.6.26-1-amd64/preinst/initrd-2.6.26-1-amd64:
linux-image-2.6.26-1-amd64/postinst/depmod-error-initrd-2.6.26-1-amd64: false
linux-image-2.6.26-1-amd64/preinst/elilo-initrd-2.6.26-1-amd64: true
linux-image-2.6.26-1-amd64/postinst/bootloader-error-2.6.26-1-amd64:
linux-image-2.6.26-1-amd64/preinst/abort-install-2.6.26-1-amd64:
linux-image-2.6.26-1-amd64/postinst/depmod-error-2.6.26-1-amd64: false
linux-image-2.6.26-1-amd64/preinst/abort-overwrite-2.6.26-1-amd64:
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#499046: kernel: Call Trace: [] schedule_timeout+0x1e/0xad...
> as reported even below in the "Kernel log" section, I'm back home and find 2 > out > of 4 core not running boinc, and other program with "strange" behaviour during > the day, so I'm reporting this bug. it has happened again today, and I'm again attaching the kern.log (for today only). Please help me fix this, since it's causing a lot of trouble in my workstation. Thanks in advance, Sandro -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi kern.log.2008-09-16.bz2 Description: BZip2 compressed data
Bug#498328: linux-image-2.6.26-1-amd64: nice is not "fair": mouse jumps and chars repeated in terminal
severity 498328 important thanks On Tue, Sep 9, 2008 at 09:24, Sandro Tosi <[EMAIL PROTECTED]> wrote: > Package: linux-image-2.6.26-1-amd64 > Version: 2.6.26-4 > Severity: normal > > Hello, > I updated 2 days ago to this kernel, and I start notice pretty soon this > problem: when I execute a program of mine (even with nice -n 19), with 4 > parallel thread (it's cpu bound), the system completely slow down, the mouse > starts jumping (not a smooth movement), switching to other application is > really slow and the programs starts repeating input chars randomly (verified > with amsn and gnome-terminal): this is what I came out trying a "ls /proc...": > > $ s > /pro/2808 Today the situation was much more worst (after 3 days of uptime): while trying to access to mysql from terminal, I start typing 'm' char and then the drama begins: the 'm' char was repeating forever (and it's not a faulty keyboard, since I remove the battery and the flow kept going) in every window I choose, both terminals, xchat, iceweasel, etc. in the current virtual desktop and in others After a while, the whole machine start "ranting": switching to other virtual desktop result in freezed windows, trying to exit from the DE (xfce in this case) was not possible since xfce-panel was not responding, and not even ssh from another pc worked!! Please treat this as a grave bug (I didn't raise the severity to that level because I still don't know if it's RC or not). I renew my offer to support you in any way to debug & fix it. I saw a -5 was released: I'll try it but from changelog it doesn't seem to address this problem. Thanks in advance, Sandro -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#498328: linux-image-2.6.26-1-amd64: nice is not "fair": mouse jumps and chars repeated in terminal
Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-4 Severity: normal Hello, I updated 2 days ago to this kernel, and I start notice pretty soon this problem: when I execute a program of mine (even with nice -n 19), with 4 parallel thread (it's cpu bound), the system completely slow down, the mouse starts jumping (not a smooth movement), switching to other application is really slow and the programs starts repeating input chars randomly (verified with amsn and gnome-terminal): this is what I came out trying a "ls /proc...": $ s /pro/2808 The funny thing is that this machine has boinc always running (on 4 cores) and I cannot experience any of the above problem. I used the default configuration shipped along with this kernel. Please let me know anything I can do to help you fix is. Thanks, Sandro -- Package-specific info: ** Version: Linux version 2.6.26-1-amd64 (Debian 2.6.26-4) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Thu Aug 28 11:13:42 UTC 2008 ** Command line: BOOT_IMAGE=Linux-2.6.26-1 ro root=fe00 root=/dev/mapper/system-root ** Not tainted ** Kernel log: [ 16.927913] XFS mounting filesystem dm-5 [ 16.996832] Ending clean XFS mount for filesystem: dm-5 [ 17.023057] Filesystem "dm-6": Disabling barriers, not supported by the underlying device [ 17.029946] XFS mounting filesystem dm-6 [ 17.104940] Ending clean XFS mount for filesystem: dm-6 [ 17.156946] Filesystem "dm-4": Disabling barriers, not supported by the underlying device [ 17.270190] XFS mounting filesystem dm-4 [ 17.394182] Ending clean XFS mount for filesystem: dm-4 [ 17.394182] Filesystem "dm-3": Disabling barriers, not supported by the underlying device [ 17.451200] XFS mounting filesystem dm-3 [ 17.488301] Ending clean XFS mount for filesystem: dm-3 [ 17.847446] usb-storage: device scan complete [ 17.847993] scsi 6:0:0:0: Direct-Access TOSHIBA MK2546GSX PQ: 0 ANSI: 2 CCS [ 17.860391] sd 6:0:0:0: [sdc] 488397168 512-byte hardware sectors (250059 MB) [ 17.868879] sd 6:0:0:0: [sdc] Write Protect is off [ 17.874246] sd 6:0:0:0: [sdc] Mode Sense: 00 38 00 00 [ 17.874248] sd 6:0:0:0: [sdc] Assuming drive cache: write through [ 17.880878] sd 6:0:0:0: [sdc] 488397168 512-byte hardware sectors (250059 MB) [ 17.887943] sd 6:0:0:0: [sdc] Write Protect is off [ 17.891962] sd 6:0:0:0: [sdc] Mode Sense: 00 38 00 00 [ 17.891963] sd 6:0:0:0: [sdc] Assuming drive cache: write through [ 17.898839] sdc: sdc1 [ 17.971295] sd 6:0:0:0: [sdc] Attached SCSI disk [ 17.976547] sd 6:0:0:0: Attached scsi generic sg3 type 0 [ 43.751324] r8169: eth1: link up [ 43.756467] r8169: eth1: link up [ 44.180058] NET: Registered protocol family 10 [ 44.185662] lo: Disabled Privacy Extensions [ 44.203348] r8169: eth0: link down [ 44.208203] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 56.445781] eth1: no IPv6 routers present [ 65.608352] lp0: using parport0 (interrupt-driven). [ 65.641647] ppdev: user-space parallel port driver [ 67.220265] RPC: Registered udp transport module. [ 67.224270] RPC: Registered tcp transport module. [ 67.286716] Installing knfsd (copyright (C) 1996 [EMAIL PROTECTED]). [ 67.350703] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory [ 67.355545] NFSD: starting 90-second grace period [ 68.267317] device eth0 entered promiscuous mode [ 72.760695] mtrr: type mismatch for e000,1000 old: write-back new: write-combining [ 107.795864] FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! [ 216.943229] r8169: eth1: link down [ 218.535229] r8169: eth1: link up [17932.161204] usb 8-2: new high speed USB device using ehci_hcd and address 3 [17932.297175] usb 8-2: configuration #2 chosen from 1 choice [17932.301175] usb 8-2: New USB device found, idVendor=047e, idProduct=2892 [17932.301175] usb 8-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [17932.301175] usb 8-2: Product: Agere USB2.0 V.92 SoftModem [17932.301175] usb 8-2: Manufacturer: Agere Systems [23145.694467] usb 8-1: usbfs: USBDEVFS_CONTROL failed cmd lsusb rqt 128 rq 6 len 4 ret -110 [23779.373518] usb 8-2: USB disconnect, address 3 [52444.343859] usb 8-2: new high speed USB device using ehci_hcd and address 4 [52444.483842] usb 8-2: configuration #1 chosen from 1 choice [52444.483842] scsi7 : SCSI emulation for USB Mass Storage devices [52444.483842] usb 8-2: New USB device found, idVendor=1b1c, idProduct=1a90 [52444.483842] usb 8-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [52444.483842] usb 8-2: Product: Voyager GT [52444.483842] usb 8-2: Manufacturer: Corsair [52444.483842] usb 8-2: SerialNumber: A7700102 [52444.483842] usb-storage: device found at 4 [52444.483842] usb-storage: waiting for device to settle before scanning [52449.509328] usb-storage
