Hide Forgot
Created attachment 541604 [details] Kernel output from the crash Description of problem: sadc from package sysstat causes kernel 3.1.4-1.fc16.x86_64 to crash Version-Release number of selected component (if applicable): 3.1.4-1.fc16.x86_64 How reproducible: Install sysstat package and enable sadc Additional info: Upgraded from Fedora 15 to 16 and immediately after the upgrade system started to crash. Uninstalled sysstat package and crashing stopped. Kernel output from the crash attached.
This is happening in the serial driver code. Are you running sadc on a serial console?
No, I'm not running sadc on a serial console. But /dev/console is mapped to a serial console. Kernel boot parameters are: ro root=/dev/mapper/vg_raid10-root rd_LVM_LV=vg_raid10/root rd_LVM_LV=vg_raid10/swap rd_NO_MD KEYTABLE=fi consoleblank=0 fbcon=vc:1-9 console=ttyS1,115200n8r console=tty1 reboot=bios,warm selinux=0
The box is Dell R710 in UEFI mode. /dev/ttyS1 is IPMI Serial-over-LAN console port.
The problem occured also with kernel-3.3.5-2.fc16.x86_64
Ilari, are you still seeing this with the 3.4 or 3.5 kernel updates?
# Mass update to all open bugs. Kernel 3.6.2-1.fc16 has just been pushed to updates. This update is a significant rebase from the previous version. Please retest with this kernel, and let us know if your problem has been fixed. In the event that you have upgraded to a newer release and the bug you reported is still present, please change the version field to the newest release you have encountered the issue with. Before doing so, please ensure you are testing the latest kernel update in that release and attach any new and relevant information you may have gathered. If you are not the original bug reporter and you still experience this bug, please file a new report, as it is possible that you may be seeing a different problem. (Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient).
With no response, we are closing this bug under the assumption that it is no longer an issue. If you still experience this bug, please feel free to reopen the bug report.