I've been using linux-image-2.6.38-2-686 for some time without preblems.

After a dist-upgrade in Sid today I acquired
linux-image-2.6.39-1-686-pae. On booting this I had no connection
(wired) to my router. Also, on starting X (startx) the screen locked up
and I had to do a hard reset.

I reverted to linux-image-2.6.38-2-686, which was working previously,
and the same errors now appeared: no connection to router and lockup in
X.

Luckily, I still had linux-image-2.6.37-2-686 and this runs without
problems.

I can only suppose that some package which was also upgraded today
(there were various libraries) has affected both kernels. I would put in
a bug report but I have no idea where the problem could lie.

Any suggestions?

--
Anthony Campbell - ac@acampbell.org.uk
Microsoft-free zone - Using Debian GNU/Linux
http://www.acampbell.org.uk - sample my ebooks at
http://www.smashwords.com/profile/view/acampbell


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110522140818.GA2538@acampbell.org.uk">http://lists.debian.org/20110522140818.GA2538@acampbell.org.uk

On Sun, May 22, 2011 at 15:08 +0100, Anthony Campbell wrote:
> I can only suppose that some package which was also upgraded today
> (there were various libraries) has affected both kernels. I would put in
> a bug report but I have no idea where the problem could lie.
>
> Any suggestions?

A list of the packages that were upgraded would help tremendously, but my gut
feeling says udev. There were a couple of RC bugs against udev 169 (check the
BTS) so it would be interesting to know which version you have installed.
--
.'`. Wolodja Wentland <babilen@gmail.com>
: :' :
`. `'` 4096R/CAF14EFC
`- 081C B7CD FF04 2BA9 94EA 36B2 8B7F 7D30 CAF1 4EFC

On 22 May 2011, Wolodja Wentland wrote:
> On Sun, May 22, 2011 at 15:08 +0100, Anthony Campbell wrote:
> > I can only suppose that some package which was also upgraded today
> > (there were various libraries) has affected both kernels. I would put in
> > a bug report but I have no idea where the problem could lie.
> >
> > Any suggestions?
>
> A list of the packages that were upgraded would help tremendously, but my gut
> feeling says udev. There were a couple of RC bugs against udev 169 (check the
> BTS) so it would be interesting to know which version you have installed.
> --
> .'`. Wolodja Wentland <babilen@gmail.com>
> : :' :
> `. `'` 4096R/CAF14EFC
> `- 081C B7CD FF04 2BA9 94EA 36B2 8B7F 7D30 CAF1 4EFC



I have udev_169.1.

I've listed the packages installed in the last 3 days:


consolekit
sysvinit-utils
rpm-common
cabextract
initscripts
linux-image-686-pae
librdf0
libfuse2
binutils
perl
libck-connector0
luatex
libstdc++6-4.6-dev
isc-dhcp-common
linux-image-686
libtime-modules-perl
libgdu0
libdc1394-22
fuse-utils
librpmsign0
libperl5.12
librpmbuild2
perl-base
libstdc++6
patch
linux-libc-dev
libsqlite3-0
libgomp1
isc-dhcp-client
libgcc1
gcc-4.6
librpm2
gcc-4.6-base
perl-modules
libgudev-1.0-0
librpmio2
sysv-rc
libquadmath0
sysvinit
udev
dhcp3-client
g++-4.6
libgfortran3
libudev0
rpm2cpio
libglibmm-2.4-1c2a
rpm
libpam-ck-connector
cpp-4.6
linux-image-2.6.39-1-686-pae


--
Anthony Campbell - ac@acampbell.org.uk
Microsoft-free zone - Using Debian GNU/Linux
http://www.acampbell.org.uk - sample my ebooks at
http://www.smashwords.com/profile/view/acampbell


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110522152402.GB2538@acampbell.org.uk">http://lists.debian.org/20110522152402.GB2538@acampbell.org.uk

On Sun, 22 May 2011 16:24:02 +0100
Anthony Campbell <ac@acampbell.org.uk> wrote:

> On 22 May 2011, Wolodja Wentland wrote:
> > On Sun, May 22, 2011 at 15:08 +0100, Anthony Campbell wrote:
> > > I can only suppose that some package which was also upgraded today
> > > (there were various libraries) has affected both kernels. I would put in
> > > a bug report but I have no idea where the problem could lie.
> > >
> > > Any suggestions?
> >
> > A list of the packages that were upgraded would help tremendously, but my gut
> > feeling says udev. There were a couple of RC bugs against udev 169 (check the
> > BTS) so it would be interesting to know which version you have installed.

>
> I have udev_169.1.
>
> I've listed the packages installed in the last 3 days:
>
>
> consolekit
> sysvinit-utils
> rpm-common

//big snip//

Same situation here - the problem arose after yesterdays
upgrades...which are:


[UPGRADE] libgudev-1.0-0 169-1 -> 170-1
[UPGRADE] libudev0 169-1 -> 170-1
[UPGRADE] net-tools 1.60-23 -> 1.60-24
[UPGRADE] udev 169-1 -> 170-1
================================================== =======

Strange you have udev 169-1..mine was upgraded to 170-1 which
created the problem.


--
-- Frank --


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110522113433.0ef5512a.debianlist@videotron.ca">h ttp://lists.debian.org/20110522113433.0ef5512a.debianlist@videotron.ca

On Sun, May 22, 2011 at 16:24 +0100, Anthony Campbell wrote:
> On 22 May 2011, Wolodja Wentland wrote:
> > On Sun, May 22, 2011 at 15:08 +0100, Anthony Campbell wrote:
> > > I can only suppose that some package which was also upgraded today
> > > (there were various libraries) has affected both kernels. I would put in
> > > a bug report but I have no idea where the problem could lie.
> > >
> > > Any suggestions?
> >
> > A list of the packages that were upgraded would help tremendously, but my gut
> > feeling says udev. There were a couple of RC bugs against udev 169 (check the
> > BTS) so it would be interesting to know which version you have installed.

> I have udev_169.1.

I am almost entirely certain that udev is to blame, but luckily udev 170 has
just been uploaded and I would recommend to upgrade to that version.

--
.'`. Wolodja Wentland <babilen@gmail.com>
: :' :
`. `'` 4096R/CAF14EFC
`- 081C B7CD FF04 2BA9 94EA 36B2 8B7F 7D30 CAF1 4EFC

Wolodja Wentland wrote:

On Sun, May 22, 2011 at 15:08 +0100, Anthony Campbell wrote:

I can only suppose that some package which was also upgraded today
(there were various libraries) has affected both kernels. I would put in
a bug report but I have no idea where the problem could lie.

Any suggestions?


A list of the packages that were upgraded would help tremendously, but my gut
feeling says udev. There were a couple of RC bugs against udev 169 (check the
BTS) so it would be interesting to know which version you have installed.


Upgraded Sid to udev 170-1 and linux-image-2.6.39-1-amd64.
Runs fine
listbugs found no errors...

Hugo


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: irbai8$nh6$1@dough.gmane.org">http://lists.debian.org/irbai8$nh6$1@dough.gmane.org

On 2011-05-22 17:34 +0200, Frank McCormick wrote:

> Same situation here - the problem arose after yesterdays
> upgrades...which are:
>
>
> [UPGRADE] libgudev-1.0-0 169-1 -> 170-1
> [UPGRADE] libudev0 169-1 -> 170-1
> [UPGRADE] net-tools 1.60-23 -> 1.60-24
> [UPGRADE] udev 169-1 -> 170-1
> ================================================== =======

These packages became available just a few hours ago, so they were
probably not included in yesterday's upgrade.

> Strange you have udev 169-1..mine was upgraded to 170-1 which
> created the problem.

I doubt that. Note that the udev problem only manifests itself in the
initramfs, and the kernel you have just started might not have the
latest udev version in its initramfs.

Sven


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 87boyu7nca.fsf@turtle.gmx.de">http://lists.debian.org/87boyu7nca.fsf@turtle.gmx.de

On Sun, May 22, 2011 at 11:34 -0400, Frank McCormick wrote:

> Same situation here - the problem arose after yesterdays
> upgrades...which are:

> [UPGRADE] libgudev-1.0-0 169-1 -> 170-1
> [UPGRADE] libudev0 169-1 -> 170-1
> [UPGRADE] net-tools 1.60-23 -> 1.60-24
> [UPGRADE] udev 169-1 -> 170-1
> ================================================== =======
>
> Strange you have udev 169-1..mine was upgraded to 170-1 which
> created the problem.

That is interesting as from what I've heard on #debian-next (irc.oftc.net)
udev 170 fixed a lot of the problems introduced in the 169 version. (#627446
for example).

This *might* very well be a new issue, but I would suggest to check the BTS
for applicable reports. What symptoms do you experience exactly? If you want
you can also come to #debian-next and we can work on this issue or you could
file a new bug report if there is no applicable one already.
--
.'`. Wolodja Wentland <babilen@gmail.com>
: :' :
`. `'` 4096R/CAF14EFC
`- 081C B7CD FF04 2BA9 94EA 36B2 8B7F 7D30 CAF1 4EFC

On Sun, 22 May 2011 17:43:17 +0200
Sven Joachim <svenjoac@gmx.de> wrote:

> On 2011-05-22 17:34 +0200, Frank McCormick wrote:
>
> > Same situation here - the problem arose after yesterdays
> > upgrades...which are:
> >
> >
> > [UPGRADE] libgudev-1.0-0 169-1 -> 170-1
> > [UPGRADE] libudev0 169-1 -> 170-1
> > [UPGRADE] net-tools 1.60-23 -> 1.60-24
> > [UPGRADE] udev 169-1 -> 170-1
> > ================================================== =======
>
> These packages became available just a few hours ago, so they were
> probably not included in yesterday's upgrade.
>
> > Strange you have udev 169-1..mine was upgraded to 170-1 which
> > created the problem.
>
> I doubt that. Note that the udev problem only manifests itself in the
> initramfs, and the kernel you have just started might not have the
> latest udev version in its initramfs.

Sorry...what happened in my case was the new pae kernel was
installed on the 21st...but I did not reboot. Today when I
did, the boot failure happened. So I went back to the old kernel, and
this morning did an upgrade at which point udev 170-1 was installed.
But initramfs was not re-created. So when I tried again to boot into
the pae kernel it again failed. I will rebuild initramfs and we'll
see what happens.



--
-- Frank --


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110522121825.8873c47d.debianlist@videotron.ca">h ttp://lists.debian.org/20110522121825.8873c47d.debianlist@videotron.ca

On Sun, 22 May 2011 16:51:25 +0100
Wolodja Wentland <babilen@gmail.com> wrote:

> On Sun, May 22, 2011 at 11:34 -0400, Frank McCormick wrote:
>
> > Same situation here - the problem arose after yesterdays
> > upgrades...which are:
>
> > [UPGRADE] libgudev-1.0-0 169-1 -> 170-1
> > [UPGRADE] libudev0 169-1 -> 170-1
> > [UPGRADE] net-tools 1.60-23 -> 1.60-24
> > [UPGRADE] udev 169-1 -> 170-1
> > ================================================== =======
> >
> > Strange you have udev 169-1..mine was upgraded to 170-1 which
> > created the problem.
>
> That is interesting as from what I've heard on #debian-next (irc.oftc.net)
> udev 170 fixed a lot of the problems introduced in the 169 version. (#627446
> for example).


Sorry I wrote that without enough coffee See my other reply on
this issue.


--
-- Frank --


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110522121947.47a654d8.debianlist@videotron.ca">h ttp://lists.debian.org/20110522121947.47a654d8.debianlist@videotron.ca