Bug#680513: linux-image-3.4-trunk-amd64: bad rss-counter state
Am Montag, den 06.08.2012, 10:59 +0200 schrieb Michael Below: Was this crash reproducible? Does upgrading to 3.5 from experimental avoid trouble? Am I correct in guessing that 3.2.y from wheezy is not affected? ... I will try the 3.5 kernel soon, but first I will see what I can tell you about the rcu_sched_state bug in 3.2 (#656196). To check out if that 3.2 bug is fixed I tried 3.3rc6. I noticed that the rss-counter state issue didn't appear there. -- Michael Below be...@judiz.de -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680513: linux-image-3.4-trunk-amd64: bad rss-counter state
Hi Michael, Michael Below wrote: after the system had been idle (lunch break) I found a message BUG: bad rss-counter state in the log file, see below It seems to be solved here: https://lkml.org/lkml/2012/6/9/47 For reference, that link leads to commit 4fe7efdbdfb1c7e7a7f31decfd831c0f31d37091 Author: Konstantin Khlebnikov khlebni...@openvz.org Date: Wed Jun 20 12:53:01 2012 -0700 mm: correctly synchronize rss-counters at exit/exec which is part of 3.5-rc4. Was this crash reproducible? Does upgrading to 3.5 from experimental avoid trouble? Am I correct in guessing that 3.2.y from wheezy is not affected? Thanks for reporting and hope that helps, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680513: linux-image-3.4-trunk-amd64: bad rss-counter state
Hi, Am Montag, den 06.08.2012, 00:33 -0700 schrieb Jonathan Nieder: Was this crash reproducible? Does upgrading to 3.5 from experimental avoid trouble? Am I correct in guessing that 3.2.y from wheezy is not affected? Yes, it is reproducible, the error happens daily a couple of times if I am running 3.4 from experimental. Mostly, I see it during shutdown. But it's not a crash that brings down the system. I haven't seen this bug with 3.2 kernels. I will try the 3.5 kernel soon, but first I will see what I can tell you about the rcu_sched_state bug in 3.2 (#656196). Thanks Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680513: linux-image-3.4-trunk-amd64: bad rss-counter state
Package: src Version: 3.4.4-1~experimental.1 Severity: normal Tags: upstream patch Dear Maintainer, after the system had been idle (lunch break) I found a message BUG: bad rss-counter state in the log file, see below It seems to be solved here: https://lkml.org/lkml/2012/6/9/47 Cheers Michael -- Package-specific info: ** Version: Linux version 3.4-trunk-amd64 (Debian 3.4.4-1~experimental.1) (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-1) ) #1 SMP Tue Jun 26 17:23:03 UTC 2012 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.4-trunk-amd64 root=UUID=66e75d80-ed82-400a-9c84-397b29fef7ce ro quiet ** Not tainted ** Kernel log: [6.243325] [drm] Loading RS780 Microcode [6.506830] usb 1-4: reset high-speed USB device number 4 using ehci_hcd [6.556900] [drm] PCIE GART of 512M enabled (table at 0xC004). [6.557027] radeon :01:05.0: WB enabled [6.557036] [drm] fence driver on ring 0 use gpu addr 0xac00 and cpu addr 0x88006b255c00 [6.589273] [drm] ring test on 0 succeeded in 1 usecs [6.589507] [drm] ib test on ring 0 succeeded in 0 usecs [6.590027] [drm] Radeon Display Connectors [6.590033] [drm] Connector 0: [6.590037] [drm] VGA [6.590042] [drm] DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c [6.590047] [drm] Encoders: [6.590051] [drm] CRT1: INTERNAL_KLDSCP_DAC1 [6.590055] [drm] Connector 1: [6.590059] [drm] DVI-D [6.590062] [drm] HPD1 [6.590068] [drm] DDC: 0x7e50 0x7e50 0x7e54 0x7e54 0x7e58 0x7e58 0x7e5c 0x7e5c [6.590072] [drm] Encoders: [6.590076] [drm] DFP1: INTERNAL_KLDSCP_LVTMA [6.590130] [drm] radeon: power management initialized [6.636560] [drm] fb mappable at 0xE0142000 [6.636561] [drm] vram apper at 0xE000 [6.636563] [drm] size 3981312 [6.636564] [drm] fb depth is 24 [6.636565] [drm]pitch is 4608 [6.636664] fbcon: radeondrmfb (fb0) is primary device [6.659298] Console: switching to colour frame buffer device 144x54 [6.668563] fb0: radeondrmfb frame buffer device [6.668566] drm: registered panic notifier [6.668599] [drm] Initialized radeon 2.16.0 20080528 for :01:05.0 on minor 0 [6.993140] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [6.993728] Registered led device: rt73usb-phy0::radio [6.993782] Registered led device: rt73usb-phy0::assoc [6.993831] Registered led device: rt73usb-phy0::quality [6.995186] usbcore: registered new interface driver rt73usb [7.121136] input: HDA Digital PCBeep as /devices/pci:00/:00:14.2/input/input8 [8.281749] Adding 3004148k swap on /dev/sda2. Priority:-1 extents:1 across:3004148k [8.653588] EXT3-fs (sda4): using internal journal [8.950590] loop: module loaded [8.961619] smsc47b397: found SMSC SCH5317 (base address 0x0880, revision 1) [ 10.456104] tmpfs: Bad mount option errors [ 13.058468] fuse init (API version 7.18) [ 13.584907] kjournald starting. Commit interval 5 seconds [ 13.585179] EXT3-fs (dm-3): using internal journal [ 13.585190] EXT3-fs (dm-3): mounted filesystem with ordered data mode [ 13.624955] kjournald starting. Commit interval 5 seconds [ 13.625497] EXT3-fs (dm-2): using internal journal [ 13.625505] EXT3-fs (dm-2): mounted filesystem with ordered data mode [ 13.672690] kjournald starting. Commit interval 5 seconds [ 13.673020] EXT3-fs (dm-0): using internal journal [ 13.673027] EXT3-fs (dm-0): mounted filesystem with ordered data mode [ 13.722760] kjournald starting. Commit interval 5 seconds [ 13.723134] EXT3-fs (dm-1): using internal journal [ 13.723141] EXT3-fs (dm-1): mounted filesystem with ordered data mode [ 26.728730] tg3 :3f:00.0: irq 41 for MSI/MSI-X [ 26.776222] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 27.136120] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 30.117359] wlan0: authenticate with 00:c0:02:1a:80:bc [ 30.156855] wlan0: send auth to 00:c0:02:1a:80:bc (try 1/3) [ 30.158835] wlan0: authenticated [ 30.179448] wlan0: associate with 00:c0:02:1a:80:bc (try 1/3) [ 30.183293] wlan0: RX AssocResp from 00:c0:02:1a:80:bc (capab=0x471 status=0 aid=3) [ 30.183301] wlan0: associated [ 30.195247] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 40.706773] wlan0: no IPv6 routers present [ 51.506418] Bluetooth: Core ver 2.16 [ 51.506473] NET: Registered protocol family 31 [ 51.506479] Bluetooth: HCI device and connection manager initialized [ 51.506486] Bluetooth: HCI socket layer initialized [ 51.506491] Bluetooth: L2CAP socket layer initialized [ 51.506500] Bluetooth: SCO socket layer initialized [ 51.533836] Bluetooth: RFCOMM TTY layer initialized [ 51.533848] Bluetooth: RFCOMM socket layer initialized [ 51.533855] Bluetooth: RFCOMM ver 1.11 [ 51.880732] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 51.880740] Bluetooth: BNEP filters: protocol multicast [ 57.637638] lp:
