[opensuse] 13.1 zypper crash - kernel general protection fault (hadn't seen this before)
All, Earlier this evening I went to do a `zypper in` and the system slowly melted down. Checking the log it was do to a general protection fault in some 'd_materialise_unique' function?? I don't know if this was just a spurious failure or whether it needs more looking into. The box must have booted into the 3.15 kernel on startup if that is relevant. The crash and the register values are included below. If anybody has any ideas, let me know, otherwise, I'll chock it up to gremlins until the next one occurs: 2015-10-11T23:30:11.542472-05:00 alchemy sudo: david : TTY=pts/9 ; PWD=/home/david/dev/src-c/io/database/db ; USER=root ; COMMAND=/usr/bin/zypper -v in -r kde3 db-utils db-utils-doc 2015-10-11T23:30:11.546723-05:00 alchemy sudo: pam_unix(sudo:session): session opened for user root by (uid=0) 2015-10-11T23:30:12.972543-05:00 alchemy kernel: [326900.233400] general protection fault: 0000 [#1] PREEMPT SMP 2015-10-11T23:30:12.972568-05:00 alchemy kernel: [326900.233510] Modules linked in: fuse ctr ccm xt_pkttype xt_LOG xt_limit bnep bluetooth 6lowpan_iphc af_packet ip6t_REJECT xt_tcpudp nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_raw ipt_REJECT iptable_raw xt_CT iptable_filter ip6table_mangle nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_ipv4 nf_defrag_ipv4 ip_tables xt_conntrack nf_conntrack ip6table_filter ip6_tables x_tables arc4 snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel snd_hda_controller snd_hda_codec firewire_ohci powernow_k8 snd_hwdep ath5k ath snd_pcm sp5100_tco snd_seq kvm_amd sr_mod kvm cdrom pcmcia mac80211 snd_timer snd_seq_device snd sdhci_pci firewire_core k8temp sdhci r8169 pcspkr joydev serio_raw edac_core soundcore edac_mce_amd ata_generic yenta_socket pcmcia_rsrc pcmcia_core mmc_core tifm_7xx1 tifm_core cfg80211 i2c_piix4 crc_itu_t pata_atiixp toshiba_acpi mii sparse_keymap rfkill battery video button shpchp wmi toshiba_bluetooth ac sg dm_mod ohci_pci radeon ttm drm_kms_helper drm i2c_algo_bit processor scsi_dh_alua scsi_dh_rdac scsi_dh_hp_sw scsi_dh_emc scsi_dh 2015-10-11T23:30:12.972744-05:00 alchemy kernel: [326900.234008] CPU: 1 PID: 29594 Comm: zypper Not tainted 3.15.6-2.gedc5ddf-desktop #1 2015-10-11T23:30:12.972748-05:00 alchemy kernel: [326900.234008] Hardware name: TOSHIBA Satellite P205D/JASAA, BIOS V1.70 01/15/2010 2015-10-11T23:30:12.972750-05:00 alchemy kernel: [326900.234008] task: ffff88004bc36110 ti: ffff880050c6c000 task.ti: ffff880050c6c000 2015-10-11T23:30:12.972753-05:00 alchemy kernel: [326900.234008] RIP: 0010:[<ffffffff811c4fc4>] [<ffffffff811c4fc4>] d_materialise_unique+0x354/0x3e0 2015-10-11T23:30:12.972755-05:00 alchemy kernel: [326900.234008] RSP: 0018:ffff880050c6fc78 EFLAGS: 00010202 2015-10-11T23:30:12.972757-05:00 alchemy kernel: [326900.234008] RAX: fdff8800d211ae58 RBX: ffff880047457008 RCX: ffff8800d3bd4798 2015-10-11T23:30:12.972870-05:00 alchemy kernel: [326900.234008] RDX: 0000000000000000 RSI: ffff880047457120 RDI: ffff8800d0bddb10 2015-10-11T23:30:12.972886-05:00 alchemy kernel: [326900.234008] RBP: fdff8800d211ae58 R08: e798d28deb2d50de R09: 0000000000000000 2015-10-11T23:30:12.972888-05:00 alchemy kernel: [326900.234008] R10: fefefefefefefeff R11: 2f2f2f2f2f2f2f2f R12: ffff8800c6e0f9d8 2015-10-11T23:30:12.972891-05:00 alchemy kernel: [326900.234008] R13: ffff880047457090 R14: ffff8800d0bddb10 R15: ffff8800474553d8 2015-10-11T23:30:12.972893-05:00 alchemy kernel: [326900.234008] FS: 00007f5c78ae3840(0000) GS:ffff88011fd00000(0000) knlGS:0000000000000000 2015-10-11T23:30:12.972895-05:00 alchemy kernel: [326900.234008] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 2015-10-11T23:30:12.972898-05:00 alchemy kernel: [326900.234008] CR2: 00000000013fa000 CR3: 00000000d10af000 CR4: 00000000000007e0 gremlins... -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
David C. Rankin composed on 2015-10-12 02:10 (UTC-0500):
...The box must have booted into the 3.15 kernel on startup if that is relevant...
Where did it get a 3.15 kernel from, and why? 13.1 got released with 3.11, while most of mine are using Kubeèek's 3.12, which is on track to become 13.1's evergreen kernel. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/12/2015 02:36 AM, Felix Miata wrote:
Where did it get a 3.15 kernel from, and why? 13.1 got released with 3.11, while most of mine are using Kubeèek's 3.12, which is on track to become 13.1's evergreen kernel.
That was from the kotd when we were troubleshooting the broken backlight control levels (no function key control of screen brightness). During the bug troubleshooting we loaded the kotd which at that time was 3.15. It runs fine, but didn't fix the problem. Next tried kotd 3.16 which wouldn't even display graphics anymore as the tweaks to X in the 10 days between me getting 3.15 and the release of 3.16 had totally broken X for my laptop. I generally run the 3.11 kernel from update. I must have been busy when I booted the box and the default (3.15) was booted... Never had any issues with that plain-vanilla kernel either. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (2)
-
David C. Rankin
-
Felix Miata