Re: Linux 2.6.26-rc4

Re: Linux 2.6.26-rc4

[Linus Torvalds]

On Tue, 27 May 2008, Alejandro Riveira Fern=C3=A1ndez wrote:
> =20
>   Compiled and booting into 2.6.26-rc4
>=20
>  1) With splash quiet on grub line it doesn't boot (or i didin't wait=
 long
>     enough)
>  2) without quiet and splash I get into VT X filas becouse i use the =
evil
>     nvidia driver that's expected. But ubuntu failsafe mode (xserver =
with vesa
>     in low res) doesn't show up either *regression*

Can you give more details about where it stops?=20

>  3) i get an oops with network manager

=2E. again, please give the full oops, without that we just know that "=
an=20
oops happened".

>  4) if i try to run some sudo command it gets stuck (Crtl +C doesnt' =
help)
>     "ip route" gets stuck too. User programs i tried wrok fine (only =
ls and
>     htop). Network realted problem?

I assume it's related to the oops above - the oops probably happened wh=
ile=20
holding some mutex or other lock, which is why network-related stuff th=
en=20
blocks on that lock (which will never be released, since the oops kille=
d=20
the process that held it).

I suspect the oops is also why the bootup breaks, so it's likely all th=
e=20
same issue. Please save the dmesg into a file, reboot into a working=20
setup, and send that. Along with hw information (it's likely related to=
=20
your network device driver, since I've not seen an uproar of these kind=
s=20
of problems from everybody else..).

>  5) printk times on dmesg go crazy

More details, please, again.

			Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Linux 2.6.26-rc4

[Johannes Berg]

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


> >  4) if i try to run some sudo command it gets stuck (Crtl +C doesnt' help)
> >     "ip route" gets stuck too. User programs i tried wrok fine (only ls and
> >     htop). Network realted problem?
> 
> I assume it's related to the oops above - the oops probably happened while 
> holding some mutex or other lock, which is why network-related stuff then 
> blocks on that lock (which will never be released, since the oops killed 
> the process that held it).

rtnl, in fact, I suspect.

> I suspect the oops is also why the bootup breaks, so it's likely all the 
> same issue. Please save the dmesg into a file, reboot into a working 
> setup, and send that. Along with hw information (it's likely related to 
> your network device driver, since I've not seen an uproar of these kinds 
> of problems from everybody else..).

Actually, please apply the patch "rt2x00: Use atomic interface
iteration in irq context" before trying anything more, that'll fix it.
I'm not sure where Linville is hiding ;)

(http://article.gmane.org/gmane.linux.kernel.wireless.general/15268)

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

Re: Linux 2.6.26-rc4

[John W. Linville]

On Wed, May 28, 2008 at 10:17:57PM +0200, Johannes Berg wrote:

> > I suspect the oops is also why the bootup breaks, so it's likely al=
l the=20
> > same issue. Please save the dmesg into a file, reboot into a workin=
g=20
> > setup, and send that. Along with hw information (it's likely relate=
d to=20
> > your network device driver, since I've not seen an uproar of these =
kinds=20
> > of problems from everybody else..).
>=20
> Actually, please apply the patch "=EF=BB=BFrt2x00: Use atomic interfa=
ce
> iteration in irq context" before trying anything more, that'll fix it=
=2E
> I'm not sure where Linville is hiding ;)
>=20
> (http://article.gmane.org/gmane.linux.kernel.wireless.general/15268)

Zzzzzzz....huh, what?? :-)

I just sent a pull request to Dave M. with that patch in it.
Last weekend was a long one in the USA, so I apologize for the delay...

John
--=20
John W. Linville
linville@tuxdriver.com
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html