Will Woods wrote:
G'day.
Boy, am I glad to see you here:-)
On Mar 11, 2008, at 8:32 PM, John Summerfield wrote:
Michal Jaegermann wrote:
On Tue, Mar 11, 2008 at 04:59:50PM +0900, John Summerfield wrote:
Note that the ATA buses are detected - a full transcription is here:
https://bugzilla.redhat.com/process_bug.cgi
https://bugzilla.redhat.com/show_bug.cgi?id=436099
Try again, please. (I made the same "copy-and-waste" in a hurry
mistakes in the past. :-)
I normally double-click and that doesn't stop at the "?." I am cursed
with the "swapped buttons" bug and that's been making lide difficult.
https://bugzilla.redhat.com/show_bug.cgi?id=436099
and so's the SATA DVD drive, Just not the two SATA drives.
Does the following look familiar?
Looks familiar, but I don't think it's the same. I don't get a
timeout. B'sides, mine's Intel CPU and chips.
https://bugzilla.redhat.com/show_bug.cgi?id=436591
Note also URL references mentioned in comments. What about
nvidia chips. Mine are Chipzilla.
http://lkml.org/lkml/2008/3/9/136
and other messages in the same thread? If that is the case
then maybe 'irqpoll' has a chance to alleviate the problem
at least enough to boot?
Michal
The Jones boy think it's mkinitrd. I'm sceptical, it the same works
for other kernels, but I do wish it would go away.
There were a *lot* of people who were unable to boot after we moved to
pre-release 2.6.25 kernels:
0) mkinitrd figures out what device types / modules it's dealing with by
poking around in /sys.
1) There are big changes in the layout of /sys in 2.6.25 kernels.
2) Therefore, initrds created for 2.6.25 kernels fail under certain
(common) conditions.
All that said, the modules that get loaded are the same ones loaded for
earlier kernels.
And there's the fact the .21 xen kernel has the same problem. That's got
me confused too.
So, nearly all of the "cannot find /dev/root" problems we've seen have
been mkinitrd-related. So davej is correct: it is very likely to be a
Wrong Jones boy:-)
mkinitrd bug. It *might* actually be something in the sata driver.. but
I can't really tell one way or the other.
What's your disk layout / fstab look like?
First, I think this is the best info:
[summer@localhost ~]$ cat /proc/partitions
major minor #blocks name
8 0 312571224 sda
8 1 69633711 sda1
8 2 8393962 sda2
8 3 104422 sda3
8 4 1 sda4
8 5 104391 sda5
8 6 234324058 sda6
8 16 488386584 sdb
8 17 488384001 sdb1
253 0 234291200 dm-0
[summer@localhost ~]$
but if you think differently:
[summer@localhost ~]$ cat /etc/fstab
/dev/VolGroup00/LogVol00 / ext3 defaults 1 1
LABEL=/boot /boot ext3 defaults 1 2
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0
/var/swapfile1 swap swap auto 0 0
/var/swapfile swap swap auto 0 0
Note that filesystems not mentioned there get mounted automatically
anyway (even worse, rw).
[summer@localhost ~]$
[summer@localhost ~]$ sudo fdisk -l /dev/sda
Disk /dev/sda: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xd42ad42a
Device Boot Start End Blocks Id System
/dev/sda1 * 1 8669 69633711 7 HPFS/NTFS
/dev/sda2 8671 9715 8393962+ 7 HPFS/NTFS
/dev/sda3 9716 9728 104422+ 72 Unknown
/dev/sda4 9729 38913 234428512+ 5 Extended
/dev/sda5 9729 9741 104391 83 Linux
/dev/sda6 9742 38913 234324058+ 8e Linux LVM
[summer@localhost ~]$ sudo fdisk -l /dev/sdb
Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x6bdb05f3
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 60801 488384001 6 FAT16
[summer@localhost ~]$
Here's an extract from dmesg (I want you coming back with a solution,
not more questions:-))
[summer@localhost ~]$ dmesg | grep -i ata
PERCPU: Allocating 436208 bytes of per cpu data
Memory: 2008032k/2072260k available (2584k kernel code, 63840k reserved,
1453k data, 720k init)
Write protecting the kernel read-only data: 1104k
libata version 3.00 loaded.
ata_piix 0000:00:1f.2: version 2.12
ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
scsi0 : ata_piix
scsi1 : ata_piix
ata1: SATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0x10e0 irq 14
ata2: SATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0x10e8 irq 15
ata1.00: ATA-7: ST3320620AS, 3.AAK, max UDMA/133
ata1.00: 625142448 sectors, multi 16: LBA48 NCQ (depth 0/32)
ata1.01: ATA-8: WDC WD5000AAKS-00YGA0, 12.01C02, max UDMA/133
ata1.01: 976773168 sectors, multi 16: LBA48 NCQ (depth 0/32)
ata1.00: configured for UDMA/133
ata1.01: configured for UDMA/133
ata2.00: ATAPI: PIONEER DVD-RW DVR-212, 1.21, max UDMA/66
ata2.00: configured for UDMA/66
scsi 0:0:0:0: Direct-Access ATA ST3320620AS 3.AA PQ: 0 ANSI: 5
scsi 0:0:1:0: Direct-Access ATA WDC WD5000AAKS-0 12.0 PQ: 0 ANSI: 5
EXT3-fs: mounted filesystem with ordered data mode.
EXT3-fs: mounted filesystem with ordered data mode.
[summer@localhost ~]$
Should I post the whole thing to the bug report?
-w
--
fedora-test-list mailing list
fedora-test-list@xxxxxxxxxx
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-test-list
