Re: bad pmd filemap.c, oops; 2.4.30 and 2.4.32

On Sat, Dec 31, 2005 at 02:39:43AM -0800, Chris Stromsoe wrote:
> On Sat, 31 Dec 2005, Willy Tarreau wrote:
> >On Fri, Dec 30, 2005 at 05:48:15PM -0800, Chris Stromsoe wrote:
> >
> >>I'm starting to suspect bad hardware. Booting is now hanging (with
> >>2.4.27, 2.4.30 and 2.4.32) after scsi drivers load:
> >
> >And nothing changed since previous boot, except UP ?
>
> All I changed was adding nosmp to the kernel boot line.

OK maybe interrupts don't get distributed to the remaining CPU, which
would explain your timeouts.

> >It's not necessarily bad hardware. I also had trouble on one version of
> >the 29160 bios where it hanged during device scan if there were too many
> >terminations. Oh, BTW, please check that you have disabled "automatic"
> >termination in the BIOS. Manually set it either to ON or OFF (low/high
> >depending on your setup).
>
> I'll have to check it tomorrow or on Monday.
>
> >>How likely is it that a failing scsi controller contribute to the other
> >>problems I was seeing?
> >
> >Not much. Perhaps at worst, a failing controller could corrupt memory by
> >writing garbage at wrong locations, but you would not always get the
> >same messages. It seems to be a different problem here. To be honnest,
> >it's where I think you should try the new driver.
>
> The machine has been running 2.6.14.4 for the last 6 hours. It came up
> fine. I did not try booting it with nosmp. If I have time, I will
> revert back to 2.4 with the newer driver to test.

Thanks.

> -Chris

Willy

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • Re: unmountable boot volume blue screen error
    ... It's always hard to narrow down a boot failure. ... intelppm.sys -Processor Device driver. ... purpose but I suspect disconnecting hardware is not a solution. ... screen) but it just keeps going to the windows screen telling you ...
    (microsoft.public.windowsxp.general)
  • Re: unmountable boot volume blue screen error
    ... Not a lot of Unmountable Boot Volume problems end up with a good result and also knowing what caused the problem. ... system 32 driver folder after mup.sys. ... purpose but I suspect disconnecting hardware is not a solution. ... Windows 2000 Miniport Driver. ...
    (microsoft.public.windowsxp.general)
  • Re: 2008 SBS no longer boots
    ... Windows *does* write to a log, however, during a safe-mode boot what ... driver it is attempting to load. ... Any thermal issues and a lot of other hardware problems should show up ... the customer in an already crappy situation and you have to make due. ...
    (microsoft.public.windows.server.sbs)
  • Re: WinXP doesnt start
    ... > My computer stopped booting properly. ... > driver updates. ... > - When normal boot is chosen it starts boot process then reboots. ... and replacing or swapping its flat ribbon cable, ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: replacing / duplicating domain controller
    ... Since the current domain controller boots to the D: drive, ... Knew there was a reason I never us the C: drive as the main boot ... to get the new hardware in. ... Also check that the video driver in use supports the new video hardware ...
    (comp.os.os2.networking.server)