Bug#353480: [parisc-linux] Re: Bug#353480: yaird: [hppa] /dev/sd* device nodes not created and eth0 not enabled

2006-02-21 Thread Joel Soete
> 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
> > 
> 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-devel&m=114019842906313&w=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

2006-02-21 Thread Kyle McMartin
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

2006-02-21 Thread Joel Soete
> > 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
> > >  >
> > 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-devel&m=114019842906313&w=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: bind
[42949644.38] md: bind
[42949644.42] md: bind
[42949644.46] md: bind
[42949644.49] md: bind
[42949644.52] md: bind
[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 files, 104630/128960 blocks
[/sbin/fsck.ext3

Bug#353480: [parisc-linux] Re: Bug#353480: yaird: [hppa] /dev/sd* device nodes not created and eth0 not enabled

2006-02-21 Thread Matthew Wilcox
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: [parisc-linux] Re: Bug#353480: yaird: [hppa] /dev/sd* device nodes not created and eth0 not enabled

2006-02-22 Thread
-- 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.