Sponsored Content
Special Forums UNIX Desktop Questions & Answers kernel panic-not syncing:fatal exception while booting Post 302272216 by jack00423 on Tuesday 30th of December 2008 02:02:54 AM
Old 12-30-2008
Hi

Hi,

It is

Dell xps M1330
320 samsung sata hard disk
2.8 ghz dual core
3 gb ram

Please help me..

Thanks
Jack
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Kernel panic - not syncing == While RHEL AS install

I am trying to Install RHEL AS 4 on x86 pc, through VNC and got the below error, Am not pretty sure as how to resolve this. Can some one guide me through the process, or what might be missing.... Have Installed RHEL, many a times but cudnt find this out... Wud appreciate an early reply ......... (0 Replies)
Discussion started by: Crazy_murli
0 Replies

2. Linux

Kernel panic - not syncing: cannot execute a PAE-enabled kernel on PAE-less CPU

ok so I just installed fedora core 6 on my dell inspiron 700m and I go to boot into linux and I get this error. Has anyone seen this before? I also had XP Pro and Vista installed on this pc prior to putting fedora core 6 on the machine. I'm trying to setup a triple boot system. Please Help... (2 Replies)
Discussion started by: dave043
2 Replies

3. UNIX for Advanced & Expert Users

Kernel panic : Fatal exception

HI, My Machine is running on RHEL3, Its not booting. When I try to boot in rescue mode.Its giving the following err: " Kernel panic : Fatal exception " Can any one tel me how to get rid of this error? (3 Replies)
Discussion started by: praveen_b744
3 Replies

4. UNIX for Advanced & Expert Users

FATAL:exception occured with pthread_exit()

We had written an application in which we create worker thread. So the main thread will create the worker thread. After some time the child thread(Worker thread) will call pthread_exit(). This function was written in try{} and there occured an Exception and is handled in catch(...)... (0 Replies)
Discussion started by: platso
0 Replies

5. Solaris

can any body tell me what is the difference between server panic and fatal error.

HI friends can any body tell me what is the difference between server panic and fatal error. (1 Reply)
Discussion started by: tv.praveenkumar
1 Replies

6. UNIX for Advanced & Expert Users

what does the kernel panic mean?

Hi, all: How should I obtain the reason of kernel panic? How should I debug the program which result in a kernel panic? What can I get from the panic information? li, kunlun (3 Replies)
Discussion started by: liklstar
3 Replies

7. Ubuntu

kenel panic not syncing

I installed a new kernel 3.0.22 on ubuntu server 11.04 32 bit. when I select the kenel from boot loader it stops when Code: loading initial ramdisk... I added all_generic_ide at the end of linux line and also added dev/sda1 to linux line: root=UUID=dev/sda1 now it says that ... (12 Replies)
Discussion started by: dr_mabuse
12 Replies

8. Slackware

Help with kernel panic - not syncing slackware 13.0

Hi, first of all I'm 110% newbie, sorry for any mistake if I made it. In my country there are no normal or active linux forums, so i found this forum. Ok, that's for begining, but not for may real problem. --------------------------------------------------- I am system administrator... (4 Replies)
Discussion started by: ElvijsL
4 Replies

9. Red Hat

Error: kernal panic not syncing

HI All, server stopped here, we are suspecting server crash, need install new OS. Any suggestions on this. kindly help to us. Thanks Rajesh (0 Replies)
Discussion started by: Rajesh_Apple
0 Replies

10. Red Hat

Kernel panic-not syncing

dear experts linux i am using RHEL 5.5 run on a physical server. i am front of a big trouble, the Rhel can't run correctly , it show me this error message in black screen: reading all physical volumes. this my take a while .. found volume group "VolGroup00" using metadata type lvm2 9... (1 Reply)
Discussion started by: wassimpb
1 Replies
sata(7D)							      Devices								  sata(7D)

NAME
sata - Solaris SATA framework DESCRIPTION
Serial ATA is an interconnect technology designed to replace parallel ATA technology. It is used to connect hard drives, optical drives, removable magnetic media devices and other peripherals to the host system. For complete information on Serial ATA technology, visit the Serial ATA web site at http://www.serialata.org. Up to 32 SATA devices may be plugged directly to each SATA HBA supported by the Solaris SATA framework. The actual number of pluggable devices my be lower, and is limited by a number of device ports on the SATA HBA. The maximum data rate is either 1.5Gb/sec. or 3.0Gb/sec., depending on the capability of a SATA device and SATA HBA controller. The Solaris SATA framework adheres to the Serial ATA 1.0a specification and supports SATA-2 signaling speed 3.0Gb/sec. SATA devices that are connected to SATA HBAs controlled by a SATA framework-compliant HBA driver are treated by the system as SCSI devices. The Solaris SCSI disk driver (sd(7D)) is attached as a target driver for each device node created by the SATA framework. You can use the cfgadm(1M) utility to manage hot plugged and unplugged SATA devices. FILES
/kernel/misc/sata 32-bit ELF kernel module (x86). /kernel/misc/amd64/sata 64-bit ELF kernel module (x86). ATTRIBUTES
See attributes(5) for descriptions of the following attribute: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Architecture |x86 | +-----------------------------+-----------------------------+ |Availability |SUNWckr | +-----------------------------+-----------------------------+ SEE ALSO
cfgadm(1M), prtconf(1M), cfgadm_sata(1M), attributes(5), ahci(7D), marvell88sx(7D), nv_sata(7D), sd(7D), si3124(7D) Serial ATA 1.0a Specification -- Serial ATA International Organization. Serial ATA II (Extension to Serial ATA 1.0.a.) -- Serial ATA International Organization. http://www.sun.com/io DIAGNOSTICS
The messages described below may appear on the system console as well as being logged. All messages are presented in one of the following formats and are followed by the diagnostic message: sata: WARNING: <controller/devices/.. path>: or: sata: NOTICE: <controller/devices/.. path>: ...where <controller/devices/.. path> identifies a specific SATA HBA issuing a diagnostic message shown below. SATA port X: link lost. Communication (via serial link) between the HBA and the device plugged to the specified SATA device port has been lost. SATA port X: link established. Communication (via serial link) between the HBA and the device plugged to the specified SATA device port has been established. SATA port X: device reset. The device plugged to the specified SATA device port has been reset. The reset may be due to a communication or command error, command timeout, or an explicit request from the host. SATA port X failed. The specified SATA device port failed and is in an unusable state. You can change the port state by deactivating the port and activat- ing it again using cfgadm SATA hardware-specific commands (see cfgadm_sata(1M)). SATA port X error. An error was detected in specified SATA device port operations. SATA device detached at port X. Communication (via serial link) between the HBA and the device plugged to the specified SATA device port has been lost and could not be re-established. The SATA framework assumes that the device is unplugged from the specified SATA device port. SATA device detected at port X. Communication( via serial link) between the HBA and the device plugged to the specified empty SATA device port has been established. The SATA framework assumes that the new device is plugged to the specified SATA device port. SATA disk device at port X. This message is followed by a disk description specifying the disk vendor, serial number, firmware revision number and the disk capa- bilities. SATA CD/DVD (ATAPI) device at port X. This message is followed by a SATA CD/DVD description specifying the DVD vendor, serial number, firmware revision number and the DVD capabilities. SATA device at port X cannot be configured. Application(s) accessing previously attached device have to release it before newly inserted device can be made accessible. The port cannot be configured because there is application using the previous attached device, so the application must release it, then the newly inserted device can be configured. Application(s) accessing previously attached SATA device have to release it before newly inserted device can be made accessible. The target node remained and it belongs to a previously attached device. This happens when the file was open or the node was waiting for resources at the time the associated device was removed. Instruct event daemon to retry the cleanup later. sata: error recovery request for non-attached device at cport X. When error recovery is requested, the device is not yet attached. SATA device at port X will not be power-managed. When property "pm-capable" on the target device node setting fails, the SATA device won't be power-managed. SATA disk device at port X does not support LBA. The disk device plugged into specified SATA device port does not support LBA addressing and cannot be used. Cannot identify SATA device at port X - device will not be attached. IDENTIFY (PACKET) DEVICE data cannot be retrieved successfully after the device is attached to the SATA port. sata: <HBA driver name><instance number>:hba attached failed. The SATA HBA instance attach operation failed. This HBA instance cannot be configured and is not available. sata: invalid ATAPI cdb length<command cdb length>. The length of the command cdb is greater than that the device can support. sata: invalid sata_hba_tran version X for driver <HBA driver name>. The specified SATA HBA driver and the SATA framework are incompatible. The driver cannot attach and SATA HBAs controlled by this driver (and devices plugged to this SATA HBA ports) are not available. sata_hba_attach: cannot create SATA attachment point for port X. The specified SATA device port cannot be configured in the system and a device plugged to this port could not be not be configured and used. sata_create_target_node: cannot create target node for device at port X. The device target node for the device plugged to the specified SATA device port could not be created. As a result, the device cannot be configured and used. SunOS 5.11 5 Sep 2007 sata(7D)
All times are GMT -4. The time now is 10:44 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy