Bug#353480: [parisc-linux] Re: Bug#353480: yaird: [hppa] /dev/sd* device nodes not created and eth0 not enabled
-- Initial header --- From : Matthew Wilcox [EMAIL PROTECTED] To : Joel Soete [EMAIL PROTECTED] CC : parisc-linux [EMAIL PROTECTED],kyle [EMAIL PROTECTED],aragorn [EMAIL PROTECTED],tsg45800 [EMAIL PROTECTED],353480 [EMAIL PROTECTED],debian-hppa debian-hppa@lists.debian.org Date : Tue, 21 Feb 2006 10:26:06 -0700 Subject : Re: [parisc-linux] Re: Bug#353480: yaird: [hppa] /dev/sd* device nodes not created and eth0 not enabled On Tue, Feb 21, 2006 at 06:00:43PM +0100, Joel Soete wrote: Just a small update to confirm that works fine: INIT: version 2.86 booting Starting the hotplug events dispatcher: udevd. Synthesizing the initial hotplug events...done. Waiting for /dev to be fully populated... done (timeout). How is timing out works fine? Works better, sure, but why is it timing out? Right: works far better ;) That said, I have a look in more detail about 'timeout' and it seems to me that this system just need more time to complete its '/dev full population'. I so increased timeout const to 90 (60 is not yet enough) and it finished without any more timing out (for smp and up 32bit kernel): [...] [42949443.40] 356k freed INIT: version 2.86 booting Starting the hotplug events dispatcher: udevd. Synthesizing the initial hotplug events...done. Waiting for /dev to be fully populated...done. Will now activate swap. swapon on /dev/md/1 [42949602.86] Adding 385976k swap on /dev/md/1. Priority:-1 extents:1 across:385976k Done activating swap. Will now check root file system. [...] Hth, Joel --- NOTE! My email address is changing to ... @scarlet.be Please make the necessary changes in your address book.
Bug#353480: [parisc-linux] Re: Bug#353480: yaird: [hppa] /dev/sd* device nodes not created and eth0 not enabled
On Sat, Feb 18, 2006 at 10:02:28PM +0100, Frans Pop wrote: udevd[862]: get_netlink_msg: unable to receive kernel netlink message: No buffer space available !-- not sure about this message, but the same is shown for initramfs-tools -- This is the reason you aren't getting /dev/sd* nodes. I debugged this yesterday, needs new udev upload, more details here: http://marc.theaimsgroup.com/?l=linux-hotplug-develm=114019842906313w=2 hihi, as I have to rebuild the pkg is also discover: udev_libc_wrapper.h:69:2: warning: #warning inotify unsupported on this architecture! this warning is obviously false and, imho, could be esaly fixed by: --- udev-084/udev_libc_wrapper.h.Orig 2006-02-21 10:58:11.0 +0100 +++ udev-084/udev_libc_wrapper.h2006-02-21 10:56:25.0 +0100 @@ -65,6 +65,10 @@ # define __NR_inotify_init 290 # define __NR_inotify_add_watch291 # define __NR_inotify_rm_watch 292 +#elif defined (__hppa__) +# define __NR_inotify_init 269 +# define __NR_inotify_add_watch270 +# define __NR_inotify_rm_watch 271 #else #warning inotify unsupported on this architecture! #endif Marco, Kyle, will you also submitted upstream? TIA, Joel --- NOTE! My email address is changing to ... @scarlet.be Please make the necessary changes in your address book.
Bug#353480: [parisc-linux] Re: Bug#353480: yaird: [hppa] /dev/sd* device nodes not created and eth0 not enabled
On Tue, Feb 21, 2006 at 02:46:09PM +0100, Joel Soete wrote: hihi, as I have to rebuild the pkg is also discover: udev_libc_wrapper.h:69:2: warning: #warning inotify unsupported on this architecture! Good catch, I missed this. Yes, this should also go upstream... not that I've yet received any reply from upstream to my first change... Cheers, Kyle -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#353480: [parisc-linux] Re: Bug#353480: yaird: [hppa] /dev/sd* device nodes not created and eth0 not enabled
On Sat, Feb 18, 2006 at 10:02:28PM +0100, Frans Pop wrote: udevd[862]: get_netlink_msg: unable to receive kernel netlink message: No buffer space available !-- not sure about this message, but the same is shown for initramfs-tools -- This is the reason you aren't getting /dev/sd* nodes. I debugged this yesterday, needs new udev upload, more details here: http://marc.theaimsgroup.com/?l=linux-hotplug-develm=114019842906313w=2 hihi, as I have to rebuild the pkg is also discover: udev_libc_wrapper.h:69:2: warning: #warning inotify unsupported on this architecture! this warning is obviously false and, imho, could be esaly fixed by: --- udev-084/udev_libc_wrapper.h.Orig 2006-02-21 10:58:11.0 +0100 +++ udev-084/udev_libc_wrapper.h2006-02-21 10:56:25.0 +0100 @@ -65,6 +65,10 @@ # define __NR_inotify_init 290 # define __NR_inotify_add_watch291 # define __NR_inotify_rm_watch 292 +#elif defined (__hppa__) +# define __NR_inotify_init 269 +# define __NR_inotify_add_watch270 +# define __NR_inotify_rm_watch 271 #else #warning inotify unsupported on this architecture! #endif Just a small update to confirm that works fine: INIT: version 2.86 booting Starting the hotplug events dispatcher: udevd. Synthesizing the initial hotplug events...done. Waiting for /dev to be fully populated... done (timeout). Will now activate swap. swapon on /dev/md/1 [42949610.96] Adding 385976k swap on /dev/md/1. Priority:-1 extents:1 across:385976k Done activating swap. Will now check root file system. fsck 1.39-WIP (31-Dec-2005) [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a -C0 /dev/md2 /dev/md2: clean, 85433/256000 files, 326381/511968 blocks Done checking root file system. A log will be saved in /var/log/fsck/checkroot if that location is writable. [42949612.40] EXT3 FS on md2, internal journal Setting the system clock.. System Clock set. Local time: Tue Feb 21 16:39:08 UTC 2006. Cleaning up ifupdown...done. Not running depmod because /lib/modules/2.6.16-rc4-pa1-d32mp/ is not writeable. Loading modules... All modules loaded. FATAL: Could not load /lib/modules/2.6.16-rc4-pa1-d32mp/modules.dep: No such file or directory Setting the system clock again.. System Clock set. Local time: Tue Feb 21 16:39:11 UTC 2006. Loading device-mapper support. Starting raid devices: [42949640.19] md: md4 stopped. mdadm: cannot open device /dev/sdc2: Device or resource busy mdadm: /dev/sdc2 has no superblock - assembly aborted [42949641.38] md: md4 stopped. mdadm: cannot open device /dev/sdc3: Device or resource busy mdadm: /dev/sdc3 has no superblock - assembly aborted [42949642.39] md: md4 stopped. mdadm: cannot open device /dev/sdc5: Device or resource busy mdadm: /dev/sdc5 has no superblock - assembly aborted [42949643.38] md: md4 stopped. mdadm: cannot open device /dev/sdc6: Device or resource busy mdadm: /dev/sdc6 has no superblock - assembly aborted [42949644.28] md: md4 stopped. [42949644.34] md: bindsdg [42949644.38] md: bindsdh [42949644.42] md: bindsdi [42949644.46] md: bindsdj [42949644.49] md: bindsdk [42949644.52] md: bindsdf [42949644.56] raid5: device sdf operational as raid disk 0 [42949644.62] raid5: device sdk operational as raid disk 5 [42949644.69] raid5: device sdj operational as raid disk 4 [42949644.76] raid5: device sdi operational as raid disk 3 [42949644.82] raid5: device sdh operational as raid disk 2 [42949644.89] raid5: device sdg operational as raid disk 1 [42949644.96] raid5: allocated 6279kB for md4 [42949645.02] raid5: raid level 5 set md4 active with 6 out of 6 devices, algorithm 2 [42949645.11] RAID5 conf printout: [42949645.15] --- rd:6 wd:6 fd:0 [42949645.19] disk 0, o:1, dev:sdf [42949645.24] disk 1, o:1, dev:sdg [42949645.28] disk 2, o:1, dev:sdh [42949645.32] disk 3, o:1, dev:sdi [42949645.36] disk 4, o:1, dev:sdj [42949645.41] disk 5, o:1, dev:sdk mdadm: /dev/md/4 has been started with 6 drives. done. Setting up LVM Volume Groups... Reading all physical volumes. This may take a while... Failed to read VG data from PV (/dev/sdb1) Failed to read VG data from PV (/dev/sdb1) Failed to read VG data from PV (/dev/sdb1) Failed to read VG data from PV (/dev/sdb1) Volume group root_vg not found Found volume group vg_raid5 using metadata type lvm2 Found volume group vg00 using metadata type lvm2 Failed to read VG data from PV (/dev/sdb1) Failed to read VG data from PV (/dev/sdb1) Failed to read VG data from PV (/dev/sdb1) Failed to read VG data from PV (/dev/sdb1) Unable to find volume group root_vg 3 logical volume(s) in volume group vg_raid5 now active 4 logical volume(s) in volume group vg00 now active Will now check all file systems. fsck 1.39-WIP (31-Dec-2005) Checking all file systems. [/sbin/fsck.ext3 (1) -- /boot] fsck.ext3 -a -C0 /dev/md/0 /dev/md/0: clean, 104/32256
Bug#353480: [parisc-linux] Re: Bug#353480: yaird: [hppa] /dev/sd* device nodes not created and eth0 not enabled
On Tue, Feb 21, 2006 at 06:00:43PM +0100, Joel Soete wrote: Just a small update to confirm that works fine: INIT: version 2.86 booting Starting the hotplug events dispatcher: udevd. Synthesizing the initial hotplug events...done. Waiting for /dev to be fully populated... done (timeout). How is timing out works fine? Works better, sure, but why is it timing out? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#353480: yaird: [hppa] /dev/sd* device nodes not created and eth0 not enabled
Frans Pop wrote: Package: yaird Version: 0.0.12-3 Severity: important After a new installation on hppa, the system seemed to boot correctly, but failed to mount /boot and /home directories. Also the eth0 network interface was not brought up automatically. If I create the initrd using initramfs-tools these problems do not occur. The reason /boot and /home are not mounted is that /dev/sd* is not present. This seems to indicate a problem with udev, which would also explain eth0 not coming up as it needs to be hotplug detected. Full log attached. Here are some relevant pieces with comments. [...] udevd[862]: get_netlink_msg: unable to receive kernel netlink message: No buffer space available mmm, yes I encountered the same pb with a recent smp kernel (iirc 2.6.16-rc2...) and udev. but not with a up kernel. !-- not sure about this message, but the same is shown for initramfs-tools -- I don't (want to) use initramfs (not enough clue to rebuild it :\ ) [...] Waiting for /dev to be fully populated...hda: CD-532E-B, ATAPI CD/DVD-ROM drive !-- Hmm. Looks like things have not really been waiting... -- [...] Checking all file systems. [/sbin/fsck.ext2 (1) -- /boot] fsck.ext2 -a -C0 /dev/sda2 fsck.ext2: No such file or directory while trying to open /dev/sda2 /dev/sda2: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 device [/sbin/fsck.ext3 (1) -- /home] fsck.ext3 -a -C0 /dev/sda7 fsck.ext3: No such file or directory while trying to open /dev/sda7 /dev/sda7: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 device fsck died with exit status 8 File system check failed. A log is being saved in /var/log/fsck/checkfs if that location is writable. Please repair the file system manually. A maintenance shell will now be started. CONTROL-D will terminate this shell and resume system boot. Give root password for maintenance (or type Control-D to continue): The same here. Sorry to not being of more help but I don't yet found time to debug more this other udev pb with smp kernel ;( Joel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#353480: yaird: [hppa] /dev/sd* device nodes not created and eth0 not enabled
On Sunday 19 February 2006 11:11, Joel Soete wrote: Frans Pop wrote: udevd[862]: get_netlink_msg: unable to receive kernel netlink message: No buffer space available mmm, yes I encountered the same pb with a recent smp kernel (iirc 2.6.16-rc2...) and udev. but not with a up kernel. Hmm. I have tried with UP kernel too and get the exact same message and errors there too. The kernels I've tried are: - linux-image-2.6.15-1-parisc (2.6.15-6) - linux-image-2.6.15-1-parisc-smp (2.6.15-6) (From boot messages during install I understand that my box should support 64-bit kernels as well, but I've not yet tried those.) !-- not sure about this message, but the same is shown for initramfs-tools -- I don't (want to) use initramfs (not enough clue to rebuild it :\ ) It's quite easy: update-initramfs -v -u -t [-k kernel version] [...log messages showing mount failures...] The same here. Sorry to not being of more help but I don't yet found time to debug more this other udev pb with smp kernel ;( Joel pgpoRe1ZwoEYs.pgp Description: PGP signature
Bug#353480: yaird: [hppa] /dev/sd* device nodes not created and eth0 not enabled
Package: yaird Version: 0.0.12-3 Severity: important After a new installation on hppa, the system seemed to boot correctly, but failed to mount /boot and /home directories. Also the eth0 network interface was not brought up automatically. If I create the initrd using initramfs-tools these problems do not occur. The reason /boot and /home are not mounted is that /dev/sd* is not present. This seems to indicate a problem with udev, which would also explain eth0 not coming up as it needs to be hotplug detected. Full log attached. Here are some relevant pieces with comments. [...] SCSI device sda: 17773524 512-byte hdwr sectors (9100 MB) SCSI device sda: drive cache: write back SCSI device sda: 17773524 512-byte hdwr sectors (9100 MB) SCSI device sda: drive cache: write back sda: sda1 sda2 sda3 sda5 sda6 sda7 !-- SCSI devices detected OK, so driver must be loaded -- [...] INIT: version 2.86 booting Starting the hotplug events dispatcher: udevd. Synthesizing the initial hotplug events...usbcore: registered new driver usbfs !-- udev is started, but I guess that as scsi driver and network driver are loaded already, it does not receive events for them and thus does not create device nodes in /dev, and does not hotplug eth0 -- usbcore: registered new driver hub ohci_hcd :00:0e.2: OHCI Host Controller ohci_hcd :00:0e.2: new USB bus registered, assigned bus number 1 ohci_hcd :00:0e.2: irq 1, io mem 0xf4007000 usb usb1: Product: OHCI Host Controller usb usb1: Manufacturer: Linux 2.6.15-1-parisc-smp ohci_hcd usb usb1: SerialNumber: :00:0e.2 hub 1-0:1.0: USB hub found hub 1-0:1.0: 3 ports detected udevd[862]: get_netlink_msg: unable to receive kernel netlink message: No buffer space available !-- not sure about this message, but the same is shown for initramfs-tools -- Linux Tulip driver version 1.1.13 (December 15, 2004) tulip0: no phy info, aborting mtable build tulip0: MII transceiver #1 config 1000 status 782d advertising 0081. eth0: Digital DS21142/DS21143 Tulip rev 65 at 80001000, 00:10:83:CF:15:A5, IRQ 66. Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx NS87415: IDE controller at PCI slot :00:0e.0 NS87415: chipset revision 3 NS87415: 100% native mode on irq 7 ide0: BM-DMA at 0x0a00-0x0a07, BIOS settings: hda:DMA, hdb:DMA ide1: BM-DMA at 0x0a08-0x0a0f, BIOS settings: hdc:DMA, hdd:DMA done. Waiting for /dev to be fully populated...hda: CD-532E-B, ATAPI CD/DVD-ROM drive !-- Hmm. Looks like things have not really been waiting... -- [...] Checking all file systems. [/sbin/fsck.ext2 (1) -- /boot] fsck.ext2 -a -C0 /dev/sda2 fsck.ext2: No such file or directory while trying to open /dev/sda2 /dev/sda2: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 device [/sbin/fsck.ext3 (1) -- /home] fsck.ext3 -a -C0 /dev/sda7 fsck.ext3: No such file or directory while trying to open /dev/sda7 /dev/sda7: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 device fsck died with exit status 8 File system check failed. A log is being saved in /var/log/fsck/checkfs if that location is writable. Please repair the file system manually. A maintenance shell will now be started. CONTROL-D will terminate this shell and resume system boot. Give root password for maintenance (or type Control-D to continue): Setting kernel variables ... done. Will now mount local filesystems. mount: special device /dev/sda2 does not exist mount: special device /dev/sda7 does not exist Mounting local filesystems failed with error code 32. Will now activate swapfile swap. Done activating swapfile swap. !-- So here we have the failure to mount /boot and /home -- -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: hppa (parisc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-parisc-smp Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages yaird depends on: ii cpio 2.6-10 GNU cpio -- a program to manage ar ii dash 0.5.3-2 The Debian Almquist Shell ii libc62.3.6-1 GNU C Library: Shared libraries an ii libhtml-template-perl2.8-1 HTML::Template : A module for usin ii libparse-recdescent-perl 1.94.free-1 Generates recursive-descent parser ii perl 5.8.8-2 Larry Wall's Practical Extraction
Bug#353480: [Yaird-devel] Bug#353480: yaird: [hppa] /dev/sd* device nodes not created and eth0 not enabled
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 reassign 353480 udev thanks On Sat, 18 Feb 2006 22:02:28 +0100 Frans Pop [EMAIL PROTECTED] wrote: After a new installation on hppa, the system seemed to boot correctly, but failed to mount /boot and /home directories. Also the eth0 network interface was not brought up automatically. If I create the initrd using initramfs-tools these problems do not occur. The reason /boot and /home are not mounted is that /dev/sd* is not present. This seems to indicate a problem with udev, which would also explain eth0 not coming up as it needs to be hotplug detected. Yaird seems to do its job correctly: Bring the system to a point of the root filesystem being mounted. Udev not cold-plugging already-loaded modules sounds like a bug in udev - or perhaps in kernel modules not being udev-friendly. Reassigning to udev. I trust Marco in knowing if the bug is there or the kernel (or can clarify why it might be a bug in yaird after all). - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ - Enden er nær: http://www.shibumi.org/eoti.htm -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFD95N2n7DbMsAkQLgRAnDQAJsGZsXn+XQmoIfSvhVtlaf+wN/vtACgnKKD m37LvBOyvu32u+nedGoosfM= =a9Rx -END PGP SIGNATURE-
Bug#353480: yaird: [hppa] /dev/sd* device nodes not created and eth0 not enabled
On Sat, Feb 18, 2006 at 10:02:28PM +0100, Frans Pop wrote: udevd[862]: get_netlink_msg: unable to receive kernel netlink message: No buffer space available !-- not sure about this message, but the same is shown for initramfs-tools -- This is the reason you aren't getting /dev/sd* nodes. I debugged this yesterday, needs new udev upload, more details here: http://marc.theaimsgroup.com/?l=linux-hotplug-develm=114019842906313w=2 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
