Bug#771045: Info received (Bug#771045: Info received (Bug#771045: Info received (Bug#771045: Acknowledgement (linux-image-3.16.0-4-amd64: System randomly freezes using Kernel 3.16 and radeon))))
Still freezes. Switching now to Arch. Tom -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771045: Info received (Bug#771045: Info received (Bug#771045: Info received (Bug#771045: Acknowledgement (linux-image-3.16.0-4-amd64: System randomly freezes using Kernel 3.16 and radeon))))
Still random freezes with kernel: 3.16.7-ckt7-1 (2015-03-01) Bests Tom -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771045: Info received (Bug#771045: Info received (Bug#771045: Info received (Bug#771045: Acknowledgement (linux-image-3.16.0-4-amd64: System randomly freezes using Kernel 3.16 and radeon))))
Random system freezes with power management disabled: [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 root=UUID=8b037d1e-7609-4503-bea5-d0d4f2a4107f ro quiet radeon.dpm=0 radeon.audio=0 How can I help to provide more information? Bests Tom -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771045: Info received (Bug#771045: Info received (Bug#771045: Acknowledgement (linux-image-3.16.0-4-amd64: System randomly freezes using Kernel 3.16 and radeon)))
Hello. The bug still appears: [22705.085397] radeon :03:00.0: ring 0 stalled for more than 10012msec [22705.085402] radeon :03:00.0: GPU lockup (waiting for 0x00248486 last fence id 0x0024847f on ring 0) [22705.085432] radeon :03:00.0: failed to get a new IB (-35) [22705.572187] radeon :03:00.0: Saved 11021 dwords of commands on ring 0. [22705.572316] radeon :03:00.0: GPU softreset: 0x006C [22705.572318] radeon :03:00.0: GRBM_STATUS = 0xA0003028 [22705.572320] radeon :03:00.0: GRBM_STATUS_SE0 = 0x0006 [22705.572322] radeon :03:00.0: GRBM_STATUS_SE1 = 0x0006 [22705.572323] radeon :03:00.0: SRBM_STATUS = 0x20C0 [22705.572434] radeon :03:00.0: SRBM_STATUS2 = 0x [22705.572436] radeon :03:00.0: R_008674_CP_STALLED_STAT1 = 0x [22705.572438] radeon :03:00.0: R_008678_CP_STALLED_STAT2 = 0x0001 [22705.572439] radeon :03:00.0: R_00867C_CP_BUSY_STAT = 0x0002 [22705.572441] radeon :03:00.0: R_008680_CP_STAT = 0x80010243 [22705.572443] radeon :03:00.0: R_00D034_DMA_STATUS_REG = 0x44483146 [22705.572445] radeon :03:00.0: R_00D834_DMA_STATUS_REG = 0x44C84246 [22705.572447] radeon :03:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x [22705.572449] radeon :03:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x [22706.056014] radeon :03:00.0: GRBM_SOFT_RESET=0xDDFF [22706.056069] radeon :03:00.0: SRBM_SOFT_RESET=0x00100140 [22706.057216] radeon :03:00.0: GRBM_STATUS = 0x3028 [22706.057218] radeon :03:00.0: GRBM_STATUS_SE0 = 0x0006 [22706.057220] radeon :03:00.0: GRBM_STATUS_SE1 = 0x0006 [22706.057221] radeon :03:00.0: SRBM_STATUS = 0x20C0 [22706.057332] radeon :03:00.0: SRBM_STATUS2 = 0x [22706.057334] radeon :03:00.0: R_008674_CP_STALLED_STAT1 = 0x [22706.057336] radeon :03:00.0: R_008678_CP_STALLED_STAT2 = 0x [22706.057337] radeon :03:00.0: R_00867C_CP_BUSY_STAT = 0x [22706.057339] radeon :03:00.0: R_008680_CP_STAT = 0x [22706.057341] radeon :03:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 [22706.057343] radeon :03:00.0: R_00D834_DMA_STATUS_REG = 0x44C83D57 [22706.057584] radeon :03:00.0: GPU reset succeeded, trying to resume [22706.084253] [drm] probing gen 2 caps for device 8086:e04 = 7a7903/e [22706.084257] [drm] PCIE gen 3 link speeds already enabled [22706.086412] [drm] PCIE GART of 1024M enabled (table at 0x00276000). [22706.086525] radeon :03:00.0: WB enabled [22706.086527] radeon :03:00.0: fence driver on ring 0 use gpu addr 0x8c00 and cpu addr 0x88085b69fc00 [22706.086529] radeon :03:00.0: fence driver on ring 1 use gpu addr 0x8c04 and cpu addr 0x88085b69fc04 [22706.086530] radeon :03:00.0: fence driver on ring 2 use gpu addr 0x8c08 and cpu addr 0x88085b69fc08 [22706.086532] radeon :03:00.0: fence driver on ring 3 use gpu addr 0x8c0c and cpu addr 0x88085b69fc0c [22706.086533] radeon :03:00.0: fence driver on ring 4 use gpu addr 0x8c10 and cpu addr 0x88085b69fc10 [22706.087140] radeon :03:00.0: fence driver on ring 5 use gpu addr 0x00075a18 and cpu addr 0xc90015eb5a18 [22706.250455] [drm] ring test on 0 succeeded in 3 usecs [22706.250461] [drm] ring test on 1 succeeded in 1 usecs [22706.250465] [drm] ring test on 2 succeeded in 1 usecs [22706.250476] [drm] ring test on 3 succeeded in 6 usecs [22706.250484] [drm] ring test on 4 succeeded in 5 usecs [22706.426300] [drm] ring test on 5 succeeded in 2 usecs [22706.426307] [drm] UVD initialized successfully. [22716.434414] radeon :03:00.0: ring 0 stalled for more than 10004msec [22716.434419] radeon :03:00.0: GPU lockup (waiting for 0x002484f4 last fence id 0x0024847f on ring 0) [22716.434421] [drm:r600_ib_test] *ERROR* radeon: fence wait failed (-35). [22716.434424] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on GFX ring (-35). [22716.434426] radeon :03:00.0: ib ring test failed (-35). [22716.918923] radeon :03:00.0: GPU softreset: 0x0048 [22716.918929] radeon :03:00.0: GRBM_STATUS = 0xA0003028 [22716.918932] radeon :03:00.0: GRBM_STATUS_SE0 = 0x0006 [22716.918933] radeon :03:00.0: GRBM_STATUS_SE1 = 0x0006 [22716.918935] radeon :03:00.0: SRBM_STATUS = 0x20C0 [22716.919046] radeon :03:00.0: SRBM_STATUS2 = 0x [22716.919048] radeon :03:00.0: R_008674_CP_STALLED_STAT1 = 0x [22716.919050] radeon :03:00.0: R_008678_CP_STALLED_STAT2 = 0x0001 [22716.919052] radeon :03:00.0: R_00867C_CP_BUSY_STAT = 0x0002
Bug#771045: Info received (Bug#771045: Acknowledgement (linux-image-3.16.0-4-amd64: System randomly freezes using Kernel 3.16 and radeon))
Thank you for testing this. Would you file a bug in the mesa packages to resolve this problem, please? Thank you again and kind regards! Tom -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771045: Info received (Bug#771045: Acknowledgement (linux-image-3.16.0-4-amd64: System randomly freezes using Kernel 3.16 and radeon))
Further freezes: Bests Tom [ 1198.159861] radeon :02:00.0: GPU fault detected: 147 0x0fa29002 [ 1198.159864] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x000117B2 [ 1198.159866] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x030E0002 [ 1198.159868] VM fault (0x02, vmid 1) at page 71602, write from CB (224) [ 1198.159871] radeon :02:00.0: GPU fault detected: 147 0x01626002 [ 1198.159873] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00011796 [ 1198.159875] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x02048002 [ 1198.159877] VM fault (0x02, vmid 1) at page 71574, read from TC (72) [ 1198.159877] systemd-journald[233]: /dev/kmsg buffer overrun, some messages lost. [ 1198.159883] radeon :02:00.0: GPU fault detected: 147 0x0e026002 [ 1198.159885] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x000117CA [ 1198.159887] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x030A0002 [ 1198.159890] VM fault (0x02, vmid 1) at page 71626, write from CB (160) [ 1198.159891] systemd-journald[233]: /dev/kmsg buffer overrun, some messages lost. [ 1198.159910] radeon :02:00.0: GPU fault detected: 147 0x0e02e002 [ 1198.159912] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x0001180B [ 1198.159914] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x030A0002 [ 1198.159916] VM fault (0x02, vmid 1) at page 71691, write from CB (160) [ 1198.159920] radeon :02:00.0: GPU fault detected: 147 0x01622002 [ 1198.159922] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00011824 [ 1198.159923] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x030D0002 [ 1198.159925] VM fault (0x02, vmid 1) at page 71716, write from CB (208) [ 1198.159929] radeon :02:00.0: GPU fault detected: 147 0x01621002 [ 1198.159931] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00011731 [ 1198.159933] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x03060002 [ 1198.159935] VM fault (0x02, vmid 1) at page 71473, write from CB (96) [ 1198.159949] radeon :02:00.0: GPU fault detected: 147 0x0e036002 [ 1198.159951] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x0001173B [ 1198.159953] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x02044002 [ 1198.159955] VM fault (0x02, vmid 1) at page 71483, read from TC (68) [ 1198.159959] radeon :02:00.0: GPU fault detected: 147 0x0e036002 [ 1198.159960] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x0001172A [ 1198.159962] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x03020002 [ 1198.159964] VM fault (0x02, vmid 1) at page 71466, write from CB (32) [ 1198.160094] radeon :02:00.0: GPU fault detected: 147 0x0f03d002 [ 1198.160096] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x [ 1198.160098] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x03060002 [ 1198.160100] VM fault (0x02, vmid 1) at page 0, write from CB (96) [ 1198.160147] radeon :02:00.0: GPU fault detected: 147 0x0ec3d002 [ 1198.160149] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x [ 1198.160151] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0303D002 [ 1198.160152] VM fault (0x02, vmid 1) at page 0, write from DMA1 (61) [ 1198.160156] radeon :02:00.0: GPU fault detected: 147 0x0ec3a002 [ 1198.160158] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x0001175E [ 1198.160160] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0303D002 [ 1198.160162] VM fault (0x02, vmid 1) at page 71518, write from DMA1 (61) [ 1198.160220] systemd-journald[233]: /dev/kmsg buffer overrun, some messages lost. [ 1198.160232] radeon :02:00.0: GPU fault detected: 147 0x0e63a002 [ 1198.160234] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x [ 1198.160236] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x02088002 [ 1198.160238] VM fault (0x02, vmid 1) at page 0, read from TC (136) [ 1198.160242] radeon :02:00.0: GPU fault detected: 147 0x0e832002 [ 1198.160244] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0xC94A [ 1198.160246] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x03060004 [ 1198.160248] VM fault (0x04, vmid 1) at page 51530, write from CB (96) [ 1198.160251] radeon :02:00.0: GPU fault detected: 147 0x0e832002 [ 1198.160253] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0xC94A [ 1198.160255] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x02084004 [ 1198.160257] VM fault (0x04, vmid 1) at page 51530, read from TC (132) [ 1198.160262] radeon :02:00.0: GPU fault detected: 147 0x0e639002 [ 1198.160264] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00011747 [ 1198.160266] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x03020002 [ 1198.160268] VM fault (0x02, vmid 1) at page 71495,
Bug#771045: Acknowledgement (linux-image-3.16.0-4-amd64: System randomly freezes using Kernel 3.16 and radeon)
Here is the tail of dmesg after such an error. Best regards Tom Guder [ 1104.412089] radeon :02:00.0: ring 0 stalled for more than 10104msec [ 1104.412098] radeon :02:00.0: GPU lockup (waiting for 0x000664a0 last fence id 0x0006649f on ring 0) [ 1104.412102] radeon :02:00.0: failed to get a new IB (-35) [ 1104.900461] radeon :02:00.0: Saved 21357 dwords of commands on ring 0. [ 1104.900590] radeon :02:00.0: GPU softreset: 0x006C [ 1104.900592] radeon :02:00.0: GRBM_STATUS = 0xA0003028 [ 1104.900593] radeon :02:00.0: GRBM_STATUS_SE0 = 0x0006 [ 1104.900594] radeon :02:00.0: GRBM_STATUS_SE1 = 0x0006 [ 1104.900595] radeon :02:00.0: SRBM_STATUS = 0x20C0 [ 1104.900706] radeon :02:00.0: SRBM_STATUS2 = 0x [ 1104.900707] radeon :02:00.0: R_008674_CP_STALLED_STAT1 = 0x [ 1104.900708] radeon :02:00.0: R_008678_CP_STALLED_STAT2 = 0x0001 [ 1104.900710] radeon :02:00.0: R_00867C_CP_BUSY_STAT = 0x0002 [ 1104.900711] radeon :02:00.0: R_008680_CP_STAT = 0x80010243 [ 1104.900713] radeon :02:00.0: R_00D034_DMA_STATUS_REG = 0x44C83146 [ 1104.900714] radeon :02:00.0: R_00D834_DMA_STATUS_REG = 0x44C84246 [ 1104.900716] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x [ 1104.900718] radeon :02:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x [ 1105.370049] radeon :02:00.0: GRBM_SOFT_RESET=0xDDFF [ 1105.370101] radeon :02:00.0: SRBM_SOFT_RESET=0x00100140 [ 1105.371247] radeon :02:00.0: GRBM_STATUS = 0x3028 [ 1105.371248] radeon :02:00.0: GRBM_STATUS_SE0 = 0x0006 [ 1105.371249] radeon :02:00.0: GRBM_STATUS_SE1 = 0x0006 [ 1105.371250] radeon :02:00.0: SRBM_STATUS = 0x20C0 [ 1105.371361] radeon :02:00.0: SRBM_STATUS2 = 0x [ 1105.371362] radeon :02:00.0: R_008674_CP_STALLED_STAT1 = 0x [ 1105.371363] radeon :02:00.0: R_008678_CP_STALLED_STAT2 = 0x [ 1105.371365] radeon :02:00.0: R_00867C_CP_BUSY_STAT = 0x [ 1105.371366] radeon :02:00.0: R_008680_CP_STAT = 0x [ 1105.371367] radeon :02:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 [ 1105.371369] radeon :02:00.0: R_00D834_DMA_STATUS_REG = 0x44C83D57 [ 1105.371608] radeon :02:00.0: GPU reset succeeded, trying to resume [ 1105.402616] [drm] probing gen 2 caps for device 8086:e04 = 7a7903/e [ 1105.402619] [drm] PCIE gen 3 link speeds already enabled [ 1105.404456] [drm] PCIE GART of 1024M enabled (table at 0x00276000). [ 1105.404557] radeon :02:00.0: WB enabled [ 1105.404559] radeon :02:00.0: fence driver on ring 0 use gpu addr 0x8c00 and cpu addr 0x8800b54c0c00 [ 1105.404560] radeon :02:00.0: fence driver on ring 1 use gpu addr 0x8c04 and cpu addr 0x8800b54c0c04 [ 1105.404561] radeon :02:00.0: fence driver on ring 2 use gpu addr 0x8c08 and cpu addr 0x8800b54c0c08 [ 1105.404561] radeon :02:00.0: fence driver on ring 3 use gpu addr 0x8c0c and cpu addr 0x8800b54c0c0c [ 1105.404562] radeon :02:00.0: fence driver on ring 4 use gpu addr 0x8c10 and cpu addr 0x8800b54c0c10 [ 1105.405169] radeon :02:00.0: fence driver on ring 5 use gpu addr 0x00075a18 and cpu addr 0xc90011fb5a18 [ 1105.564971] [drm] ring test on 0 succeeded in 2 usecs [ 1105.564978] [drm] ring test on 1 succeeded in 1 usecs [ 1105.564984] [drm] ring test on 2 succeeded in 1 usecs [ 1105.564995] [drm] ring test on 3 succeeded in 5 usecs [ 1105.565005] [drm] ring test on 4 succeeded in 5 usecs [ 1105.740770] [drm] ring test on 5 succeeded in 2 usecs [ 1105.740776] [drm] UVD initialized successfully. [ 1115.740176] radeon :02:00.0: ring 0 stalled for more than 1msec [ 1115.740183] radeon :02:00.0: GPU lockup (waiting for 0x000665a7 last fence id 0x0006649f on ring 0) [ 1115.740187] [drm:r600_ib_test] *ERROR* radeon: fence wait failed (-35). [ 1115.740192] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on GFX ring (-35). [ 1115.740195] radeon :02:00.0: ib ring test failed (-35). [ 1116.221093] radeon :02:00.0: GPU softreset: 0x0048 [ 1116.221095] radeon :02:00.0: GRBM_STATUS = 0xA0003028 [ 1116.221097] radeon :02:00.0: GRBM_STATUS_SE0 = 0x0006 [ 1116.221098] radeon :02:00.0: GRBM_STATUS_SE1 = 0x0006 [ 1116.221099] radeon :02:00.0: SRBM_STATUS = 0x20C0 [ 1116.221210] radeon :02:00.0: SRBM_STATUS2 = 0x [ 1116.221211] radeon :02:00.0: R_008674_CP_STALLED_STAT1 = 0x [ 1116.221212] radeon :02:00.0: R_008678_CP_STALLED_STAT2 = 0x0001 [ 1116.221214] radeon
Bug#771042: closed by m...@debian.org (Matteo F. Vescovi) (Bug#771042: fixed in blender 2.72.b+dfsg0-2)
Hello, I can confirm, that this bug doesn't appear anymore. Thank you very much! -- Ingenieurbüro Tom Guder Waldstraße 75 04105 Leipzig Funk.: 0176-82119565 Tel.: 0341-26432046 Internet: www.ib-guder.de USt-IdNr.: DE296778004 Debian Bug Tracking System ow...@bugs.debian.org hat am 3. Dezember 2014 um 14:39 geschrieben: This is an automatic notification regarding your Bug report which was filed against the blender package: #771042: blender: Blender crashes while rendering with cycles It has been closed by m...@debian.org (Matteo F. Vescovi). Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact m...@debian.org (Matteo F. Vescovi) by replying to this email. -- 771042: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771042 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems Matteo F. Vescovi m...@debian.org hat am 3. Dezember 2014 um 14:34 geschrieben: Source: blender Source-Version: 2.72.b+dfsg0-2 We believe that the bug you reported is fixed in the latest version of blender, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 771...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matteo F. Vescovi m...@debian.org (supplier of updated blender package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 03 Dec 2014 10:52:10 +0100 Source: blender Binary: blender blender-data blender-dbg Architecture: source all Version: 2.72.b+dfsg0-2 Distribution: experimental Urgency: medium Maintainer: Debian Multimedia Maintainers pkg-multimedia-maintain...@lists.alioth.debian.org Changed-By: Matteo F. Vescovi m...@debian.org Description: blender- Very fast and versatile 3D modeller/renderer blender-data - Very fast and versatile 3D modeller/renderer - data package blender-dbg - debug symbols for Blender Closes: 771042 Changes: blender (2.72.b+dfsg0-2) experimental; urgency=medium . * debian/control: Uploader e-mail address updated * debian/patches/: patchset updated - #0001 = #0007 refreshed - 0010-fix_atomic_issue.patch added (Closes: #771042) Thanks to Sergey Sharybin (upstream devel) for #0010. Checksums-Sha1: a5ac9469a4e1a8df6fc46292145bc969d8a0f0f0 2883 blender_2.72.b+dfsg0-2.dsc d3adc95d1f78ee3de872bc80b08955c747382ca7 45164 blender_2.72.b+dfsg0-2.debian.tar.xz 9498d801eaafca829585d27663235e8c6fc671ad 7996122 blender-data_2.72.b+dfsg0-2_all.deb Checksums-Sha256: 84e6fe17845eaec9287af14ca37072f12f3143a809a9881fff234b1acd1b3c0b 2883 blender_2.72.b+dfsg0-2.dsc 4cb94c3fc2469bfff52c4e13cb9c24397b655e687232ac468fcfbc0fcb5168b0 45164 blender_2.72.b+dfsg0-2.debian.tar.xz 3863cc0a6d35f9ec62373f263c13ebff4497b9b5212fde400a2677e500759b06 7996122 blender-data_2.72.b+dfsg0-2_all.deb Files: 4d88059283740e636c29e01c2ac9517b 2883 graphics optional blender_2.72.b+dfsg0-2.dsc 3e1f379c21d9f456248f8073718bc80f 45164 graphics optional blender_2.72.b+dfsg0-2.debian.tar.xz 7c7f4a2999d2df721639f42637784d06 7996122 graphics optional blender-data_2.72.b+dfsg0-2_all.deb -BEGIN PGP SIGNATURE- Comment: Debian powered! iQJ8BAEBCgBmBQJUfwzqXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGNTg2N0ZDMzRDQTU4REQ5RTU2M0I2MUVB NTA2MzVCQ0JGMDI1NzZDAAoJEKUGNby/AldsXdwP/RE7TnIKGwemiepRVSMOg9mn NPaWvM9Lt/+Hdgncym2EH6Z4Rkzt2qPck2mTy5OC7TEl2KXXdMCds2RmIA50tL/q Wy+9dQHp3JDWpEqWBSlyhZc9Ule8OToqFcPLRxiWAiXkNdHzY+vU7C61lzD+IG9d Sze4lJi1rcV4Y7UpsnTnu+2yL51z0yxi9RF88zoA17CLfEdAIH3Ih5IY34q7pGip hNiLXIB4H0Mb1FtczhSrRij8sXKw1AWOQq/bAhb1StsiF8pd7AKuZ6tNc0wlqVbD ceP9dpstg2jdZQIoJlX8ECotp11pjqhsbyLQghtd7SF5mgSg+fWbuYjoxQ8M7su8 b1ohCHhsyp4GjF4X2fRZAOjOqSjaK7iaccabDQjZuGL1urTdDMm1WqtKZs0jltdR JDAfWLXGmQc6BItNwfajSt9Zy4dVeYi0AXAHd9RqCMzZ+vBV2dWzxPB8r9rztS4s 9eH5rgiXK+KFiIasFiI9jVl0EveSUBcgmpsBuZWRHP0g/nF7hf5IGL/Yymm89SCa XjYXypqC5CtnlNas/7J2Fm9Wt+e8z9RCAyLO0B6MVsrdKno8l7MK5hviggKpUODV gBrXzbyTxsjNJjHHutCraQhQcVYsn1H2pZVD97CeYWeYU9HbI5E55Q1NIREv1w+j Ori5VUvv2N3M70/dx+f8 =CrU9 -END PGP SIGNATURE- Tom Guder kont...@ib-guder.de hat am 26. November 2014 um 10:20 geschrieben: Package: blender Version: 2.72.b+dfsg0-1 Severity: normal Dear Maintainer, blender crashes with this message when rendering: Fra:9 Mem:18.23M (0.00M, Peak 35.96M) | Remaining:00:00.11 | Mem:3.25M, Peak:3.33M | Scene, RenderLayer
Bug#771042: Info received (Bug#771042: Acknowledgement (blender: Blender crashes while rendering with cycles))
Hello - Does this issue happen with default cube scene? If not, it really worth preparing .blend file which gives issues for sure. see last post. - Is it CPU or GPU rendering? CPU - Is OSL involved into the test file? - How much threads you're using for rendering? 12 - Is it crash when rendering animation or rendering still image also gives issues? Rendering animation gives issues more reliable. Rendering a singe frame also gives crashes randomly. - Does the crash happens when you render from command line: `blender -b /path/to/file.blend -f 1` Yes, after a few tries: Fra:1 Mem:6.76M (0.00M, Peak 8.17M) | Remaining:00:00.00 | Mem:0.38M, Peak:0.39M | Scene, RenderLayer | Path Tracing Tile 84/84 Fra:1 Mem:6.76M (0.00M, Peak 8.17M) | Mem:0.28M, Peak:0.39M | Scene, RenderLayer | Finished blender: /build/blender-mPVjzj/blender-2.72.b+dfsg0/intern/cycles/device/../util/util_stats.h:33: void ccl::Stats::mem_free(size_t): Assertion `mem_used = size' failed. Abgebrochen Bests Tom -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771042: blender: Blender crashes while rendering with cycles
Package: blender Version: 2.72.b+dfsg0-1 Severity: normal Dear Maintainer, blender crashes with this message when rendering: Fra:9 Mem:18.23M (0.00M, Peak 35.96M) | Remaining:00:00.11 | Mem:3.25M, Peak:3.33M | Scene, RenderLayer | Path Tracing Tile 134/135 Fra:9 Mem:18.23M (0.00M, Peak 35.96M) | Remaining:00:00.09 | Mem:3.18M, Peak:3.33M | Scene, RenderLayer | Path Tracing Tile 135/135 Fra:9 Mem:18.23M (0.00M, Peak 35.96M) | Mem:1.93M, Peak:3.33M | Scene, RenderLayer | Finished blender: /build/blender- mPVjzj/blender-2.72.b+dfsg0/intern/cycles/device/../util/util_stats.h:33: void ccl::Stats::mem_free(size_t): Assertion `mem_used = size' failed. Aborted It appears randomly with any model i like to render. Best regards Tom Guder -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/12 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages blender depends on: ii blender-data 2.72.b+dfsg0-1 ii fonts-droid 1:4.4.4r2-4 ii libavcodec56 6:11-2 ii libavdevice55 6:11-2 ii libavformat56 6:11-2 ii libavutil54 6:11-2 ii libboost-date-time1.55.0 1.55.0+dfsg-3 ii libboost-filesystem1.55.0 1.55.0+dfsg-3 ii libboost-locale1.55.0 1.55.0+dfsg-3 ii libboost-regex1.55.0 1.55.0+dfsg-3 ii libboost-system1.55.0 1.55.0+dfsg-3 ii libboost-thread1.55.0 1.55.0+dfsg-3 ii libc6 2.19-13 ii libfftw3-double3 3.3.4-1.1 ii libfreetype6 2.5.2-2 ii libgcc1 1:4.9.1-19 ii libgl1-mesa-glx [libgl1] 10.3.2-1 ii libglew1.10 1.10.0-3 ii libglu1-mesa [libglu1]9.0.0-2 ii libgomp1 4.9.1-19 ii libilmbase6 1.0.1-6.1 ii libjack-jackd2-0 [libjack-0.116] 1.9.10+20140719git3eb0ae6a~dfsg-2 ii libjpeg62-turbo 1:1.3.1-10 ii libjs-jquery 1.7.2+dfsg-3.2 ii libjs-jquery-ui 1.10.1+dfsg-1 ii libopenal11:1.15.1-5 ii libopencolorio1 1.0.9~dfsg0-3 ii libopenexr6 1.6.1-8 ii libopenimageio1.4 1.4.14~dfsg0-1 ii libopenjpeg5 1:1.5.2-3 ii libpng12-01.2.50-2+b1 ii libpython3.4 3.4.2-1 ii libsdl1.2debian 1.2.15-10 ii libsndfile1 1.0.25-9+b1 ii libspnav0 0.2.2-1 ii libstdc++64.9.1-19 ii libswscale3 6:11-2 ii libtiff5 4.0.3-10+b3 ii libx11-6 2:1.6.2-3 ii libxi62:1.7.4-1+b1 ii libxxf86vm1 1:1.1.3-1+b1 ii zlib1g1:1.2.8.dfsg-2 blender recommends no packages. blender suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771045: linux-image-3.16.0-4-amd64: System randomly freezes using Kernel 3.16 and radeon
Package: src:linux Version: 3.16.7-2 Severity: important Dear Maintainer, with all my computers with radeon cards the system freezes randomy. I can't reproduce freezing. It happens more often with kernel 3.16 and less often with 3.14. Some others report this issue too: http://lists.freedesktop.org/archives/dri-devel/2014-July/065061.html https://bugzilla.kernel.org/show_bug.cgi?id=85421 Sometimes the system responds via ssh, sometimes everything is locked. Best regards Tom -- Package-specific info: ** Version: Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.3 (Debian 4.8.3-13) ) #1 SMP Debian 3.16.7-2 (2014-11-06) ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 root=UUID=8b037d1e-7609-4503-bea5-d0d4f2a4107f ro quiet ** Not tainted ** Kernel log: [7.365395] radeon :03:00.0: firmware: direct-loading firmware radeon/PITCAIRN_me.bin [7.431087] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro [7.434492] systemd-journald[234]: Received request to flush runtime journal from PID 1 [7.464108] radeon :03:00.0: firmware: direct-loading firmware radeon/PITCAIRN_ce.bin [7.545250] radeon :03:00.0: firmware: direct-loading firmware radeon/PITCAIRN_rlc.bin [7.572113] radeon :03:00.0: firmware: direct-loading firmware radeon/PITCAIRN_mc2.bin [7.572122] [drm] radeon/PITCAIRN_mc2.bin: 31100 bytes [7.599761] radeon :03:00.0: firmware: direct-loading firmware radeon/PITCAIRN_smc.bin [7.599772] [drm] Internal thermal controller with fan control [7.599878] [drm] probing gen 2 caps for device 8086:e04 = 7a7903/e [7.611793] [drm] radeon: dpm initialized [7.635468] radeon :03:00.0: firmware: direct-loading firmware radeon/TAHITI_uvd.bin [7.635520] [drm] GART: num cpu pages 262144, num gpu pages 262144 [7.636660] [drm] probing gen 2 caps for device 8086:e04 = 7a7903/e [7.636664] [drm] PCIE gen 3 link speeds already enabled [7.654264] [drm] PCIE GART of 1024M enabled (table at 0x00276000). [7.654411] radeon :03:00.0: WB enabled [7.654415] radeon :03:00.0: fence driver on ring 0 use gpu addr 0x8c00 and cpu addr 0x88085b634c00 [7.654417] radeon :03:00.0: fence driver on ring 1 use gpu addr 0x8c04 and cpu addr 0x88085b634c04 [7.654420] radeon :03:00.0: fence driver on ring 2 use gpu addr 0x8c08 and cpu addr 0x88085b634c08 [7.654422] radeon :03:00.0: fence driver on ring 3 use gpu addr 0x8c0c and cpu addr 0x88085b634c0c [7.654424] radeon :03:00.0: fence driver on ring 4 use gpu addr 0x8c10 and cpu addr 0x88085b634c10 [7.655034] radeon :03:00.0: fence driver on ring 5 use gpu addr 0x00075a18 and cpu addr 0xc90015bb5a18 [7.655036] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [7.655037] [drm] Driver supports precise vblank timestamp query. [7.655065] radeon :03:00.0: irq 120 for MSI/MSI-X [7.655077] radeon :03:00.0: radeon: using MSI. [7.655140] [drm] radeon: irq initialized. [7.819842] [drm] ring test on 0 succeeded in 4 usecs [7.819847] [drm] ring test on 1 succeeded in 1 usecs [7.819851] [drm] ring test on 2 succeeded in 1 usecs [7.819863] [drm] ring test on 3 succeeded in 2 usecs [7.819873] [drm] ring test on 4 succeeded in 1 usecs [8.005659] [drm] ring test on 5 succeeded in 2 usecs [8.005666] [drm] UVD initialized successfully. [8.005909] [drm] ib test on ring 0 succeeded in 0 usecs [8.005959] [drm] ib test on ring 1 succeeded in 0 usecs [8.006007] [drm] ib test on ring 2 succeeded in 0 usecs [8.006048] [drm] ib test on ring 3 succeeded in 0 usecs [8.006088] [drm] ib test on ring 4 succeeded in 1 usecs [8.157226] [drm] ib test on ring 5 succeeded [8.157709] [drm] Radeon Display Connectors [8.157711] [drm] Connector 0: [8.157712] [drm] DP-1 [8.157712] [drm] HPD4 [8.157714] [drm] DDC: 0x6530 0x6530 0x6534 0x6534 0x6538 0x6538 0x653c 0x653c [8.157715] [drm] Encoders: [8.157716] [drm] DFP1: INTERNAL_UNIPHY2 [8.157716] [drm] Connector 1: [8.157717] [drm] HDMI-A-1 [8.157718] [drm] HPD5 [8.157719] [drm] DDC: 0x6540 0x6540 0x6544 0x6544 0x6548 0x6548 0x654c 0x654c [8.157720] [drm] Encoders: [8.157721] [drm] DFP2: INTERNAL_UNIPHY2 [8.157722] [drm] Connector 2: [8.157722] [drm] DVI-I-1 [8.157723] [drm] HPD1 [8.157724] [drm] DDC: 0x6550 0x6550 0x6554 0x6554 0x6558 0x6558 0x655c 0x655c [8.157725] [drm] Encoders: [8.157726] [drm] DFP3: INTERNAL_UNIPHY1 [8.157727] [drm] Connector 3: [8.157727] [drm] DVI-I-2 [8.157728] [drm] HPD6 [8.157729] [drm] DDC: 0x6580 0x6580 0x6584 0x6584 0x6588 0x6588 0x658c 0x658c [8.157730] [drm] Encoders: [8.157731] [drm] DFP4: INTERNAL_UNIPHY [8.157732] [drm]
Bug#770677: blender: Blender crashes while rendering with cycles.
Package: blender Version: 2.72.b+dfsg0-1 Severity: important Dear Maintainer, blender crashes while rendering with cycles (with gui and in a shell also). I tested it on all my systems, so I think it is a problem in general. The originalpackage from blender.org works. Thank you and best regards Tom Guder -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.14-2-amd64 (SMP w/12 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages blender depends on: ii blender-data 2.72.b+dfsg0-1 ii fonts-droid 1:4.4.4r2-4 ii libavcodec56 10:2.4.3-dmo1 ii libavdevice55 6:11-2 ii libavformat56 10:2.4.3-dmo1 ii libavutil54 10:2.4.3-dmo1 ii libboost-date-time1.55.0 1.55.0+dfsg-3 ii libboost-filesystem1.55.0 1.55.0+dfsg-3 ii libboost-locale1.55.0 1.55.0+dfsg-3 ii libboost-regex1.55.0 1.55.0+dfsg-3 ii libboost-system1.55.0 1.55.0+dfsg-3 ii libboost-thread1.55.0 1.55.0+dfsg-3 ii libc6 2.19-13 ii libfftw3-double3 3.3.4-1.1 ii libfreetype6 2.5.2-2 ii libgcc1 1:4.9.1-19 ii libgl1-mesa-glx [libgl1] 10.3.2-1 ii libglew1.10 1.10.0-3 ii libglu1-mesa [libglu1]9.0.0-2 ii libgomp1 4.9.1-19 ii libilmbase6 1.0.1-6.1 ii libjack-jackd2-0 [libjack-0.116] 1.9.10+20140719git3eb0ae6a~dfsg-2 ii libjpeg62-turbo 1:1.3.1-10 ii libjs-jquery 1.7.2+dfsg-3.2 ii libjs-jquery-ui 1.10.1+dfsg-1 ii libopenal11:1.15.1-5 ii libopencolorio1 1.0.9~dfsg0-3 ii libopenexr6 1.6.1-8 ii libopenimageio1.4 1.4.14~dfsg0-1 ii libopenjpeg5 1:1.5.2-3 ii libpng12-01.2.50-2+b1 ii libpython3.4 3.4.2-1 ii libsdl1.2debian 1.2.15-10 ii libsndfile1 1.0.25-9+b1 ii libspnav0 0.2.2-1 ii libstdc++64.9.1-19 ii libswscale3 10:2.4.3-dmo1 ii libtiff5 4.0.3-10+b3 ii libx11-6 2:1.6.2-3 ii libxi62:1.7.4-1+b1 ii libxxf86vm1 1:1.1.3-1+b1 ii zlib1g1:1.2.8.dfsg-2 blender recommends no packages. blender suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
