Bug 689104 - System crashes ( stops without kernel panic ) - HP Compaq 6530b
Summary: System crashes ( stops without kernel panic ) - HP Compaq 6530b
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 14
Hardware: i686
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: John W. Linville
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-19 13:58 UTC by Ivan Georgiev
Modified: 2011-03-24 13:42 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-24 13:42:00 UTC
Type: ---


Attachments (Terms of Use)
System logs before crash and hardware info (17.51 KB, text/plain)
2011-03-19 13:58 UTC, Ivan Georgiev
no flags Details
My complete messages log file (397.92 KB, text/plain)
2011-03-22 21:54 UTC, Ivan Georgiev
no flags Details

Description Ivan Georgiev 2011-03-19 13:58:52 UTC
Created attachment 486377 [details]
System logs before crash and hardware info

Description of problem:
System crashes on random intervals when I use wireless. Logs and hardware information are attached.


Version-Release number of selected component (if applicable):
kernel-2.6.35.10-72.fc14.i686
kernel-2.6.35.10-74.fc14.i686 ##Currently in use
kernel-2.6.35.11-83.fc14.i686
iw-0.9.20-1.fc14.i686
iwl1000-firmware-128.50.3.1-2.fc13.noarch
iwl5150-firmware-8.24.2.2-1.fc13.noarch
iwl6000-firmware-9.221.4.1-1.fc14.noarch
iwl6050-firmware-41.28.5.1-2.fc14.noarch

How reproducible:
Use wireless connectivity and wait for an hour

 
Additional info:

1) Earlier system only lost connectivity on random intervals.
2) There are no issues with Windows Vista ( it is not a hardware problem )


You can always contact me at ivan.georgiev89

Comment 1 John W. Linville 2011-03-21 14:06:38 UTC
Where is the crash?

Comment 2 Ivan Georgiev 2011-03-22 05:36:15 UTC
If you mean crash dump, then please tell me how to aquire it. If you check the attached caselogs I have shown examples when the system freezes. Later today I will upload the complete caselog.

Please do not close the bug report as it is observerd by other collegues of mine.

Comment 3 John W. Linville 2011-03-22 13:47:12 UTC
You attached highly edited information that appears to show some firmware restarts.  There is no indication of a "crash" (e.g. a kernel backtrace) and no description of what was happening.

In comment 2 you use the term "system freezes".  Perhaps you can use netconsole to capture a backtrace over an ethernet connection?

Comment 4 Ivan Georgiev 2011-03-22 21:53:33 UTC
Hello,
Sorry for the misunderstanding - I am not much of a bug reporter. As promised I am attaching my complete messages log. If you compare the "highly edited" information in the log you will notice:
1) System stopped for unknown reason
2) There is no kernel trace.

I have little more experience with HP-UX where system generates crash dumps in /var/adm/crash, but unfortunately in this situation I have no proper hardware or knowledge. 

Please guide me!

Is there a way to enable kernel dumping on crash?

I would also like also to describe the scenario:
I have dual boot on my laptop with Fedora 14 and Windows Vista Enterprise.

I use my computer a lot - more then 16 hours a day and say that i have tested both OSes very well. Here is what happens

1) I enable my wireless
2) System freezes -  Ctrl+ALt+F1/2/3/4.. is not working. Display is not responding. Wireless indicator starts blinking ( as if there is a fault )

In order to use my computer again I have to hold the power button. Issue occurs very randomly. Yesterday I had 5 crashes only in the morning. Today it did not crash even once  and I had not made any changes.

There is already a bug report for the broken Intel Firmware: 648732. But it seems that only I have issue where the system stops responding.

Comment 5 Ivan Georgiev 2011-03-22 21:54:17 UTC
Created attachment 486914 [details]
My complete messages log file

Comment 6 John W. Linville 2011-03-23 13:22:58 UTC
I often use netconsole to capture stack traces:

   http://fedoraproject.org/wiki/Netconsole

You might need to "service iptables off" on the "debugger" machine for netconsole to work.

For an alternative more similar to what you mentioned with HP-UX, you might try using kdump instead;

   http://fedoraproject.org/wiki/Kernel/kdump

If you use kdump, please start by using the "bt" command in 'crash' to determine where the crash happened.

Comment 7 Ivan Georgiev 2011-03-23 15:21:32 UTC
Hello,
Please... some urgent help:
1) I did:
yum install --enablerepo=fedora-debuginfo --enablerepo=updates-debuginfo kexec-tools crash kernel-debuginfo
2) I added in the end of my boot parameters:
 crashkernel=128M

3) I did 
service start kdump
and it configured new initramfs file.

My computer has MacAfee end point ecryption and it is VERY important that I do not touch the MBR.

I rebooted the system.

MacAfee starts, I enter the code and then the computer freezes to "Reseting hardware" No GRUB. No OS. Nothing!

Please tell me what could have gone wrong. I think i have backup of the MBR but before taking any risky steps I need confirmation that the commands above have touched something on my disk.


Thank you in advance for your fast response!

Comment 8 John W. Linville 2011-03-23 15:37:31 UTC
The commands listed above will create some files in the filesystem, but they should not modified your MBR -- I have no idea why your machine would refuse to boot.

I'm sorry, but I'm not familiar with MacAfee's offerings.  So I really don't now what to suggest.  Perhaps you're local IT folk can help?

Comment 9 Ivan Georgiev 2011-03-23 23:27:51 UTC
I reinstalled my computer. I abandoned the idea of having Linux on the working station. I used happily Fedora since 11, but today I spent 6 hours on restoring. You may close the bug report, because i do not have another laptop with the same hardware.

Very sorry for losing your time.

Comment 10 John W. Linville 2011-03-24 13:42:00 UTC
Well, I'm sorry this happened -- I wish I could explain it, but I don't see anything in the kdump setup process that would account for the problem you experienced.


Note You need to log in before you can comment on or make changes to this bug.