** Branch linked: lp:ubuntu/quantal-proposed/linux-lowlatency
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1022351
Title:
BUG: unable to handle kernel NULL pointer dereference at
This bug was fixed in the package linux - 3.5.0-7.7
---
linux (3.5.0-7.7) quantal-proposed; urgency=low
[ Andy Whitcroft ]
* [Config] CONFIG_X86_POWERNOW_K6=m
* [Config] CONFIG_X86_POWERNOW_K7=m
* [Config] CONFIG_X86_LONGHAUL=m
* [Config] CONFIG_X86_LONGRUN=m
* [Config]
Pushed to the Quantal kernel git repo. I'll also submit this to
upstream stable. Thanks.
** Changed in: linux (Ubuntu Quantal)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: linux (Ubuntu Quantal)
Importance: Medium
Status: Triaged
** Changed in: linux (Ubuntu Quantal)
Status: Triaged = In Progress
** Changed in: linux (Ubuntu Quantal)
Assignee: (unassigned) = Leann Ogasawara (leannogasawara)
--
You received this bug
Hi Leon,
I've posted a Quantal test kernel with the upstream patch applied.
Could you give it a test and let me know your results?
http://people.canonical.com/~ogasawara/lp1022351/amd64/
Note: Please be sure to install both the linux-image and linux-image-
extra packages when testing. Thanks.
This is the result of a quick test run in Ubuntu based Mint 13. I did
get some errors during installation, something about driver modules. I
will include the actual error when I test with a Quantal installation,
should be within the hour.
** Attachment added: Mint 13 (ubuntu based) dmesg
I'm not sure what the mint errors were, I suspect it may have been
related to using the fglrx-beta-legacy driver, I didn't expect it to
work with the 3.5 kernel anyway. But it did install without errors on my
Ubuntu installation, and the effected wireless device and everything
else that I can tell
Not fixed in 3.5, upstream dropped the ball on this one, which means not
suitable for any embedded devices which use the effected hardware or
where the hardware is not removable since the bug hinders the ability to
shutdown, reboot, or even use root access.
--
You received this bug notification
Fix not applied to RC7. Upstream aware.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1022351
Title:
BUG: unable to handle kernel NULL pointer dereference at
0080
To manage
bug is still in RC7
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1022351
Title:
BUG: unable to handle kernel NULL pointer dereference at
0080
To manage notifications about this bug
** Changed in: linux
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/1022351
Title:
BUG: unable to handle kernel NULL pointer dereference at
0080
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 at bugzilla.kernel.org [1]? That will allow the upstream
Developers to examine the issue, and may provide a quicker resolution to
the bug.
If you
** Bug watch added: Linux Kernel Bug Tracker #44411
http://bugzilla.kernel.org/show_bug.cgi?id=44411
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=44411
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of
Upstream bug report filed (stretching the boundaries of my noob skills)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1022351
Title:
BUG: unable to handle kernel NULL pointer dereference at
** Changed in: linux
Status: Unknown = Confirmed
** Changed in: linux
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1022351
Title:
BUG: unable to handle
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.5kernel[0] (Not a kernel in the daily directory) and install both the
linux-image and linux-image-extra .deb packages.
Once you've tested the
The issue still remains. Since the initial report was done using a live
USB session, I did an install on a spare hard drive so I could try the
latest mainline kernel, RC6, but the error still remains. In addition to
sudo hanging when this issue is present, shutdown also fails. With the
wifi card
** Attachment added: dmesg.log
https://bugs.launchpad.net/bugs/1022351/+attachment/3216899/+files/dmesg.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1022351
Title:
BUG: unable to handle
** Attachment added: lspci -vvnn without sudo
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1022351/+attachment/3216900/+files/lspci-vvnn.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: uname-a.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1022351/+attachment/3216901/+files/uname-a.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1022351
Title:
** Changed in: linux (Ubuntu)
Status: New = Confirmed
** Tags added: quantal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1022351
Title:
BUG: unable to handle kernel NULL pointer
Looks wifi related:
[ 26.171255] cfg80211: Updating information on frequency 2484 MHz for a 20
MHz width channel with regulatory rule:
[ 26.171257] cfg80211: 2474000 KHz - 2494000 KHz @ 2 KHz), (600 mBi, 2000
mBm)
[ 26.246994] ieee80211 phy0: Selected rate control algorithm
The attached file here is the output of lspci-vnn.log from an almost
identical machine (same motherboard and network card) running kernel
3.2. The issue goes away when the card is not present.
The card is the ASUSTeK Computer Inc. WL-130g, which was packaged with
the A8V Deluxe.
From a the
23 matches
Mail list logo
