2.6 kernel panics and hangs at boot (due to IDE DMA issues?)

From: Radosław Balcewicz (radek_at_clanet.pl)
Date: 04/19/05

  • Next message: Nicolas Boichat: "[PATCH] Leadtek Winfast remote controls"
    To: <linux-kernel@vger.kernel.org>
    Date:	Tue, 19 Apr 2005 02:00:31 +0200
    
    

    Hello.

    I've been trying to run Fedora Core 3 on dual P3 machine (Asus P2B-DS board, Intel BX chipset), but every time I try to boot it, it hangs moments after mounting local filesystems. It doesn't really matter if I boot SMP or non-SMP kernel and I've tried several, from 2.6.9 to latest 2.6.11-1 fresh from yum update. All I can do is boot rescue CD and chroot... Only once I got it to spit something that looked like this (sorry, I did not write it down at that time so it's just what I remember):

    kernel panic - not syncing: drivers/ide/pci/piix.c:<something>:spin-lock (drivers/ide/ide.c:<something>) already locked by drivers/ide/dma.c

    After few hours of trials and errors (and Google help) I finally got it running by adding ide=nodma to boot command line and by changing USE_DMA to =0 in /etc/sysconfig/harddisks. Now it boots every kernel it didn't before, SMP works fine, gcc recompiled kernel sources several time without single core dump, it's just without DMA disk data transfers are down to few MB/sec. Burning DVDs is short of impossible.

    From what I found this is a well-known problem with FC 2 & 3, Suse 9.1 and some other distributions based on recent 2.6 kernels and not-so-new hardware. So far I've failed to properly compile a vanilla 2.6.11.7 kernel (hangs just before INIT) so I can't say anything about that one... If this is a known problem then please don't flame me. I have been looking for possible solutions and posting here is my last resort at getting one. If someone can just point me to some explanation I'll be on my way. And please do CC to me directly as I have not subscribed...

    If this is a new problem then I'll be happy to assist and provide with logs and /proc infromations, it's just I wasn't sure I should include all that if this is perhaps some silly mistake on my behalf...

    Looking forward to an answer
    Radek

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


  • Next message: Nicolas Boichat: "[PATCH] Leadtek Winfast remote controls"

    Relevant Pages

    • Re: 2.6.6-rc2-bk3 (and earlier?) mount problem (?
      ... > to the bd_claimdebugging thing... ... > It will fill the logs, but I don't think it happens often enough to be a ... send the line "unsubscribe linux-kernel" in ... Please read the FAQ at http://www.tux.org/lkml/ ...
      (Linux-Kernel)
    • Re: Bug/Oops Power Management with linux-2.6.0-test5-mm2
      ... On Wednesday 17 September 2003 00:53, Patrick Mochel wrote: ... I missed that line in the logs before. ... send the line "unsubscribe linux-kernel" in ... Please read the FAQ at http://www.tux.org/lkml/ ...
      (Linux-Kernel)
    • Re: 2.6.0-test4: blkdev_requests "memory before object was overwritten" and oops in __iget
      ... Oleg Drokin wrote: ... > That's what was in logs: ... send the line "unsubscribe linux-kernel" in ... Please read the FAQ at http://www.tux.org/lkml/ ...
      (Linux-Kernel)
    • Re: reiser4 and megaraid problems with debian 2.6.5
      ... > Is there anything in the logs? ... send the line "unsubscribe linux-kernel" in ... More majordomo info at http://vger.kernel.org/majordomo-info.html ... Please read the FAQ at http://www.tux.org/lkml/ ...
      (Linux-Kernel)
    • Re: 2.6.0-test2-mm3
      ... I am using Fujitsu E-7010. ... There's nothing in my logs at all, so there's no way to tell what, if ... send the line "unsubscribe linux-kernel" in ... Please read the FAQ at http://www.tux.org/lkml/ ...
      (Linux-Kernel)