LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 01-12-2012, 09:01 AM   #1
procfs
Member
 
Registered: Jan 2006
Location: Sri Lanka
Posts: 608

Rep: Reputation: 34
Error: Driver 'pcspkr' is already registered, aborting


Hi below is a part of a message log in Redhat 5.6 EL (64). can some one tell me what his this error is all about can this caus the server to reboot!

Jan 12 15:59:01 avaback01 kernel: lpfc 0000:0e:00.0: 10):2753 PLOGI failure DID:010400 Status:x3/x16
Jan 12 15:59:01 avaback01 kernel: scsi 1:0:2:0: Sequential-Access HP Ultrium 4-SCSI H5AW PQ: 0 ANSI: 5
Jan 12 15:59:01 avaback01 kernel: scsi 1:0:2:0: Attached scsi generic sg8 type 1
Jan 12 15:59:01 avaback01 kernel: EXT3-fs: INFO: recovery required on readonly filesystem.
Jan 12 15:59:01 avaback01 kernel: EXT3-fs: write access will be enabled during recovery.
Jan 12 15:59:01 avaback01 kernel: kjournald starting. Commit interval 5 seconds
Jan 12 15:59:01 avaback01 kernel: EXT3-fs: recovery complete.
Jan 12 15:59:01 avaback01 kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jan 12 15:59:01 avaback01 kernel: SELinux: Disabled at runtime.
Jan 12 15:59:01 avaback01 kernel: type=1404 audit(1326373112.154:2): selinux=0 auid=4294967295 ses=4294967295
Jan 12 15:59:01 avaback01 kernel: iTCO_vendor_support: vendor-support=0
Jan 12 15:59:01 avaback01 kernel: iTCO_wdt: Intel TCO WatchDog Timer Driver v1.05
Jan 12 15:59:01 avaback01 kernel: iTCO_wdt: failed to reset NO_REBOOT flag, reboot disabled by hardware
Jan 12 15:59:01 avaback01 kernel: iTCO_wdt: No card detected
Jan 12 15:59:01 avaback01 kernel: input: PC Speaker as /class/input/input6
Jan 12 15:59:01 avaback01 kernel: Error: Driver 'pcspkr' is already registered, aborting...
Jan 12 15:59:01 avaback01 kernel: Floppy drive(s): fd0 is 1.44M
Jan 12 15:59:01 avaback01 kernel: hpwdt 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Jan 12 15:59:01 avaback01 kernel: hp Watchdog Timer Driver: 1.1.1, timer margin: 30 seconds (nowayout=0), allow kernel dump: OFF (default = 0/OFF), priority: LAST (defa
ult = 0/LAST).
Jan 12 15:59:01 avaback01 kernel: [drm] Initialized drm 1.1.0 20060810

Thanks and Regards
 
Old 01-12-2012, 10:20 AM   #2
unSpawn
Moderator
 
Registered: May 2001
Posts: 29,353
Blog Entries: 55

Rep: Reputation: 3541Reputation: 3541Reputation: 3541Reputation: 3541Reputation: 3541Reputation: 3541Reputation: 3541Reputation: 3541Reputation: 3541Reputation: 3541Reputation: 3541
Try '/sbin/modinfo pcspkr' for details. I strongly doubt it's the pcspkr kernel module that makes the server reboot. To test it you could try and blacklist it (see /etc/modprobe.d/ contents).
 
Old 01-12-2012, 11:32 AM   #3
procfs
Member
 
Registered: Jan 2006
Location: Sri Lanka
Posts: 608

Original Poster
Rep: Reputation: 34
hi unSpawn thank you for the reply, you are right looks like OCFS or relating to OCFS is causing the problem. cant seems to narrrow it down to what it is though. when I try to access the cluster file system the session hangs!

Thanks and best regards
 
Old 01-12-2012, 02:18 PM   #4
unSpawn
Moderator
 
Registered: May 2001
Posts: 29,353
Blog Entries: 55

Rep: Reputation: 3541Reputation: 3541Reputation: 3541Reputation: 3541Reputation: 3541Reputation: 3541Reputation: 3541Reputation: 3541Reputation: 3541Reputation: 3541Reputation: 3541
Quote:
Originally Posted by procfs View Post
looks like OCFS or relating to OCFS is causing the problem. cant seems to narrrow it down to what it is though. when I try to access the cluster file system the session hangs!
How and what with do you establish that "session"? Can it be made to output verbose and or debug output? Are any errors returned? Are there other methods that allow you to establish a connection OK?
 
Old 01-17-2012, 04:44 AM   #5
procfs
Member
 
Registered: Jan 2006
Location: Sri Lanka
Posts: 608

Original Poster
Rep: Reputation: 34
Hi unSpawn

Sorry for the delay

I am using putty to get in to the machine > then I changed in to the cluster mount and did ls it was like stuck and I had to kill the session to get out of the command. vired thing is this happens time to time I cam unable to tell when or where. I am trying to put this demon in debug mode, thing is I am new to this kind of setup!

I have attached message log here with

Thanks and Best regards
 
Old 01-23-2012, 03:53 AM   #6
procfs
Member
 
Registered: Jan 2006
Location: Sri Lanka
Posts: 608

Original Poster
Rep: Reputation: 34
Hi Thanks for the help guess I need to start sprat ticket.

Best Regards
 
Old 06-09-2012, 03:32 AM   #7
procfs
Member
 
Registered: Jan 2006
Location: Sri Lanka
Posts: 608

Original Poster
Rep: Reputation: 34
Hi all we could not find what was the couse of the problem and we did a reinstallation so far the systems is stable

Thanks you for all your help
 
Old 09-10-2012, 05:00 PM   #8
slingshotsuicide
LQ Newbie
 
Registered: Nov 2010
Distribution: Debian... again
Posts: 5

Rep: Reputation: 0
With all due respect procfs... This doesn't sound 'solved' to me. From your last comment, it sounds like you just reinstalled (not really the resolution most are looking for) and I'd guess it's still kicking the error (since my system kicks it but works) It may just be me, but 'Solved' means "We found out that the problem was caused by X, we did Y, and now I no longer get the error but the pc speaker works. I've now wasted the time to read this thread for nothing (no acceptable resolution whatsoever) reinstall is for Windows techs, "I tore out the problem, fixed the config that was causing it, and all is right with the world." That's how I approach my Linux issues.

Last edited by slingshotsuicide; 09-10-2012 at 05:03 PM.
 
Old 09-10-2012, 05:15 PM   #9
slingshotsuicide
LQ Newbie
 
Registered: Nov 2010
Distribution: Debian... again
Posts: 5

Rep: Reputation: 0
Ok, here, now your thread is properly marked:
http://mindref.blogspot.com/2010/04/...egistered.html
In case the link goes away, it says (do as root)

echo 'blacklist snd-pcsp' >> /etc/modprobe.d/blacklist.conf

It means, 'Don't load this module' (because it's already loaded.)

Last edited by slingshotsuicide; 09-10-2012 at 05:17 PM.
 
Old 09-10-2012, 06:02 PM   #10
unSpawn
Moderator
 
Registered: May 2001
Posts: 29,353
Blog Entries: 55

Rep: Reputation: 3541Reputation: 3541Reputation: 3541Reputation: 3541Reputation: 3541Reputation: 3541Reputation: 3541Reputation: 3541Reputation: 3541Reputation: 3541Reputation: 3541
Quote:
Originally Posted by slingshotsuicide View Post
I've now wasted the time to read this thread for nothing
I'm sorry but your post does not shed any new light on the OP's problem.
Besides I already talked about blacklisting in my first reply so if you're going to read threads then please read them carefully before posting.
 
Old 09-10-2012, 11:58 PM   #11
procfs
Member
 
Registered: Jan 2006
Location: Sri Lanka
Posts: 608

Original Poster
Rep: Reputation: 34
Hi, slingshotsuicide since I am no guru so for me this is solved since by reinstalling my issue went away hence the status "SOLVED"

Hi, unSpawna thank you for trying to help me, since the re installation 2nod cluster is running stable with OCFS2 and I do not see any warnings nor errors in the logs

Thanks and Best Regards

Last edited by procfs; 09-11-2012 at 12:03 AM.
 
Old 09-12-2012, 08:54 AM   #12
slingshotsuicide
LQ Newbie
 
Registered: Nov 2010
Distribution: Debian... again
Posts: 5

Rep: Reputation: 0
You are correct unSpawn, I DID miss your earlier post of blacklisting the mod... (not sure how I did that since I distinctly remember reading "I strongly doubt it's the pcspkr kernel module that makes the server reboot."

procfs Apologies as well, but generally when I see SOLVED I do expect to see "This was the issue, and here's how it was solved" I admin webservers for a living, and I can't post here the reply I would get for suggesting the downtime of a reimage to resolve an error message. Especially when it came with "There's a chance this might fix it."

Crap!! It's worse, I google'd to get here in the first place and just now realized it's a newbie forum. Very sorry procfs. This does get easier, and you'll learn to love it.

Last edited by slingshotsuicide; 09-12-2012 at 08:59 AM.
 
Old 09-13-2012, 03:09 AM   #13
procfs
Member
 
Registered: Jan 2006
Location: Sri Lanka
Posts: 608

Original Poster
Rep: Reputation: 34
Hi slingshotsuicide, no worries, and once you get used to it this is a great place to get answers to your question, have been using this for a while and enjoyed every step

Best Regards
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
unrecoverable fatal error, aborting mahfuz05 Linux - Newbie 3 07-01-2010 01:38 PM
z600 Lexmark driver is always aborting KasperLotus Linux - Hardware 1 10-07-2005 09:59 PM
Aborting with an error when i use pbuilder sakulaqi Debian 0 08-07-2005 08:42 AM
Sound Server Fatal Error: CPU overload. aborting hoe Linux - Newbie 0 05-29-2004 10:55 AM
sound server fatal error, cpu overload:aborting. fettouhi Linux - Software 1 02-29-2004 12:26 PM


All times are GMT -5. The time now is 02:55 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration