Re: syslogd messages, FC5, kernel 2.6.17-1.2174_FC5
- From: Andy Green <andy@xxxxxxxxxxx>
- Date: Wed, 23 Aug 2006 20:43:53 +0100
Antonio Olivares wrote:
I can turn on the machine and connect to the internet
with an external modem and see if the kernel oops
happens again.
You need to stop the slamr driver from getting loaded too in order to make a reasonable test. You can add
install slamr /bin/true
to
/etc/modprobe.conf
to defeat the loading of that module, then reboot. Run
lsmod | grep slamr
to confirm on reboot.
Thanks for your suggestions, hopefully when a newer
kernel is released I'll install it and the problem
goes away.
I note you can't say slamr without saying lamr! If that is the source of the problem, as it might be, a newer kernel isn't going to help.
-Andy
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
- Follow-Ups:
- Re: syslogd messages, FC5, kernel 2.6.17-1.2174_FC5
- From: Antonio Olivares
- Re: syslogd messages, FC5, kernel 2.6.17-1.2174_FC5
- References:
- Re: syslogd messages, FC5, kernel 2.6.17-1.2174_FC5
- From: Antonio Olivares
- Re: syslogd messages, FC5, kernel 2.6.17-1.2174_FC5
- Prev by Date: sftp transfer has different unix right
- Next by Date: Re: Born this Day (Lord Willing) The Crash Cart Project
- Previous by thread: Re: syslogd messages, FC5, kernel 2.6.17-1.2174_FC5
- Next by thread: Re: syslogd messages, FC5, kernel 2.6.17-1.2174_FC5
- Index(es):
Relevant Pages
|