*** This bug is a duplicate of bug 63134 ***
As far as I can see this is a duplicate of bug 63134 (or maybe the other
way round as this one is older, but the other bug has a patch attached
so I'm going this way).
This bug has quite a few people posting in it, so I had some problems
identifying t
I am having the exact same problem as original poster, whenever I try to
boot the edgy eft live cd. I have AMD Barton 2600+ on MSI KT4 mobo,
which uses VIA chipset. I think this definately has to do with VIA. I
have tried ACPI =force, ACPI=off, pnpbios=off, and various combinations
of these flag
I get the same error as the picture shown and cannot even boot the
system, except the number on the left is a bit higher. I am also running
on a VIA chipset, so these bugs may be related.
https://launchpad.net/distros/ubuntu/+source/linux-
source-2.6.17/+bug/65710
--
[edgy] kernel panic after las
2.6.17-10-386 appears to work (was using the generic kernel before)
without need for any extra boot parameters.
--
[edgy] kernel panic after last update
https://launchpad.net/bugs/61848
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bug
acpi=force never worked under the older kernel (2.6.15) for me, and
doesn't with the newer one, either. noapic doesn't do much on my
hardware, either and nor does pnpbios=off. Still no joy as of 22nd
October.
--
[edgy] kernel panic after last update
https://launchpad.net/bugs/61848
--
ubuntu-bu
noapic made usb work!!
so, for me optional parameters are now "noapic acpi=force"
HTH
--
[edgy] kernel panic after last update
https://launchpad.net/bugs/61848
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
my dmesg. it may help to fix both this issue (that looks really acpi
related). booted with acpi=force (without that, it will just panic)
** Attachment added: "nowhereman's dmesg"
http://librarian.launchpad.net/4886667/dmesg.txt
--
[edgy] kernel panic after last update
https://launchpad.net/bu
Ok, there's a lot of cruft in this bug. People, please don't put "me
too's" into a bug report about a crash just because you have a crash
too. Unless your traceback is the same, then you have a different bug.
** Changed in: linux-source-2.6.17 (Ubuntu)
Status: Fix Released => Confirmed
--
I'm sorry, Ben, but this bug is not related to amd64-agp; as I already
said, mine is not an amd64
--
[edgy] kernel panic after last update
https://launchpad.net/bugs/61848
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Ben, The problem is not fixed here, should I file a new bug?
--
[edgy] kernel panic after last update
https://launchpad.net/bugs/61848
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
The initial problem of amd64-agp is fixed. So please open another bug
regarding the USB issues.
** Changed in: linux-source-2.6.17 (Ubuntu)
Status: Unconfirmed => Fix Released
--
[edgy] kernel panic after last update
https://launchpad.net/bugs/61848
--
ubuntu-bugs mailing list
ubuntu-bu
did you try to unplug and plug them back after the boot have finished?
--
[edgy] kernel panic after last update
https://launchpad.net/bugs/61848
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I confirm that if you plug them before the boot hey may work (my mouse
however is choppy), if you plug them when system is up, they're not seen
--
[edgy] kernel panic after last update
https://launchpad.net/bugs/61848
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu
My USB devices are working flawlessly using acpi=force.
--
[edgy] kernel panic after last update
https://launchpad.net/bugs/61848
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
IMPORTANT! confirming that now acpi=force is enough to boot (no pnpbios=off)
but--
NEW ISSUE! are you having issues with usb devices? I DO! They're not
activated, usb ports look dead! with -7 they work!
please confirm
--
[edgy] kernel panic after last update
https://launchpad.net/bugs/61848
--
Well it seems most of us (all?) have a VIA chipset, it could have some
relation with the kernel panic, couldn't it?
Sslaxx and me can't boot even with the flags, I noticied his chipset is
KM400, mine is KT400, could be a particular problem...
--
[edgy] kernel panic after last update
https://laun
@Quim Calpe,
I have a VIA chipset as well...
--
[edgy] kernel panic after last update
https://launchpad.net/bugs/61848
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
oh, maybe I have an Intel; we probably have different BIOSes, too; as
I've already said, mine is this "Insyde Software MobilePro BIOS ver
4.20.10" ...
--
[edgy] kernel panic after last update
https://launchpad.net/bugs/61848
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists
Maybe related to AMD XP processors then (the flags issue)?
--
[edgy] kernel panic after last update
https://launchpad.net/bugs/61848
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
@Quim Calpe
my system has a Via chipset, too, but the flags work :/
--
[edgy] kernel panic after last update
https://launchpad.net/bugs/61848
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Forgot to add my system specs: Athlon XP 2000+ on an Elitegroup K7VTA3
(KT333 Northbridge, VT8235 Southbridge)
--
[edgy] kernel panic after last update
https://launchpad.net/bugs/61848
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
@Adrian Harvey: As I reported above, I'm in the same situation as
Sslaxx, and I can confirm from the very beginning of the bug, it's the
same, at least the core dump is exactly the same. Those flags doesn't
work here...
@Sslaxx: I noticed you probably have a Via chipset, like me, it could be
the
Same problem here. Kernel panic after acpi_hw_low_level_read,
"acpi=force" lets me boot without problems.
--
[edgy] kernel panic after last update
https://launchpad.net/bugs/61848
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Yep, same here. Actually, in my case "acpi=force" is enough to boot..
--
[edgy] kernel panic after last update
https://launchpad.net/bugs/61848
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
still panic'ing if disabling those two options, even with the latest
updates
--
[edgy] kernel panic after last update
https://launchpad.net/bugs/61848
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
SSlaxx,
Can you confirm you have the same bug as the rest of us, ie: the kernel panics
right after an acpi_hw_low_level_read?
--
[edgy] kernel panic after last update
https://launchpad.net/bugs/61848
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/list
Tried acpi=off and force, with pnpbios=off, nolapic and noapic
options... nothing works, 2.6.17-31 does not boot under any
circumstances on this machine.
VT8378 (KM400/A) motherboard. Athlon XP 2000+.
--
[edgy] kernel panic after last update
https://launchpad.net/bugs/61848
--
ubuntu-bugs mail
Yeah, I'm wondering too, what should be done, to make this BUG confirmed
and fixed...
--
[edgy] kernel panic after last update
https://launchpad.net/bugs/61848
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I have also tried it with the "pnpbios=off acpi=force" and that does let
my system boot. Clearly a bug though.
I think the next step is for this bug to be marked confirmed. Who does
that, and what information do they need to reassure themselves that it's
a real bug? It sure seems real from here
@NoWhereMan I finally tried your options, that is "pnpbios=off acpi=force"
It works :) I'm running the latest kernel now, that is -10.30 and it boots
wothout problems. I also tried adding only "acpi=force" and it boots as well.
But in my opinion it's still broken. I wouldn't expect any newbie edit
without those flags however kernel still panics...
--
[edgy] kernel panic after last update
https://launchpad.net/bugs/61848
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
No luck here with "pnpbios=off acpi=force" flags :-(
--
[edgy] kernel panic after last update
https://launchpad.net/bugs/61848
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
definitely looks like a pnpbios issue, i guess
--
[edgy] kernel panic after last update
https://launchpad.net/bugs/61848
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
@NoWhereMan: Perfect hint! With those two options (pnpbios=off
acpi=force) my computer finally boots a -10 kernel.
--
[edgy] kernel panic after last update
https://launchpad.net/bugs/61848
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-
have you tried the kernel options i've posted above ?
--
[edgy] kernel panic after last update
https://launchpad.net/bugs/61848
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I have similar problems as Martin above. After I switched to edgy beta, none of
the 2.6.17 kernels worked for me (including -10). Kernel panic each time, with
things like pci_write and some 'acpi read' stuff at the end. I'm using amd
athlon 2500, abit kv7 motherboard, ati 9500
2.6.15-27-k7 work
adding pnpbios=off acpi=force to kernel options in grub made me boot
with -10 kernel !
ps: the usplash bar is white at the top and brown at the bottom; is this the
correct color?
--
[edgy] kernel panic after last update
https://launchpad.net/bugs/61848
--
ubuntu-bugs mailing list
ubuntu-bugs
I have a Via EPIA board with a C3 processor and Edgy fails to boot with
almost the same message. The call trace contains
pci_write
pci_bus_write_config_byte
pci_fixup_device
init
init
and finally
<0> Kernel panic - not syncing: Attempted to kill init!
I could make a screen
I get the same thing [as Nowhereman] after upgrading from Breezy. Can
still start up by selecting the old (Breezy) kernel from grub. Has
never required any special settings previously, and changing some of the
BIOS options mentioned (I can't find the PIC/APIC one in my menus)
makes no difference.
** This bug is no longer a duplicate of bug 61898
Kernel Panic - agp_amd64_init
--
[edgy] kernel panic after last update
https://launchpad.net/bugs/61848
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
*** This bug is a duplicate of bug 61898 ***
Me neither, and I'll wait Ben or any Kernel Team member to do so, as at
the end they are the devs and the ones who know exactly what's happening
here, and they marked it as dup...
On the other hand, our machines are still unbootable!
--
[edgy] kernel
*** This bug is a duplicate of bug 61898 ***
click "mark as duplicate" (upper left corner) and delete the reference to
61898; that should do.
I won't do it myself as I'm not a member of the team :)
--
[edgy] kernel panic after last update
https://launchpad.net/bugs/61848
--
ubuntu-bugs mailin
*** This bug is a duplicate of bug 61898 ***
Kernel 2.6.17-10 has the same crash as -8 and -9 as guessed here this
bug IS NOT a duplicate of 61898. In fact the attached screenshot show a
rather different core dump...
Ben should we file a new one or the bug can be unmarked as duplicate?
--
[edgy
*** This bug is a duplicate of bug 61898 ***
no luck with -10 update
again, I DON'T have any amd64 nor amd processor
--
[edgy] kernel panic after last update
https://launchpad.net/bugs/61848
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubun
*** This bug is a duplicate of bug 61898 ***
** This bug has been marked a duplicate of bug 61898
Kernel Panic - agp_amd64_init
--
[edgy] kernel panic after last update
https://launchpad.net/bugs/61848
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman
I get the same thing when i start up with the 2.6.17-9-generic kernel, but with
the -7. I do not have the -8 kernel to test whether it works or not.
My processor is an AMD Athlon 64 3400+
--
[edgy] kernel panic after last update
https://launchpad.net/bugs/61848
--
ubuntu-bugs mailing list
ubun
Well I just found something... I have to dualboot Windows XP sometimes,
and with this workaround (setting the interrupt mode changed to PIC),
Windows XP doesn't boot anymore...
Still not sure if it's good or bad ;-)
--
[edgy] kernel panic after last update
https://launchpad.net/bugs/61848
--
u
@koolatron: The crash you describe is closer to the crash people is
reporting in bug https://launchpad.net/bugs/61877 and seems related to
AMD64 machines.
@NoWhereMan: The workaround didn't work for me, but one thing did: I
changed in BIOS the interrupt mode from APIC to PIC, the crash was the
sam
Transcribed screen trash on failed boot:
[ 19.103815] CS: 0010 DS: 0018 ES: 0018 CR0: 8005003b
[ 19.103858] CR2: 0008 CR3: 00201000 CR4: 06e0
[ 19.103906] Process swapper (pid: 1, threadinfo 81003f1c8000, task
81003f1c7510)
[ 19.103986] St
Same kernel panic here, on an AMD64 single-core processor, Gigabyte
K8U-939 motherboard.
kernel 2.6.17-7 boots, -9 panics leaving me with much the same error as
NoWhereMan. I'll scrounge up a screenshot and post it here tonight;
failing that, I'll just give my fingers a workout and transcribe it.
possbible workaround?
http://ubuntuforums.org/showthread.php?p=1542776#post1542776
damn, I don't have that option on my BIOS (and that's a NEW laptop!)!!
"Insyde Software MobilePro BIOS ver 4.20.10"
--
[edgy] kernel panic after last update
https://launchpad.net/bugs/61848
--
ubuntu-bugs maili
@Earthfall: I think your problem is more related to bug
https://launchpad.net/bugs/61877
--
[edgy] kernel panic after last update
https://launchpad.net/bugs/61848
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I am running my AMD64 desktop system with edge and the recent update of
2.6.17-9-generic gave me the kernel panic. 2.6.17-8-generic was fine.
--
[edgy] kernel panic after last update
https://launchpad.net/bugs/61848
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.c
** Changed in: Ubuntu
Sourcepackagename: None => linux-source-2.6.17
--
[edgy] kernel panic after last update
https://launchpad.net/bugs/61848
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
well, just wondering if that could be the cause... my system never
booted up without the acpi=off flag, but Ubuntu installation put
"automagically" the flag in defoptions of grub's menu.lst, so no problem
in that regard.
--
[edgy] kernel panic after last update
https://launchpad.net/bugs/61848
-
actually -7 works with both acpi=force or without it, it is disabled as
a default, as a for safety reasons by the kernel. I've left it off, as
forcing revealed a lot of debug output i was not sure about. keeping it
off require me to power off using the hardware button in the end of the
shutdown pro
Same here, but with a AMD XP 2200+. The same happened with
2.6.17-8-generic kernel, I just waited for the new kernel
update(2.6.17-9-generic), but it crashes the same way.
Kernel linux-image-2.6.17-7-generic works fine thought...
As a side note, my motherboard (Asus K7V8-X) requires acpi=off to b
** Attachment added: "screenshot"
http://librarian.launchpad.net/4394752/Foto_092206_001.jpg
--
[edgy] kernel panic after last update
https://launchpad.net/bugs/61848
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
58 matches
Mail list logo
