boot fails: does not detect hda any more (port conflict?)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
initramfs-tools (Ubuntu) |
Fix Released
|
High
|
Ben Collins | ||
linux-source-2.6.20 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: linux-source-2.6.20
After today's dist-upgrade the kernel (2.6.20-2.2) does not boot any more because it cannot find the root fs (/dev/hda2). However, the only boot-related package upgrade today was udev, the very same kernel already booted fine for me this morning.
Booting current feisty with 2.6.17 works fine, dmesg says:
[ 28.035156] hda: max request size: 128KiB
[ 28.045570] hda: Host Protected Area detected.
[ 28.045573] current capacity is 25408559 sectors (13009 MB)
[ 28.045574] native capacity is 25410672 sectors (13010 MB)
[ 28.080730] hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
[ 28.080734] hda: task_no_data_intr: error=0x04 { DriveStatusError }
[ 28.080738] ide: failed opcode was: 0xf9
[ 28.080749] hda: 25408559 sectors (13009 MB) w/512KiB Cache, CHS=25206/16/63, UDMA(66)
[ 28.080755] hda: cache flushes not supported
[ 28.080798] hda: hda1 hda2
[ 28.108631] hdc: max request size: 512KiB
The task_no_data_intr error messages always appear and seem to be harmless. It detects hda1 and hda2 just fine (just as 2.6.20-2.2 did this morning).
Now, when I boot 2.6.20, I get:
ide0: I/O resource 0x3F6-0x3F6 not free.
hda: ERROR, PORTS ALREADY IN USE
ide0 at 0x1f0-0x1f7,0x3f6 on irq14
ide1: I/O resource 0x376-0x376 not free.
ide1: ports already in use, skipping probe
register_blkdev: cannot get major 3 for ide0
a little later, the partitions on hdc (1 to 4) are detected just fine, but not hda's. Thus booting gets stuck in the initramfs because the root partition doesn't exist.
Changed in linux-source-2.6.20: | |
status: | Unconfirmed → Rejected |
tags: | added: iso-testing |
This is the output of packages. txt
$ grep '2006-12-22.*status installed' /var/log/dpkg.log | cut -f 5 -d\ |sort -u > /tmp/upgraded-
just in case someone spots another package that could be responsible for this breakage.