Bug 241929
Summary: | Load Into Ram Bug | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | nomb85 | ||||||
Component: | kernel | Assignee: | Alan Cox <alan> | ||||||
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Brian Brock <bbrock> | ||||||
Severity: | high | Docs Contact: | |||||||
Priority: | low | ||||||||
Version: | 7 | CC: | alan, davej, davidz, dcantrell, katzj | ||||||
Target Milestone: | --- | Keywords: | Reopened | ||||||
Target Release: | --- | ||||||||
Hardware: | i686 | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2007-09-10 15:32:03 UTC | Type: | --- | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Description
nomb85
2007-05-31 19:03:18 UTC
Looks like a coaster, e.g. there are physical errors on the media. Suggest to try and burn to another disc. I've verified the md5's Burnt 3 gnomes and 3 kdes and they all do the same thing. also, this is not just me. other people form linuxquestions.org are having the same problem. are you saying we are all burning the badly? Do you have pointers to the threads on linuxquestions.org? Sorry for just closing the bug but it really _does_ look like a coaster and coasters happen often. So it was more a knee jerk reaction. The block numbers look suspiciously high - the lowest one is 352484; at 2048 bytes per block; that would be at an offset that is 688MB (where 1MB = 2^20 bytes).. hmm.. so still OK. Questions 1. Did you use a 700MB disc? 2. What kind of drive is it? (please attach output of lshal) 3. Does the verify disc from grub work? I'm tempted to reassign this to the kernel, blaming the driver... Here's the thread: http://www.linuxquestions.org/questions/showthread.php?t=557702 I get the same errors on two KDE live disks and a Gnome disk burned from a seperate computer. I even used a 4x burn speed on one of the KDE disks. If I or the OP boot to the CD in not-to-RAM mode, the boot is successful. Created attachment 155855 [details]
lshal output
I ran the Verify Disk feature, and the disk passed the test. On a (possibly) related note, no boot options work on my laptop unless I enter the options "noapic nolapic" at boot. Without those, it stops at "uncompressing kernel" Hi, thanks for the feedback and taking time to provide the requested information. From the lshal output I can see you're using the ata_piix driver. My best guess at this point is that there's a defect in that driver; all we do in the initramfs is basically 1. mount root iso9660 fs at /sysroot 2. dd if=/sysroot/squashfs.img of=/squashed.img bs=512 (e.g. copy a file from the CD to the tmpfs of the initramfs) e.g. we haven't set up any of the device mapper stuff yet. For reference, the script that generates the initramfs is here http://git.fedoraproject.org/?p=hosted/livecd;a=blob_plain;f=creator/mayflower;h=ef43ddcda3c2a5f9c2a57642d09fc39b50a3834f I'm reassigning to the kernel from now and adding Alan and Dave as they probably know what changed from Test4 to GOLD. I'm also adding myself as Cc in case we've screwed something up in user space. Also, I think we can probably rule out that the drive is broken as this worked for you in Test4. So everything points to a driver bug I guess? Thanks. Created attachment 155874 [details]
My lshal output.
Also, All the discs were 700mb I only verified two of them, one gnome, one kde, but they were fine My lshal is above. Don't worry about just closing the ticket. If I went through as many as you guys, I'd probably do the same thing. nomb Brian - can you open a seperate bug about the APIC problem if you haven't already and attach a dmidecode to it. Ticket opened: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=242717 Thanks There are no ata_piix changes between the two as far as I can tell and it seems to be a real media error (unfortuantely the bits of trace you have are too late after the media error would have been displayed to be 100% sure) |