Bug#701189: linux-image-3.7-trunk-amd64: 3.7.8 locks up occasionally
On Wednesday, 20 March 2013 at 23:57, Ben Hutchings wrote: > That was the change that caused this memory leak. I doubt that it has > anything to do with the bug you reported. Well, I'll upload 3.8.4 soon > and you can find out whether it is really fixed. 3.8.5 ran for 33 days now without problems, so it looks fixed. Best regards, Christian Ohm -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#701189: linux-image-3.7-trunk-amd64: 3.7.8 locks up occasionally
On Wed, 2013-03-20 at 22:51 +0100, Christian Ohm wrote: > > On Monday, 25 February 2013 at 4:10, Ben Hutchings wrote: > > > Instead of updating to 3.7.9, I'll be uploading 3.8 to experimental > > > shortly. Could you report whether that is more stable, once you've used > > > it for a while? > > So far, I've had two more hangs under 3.7, but in general it was pretty > ok. 3.8 didn't hang in the short time I tried it, but it lost the > network card pretty soon after booting, spamming the kernel log with > lots of "atl1c :02:00.0: PCI-DMA: Out of IOMMU space for 1522 bytes" > (with different sizes). Google gives > https://bugzilla.redhat.com/show_bug.cgi?id=918393 which indicates that > the just released kernel 3.8.4 includes a fix for that. Right, there was a change to atl1c in Linux 3.8 that causes it to leak memory very quickly. > I've also found > https://www.kernel.org/pub/linux/kernel/projects/backports/stable/v3.8/ChangeLog-3.8-1 > saying "2) PCI dma mapping errors in atl1c are not checked for and this > cause hard crashes for some users, from Xiong Huang." which seems to be > the cause of the broken network, and also might be a fix for the hangs > in 3.7. That was the change that caused this memory leak. I doubt that it has anything to do with the bug you reported. Well, I'll upload 3.8.4 soon and you can find out whether it is really fixed. Ben. -- Ben Hutchings The generation of random numbers is too important to be left to chance. - Robert Coveyou signature.asc Description: This is a digitally signed message part
Bug#701189: linux-image-3.7-trunk-amd64: 3.7.8 locks up occasionally
> On Monday, 25 February 2013 at 4:10, Ben Hutchings wrote: > > Instead of updating to 3.7.9, I'll be uploading 3.8 to experimental > > shortly. Could you report whether that is more stable, once you've used > > it for a while? So far, I've had two more hangs under 3.7, but in general it was pretty ok. 3.8 didn't hang in the short time I tried it, but it lost the network card pretty soon after booting, spamming the kernel log with lots of "atl1c :02:00.0: PCI-DMA: Out of IOMMU space for 1522 bytes" (with different sizes). Google gives https://bugzilla.redhat.com/show_bug.cgi?id=918393 which indicates that the just released kernel 3.8.4 includes a fix for that. I've also found https://www.kernel.org/pub/linux/kernel/projects/backports/stable/v3.8/ChangeLog-3.8-1 saying "2) PCI dma mapping errors in atl1c are not checked for and this cause hard crashes for some users, from Xiong Huang." which seems to be the cause of the broken network, and also might be a fix for the hangs in 3.7. Best regards, Christian Ohm -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#701189: linux-image-3.7-trunk-amd64: 3.7.8 locks up occasionally
On Monday, 25 February 2013 at 4:10, Ben Hutchings wrote: > Instead of updating to 3.7.9, I'll be uploading 3.8 to experimental > shortly. Could you report whether that is more stable, once you've used > it for a while? Sure. I usually update the kernel once the corresponding linux-tools package is available (for perf), but depending on how annoying 3.7 gets I might update earlier this time. Best regards, Christian Ohm -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#701189: linux-image-3.7-trunk-amd64: 3.7.8 locks up occasionally
Control: tag -1 moreinfo On Fri, 2013-02-22 at 15:48 +0100, Christian Ohm wrote: > Package: src:linux > Version: 3.7.8-1~experimental.1 > Severity: important > > Dear Maintainer, > > After upgrading from 3.7.3-1~experimental.1 to 3.7.8-1~experimental.1, > my system locked up occasionally. 3.7.3 had an uptime of about one > month, with frequent suspend to ram. 3.7.8 locked up after a short time > (two or three times now since the update). I didn't see anything in the > logs, screen was off, the music that was playing hung in a short > repeating loop, keyboard leds were normal iirc. I'm not sure if any of > the patches in 3.7.9 might fix this, but I notice that it came out quite > quickly with only a few changes, so it seems important. [...] Linux 3.7.9 has a fix for a regression in xfs in 3.7.6, but the rest of the fixes are for older bugs. Instead of updating to 3.7.9, I'll be uploading 3.8 to experimental shortly. Could you report whether that is more stable, once you've used it for a while? Ben. -- Ben Hutchings Absolutum obsoletum. (If it works, it's out of date.) - Stafford Beer signature.asc Description: This is a digitally signed message part
Bug#701189: linux-image-3.7-trunk-amd64: 3.7.8 locks up occasionally
Package: src:linux Version: 3.7.8-1~experimental.1 Severity: important Dear Maintainer, After upgrading from 3.7.3-1~experimental.1 to 3.7.8-1~experimental.1, my system locked up occasionally. 3.7.3 had an uptime of about one month, with frequent suspend to ram. 3.7.8 locked up after a short time (two or three times now since the update). I didn't see anything in the logs, screen was off, the music that was playing hung in a short repeating loop, keyboard leds were normal iirc. I'm not sure if any of the patches in 3.7.9 might fix this, but I notice that it came out quite quickly with only a few changes, so it seems important. Best regards, Christian Ohm -- Package-specific info: ** Version: Linux version 3.7-trunk-amd64 (debian-ker...@lists.debian.org) (gcc version 4.7.2 (Debian 4.7.2-5) ) #1 SMP Debian 3.7.8-1~experimental.1 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.7-trunk-amd64 root=UUID=975a37a6-840b-45bc-8020-21b5c0ec8216 ro quiet radeon.pcie_gen2=1 ** Not tainted ** Kernel log: [6.335982] platform radeon_cp.0: firmware: agent loaded radeon/RS780_me.bin into memory [6.408116] input: HDA ATI SB Line as /devices/pci:00/:00:14.2/sound/card0/input6 [6.408429] input: HDA ATI SB Front Mic as /devices/pci:00/:00:14.2/sound/card0/input7 [6.408716] input: HDA ATI SB Rear Mic as /devices/pci:00/:00:14.2/sound/card0/input8 [6.408963] input: HDA ATI SB Front Headphone as /devices/pci:00/:00:14.2/sound/card0/input9 [6.409316] input: HDA ATI SB Line Out Side as /devices/pci:00/:00:14.2/sound/card0/input10 [6.409649] input: HDA ATI SB Line Out CLFE as /devices/pci:00/:00:14.2/sound/card0/input11 [6.409983] input: HDA ATI SB Line Out Surround as /devices/pci:00/:00:14.2/sound/card0/input12 [6.410316] input: HDA ATI SB Line Out Front as /devices/pci:00/:00:14.2/sound/card0/input13 [6.524933] platform radeon_cp.0: firmware: agent loaded radeon/R600_rlc.bin into memory [6.528825] [drm] PCIE GART of 512M enabled (table at 0xC004). [6.528982] radeon :01:05.0: WB enabled [6.528994] radeon :01:05.0: fence driver on ring 0 use gpu addr 0xac00 and cpu addr 0x88040c947c00 [6.529301] radeon :01:05.0: setting latency timer to 64 [6.561305] [drm] ring test on 0 succeeded in 0 usecs [6.561566] [drm] ib test on ring 0 succeeded in 0 usecs [6.562071] [drm] Radeon Display Connectors [6.562075] [drm] Connector 0: [6.562079] [drm] VGA-1 [6.562086] [drm] DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c [6.562089] [drm] Encoders: [6.562093] [drm] CRT1: INTERNAL_KLDSCP_DAC1 [6.562097] [drm] Connector 1: [6.562101] [drm] DVI-D-1 [6.562104] [drm] HPD3 [6.562110] [drm] DDC: 0x7e50 0x7e50 0x7e54 0x7e54 0x7e58 0x7e58 0x7e5c 0x7e5c [6.562113] [drm] Encoders: [6.562117] [drm] DFP3: INTERNAL_KLDSCP_LVTMA [6.562156] [drm] radeon: power management initialized [6.618833] [drm] fb mappable at 0xD0142000 [6.618835] [drm] vram apper at 0xD000 [6.618836] [drm] size 768 [6.618838] [drm] fb depth is 24 [6.618839] [drm]pitch is 6400 [6.619013] fbcon: radeondrmfb (fb0) is primary device [6.668028] Console: switching to colour frame buffer device 200x75 [6.695333] fb0: radeondrmfb frame buffer device [6.695337] drm: registered panic notifier [6.69] [drm] Initialized radeon 2.24.0 20080528 for :01:05.0 on minor 0 [9.021380] Adding 8388604k swap on /dev/sda1. Priority:-1 extents:1 across:8388604k [9.062754] EXT4-fs (sda3): re-mounted. Opts: (null) [9.367789] EXT4-fs (sda3): re-mounted. Opts: errors=remount-ro,commit=15 [9.552690] fuse init (API version 7.20) [9.629498] loop: module loaded [9.680781] lirc_dev: IR Remote Control driver registered, major 249 [9.792764] it87: Found IT8721F chip at 0xe80, revision 3 [9.792788] it87: Beeping is supported [9.792857] ACPI Warning: 0x0e85-0x0e86 SystemIO conflicts with Region \HWMR 1 (20120913/utaddress-251) [9.792872] ACPI Warning: 0x0e85-0x0e86 SystemIO conflicts with Region \IOHD 2 (20120913/utaddress-251) [9.792885] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 16.420874] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null) [ 16.464168] EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: (null) [ 16.525970] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) [ 16.591829] kjournald starting. Commit interval 5 seconds [ 16.594468] EXT3-fs (sdc1): using internal journal [ 16.594480] EXT3-fs (sdc1): mounted filesystem with ordered data mode [ 17.616752] atl1c :02:00.0: irq 42 for MSI/MSI-X [ 17.616885] atl1c :02:00.0: atl1c: eth1 NIC Link is Up<1000 Mb
