Welcome, Guest. Please login or register.
Did you miss your activation email?

Author Topic:  Freeze mit Kernel 3.19.3-towo.1  (Read 2156 times)

Offline bluelupo

  • User
  • Posts: 2.068
    • BluelupoMe
Freeze mit Kernel 3.19.3-towo.1
« on: 2015/04/06, 17:48:12 »
Hallo Community,

ich habe mit dem neuesten Kernel 3.19.3-towo.1 ein reprozierbaren Freeze, der sich beim Abmelden (oder Shutdown oder Wechsel auf die Textkonsole) aus dem KDE bemerkbar macht.

journalctl meldet folgendes:
Code: [Select]
Apr 05 22:26:01 shira kernel: ^[[1;39m------------[ cut here ]------------
Apr 05 22:26:01 shira kernel: kernel BUG at /tmp/buildd/linux-siduction-3.19/drivers/gpu/drm/drm_crtc.c:536!
Apr 05 22:26:02 shira kernel: ^[[1;39minvalid opcode: 0000 [#1] PREEMPT SMP
Apr 05 22:26:02 shira kernel: ^[[1;39mModules linked in: dm_snapshot dm_bufio bnep bluetooth af_packet cpufreq_powersave cpufreq_stats cpufreq_conse$
Apr 05 22:26:02 shira kernel: ^[[1;39m crc16 jbd2 mbcache crc32c_generic btrfs xor raid6_pq dm_mod sg sr_mod cdrom sd_mod hid_logitech ff_memless us$
Apr 05 22:26:02 shira kernel: ^[[1;39mCPU: 1 PID: 1003 Comm: Xorg Not tainted 3.19.3-towo.1-siduction-amd64 #1 siduction 3.19-9
Apr 05 22:26:02 shira kernel: ^[[1;39mHardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./i45GMt-HD R1.07 Jul.07.2009, BIOS 080015  07/07/2$
Apr 05 22:26:02 shira kernel: ^[[1;39mtask: ffff8800a7a4db40 ti: ffff8800a7a60000 task.ti: ffff8800a7a60000
Apr 05 22:26:02 shira kernel: ^[[1;39mRIP: 0010:[<ffffffffa04de760>]  [<ffffffffa04de760>] drm_framebuffer_free_bug+0x0/0x10 [drm]
Apr 05 22:26:02 shira kernel: ^[[1;39mRSP: 0018:ffff8800a7a63a40  EFLAGS: 00010246
Apr 05 22:26:02 shira kernel: ^[[1;39mRAX: 0000000000000000 RBX: ffff880139893400 RCX: 0000000000000001
Apr 05 22:26:02 shira kernel: ^[[1;39mRDX: 0000000000000040 RSI: 0000000000000000 RDI: ffff8800a8cede48
Apr 05 22:26:02 shira kernel: ^[[1;39mRBP: ffff8800a8cede40 R08: ffff8800a04d7970 R09: 0000000000000000
Apr 05 22:26:02 shira kernel: ^[[1;39mR10: 00007ffc8c8862e0 R11: 0000000000000000 R12: ffff88013a02f000
Apr 05 22:26:02 shira kernel: ^[[1;39mR13: ffff8800b19bf378 R14: ffff8800a7a63b80 R15: 0000000000000080
Apr 05 22:26:02 shira kernel: ^[[1;39mFS:  00007fc69ada1980(0000) GS:ffff88013fc80000(0000) knlGS:0000000000000000
Apr 05 22:26:02 shira kernel: ^[[1;39mCS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Apr 05 22:26:02 shira kernel: ^[[1;39mCR2: 00007f1a1b1b7358 CR3: 00000000a7926000 CR4: 00000000000007e0
Apr 05 22:26:02 shira kernel: ^[[1;39mStack:
Apr 05 22:26:02 shira kernel: ^[[1;39m ffffffffa04e0545 ffff880139893800 ffff880139893400 ffff8800b19bf000
Apr 05 22:26:02 shira kernel: ^[[1;39m ffffffffa00f7571 ffff88013a02f000 ffff8800b19bf000 0000000000200001
Apr 05 22:26:02 shira kernel: ^[[1;39m ffff88013a658860 ffff8800a7a63b80 ffffffffa00f94bb ffff88013a02f000
Apr 05 22:26:02 shira kernel: ^[[1;39mCall Trace:
Apr 05 22:26:02 shira kernel: ^[[1;39m [<ffffffffa04e0545>] ? drm_plane_force_disable+0x95/0xc0 [drm]
Apr 05 22:26:02 shira kernel: ^[[1;39m [<ffffffffa00f7571>] ? restore_fbdev_mode+0x41/0xe0 [drm_kms_helper]
Apr 05 22:26:02 shira kernel: ^[[1;39m [<ffffffffa00f94bb>] ? drm_fb_helper_restore_fbdev_mode_unlocked+0x1b/0x60 [drm_kms_helper]
Apr 05 22:26:02 shira kernel: ^[[1;39m [<ffffffffa00f951d>] ? drm_fb_helper_set_par+0x1d/0x40 [drm_kms_helper]
Apr 05 22:26:02 shira kernel: ^[[1;39m [<ffffffffa0582261>] ? intel_fbdev_set_par+0x11/0x60 [i915]
Apr 05 22:26:02 shira kernel: ^[[1;39m [<ffffffff812d7e6f>] ? fb_set_var+0x16f/0x3e0
Apr 05 22:26:02 shira kernel: ^[[1;39m [<ffffffff8107c8d7>] ? preempt_count_add+0x47/0xa0
Apr 05 22:26:02 shira kernel: ^[[1;39m [<ffffffffa0390ff1>] ? jbd2_journal_put_journal_head+0x41/0x208 [jbd2]
Apr 05 22:26:02 shira kernel: ^[[1;39m [<ffffffff8107c879>] ? get_parent_ip+0x9/0x20
Apr 05 22:26:02 shira kernel: ^[[1;39m [<ffffffff8107c8d7>] ? preempt_count_add+0x47/0xa0
Apr 05 22:26:02 shira kernel: ^[[1;39m [<ffffffffa0390ff1>] ? jbd2_journal_put_journal_head+0x41/0x208 [jbd2]
Apr 05 22:26:02 shira kernel: ^[[1;39m [<ffffffffa03892d3>] ? jbd2_journal_dirty_metadata+0xf3/0x2f0 [jbd2]
Apr 05 22:26:02 shira kernel: ^[[1;39m [<ffffffffa0388cbd>] ? do_get_write_access+0x43d/0x5a0 [jbd2]
Apr 05 22:26:02 shira kernel: ^[[1;39m [<ffffffff812ceeb3>] ? fbcon_blank+0x243/0x300
Apr 05 22:26:02 shira kernel: ^[[1;39m [<ffffffff81333a92>] ? do_unblank_screen+0xa2/0x1c0
Apr 05 22:26:02 shira kernel: ^[[1;39m [<ffffffff8132a4d8>] ? vt_ioctl+0x6c8/0x1380
Apr 05 22:26:02 shira kernel: ^[[1;39m [<ffffffffa03881c7>] ? jbd2_journal_stop+0x167/0x2e0 [jbd2]
Apr 05 22:26:02 shira kernel: ^[[1;39m [<ffffffff8131db7e>] ? tty_ioctl+0x3ee/0xc70
Apr 05 22:26:02 shira kernel: ^[[1;39m [<ffffffff8118ce71>] ? do_unlinkat+0xe1/0x2e0
Apr 05 22:26:02 shira kernel: ^[[1;39m [<ffffffff8107c879>] ? get_parent_ip+0x9/0x20
Apr 05 22:26:02 shira kernel: ^[[1;39m [<ffffffff81363149>] ? vga_arb_release+0xe9/0x100
Apr 05 22:26:02 shira kernel: ^[[1;39m [<ffffffff8107c879>] ? get_parent_ip+0x9/0x20
Apr 05 22:26:02 shira kernel: ^[[1;39m [<ffffffff81193db0>] ? dput+0x20/0x1d0
Apr 05 22:26:02 shira kernel: ^[[1;39m [<ffffffff8118fe68>] ? do_vfs_ioctl+0x308/0x510
Apr 05 22:26:02 shira kernel: ^[[1;39m [<ffffffff8119c3c9>] ? mntput_no_expire+0x9/0x140
Apr 05 22:26:02 shira kernel: ^[[1;39m [<ffffffff8107237c>] ? task_work_run+0xbc/0xf0
Apr 05 22:26:02 shira kernel: ^[[1;39m [<ffffffff811900e9>] ? SyS_ioctl+0x79/0x90
Apr 05 22:26:02 shira kernel: ^[[1;39m [<ffffffff814f2cef>] ? int_signal+0x12/0x17
Apr 05 22:26:02 shira kernel: ^[[1;39m [<ffffffff814f2a4d>] ? system_call_fastpath+0x16/0x1b
Apr 05 22:26:02 shira kernel: ^[[1;39mCode: e8 c6 1e 01 e1 8b 75 10 48 8d bb c0 02 00 00 e8 77 20 d9 e0 4c 89 e7 e8 0f 1d 01 e1 5b 48 89 ef 5d 41 5c$
Apr 05 22:26:02 shira kernel: RIP  [<ffffffffa04de760>] drm_framebuffer_free_bug+0x0/0x10 [drm]
Apr 05 22:26:02 shira kernel: ^[[1;39m RSP <ffff8800a7a63a40>
Apr 05 22:26:02 shira kernel: ^[[1;39m---[ end trace 3510ec3a3b7a9800 ]---

Das dürfte vermutlich der Auslöser sein:
Code: [Select]
kernel BUG at /tmp/buildd/linux-siduction-3.19/drivers/gpu/drm/drm_crtc.c:536!

Mit einem älteren Kernel zB. 3.18.6-towo oder 3.19.1-towo.3 konnte ich den Freeze nicht provozieren.

Mein System:
Code: [Select]
# inxi -v7
System:    Host: shira Kernel: 3.19.1-towo.3-siduction-amd64 x86_64 (64 bit gcc: 4.9.2)
           Console: tty 0 dm: lightdm Distro: siduction 14.1.0 Indian Summer - kde - (201411230337)
Machine:   Mobo: AOpen model: i45GMt-HD R1.07 Jul.07.2009 v: 918ET10I520 serial: 93600029JEB3
           Bios: American Megatrends v: 080015 date: 07/07/2009
CPU:       Dual core Intel Core2 Duo P9500 (-MCP-) cache: 6144 KB
           flags: (lm nx sse sse2 sse3 sse4_1 ssse3 vmx) bmips: 10115
           clock speeds: min/max: 800/2534 MHz 1: 1600 MHz 2: 800 MHz
Memory:    Array-1 capacity: 8 GB devices: 4 EC: None max module size: 4 GB
           Device-1: DIMM0 size: 2 GB (Double-bank) speed: N/A type: DDR2 (Synchronous)
           bus width: 64 bits manufacturer: N/A part: N/A serial: N/A
           Device-2: DIMM1 size: No Module Installed type: N/A bus width: 64 bits
           Device-3: DIMM2 size: 2 GB (Double-bank) speed: N/A type: DDR2 (Synchronous)
           bus width: 64 bits manufacturer: N/A part: N/A serial: N/A
           Device-4: DIMM3 size: No Module Installed type: N/A bus width: 64 bits
Graphics:  Card: Intel Mobile 4 Series Integrated Graphics Controller bus-ID: 00:02.0 chip-ID: 8086:2a42
           Display Server: X.org 1.16.4 drivers: intel (unloaded: fbdev,vesa)
           tty size: 149x55 Advanced Data: N/A for root out of X
Audio:     Card-1 Intel 82801I (ICH9 Family) HD Audio Controller
           driver: snd_hda_intel bus-ID: 00:1b.0 chip-ID: 8086:293e
           Card-2 Microsoft LifeCam Cinema driver: USB Audio usb-ID: 001-002 chip-ID: 045e:075d
           Sound: Advanced Linux Sound Architecture v: k3.19.1-towo.3-siduction-amd64
Network:   Card-1: Intel 82567LF Gigabit Network Connection
           driver: e1000e v: 2.3.2-k port: d080 bus-ID: 00:19.0 chip-ID: 8086:10bf
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: 00:01:80:78:82:35
           Card-2: Intel WiFi Link 5100 driver: iwlwifi v: in-tree: bus-ID: 02:00.0 chip-ID: 8086:4232
           IF: wlan0 state: down mac: 00:1e:65:d9:27:7e
           WAN IP: 87.142.29.222 IF: eth0 ip: 192.168.178.15 ip-v6: fe80::201:80ff:fe78:8235
           IF: wlan0 ip: N/A ip-v6: N/A
Drives:    HDD Total Size: 930.2GB (39.6% used)
           ID-1: /dev/sda model: INTEL_SSDSC2BW18 size: 180.0GB serial: BTDA328306M51802GN temp: 0C
           ID-2: /dev/sdb model: WDC_WD7500BPVT size: 750.2GB serial: WD-WXM1EA0JCN34 temp: 33C
           Optical: /dev/sr0 model: TSST CDDVDW SN-S083B rev: SB00 dev-links: cdrom,cdrw,dvd,dvdrw
           Features: speed: 24x multisession: yes
           audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r,dvd-ram state: running
Partition: ID-1: / size: 6.8G used: 4.7G (72%) fs: ext4 dev: /dev/dm-0
           label: ROOT uuid: 907e7ea9-3f82-4fb6-8300-f89bafc0d6ee
           ID-2: /mnt/import/backup size: 443G used: 321G (73%) fs: ext4 dev: /dev/dm-1
           label: BACKUP uuid: cd7f6327-0d9b-48d8-9226-f1e7acc2297e
           ID-3: /mnt/share/userdata size: 9.8G used: 8.0G (82%) fs: ext4 dev: /dev/dm-6
           label: USERDATA uuid: af7e1346-dadb-416c-b138-ad0a13d99962
           ID-4: /mnt/share/dataexchange size: 4.8G used: 11M (1%) fs: ext4 dev: /dev/dm-2
           label: DATAEX uuid: ff528ce8-14d1-48ae-b972-5c691dde828e
           ID-5: /home size: 5.3G used: 2.7G (53%) fs: ext4 dev: /dev/dm-4
           label: HOME uuid: 05812272-79b3-4e84-a052-55a818dce47e
           ID-6: /var size: 4.4G used: 2.2G (53%) fs: ext4 dev: /dev/dm-3
           label: VAR uuid: b6a5d8f2-8e8c-4fed-84dc-7120c8f0a784
           ID-7: /mnt/share/photo size: 15G used: 3.7G (25%) fs: ext4 dev: /dev/dm-7
           label: PHOTO uuid: cfecffc1-0202-4feb-a2da-7b731db4874f
           ID-8: swap-1 size: 2.15GB used: 0.00GB (0%) fs: swap dev: /dev/dm-5
           label: N/A uuid: 8f532b44-feba-4337-9f44-2f8ecbe0a2c9
RAID:      No RAID data: /proc/mdstat missing-is md_mod kernel module loaded?
Unmounted: ID-1: /dev/sda1 size: 180.04G label: N/A uuid: N/A
           ID-2: /dev/sdb1 size: 750.16G label: N/A uuid: N/A
Sensors:   System Temperatures: cpu: 30.0C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 157 Uptime: 8:50 Memory: 297.9/3829.6MB Init: systemd v: 215 runlevel: 5 Gcc sys: 4.9.2
           Client: Shell (bash 4.3.331 running in tty 0) inxi: 2.2.18

Offline towo

  • Administrator
  • User
  • *****
  • Posts: 2.939
Re: Freeze mit Kernel 3.19.3-towo.1
« Reply #1 on: 2015/04/07, 10:53:00 »
Please try the new kernel, i have added the suggested patch from the bugreport of this upstream issue.
Ich gehe nicht zum Karneval, ich verleihe nur manchmal mein Gesicht.

Offline bluelupo

  • User
  • Posts: 2.068
    • BluelupoMe
Re: Freeze mit Kernel 3.19.3-towo.1
« Reply #2 on: 2015/04/12, 11:36:32 »
With kernel 3.19.3-towo.3-siduction-amd64 have occurred no more crashes so far, I've been watching this has yet awhile.