linux-kernel - Re: 2.6.24-rc1 freezes on powerbook at first boot stage

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <1195053964.4091.20.camel@johannes.berg>
Date:	Wed, 14 Nov 2007 16:26:04 +0100
From:	Johannes Berg <johannes@...solutions.net>
To:	Elimar Riesebieter <riesebie@...ec.de>
Cc:	Nathan Lynch <ntl@...ox.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linuxppc-dev@...abs.org, linux-usb-devel@...ts.sourceforge.net,
	linux-wireless@...r.kernel.org
Subject: Re: 2.6.24-rc1 freezes on powerbook at first boot stage


[FWIW, my powerbook worked with -rc1]

> 2.6.24-rc2 works so lala :)

> b43 doesn't authenticate via wpa (bluetooth isn't loaded):
> WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
> WEXT auth param 5 value 0x1 - Internet Systems Consortium DHCP Client V3.1.0

Those error messages are unrelated. My b43 works fine, even with a
multi-MAC patch.

> TCP: Hash tables configured (established 131072 bind 65536)
> TCP reno registered
> sysctl table check failed: /kernel .1 Writable sysctl directory
> Call Trace:
> [c1061e60] [c0008b28] show_stack+0x4c/0x1ac (unreliable)
> [c1061ea0] [c0047354] set_fail+0x50/0x68
> [c1061ec0] [c0047784] sysctl_check_table+0x418/0x714
> [c1061f30] [c00335b8] register_sysctl_table+0x64/0xb4
> [c1061f50] [c033fd5c] register_powersave_nap_sysctl+0x18/0x2c
> [c1061f60] [c03391e4] kernel_init+0xc0/0x2a0
> [c1061ff0] [c0011a58] kernel_thread+0x44/0x60

This has been fixed.

> There is a lot to do, but it seems to be a big, big code change in
> that version. This impressed me by looking at the git changes and
> the size of patches. And the rc's don't seem to be frozend versions.
> A lot of new code comes in....
> Let me know whether a complete dmesg is needed.

What is the problem? Why is this on wireless? It'd help if you'd make
one message per problem and post it to the correct mailing lists.

johannes

Download attachment "signature.asc" of type "application/pgp-signature" (829 bytes)