Bug#404950: Installation Report [mips] [rc1] [Failure] SWARM (Broadcom BCM91250a)
On Fri, Dec 29, 2006 at 04:09:44PM +0100, Karsten Merker wrote:
[d-i etch rc1 on SWARM/BCM91250a (mips/big-endian mode)]
> In the step "detecting hard drives" a reproducible kernel panic
> occurs (log follows below).
> RC1 uses a 2.6.17 kernel. Not sure whether this is relevant in
> this case, but according to the git commit logs there have been
> changes to the SWARM IDE code in the Linux/MIPS tree with regard
> to 2.6.17 and 2.6.18 in November/December 2006.
Further investigation has shown that the problem seems to be
caused by an add-on PCI-card with an IDE controller based on
the ITE IT8212 chipset and not by the onboard IDE controller.
With the card removed, the kernel panic does not occur.
Additional observations during the installation
In the step "Detecting disks and all other hardware" another
error gets displayed: "Error while running 'modprobe -v
amd74xx'", but it does not cause any further problems. Dmesg
reveals that the module loader cannot resolve a kernel symbol:
"amd74xx: Unknown symbol pci_get_legacy_ide_irq". It looks
like this issue is already fixed upstream in the Linux/MIPS
git repository, cf.
In the partitioner I chose manual partitioning as there were
existing partitions that needed to be kept. Partition table
layout is MS-DOS style with the first partition being the
bootloader (sibyl) partition.
Partition layout was
hda1: 8,2MB sibyl (bootloader partition)
hda2: 98,7MB ext3 /boot
hda3: 20,0GB ext3 /
for a screenshot)
What makes me wonder is the text of the messages in the next two steps:
"The following partitions are going to be formatted:
partition #3 of IDE1 master, partition # (hda) as ext3
partition #7 of IDE1 master, partition # (hda) as ext3
Write the changes to disk?"
Creating ext3 file system for / in partition #3 of IDE1 master,
partition # (hda)..."
The underlined part looks strange to me, I assume this
is not the intended output at this point? For the original
screen layout please see
The rest of the installation ran ok up to the reboot.
When trying to start the installed system, sibyl, the bootloader,
loads kernel and initrd from the harddisk, but the kernel freezes
immediately. This seems to be a problem with the installed
2.6.18 kernel. It is the same effect as in bug number #404951.
Nach Paragraph 28 Abs. 3 Bundesdatenschutzgesetz widerspreche ich der Nutzung
oder Uebermittlung meiner Daten fuer Werbezwecke oder fuer die Markt- oder