Bug#695182: [PATCH] Subtract min_free_kbytes from dirtyable memory
(In the teach a person to fish category...) If you know the file and line number where a bug/regression was introduced, the git blame command is a great tool for identifying the commit which changed a given line of code. Then use git tag --contains commit it to see when a particular commit was introduced into the mainline kernel. - Ted -- 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/20130126154340.gc5...@thunk.org
Bug#698917: linux-image-3.2.0-4-amd64: cpu overheat and shutdown after suspend/resume cycle on Thinkpad T410
On Sat, 2013-01-26 at 00:17 +0100, Florian Lohoff wrote: On Fri, Jan 25, 2013 at 01:00:22PM +, Ben Hutchings wrote: The temperatures are real - you can feel the heat from the outside. Here is the kern log [...] Does the fan ever run? It does right now - Typically i can work on that machine the whole day. If it gets that hot and fails its in the first 10 Minutes after beeing in the office - which is directly after resume. But its not every time i resume. But in the case where you resume and then the machine overheats, does the fan run at any time between resume and shutdown? I have heard of bugs that would cause some laptops not to start the fan after resume. Ben. Did you see this problem with earlier kernel versions? Nope. I think it happened with 3.2.32-1~bpo60+1 too. Before i think i had a 3.0.0 which was okay - Its all a little blurry... -- Ben Hutchings Any smoothly functioning technology is indistinguishable from a rigged demo. signature.asc Description: This is a digitally signed message part
Processed: severity of 689268 is important
Processing commands for cont...@bugs.debian.org: severity 689268 important Bug #689268 [src:linux] linux-image-3.2.0-3-amd64: Intel HD 4000 (Ivy Bridge) graphics freeze Bug #692234 [src:linux] Intel DH77EB (H77): sporadic freeze and increased power consumption during interactive use Bug #692500 [src:linux] [linux-image-amd64] system freezes with Ivy Brigde CPU Bug #692862 [src:linux] linux-image-3.2.0-4-amd64: hangs with Intel i5-3210M CPU / Intel HD 4000 graphics Severity set to 'important' from 'serious' Severity set to 'important' from 'serious' Severity set to 'important' from 'serious' Severity set to 'important' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 689268: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689268 692234: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692234 692500: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692500 692862: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692862 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.13592234307213.transcr...@bugs.debian.org
Bug#687442: linux-image-3.2.0-4.drm-amd64
Re: http://womble.decadent.org.uk/blog/whats-in-the-linux-kernel-for-debian-70-wheezy-part-4.html Been using the kernel *linux-image-3.2.0-4.drm-amd64* for a few hours and everything looks fine here. Tested on Compaq Presaro CQ70 laptop with Intel GMA 4500MHD graphics. Suspend/resume works, as does 3D (running Gnome-shell and tested graphics by playing System Shock 2 via Wine). -- 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/CAErRyQiWzyNa=hegdk3j7prj6xwszcodz-foy2nj2macmph...@mail.gmail.com
Bug#692234: Processed: severity of 689268 is important
Am 26.01.2013 19:06, schrieb Debian Bug Tracking System: Processing commands for cont...@bugs.debian.org: severity 689268 important Bug #689268 [src:linux] linux-image-3.2.0-3-amd64: Intel HD 4000 (Ivy Bridge) graphics freeze Bug #692234 [src:linux] Intel DH77EB (H77): sporadic freeze and increased power consumption during interactive use Bug #692500 [src:linux] [linux-image-amd64] system freezes with Ivy Brigde CPU Bug #692862 [src:linux] linux-image-3.2.0-4-amd64: hangs with Intel i5-3210M CPU / Intel HD 4000 graphics Severity set to 'important' from 'serious' Severity set to 'important' from 'serious' Severity set to 'important' from 'serious' Severity set to 'important' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. Does that really mean that this bug is going to be released with Wheezy? If yes, this means Wheezy should not be installed on Ivy-Bridge systems with HD4000. Wouldn't it be a feasible alternative to accept kernel 3.4.x as an alternative in the repository (besides Wheezy's 3.2)? 3.4 is a long term kernel and well maintained by Greg K-H.. I am currently on 3.4.25 from kernel.org which is distributed by openSuse as well. It runs flawlessly on said hardware and does not show any incompatibilities with any Wheezy-component here. I did nort yet install 3.4.26 which appearently got a major backport of Intel's drm/i915 - 25 commits in total. -- 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/510424fd.5020...@gmx.net
Bug#696650: fsync() on read-only RAID triggers BUG
On Fri, 2013-01-25 at 16:09 +0100, Sebastian Riemer wrote:
On 20.01.2013 19:44, Ben Hutchings wrote:
# Call fsync()
python -c import os; os.fsync(os.open('/dev/md0', os.O_RDWR))
--- END ---
I assume that the sync request should be filtered out at some point
before this assertion is made, since there can be nothing to sync.
I wrote a test case in C. It gets SIGSEGV upon fsync. When making the
rdevs below also read-only the MD device can't be stopped anymore as it
thinks that there is still active IO.
The attached patch should fix it. Please confirm.
I applied this on top of 3.2.37 and it certainly fixes the crash.
However I wonder whether fsync() should fail or should immediately
succeed. I don't know whether the installer expects it to succeed.
Ben.
We have to return a
completion without incrementing the active IO count. Error code -EROFS
seems to be suited best.
But the libc fsync gets -EIO anyway:
Input/output error
Any objection?
Cheers,
Sebastian
--
Ben Hutchings
Any smoothly functioning technology is indistinguishable from a rigged demo.
signature.asc
Description: This is a digitally signed message part
Bug#695182: [PATCH] Subtract min_free_kbytes from dirtyable memory
Dear Jonathan, If you can identify where it was fixed then your patch for older versions should go to stable with a reference to the upstream fix (see Documentation/stable_kernel_rules.txt). How about this patch? It was applied in mainline during the 3.3 merge window, so kernels newer than 3.2.y shouldn't need it. ... commit ab8fabd46f811d5153d8a0cd2fac9a0d41fb593d upstream. ... Yes, I beleive that is the correct patch, surely better than my simple subtraction of min_free_kbytes. Noting, that this does not solve all problems, the latest 3.8 kernel still crashes with OOM: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1098961/comments/18 Thanks, Paul Paul Szabo p...@maths.usyd.edu.au http://www.maths.usyd.edu.au/u/psz/ School of Mathematics and Statistics University of SydneyAustralia -- 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/201301262023.r0qkniak029...@como.maths.usyd.edu.au
Bug#698917: linux-image-3.2.0-4-amd64: cpu overheat and shutdown after suspend/resume cycle on Thinkpad T410
On Sat, Jan 26, 2013 at 04:44:09PM +, Ben Hutchings wrote: But in the case where you resume and then the machine overheats, does the fan run at any time between resume and shutdown? I have heard of bugs that would cause some laptops not to start the fan after resume. No - it doesnt run - at least i havent noticed it. When you turn on the notebook after shutdown you can immediatly hear the fan turn up to maximum. I am running 3.7 from experimental now and made approx 20 Suspend/Resume cycles without any problem. Flo -- Florian Lohoff f...@zz.de signature.asc Description: Digital signature
Bug#699056: linux-image-3.2.0-4-amd64: kernel BUG at /build/buildd-linux_3.2.35-2-amd64-v9djlH/linux-3.2.35/fs/locks.c:2104!
Package: src:linux Version: 3.2.35-2 Severity: normal Dear Maintainer, I know, that the information I can give is most likely not enough for tracking the bug. The bad thing is, that I don't have direct access to the console of the system, a 48-core machine with 512 GB main memory. From time to time, about every two weeks, it happens, that the system stalls. It is ping-able, but it's not possible to connect via ssh or to use existing SSH-sessions. After rebooting, the following error is found in kern.log: Jan 26 15:19:19 prost kernel: [798028.655254] [ cut here ] Jan 26 15:19:19 prost kernel: [798028.659193] kernel BUG at /build/buildd-linux_3.2.35-2-amd64-v9djlH/linux-3.2.35/fs/locks.c:2104! Jan 26 15:19:19 prost kernel: [798028.659193] invalid opcode: [#1] SMP Jan 26 15:19:19 prost kernel: [798028.659193] CPU 0 If you need more information, I will try the best what is possible on a machine in production use… -- Package-specific info: ** Version: Linux version 3.2.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.35-2 ** Command line: BOOT_IMAGE=/vmlinuz-3.2.0-4-amd64 root=UUID=7a8c2b23-84f9-4495-aa8e-391262c1f3bd ro ** Not tainted ** Kernel log: [ 19.323059] EDAC MC: DCT1 chip selects: [ 19.323060] EDAC amd64: MC: 0: 8192MB 1: 8192MB [ 19.323159] EDAC amd64: MC: 2: 8192MB 3: 8192MB [ 19.323257] EDAC amd64: MC: 4: 0MB 5: 0MB [ 19.323355] EDAC amd64: MC: 6: 0MB 7: 0MB [ 19.323453] EDAC amd64: using x8 syndromes. [ 19.323571] EDAC amd64: MCT channel count: 2 [ 19.323689] EDAC amd64: CS0: Registered DDR3 RAM [ 19.323787] EDAC amd64: CS1: Registered DDR3 RAM [ 19.323885] EDAC amd64: CS2: Registered DDR3 RAM [ 19.323983] EDAC amd64: CS3: Registered DDR3 RAM [ 19.324156] EDAC MC5: Giving out device to 'amd64_edac' 'F15h': DEV :00:1d.2 [ 19.324330] EDAC amd64: DRAM ECC enabled. [ 19.324446] EDAC amd64: F15h detected (node 6). [ 19.324738] EDAC MC: DCT0 chip selects: [ 19.324740] EDAC amd64: MC: 0: 8192MB 1: 8192MB [ 19.324860] EDAC amd64: MC: 2: 8192MB 3: 8192MB [ 19.324957] EDAC amd64: MC: 4: 0MB 5: 0MB [ 19.325054] EDAC amd64: MC: 6: 0MB 7: 0MB [ 19.325152] EDAC MC: DCT1 chip selects: [ 19.325153] EDAC amd64: MC: 0: 8192MB 1: 8192MB [ 19.325250] EDAC amd64: MC: 2: 8192MB 3: 8192MB [ 19.325347] EDAC amd64: MC: 4: 0MB 5: 0MB [ 19.325443] EDAC amd64: MC: 6: 0MB 7: 0MB [ 19.325542] EDAC amd64: using x8 syndromes. [ 19.325637] EDAC amd64: MCT channel count: 2 [ 19.325755] EDAC amd64: CS0: Registered DDR3 RAM [ 19.325851] EDAC amd64: CS1: Registered DDR3 RAM [ 19.325948] EDAC amd64: CS2: Registered DDR3 RAM [ 19.326067] EDAC amd64: CS3: Registered DDR3 RAM [ 19.326211] EDAC MC6: Giving out device to 'amd64_edac' 'F15h': DEV :00:1e.2 [ 19.326404] EDAC amd64: DRAM ECC enabled. [ 19.326532] EDAC amd64: F15h detected (node 7). [ 19.326839] EDAC MC: DCT0 chip selects: [ 19.326842] EDAC amd64: MC: 0: 8192MB 1: 8192MB [ 19.326941] EDAC amd64: MC: 2: 8192MB 3: 8192MB [ 19.327040] EDAC amd64: MC: 4: 0MB 5: 0MB [ 19.327138] EDAC amd64: MC: 6: 0MB 7: 0MB [ 19.327254] EDAC MC: DCT1 chip selects: [ 19.327255] EDAC amd64: MC: 0: 8192MB 1: 8192MB [ 19.327353] EDAC amd64: MC: 2: 8192MB 3: 8192MB [ 19.327451] EDAC amd64: MC: 4: 0MB 5: 0MB [ 19.327550] EDAC amd64: MC: 6: 0MB 7: 0MB [ 19.327648] EDAC amd64: using x8 syndromes. [ 19.327744] EDAC amd64: MCT channel count: 2 [ 19.327869] EDAC amd64: CS0: Registered DDR3 RAM [ 19.327967] EDAC amd64: CS1: Registered DDR3 RAM [ 19.328080] EDAC amd64: CS2: Registered DDR3 RAM [ 19.328178] EDAC amd64: CS3: Registered DDR3 RAM [ 19.328325] EDAC MC7: Giving out device to 'amd64_edac' 'F15h': DEV :00:1f.2 [ 19.328565] EDAC PCI0: Giving out device to module 'amd64_edac' controller 'EDAC PCI controller': DEV ':00:18.2' (POLLED) [ 19.395942] alg: No test for __gcm-aes-aesni (__driver-gcm-aes-aesni) [ 19.438742] powernow-k8: Found 8 AMD Opteron(TM) Processor 6238 (48 cpu cores) (version 2.20.00) [ 19.438940] powernow-k8: Core Performance Boosting: on. [ 19.439069] [Firmware Bug]: powernow-k8: No compatible ACPI _PSS objects found. [ 19.439071] [Firmware Bug]: powernow-k8: Try again with latest BIOS. [ 23.426996] Adding 19531244k swap on /dev/sdi2. Priority:-1 extents:1 across:19531244k [ 23.454499] EXT4-fs (sdi3): re-mounted. Opts: (null) [ 23.614092] EXT4-fs (sdi3): re-mounted. Opts: errors=remount-ro [ 23.725034] loop: module loaded [ 23.735019] device-mapper: multipath: version 1.3.0 loaded [ 23.824539] device-mapper: multipath round-robin: version 1.0.0 loaded [ 23.824861] device-mapper: table: 254:0: multipath: error getting device [ 23.824967] device-mapper: ioctl: error adding target to table [ 23.825914] device-mapper: table:
Bug#687442: Test packages for this bug
Julien Cristau's latest test packages can be installed using APT as follows: gpg --no-default-keyring --keyring /usr/share/keyrings/debian-keyring.gpg --export 310180050905E40C | apt-key add - echo deb http://people.debian.org/~jcristau/wheezy-drm34/ ./ /etc/apt/sources.list.d/jcristau-wheezy-drm34.list apt-get update apt-get install linux-image-3.2.0-4.drm-amd64 # or -486, or -686-pae Ben. -- Ben Hutchings Any smoothly functioning technology is indistinguishable from a rigged demo. signature.asc Description: This is a digitally signed message part
Processed: severity of 687442 is important, block 692862 with 687442
Processing commands for cont...@bugs.debian.org: severity 687442 important Bug #687442 [src:linux] Use DRM/KMS subsystem from Linux 3.4 in wheezy Severity set to 'important' from 'normal' block 692862 with 687442 Bug #692862 [src:linux] linux-image-3.2.0-4-amd64: hangs with Intel i5-3210M CPU / Intel HD 4000 graphics Bug #689268 [src:linux] linux-image-3.2.0-3-amd64: Intel HD 4000 (Ivy Bridge) graphics freeze Bug #692234 [src:linux] Intel DH77EB (H77): sporadic freeze and increased power consumption during interactive use Bug #692500 [src:linux] [linux-image-amd64] system freezes with Ivy Brigde CPU 692862 was not blocked by any bugs. 692862 was not blocking any bugs. Added blocking bug(s) of 692862: 687442 689268 was not blocked by any bugs. 689268 was not blocking any bugs. Added blocking bug(s) of 689268: 687442 692234 was not blocked by any bugs. 692234 was not blocking any bugs. Added blocking bug(s) of 692234: 687442 692500 was not blocked by any bugs. 692500 was not blocking any bugs. Added blocking bug(s) of 692500: 687442 thanks Stopping processing here. Please contact me if you need assistance. -- 687442: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687442 689268: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689268 692234: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692234 692500: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692500 692862: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692862 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.135923883020433.transcr...@bugs.debian.org
Bug#689268: Bug#692234: Processed: severity of 689268 is important
On Sat, 2013-01-26 at 19:48 +0100, Ingo wrote: Am 26.01.2013 19:06, schrieb Debian Bug Tracking System: Processing commands for cont...@bugs.debian.org: severity 689268 important Bug #689268 [src:linux] linux-image-3.2.0-3-amd64: Intel HD 4000 (Ivy Bridge) graphics freeze Bug #692234 [src:linux] Intel DH77EB (H77): sporadic freeze and increased power consumption during interactive use Bug #692500 [src:linux] [linux-image-amd64] system freezes with Ivy Brigde CPU Bug #692862 [src:linux] linux-image-3.2.0-4-amd64: hangs with Intel i5-3210M CPU / Intel HD 4000 graphics Severity set to 'important' from 'serious' Severity set to 'important' from 'serious' Severity set to 'important' from 'serious' Severity set to 'important' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. Does that really mean that this bug is going to be released with Wheezy? If yes, this means Wheezy should not be installed on Ivy-Bridge systems with HD4000. I'm not going to insist that it's a blocker for the release though I will be very disappointed if we don't fix it. I think we will. Wouldn't it be a feasible alternative to accept kernel 3.4.x as an alternative in the repository (besides Wheezy's 3.2)? 3.4 is a long term kernel and well maintained by Greg K-H.. I am currently on 3.4.25 from kernel.org which is distributed by openSuse as well. It runs flawlessly on said hardware and does not show any incompatibilities with any Wheezy-component here. We can't support two different kernel versions but we can potentially update the DRM drivers to the versions in Linux 3.4.y. This is covered by bug #687442 which I've marked as blocking this bug. Julien Cristau prepared some packages for testing before we make this change. Here's how you would install them with APT: gpg --no-default-keyring --keyring /usr/share/keyrings/debian-keyring.gpg --export 310180050905E40C | apt-key add - echo deb http://people.debian.org/~jcristau/wheezy-drm34/ ./ /etc/apt/sources.list.d/jcristau-wheezy-drm34.list apt-get update apt-get install linux-image-3.2.0-4.drm-amd64 # or -486, or -686-pae Please test and send your results (good or bad) to 687...@bugs.debian.org I did nort yet install 3.4.26 which appearently got a major backport of Intel's drm/i915 - 25 commits in total. Most of those are bug fixes that we already had and that Julien requested for 3.4.y. Ben. -- Ben Hutchings Any smoothly functioning technology is indistinguishable from a rigged demo. signature.asc Description: This is a digitally signed message part
Bug#699063: needs versioned build-depends against linux-libc-dev = 3.7
Package: linux-tools Version: 3.7.1-1~experimental.1 package FTFBS with older linux-libc-dev, please bumb build-depends accordingly. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- 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/51045ca6.9000...@progress-technologies.net
Bug#699063: marked as done (needs versioned build-depends against linux-libc-dev = 3.7)
Your message dated Sun, 27 Jan 2013 00:20:06 +0100 with message-id 510464a6.4040...@progress-technologies.net and subject line Re: Bug#699063: Acknowledgement (needs versioned build-depends against linux-libc-dev = 3.7) has caused the Debian Bug report #699063, regarding needs versioned build-depends against linux-libc-dev = 3.7 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.) -- 699063: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699063 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-tools Version: 3.7.1-1~experimental.1 package FTFBS with older linux-libc-dev, please bumb build-depends accordingly. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ ---End Message--- ---BeginMessage--- hmm, seems to have been another issue, closing, sorry for the noise. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/---End Message---
Processed: tagging 685726
Processing commands for cont...@bugs.debian.org: tags 685726 + pending Bug #685726 [src:linux] linux-image-3.2.0-3-amd64: return error when trying to format image file (mkfs -t ext4 file.img) Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 685726: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685726 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.13592456608769.transcr...@bugs.debian.org
Bug#685726: linux-image-3.2.0-3-amd64: return error when trying
On Tue, 2012-11-13 at 02:33 +0400, hr...@infotech.am wrote: Yeah, Bug is not completely disappeared, my test was done in new formatted partition, which was almost free, and no any error was appeared for image 160Gb. But when I tried to format 160Gb image file on the other machine, where the 2Tb partition is full more than 80% and fragmented, I could reproduce the bug. I'm not sure that these facts are directly connected to bug reproduction, but doing few test on different machines, I'm able to reproduce the error. This doesn't include any of the changes that were expected to fix this bug, as you did not report that you had tested them. Yeah, I haven't chance to compile and test the new kernel due to lack of time:( I was able to reproduce this with: SCRATCH=/dev/sdc1 mke2fs -t ext4 -m 0 $SCRATCH mount $SCRATCH /mnt dd if=/dev/zero of=/mnt/test.img bs=256M count=640 losetup /dev/loop0 /mnt/test.img mke2fs -t ext4 /dev/loop0 I tested Ted's patches on top of 3.2.37 (one of them needed a context change as we already got commit dee1f973ca341c266229faa5a1a5bb268bed3531) and they seem to fix the problem: I see no errors from mke2fs, or the kernel, or subsequent 'fsck.ext4 -f' of the inner and outer filesystems. I have therefore committed these for the next Debian release and will also queue them up for 3.2.y. Ben. -- Ben Hutchings Experience is what causes a person to make new mistakes instead of old ones. signature.asc Description: This is a digitally signed message part
Processed: tagging 696650
Processing commands for cont...@bugs.debian.org: tags 696650 + pending Bug #696650 [linux] fsync() of read-only RAID triggers BUG Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 696650: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696650 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.135924727620925.transcr...@bugs.debian.org
Bug#699056: linux-image-3.2.0-4-amd64: kernel BUG at /build/buildd-linux_3.2.35-2-amd64-v9djlH/linux-3.2.35/fs/locks.c:2104!
On Sat, 2013-01-26 at 21:34 +0100, Erik Braun wrote: Package: src:linux Version: 3.2.35-2 Severity: normal Dear Maintainer, I know, that the information I can give is most likely not enough for tracking the bug. The bad thing is, that I don't have direct access to the console of the system, a 48-core machine with 512 GB main memory. How about netconsole or an IPMI serial console? From time to time, about every two weeks, it happens, that the system stalls. It is ping-able, but it's not possible to connect via ssh or to use existing SSH-sessions. After rebooting, the following error is found in kern.log: Jan 26 15:19:19 prost kernel: [798028.655254] [ cut here ] Jan 26 15:19:19 prost kernel: [798028.659193] kernel BUG at /build/buildd-linux_3.2.35-2-amd64-v9djlH/linux-3.2.35/fs/locks.c:2104! Jan 26 15:19:19 prost kernel: [798028.659193] invalid opcode: [#1] SMP Jan 26 15:19:19 prost kernel: [798028.659193] CPU 0 [...] That's all it says? Nothing more before the next boot messages? Ben. -- Ben Hutchings Experience is what causes a person to make new mistakes instead of old ones. signature.asc Description: This is a digitally signed message part
