WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Call Trace error  (Read 2353 times)

Offline coreplayer2

  • Hero Member
  • *****
  • Posts: 3020
Call Trace error
« on: May 03, 2012, 08:46:47 AM »
Have seen this a few times recently during boot which of course stops here.

call trace:
[<c042274e>] ? 0xc042274e
etc etc (maybe twenty or so addresses listed after this with no other details)


I believe this indicates a Kernel Panic which is likely caused by the initrd not loading.

Could this error be caused by anything else??




Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 8123
Re: Call Trace error
« Reply #1 on: May 03, 2012, 09:10:36 AM »
Hi coreplayer2
Waitusb time is not long enough? RAM problem?

Offline tinypoodle

  • Hero Member
  • *****
  • Posts: 3857
Re: Call Trace error
« Reply #2 on: May 03, 2012, 10:59:00 AM »
Besides from kernel panic, a Call Trace showing could also be caused by an oops or a watchdog.
"Software gets slower faster than hardware gets faster." Niklaus Wirth - A Plea for Lean Software (1995)

Offline coreplayer2

  • Hero Member
  • *****
  • Posts: 3020
Re: Call Trace error
« Reply #3 on: May 03, 2012, 11:24:58 PM »
Thanks for the info,  will advise when I get feedback..