Using Karmic and mostly after reading Liferea feeds, crash icon in notification
area. Last update was on Oct 16 around 1900 EDT.
Hopes this helps. Karmic is awesome!!
--
BUG in kernel 2.6.24-7? BUG: unable to handle kernel NULL pointer dereference
at virtual address 0001 Based on question
Il solved my problems by changing my grub boot line with:
# defoptions=vga=791 pnpbios=off acpi=force pci=noacpi locale=fr_FR
elevator=cfq splash
--
BUG in kernel 2.6.24-7? BUG: unable to handle kernel NULL pointer dereference
at virtual address 0001 Based on question #24954
My problem had been solved with the last kernel update, linux (2.6.24-15.26)
See (LP: #207014).
So, this BUG is not a Invalid one, but a 'Fix released' one!!
Yes, some of my hardware has change, and it was the battery that get
into a corrupted one.
coubi64, if the current state don't solve
To further reference http://bugzilla.kernel.org/show_bug.cgi?id=10339#c15
that discuss this bug.
--
BUG in kernel 2.6.24-7? BUG: unable to handle kernel NULL pointer dereference
at virtual address 0001 Based on question #24954
https://bugs.launchpad.net/bugs/191721
You received this bug
coubi64, is 'acpi=off' a valid workaround?
Do you any progress?
My system still's unstable. I will try make a complete report to find help, in
order to find the bug or the damage hardware piece?
(as you had read, my problem just occur recently. So I believe in some hardware
issue.. )
Hi !!!
I have the same problem.
I'm running
[0.00] Linux version 2.6.24-15-generic ([EMAIL PROTECTED]) (gcc version
4.2.3 (Ubuntu 4.2.3-2ubuntu7)) #1 SMP Tue Apr 8 00:33:51 UTC 2008 (Ubuntu
2.6.24-15.27-generic)
and see crash message during the boot every time i start my Ubuntu.
Same problem for me. See my dmesg
** Attachment added: dmesg
http://launchpadlibrarian.net/12924831/bug.txt
--
BUG in kernel 2.6.24-7? BUG: unable to handle kernel NULL pointer dereference
at virtual address 0001 Based on question #24954
https://bugs.launchpad.net/bugs/191721
You
Bhavani, thanks for the alert at 'answers' section.
(Well, at this moment my laptop doesn't work.
The same, kernel panic (*1) issue arrives. So, I just see the email running)
Colin, I run memtes96++, for at least 12 hours. None errors. 27 tests
successful.
However, I believe that some hardware
Heya guys..
This was converted from a question to a bug.. (See the Related questions
panel) and please ask the question owner to provide more information...
Bhavani Shankar.
--
BUG in kernel 2.6.24-7? BUG: unable to handle kernel NULL pointer dereference
at virtual address 0001 Based on
Was the error: BUG: soft lockup - CPU#0 stuck for 11s ?
Strange, looking at the source code, it appears that you should probably
also have a dump of the processor registers and a stack dump too.
Without this information it is almost impossible to work out why the
lockup is occurring. A soft
Hi,
Thanks for the logs.
Any chance of seeing what the kernel panic message was? - even a digital
photo of the console when it panics is helpful. It is a little worrying
that your laptop is producing kernel panics now from the LiveCD. This
sounds more like some hardware problem to me than a
Some missing parts at the text:
(*1) = sometimes, the error is something like CPU#0 didn't answer for 11
seconds
Correction at text:
They aren't load at boot time and the system boot up successful, and Gnome just
report that he couldn't initialize 'HAL'. 'Network Manager', at least the
applet
Thanks for the help.
Well, let's talk with the machine.
All the steps (I'm writing this, on a second machine, at the same time I
perform the refered steps):
=Boot into recovery mode.
=manually running dbus and hal ... [OK]
Hmm, the system still running. Great!
=apt-get dist-upgrade
(hmm, getting
OK, Let's see how this works out with 2.6.24-8.
The fact that the LiveCD didn't work originally, and on your lest test
it does work indicates there may be some hardware instability. It
concerns me that the your are seeing 30 second and 20 second delays
during ATA configuration. Does this always
With the installed system, Hardy it happen always.
With LiveCD, ubuntu 7.10, that now is booting correctly, ATA configuration is
doing instantly.
Well, not any more, crash back again.
ATA configuration runs well, and as I said is doing instantly, but when loading
hal the system crash.
Let's
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
--
BUG in kernel 2.6.24-7? BUG: unable to handle kernel NULL pointer dereference
at virtual address 0001 Based on question #24954
https://bugs.launchpad.net/bugs/191721
You received this bug notification because you are a
If you see this error one should also see a stack dump too - if so, can you
send a dmesg log of this.
Well, now I had get one.
Photo in the attachment.
** Attachment added: HardyCrash-5.cpu-stuck-for-11s.tar.bz2
http://launchpadlibrarian.net/12135212/HardyCrash-5.cpu-stuck-for-11s.tar.bz2
I suggest first try booting with the acpi=off kernel parameter and
seeing if this helps.
with the acpi=off:
Is booting correctly.
Confirmed, again and again (5 times).
ATA configuration is doing instantly.
dmesg file, follow in attachment.
Without acpi=off is crashing like reported above.
ATA
It it was useful, follow the dmidecode log.
I get it, in Hardy, with the boot option acpi=off.
** Attachment added: dmidecode.log
http://launchpadlibrarian.net/12154030/dmidecode.log
--
BUG in kernel 2.6.24-7? BUG: unable to handle kernel NULL pointer dereference
at virtual address
It seems then that the problem is a buggy DSDT with your machine, which
should be fixed.
I had a look for any ACPI DSDT updates that one could apply to your
machine:
http://acpi.sourceforge.net/dsdt/view.php?manufacturer=ACERname=Aspire+1694WLMi
However, it seems that for your version, the 3A45
That BIOS version was installed, when the laptop went into warranty.
Isn't yet available at the download site,
http://support.acer-euro.com/drivers/notebook/as_1690_ddr2.html .
For now, I will work with acpi=off :(
Do you have any idea what could change, at the BIOS, at the hardware or
We have concluded that this is not a kernel bug, but a broken DSDT. I
suggest contacting the manufacturer and requesting them to fix the DSDT.
** Changed in: linux (Ubuntu)
Status: In Progress = Invalid
--
BUG in kernel 2.6.24-7? BUG: unable to handle kernel NULL pointer dereference
at
Hi Bhavani,
I've traced this through to the slub memory allocator, the problem
occurs when slab_alloc() is getting an incorrect return value of 1 from
get_cpu_slab(). This indicates the slub allocator is getting corrupted
somehow, but with little more evidence, it is hard to determine what
** Changed in: linux (Ubuntu)
Assignee: Ubuntu Kernel Team (ubuntu-kernel-team) = Colin King
(colin-king)
--
BUG in kernel 2.6.24-7? BUG: unable to handle kernel NULL pointer dereference
at virtual address 0001 Based on question #24954
https://bugs.launchpad.net/bugs/191721
You
Hi Bhavani,
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Per the kernel team's bug policy, can you please attach
the following information. Please be sure to attach each file as a
separate attachment.
* uname -a uname-a.log
* cat /proc/version_signature
** Changed in: linux (Ubuntu)
Status: Incomplete = In Progress
--
BUG in kernel 2.6.24-7? BUG: unable to handle kernel NULL pointer dereference
at virtual address 0001 Based on question #24954
https://bugs.launchpad.net/bugs/191721
You received this bug notification because you are a
Hi Bhavani,
Just curious if you are able to readily reproduce this Ooops? If so,
care to provide the steps to reproduce? Thanks.
** Changed in: linux (Ubuntu)
Status: New = Incomplete
--
BUG in kernel 2.6.24-7? BUG: unable to handle kernel NULL pointer dereference
at virtual address
Also care to try updating to the 2.6.24-8 kernel? Thanks.
--
BUG in kernel 2.6.24-7? BUG: unable to handle kernel NULL pointer dereference
at virtual address 0001 Based on question #24954
https://bugs.launchpad.net/bugs/191721
You received this bug notification because you are a member of
Thank you for taking the time to report this issue and helping to improve
Ubuntu!
This report was not reported against a specific package. I have assigned the
correct package now. Please try to file future bug reports against the right
packages. You can learn to find the right package at
Thanks for the orientation.
By the way, the full dmesg log follow in the attachment.
** Attachment added: Full dmesg with BUG report in it
http://launchpadlibrarian.net/11961233/dmesg.13.02.08_21.45h.log
--
BUG in kernel 2.6.24-7? BUG: unable to handle kernel NULL pointer dereference
at
30 matches
Mail list logo
