[gentoo-user] Weird "Buffer I/O error" in dev ndb0

[gentoo-user] Weird "Buffer I/O error" in dev ndb0

[Phill MV]

[-- Attachment #1: Type: text/plain, Size: 16259 bytes --]

Evertyime I boot up I gett a long string of weird buffer errors shortly
after udev starts up;
stuff like

nbd0: Request when not-ready
end_request: I/O error, dev nbd0, sector 4294965120

where ndb0 changes up to ndb12.

I still have no clue what dev/ndb0 refers to, but the computer still seems
to be running fine.
fsck'ing the drives revealed nothing and I might run a memory test later on.
(some part of me fears it's my ram, tho, which sounds like it'd make sense.
)


Any ideas?



dmesg follows.

hif bin # dmesg
hda1 hda2 hda3 hda4 < hda5 >
hdb: max request size: 128KiB
hdb: 78156288 sectors (40016 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(133)
hdb: cache flushes supported
hdb: hdb1
hdc: ATAPI 48X CD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
hdd: ATAPI 24X CD-ROM drive, 128kB Cache, UDMA(33)
ide-floppy driver 0.99.newide
libata version 1.11 loaded.
ieee1394: raw1394: /dev/raw1394 device initialized
usbmon: debugs is not available
ACPI: PCI Interrupt Link [LNKE] enabled at IRQ 10
PCI: setting IRQ 10 as level-triggered
ACPI: PCI Interrupt 0000:00:10.3[D] -> Link [LNKE] -> GSI 10 (level, low) ->
IRQ 10
ehci_hcd 0000:00:10.3: VIA Technologies, Inc. USB 2.0
ehci_hcd 0000:00:10.3: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:10.3: irq 10, io mem 0xe8800000
ehci_hcd 0000:00:10.3: USB 2.0 initialized, EHCI 1.00, driver 10 Dec 2004
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 6 ports detected
ohci_hcd: 2004 Nov 08 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
USB Universal Host Controller Interface driver v2.2
ACPI: PCI Interrupt 0000:00:10.0[A] -> Link [LNKE] -> GSI 10 (level, low) ->
IRQ 10
uhci_hcd 0000:00:10.0: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1Controller
uhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:10.0: irq 10, io base 0x0000d800
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:10.1[B] -> Link [LNKE] -> GSI 10 (level, low) ->
IRQ 10
uhci_hcd 0000:00:10.1: VIA Technologies, Inc. VT82xxxxx UHCI USB
1.1Controller (#2)
uhci_hcd 0000:00:10.1: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:10.1: irq 10, io base 0x0000d400
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:10.2[C] -> Link [LNKE] -> GSI 10 (level, low) ->
IRQ 10
uhci_hcd 0000:00:10.2: VIA Technologies, Inc. VT82xxxxx UHCI USB
1.1Controller (#3)
uhci_hcd 0000:00:10.2: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:10.2: irq 10, io base 0x0000d000
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
usbcore: registered new driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
Initializing USB Mass Storage driver...
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.01:USB HID core driver
Advanced Linux Sound Architecture Driver Version 1.0.9rc2 (Thu Mar 24
10:33:39 2005 UTC).
ACPI: PCI Interrupt Link [LNKF] enabled at IRQ 3
PCI: setting IRQ 3 as level-triggered
ACPI: PCI Interrupt 0000:00:11.5[C] -> Link [LNKF] -> GSI 3 (level, low) ->
IRQ 3
PCI: Setting latency timer of device 0000:00:11.5 to 64
codec_read: codec 0 is not valid [0x107e5370]
codec_read: codec 0 is not valid [0x107e5370]
codec_read: codec 0 is not valid [0x107e5370]
codec_read: codec 0 is not valid [0x107e5370]
ALSA device list:
#0: VIA 8235 with AD1980 at 0xe000, irq 3
oprofile: using timer interrupt.
NET: Registered protocol family 2
IP: routing cache hash table of 2048 buckets, 16Kbytes
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
ip_conntrack version 2.1 (2047 buckets, 16376 max) - 212 bytes per conntrack
ip_tables: (C) 2000-2002 Netfilter core team
ipt_recent v0.3.1: Stephen Frost <sfrost@snowman.net>.
http://snowman.net/projects/ipt_recent/
arp_tables: (C) 2002 David S. Miller
NET: Registered protocol family 1
NET: Registered protocol family 17
ACPI wakeup devices:
PCI0 PCI1 USB0 USB1 USB2 SU20 SLAN
ACPI: (supports S0 S1 S4 S5)
ReiserFS: hda3: found reiserfs format "3.6" with standard journal
ReiserFS: hda3: using ordered data mode
ReiserFS: hda3: journal params: device hda3, size 8192, journal first block
18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: hda3: checking transaction log (hda3)
ReiserFS: hda3: journal-1153: found in header: first_unflushed_offset 6104,
last_flushed_trans_id 917135
ReiserFS: hda3: journal-1206: Starting replay from offset 3939069125990360,
trans_id 0
ReiserFS: hda3: journal-1299: Setting newest_mount_id to 307
ReiserFS: hda3: Using r5 hash to sort names
VFS: Mounted root (reiserfs filesystem) readonly.
Freeing unused kernel memory: 200k freed
nbd0: Request when not-ready
end_request: I/O error, dev nbd0, sector 4294965120
Buffer I/O error on device nbd0, logical block 536870640
nbd0: Request when not-ready
end_request: I/O error, dev nbd0, sector 4294965120
Buffer I/O error on device nbd0, logical block 536870640
nbd0: Request when not-ready
end_request: I/O error, dev nbd0, sector 4294964992
Buffer I/O error on device nbd0, logical block 536870624
nbd0: Request when not-ready
end_request: I/O error, dev nbd0, sector 4294964992
Buffer I/O error on device nbd0, logical block 536870624
nbd0: Request when not-ready
end_request: I/O error, dev nbd0, sector 4294964992
Buffer I/O error on device nbd0, logical block 536870624
nbd0: Request when not-ready
end_request: I/O error, dev nbd0, sector 4294964848
Buffer I/O error on device nbd0, logical block 536870606
nbd0: Request when not-ready
end_request: I/O error, dev nbd0, sector 4294964848
Buffer I/O error on device nbd0, logical block 536870606
nbd1: Request when not-ready
end_request: I/O error, dev nbd1, sector 4294965120
Buffer I/O error on device nbd1, logical block 536870640
nbd1: Request when not-ready
end_request: I/O error, dev nbd1, sector 4294965120
Buffer I/O error on device nbd1, logical block 536870640
nbd1: Request when not-ready
end_request: I/O error, dev nbd1, sector 4294964992
Buffer I/O error on device nbd1, logical block 536870624
nbd1: Request when not-ready
end_request: I/O error, dev nbd1, sector 4294964992
nbd1: Request when not-ready
end_request: I/O error, dev nbd1, sector 4294964992
nbd1: Request when not-ready
end_request: I/O error, dev nbd1, sector 4294964848
nbd1: Request when not-ready
end_request: I/O error, dev nbd1, sector 4294964848
nbd10: Request when not-ready
end_request: I/O error, dev nbd10, sector 4294965120
nbd10: Request when not-ready
end_request: I/O error, dev nbd10, sector 4294965120
nbd10: Request when not-ready
end_request: I/O error, dev nbd10, sector 4294964992
nbd10: Request when not-ready
end_request: I/O error, dev nbd10, sector 4294964992
nbd10: Request when not-ready
end_request: I/O error, dev nbd10, sector 4294964992
nbd10: Request when not-ready
end_request: I/O error, dev nbd10, sector 4294964848
nbd10: Request when not-ready
end_request: I/O error, dev nbd10, sector 4294964848
nbd11: Request when not-ready
end_request: I/O error, dev nbd11, sector 4294965120
nbd11: Request when not-ready
end_request: I/O error, dev nbd11, sector 4294965120
nbd11: Request when not-ready
end_request: I/O error, dev nbd11, sector 4294964992
nbd11: Request when not-ready
end_request: I/O error, dev nbd11, sector 4294964992
nbd11: Request when not-ready
end_request: I/O error, dev nbd11, sector 4294964992
nbd11: Request when not-ready
end_request: I/O error, dev nbd11, sector 4294964848
nbd11: Request when not-ready
end_request: I/O error, dev nbd11, sector 4294964848
nbd12: Request when not-ready
end_request: I/O error, dev nbd12, sector 4294965120
nbd12: Request when not-ready
end_request: I/O error, dev nbd12, sector 4294965120
nbd12: Request when not-ready
end_request: I/O error, dev nbd12, sector 4294964992
nbd12: Request when not-ready
end_request: I/O error, dev nbd12, sector 4294964992
nbd12: Request when not-ready
end_request: I/O error, dev nbd12, sector 4294964992
nbd12: Request when not-ready
end_request: I/O error, dev nbd12, sector 4294964848
nbd12: Request when not-ready
end_request: I/O error, dev nbd12, sector 4294964848
nbd13: Request when not-ready
end_request: I/O error, dev nbd13, sector 4294965120
nbd13: Request when not-ready
end_request: I/O error, dev nbd13, sector 4294965120
nbd13: Request when not-ready
end_request: I/O error, dev nbd13, sector 4294964992
nbd13: Request when not-ready
end_request: I/O error, dev nbd13, sector 4294964992
nbd13: Request when not-ready
end_request: I/O error, dev nbd13, sector 4294964992
nbd13: Request when not-ready
end_request: I/O error, dev nbd13, sector 4294964848
nbd13: Request when not-ready
end_request: I/O error, dev nbd13, sector 4294964848
nbd14: Request when not-ready
end_request: I/O error, dev nbd14, sector 4294965120
nbd14: Request when not-ready
end_request: I/O error, dev nbd14, sector 4294965120
nbd14: Request when not-ready
end_request: I/O error, dev nbd14, sector 4294964992
nbd14: Request when not-ready
end_request: I/O error, dev nbd14, sector 4294964992
nbd14: Request when not-ready
end_request: I/O error, dev nbd14, sector 4294964992
nbd14: Request when not-ready
end_request: I/O error, dev nbd14, sector 4294964848
nbd14: Request when not-ready
end_request: I/O error, dev nbd14, sector 4294964848
nbd15: Request when not-ready
end_request: I/O error, dev nbd15, sector 4294965120
nbd15: Request when not-ready
end_request: I/O error, dev nbd15, sector 4294965120
nbd15: Request when not-ready
end_request: I/O error, dev nbd15, sector 4294964992
nbd15: Request when not-ready
end_request: I/O error, dev nbd15, sector 4294964992
nbd15: Request when not-ready
end_request: I/O error, dev nbd15, sector 4294964992
nbd15: Request when not-ready
end_request: I/O error, dev nbd15, sector 4294964848
nbd15: Request when not-ready
end_request: I/O error, dev nbd15, sector 4294964848
nbd2: Request when not-ready
end_request: I/O error, dev nbd2, sector 4294965120
nbd2: Request when not-ready
end_request: I/O error, dev nbd2, sector 4294965120
nbd2: Request when not-ready
end_request: I/O error, dev nbd2, sector 4294964992
nbd2: Request when not-ready
end_request: I/O error, dev nbd2, sector 4294964992
nbd2: Request when not-ready
end_request: I/O error, dev nbd2, sector 4294964992
nbd2: Request when not-ready
end_request: I/O error, dev nbd2, sector 4294964848
nbd2: Request when not-ready
end_request: I/O error, dev nbd2, sector 4294964848
nbd3: Request when not-ready
end_request: I/O error, dev nbd3, sector 4294965120
nbd3: Request when not-ready
end_request: I/O error, dev nbd3, sector 4294965120
nbd3: Request when not-ready
end_request: I/O error, dev nbd3, sector 4294964992
nbd3: Request when not-ready
end_request: I/O error, dev nbd3, sector 4294964992
nbd3: Request when not-ready
end_request: I/O error, dev nbd3, sector 4294964992
nbd3: Request when not-ready
end_request: I/O error, dev nbd3, sector 4294964848
nbd3: Request when not-ready
end_request: I/O error, dev nbd3, sector 4294964848
nbd4: Request when not-ready
end_request: I/O error, dev nbd4, sector 4294965120
nbd4: Request when not-ready
end_request: I/O error, dev nbd4, sector 4294965120
nbd4: Request when not-ready
end_request: I/O error, dev nbd4, sector 4294964992
nbd4: Request when not-ready
end_request: I/O error, dev nbd4, sector 4294964992
nbd4: Request when not-ready
end_request: I/O error, dev nbd4, sector 4294964992
nbd4: Request when not-ready
end_request: I/O error, dev nbd4, sector 4294964848
nbd4: Request when not-ready
end_request: I/O error, dev nbd4, sector 4294964848
nbd5: Request when not-ready
end_request: I/O error, dev nbd5, sector 4294965120
nbd5: Request when not-ready
end_request: I/O error, dev nbd5, sector 4294965120
nbd5: Request when not-ready
end_request: I/O error, dev nbd5, sector 4294964992
nbd5: Request when not-ready
end_request: I/O error, dev nbd5, sector 4294964992
nbd5: Request when not-ready
end_request: I/O error, dev nbd5, sector 4294964992
nbd5: Request when not-ready
end_request: I/O error, dev nbd5, sector 4294964848
nbd5: Request when not-ready
end_request: I/O error, dev nbd5, sector 4294964848
nbd6: Request when not-ready
end_request: I/O error, dev nbd6, sector 4294965120
nbd6: Request when not-ready
end_request: I/O error, dev nbd6, sector 4294965120
nbd6: Request when not-ready
end_request: I/O error, dev nbd6, sector 4294964992
nbd6: Request when not-ready
end_request: I/O error, dev nbd6, sector 4294964992
nbd6: Request when not-ready
end_request: I/O error, dev nbd6, sector 4294964992
nbd6: Request when not-ready
end_request: I/O error, dev nbd6, sector 4294964848
nbd6: Request when not-ready
end_request: I/O error, dev nbd6, sector 4294964848
nbd7: Request when not-ready
end_request: I/O error, dev nbd7, sector 4294965120
nbd7: Request when not-ready
end_request: I/O error, dev nbd7, sector 4294965120
nbd7: Request when not-ready
end_request: I/O error, dev nbd7, sector 4294964992
nbd7: Request when not-ready
end_request: I/O error, dev nbd7, sector 4294964992
nbd7: Request when not-ready
end_request: I/O error, dev nbd7, sector 4294964992
nbd7: Request when not-ready
end_request: I/O error, dev nbd7, sector 4294964848
nbd7: Request when not-ready
end_request: I/O error, dev nbd7, sector 4294964848
nbd8: Request when not-ready
end_request: I/O error, dev nbd8, sector 4294965120
nbd8: Request when not-ready
end_request: I/O error, dev nbd8, sector 4294965120
nbd8: Request when not-ready
end_request: I/O error, dev nbd8, sector 4294964992
nbd8: Request when not-ready
end_request: I/O error, dev nbd8, sector 4294964992
nbd8: Request when not-ready
end_request: I/O error, dev nbd8, sector 4294964992
nbd8: Request when not-ready
end_request: I/O error, dev nbd8, sector 4294964848
nbd8: Request when not-ready
end_request: I/O error, dev nbd8, sector 4294964848
nbd9: Request when not-ready
end_request: I/O error, dev nbd9, sector 4294965120
nbd9: Request when not-ready
end_request: I/O error, dev nbd9, sector 4294965120
nbd9: Request when not-ready
end_request: I/O error, dev nbd9, sector 4294964992
nbd9: Request when not-ready
end_request: I/O error, dev nbd9, sector 4294964992
nbd9: Request when not-ready
end_request: I/O error, dev nbd9, sector 4294964992
nbd9: Request when not-ready
end_request: I/O error, dev nbd9, sector 4294964848
nbd9: Request when not-ready
end_request: I/O error, dev nbd9, sector 4294964848
Adding 923696k swap on /dev/hda5. Priority:-1 extents:1
nvidia: module license 'NVIDIA' taints kernel.
PCI: Enabling device 0000:00:0a.0 (0000 -> 0002)
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11
PCI: setting IRQ 11 as level-triggered
ACPI: PCI Interrupt 0000:00:0a.0[A] -> Link [LNKA] -> GSI 11 (level, low) ->
IRQ 11
ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LNKA] -> GSI 11 (level, low) ->
IRQ 11
NVRM: loading NVIDIA Linux x86 NVIDIA Kernel Module 1.0-6629 Wed Nov 3
13:12:51 PST 2004
ReiserFS: hdb1: found reiserfs format "3.6" with standard journal
ReiserFS: hdb1: warning: CONFIG_REISERFS_CHECK is set ON
ReiserFS: hdb1: warning: - it is slow mode for debugging.
ReiserFS: hdb1: using ordered data mode
ReiserFS: hdb1: journal params: device hdb1, size 8192, journal first block
18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: hdb1: checking transaction log (hdb1)
ReiserFS: hdb1: journal-1153: found in header: first_unflushed_offset 3344,
last_flushed_trans_id 11825
ReiserFS: hdb1: journal-1206: Starting replay from offset 50792283245840,
trans_id 0
ReiserFS: hdb1: journal-1299: Setting newest_mount_id to 288
ReiserFS: hdb1: Using r5 hash to sort names
eth0: link up, 100Mbps, full-duplex, lpa 0xFFFF

[-- Attachment #2: Type: text/html, Size: 17929 bytes --]

Re: [gentoo-user] Weird "Buffer I/O error" in dev ndb0

[Matthias Guede]

Phill MV wrote:
> Evertyime I boot up I gett a long string of weird buffer errors shortly 
> after udev starts up;
> stuff like
> 
> nbd0: Request when not-ready
> end_request: I/O error, dev nbd0, sector 4294965120
> 
> where ndb0 changes up to ndb12.
> 
> I still have no clue what dev/ndb0 refers to,  but the computer still 
> seems to be running fine.
> fsck'ing the drives revealed nothing and I might run a memory test later on.
> (some part of me fears it's my ram, tho, which sounds like it'd make 
> sense. )


Seems like you have the Network Block Device compiled in your Kernel 
(Device Driver -> Block devices) and somebody probes these devices now 
at bootup.


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Weird "Buffer I/O error" in dev ndb0

[Holly Bostick]

Matthias Guede schreef:
> Phill MV wrote:
> 
>> Evertyime I boot up I gett a long string of weird buffer errors 
>> shortly after udev starts up; stuff like
>> 
>> nbd0: Request when not-ready end_request: I/O error, dev nbd0, 
>> sector 4294965120
>> 
>> where ndb0 changes up to ndb12.
>> 
>> I still have no clue what dev/ndb0 refers to,  but the computer 
>> still seems to be running fine. fsck'ing the drives revealed 
>> nothing and I might run a memory test later on. (some part of me 
>> fears it's my ram, tho, which sounds like it'd make sense. )
> 
> 
> 
> Seems like you have the Network Block Device compiled in your Kernel
>  (Device Driver -> Block devices) and somebody probes these devices 
> now at bootup.
> 
> 

Yes, I was getting the same errors/warnings; it finally annoyed me so
much that I recompiled the kernel without NBD support, since I couldn't
find any suggestion that I actually needed it, and all was well after
that. Certainly I didn't find that anything which had been working got
broke due to the removal-- but that wasn't a big surprise, since the
errors/warnings suggested that a function was being probed that did not
exist anyway (so I wasn't actually using NBD in the first place, which
was what it seemed to be complaining about).

HTH,
Holly
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Weird "Buffer I/O error" in dev ndb0

[Heinz Sporn]

Am Dienstag, den 27.09.2005, 01:31 -0400 schrieb Phill MV:
> Evertyime I boot up I gett a long string of weird buffer errors
> shortly after udev starts up;
> stuff like 
> 
> nbd0: Request when not-ready
> end_request: I/O error, dev nbd0, sector 4294965120
> 
> where ndb0 changes up to ndb12.
> 

Same here. Found a post that recommended compiling it as module. Problem
solved.

> I still have no clue what dev/ndb0 refers to,  but the computer still
> seems to be running fine.
> fsck'ing the drives revealed nothing and I might run a memory test
> later on.
> (some part of me fears it's my ram, tho, which sounds like it'd make
> sense. )
> 
> 
> Any ideas?
> 
> 
> 
> dmesg follows.
> 
> hif bin # dmesg
> hda1 hda2 hda3 hda4 < hda5 >
> hdb: max request size: 128KiB
> hdb: 78156288 sectors (40016 MB) w/2048KiB Cache, CHS=65535/16/63,
> UDMA(133)
> hdb: cache flushes supported
>  hdb: hdb1
> hdc: ATAPI 48X CD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33)
> Uniform CD-ROM driver Revision: 3.20
> hdd: ATAPI 24X CD-ROM drive, 128kB Cache, UDMA(33)
> ide-floppy driver 0.99.newide
> libata version 1.11 loaded.
> ieee1394: raw1394: /dev/raw1394 device initialized
> usbmon: debugs is not available
> ACPI: PCI Interrupt Link [LNKE] enabled at IRQ 10
> PCI: setting IRQ 10 as level-triggered
> ACPI: PCI Interrupt 0000:00:10.3[D] -> Link [LNKE] -> GSI 10 (level,
> low) -> IRQ 10
> ehci_hcd 0000:00:10.3: VIA Technologies, Inc. USB 2.0
> ehci_hcd 0000:00:10.3: new USB bus registered, assigned bus number 1
> ehci_hcd 0000:00:10.3: irq 10, io mem 0xe8800000
> ehci_hcd 0000:00:10.3: USB 2.0 initialized, EHCI 1.00, driver 10 Dec
> 2004
> hub 1-0:1.0: USB hub found
> hub 1-0:1.0: 6 ports detected
> ohci_hcd: 2004 Nov 08 USB 1.1 'Open' Host Controller (OHCI) Driver
> (PCI)
> USB Universal Host Controller Interface driver v2.2
> ACPI: PCI Interrupt 0000:00:10.0[A] -> Link [LNKE] -> GSI 10 (level,
> low) -> IRQ 10
> uhci_hcd 0000:00:10.0: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
> Controller
> uhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 2
> uhci_hcd 0000:00:10.0: irq 10, io base 0x0000d800
> hub 2-0:1.0: USB hub found
> hub 2-0:1.0: 2 ports detected
> ACPI: PCI Interrupt 0000:00:10.1[B] -> Link [LNKE] -> GSI 10 (level,
> low) -> IRQ 10
> uhci_hcd 0000:00:10.1: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
> Controller (#2)
> uhci_hcd 0000:00:10.1: new USB bus registered, assigned bus number 3
> uhci_hcd 0000:00:10.1: irq 10, io base 0x0000d400
> hub 3-0:1.0: USB hub found
> hub 3-0:1.0: 2 ports detected
> ACPI: PCI Interrupt 0000:00:10.2[C] -> Link [LNKE] -> GSI 10 (level,
> low) -> IRQ 10
> uhci_hcd 0000:00:10.2: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
> Controller (#3)
> uhci_hcd 0000:00:10.2: new USB bus registered, assigned bus number 4
> uhci_hcd 0000:00:10.2: irq 10, io base 0x0000d000
> hub 4-0:1.0: USB hub found
> hub 4-0:1.0: 2 ports detected
> usbcore: registered new driver usblp
> drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
> Initializing USB Mass Storage driver...
> usbcore: registered new driver usb-storage
> USB Mass Storage support registered.
> usbcore: registered new driver usbhid
> drivers/usb/input/hid-core.c: v2.01:USB HID core driver
> Advanced Linux Sound Architecture Driver Version 1.0.9rc2  (Thu Mar 24
> 10:33:39 2005 UTC).
> ACPI: PCI Interrupt Link [LNKF] enabled at IRQ 3
> PCI: setting IRQ 3 as level-triggered
> ACPI: PCI Interrupt 0000:00:11.5[C] -> Link [LNKF] -> GSI 3 (level,
> low) -> IRQ 3
> PCI: Setting latency timer of device 0000:00:11.5 to 64
> codec_read: codec 0 is not valid [0x107e5370]
> codec_read: codec 0 is not valid [0x107e5370]
> codec_read: codec 0 is not valid [0x107e5370]
> codec_read: codec 0 is not valid [0x107e5370]
> ALSA device list:
>   #0: VIA 8235 with AD1980 at 0xe000, irq 3
> oprofile: using timer interrupt.
> NET: Registered protocol family 2
> IP: routing cache hash table of 2048 buckets, 16Kbytes
> TCP established hash table entries: 16384 (order: 5, 131072 bytes)
> TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
> TCP: Hash tables configured (established 16384 bind 16384)
> ip_conntrack version 2.1 (2047 buckets, 16376 max) - 212 bytes per
> conntrack
> ip_tables: (C) 2000-2002 Netfilter core team
> ipt_recent v0.3.1: Stephen Frost <sfrost@snowman.net>.
> http://snowman.net/projects/ipt_recent/
> arp_tables: (C) 2002 David S. Miller
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> ACPI wakeup devices:
> PCI0 PCI1 USB0 USB1 USB2 SU20 SLAN
> ACPI: (supports S0 S1 S4 S5)
> ReiserFS: hda3: found reiserfs format "3.6" with standard journal
> ReiserFS: hda3: using ordered data mode
> ReiserFS: hda3: journal params: device hda3, size 8192, journal first
> block 18, max trans len 1024, max batch 900, max commit age 30, max
> trans age 30
> ReiserFS: hda3: checking transaction log (hda3)
> ReiserFS: hda3: journal-1153: found in header: first_unflushed_offset
> 6104, last_flushed_trans_id 917135
> ReiserFS: hda3: journal-1206: Starting replay from offset
> 3939069125990360, trans_id 0
> ReiserFS: hda3: journal-1299: Setting newest_mount_id to 307
> ReiserFS: hda3: Using r5 hash to sort names
> VFS: Mounted root (reiserfs filesystem) readonly.
> Freeing unused kernel memory: 200k freed
> nbd0: Request when not-ready
> end_request: I/O error, dev nbd0, sector 4294965120
> Buffer I/O error on device nbd0, logical block 536870640
> nbd0: Request when not-ready
> end_request: I/O error, dev nbd0, sector 4294965120
> Buffer I/O error on device nbd0, logical block 536870640
> nbd0: Request when not-ready
> end_request: I/O error, dev nbd0, sector 4294964992
> Buffer I/O error on device nbd0, logical block 536870624
> nbd0: Request when not-ready
> end_request: I/O error, dev nbd0, sector 4294964992
> Buffer I/O error on device nbd0, logical block 536870624
> nbd0: Request when not-ready
> end_request: I/O error, dev nbd0, sector 4294964992
> Buffer I/O error on device nbd0, logical block 536870624
> nbd0: Request when not-ready
> end_request: I/O error, dev nbd0, sector 4294964848
> Buffer I/O error on device nbd0, logical block 536870606
> nbd0: Request when not-ready
> end_request: I/O error, dev nbd0, sector 4294964848
> Buffer I/O error on device nbd0, logical block 536870606
> nbd1: Request when not-ready
> end_request: I/O error, dev nbd1, sector 4294965120
> Buffer I/O error on device nbd1, logical block 536870640
> nbd1: Request when not-ready
> end_request: I/O error, dev nbd1, sector 4294965120
> Buffer I/O error on device nbd1, logical block 536870640
> nbd1: Request when not-ready
> end_request: I/O error, dev nbd1, sector 4294964992
> Buffer I/O error on device nbd1, logical block 536870624
> nbd1: Request when not-ready
> end_request: I/O error, dev nbd1, sector 4294964992
> nbd1: Request when not-ready
> end_request: I/O error, dev nbd1, sector 4294964992
> nbd1: Request when not-ready
> end_request: I/O error, dev nbd1, sector 4294964848
> nbd1: Request when not-ready
> end_request: I/O error, dev nbd1, sector 4294964848
> nbd10: Request when not-ready
> end_request: I/O error, dev nbd10, sector 4294965120
> nbd10: Request when not-ready
> end_request: I/O error, dev nbd10, sector 4294965120
> nbd10: Request when not-ready
> end_request: I/O error, dev nbd10, sector 4294964992
> nbd10: Request when not-ready
> end_request: I/O error, dev nbd10, sector 4294964992
> nbd10: Request when not-ready
> end_request: I/O error, dev nbd10, sector 4294964992
> nbd10: Request when not-ready
> end_request: I/O error, dev nbd10, sector 4294964848
> nbd10: Request when not-ready
> end_request: I/O error, dev nbd10, sector 4294964848
> nbd11: Request when not-ready
> end_request: I/O error, dev nbd11, sector 4294965120
> nbd11: Request when not-ready
> end_request: I/O error, dev nbd11, sector 4294965120
> nbd11: Request when not-ready
> end_request: I/O error, dev nbd11, sector 4294964992
> nbd11: Request when not-ready
> end_request: I/O error, dev nbd11, sector 4294964992
> nbd11: Request when not-ready
> end_request: I/O error, dev nbd11, sector 4294964992
> nbd11: Request when not-ready
> end_request: I/O error, dev nbd11, sector 4294964848
> nbd11: Request when not-ready
> end_request: I/O error, dev nbd11, sector 4294964848
> nbd12: Request when not-ready
> end_request: I/O error, dev nbd12, sector 4294965120
> nbd12: Request when not-ready
> end_request: I/O error, dev nbd12, sector 4294965120
> nbd12: Request when not-ready
> end_request: I/O error, dev nbd12, sector 4294964992
> nbd12: Request when not-ready
> end_request: I/O error, dev nbd12, sector 4294964992
> nbd12: Request when not-ready
> end_request: I/O error, dev nbd12, sector 4294964992
> nbd12: Request when not-ready
> end_request: I/O error, dev nbd12, sector 4294964848
> nbd12: Request when not-ready
> end_request: I/O error, dev nbd12, sector 4294964848
> nbd13: Request when not-ready
> end_request: I/O error, dev nbd13, sector 4294965120
> nbd13: Request when not-ready
> end_request: I/O error, dev nbd13, sector 4294965120
> nbd13: Request when not-ready
> end_request: I/O error, dev nbd13, sector 4294964992
> nbd13: Request when not-ready
> end_request: I/O error, dev nbd13, sector 4294964992
> nbd13: Request when not-ready
> end_request: I/O error, dev nbd13, sector 4294964992
> nbd13: Request when not-ready
> end_request: I/O error, dev nbd13, sector 4294964848
> nbd13: Request when not-ready
> end_request: I/O error, dev nbd13, sector 4294964848
> nbd14: Request when not-ready
> end_request: I/O error, dev nbd14, sector 4294965120
> nbd14: Request when not-ready
> end_request: I/O error, dev nbd14, sector 4294965120
> nbd14: Request when not-ready
> end_request: I/O error, dev nbd14, sector 4294964992
> nbd14: Request when not-ready
> end_request: I/O error, dev nbd14, sector 4294964992
> nbd14: Request when not-ready
> end_request: I/O error, dev nbd14, sector 4294964992
> nbd14: Request when not-ready
> end_request: I/O error, dev nbd14, sector 4294964848
> nbd14: Request when not-ready
> end_request: I/O error, dev nbd14, sector 4294964848
> nbd15: Request when not-ready
> end_request: I/O error, dev nbd15, sector 4294965120
> nbd15: Request when not-ready
> end_request: I/O error, dev nbd15, sector 4294965120
> nbd15: Request when not-ready
> end_request: I/O error, dev nbd15, sector 4294964992
> nbd15: Request when not-ready
> end_request: I/O error, dev nbd15, sector 4294964992
> nbd15: Request when not-ready
> end_request: I/O error, dev nbd15, sector 4294964992
> nbd15: Request when not-ready
> end_request: I/O error, dev nbd15, sector 4294964848
> nbd15: Request when not-ready
> end_request: I/O error, dev nbd15, sector 4294964848
> nbd2: Request when not-ready
> end_request: I/O error, dev nbd2, sector 4294965120
> nbd2: Request when not-ready
> end_request: I/O error, dev nbd2, sector 4294965120
> nbd2: Request when not-ready
> end_request: I/O error, dev nbd2, sector 4294964992
> nbd2: Request when not-ready
> end_request: I/O error, dev nbd2, sector 4294964992
> nbd2: Request when not-ready
> end_request: I/O error, dev nbd2, sector 4294964992
> nbd2: Request when not-ready
> end_request: I/O error, dev nbd2, sector 4294964848
> nbd2: Request when not-ready
> end_request: I/O error, dev nbd2, sector 4294964848
> nbd3: Request when not-ready
> end_request: I/O error, dev nbd3, sector 4294965120
> nbd3: Request when not-ready
> end_request: I/O error, dev nbd3, sector 4294965120
> nbd3: Request when not-ready
> end_request: I/O error, dev nbd3, sector 4294964992
> nbd3: Request when not-ready
> end_request: I/O error, dev nbd3, sector 4294964992
> nbd3: Request when not-ready
> end_request: I/O error, dev nbd3, sector 4294964992
> nbd3: Request when not-ready
> end_request: I/O error, dev nbd3, sector 4294964848
> nbd3: Request when not-ready
> end_request: I/O error, dev nbd3, sector 4294964848
> nbd4: Request when not-ready
> end_request: I/O error, dev nbd4, sector 4294965120
> nbd4: Request when not-ready
> end_request: I/O error, dev nbd4, sector 4294965120
> nbd4: Request when not-ready
> end_request: I/O error, dev nbd4, sector 4294964992
> nbd4: Request when not-ready
> end_request: I/O error, dev nbd4, sector 4294964992
> nbd4: Request when not-ready
> end_request: I/O error, dev nbd4, sector 4294964992
> nbd4: Request when not-ready
> end_request: I/O error, dev nbd4, sector 4294964848
> nbd4: Request when not-ready
> end_request: I/O error, dev nbd4, sector 4294964848
> nbd5: Request when not-ready
> end_request: I/O error, dev nbd5, sector 4294965120
> nbd5: Request when not-ready
> end_request: I/O error, dev nbd5, sector 4294965120
> nbd5: Request when not-ready
> end_request: I/O error, dev nbd5, sector 4294964992
> nbd5: Request when not-ready
> end_request: I/O error, dev nbd5, sector 4294964992
> nbd5: Request when not-ready
> end_request: I/O error, dev nbd5, sector 4294964992
> nbd5: Request when not-ready
> end_request: I/O error, dev nbd5, sector 4294964848
> nbd5: Request when not-ready
> end_request: I/O error, dev nbd5, sector 4294964848
> nbd6: Request when not-ready
> end_request: I/O error, dev nbd6, sector 4294965120
> nbd6: Request when not-ready
> end_request: I/O error, dev nbd6, sector 4294965120
> nbd6: Request when not-ready
> end_request: I/O error, dev nbd6, sector 4294964992
> nbd6: Request when not-ready
> end_request: I/O error, dev nbd6, sector 4294964992
> nbd6: Request when not-ready
> end_request: I/O error, dev nbd6, sector 4294964992
> nbd6: Request when not-ready
> end_request: I/O error, dev nbd6, sector 4294964848
> nbd6: Request when not-ready
> end_request: I/O error, dev nbd6, sector 4294964848
> nbd7: Request when not-ready
> end_request: I/O error, dev nbd7, sector 4294965120
> nbd7: Request when not-ready
> end_request: I/O error, dev nbd7, sector 4294965120
> nbd7: Request when not-ready
> end_request: I/O error, dev nbd7, sector 4294964992
> nbd7: Request when not-ready
> end_request: I/O error, dev nbd7, sector 4294964992
> nbd7: Request when not-ready
> end_request: I/O error, dev nbd7, sector 4294964992
> nbd7: Request when not-ready
> end_request: I/O error, dev nbd7, sector 4294964848
> nbd7: Request when not-ready
> end_request: I/O error, dev nbd7, sector 4294964848
> nbd8: Request when not-ready
> end_request: I/O error, dev nbd8, sector 4294965120
> nbd8: Request when not-ready
> end_request: I/O error, dev nbd8, sector 4294965120
> nbd8: Request when not-ready
> end_request: I/O error, dev nbd8, sector 4294964992
> nbd8: Request when not-ready
> end_request: I/O error, dev nbd8, sector 4294964992
> nbd8: Request when not-ready
> end_request: I/O error, dev nbd8, sector 4294964992
> nbd8: Request when not-ready
> end_request: I/O error, dev nbd8, sector 4294964848
> nbd8: Request when not-ready
> end_request: I/O error, dev nbd8, sector 4294964848
> nbd9: Request when not-ready
> end_request: I/O error, dev nbd9, sector 4294965120
> nbd9: Request when not-ready
> end_request: I/O error, dev nbd9, sector 4294965120
> nbd9: Request when not-ready
> end_request: I/O error, dev nbd9, sector 4294964992
> nbd9: Request when not-ready
> end_request: I/O error, dev nbd9, sector 4294964992
> nbd9: Request when not-ready
> end_request: I/O error, dev nbd9, sector 4294964992
> nbd9: Request when not-ready
> end_request: I/O error, dev nbd9, sector 4294964848
> nbd9: Request when not-ready
> end_request: I/O error, dev nbd9, sector 4294964848
> Adding 923696k swap on /dev/hda5.  Priority:-1 extents:1
> nvidia: module license 'NVIDIA' taints kernel.
> PCI: Enabling device 0000:00:0a.0 (0000 -> 0002)
> ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11
> PCI: setting IRQ 11 as level-triggered
> ACPI: PCI Interrupt 0000:00:0a.0[A] -> Link [LNKA] -> GSI 11 (level,
> low) -> IRQ 11
> ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LNKA] -> GSI 11 (level,
> low) -> IRQ 11
> NVRM: loading NVIDIA Linux x86 NVIDIA Kernel Module  1.0-6629  Wed Nov
> 3 13:12:51 PST 2004
> ReiserFS: hdb1: found reiserfs format "3.6" with standard journal
> ReiserFS: hdb1: warning: CONFIG_REISERFS_CHECK is set ON
> ReiserFS: hdb1: warning: - it is slow mode for debugging.
> ReiserFS: hdb1: using ordered data mode
> ReiserFS: hdb1: journal params: device hdb1, size 8192, journal first
> block 18, max trans len 1024, max batch 900, max commit age 30, max
> trans age 30
> ReiserFS: hdb1: checking transaction log (hdb1)
> ReiserFS: hdb1: journal-1153: found in header: first_unflushed_offset
> 3344, last_flushed_trans_id 11825
> ReiserFS: hdb1: journal-1206: Starting replay from offset
> 50792283245840, trans_id 0
> ReiserFS: hdb1: journal-1299: Setting newest_mount_id to 288
> ReiserFS: hdb1: Using r5 hash to sort names
> eth0: link up, 100Mbps, full-duplex, lpa 0xFFFF
> 
-- 
Mit freundlichen Grüßen

Heinz Sporn

SPORN it-freelancing

Mobile:  ++43 (0)699 / 127 827 07
Email:   heinz.sporn@sporn-it.com
         heinz.sporn@utanet.at
Website: http://www.sporn-it.com
Snail:   Steyrer Str. 20
         A-4540 Bad Hall
         Austria / Europe

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Weird "Buffer I/O error" in dev ndb0

[Phill MV]

[-- Attachment #1: Type: text/plain, Size: 730 bytes --]

That makes me feel much better.
On a related note, shouldn't we be filing bug reports, then?

Yes, I was getting the same errors/warnings; it finally annoyed me so
> much that I recompiled the kernel without NBD support, since I couldn't
> find any suggestion that I actually needed it, and all was well after
> that. Certainly I didn't find that anything which had been working got
> broke due to the removal-- but that wasn't a big surprise, since the
> errors/warnings suggested that a function was being probed that did not
> exist anyway (so I wasn't actually using NBD in the first place, which
> was what it seemed to be complaining about).
>
> HTH,
> Holly
> --
> gentoo-user@gentoo.org mailing list
>
>

[-- Attachment #2: Type: text/html, Size: 967 bytes --]

Re: [gentoo-user] Weird "Buffer I/O error" in dev ndb0

[Holly Bostick]

Phill MV schreef:
> That makes me feel much better. On a related note, shouldn't we be
> filing bug reports, then?

Never occurred to me since it was a PEBKAC (problem existing between
keyboard and chair, to save people having to look it up). The only
reason NBD was compiled into the kernel was because I put it there,
having mysteriously forgotten that I had gotten along fine without it
for some time, and having suddenly conceived a conviction that it was
some kind of missing link to a network paradise of some sort.

Which it may well be, but not for my home network of two puny PCs. I
don't know what came over me.

And I definitely don't know what kind of a bug 'should' be filed, if I
thought one was needed.

Holly
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Weird "Buffer I/O error" in dev ndb0

[Phill MV]

[-- Attachment #1: Type: text/plain, Size: 1141 bytes --]

Well, *something* is trying to access a function that doesnt exist in NDB;
whether we know what it does or why, I'm guessing it's a behaviour that
shouldn't happen :P.

I suppose whatever tries to access NDB has a bug in it... but what would
that be?

On 27/09/05, Holly Bostick <motub@planet.nl> wrote:
>
> Phill MV schreef:
> > That makes me feel much better. On a related note, shouldn't we be
> > filing bug reports, then?
>
> Never occurred to me since it was a PEBKAC (problem existing between
> keyboard and chair, to save people having to look it up). The only
> reason NBD was compiled into the kernel was because I put it there,
> having mysteriously forgotten that I had gotten along fine without it
> for some time, and having suddenly conceived a conviction that it was
> some kind of missing link to a network paradise of some sort.
>
> Which it may well be, but not for my home network of two puny PCs. I
> don't know what came over me.
>
> And I definitely don't know what kind of a bug 'should' be filed, if I
> thought one was needed.
>
> Holly
> --
> gentoo-user@gentoo.org mailing list
>
>

[-- Attachment #2: Type: text/html, Size: 1476 bytes --]

Re: [gentoo-user] Weird "Buffer I/O error" in dev ndb0

[Richard Fish]

Phill MV wrote:

> Well, *something* is trying to access a function that doesnt exist in 
> NDB; whether we know what it does or why, I'm guessing it's a 
> behaviour that shouldn't happen :P.
>
> I suppose whatever tries to access NDB has a bug in it... but what 
> would that be?


Do you have lvm installed (/sbin/lvm)?

If so, the Gentoo startup script /sbin/rc will try to execute it after 
starting udev to probe for physical volumes, volume groups, and logical 
volumes.
The default configuration of lvm probes _all_ block devices, so this is 
a probable suspect.  You can try adding a filter to /etc/lvm/lvm.conf in 
this case, like so:

    filter = [ "r|/dev/nbd.*|" ]

As for whether it should or shouldn't happen, I am not sure.  I don't 
know how common it is to use network block devices...it is definitely a 
high-end feature.  I would guess that anyone using nbd would also be 
interested in using lvm, so it is probably more useful to have lvm probe 
these devices if they exist.

-Richard

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Weird "Buffer I/O error" in dev ndb0

[Holly Bostick]

Richard Fish schreef:
> Phill MV wrote:
> 
>> Well, *something* is trying to access a function that doesnt exist
>> in NDB; whether we know what it does or why, I'm guessing it's a 
>> behaviour that shouldn't happen :P.
>> 
>> I suppose whatever tries to access NDB has a bug in it... but what 
>> would that be?
> 
> 
> 
> Do you have lvm installed (/sbin/lvm)?
> 
> If so, the Gentoo startup script /sbin/rc will try to execute it
> after starting udev to probe for physical volumes, volume groups, and
> logical volumes. The default configuration of lvm probes _all_ block
> devices, so this is a probable suspect.  You can try adding a filter
> to /etc/lvm/lvm.conf in this case, like so:
> 
> filter = [ "r|/dev/nbd.*|" ]
> 
> As for whether it should or shouldn't happen, I am not sure.  I don't
>  know how common it is to use network block devices...it is
> definitely a high-end feature.  I would guess that anyone using nbd
> would also be interested in using lvm, so it is probably more useful
> to have lvm probe these devices if they exist.


Well, insofar as it is a confirmation of anything, I can say that that
explains the problem with nbd in my case; I have an lvm2 volume, managed
by evms (which is also too hige-end for my use, but I'm kinda stuck with
it now). Evms is also prone to probe every d*mn thing it can find, and
of course the lvm plugin is in use, because I actually do have an lvm2
volume. So I can see how if nbd was available, it would want to check
that as well, and both why removing it was necessary to make it stop, as
well as why it was unnecessary for me in the first place.

Thanks for the explanation.

Holly
-- 
gentoo-user@gentoo.org mailing list