Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/648631
Title:
Kernel Oops - unable to handle kernel NULL pointer dereference; IP:
[a007e3c6] ips_detect_cpu+0x76/0x1d0 [intel_ips]
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug
** Tags added: hwe-blocker
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/648631
Title:
Kernel Oops - unable to handle kernel NULL pointer dereference; IP:
[a007e3c6]
@AceLan: I can reproduce the bug in 2.6.35-22.35.
I can't reproduce in 2.6.35-23.40; the changelog indicates it may have
been fixed by an upstream commit in 2.6.35-23.36 (intel_ips: potential
null dereference).
--
Kernel Oops - unable to handle kernel NULL pointer dereference; IP:
It works for me on my Acer Aspire One 753 with the 2.6.35-23.40 generic
kernel
--
Kernel Oops - unable to handle kernel NULL pointer dereference; IP:
[a007e3c6] ips_detect_cpu+0x76/0x1d0 [intel_ips]
https://bugs.launchpad.net/bugs/648631
You received this bug notification because you
It works for me on my Acer Aspire One 753 with the 2.6.35-23.40 generic
kernel
--
Kernel Oops - unable to handle kernel NULL pointer dereference; IP:
[a007e3c6] ips_detect_cpu+0x76/0x1d0 [intel_ips]
https://bugs.launchpad.net/bugs/648631
You received this bug notification because you
Thank you guys, I'm going to close this bug.
Please feel free to re-open this bug, if you encounter this problem again.
** Changed in: linux (Ubuntu)
Status: In Progress = Fix Released
--
Kernel Oops - unable to handle kernel NULL pointer dereference; IP:
[a007e3c6]
Hi,
I still have this problem yesterday even after an update.
However, blacklisting the module solved the trouble.
On Sat, Nov 20, 2010 at 6:30 AM, AceLan Kao 648...@bugs.launchpad.net wrote:
Steve, does this bug still exist?
I saw the patch already be applied on 2.6.35-22.35 security release.
The kernel at http://people.canonical.com/~acelan/bugs/lp648631/ fixes a
boot failure with the same symptoms ('No CPUID...' message in dmesg
followed by an OOPS, non-functional X) on a Thinkpad Edge 13 w/ Intel
Pentium U5400.
--
Kernel Oops - unable to handle kernel NULL pointer dereference; IP:
Steve, does this bug still exist?
I saw the patch already be applied on 2.6.35-22.35 security release.
--
Kernel Oops - unable to handle kernel NULL pointer dereference; IP:
[a007e3c6] ips_detect_cpu+0x76/0x1d0 [intel_ips]
https://bugs.launchpad.net/bugs/648631
You received this bug
** Changed in: linux (Ubuntu)
Status: Confirmed = In Progress
--
Kernel Oops - unable to handle kernel NULL pointer dereference; IP:
[a007e3c6] ips_detect_cpu+0x76/0x1d0 [intel_ips]
https://bugs.launchpad.net/bugs/648631
You received this bug notification because you are a member
That package indeed seems to work now. Dmesg says that intel_ips doesn't
support my CPU, but X works fine, so..
--
Kernel Oops - unable to handle kernel NULL pointer dereference; IP:
[a007e3c6] ips_detect_cpu+0x76/0x1d0 [intel_ips]
https://bugs.launchpad.net/bugs/648631
You received
Great, that's the correct behavior. Non supported CPU will encounter the NULL
pointer dereference OOPS.
The patch fixed the problem.
I'll send SRU to the kernel team list for review and hope this patch could be
included soon.
Thanks for the bug report.
--
Kernel Oops - unable to handle kernel
Lauri,
In the same directory has the new packages, could help to test it again.
Thanks.
http://people.canonical.com/~acelan/bugs/lp648631/
--
Kernel Oops - unable to handle kernel NULL pointer dereference; IP:
[a007e3c6] ips_detect_cpu+0x76/0x1d0 [intel_ips]
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = AceLan Kao (acelankao)
--
Kernel Oops - unable to handle kernel NULL pointer dereference; IP:
[a007e3c6] ips_detect_cpu+0x76/0x1d0 [intel_ips]
https://bugs.launchpad.net/bugs/648631
You received this bug notification because
Lauri,
Aha, I got it, your CPU is the newest one and not listed in the code.
I'll drop the author an email to see how to fix this problem.
So, before the patch comes out, please blacklisting intel_ips modules :)
--
Kernel Oops - unable to handle kernel NULL pointer dereference; IP:
** Bug watch added: Linux Kernel Bug Tracker #18742
http://bugzilla.kernel.org/show_bug.cgi?id=18742
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=18742
Importance: Unknown
Status: Unknown
--
Kernel Oops - unable to handle kernel NULL pointer dereference;
** Changed in: linux
Importance: Unknown = Undecided
** Changed in: linux
Status: Unknown = New
** Changed in: linux
Remote watch: Linux Kernel Bug Tracker #18742 = None
** Changed in: linux
Status: New = Invalid
--
Kernel Oops - unable to handle kernel NULL pointer
Lauri,
I found the root cause and informed the owner of the driver.
Could you also help me to confirm if my modification also works for you?
Thanks.
http://people.canonical.com/~acelan/bugs/lp648631/
--
Kernel Oops - unable to handle kernel NULL pointer dereference; IP:
[a007e3c6]
I tested the kernel of yours, and I still have the same oops with it.
--
Kernel Oops - unable to handle kernel NULL pointer dereference; IP:
[a007e3c6] ips_detect_cpu+0x76/0x1d0 [intel_ips]
https://bugs.launchpad.net/bugs/648631
You received this bug notification because you are a
Yes, it's working now. Sorry, I forgot to remove other rework on the
kernel.
--
Kernel Oops - unable to handle kernel NULL pointer dereference; IP:
[a007e3c6] ips_detect_cpu+0x76/0x1d0 [intel_ips]
https://bugs.launchpad.net/bugs/648631
You received this bug notification because you are
Lauri,
Does blacklist intel_ips make the system enter X successful?
It seems not work for me, but yes, no error msg in dmesg.
My kernel version is vmlinuz-2.6.35-22-generic
--
Kernel Oops - unable to handle kernel NULL pointer dereference; IP:
[a007e3c6] ips_detect_cpu+0x76/0x1d0
AceLan Kao,
If you're experiencing this bug too, please file a separate bug report by
typing ubuntu-bug linux into a terminal. There's a strict
one-report-per-person policy with kernel bugs. Thank you.
--
Kernel Oops - unable to handle kernel NULL pointer dereference; IP:
[a007e3c6]
Indeed, I have X working flawlessly with intel_ips blacklisted.
--
Kernel Oops - unable to handle kernel NULL pointer dereference; IP:
[a007e3c6] ips_detect_cpu+0x76/0x1d0 [intel_ips]
https://bugs.launchpad.net/bugs/648631
You received this bug notification because you are a member of
** Description changed:
=== Problem ===
- From the Maverick 2.6.35-16 kernel and onward, X does not load and the
computer boots to a tty login prompt.
+ From the Maverick 2.6.35-17 kernel and onward, the INTEL_IPS config option
was enabled to fix Bug 601057. Here, the intel_ips module causes
Thank you for taking the time to narrow down the cause of this bug. I've
marked the bug as ready to be viewed by a developer, so they'll continue
the debugging process once they get a chance.
--
Kernel Oops - unable to handle kernel NULL pointer dereference; IP:
[a007e3c6]
You're welcome. And thanks to you too for the help!
--
Kernel Oops - unable to handle kernel NULL pointer dereference; IP:
[a007e3c6] ips_detect_cpu+0x76/0x1d0 [intel_ips]
https://bugs.launchpad.net/bugs/648631
You received this bug notification because you are a member of Ubuntu
Bugs,
I guess blacklisting the module isn't enough, then?
(I've never compiled a kernel before, I'll do so later on if needed though)
--
Kernel Oops - unable to handle kernel NULL pointer dereference; IP:
[a007e3c6] ips_detect_cpu+0x76/0x1d0 [intel_ips]
https://bugs.launchpad.net/bugs/648631
Blacklisting it is fine too.
--
Kernel Oops - unable to handle kernel NULL pointer dereference; IP:
[a007e3c6] ips_detect_cpu+0x76/0x1d0 [intel_ips]
https://bugs.launchpad.net/bugs/648631
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Well, the kernel 2.6.35-22 booted with no noticeable issues with
intel_ips blacklisted.
--
Kernel Oops - unable to handle kernel NULL pointer dereference; IP:
[a007e3c6] ips_detect_cpu+0x76/0x1d0 [intel_ips]
https://bugs.launchpad.net/bugs/648631
You received this bug notification
** Attachment added: dmesg.2.6.35-22_working
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/648631/+attachment/1675297/+files/dmesg.2.6.35-22_working
--
Kernel Oops - unable to handle kernel NULL pointer dereference; IP:
[a007e3c6] ips_detect_cpu+0x76/0x1d0 [intel_ips]
https
Which kernel do you want me to attach the output of?
2.6.35-22.
--
Kernel Oops - unable to handle kernel NULL pointer dereference; IP:
[a007e3c6] ips_detect_cpu+0x76/0x1d0 [intel_ips]
https://bugs.launchpad.net/bugs/648631
You received this bug notification because you are a member of
** Attachment added: lspci.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/648631/+attachment/1673523/+files/lspci.txt
--
Kernel Oops - unable to handle kernel NULL pointer dereference; IP:
[a007e3c6] ips_detect_cpu+0x76/0x1d0 [intel_ips]
https://bugs.launchpad.net/bugs
** Attachment added: uname-2.6.35-22
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/648631/+attachment/1673524/+files/uname-2.6.35-22
--
Kernel Oops - unable to handle kernel NULL pointer dereference; IP:
[a007e3c6] ips_detect_cpu+0x76/0x1d0 [intel_ips]
https
Also, looking at the edited report, perhaps you didn't read one of my
comments closely enough. I don't know whether the kernel 2.6.35-16 works
because I never had it installed for some reason. I'd test it, but I did
some looking around and I can't seem to find any packages for it. I
found the
In that case, it looks like this is probably the change that introduced the bug
(from the 2.6.35-17 changelog):
* [Config] Enable INTEL_IPS
- LP: #601057
Could you compile the current Ubuntu kernel, disabling the INTEL_IPS
module and testing that?
--
Kernel Oops - unable to handle kernel
long, by the way!
** Attachment added: Xorg.0.log-2.6.36-rc6
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/648631/+attachment/1671620/+files/Xorg.0.log-2.6.36-rc6
--
Intel graphics drivers not working on new kernels on Maverick?
https://bugs.launchpad.net/bugs/648631
You received
** Attachment added: Xorg.0.log-2.6.35-3
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/648631/+attachment/1671621/+files/Xorg.0.log-2.6.35-3
--
Intel graphics drivers not working on new kernels on Maverick?
https://bugs.launchpad.net/bugs/648631
You received this bug notification
** Attachment added: Xorg.0.log-2.6.35-2
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/648631/+attachment/1671622/+files/Xorg.0.log-2.6.35-2
--
Intel graphics drivers not working on new kernels on Maverick?
https://bugs.launchpad.net/bugs/648631
You received this bug notification
** Attachment added: Xorg.0.log-2.6.35-1
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/648631/+attachment/1671623/+files/Xorg.0.log-2.6.35-1
--
Intel graphics drivers not working on new kernels on Maverick?
https://bugs.launchpad.net/bugs/648631
You received this bug notification
** Attachment added: dmesg-2.6.36-rc6
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/648631/+attachment/1671624/+files/dmesg-2.6.36-rc6
--
Intel graphics drivers not working on new kernels on Maverick?
https://bugs.launchpad.net/bugs/648631
You received this bug notification because
** Attachment added: dmesg-2.6.35-3
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/648631/+attachment/1671625/+files/dmesg-2.6.35-3
--
Intel graphics drivers not working on new kernels on Maverick?
https://bugs.launchpad.net/bugs/648631
You received this bug notification because you
** Attachment added: dmesg-2.6.35-2
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/648631/+attachment/1671630/+files/dmesg-2.6.35-2
--
Intel graphics drivers not working on new kernels on Maverick?
https://bugs.launchpad.net/bugs/648631
You received this bug notification because you
Is there a method for submitting more than one attachment at once,
anyway? I couldn't figure one out, at least..
** Attachment added: dmesg-2.6.35-1
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/648631/+attachment/1671632/+files/dmesg-2.6.35-1
--
Intel graphics drivers not working
Excellent, thank you.
Please also test the current Ubuntu kernel (2.6.35-22 at the moment) by
just upgrading your system (sudo apt-get update sudo apt-get
upgrade). This will tell us whether or not this has already been fixed
in the more recent kernels shipped with Ubuntu. (They might be held
I have already tested it, and it doesn't work either.
--
Intel graphics drivers not working on new kernels on Maverick?
https://bugs.launchpad.net/bugs/648631
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Tags removed: needs-upstream-testing
--
Intel graphics drivers not working on new kernels on Maverick?
https://bugs.launchpad.net/bugs/648631
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Please attach dmesg and Xorg.0.log for the -22 kernel then please.
--
Intel graphics drivers not working on new kernels on Maverick?
https://bugs.launchpad.net/bugs/648631
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: dmesg.2.6.35-22
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/648631/+attachment/1671972/+files/dmesg.2.6.35-22
--
Intel graphics drivers not working on new kernels on Maverick?
https://bugs.launchpad.net/bugs/648631
You received this bug notification because you
Leaving for today by the way, I'll submit more information if needed
tomorrow.
** Attachment added: Xorg.0.log-2.6.35-22
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/648631/+attachment/1671973/+files/Xorg.0.log-2.6.35-22
--
Intel graphics drivers not working on new kernels
Please also attach lspci -vvnn lspci.txt.
--
Intel graphics drivers not working on new kernels on Maverick?
https://bugs.launchpad.net/bugs/648631
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Description changed:
+ === Problem ===
+ From the Maverick 2.6.35-16 kernel and onward, X does not load and the
computer boots to a tty login prompt.
+
+ === dmesg (2.6.35-22.33) ===
+ (snip)
+ [ 20.162308] intel ips :00:1f.6: No CPUID match found.
+ [ 20.162319] BUG: unable to
Please also attach the output of 'uname -a'.
--
Kernel Oops - unable to handle kernel NULL pointer dereference; IP:
[a007e3c6] ips_detect_cpu+0x76/0x1d0 [intel_ips]
https://bugs.launchpad.net/bugs/648631
You received this bug notification because you are a member of Ubuntu
Bugs, which
Which kernel do you want me to attach the output of? All of the ones I've
tested?
Two other observations which I probably should've mentioned before, I'm not
sure if they're related or not:
I also have this bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/642421
It doesn't actually
No, I wasn't trying to click it. I did understand how to use a link with
that browser, it just didn't seem to think the Continue button was a
link at all. (Other links worked fine.) I think it may be related to the
Continue button being different from Firefox too (I can't see where does
it lead
on Firefox, even.
--
Intel graphics drivers not working on new kernels on Maverick?
https://bugs.launchpad.net/bugs/648631
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Were you trying to click it? You have to arrow down and highlight the
link and then hit Enter.
If it actually doesn't work, only attaching dmesg from the current
maverick kernel will suffice for an apport-collect.
** Tags added: kernel-graphics
--
Intel graphics drivers not working on new
Actually, now that I think about it, it would be helpful for you to
attach both dmesg and /var/log/Xorg.0.log for each of the kernels you
test.
--
Intel graphics drivers not working on new kernels on Maverick?
https://bugs.launchpad.net/bugs/648631
You received this bug notification because you
I ran into an unrelated problem yesterday trying to run apport-collect to get
the information you requested.
Upon running it, it opened up a text-only web browser and took me to the
launchpad login page. The problem was, the Continue button didn't work at all
using the browser, it didn't even
Ah, maybe I wasn't clear enough. The -15 ḱernel didn't introduce the
bug, as that kernel works perfectly. It's only the newer ones than that
not working. Either way, I will run these tests and report back later.
--
Intel graphics drivers not working on new kernels on Maverick?
Ah, I see what you meant now, sorry.
The 2.6.35-16 kernel rebased to the 2.6.35.2 mainline kernel, so the
same logic applies, you just have to test the mainline 2.6.35.1 and
2.6.35.2 kernels instead of 2.6.35 vs. 2.6.35.1 for the presence of the
bug (and of course still do everything else in my
To my untrained eye, the dmesg log in my report shows that *something*
is crashing at bootup (starting at line 765) which isn't happening on
the kernels that are working just fine. I'd bet that's related.
--
Intel graphics drivers not working on new kernels on Maverick?
** Package changed: xserver-xorg-video-intel (Ubuntu) = linux (Ubuntu)
--
Intel graphics drivers not working on new kernels on Maverick?
https://bugs.launchpad.net/bugs/648631
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Please purge the xorg-edgers PPA so you can get a cleaner debugging
environment (default Maverick packages).
Please upgrade your system, since there's a chance that this bug might
have already been fixed in a more recent kernel. At the text console,
login, and then run sudo apt-get update sudo
Public bug reported:
Binary package hint: xserver-xorg-video-intel
Basically, on Maverick, X fails to start properly for me on newer
kernels. Kernels up to 2.6.35-15 work just fine, but the later ones
don't. While booting, I get into a terminal login. If I run startx from
there, it complains
** Tags added: edgers
** Tags added: maverick
--
Intel graphics drivers not working on new kernels on Maverick?
https://bugs.launchpad.net/bugs/648631
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
65 matches
Mail list logo
