Re: 5.4-STABLE changes breaks IDE boot (was Re: 5.3 -> 5.4 breaks ATA (Intel ICH2))

From: Julian C. Dunn (lists_at_aquezada.com)
Date: 09/27/05

  • Next message: Tim Howe: "[PATCH] option to re-enable aggressive ATA probing (was: 5.3 -> 5.4 breaks ATA (Intel ICH2))"
    To: Billy Newsom <smartweb@leadhill.net>
    Date: Tue, 27 Sep 2005 00:35:07 -0400
    
    

    On Sun, 2005-09-25 at 15:36 -0500, Billy Newsom wrote:

    > I would like to concur with this sighting. I will repeat it to emphasize
    > this for whoever can decipher this for bug fixes:
    >
    > 1. In recent 5-Stable
    > 2. The IDE controller, atapci0,
    > 3. seems to be detectected, but without a certain memory allocation
    > 4. namely, 0xfff0-0xffff
    > 5. while the other memory and I/O segments are detected fine.
    >
    > Furthermore,
    > 6. It won't boot on the affected machines.
    > 7. More than one controller is affected (ICH2, PIIX3, and possibly PIIX4)
    > 8. Mine, at least, boots fine to a July 4th 5-Stable.
    >
    > Here is an example I found from someone reporting a similar issue
    > (Julian Dunn)
    >
    > Look at this from his dmesg:
    >
    > *First* his good booting dmesg line:
    > atapci0: <Intel PIIX4 UDMA33 controller> port
    > 0xfff0-0xffff,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 2.1 on pci0
    >
    > *Second* his non-booting dmesg line:
    > atapci0: <Intel PIIX4 UDMA33 controller> port
    > 0x376,0x170-0x177,0x3f6,0x1f0-0x1f
    > atapci0: Lazy allocation of 0x10 bytes rid 0x20 type 4 at 0
    > 7 at device 2.1 on pci0
    >
    > Can I point out the fact that these two lines (first from the good,
    > second from the bad dmesg) seem to say that atapci0 is not getting its
    > memory segment detected -- the segment at 0xfff0-0xffff.

    Here's a bit more information about the defect. I discovered this
    accidentally while testing out a -STABLE kernel built today. When I
    booted the -STABLE kernel, it went and autoloaded the
    old /boot/kernel/acpi.ko from the -RELEASE kernel, and the system would
    boot as normal. However, if I broke to the loader prompt and loaded the
    -STABLE kernel and its corresponding acpi.ko, the machine would fail to
    boot (as above, with the memory segment not being detected).

    Would this help anyone in filing a PR about the issue?

    - Julian

    -- 
    [ Julian C. Dunn <jdunn@aquezada.com>  *  "You can throw confetti,   ]
    [ WWW: www.aquezada.com/staff/julian   *  but you're still going     ]
    [ PGP: 91B3 7A9D 683C 7C16 715F        *  through the motions, baby" ]
    [      442C 6065 D533 FDC2 05B9        *                - Aimee Mann ]
    _______________________________________________
    freebsd-stable@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-stable
    To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
    

  • Next message: Tim Howe: "[PATCH] option to re-enable aggressive ATA probing (was: 5.3 -> 5.4 breaks ATA (Intel ICH2))"

    Relevant Pages

    • 2.6.28-rc9 panics with crashkernel=256M while booting
      ... parameter causes the kernel to panic while booting. ... Phyp-dump disabled at boot time ... console enabled ... memory reservation spans across these two nodes. ...
      (Linux-Kernel)
    • Re: Spontaneous unclean reboots
      ... I suggest you take a look at your hardware before you do anything else, to lessen the risk of corrupting your file system further, you should not boot into your system. ... You should use the memtest that you boot into, not using a tool that run as an application, as you want to be able to test the whole memory, otherwise you have to keep the kernel part of the memory out of the test and you won't see if there is anything wrong in that part, if you don't exclude the kernels memory space, then you will automatically crash wne you get to that point. ... Of course, you could have corrupted libraries, etc. or your hard drive could be slowly failing, which is a good possibility, if the hard drive like the system is 7 years old. ...
      (alt.os.linux)
    • Re: debian sarge and new installer
      ... Personally I also noticed some errors after I upgraded my kernel to 2.6; ... >>I have installed sarge using the installer cd. ... >>kernel and all seems to be running ok, but when I boot the system, I notice ... >>are not in dmesg. ...
      (Debian-User)
    • kernel panic - not syncing ???
      ... amd64 server will not complete boot, regardless which kernel from grub menu ... google hit on memory; but, that does not appear to be the case, after swapping memory ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". ...
      (Debian-User)
    • 2.6.12.1 problems I meet (please CC: me)
      ... I use a customized kernel to do packets analysis. ... during boot, the kernel boot with error "unknown bus type 0" and freeze. ... boot up execept that the analysis code can't vmallocthe needed memory. ...
      (Linux-Kernel)