2.6.14 update throws kernel panic

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: For users of Fedora Core releases <fedora-list@xxxxxxxxxx>
Subject: 2.6.14 update throws kernel panic
From: Sean Bruno <sean.bruno@xxxxxxxxxxxx>
Date: Fri, 11 Nov 2005 14:25:58 -0800
List-help: <mailto:[email protected]?subject=help>
List-id: For users of Fedora Core releases <fedora-list.redhat.com>
List-post: <mailto:[email protected]>
List-subscribe: <https://www.redhat.com/mailman/listinfo/fedora-list>, <mailto:[email protected]?subject=subscribe>
List-unsubscribe: <https://www.redhat.com/mailman/listinfo/fedora-list>, <mailto:[email protected]?subject=unsubscribe>
Reply-to: For users of Fedora Core releases <fedora-list@xxxxxxxxxx>

I updated to the 2.6.14 release today and was greeted with a kernel
panic on reboot.  It looks like some behaviour has changed regarding the
kernel boot option "iommu=memaper=x" flags.  

I have a dual opteron 246 with 6GB of ram on an ASUS K8N-DL.  It
apparently doesn't have an IOMMU on board, so I have been able to
function with the iommu=memaper=3 option up until now.

The panic was pretty short, no code or pointer to output.  It just
referenced the fact that I didn't have an IOMMU and halted.

Sean

Follow-Ups:
- Re: 2.6.14 update throws kernel panic
  - From: Wolfgang S. Rupprecht

Prev by Date: [fwd] md raid1 chokes when one disk is removed
Next by Date: Re: [fwd] md raid1 chokes when one disk is removed
Previous by thread: [fwd] md raid1 chokes when one disk is removed
Next by thread: Re: 2.6.14 update throws kernel panic
Index(es):
- Date
- Thread

[Index of Archives] [Current Fedora Users] [Fedora Desktop] [Fedora SELinux] [Yosemite News] [Yosemite Photos] [KDE Users] [Fedora Tools] [Fedora Docs]