[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

2015-02-13 Thread Samantha Jian-Pielak
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.

[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

2014-12-22 Thread Joerie de Gram
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

[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

2014-12-18 Thread Joerie de Gram
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

[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

2014-12-10 Thread Samantha Jian-Pielak
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

[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

2014-10-29 Thread atimonin
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

[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

2014-10-29 Thread atimonin
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

[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

2014-10-22 Thread Jiri Fojtasek
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

[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

2014-10-20 Thread John Stultz
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: [8145d382]

[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

2014-10-14 Thread Hugh Saunders
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)