Per #32 and #33, bug has been fixed. Closing
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
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: con
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
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 Ubunt
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 co
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 ker
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-o
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 =
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 201
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
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)
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 gene
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 s
** 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 ma
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: con
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 t
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 Ubun
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 wind
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 astd
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: f
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 su
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 possibl
** 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
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
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
24 matches
Mail list logo
