[Bug 1296660] Re: Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA (unable to handle kernel NULL pointer dereference / con_set_unimap+0x32
Have rebooted 40 times without this issue with 3.13.0-44 (linux- headers-3.13.0-44-generic, linux-image-3.13.0-44-generic and linux- image-extra-3.13.0-44-generic). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296660 Title: Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA (unable to handle kernel NULL pointer dereference / con_set_unimap+0x32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1296660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296660] Re: Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA (unable to handle kernel NULL pointer dereference / con_set_unimap+0x32
Actually, the patch posted above appears to be included in 3.13.0-44.73, which is currently in proposed (also see: #1402853). I suppose that warrants a 'Fix Released' status, though I'll leave that to the Ubuntu kernel team. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296660 Title: Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA (unable to handle kernel NULL pointer dereference / con_set_unimap+0x32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1296660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296660] Re: Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA (unable to handle kernel NULL pointer dereference / con_set_unimap+0x32
Still in 3.13.0-43-generic. Furthermore, I have a strong suspicion this was fixed upstream in v3.18, even though Wolfgang reported v3.14 worked fine for him. https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=9e326f78713a4421fe11afc2ddeac07698fac131 Can anyone test and confirm this solves the issue? I'm affected, though testing is tricky without console access. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296660 Title: Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA (unable to handle kernel NULL pointer dereference / con_set_unimap+0x32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1296660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296660] Re: Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA (unable to handle kernel NULL pointer dereference / con_set_unimap+0x32
reproducible with 3.13.0-40-generic Ubuntu 3.13.0-40.69~precise1-generic 3.13.11.10 Dec 5 16:49:56 ubuntu kernel: [ 21.340139] [drm] AST 2300 detected Dec 5 16:49:56 ubuntu kernel: [ 21.340183] [drm] dram 163200 1 16 0080 Dec 5 16:49:56 ubuntu kernel: [ 21.340211] [TTM] Zone kernel: Available graphics memory: 65964816 kiB Dec 5 16:49:56 ubuntu kernel: [ 21.340211] [TTM] Zone dma32: Available graphics memory: 2097152 kiB Dec 5 16:49:56 ubuntu kernel: [ 21.340212] [TTM] Initializing pool allocator Dec 5 16:49:56 ubuntu kernel: [ 21.340214] [TTM] Initializing DMA pool allocator Dec 5 16:49:56 ubuntu kernel: [ 21.354338] checking generic (c700 13) vs hw (c700 80) Dec 5 16:49:56 ubuntu kernel: [ 21.354339] fb: conflicting fb hw usage astdrmfb vs VESA VGA - removing generic driver Dec 5 16:49:56 ubuntu kernel: [ 21.394467] Console: switching to colour dummy device 80x25 Dec 5 16:49:56 ubuntu kernel: [ 21.394513] BUG: unable to handle kernel NULL pointer dereference at 0138 Dec 5 16:49:56 ubuntu kernel: [ 21.394517] IP: [] con_set_unimap+0x34/0x2a0 Dec 5 16:49:56 ubuntu kernel: [ 21.394518] PGD 10267e2067 PUD 1025232067 PMD 0 Dec 5 16:49:56 ubuntu kernel: [ 21.394519] Oops: [#1] SMP Dec 5 16:49:56 ubuntu kernel: [ 21.394527] Modules linked in: ast(+) ttm drm_kms_helper drm gpio_ich sysimgblt sysfillrect syscopyarea shpchp lpc_ich wmi joydev ipmi_si parport_pc ppdev mac_hid acpi_pad lp parport hid_generic usbhid hid mpt2sas igb dca ahci scsi_transport_sas i2c_algo_bit raid_class ptp libahci pps_core Dec 5 16:49:56 ubuntu kernel: [ 21.394528] CPU: 4 PID: 1649 Comm: setfont Not tainted 3.13.0-40-generic #69~precise1-Ubuntu Dec 5 16:49:56 ubuntu kernel: [ 21.394529] Hardware name: Quanta Computer Inc T41S-2U/S2S, BIOS S2S_3A14 09/19/2014 Dec 5 16:49:56 ubuntu kernel: [ 21.394529] task: 88202467c800 ti: 8820270da000 task.ti: 8820270da000 Dec 5 16:49:56 ubuntu kernel: [ 21.394531] RIP: 0010:[] [] con_set_unimap+0x34/0x2a0 Dec 5 16:49:56 ubuntu kernel: [ 21.394531] RSP: 0018:8820270dbd18 EFLAGS: 00010246 Dec 5 16:49:56 ubuntu kernel: [ 21.394532] RAX: 8820262a8308 RBX: 4b67 RCX: Dec 5 16:49:56 ubuntu kernel: [ 21.394532] RDX: 8820262a8000 RSI: 0296 RDI: Dec 5 16:49:56 ubuntu kernel: [ 21.394533] RBP: 8820270dbd98 R08: 8820270da000 R09: 0001 Dec 5 16:49:56 ubuntu kernel: [ 21.394533] R10: 0020 R11: R12: Dec 5 16:49:56 ubuntu kernel: [ 21.394533] R13: 021f9b10 R14: 0001 R15: Dec 5 16:49:56 ubuntu kernel: [ 21.394534] FS: 7f9209142700() GS:88103fc8() knlGS: Dec 5 16:49:56 ubuntu kernel: [ 21.394534] CS: 0010 DS: ES: CR0: 80050033 Dec 5 16:49:56 ubuntu kernel: [ 21.394535] CR2: 0138 CR3: 00101f23 CR4: 001407e0 Dec 5 16:49:56 ubuntu kernel: [ 21.394535] Stack: Dec 5 16:49:56 ubuntu kernel: [ 21.394537] 0286 8820270dbd58 8132657b Dec 5 16:49:56 ubuntu kernel: [ 21.394539] 88202467c800 fdfd 8820262a8000 0001 Dec 5 16:49:56 ubuntu kernel: [ 21.394540] 02e18820270dbd68 8820262a8000 8820270dbd88 4b67 Dec 5 16:49:56 ubuntu kernel: [ 21.394540] Call Trace: Dec 5 16:49:56 ubuntu kernel: [ 21.394545] [] ? apparmor_capable+0x2b/0x110 Dec 5 16:49:56 ubuntu kernel: [ 21.394547] [] vt_ioctl+0xfdd/0x11d0 Dec 5 16:49:56 ubuntu kernel: [ 21.394551] [] ? handle_mm_fault+0xb3/0x160 Dec 5 16:49:56 ubuntu kernel: [ 21.394554] [] tty_ioctl+0x298/0x8f0 Dec 5 16:49:56 ubuntu kernel: [ 21.394556] [] ? remove_vma+0x80/0xb0 Dec 5 16:49:56 ubuntu kernel: [ 21.394558] [] do_vfs_ioctl+0x75/0x2c0 Dec 5 16:49:56 ubuntu kernel: [ 21.394559] [] SyS_ioctl+0x91/0xb0 Dec 5 16:49:56 ubuntu kernel: [ 21.394560] [] ? vm_munmap+0x59/0x70 Dec 5 16:49:56 ubuntu kernel: [ 21.394563] [] system_call_fastpath+0x1a/0x1f -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296660 Title: Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA (unable to handle kernel NULL pointer dereference / con_set_unimap+0x32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1296660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296660] Re: Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA (unable to handle kernel NULL pointer dereference / con_set_unimap+0x32
and here how it looks like on normal boot: .. [drm] Initialized drm 1.1.0 20060810 Oct 29 09:09:30 spb-office kernel: [6.100409] mei_me :00:16.0: irq 45 for MSI/MSI-X Oct 29 09:09:30 spb-office kernel: [6.166581] [drm] Memory usable by graphics device = 2048M Oct 29 09:09:30 spb-office kernel: [6.214256] i915 :00:02.0: irq 46 for MSI/MSI-X Oct 29 09:09:30 spb-office kernel: [6.214272] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). Oct 29 09:09:30 spb-office kernel: [6.214274] [drm] Driver supports precise vblank timestamp query. Oct 29 09:09:30 spb-office kernel: [6.214374] vgaarb: device changed decodes: PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns= io+mem Oct 29 09:09:30 spb-office kernel: [6.299190] fbcon: inteldrmfb (fb0) is primary device Oct 29 09:09:30 spb-office kernel: [6.492114] Console: switching to colour frame buffer device 180x56 Oct 29 09:09:30 spb-office kernel: [6.494227] i915 :00:02.0: fb0: inteldrmfb frame buffer device Oct 29 09:09:30 spb-office kernel: [6.494228] i915 :00:02.0: registered panic notifier Oct 29 09:09:30 spb-office kernel: [6.510108] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) Oct 29 09:09:30 spb-office kernel: [6.510269] acpi device:36: registered as cooling_device9 Oct 29 09:09:30 spb-office kernel: [6.510321] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input7 Oct 29 09:09:30 spb-office kernel: [6.510386] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 Oct 29 09:09:30 spb-office kernel: [6.510677] snd_hda_intel :00:1b.0: irq 47 for MSI/MSI-X . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296660 Title: Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA (unable to handle kernel NULL pointer dereference / con_set_unimap+0x32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1296660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296660] Re: Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA (unable to handle kernel NULL pointer dereference / con_set_unimap+0x32
also hit this bug: ... Oct 29 09:04:14 spb-office kernel: [8.299240] [drm] Initialized drm 1.1.0 20060810 Oct 29 09:04:14 spb-office kernel: [8.337211] mei_me :00:16.0: irq 45 for MSI/MSI-X Oct 29 09:04:14 spb-office kernel: [8.537626] [drm] Memory usable by graphics device = 2048M Oct 29 09:04:14 spb-office kernel: [8.537628] checking generic (e000 30) vs hw (e000 1000) Oct 29 09:04:14 spb-office kernel: [8.537629] fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic driver Oct 29 09:04:14 spb-office kernel: [8.561832] Console: switching to colour dummy device 80x25 Oct 29 09:04:14 spb-office kernel: [8.561844] BUG: unable to handle kernel NULL pointer dereference at 0138 Oct 29 09:04:14 spb-office kernel: [8.561848] IP: [] con_set_unimap+0x32/0x290 Oct 29 09:04:14 spb-office kernel: [8.561850] PGD c73dd067 PUD c73db067 PMD 0 Oct 29 09:04:14 spb-office kernel: [8.561851] Oops: [#1] SMP Oct 29 09:04:14 spb-office kernel: [8.561862] Modules linked in: snd_hwdep kvm_intel i915(+) snd_pcm snd_page_alloc kvm crct10dif_pcl mul mei_me crc32_pclmul drm_kms_helper snd_timer drm mei snd ghash_clmulni_intel soundcore cryptd i2c_algo_bit joydev lpc_ich wmi mac_hid video serio_raw lp parport hid_generic usbhid hid ahci psmouse libahci r8169 mii Oct 29 09:04:14 spb-office kernel: [8.561864] CPU: 0 PID: 475 Comm: setfont Not tainted 3.13.0-36-generic #63-Ubuntu Oct 29 09:04:14 spb-office kernel: [8.561864] Hardware name: System manufacturer System Product Name/P8H61-MX R2.0, BIOS 1102 06/04/2 013 Oct 29 09:04:14 spb-office kernel: [8.561865] task: 88003697e000 ti: 8800c600e000 task.ti: 8800c600e000 Oct 29 09:04:14 spb-office kernel: [8.561867] RIP: 0010:[] [] con_set_unimap+0x32/0x290 Oct 29 09:04:14 spb-office kernel: [8.561868] RSP: 0018:8800c600fd48 EFLAGS: 00010246 Oct 29 09:04:14 spb-office kernel: [8.561869] RAX: 880035f46f08 RBX: 00c88150 RCX: Oct 29 09:04:14 spb-office kernel: [8.561870] RDX: 1278 RSI: 0296 RDI: 0296 Oct 29 09:04:14 spb-office kernel: [8.561870] RBP: 8800c600fdb0 R08: 8800c600e000 R09: 0001 Oct 29 09:04:14 spb-office kernel: [8.561871] R10: 0001 R11: 880035b2d6be R12: Oct 29 09:04:14 spb-office kernel: [8.561871] R13: 4b67 R14: 880035f46c00 R15: 880035f46c00 Oct 29 09:04:14 spb-office kernel: [8.561872] FS: 7f1770436740() GS:88011fa0() knlGS: Oct 29 09:04:14 spb-office kernel: [8.561873] CS: 0010 DS: ES: CR0: 80050033 Oct 29 09:04:14 spb-office kernel: [8.561874] CR2: 0138 CR3: c71e1000 CR4: 001407f0 Oct 29 09:04:14 spb-office kernel: [8.561874] Stack: Oct 29 09:04:14 spb-office kernel: [8.561876] 8800c600fd78 81311dfd 88003697e000 0005 Oct 29 09:04:14 spb-office kernel: [8.561878] 4b67 880035f46c00 01dac600fd88 880035f46c00 Oct 29 09:04:14 spb-office kernel: [8.561879] 0005 4b67 880035f46c00 Oct 29 09:04:14 spb-office kernel: [8.561879] Call Trace: Oct 29 09:04:14 spb-office kernel: [8.561884] [] ? apparmor_capable+0x1d/0x130 Oct 29 09:04:14 spb-office kernel: [8.561887] [] vt_ioctl+0xe83/0x11c0 Oct 29 09:04:14 spb-office kernel: [8.561889] [] tty_ioctl+0x26d/0xbb0 Oct 29 09:04:14 spb-office kernel: [8.561892] [] do_vfs_ioctl+0x2e0/0x4c0 Oct 29 09:04:14 spb-office kernel: [8.561894] [] ? do_munmap+0x297/0x3b0 Oct 29 09:04:14 spb-office kernel: [8.561895] [] SyS_ioctl+0x81/0xa0 Oct 29 09:04:14 spb-office kernel: [8.561897] [] system_call_fastpath+0x1a/0x1f Oct 29 09:04:14 spb-office kernel: [8.561906] Code: 89 e5 41 57 49 89 ff 41 56 41 55 41 54 53 48 89 d3 48 83 ec 40 48 89 7d d0 89 75 cc e8 68 e9 c5 ff 49 8b 87 10 03 00 00 4c 8b 20 <41> 8b 84 24 38 01 00 00 85 c0 0f 85 38 02 00 00 66 83 7d cc 00 Oct 29 09:04:14 spb-office kernel: [8.561907] RIP [] con_set_unimap+0x32/0x290 Oct 29 09:04:14 spb-office kernel: [8.561907] RSP Oct 29 09:04:14 spb-office kernel: [8.561907] CR2: 0138 Oct 29 09:04:14 spb-office kernel: [8.561909] ---[ end trace 5f42f50c9417d000 ]--- and system hangs... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296660 Title: Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA (unable to handle kernel NULL pointer dereference / con_set_unimap+0x32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1296660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mai
[Bug 1296660] Re: Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA (unable to handle kernel NULL pointer dereference / con_set_unimap+0x32
I had the same problem with Ubuntu 12.04 and kernel 3.13.0-37-generic
This solution working:
http://askubuntu.com/questions/169912/fb-conflicting-fb-hw-usage-inteldrmfb-vs-efi-vga-removing-generic-driver
but is incomplette. That helped me to make permanent fix:
"
--- /etc/grub.d/10_linux 2014-10-22 15:22:09.749586332 +0200
+++ /etc/grub.d/10_linux2014-10-22 15:08:09.908607933 +0200
@@ -95,9 +95,10 @@
if ! ${recovery} ; then
save_default_entry | sed -e "s/^/\t/"
- cat << EOF
- gfxmode \$linux_gfx_mode
-EOF
+# comment to fix "fb: conflicting fb hw usage inteldrmfb vs VESA VGA -
removing generic driver"
+# cat << EOF
+# gfxmode \$linux_gfx_mode
+#EOF
fi
cat << EOF
"
ther run update-grub, reboot and the error message is gone. SInce the
boot hang was occasional i cannot check it immediately, but if it happen
with this fix ill report it back.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1296660
Title:
Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA (unable
to handle kernel NULL pointer dereference / con_set_unimap+0x32
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1296660/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296660] Re: Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA (unable to handle kernel NULL pointer dereference / con_set_unimap+0x32
Also seeing the issue here (on occasion) w/ 3.13.0-37-generic: fb: conflicting fb hw usage nouveaufb vs VESA VGA - removing generic driver Console: switching to colour dummy device 80x25 BUG: unable to handle kernel NULL pointer dereference at 0138 IP: [] con_set_unimap+0x32/0x290 Call Trace: [] ? apparmor_capable+0x1d/0x130 [] vt_ioctl+0xe83/0x11c0 [] tty_ioctl+0x26d/0xbb0 [] do_vfs_ioctl+0x2e0/0x4c0 [] SyS_ioctl+0x81/0xa0 [] system_call_fastpath+0x1a/0x1f -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296660 Title: Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA (unable to handle kernel NULL pointer dereference / con_set_unimap+0x32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1296660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296660] Re: Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA (unable to handle kernel NULL pointer dereference / con_set_unimap+0x32
Hi, I am also getting similar traces on boot, not every time. The following is from a fresh net install on a ProLiant DL380 G7. Oct 13 11:54:36 node21 kernel: [3.347415] [drm] radeon kernel modesetting enabled. Oct 13 11:54:36 node21 kernel: [3.347490] checking generic (e800 13) vs hw (e800 800) Oct 13 11:54:36 node21 kernel: [3.347491] fb: conflicting fb hw usage radeondrmfb vs VESA VGA - removing generic driver Oct 13 11:54:36 node21 kernel: [3.349507] Console: switching to colour dummy device 80x25 Oct 13 11:54:36 node21 kernel: [3.349524] BUG: unable to handle kernel NULL pointer dereference at 0138 Oct 13 11:54:36 node21 kernel: [3.349528] IP: [] con_set_unimap+0x32/0x290 Oct 13 11:54:36 node21 kernel: [3.349531] PGD bdbef4067 PUD bdada8067 PMD 0 Oct 13 11:54:36 node21 kernel: [3.349532] Oops: [#1] SMP Oct 13 11:54:36 node21 kernel: [3.349548] Modules linked in: intel_powerclamp radeon(+) coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul gpio_ich ghash_clmulni_intel ttm aesni_intel drm_kms_helper aes_x86_64 drm lrw gf128mul glue_helper ablk_helper i2c_algo_bit cryptd hpilo hpwdt i7core_edac joydev edac_core lpc_ich ipmi_si serio_raw mac_hid acpi_power_meter lp parport hid_generic usbhid hid psmouse bnx2 hpsa Oct 13 11:54:36 node21 kernel: [3.349551] CPU: 22 PID: 700 Comm: setfont Tainted: G I 3.13.0-37-generic #64-Ubuntu Oct 13 11:54:36 node21 kernel: [3.349552] Hardware name: HP ProLiant DL380 G7, BIOS P67 05/05/2011 Oct 13 11:54:36 node21 kernel: [3.349553] task: 8817da688000 ti: 880bd5d6 task.ti: 880bd5d6 Oct 13 11:54:36 node21 kernel: [3.349556] RIP: 0010:[] [] con_set_unimap+0x32/0x290 Oct 13 11:54:36 node21 kernel: [3.349557] RSP: 0018:880bd5d61d48 EFLAGS: 00010246 Oct 13 11:54:36 node21 kernel: [3.349558] RAX: 880bdadd0b08 RBX: 01c0bb10 RCX: c100 Oct 13 11:54:36 node21 kernel: [3.349558] RDX: 1530 RSI: 0296 RDI: 0296 Oct 13 11:54:36 node21 kernel: [3.349559] RBP: 880bd5d61db0 R08: 880bd5d6 R09: 001c Oct 13 11:54:36 node21 kernel: [3.349561] R10: 0054 R11: 004c R12: Oct 13 11:54:36 node21 kernel: [3.349562] R13: 4b67 R14: 880bdadd0800 R15: 880bdadd0800 Oct 13 11:54:36 node21 kernel: [3.349563] FS: 7f81dbf6c740() GS:880befd6() knlGS: Oct 13 11:54:36 node21 kernel: [3.349564] CS: 0010 DS: ES: CR0: 8005003b Oct 13 11:54:36 node21 kernel: [3.349565] CR2: 0138 CR3: 000bd5c8e000 CR4: 07e0 Oct 13 11:54:36 node21 kernel: [3.349566] Stack: Oct 13 11:54:36 node21 kernel: [3.349571] 880bd5d61d78 8131226d 8817da688000 0002 Oct 13 11:54:36 node21 kernel: [3.349575] 4b67 880bdadd0800 02e1d5d61d88 880bdadd0800 Oct 13 11:54:36 node21 kernel: [3.349577] 0002 4b67 880bdadd0800 Oct 13 11:54:36 node21 kernel: [3.349577] Call Trace: Oct 13 11:54:36 node21 kernel: [3.349583] [] ? apparmor_capable+0x1d/0x130 Oct 13 11:54:36 node21 kernel: [3.349587] [] vt_ioctl+0xe83/0x11c0 Oct 13 11:54:36 node21 kernel: [3.349590] [] tty_ioctl+0x26d/0xbb0 Oct 13 11:54:36 node21 kernel: [3.349594] [] do_vfs_ioctl+0x2e0/0x4c0 Oct 13 11:54:36 node21 kernel: [3.349597] [] ? do_munmap+0x297/0x3b0 Oct 13 11:54:36 node21 kernel: [3.349599] [] SyS_ioctl+0x81/0xa0 Oct 13 11:54:36 node21 kernel: [3.349602] [] system_call_fastpath+0x1a/0x1f Oct 13 11:54:36 node21 kernel: [3.349614] Code: 89 e5 41 57 49 89 ff 41 56 41 55 41 54 53 48 89 d3 48 83 ec 40 48 89 7d d0 89 75 cc e8 a8 e4 c5 ff 49 8b 87 10 03 00 00 4c 8b 20 <41> 8b 84 24 38 01 00 00 85 c0 0f 85 38 02 00 00 66 83 7d cc 00 Oct 13 11:54:36 node21 kernel: [3.349616] RIP [] con_set_unimap+0x32/0x290 Oct 13 11:54:36 node21 kernel: [3.349616] RSP Oct 13 11:54:36 node21 kernel: [3.349617] CR2: 0138 Oct 13 11:54:36 node21 kernel: [3.349618] ---[ end trace f62d7fc492f713e6 ]--- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296660 Title: Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA (unable to handle kernel NULL pointer dereference / con_set_unimap+0x32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1296660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296660] Re: Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA
Joseph: I'm seeing an identical backtrace on one of my dads machines after upgrade to a recent kernel; it's intermittent perhaps 1/4 ish boots 3.13.0-32-generic, so I say not fixed: Jul 22 17:58:13 thedr kernel: [ 16.146863] fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic driver Jul 22 17:58:13 thedr kernel: [ 16.202062] Console: switching to colour dummy device 80x25 Jul 22 17:58:13 thedr kernel: [ 16.202085] BUG: unable to handle kernel NULL pointer dereference at 0138 Jul 22 17:58:13 thedr kernel: [ 16.202089] IP: [] con_set_unimap+0x32/0x290 Jul 22 17:58:13 thedr kernel: [ 16.202091] PGD c6dc1067 PUD c6d8d067 PMD 0 Jul 22 17:58:13 thedr kernel: [ 16.202092] Oops: [#1] SMP Jul 22 17:58:13 thedr kernel: [ 16.202104] Modules linked in: intel_powerclamp snd_hda_codec coretemp i915(+) snd_hwdep lpc_ich snd_pcm snd_page_alloc kvm_intel kvm snd_seq_midi snd_seq_midi_event crct10dif_pclmul snd_rawmidi crc32_pclmul snd_seq drm_kms_helper drm i2c_algo_bit mei_me mei ghash_clmulni_intel cryptd snd_seq_device snd_timer wmi parport_pc snd video ppdev serio_raw soundcore mac_hid lp parport binfmt_misc hid_generic usbhid hid r8169 mii Jul 22 17:58:13 thedr kernel: [ 16.202106] CPU: 1 PID: 593 Comm: setfont Not tainted 3.13.0-32-generic #57-Ubuntu Jul 22 17:58:13 thedr kernel: [ 16.202106] Hardware name: System manufacturer System Product Name/P8H61-MX R2.0, BIOS 0504 06/29/2012 Jul 22 17:58:13 thedr kernel: [ 16.202107] task: 8802126cdfc0 ti: 8800c6c86000 task.ti: 8800c6c86000 Jul 22 17:58:13 thedr kernel: [ 16.202110] RIP: 0010:[] [] con_set_unimap+0x32/0x290 Jul 22 17:58:13 thedr kernel: [ 16.202110] RSP: 0018:8800c6c87d48 EFLAGS: 00010246 Jul 22 17:58:13 thedr kernel: [ 16.202111] RAX: 88021740c308 RBX: 00e58b10 RCX: c710 Jul 22 17:58:13 thedr kernel: [ 16.202111] RDX: 1278 RSI: 0296 RDI: 0296 Jul 22 17:58:13 thedr kernel: [ 16.202112] RBP: 8800c6c87db0 R08: 8800c6c86000 R09: 0001 Jul 22 17:58:13 thedr kernel: [ 16.202113] R10: 0001 R11: ea0008424740 R12: Jul 22 17:58:13 thedr kernel: [ 16.202113] R13: 4b67 R14: 88021740c000 R15: 88021740c000 Jul 22 17:58:13 thedr kernel: [ 16.202114] FS: 7fe0c4bf9740() GS:88021fb0() knlGS: Jul 22 17:58:13 thedr kernel: [ 16.202115] CS: 0010 DS: ES: CR0: 80050033 Jul 22 17:58:13 thedr kernel: [ 16.202115] CR2: 0138 CR3: c6d92000 CR4: 000407e0 Jul 22 17:58:13 thedr kernel: [ 16.202116] Stack: Jul 22 17:58:13 thedr kernel: [ 16.202118] 8800c6c87d78 813110ed 8802126cdfc0 Jul 22 17:58:13 thedr kernel: [ 16.202119] 4b67 88021740c000 02e1c6c87d88 88021740c000 Jul 22 17:58:13 thedr kernel: [ 16.202120] 4b67 88021740c000 Jul 22 17:58:13 thedr kernel: [ 16.202120] Call Trace: Jul 22 17:58:13 thedr kernel: [ 16.202125] [] ? apparmor_capable+0x1d/0x130 Jul 22 17:58:13 thedr kernel: [ 16.202127] [] vt_ioctl+0xe83/0x11c0 Jul 22 17:58:13 thedr kernel: [ 16.202129] [] tty_ioctl+0x26d/0xbb0 Jul 22 17:58:13 thedr kernel: [ 16.202132] [] do_vfs_ioctl+0x2e0/0x4c0 Jul 22 17:58:13 thedr kernel: [ 16.202134] [] ? vtime_account_user+0x54/0x60 Jul 22 17:58:13 thedr kernel: [ 16.202136] [] SyS_ioctl+0x81/0xa0 Jul 22 17:58:13 thedr kernel: [ 16.202139] [] tracesys+0xe1/0xe6 Jul 22 17:58:13 thedr kernel: [ 16.202149] Code: 89 e5 41 57 49 89 ff 41 56 41 55 41 54 53 48 89 d3 48 83 ec 40 48 89 7d d0 89 75 cc e8 38 0c c6 ff 49 8b 87 10 03 00 00 4c 8b 20 <41> 8b 84 24 38 01 00 00 85 c0 0f 85 38 02 00 00 66 83 7d cc 00 Jul 22 17:58:13 thedr kernel: [ 16.202151] RIP [] con_set_unimap+0x32/0x290 Jul 22 17:58:13 thedr kernel: [ 16.202151] RSP Jul 22 17:58:13 thedr kernel: [ 16.202152] CR2: 0138 Jul 22 17:58:13 thedr kernel: [ 16.202153] ---[ end trace 2040d79b62a518c4 ]--- 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Summary changed: - Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA + Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA (unable to handle kernel NULL pointer dereference / con_set_unimap+0x32 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296660 Title: Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA (unable to handle kernel NULL pointer dereference / con_set_unimap+0x32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1296660/+subscriptions
[Bug 1296660] Re: Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA
Thank you for taking the time to file a bug report on this issue. However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request. With the recent release of this Ubuntu release, would like to confirm if this bug is still present. Please test again with the newer kernel and indicate in the bug if this issue still exists or not. You can update to the latest development kernel by simply running the following commands in a terminal window: sudo apt-get update sudo apt-get dist-upgrade If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released. If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging. Thank you for your help, we really do appreciate it. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Tags added: kernel-request-3.13.0-24.46 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296660 Title: Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1296660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296660] Re: Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296660 Title: Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1296660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296660] Re: Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA
kernel-fixed-upstream - v3.14-rc8 booted without problem in 6 successive tests ** Tags added: kernel-fixed-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296660 Title: Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1296660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296660] Re: Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.14 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-rc8-trusty/ ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296660 Title: Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1296660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1296660] Re: Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA
El 25/03/14 17:58, Wolfgang Denk escribió: > I agree that this seems strange, but that was what I have been asked > to do: It seems they decided to confirm by default, so everything is okay. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296660 Title: Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1296660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1296660] Re: Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA
Dear Alberto, In message <20140325163154.5705.60364.mal...@chaenomeles.canonical.com> you wrote: > Never confirm your own bugs! > > ** Changed in: linux (Ubuntu) >Status: Confirmed => New I agree that this seems strange, but that was what I have been asked to do: | >From a terminal window please run: | | apport-collect 1296660 | | and then change the status of the bug to 'Confirmed'. | | If, due to the nature of the issue you have encountered, you are unable | to run this command, please add a comment stating that fact and change | the bug status to 'Confirmed'. This explicitly says I should - in both cases - "change the status of the bug to 'Confirmed'." Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: w...@denx.de A morsel of genuine history is a thing so rare as to be always valuable. - Thomas Jefferson -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296660 Title: Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1296660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296660] Re: Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA
Never confirm your own bugs! ** Changed in: linux (Ubuntu) Status: Confirmed => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296660 Title: Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1296660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296660] Re: Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA
It renders the system temporarily or permanently unusable. ** Changed in: linux (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296660 Title: Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1296660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296660] Re: Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA
Obviously I can run the apport-collect command only in case of a successful boot, but not in the error case when the whole system hangs. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296660 Title: Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1296660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296660] Re: Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA
apport information ** Tags added: apport-collected ** Description changed: Booting hangs on a Ubuntu Trusty Tahr (development branch) [3.13.0-18-generic #38-Ubuntu SMP Mon Mar 17 21:40:06 UTC 2014 x86_64] based system. I can ping the system, but neither local nor remote login is possible. The system log shows this: Mar 23 21:59:08 minerva kernel: [ 36.301855] [drm] AST 2300 detected Mar 23 21:59:08 minerva kernel: [ 36.301899] [drm] dram 163200 1 16 0100 Mar 23 21:59:08 minerva kernel: [ 36.301968] [TTM] Zone kernel: Available graphics memory: 819 kiB Mar 23 21:59:08 minerva kernel: [ 36.301969] [TTM] Zone dma32: Available graphics memory: 2097152 kiB Mar 23 21:59:08 minerva kernel: [ 36.301969] [TTM] Initializing pool allocator Mar 23 21:59:08 minerva kernel: [ 36.301972] [TTM] Initializing DMA pool allocator Mar 23 21:59:09 minerva kernel: [ 36.470046] checking generic (f600 50) vs hw (f600 100) Mar 23 21:59:09 minerva kernel: [ 36.470047] fb: conflicting fb hw usage astdrmfb vs VESA VGA - removing generic driver Mar 23 21:59:09 minerva kernel: [ 36.632111] Console: switching to colour dummy device 80x25 Mar 23 21:59:09 minerva kernel: [ 36.632129] BUG: unable to handle kernel NULL pointer dereference at 0138 Mar 23 21:59:09 minerva kernel: [ 36.632134] IP: [] con_set_unimap+0x32/0x290 Mar 23 21:59:09 minerva kernel: [ 36.632136] PGD 35c24067 PUD 35c23067 PMD 0 Mar 23 21:59:09 minerva kernel: [ 36.632137] Oops: [#1] SMP Mar 23 21:59:09 minerva kernel: [ 36.632152] Modules linked in: x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm ast(+) ttm drm_kms_helper crct10dif_pclmul crc32_pclmul drm ghash_clmulni_intel aesni_intel aes_x86_64 syscopyarea sysfillrect sysimgblt lrw gf128mul glue_helper ablk_helper cryptd joydev lpc_ich shpchp ipmi_si video mac_hid lp parport raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq igb hid_generic i2c_algo_bit raid1 dca usbhid raid0 ahci ptp multipath hid usb_storage libahci pps_core linear Mar 23 21:59:09 minerva kernel: [ 36.632153] CPU: 4 PID: 665 Comm: setfont Not tainted 3.13.0-18-generic #38-Ubuntu Mar 23 21:59:09 minerva kernel: [ 36.632154] Hardware name: Supermicro X10SLL+-F/X10SLL+-F, BIOS 1.1a 11/01/2013 Mar 23 21:59:09 minerva kernel: [ 36.632155] task: 880408512fe0 ti: 88040852a000 task.ti: 88040852a000 Mar 23 21:59:09 minerva kernel: [ 36.632157] RIP: 0010:[] [] con_set_unimap+0x32/0x290 Mar 23 21:59:09 minerva kernel: [ 36.632157] RSP: 0018:88040852bd48 EFLAGS: 00010246 Mar 23 21:59:09 minerva kernel: [ 36.632158] RAX: 880404ee3308 RBX: 01bdcb10 RCX: c710 Mar 23 21:59:09 minerva kernel: [ 36.632159] RDX: 1674 RSI: 16761674 RDI: 0296 Mar 23 21:59:09 minerva kernel: [ 36.632159] RBP: 88040852bdb0 R08: 88040852a000 R09: Mar 23 21:59:09 minerva kernel: [ 36.632160] R10: 024f R11: 01e3 R12: Mar 23 21:59:09 minerva kernel: [ 36.632160] R13: 4b67 R14: 880404ee3000 R15: 880404ee3000 Mar 23 21:59:09 minerva kernel: [ 36.632161] FS: 7fa963158740() GS:88041fd0() knlGS: Mar 23 21:59:09 minerva kernel: [ 36.632162] CS: 0010 DS: ES: CR0: 80050033 Mar 23 21:59:09 minerva kernel: [ 36.632162] CR2: 0138 CR3: 000406428000 CR4: 001407e0 Mar 23 21:59:09 minerva kernel: [ 36.632163] DR0: DR1: DR2: Mar 23 21:59:09 minerva kernel: [ 36.632164] DR3: DR6: fffe0ff0 DR7: 0400 Mar 23 21:59:09 minerva kernel: [ 36.632164] Stack: Mar 23 21:59:09 minerva kernel: [ 36.632166] 8130bd6f 880408512fe0 0001 4b67 Mar 23 21:59:09 minerva kernel: [ 36.632168] 880404ee3000 fdfd 02e10852bd88 880404ee3000 Mar 23 21:59:09 minerva kernel: [ 36.632169] 0001 4b67 880404ee3000 Mar 23 21:59:09 minerva kernel: [ 36.632169] Call Trace: Mar 23 21:59:09 minerva kernel: [ 36.632174] [] ? apparmor_capable+0x1f/0x1a0 Mar 23 21:59:09 minerva kernel: [ 36.632176] [] vt_ioctl+0xe83/0x11c0 Mar 23 21:59:09 minerva kernel: [ 36.632178] [] tty_ioctl+0x26d/0xbb0 Mar 23 21:59:09 minerva kernel: [ 36.632182] [] do_vfs_ioctl+0x2e0/0x4c0 Mar 23 21:59:09 minerva kernel: [ 36.632184] [] ? vtime_account_user+0x54/0x60 Mar 23 21:59:09 minerva kernel: [ 36.632185] [] SyS_ioctl+0x81/0xa0 Mar 23 21:59:09 minerva kernel: [ 36.632187] [] tracesys+0xe1/0xe6 Mar 23 21:59:09 minerva kernel: [ 36.632195] Code: 89 e5 41 57 49 89 ff 41 56 41 55 41 54 53 48 89 d3 48 83 ec 40 48 89 7d d0 89
[Bug 1296660] Re: Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296660 Title: Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1296660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296660] Re: Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA
I cannot enter the Package name. Apparently the problem is with the ast driver, i. e. /lib/modules/3.13.0-18-generic/kernel/drivers/gpu/drm/ast/ast.ko ; that belongs to the linux-image-extra-3.13.0-18-generic package. Using the "Chose" option on the web page gives the same name. Nevertheless I get an error message ''There is no package named 'linux-image-extra-3.13.0-18-generic' published in Ubuntu.'' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296660 Title: Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1296660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296660] Re: Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode. To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1296660/+editstatus and add the package name in the text box next to the word Package. [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: bot-comment -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296660 Title: Kernel oops: fb: conflicting fb hw usage astdrmfb vs VESA VGA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1296660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
