Dapper Flight 5 kernel panic on boot

If I use the Flight 5 Live i386 CD the system WILL boot. And the ICplus IP1000 is recognized.

Also, I run AMD64 Hoary on this system.

On the Flight 5 i386 Live CD, the ICplus IP1000 device is found but not activated by default. If I activate it, it performs properly. Not sure why it is not activated on boot.

This is still a problem on Flight 6 Live CD AMD64. This system runs Breezy (AMD64) fine.

This is still a problem on Flight 7 Live CD AMD64.

Please try the latest daily. Some extra fixes went in after Flight 7.

Ben Collins wrote:

>Please try the latest daily. Some extra fixes went in after Flight 7.
>
>
>
The Daily is only the Install images. It does not include the Live
images. I have been using the Live CD for all of my testing and error
reporting. I will scrounge a spare HD and try an Install.

http://cdimage.ubuntulinux.org/daily/current/

Or is there a different place for the live CD daily?

Gary

Ben Collins wrote:

>Please try the latest daily. Some extra fixes went in after Flight 7.
>
>
>
I tried the daily on 9 May 2006 and it failed. It was the dapper AMD64
Install CD, not the Live CD which is what I was using before.

RIP pci_mmcfg_read+239 RSP

The traceback looks like:

init
acpi_scan_init +23
acpi_ut_acquire_mutex+58
acpi_bus_driver_init+46
pci_acpi_scan_root+55
pci_scan_child_bus+107
pci_scan_child_bus +34 -- pci_scan_bridge +401

That was the one page traceback. I can try whatever is needed to resolve
this.

First, hi all!!
I'm using kubuntu since few months on my i386 platform, it works perfectly. But i decided to buy a new pc, an HP Pavilion with athlon 64 3700+ processor, 1GB of DDR Dual channel Ram and HP motherboard (i don't know the chipset name T_T )

I tried to install the new flight7 release of kubuntu on this machine but, during the boot i have the same error of the first post! The i386 live cd works fine instead....
is it really a bug or i am not really good with linux? (i think the second answer :P)

Regards

PS: Sorry for my bad english, i'm still learning it ^^.

I loaded the 19 May daily build and it still fails. Same traceback.

I also couldn't boot off the CD with the x86_64 distribution. I worked round the problem by adding bootflags

barrier=off iommu=noforce

 I don't know if one, other or both is required.

I tried the 8 May Daily build with the bootflags barrier=off iommu=noforce
Same panic. My system does not have an AGP slot (uses PCIExpress) and has only 1GB memory. so I don't think these flags are relevant, but I tried it anyhow. The i386 live cd works. And I have run both Hoary and Warty with the AMD64 install cd successfully.

Loaded the release-candidate CD and the system still panics on booting the install CD. Same traceback

i am experiencing a similar (not sure if it's the same) problem on my notebook (HP dv8075EA). All 2.6.15 amd64 kernels (both generic and k8) that came up in dapper repository for the past 8 weeks immediately paniced on boot throwing tons of acpi errors, unless I defined "noapic" boot option. However, my self-baked 2.6.14 kernel from bpo sources works fine.

Environment:

[23:36:05] javelin:~# cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 15
model : 36
model name : AMD Turion(tm) 64 Mobile Technology ML-40
stepping : 2
cpu MHz : 795.944
cache size : 1024 KB
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext fxsr_opt lm 3dnowext 3dnow pni lahf_lm
bogomips : 1594.09
TLB size : 1024 4K pages
clflush size : 64
cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management: ts fid vid ttp tm stc

[23:36:25] javelin:~# lspci
0000:00:00.0 Host bridge: ATI Technologies Inc RS480 Host Bridge (rev 01)
0000:00:01.0 PCI bridge: ATI Technologies Inc: Unknown device 5a3f
0000:00:04.0 PCI bridge: ATI Technologies Inc: Unknown device 5a36
0000:00:13.0 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller
0000:00:13.1 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller
0000:00:13.2 USB Controller: ATI Technologies Inc IXP SB400 USB2 Host Controller
0000:00:14.0 SMBus: ATI Technologies Inc IXP SB400 SMBus Controller (rev 11)
0000:00:14.1 IDE interface: ATI Technologies Inc Standard Dual Channel PCI IDE Controller ATI
0000:00:14.3 ISA bridge: ATI Technologies Inc IXP SB400 PCI-ISA Bridge
0000:00:14.4 PCI bridge: ATI Technologies Inc IXP SB400 PCI-PCI Bridge
0000:00:14.5 Multimedia audio controller: ATI Technologies Inc IXP SB400 AC'97 Audio Controller (rev 02)
0000:00:14.6 Modem: ATI Technologies Inc ATI SB400 - AC'97 Modem Controller (rev 02)
0000:01:05.0 VGA compatible controller: ATI Technologies Inc ATI Radeon XPRESS 200M 5955 (PCIE)
0000:06:02.0 Network controller: Broadcom Corporation: Unknown device 4319 (rev 02)
0000:06:04.0 CardBus bridge: Texas Instruments PCIxx21/x515 Cardbus Controller
0000:06:04.2 FireWire (IEEE 1394): Texas Instruments OHCI Compliant IEEE 1394 Host Controller
0000:06:04.3 Mass storage controller: Texas Instruments PCIxx21 Integrated FlashMedia Controller
0000:06:04.4 0805: Texas Instruments PCI6411, PCI6421, PCI6611, PCI6621, PCI7411, PCI7421, PCI7611, PCI7621 Secure Digital (SD) Controller
0000:06:06.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)

Please tell me if you need more info. Maybe I somehow could get a webcam and take a screenshot of the core dump if you think this would help.

I tried the AMD64 Dapper release candidate CD and did 'install noapic nolapic' and it still panics with the same error.

I also have the same problem. It used to work fine until moving to the 2.6.15_something kernel. Using the kernel boot parameter "pci=nommconf" made it work for me. I heard from somebody else who also has the same problem that it has not been seen in the 2.6.17 kernel.

Reference:

http://www.ubuntuforums.org/showthread.php?t=167310

Per another comment, I tried "pci=nommconf" and it worked fine. This is with the AMD64 Dapper 6.06 Live CD.

Ok, to help fix this bug, I am going to need a full backtrace from the kernel. If this means using a digital camera to take a photo, that is fine. Please attach it to this bug report.

This bug may be fixed in the current edgy developement system. In an effort to track this bug to our latest distribution, it is being targeted for edgy.

Please confirm whether this bug exists in edgy. If not, then please re-attach all related output (e.g. dmesg, oops output) while under edgy.

Latest Edgy CD's can be downloaded from:

http://cdimage.ubuntu.com/releases/edgy/knot-1/

If this image does not boot from you, you can also download a current daily build from:

http://cdimage.ubuntu.com/daily-live/current/

Note that it may only be necessary to boot the LiveCD to see if your bug is fixed. In this case, you do not need to upgrade your installed system at all to confirm it. Certain bugs may require that you do an actual installation.

Ok, the kernel itself works for me with edgy live cd (means it doesn't panic). However, the current edgy live snapshot throws a lot of chdir errors and finally init ends with "no more processes left in this runlevel" (booting init=/bin/bash didn't work either), so I couldn't get the dmesg.

Will try to play around with it again during the weekend, maybe I can get around this chdir problem somehow and provide better info for you.

For now, I attached the panic screenshot of dapper kernel I took with my digicam. Unfortunately, it's not complete but anyway it may still help.

I loaded the Edgy AMD64 LiveCD and it worked perfectly. no issues at all.

I am including the successful dmesg as a reference.

I was having similar problems (kernel panic when trying to install) with a dual Opteron system, and actually tried every AMD/i386 version of Dapper. The 21-Sep-2006 build of Edgy appears to install fine, though.

Guido, Gary, Patrick: Does now Edgy works without problems for you?

Then I'll mark linux-source-2.6.17 (Ubuntu) as "fixed".

It works fine for me. I vote for "fixed"

gary

Am Samstag, den 17.03.2007, 16:41 +0000 schrieb Thomas Hotz:
> Guido, Gary, Patrick: Does now Edgy works without problems for you?
>
> Then I'll mark linux-source-2.6.17 (Ubuntu) as "fixed".

Edgy kernel still doesn't work for me, but the panic now only occurs
with ndiswrapper module loaded. As long as I go without it, the system
boots up and seems to run stable (enabling ndiswrapper _after_ boot
works for one or two minutes but then the system also panics). However,
with vanilla 2.6.17 build (edgy kernel config applied without changes)
it's working fine, so I still consider this to be a bug somewhere in
Ubuntu's patches.

Not sure if this really is caused by the same bug as the initially
reported problem here... I'm not a developer at all so I can only do my
best in guess and provide information... however, if you think it helps,
I can do another panic screenshot of the current edgy kernel. Besides
that, I'll check out feisty kernel as soon as beta is ready. Maybe we're
lucky and it's fixed there.

Cheers!

Guido

--
Guido Nickels | Phone: +49 (22 33) 99 40 70
Hans-Boeckler-Strasse 52-54 | Fax: +49 (22 33) 99 40 71
Germany, 50354 Huerth | Mobile: +49 (1 75) 8 85 27 87
http://www.kernel-oops.de | Freenode: nightwish

Thank you guys for the quick response.

Guido: Yes, please try Feisty Beta, when it's out. Then tell us how it works and if you still have problems. I think the best thing then would be to file a new bug. Good luck with Feisty!

> It works fine for me. I vote for "fixed".

Thanks. Please feel free to report any other bugs you find in Ubuntu.

For all the others who have problems: Please open a new bug report. Otherwise we are not able to help you.