udev: upgrade to 0.051-1 renders the system unbootable

Automatically imported from Debian bug report #293817 http://bugs.debian.org/293817

Message-Id: <email address hidden>
Date: Sun, 06 Feb 2005 01:06:27 +0100
From: "Jean-Luc Coulon (f5ibh)" <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: udev: upgrade to 0.051-1 renders the system unbootable

Package: udev
Version: 0.050-6
Severity: critical
Justification: breaks the whole system

Hi,

After upgrading from 0.050-6 to 0.051-1, the system becomes unbootable.
Some devices are missing. At least /dev/console.

init: open(/dev/console): No such file or directory

then gpm failed;
Feb 5 22:20:45 tangerine-64 gpm: oops() invoked from gpm.c(971)
Feb 5 22:20:45 tangerine-64 gpm: Failed on virtual console check: No such file
or directory

I've reverted to 0.050-6 and everything went fine.

Regards

Jean-Luc

-- Package-specific info:
-- /etc/udev/rules.d/:
/etc/udev/rules.d/:
total 4
lrwxrwxrwx 1 root root 19 2005-01-01 18:22 cd-aliases.rules -> ../cd-aliases.rules
-rw-r--r-- 1 root root 242 2005-02-05 23:23 tablet.rules
lrwxrwxrwx 1 root root 13 2005-01-01 18:22 udev.rules -> ../udev.rules
lrwxrwxrwx 1 root root 12 2005-01-29 15:07 z_hal-plugdev.rules -> ../hal.rules

-- /sys/:
/sys/block/dm-0/dev
/sys/block/dm-1/dev
/sys/block/dm-2/dev
/sys/block/dm-3/dev
/sys/block/dm-4/dev
/sys/block/dm-5/dev
/sys/block/dm-6/dev
/sys/block/dm-7/dev
/sys/block/hda/dev
/sys/block/hdc/dev
/sys/block/md0/dev
/sys/block/md100/dev
/sys/block/md101/dev
/sys/block/md102/dev
/sys/block/md103/dev
/sys/block/md104/dev
/sys/block/md105/dev
/sys/block/md106/dev
/sys/block/md107/dev
/sys/block/md108/dev
/sys/block/md109/dev
/sys/block/md10/dev
/sys/block/md110/dev
/sys/block/md111/dev
/sys/block/md112/dev
/sys/block/md113/dev
/sys/block/md114/dev
/sys/block/md115/dev
/sys/block/md116/dev
/sys/block/md117/dev
/sys/block/md118/dev
/sys/block/md119/dev
/sys/block/md11/dev
/sys/block/md120/dev
/sys/block/md121/dev
/sys/block/md122/dev
/sys/block/md123/dev
/sys/block/md124/dev
/sys/block/md125/dev
/sys/block/md126/dev
/sys/block/md127/dev
/sys/block/md128/dev
/sys/block/md129/dev
/sys/block/md12/dev
/sys/block/md130/dev
/sys/block/md131/dev
/sys/block/md132/dev
/sys/block/md133/dev
/sys/block/md134/dev
/sys/block/md135/dev
/sys/block/md136/dev
/sys/block/md137/dev
/sys/block/md138/dev
/sys/block/md139/dev
/sys/block/md13/dev
/sys/block/md140/dev
/sys/block/md141/dev
/sys/block/md142/dev
/sys/block/md143/dev
/sys/block/md144/dev
/sys/block/md145/dev
/sys/block/md146/dev
/sys/block/md147/dev
/sys/block/md148/dev
/sys/block/md149/dev
/sys/block/md14/dev
/sys/block/md150/dev
/sys/block/md151/dev
/sys/block/md152/dev
/sys/block/md153/dev
/sys/block/md154/dev
/sys/block/md155/dev
/sys/block/md156/dev
/sys/block/md157/dev
/sys/block/md158/dev
/sys/block/md159/dev
/sys/block/md15/dev
/sys/block/md160/dev
/sys/block/md161/dev
/sys/block/md162/dev
/sys/block/md163/dev
/sys/block/md164/dev
/sys/block/md165/dev
/sys/block/md166/dev
/sys/block/md167/dev
/sys/block/md168/dev
/sys/block/md169/dev
/sys/block/md16/dev
/sys/block/md170/dev
/sys/block/md171/dev
/sys/block/md172/dev
/sys/block/md173/dev
/sys/block/md174/dev
/sys/block/md175/dev
/sys/block/md176/dev
/sys/block/md177/dev
/sys/block/md178/dev
/s...

Message-ID: <email address hidden>
Date: Sun, 6 Feb 2005 01:36:59 +0100
From: <email address hidden> (Marco d'Itri)
To: "Jean-Luc Coulon (f5ibh)" <email address hidden>,
 <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#293817: udev: upgrade to 0.051-1 renders the system unbootable

--lrZ03NoBR/3+SXJZ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

severity 293817 normal
tag 293817 moreinfo unreproducible
thanks

On Feb 06, "Jean-Luc Coulon (f5ibh)" <email address hidden> wrote:

> After upgrading from 0.050-6 to 0.051-1, the system becomes unbootable.
> Some devices are missing. At least /dev/console.
It works fine for me. Please try to understand what is wrong.
Please also report the content of /etc/udev/rules.d/tablet.rules.

--=20
ciao,
Marco

--lrZ03NoBR/3+SXJZ
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFCBWarFGfw2OHuP7ERAtVOAKCbW9MtwOxfwvaZp0e6sy/OsKmLoQCgj/XC
ROPv7kQhl9aEvU4BMlWkulI=
=9R2O
-----END PGP SIGNATURE-----

--lrZ03NoBR/3+SXJZ--

Message-Id: <1107683311l.10447l.2l@tangerine-64>
Date: Sun, 06 Feb 2005 09:48:31 +0000
From: "Jean-Luc Coulon (f5ibh)" <email address hidden>
To: Marco d'Itri <email address hidden>
Cc: <email address hidden>, <email address hidden>
Subject: Re: Bug#293817: udev: upgrade to 0.051-1 renders the system
 unbootable

--=-Ufi3qqK1mxB7fj79E34o
Content-Type: text/plain; charset=ISO-8859-1; DelSp=Yes; Format=Flowed
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Le 06.02.2005 01:36:59, Marco d'Itri a =E9crit=A0:
> severity 293817 normal
> tag 293817 moreinfo unreproducible
> thanks
>=20
> On Feb 06, "Jean-Luc Coulon (f5ibh)" <email address hidden>
> wrote:
>=20
>> After upgrading from 0.050-6 to 0.051-1, the system becomes
> unbootable.
>> Some devices are missing. At least /dev/console.
> It works fine for me. Please try to understand what is wrong.

I've redone the test, it is always the same. It begin to boot and the =20
stops displaying anything while there is still some activity. I didnt =20
manage to reach my box via the network: whine I can ping it, ssh is not =20
working.

The latest displayed message are:
Feb 5 14:30:56 tangerine-64 kernel: eth0: network connection up using =20
port A
Feb 5 14:30:56 tangerine-64 kernel: speed: 100
Feb 5 14:30:56 tangerine-64 kernel: autonegotiation: yes
Feb 5 14:30:56 tangerine-64 kernel: duplex mode: full
Feb 5 14:30:56 tangerine-64 kernel: flowctrl: symmetric
Feb 5 14:30:56 tangerine-64 kernel: irq moderation: disabled
Feb 5 14:30:56 tangerine-64 kernel: scatter-gather: enabled
Feb 5 14:30:56 tangerine-64 kernel: Capability LSM initialized

After 20 minutes or so, I decided to press the reset button :-/

> Please also report the content of /etc/udev/rules.d/tablet.rules.

I've done some tests for the wacom tablet but the file has only one =20
line and is commented out. =20

#BUS=3D"usb", SYSFS{idVendor}=3D"056a", SYSFS{idProduct}=3D"0011", NAME=3D"=
%k", =20
SYMLINK=3D"input/tablet"

But the way, if I tried to enable this line, it creates first the right =20
symlink but it is overwritten later with every device in /dev/inout/ to =20
finally stay with the latest found.

To be able to boot, I've started the system on a live CD and the =20
download the previous debian package fro udev (0.050-6) from =20
snapshot.debian.net. I've extracted the package and copied the files by =20
hand on the "damaged" system. Then I was able to boot.

I'm using xfs filesystems on lvm over a software raid1.

>=20
> --
> ciao,
> Marco
>=20

Jean-Luc

--=-Ufi3qqK1mxB7fj79E34o
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQBCBefvUdGGXzzGnNARAu/VAJwPsSsZqy2gC4A0O4lnH0RPEpm2fQCeNsDZ
MZI9/BQsE/ajyCDzINeMsDY=
=CJS3
-----END PGP SIGNATURE-----

--=-Ufi3qqK1mxB7fj79E34o--

Message-ID: <email address hidden>
Date: Sun, 6 Feb 2005 11:20:38 +0100
From: <email address hidden> (Marco d'Itri)
To: "Jean-Luc Coulon (f5ibh)" <email address hidden>,
 <email address hidden>
Subject: Re: Bug#293817: udev: upgrade to 0.051-1 renders the system unbootable

--VS++wcV0S1rZb1Fb
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Feb 06, "Jean-Luc Coulon (f5ibh)" <email address hidden> wrote:

> I've redone the test, it is always the same. It begin to boot and the =20
> stops displaying anything while there is still some activity. I didnt =20
> manage to reach my box via the network: whine I can ping it, ssh is not =
=20
> working.
>=20
> The latest displayed message are:
This is not helping. Please reboot the system with init=3D/bin/bash,
manually run:

/etc/init.d/mountvirtfs start
/etc/init.d/udev start

and check what really happens.

> #BUS=3D"usb", SYSFS{idVendor}=3D"056a", SYSFS{idProduct}=3D"0011", NAME=
=3D"%k", =20
> SYMLINK=3D"input/tablet"
>=20
> But the way, if I tried to enable this line, it creates first the right =
=20
> symlink but it is overwritten later with every device in /dev/inout/ to =
=20
> finally stay with the latest found.
I find hard to believe that such a bug is exposed only on your system.

> To be able to boot, I've started the system on a live CD and the =20
> download the previous debian package fro udev (0.050-6) from =20
If udev breaks, you can disable it by disabling the init script.

Or else, add to the top of the init script:

if [ "$DISABLE_UDEV" =3D "yes" ]; then
  echo "udev disabled by a kernel parameter
  exit 0
fi

and you will be able to disable it by adding DISABLE_UDEV=3Dyes to the
kernel command line.

--=20
ciao,
Marco

--VS++wcV0S1rZb1Fb
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFCBe92FGfw2OHuP7ERAgIvAJ9NO7jY36JPkEBMHtLQ96BQfiJzGACgniMz
KqLcZfiAfQxpbQPylGzuQs4=
=kwWo
-----END PGP SIGNATURE-----

--VS++wcV0S1rZb1Fb--

Message-Id: <1107688315l.10508l.0l@tangerine-64>
Date: Sun, 06 Feb 2005 11:11:55 +0000
From: "Jean-Luc Coulon (f5ibh)" <email address hidden>
To: Marco d'Itri <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#293817: udev: upgrade to 0.051-1 renders the system
 unbootable

Le 06.02.2005 11:20:38, Marco d'Itri a =E9crit=A0:
> On Feb 06, "Jean-Luc Coulon (f5ibh)" <email address hidden>
> wrote:
>=20
>> I've redone the test, it is always the same. It begin to boot and the
>=20
>> stops displaying anything while there is still some activity. I didnt
>=20
>> manage to reach my box via the network: whine I can ping it, ssh is
> not
>> working.
>>=20
>> The latest displayed message are:
> This is not helping. Please reboot the system with init=3D/bin/bash,
> manually run:
>=20
> /etc/init.d/mountvirtfs start
> /etc/init.d/udev start
>=20
> and check what really happens.

I've to borrow an other keyboard: mine is usb and not initialised yet =20
at this level.

Anyway, I have got some arror message about the node for my root =20
filesystem (which is on lvm)

Anyway, when I've started the system with the new version of udev, I =20
gor the following error:

<<
The device node /dev/mapper/vg00-root_lv for the root filesystem is =20
missing, incorrect or there is no entry for the root filesystem in
/etc/fstab. The system is also unable to create temporary node in =20
/dev/shm to use as a work-around. This means that you have to fix this =20
manually.
>>=20

>=20
>> #BUS=3D"usb", SYSFS{idVendor}=3D"056a", SYSFS{idProduct}=3D"0011",
> NAME=3D"%k",
>> SYMLINK=3D"input/tablet"
>>=20
>> But the way, if I tried to enable this line, it creates first the
> right
>> symlink but it is overwritten later with every device in /dev/inout/
> to
>> finally stay with the latest found.
> I find hard to believe that such a bug is exposed only on your system.
>=20
>> To be able to boot, I've started the system on a live CD and the
>> download the previous debian package fro udev (0.050-6) from
> If udev breaks, you can disable it by disabling the init script.
>=20
> Or else, add to the top of the init script:
>=20
> if [ "$DISABLE_UDEV" =3D "yes" ]; then
> echo "udev disabled by a kernel parameter
> exit 0
> fi

Ok done, this save me from using a live cd to recover.

>=20
> and you will be able to disable it by adding DISABLE_UDEV=3Dyes to the
> kernel command line.
>=20
> --
> ciao,
> Marco
>=20

Jean-Luc

Message-Id: <1107709032l.10102l.0l@tangerine-64>
Date: Sun, 06 Feb 2005 16:57:12 +0000
From: "Jean-Luc Coulon (f5ibh)" <email address hidden>
To: Marco d'Itri <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#293817: udev: upgrade to 0.051-1 renders the system
 unbootable

--=-EUQUkZu8WUz2+LaHpZV+
Content-Type: text/plain; charset=ISO-8859-1; DelSp=Yes; Format=Flowed
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Le 06.02.2005 11:20:38, Marco d'Itri a =E9crit=A0:
> On Feb 06, "Jean-Luc Coulon (f5ibh)" <email address hidden>
> wrote:
>=20
>> I've redone the test, it is always the same. It begin to boot and the
>=20
>> stops displaying anything while there is still some activity. I didnt
>=20
>> manage to reach my box via the network: whine I can ping it, ssh is
> not
>> working.
>>=20
>> The latest displayed message are:
> This is not helping. Please reboot the system with init=3D/bin/bash,
> manually run:
>=20
> /etc/init.d/mountvirtfs start

I've borrowed a ps/2 to usb adapter.

When I start /init/bash then:
/etc/init.d/mountvirtfs start
and then:
/etc/init.d/udev start

I get the followinf messages:
Mounting a tmpfs over /dev... Done.
Creating inital device nodes...Done.

You will find attached the list of the created devices.

Then if I reboot, I've the same crash as before (with some data =20
corruption) :-/

[ ... ]

> --
> ciao,
> Marco
>=20

Jean-Luc
--=-EUQUkZu8WUz2+LaHpZV+
Content-Type: text/plain; charset=us-ascii; name=devices
Content-Disposition: attachment; filename=devices
Content-Transfer-Encoding: quoted-printable

MAKEDEV
console
core
fb0
fd
full
hpet
input
kmem
kmsg
loop
mapper
md0
md1
md10
md100
md101
md102
md103
md104
md105
md106
md107
md108
md109
md11
md110
md111
md112
md113
md114
md115
md116
md117
md118
md119
md12
md120
md121
md122
md123
md124
md125
md126
md127
md128
md129
md13
md130
md131
md132
md133
md134
md135
md136
md137
md138
md139
md14
md140
md141
md142
md143
md144
md145
md146
md147
md148
md149
md15
md150
md151
md152
md153
md154
md155
md156
md157
md158
md159
md16
md160
md161
md162
md163
md164
md165
md166
md167
md168
md169
md17
md170
md171
md172
md173
md174
md175
md176
md177
md178
md179
md18
md180
md181
md182
md183
md184
md185
md186
md187
md188
md189
md19
md190
md191
md192
md193
md194
md195
md196
md197
md198
md199
md2
md20
md200
md201
md202
md203
md204
md205
md206
md207
md208
md209
md21
md210
md211
md212
md213
md214
md215
md216
md217
md218
md219
md22
md220
md221
md222
md223
md224
md225
md226
md227
md228
md229
md23
md230
md231
md232
md233
md234
md235
md236
md237
md238
md239
md24
md240
md241
md242
md243
md244
md245
md246
md247
md248
md249
md25
md250
md251
md252
md253
md254
md255
md26
md27
md28
md29
md3
md30
md31
md32
md33
md34
md35
md36
md37
md38
md39
md4
md40
md41
md42
md43
md44
md45
md46
md47
md48
md49
md5
md50
md51
md52
md53
md54
md55
md56
md57
md58
md59
md6
md60
md61
md62
md63
md64
md65
md66
md67
md68
md69
md7
md70
md71
md72
md73
md74
md75
md76
md77
md78
md79
md8
md80
md81
md82
md83
md84
md85
md86
md87
md88
md89
md9
md90
md91
md92
md93
md94
md95
md96
md97
md98
md99
md_d0
md_d1
md_d10
md_d100
md_d101
md_d102
md_d103
md_d104
md_d105
md_d106
md_d107
md_d108
md_d109
md_d...

Message-ID: <email address hidden>
Date: Sun, 6 Feb 2005 18:03:21 +0100
From: <email address hidden> (Marco d'Itri)
To: "Jean-Luc Coulon (f5ibh)" <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#293817: udev: upgrade to 0.051-1 renders the system unbootable

--mYCpIKhGyMATD0i+
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Feb 06, "Jean-Luc Coulon (f5ibh)" <email address hidden> wrote:

> I get the followinf messages:
> Mounting a tmpfs over /dev... Done.
> Creating inital device nodes...Done.
>=20
> You will find attached the list of the created devices.
Are you sure that what you are seeing is really a tmpfs mounted over
/dev? (Check /proc/mounts.)
udev is not supposed to create BSD-style /dev/tty[a-z]* PTY devices, so
I think that you are looking at the on-disk /dev.

> Then if I reboot, I've the same crash as before (with some data =20
> corruption) :-/
udev cannot be the cause of data corruption.

--=20
ciao,
Marco

--mYCpIKhGyMATD0i+
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFCBk3ZFGfw2OHuP7ERAk07AKChDuBSPbbT4LtjOdiDEtg+9AONuwCeOkJC
EpRqWfv+Aftbgbe1TnuMzb8=
=t8+h
-----END PGP SIGNATURE-----

--mYCpIKhGyMATD0i+--

Message-Id: <1107710406l.10001l.0l@tangerine-64>
Date: Sun, 06 Feb 2005 17:20:06 +0000
From: "Jean-Luc Coulon (f5ibh)" <email address hidden>
To: Marco d'Itri <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#293817: udev: upgrade to 0.051-1 renders the system
 unbootable

Le 06.02.2005 18:03:21, Marco d'Itri a =E9crit=A0:
> On Feb 06, "Jean-Luc Coulon (f5ibh)" <email address hidden>
> wrote:
>=20
>> I get the followinf messages:
>> Mounting a tmpfs over /dev... Done.
>> Creating inital device nodes...Done.
>>=20
>> You will find attached the list of the created devices.
> Are you sure that what you are seeing is really a tmpfs mounted over
> /dev? (Check /proc/mounts.)

/dev/mapper/vg00-root_lv on / type xfs (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=3D5,mode=3D620)
usbfs on /proc/bus/usb type usbfs (rw)
none on /dev type tmpfs (ro)

> udev is not supposed to create BSD-style /dev/tty[a-z]* PTY devices, =20
> so
> I think that you are looking at the on-disk /dev.

Where I've to check?

>=20
>> Then if I reboot, I've the same crash as before (with some data
>> corruption) :-/
> udev cannot be the cause of data corruption.

Sure, but the reset of the system can.
>=20
> --
> ciao,
> Marco
>=20

J-L

Message-ID: <email address hidden>
Date: Sun, 6 Feb 2005 18:21:51 +0100
From: <email address hidden> (Marco d'Itri)
To: "Jean-Luc Coulon (f5ibh)" <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#293817: udev: upgrade to 0.051-1 renders the system unbootable

--X1bOJ3K7DJ5YkBrT
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Feb 06, "Jean-Luc Coulon (f5ibh)" <email address hidden> wrote:

> none on /dev type tmpfs (ro)
OK, we see a tmpfs. But why it is read only?
I think the udev init script is correct, so I cannot explain this.

--=20
ciao,
Marco

--X1bOJ3K7DJ5YkBrT
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFCBlIvFGfw2OHuP7ERAtQUAKCJvhSHbmruP545X0uiAcsRUKqR3gCdEfkR
0NOQsXHyWPMndo2g+RT+v3I=
=JQWU
-----END PGP SIGNATURE-----

--X1bOJ3K7DJ5YkBrT--

Clearly not happening for others, downgrading

Message-Id: <1108311534l.1512l.1l@tangerine-64>
Date: Sun, 13 Feb 2005 16:18:54 +0000
From: "Jean-Luc Coulon (f5ibh)" <email address hidden>
To: Marco d'Itri <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#293817: udev: upgrade to 0.051-1 renders the system
 unbootable

--=-K1K+ko8PsSgb2y01BEL/
Content-Type: text/plain; charset=ISO-8859-1; DelSp=Yes; Format=Flowed
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Dear Marco,

Le 06.02.2005 18:21:51, Marco d'Itri a =E9crit=A0:
> On Feb 06, "Jean-Luc Coulon (f5ibh)" <email address hidden>
> wrote:
>=20
>> none on /dev type tmpfs (ro)
> OK, we see a tmpfs. But why it is read only?
> I think the udev init script is correct, so I cannot explain this.

I've upgraded udev yesterday to 0.053-1.
I have rebooted the system several (ermmm ... many) times today and =20
with this version I've not the problem I've reported.

So I've downgraded to 0.051-1 and I got the problem again. Switching to =20
0.050-6 and no problem neither.

Then back to 0.053-1 with no problem.

>=20
> --
> ciao,
> Marco
>=20

Regards

Jean-Luc

--=-K1K+ko8PsSgb2y01BEL/
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQBCD33uUdGGXzzGnNARAlkWAJ92U9aFwp+kYELnmC4Lg2a0x2o09QCgmx8Z
MraBVbwU8v/kIHe5verl284=
=xF1k
-----END PGP SIGNATURE-----

--=-K1K+ko8PsSgb2y01BEL/--

Message-ID: <email address hidden>
Date: Sun, 13 Feb 2005 17:43:15 +0100
From: <email address hidden> (Marco d'Itri)
To: "Jean-Luc Coulon (f5ibh)" <email address hidden>,
 <email address hidden>
Subject: Re: Bug#293817: udev: upgrade to 0.051-1 renders the system unbootable

--YZ5djTAD1cGYuMQK
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Feb 13, "Jean-Luc Coulon (f5ibh)" <email address hidden> wrote:

> I've upgraded udev yesterday to 0.053-1.
> I have rebooted the system several (ermmm ... many) times today and =20
> with this version I've not the problem I've reported.
I *still* do not know how to explain it, but I will consider the bug
fixed.

--=20
ciao,
Marco

--YZ5djTAD1cGYuMQK
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD4DBQFCD4OjFGfw2OHuP7ERAvaFAJdhQm9a6IfIe7RVb2YsN+UhNJC0AKCUt0Oz
mj/hHyiNhYcpHdSdaAz2vw==
=kte8
-----END PGP SIGNATURE-----

--YZ5djTAD1cGYuMQK--

Closed upstream