xcasex, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control
team, and Ubuntu Bug Squad would like you to please file a new report by
executing the following in a terminal:
ubuntu-bug linux
For more on this, please see the Ubuntu Kernel team article:
Confirmed on Raring.
additional information as per Markus Schade above.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1070690
Title:
BUG: unable to handle kernel NULL pointer dereference at (null);
This depends on the definition of fixed. Booting with nomodeset still
leads to the originally reported call trace, even in 3.5.0-26-generic
#42. So, the workaround is either to blacklist i915 or to add something
like video=1024x768 to the kernel options in order to get a resolution
that is not
assuming this is fixed in raring as well.
** Changed in: linux (Ubuntu Raring)
Status: Incomplete = Invalid
** Changed in: linux (Ubuntu Raring)
Assignee: Timo Aaltonen (tjaalton) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Tim: Apologies, I didn't notice your comment #62
The oops was in dmesg, as reported in bug 1077658 and as I said in #61 the
was fixed in -19 for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Tim, did you file the bug upstream as Daniel requested?
** Changed in: linux (Ubuntu Raring)
Status: Confirmed = Incomplete
** Changed in: linux (Ubuntu Raring)
Assignee: (unassigned) = Timo Aaltonen (tjaalton)
--
You received this bug notification because you are a member of
Marking Invalid for Quantal as per
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1070690/comments/62
.
** Changed in: linux (Ubuntu Quantal)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Well, the small error message ( *ERROR* Cannot initialize the agpgart
module. DRM: Fill_in_dev failed.) when booting without 'nomodeset' is
gone. But the oops is still present when booting with nomodeset. But
since upstream says that nomodeset is not really supported, I can only
assume that only
Dear Dave,
for Markus and me the oops was fixed in 3.5.0-18. I haven't seen your
intel(0)... messages on my test systems, where did you get them?
dmesg?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I think there are really two separate bugs going on here;
1) For some reason the Intel chipset doesn't like something and gives up
2) When it cleans up from (1) it panics
It looks to me like 3.5.0-19-generic has fixed the panic on my box; although I
still get a black screen - but that looks
** Tags removed: performing-bisect
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1070690
Title:
BUG: unable to handle kernel NULL pointer dereference at (null); RIP:
0010:[8167f93a]
My and Daniels email about this problem:
http://lists.freedesktop.org/archives/intel-
gfx/2012-November/022707.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1070690
Title:
BUG: unable to
I talked to Daniel Vetter, he is responsible for the i915 driver and
works for Intel. He told me that this chipset series doesn't support the
parameter nomodeset. So this bug report can be closed now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Tim Meusel, thank you for investigating this further. Regarding your comments
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1070690/comments/57 :
He told me that this chipset series doesn't support the parameter nomodeset.
He did not say it's not supported. What he said was:
Well, you're
Dear Christopher,
Daniel wrote to me in a personal email usermodesetting was _never_ supported
on these machines. (talking about Ivy Bridge chipsets).
As written by Markus in the initial post, we had an OOPS/Kernel Panic with the
i915 driver and the first official Ubuntu 12.10 driver
** Tags removed: kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-v3.7-rc2-raring
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-upstream-3.7-rc6
kernel-unable-to-test-upstream-v3.7-rc2
--
You received this bug notification because you are a member of Ubuntu
Bugs,
FYI: the error is still present in the newest 3.7-rc6 mainline release
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1070690
Title:
BUG: unable to handle kernel NULL pointer dereference at (null);
Hi,
my previous posts were not accurate enough, sorry for that. To clarify some
facts:
The Raring Kernel 3.7.0-0.5 and the newer one from last night 3.7.0-1.7 are as
buggy as the real quantal kernel. Their dmesg output is the same as mentioned
in my comment #42. Also as written in post #49,
** Also affects: bumblebee
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1070690
Title:
BUG: unable to handle kernel NULL pointer dereference at (null);
https://github.com/Bumblebee-Project/Bumblebee/issues/277
** Also affects: bumblebee (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Quantal)
Status: Incomplete = New
** Changed in: linux (Ubuntu Raring)
Status: Incomplete = New
--
You received
Christopher M. Penalver (penalvch)
I do not share your views, so do not try to do anything without explanation.
we do not believe in an unknown fucking garbage.
therefore, you have no right to label something there just based on your
philosophy.
p.s. and, last but not least.
I never see your
Karma Dorje, to maintain a respectful atmosphere, please follow the code
of conduct - http://www.ubuntu.com/project/about-ubuntu/conduct . Bug
reports are handled by humans, the majority of whom are volunteers, so
please bear this in mind.
As well, please do not add bumblebee (Ubuntu) tasks as
Markus Meusel, thank you for your comments. Regarding them
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1070690/comments/48 :
Christopher, please read Tim's post #39.
I re-reviewed comment #39 and saw no mention of how either of you tested
this issue in a Raring environment, whose Ubuntu
Markus Schade, thank you for your comments. Regarding them
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1070690/comments/45 :
as Tim wrote, the upstream bug is fixed as of 3.7-rc5.
Changed in linux (Ubuntu Raring):
status: Incomplete → Fix Released
The fact Tim said his issue is
Fazlur, if you have a bug in Ubuntu, could you please file a new report by
executing the following in a terminal:
ubuntu-bug linux
For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
the Ubuntu Bug
Christopher, please read Tim's post #39. He is testing the platform
with me. We are working on the issue together. So the bug is indeed
fixed for Raring.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I justed tested several other raring Kernel:
3.6.4-030604-generic
3.6.6-030606-generic
3.7.0-030700rc1-generic
3.7.0-030700rc2-generic
3.7.0-030700rc3-generic
3.7.0-030700rc4-generic
they are all working, dmesg output looks like the one posted in #42
--
You received this bug notification
I tested the 3.7.0-030700rc5 #20120835 too,
looks like it works without the kernelparameter nomodeset:
[9.374325] [drm] Initialized drm 1.1.0 20060810
[9.429448] pci :00:00.0: Intel Ivybridge Chipset
[9.429524] pci :00:00.0: detected gtt size: 2097152K total, 262144K
** Attachment added: dmesg 3.7.0-030700rc5 without nomodeset
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1070690/+attachment/3431295/+files/dmesg_no_nomodeset
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am facing the same issue on 3.5.0-18 on Ubuntu 12.10 (64-bit)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1070690
Title:
BUG: unable to handle kernel NULL pointer dereference at (null); RIP:
as Tim wrote, the upstream bug is fixed as of 3.7-rc5. So the only thing
that needs to be resolved is the actual quantal bug. As we have tested
the mainstream kernels up to 3.5.7, could you please post the pre-
release quantal kernels that we should test?
** Changed in: linux (Ubuntu Raring)
I've just reported bug 1077658 which looks like it might be the same as this.
This only happens for me if I plug in via a KVM switch, not direclty in via a
monitor.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
3.7.0-030700rc5 #20120835 from the nightlies works for me
(http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7-rc5-raring/ although I'm on
a quantal userspace)
So I say that makes it a fixed upstream
3.6.3-030603 #201210211349 boots but won't start X (but ctrl-alt-f1 gets
me a console)
@Joseph
I tested together with Markus 3.5.0-16.25 and several older ones, all
are working.
In 3.5.0-17.26 were some drm/i915 related things added.
Booting the 17.26 prints the following at boot:
* Starting load fallback graphics devices [fail]
the curious thing
Upstream is already aware of the issue, see
http://www.spinics.net/lists/kernel/msg1418335.html
So the only thing that needs to be determined, is which quantal patch to
the 3.5 mainline has introduced the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
As outlined in the message the bug is triggered by adding the
nomodeset option to the kernel command line which seems to enable a
different code path. So booting without nomodeset is fine, but I don't
need KMS on a server.
--
You received this bug notification because you are a member of Ubuntu
@Markus,
Comment #27 lists some kernel version prior to The final 12.10 kernel.
Did you not see this bug in any of those listed kernels? If that is the
case, I will post some additional kernels to test.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
PLease Christopher, could you tell us what is missing to this bug ?
For what I can see this bug was introduced between 3.5.0-18-generic and
3.5.0-17-generic, and looking at the changelog, there is a bunch of i915
changes there.
--
You received this bug notification because you are a member of
Christpher, I don't see any reason to open a new bug, this is the exact
same issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1070690
Title:
BUG: unable to handle kernel NULL pointer
I also encounter this issue on my dell xps 15.
This bug happens for me with kernel 3.5.0-18-generic, but not with
3.5.0-17-generic.
When booting with 3.5.0-18-generic, driver initialization fail, and X
fallback to using the vesa driver.
--
You received this bug notification because you are a
Florent Mertens, if you have a bug in Ubuntu, could you please file a new
report by executing the following in a terminal:
ubuntu-bug linux
For more on this, please see the Ubuntu Bug Control and Ubuntu Bug Squad
article:
I am a bit puzzled. I have tested up to 3.5.7 including the mainline 3.5.5, on
which the quantal kernel is based, without encountering this error. But looking
at the changelog I can't see anything related to drm or i915.
Kernel 3.6.0 had the light version of the bug.
[9.001003]
the light bug is already present in 3.6-rc1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1070690
Title:
BUG: unable to handle kernel NULL pointer dereference at (null); RIP:
I've seen the same problem on my Dell M4700. However, it appears to fail
intermittently. The last time I booted, the driver loaded without error,
but the time before that it failed with the message below.
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor
Graphics
** Changed in: linux (Ubuntu Raring)
Status: Triaged = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1070690
Title:
BUG: unable to handle kernel NULL pointer dereference at
Simon Jones, if you have a bug in Ubuntu, could you please file a new report by
executing the following in a terminal:
ubuntu-bug linux
For more on this, please see the Ubuntu Bug Control and Ubuntu Bug Squad
article:
Markus Schade, as this report is apport-collect'ed against your ivy bridge
computer, please file a new report against your sandy bridge computer by
executing the following in a terminal, and please feel free to subscribe me to
it:
ubuntu-bug linux
Thank you for your understanding.
Status
This issue appears to be an upstream bug, since you tested the latest
upstream kernel. Would it be possible for you to open an upstream bug
report[0]? That will allow the upstream Developers to examine the
issue, and may provide a quicker resolution to the bug.
Please follow the instructions on
In addition to opening an upstream bug, I'd like to perform a bisect to
figure out what commit caused this regression. It would be very helpful
to know the earliest kernel where the issue started happening as well as
the latest kernel that did not have this issue.
Can you test the following
49 matches
Mail list logo
