LinuxQuestions.org
Visit Jeremy's Blog.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - General
User Name
Password
Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.

Notices


Reply
  Search this Thread
Old 06-29-2007, 01:01 PM   #1
tntcoder
Member
 
Registered: Sep 2003
Distribution: Arch
Posts: 89

Rep: Reputation: 15
Strange Kernel Errors


Hi,

Just built a new kernel and im getting the following errors during boot, but it still boots and there is no panic, but i would like to fix them if possible, i assume i either built something in i shoundt have, or missed something out

Code:
DMESG Segment:

device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com
nbd0: Attempted send on closed socket
end_request: I/O error, dev nbd0, sector 0
Buffer I/O error on device nbd0, logical block 0
Buffer I/O error on device nbd0, logical block 1
Buffer I/O error on device nbd0, logical block 2
Buffer I/O error on device nbd0, logical block 3
nbd0: Attempted send on closed socket
end_request: I/O error, dev nbd0, sector 0
Buffer I/O error on device nbd0, logical block 0
nbd0: Attempted send on closed socket
end_request: I/O error, dev nbd0, sector 4294965120
nbd0: Attempted send on closed socket
end_request: I/O error, dev nbd0, sector 0
nbd1: Attempted send on closed socket
end_request: I/O error, dev nbd1, sector 4294965120
nbd1: Attempted send on closed socket
end_request: I/O error, dev nbd1, sector 0
nbd2: Attempted send on closed socket
end_request: I/O error, dev nbd2, sector 4294965120
nbd2: Attempted send on closed socket
end_request: I/O error, dev nbd2, sector 0
nbd3: Attempted send on closed socket
end_request: I/O error, dev nbd3, sector 4294965120
nbd3: Attempted send on closed socket
end_request: I/O error, dev nbd3, sector 0
nbd4: Attempted send on closed socket
end_request: I/O error, dev nbd4, sector 4294965120
nbd4: Attempted send on closed socket
end_request: I/O error, dev nbd4, sector 0
nbd5: Attempted send on closed socket
end_request: I/O error, dev nbd5, sector 4294965120
nbd5: Attempted send on closed socket
end_request: I/O error, dev nbd5, sector 0
nbd6: Attempted send on closed socket
end_request: I/O error, dev nbd6, sector 4294965120
nbd6: Attempted send on closed socket
end_request: I/O error, dev nbd6, sector 0
nbd7: Attempted send on closed socket
end_request: I/O error, dev nbd7, sector 4294965120
nbd7: Attempted send on closed socket
end_request: I/O error, dev nbd7, sector 0
nbd8: Attempted send on closed socket
end_request: I/O error, dev nbd8, sector 4294965120
nbd8: Attempted send on closed socket
end_request: I/O error, dev nbd8, sector 0
nbd9: Attempted send on closed socket
end_request: I/O error, dev nbd9, sector 4294965120
nbd9: Attempted send on closed socket
end_request: I/O error, dev nbd9, sector 0
nbd10: Attempted send on closed socket
end_request: I/O error, dev nbd10, sector 4294965120
nbd10: Attempted send on closed socket
end_request: I/O error, dev nbd10, sector 0
nbd11: Attempted send on closed socket
end_request: I/O error, dev nbd11, sector 4294965120
nbd11: Attempted send on closed socket
end_request: I/O error, dev nbd11, sector 0
nbd12: Attempted send on closed socket
end_request: I/O error, dev nbd12, sector 4294965120
nbd12: Attempted send on closed socket
end_request: I/O error, dev nbd12, sector 0
nbd13: Attempted send on closed socket
end_request: I/O error, dev nbd13, sector 4294965120
nbd13: Attempted send on closed socket
end_request: I/O error, dev nbd13, sector 0
nbd14: Attempted send on closed socket
end_request: I/O error, dev nbd14, sector 4294965120
nbd14: Attempted send on closed socket
end_request: I/O error, dev nbd14, sector 0
nbd15: Attempted send on closed socket
end_request: I/O error, dev nbd15, sector 4294965120
nbd15: Attempted send on closed socket
end_request: I/O error, dev nbd15, sector 0
nbd0: Attempted send on closed socket
end_request: I/O error, dev nbd0, sector 0
nbd1: Attempted send on closed socket
end_request: I/O error, dev nbd1, sector 0
nbd2: Attempted send on closed socket
end_request: I/O error, dev nbd2, sector 0
nbd3: Attempted send on closed socket
end_request: I/O error, dev nbd3, sector 0
nbd4: Attempted send on closed socket
end_request: I/O error, dev nbd4, sector 0
nbd5: Attempted send on closed socket
end_request: I/O error, dev nbd5, sector 0
nbd6: Attempted send on closed socket
end_request: I/O error, dev nbd6, sector 0
nbd7: Attempted send on closed socket
end_request: I/O error, dev nbd7, sector 0
nbd8: Attempted send on closed socket
end_request: I/O error, dev nbd8, sector 0
nbd9: Attempted send on closed socket
end_request: I/O error, dev nbd9, sector 0
nbd10: Attempted send on closed socket
end_request: I/O error, dev nbd10, sector 0
nbd11: Attempted send on closed socket
end_request: I/O error, dev nbd11, sector 0
nbd12: Attempted send on closed socket
end_request: I/O error, dev nbd12, sector 0
nbd13: Attempted send on closed socket
end_request: I/O error, dev nbd13, sector 0
nbd14: Attempted send on closed socket
end_request: I/O error, dev nbd14, sector 0
nbd15: Attempted send on closed socket
end_request: I/O error, dev nbd15, sector 0
loop: loaded (max 8 devices)
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb3, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
NTFS volume version 3.1.
Thanks for any help,

Jack
 
Old 06-29-2007, 01:27 PM   #2
jschiwal
LQ Guru
 
Registered: Aug 2001
Location: Fargo, ND
Distribution: SuSE AMD64
Posts: 15,733

Rep: Reputation: 682Reputation: 682Reputation: 682Reputation: 682Reputation: 682Reputation: 682
Are you using nbd? It is an odd duck. You need to have a client on your computer and a server on the remote host:
Code:
   Howto: To setup nbd, you can simply do the following:

   First, serve a device or file from a remote server:

   nbd-server <port-number> <device-or-file-to-serve-to-client>

   e.g.,
        root@server1 # nbd-server 1234 /dev/sdb1

        (serves sdb1 partition on TCP port 1234)

   Then, on the local (client) system:

   nbd-client <server-name-or-IP> <server-port-number> /dev/nb[0-n]

   e.g.,
        root@client1 # nbd-client server1 1234 /dev/nb0

        (creates the nb0 device on client1)
If you aren't using it, you might not want to have the module loaded in the kernel (or did you answer Y instead of M in xconfig?).
 
Old 06-29-2007, 01:33 PM   #3
tntcoder
Member
 
Registered: Sep 2003
Distribution: Arch
Posts: 89

Original Poster
Rep: Reputation: 15
Ah thanks alot, looks like i ticked it by mistake will try a recompile without it.

Thanks for the help.
 
  


Reply



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 On
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
strange errors while compiling kernel... rubella Linux - Newbie 1 03-17-2006 03:17 AM
strange errors eltn Programming 2 10-29-2004 09:43 PM
CD-R(W) works but strange errors Kristian2 Slackware - Installation 1 06-05-2004 01:54 PM
Strange errors XPediTioN Slackware 1 07-11-2003 05:45 PM
Strange Errors in C++ ReverseLogic Programming 3 01-20-2003 11:56 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - General

All times are GMT -5. The time now is 04:50 PM.

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
Open Source Consulting | Domain Registration