Re: 2.6.21-rc4-mm1

Re: 2.6.21-rc4-mm1

[Nicolas Mailhot]

Firmware loading is broken for all subsystems, not just network

→ http://bugzilla.kernel.org/show_bug.cgi?id=8239

-- 
Nicolas Mailhot

Re: 2.6.21-rc4-mm1

[Cornelia Huck]

On Wed, 28 Mar 2007 03:26:35 +0200,
Eric Rannaud <eric.rannaud@gmail.com> wrote:

> The reason for that original patch was that it is actually possible for the
> uevent functions to return -ENOMEM, the uevent buffer being statically
> allocated to BUFFER_SIZE (2048).

So maybe -ENOMEM should still be propagated? We just don't want to fail
device_add because of it.

> It used to be 1024 but that was not
> always enough and it was doubled a while ago [1]. Using add_uevent_var()
> makes this less of a problem as such an overflow should be catched
> cleanly [2].

Reminds me that I need to look into ccw_uevent :)

Re: 2.6.21-rc4-mm1

[Eric Rannaud]

On Tue, Mar 27, 2007 at 07:17:49PM +0200, Cornelia Huck wrote:
> On Tue, 27 Mar 2007 11:25:57 +0200,
> "Kay Sievers" <kay.sievers@vrfy.org> wrote:
> > Checking the uevent return value, will not prevent any malfunction,
> > usually this kind of "error handling" just prevents bringing up a
> > whole subsystem, or booting-up a box, because the needed device does
> > not exist at all.
> 
> OK, if we consider uevents to be non-vital to a functioning device.

The reason for that original patch was that it is actually possible for the
uevent functions to return -ENOMEM, the uevent buffer being statically
allocated to BUFFER_SIZE (2048). It used to be 1024 but that was not
always enough and it was doubled a while ago [1]. Using add_uevent_var()
makes this less of a problem as such an overflow should be catched
cleanly [2].

> OTOH, I think using something like uevent_suppress (maybe via
> dev_uevent_filter?) is a saner way to suppress a uevent than to return
> an error code in the uevent function.

That makes sense, I guess. I will try that.

Thanks.


[1] http://marc.info/?t=113797361200002&r=1&w=2
[2] uevent-use-add_uevent_var-instead-of-open-coding-it.patch in rc4-mm1

Re: 2.6.21-rc4-mm1

[Cornelia Huck]

On Tue, 27 Mar 2007 11:25:57 +0200,
"Kay Sievers" <kay.sievers@vrfy.org> wrote:

> I don't see any point in deregistering a kernel device, if the event
> to userspace goes wrong, or a subsytem returns a non-zero value in the
> filter.

But if we filter the event, we just return 0?
 
> Checking the uevent return value, will not prevent any malfunction,
> usually this kind of "error handling" just prevents bringing up a
> whole subsystem, or booting-up a box, because the needed device does
> not exist at all.

OK, if we consider uevents to be non-vital to a functioning device.

OTOH, I think using something like uevent_suppress (maybe via
dev_uevent_filter?) is a saner way to suppress a uevent than to return
an error code in the uevent function.

Re: 2.6.21-rc4-mm1

[Kay Sievers]

On 3/26/07, Eric Rannaud <eric.rannaud@gmail.com> wrote:
> On Mon, Mar 26, 2007 at 01:22:32AM -0800, Andrew Morton wrote:
> > On Mon, 26 Mar 2007 11:09:49 +0200 Cornelia Huck <cornelia.huck@de.ibm.com> wrote:
> > > > If so, do you think I should labour on with
> > > > uevent-improve-error-checking-and-handling.patch plus your fix, or should I
> > > > drop the lot?  (I'm inclined toward the latter, but I'm still not
> > > > sure which patch(es) need to be dropped).
> > >
> > > This depends on what semantics uevent returning an error code should
> > > have. The firmware code was using it to suppress uevents, but
> > > uevent_suppress is a better idea now. So if we want uevent returning !=
> > > 0 to imply "something really bad happened", all uevent functions have
> > > to be audited and those that work like firmware_uevent have to be
> > > converted to uevent_suppress. This would be cleaner, but I'm not sure
> > > it's worth the work.
> >
> > We're generally struggling to stay alive amongst all the bugs at present -
> > I'll drop all those patches.
>
> My mistake, I wrote the guilty patch
> uevent-improve-error-checking-and-handling.patch assuming it was safe to
> treat the return value as an error code, since several uevent functions
> returns things like -ENOMEM.
>
> Should I rework the patch as Cornelia suggests and resubmit later, when
> things have settled down a little?

I don't see any point in deregistering a kernel device, if the event
to userspace goes wrong, or a subsytem returns a non-zero value in the
filter.

Checking the uevent return value, will not prevent any malfunction,
usually this kind of "error handling" just prevents bringing up a
whole subsystem, or booting-up a box, because the needed device does
not exist at all.

Thanks,
Kay

Re: 2.6.21-rc4-mm1

[Badari Pulavarty]

On Mon, 2007-03-26 at 15:22 -0700, Andrew Morton wrote:
..
> > Unable to handle kernel NULL pointer dereference at 0000000000000020
> > RIP:
> >  [<ffffffff804ec090>] __sched_text_start+0x460/0x889
> > PGD 1c1898067 PUD 1c1897067 PMD 0
> > Oops: 0000 [1] SMP
> > last sysfs file: block/hda/range
> > CPU 3
> > Modules linked in:
> > Pid: 900, comm: boot Not tainted 2.6.21-rc4-mm1 #1
> > RIP: 0010:[<ffffffff804ec090>]  [<ffffffff804ec090>] __sched_text_start
> 
> This is a very popular oops, caused by the rsdl scheduler.  I don't _think_
> we yet know exactly why it is happening.  Con, did you get to the bottom
> of this?
> 
> We don't know why it confused kallsyms either.
> 
> I'll try to shove rc5-mm1 out the door this evening, minus rsdl.  And
> -mm2, with rsdl.

Okay, my ppc64 box hangs on boot. It could be different. I will wait
till rc5-mm1 for debugging that one.

Thanks,
Badari

...
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
ReiserFS: sda2: found reiserfs format "3.6" with standard journal
ReiserFS: sda2: using ordered data mode
ReiserFS: sda2: journal params: device sda2, size 8192, journal first
block 18, max trans len 1024, max batch 900, max commit age 30, max
trans age 30
ReiserFS: sda2: checking transaction log (sda2)
ReiserFS: sda2: Using r5 hash to sort names
VFS: Mounted root (reiserfs filesystem) readonly.
Freeing unused kernel memory: 272k freed
Warning: unable to open an initial console.
ioctl32(showconsole:1020): Unknown cmd fd(0) cmd(40045432){00} arg
(ffecdb48) on /dev/tty0
ioctl32(showconsole:1048): Unknown cmd fd(0) cmd(40045432){00} arg
(ffb4aad8) on /dev/tty0
PDC20275: IDE controller at PCI slot 0002:d0:01.0
PDC20275: chipset revision 1
PDC20275: PLL input clock is 32814 kHz
PDC20275: 100% native mode on irq 119
    ide2: BM-DMA at 0x2eec00-0x2eec07, BIOS settings: hde:pio, hdf:pio
    ide3: BM-DMA at 0x2eec08-0x2eec0f, BIOS settings: hdg:pio, hdh:pio
scsi 0:0:15:0: Attached scsi generic sg0 type 13
scsi 0:255:255:255: Attached scsi generic sg1 type 31
sd 1:0:4:0: Attached scsi generic sg2 type 0
sd 1:0:5:0: Attached scsi generic sg3 type 0
scsi 1:0:15:0: Attached scsi generic sg4 type 13
scsi 1:255:255:255: Attached scsi generic sg5 type 31
hde: IBM DROM00205, ATAPI CD/DVD-ROM drive
ide2 at 0x2ee400-0x2ee407,0x2edc02 on irq 119
hde: ATAPI 24X DVD-ROM drive, 256kB Cache
Uniform CD-ROM driver Revision: 3.20
device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-
devel@redhat.com
ioctl32(showconsole:1918): Unknown cmd fd(0) cmd(40045432){00} arg
(fff00ad8) on /dev/tty0
loop: loaded (max 8 devices)
ioctl32(showconsole:2091): Unknown cmd fd(0) cmd(40045432){00} arg
(fff71ae8) on /dev/tty0
Adding 1050616k swap on /dev/sdb2.  Priority:-1 extents:1
across:1050616k
ioctl32(showconsole:2137): Unknown cmd fd(0) cmd(40045432){00} arg
(ffdd7b28) on /dev/tty0
e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex, Flow
Control: RX
audit(1174945021.442:2): audit_pid=2735 old=0 by auid=4294967295

Re: 2.6.21-rc4-mm1

[Paul Mackerras]

Badari Pulavarty writes:

> Patch causing the problem in -mm:
> 	ibmebus-uevent-support.patch
> 
> I don't see where ^[$,1rx^[(Bof_device_uevent^[$,1ry^[(B is defined :(

That patch depends on another one from Sylvain Munaut that I haven't
yet managed to get Ben H. to express an opinion on, and which isn't in
-mm.  I thought I mentioned that to Andrew, but maybe I only intended
to...

Paul.

Re: 2.6.21-rc4-mm1

[Greg KH]

On Mon, Mar 26, 2007 at 09:35:48PM +0200, Jean Delvare wrote:
> 
> Greg, please update your copy with this version of the patch. The only
> change is that sound/ppc/beep.c is removed from the patch.

Done.

thanks,

greg k-h

Re: 2.6.21-rc4-mm1

[Andrew Morton]

On Mon, 26 Mar 2007 13:57:57 -0800
Badari Pulavarty <pbadari@gmail.com> wrote:

> On Mon, 2007-03-19 at 20:56 -0800, Andrew Morton wrote:
> > Temporarily at
> > 
> >   http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
> > 
> > Will appear later at
> > 
> >   ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/
> > 
> 
> 
> Panics my x86-64 box. 2.6.21-rc4 works fine.
> Ideas on where to start ? Bisect ?
> 
> Thanks,
> Badari
> 
> ..
> ReiserFS: hda2: found reiserfs format "3.6" with standard journal
> ReiserFS: hda2: using ordered data mode
> ReiserFS: hda2: journal params: device hda2, size 8192, journal first
> block 18, max trans len 1024, max batch 900, max commit age 30, max
> trans age 30
> ReiserFS: hda2: checking transaction log (hda2)
> ReiserFS: hda2: Using r5 hash to sort names
> VFS: Mounted root (reiserfs filesystem) readonly.
> Freeing unused kernel memory: 376k freed
> INIT: version 2.86 booting
> Unable to handle kernel NULL pointer dereference at 0000000000000020
> RIP:
>  [<ffffffff804ec090>] __sched_text_start+0x460/0x889
> PGD 1c1898067 PUD 1c1897067 PMD 0
> Oops: 0000 [1] SMP
> last sysfs file: block/hda/range
> CPU 3
> Modules linked in:
> Pid: 900, comm: boot Not tainted 2.6.21-rc4-mm1 #1
> RIP: 0010:[<ffffffff804ec090>]  [<ffffffff804ec090>] __sched_text_start

This is a very popular oops, caused by the rsdl scheduler.  I don't _think_
we yet know exactly why it is happening.  Con, did you get to the bottom
of this?

We don't know why it confused kallsyms either.

I'll try to shove rc5-mm1 out the door this evening, minus rsdl.  And
-mm2, with rsdl.

Re: 2.6.21-rc4-mm1

[Badari Pulavarty]

On Mon, 2007-03-19 at 20:56 -0800, Andrew Morton wrote:
> Temporarily at
> 
>   http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
> 
> Will appear later at
> 
>   ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/
> 


Panics my x86-64 box. 2.6.21-rc4 works fine.
Ideas on where to start ? Bisect ?

Thanks,
Badari

..
ReiserFS: hda2: found reiserfs format "3.6" with standard journal
ReiserFS: hda2: using ordered data mode
ReiserFS: hda2: journal params: device hda2, size 8192, journal first
block 18, max trans len 1024, max batch 900, max commit age 30, max
trans age 30
ReiserFS: hda2: checking transaction log (hda2)
ReiserFS: hda2: Using r5 hash to sort names
VFS: Mounted root (reiserfs filesystem) readonly.
Freeing unused kernel memory: 376k freed
INIT: version 2.86 booting
Unable to handle kernel NULL pointer dereference at 0000000000000020
RIP:
 [<ffffffff804ec090>] __sched_text_start+0x460/0x889
PGD 1c1898067 PUD 1c1897067 PMD 0
Oops: 0000 [1] SMP
last sysfs file: block/hda/range
CPU 3
Modules linked in:
Pid: 900, comm: boot Not tainted 2.6.21-rc4-mm1 #1
RIP: 0010:[<ffffffff804ec090>]  [<ffffffff804ec090>] __sched_text_start
+0x460/0x889
RSP: 0018:ffff8101014dfee0  EFLAGS: 00010086
RAX: 0000000000000001 RBX: ffff8101c0010218 RCX: 0000000000000000
RDX: ffff8101c0010ae8 RSI: 0000000000000000 RDI: ffffffffffffffd0
RBP: ffff8101014dff70 R08: 000000000000008c R09: ffff8101c0010ad8
R10: 000000000000001c R11: ffffffff802099be R12: ffff8101c000f780
R13: 0000000000000001 R14: 0000000a7bcffd6e R15: 0000000000000003
FS:  00002b9ef1d40ae0(0000) GS:ffff8101c07b6e40(0000)
knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 0000000000000020 CR3: 0000000100f8d000 CR4: 00000000000006e0
Process boot (pid: 900, threadinfo ffff8101014de000, task
ffff8101014dd490)
Stack:  0000038c802848cf ffff8101014dfef8 ffffffff80238d82
ffff8101014dd490
 ffffffffffffffd0 ffff8101014dd630 0000000000000000 00007fffb955ff80
 00007fffb9560090 0000000000000000 ffffffff802099be ffff8101014dff48
Call Trace:
 [<ffffffff80238d82>] recalc_sigpending+0x12/0x20
 [<ffffffff802099be>] system_call+0x7e/0x83
 [<ffffffff80207ef3>] sys_clone+0x23/0x30
 [<ffffffff80209a28>] sysret_careful+0xd/0x10


Code: 48 39 47 50 74 38 48 c7 47 40 00 00 00 00 48 63 56 f4 49 8b
RIP  [<ffffffff804ec090>] __sched_text_start+0x460/0x889
 RSP <ffff8101014dfee0>
CR2: 0000000000000020

Re: 2.6.21-rc4-mm1

[J.A. Magallón]

On Fri, 23 Mar 2007 00:27:09 +0100, "J.A. Magallón" <jamagallon@ono.com> wrote:

> On Mon, 19 Mar 2007 20:56:23 -0800, Andrew Morton <akpm@linux-foundation.org> wrote:
> 
> > 
> > Temporarily at
> > 
> >   http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
> > 
> > Will appear later at
> > 
> >   ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/
> > 
> 
> Is anybody having problems with optical drives and this kernel ?
> I can't get my dvdrw to spit any events to udevmonitor. If I mount it
> manually everything works fine.
> 
> Perhaps the problem is in hal/g-v-m or anything else, but I suppose that
> udevmonitor receives events directly from kernel, isn't it ?
> 

Finally, this was a userspace problem (hal):

http://lists.freedesktop.org/archives/hal/2007-March/007545.html

What I don't understand is this: I supposed that udev (and so udevmonitor)
is independent of hal, more or less hal monitors udev events and does things,
like looking the disc label and so on.

But I do not get any events in udevmonitor if I'm not logged in gnome.
How's this ?

TIA

--
J.A. Magallon <jamagallon()ono!com>     \               Software is like sex:
                                         \         It's better when it's free
Mandriva Linux release 2007.1 (Cooker) for i586
Linux 2.6.20-jam05 (gcc 4.1.2 20070302 (prerelease) (4.1.2-1mdv2007.1)) #2 SMP PREEMPT

Re: 2.6.21-rc4-mm1

[Badari Pulavarty]

On Mon, 2007-03-19 at 20:56 -0800, Andrew Morton wrote:
> Temporarily at
> 
>   http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
> 
> Will appear later at
> 
>   ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/

 # make -j8 modules
  CHK     include/linux/version.h
  CHK     include/linux/utsrelease.h
  LD [M]  sound/soundcore.o
  CC [M]  sound/ppc/beep.o
sound/ppc/beep.c: In function ‘snd_pmac_attach_beep’:
sound/ppc/beep.c:224: error: dereferencing pointer to incomplete type
sound/ppc/beep.c:242: error: dereferencing pointer to incomplete type
sound/ppc/beep.c:265: error: dereferencing pointer to incomplete type
sound/ppc/beep.c: In function ‘snd_pmac_detach_beep’:
sound/ppc/beep.c:275: error: dereferencing pointer to incomplete type
make[2]: *** [sound/ppc/beep.o] Error 1
make[1]: *** [sound/ppc] Error 2
make: *** [sound] Error 2
make: *** Waiting for unfinished jobs....


Patch that is causing the problem in -mm:
gregkh-pci-pci-cleanup-the-includes-of-linux-pcih.patch

sound/ppc/beep.c needs to include <linux/pci.h>

Thanks,
Badari
	

Re: 2.6.21-rc4-mm1

[Badari Pulavarty]

On Mon, 2007-03-19 at 20:56 -0800, Andrew Morton wrote:
> Temporarily at
> 
>   http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
> 
> Will appear later at
> 
>   ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/
> 


  CC      arch/powerpc/kernel/ibmebus.o
arch/powerpc/kernel/ibmebus.c:463: error: ‘of_device_uevent’ undeclared
here (not in a function)
make[1]: *** [arch/powerpc/kernel/ibmebus.o] Error 1
make: *** [arch/powerpc/kernel] Error 2

Patch causing the problem in -mm:
	ibmebus-uevent-support.patch

I don't see where ‘of_device_uevent’ is defined :(

Thanks,
Badari

Re: 2.6.21-rc4-mm1

[Jean Delvare]

Hi Badari,

On Mon, 26 Mar 2007 12:05:56 -0800, Badari Pulavarty wrote:
> On Mon, 2007-03-19 at 20:56 -0800, Andrew Morton wrote:
> > Temporarily at
> > 
> >   http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
> > 
> > Will appear later at
> > 
> >   ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/
> 
>  # make -j8 modules
>   CHK     include/linux/version.h
>   CHK     include/linux/utsrelease.h
>   LD [M]  sound/soundcore.o
>   CC [M]  sound/ppc/beep.o
> sound/ppc/beep.c: In function ‘snd_pmac_attach_beep’:
> sound/ppc/beep.c:224: error: dereferencing pointer to incomplete type
> sound/ppc/beep.c:242: error: dereferencing pointer to incomplete type
> sound/ppc/beep.c:265: error: dereferencing pointer to incomplete type
> sound/ppc/beep.c: In function ‘snd_pmac_detach_beep’:
> sound/ppc/beep.c:275: error: dereferencing pointer to incomplete type
> make[2]: *** [sound/ppc/beep.o] Error 1
> make[1]: *** [sound/ppc] Error 2
> make: *** [sound] Error 2
> make: *** Waiting for unfinished jobs....
> 
> 
> Patch that is causing the problem in -mm:
> gregkh-pci-pci-cleanup-the-includes-of-linux-pcih.patch
> 
> sound/ppc/beep.c needs to include <linux/pci.h>

Good catch, thanks for reporting. I expected a few false positives to
be left in my patch, but couldn't test everything.

Greg, please update your copy with this version of the patch. The only
change is that sound/ppc/beep.c is removed from the patch.

* * * * *

I noticed that many source files include <linux/pci.h> while they do
not appear to need it. Here is an attempt to clean it all up.

In order to find all possibly affected files, I searched for all
files including <linux/pci.h> but without any other occurence of "pci"
or "PCI". I removed the include statement from all of these, then I
compiled an allmodconfig kernel on both i386 and x86_64 and fixed the
false positives manually.

My tests covered 66% of the affected files, so there could be false
positives remaining. Untested files are:

arch/alpha/kernel/err_common.c
arch/alpha/kernel/err_ev6.c
arch/alpha/kernel/err_ev7.c
arch/ia64/sn/kernel/huberror.c
arch/ia64/sn/kernel/xpnet.c
arch/m68knommu/kernel/dma.c
arch/mips/lib/iomap.c
arch/powerpc/platforms/pseries/ras.c
arch/ppc/8260_io/enet.c
arch/ppc/8260_io/fcc_enet.c
arch/ppc/8xx_io/enet.c
arch/ppc/syslib/ppc4xx_sgdma.c
arch/sh64/mach-cayman/iomap.c
arch/xtensa/kernel/xtensa_ksyms.c
arch/xtensa/platform-iss/setup.c
drivers/i2c/busses/i2c-at91.c
drivers/i2c/busses/i2c-mpc.c
drivers/media/video/saa711x.c
drivers/misc/hdpuftrs/hdpu_cpustate.c
drivers/misc/hdpuftrs/hdpu_nexus.c
drivers/net/au1000_eth.c
drivers/net/fec_8xx/fec_main.c
drivers/net/fec_8xx/fec_mii.c
drivers/net/fs_enet/fs_enet-main.c
drivers/net/fs_enet/mac-fcc.c
drivers/net/fs_enet/mac-fec.c
drivers/net/fs_enet/mac-scc.c
drivers/net/fs_enet/mii-bitbang.c
drivers/net/fs_enet/mii-fec.c
drivers/net/ibm_emac/ibm_emac_core.c
drivers/net/lasi_82596.c
drivers/parisc/hppb.c
drivers/sbus/sbus.c
drivers/video/g364fb.c
drivers/video/platinumfb.c
drivers/video/stifb.c
drivers/video/valkyriefb.c
include/asm-arm/arch-ixp4xx/dma.h
sound/oss/au1550_ac97.c

I would welcome test reports for these files. I am fine with removing
the untested files from the patch if the general opinion is that these
changes aren't safe. The tested part would still be nice to have.

Note that this patch depends on another header fixup patch I submitted
to LKML yesterday:
  [PATCH] scatterlist.h needs types.h
  http://lkml.org/lkml/2007/3/01/141

Signed-off-by: Jean Delvare <khali@linux-fr.org>
---
 arch/alpha/kernel/err_common.c               |    1 -
 arch/alpha/kernel/err_ev6.c                  |    1 -
 arch/alpha/kernel/err_ev7.c                  |    1 -
 arch/i386/kernel/cpu/cpufreq/speedstep-lib.c |    1 -
 arch/i386/kernel/cpu/cpufreq/speedstep-smi.c |    2 +-
 arch/ia64/sn/kernel/huberror.c               |    1 -
 arch/ia64/sn/kernel/xpnet.c                  |    1 -
 arch/m68knommu/kernel/dma.c                  |    1 -
 arch/mips/lib/iomap.c                        |    1 -
 arch/powerpc/platforms/pseries/ras.c         |    1 -
 arch/ppc/8260_io/enet.c                      |    1 -
 arch/ppc/8260_io/fcc_enet.c                  |    1 -
 arch/ppc/8xx_io/enet.c                       |    1 -
 arch/ppc/syslib/ppc4xx_sgdma.c               |    1 -
 arch/sh64/mach-cayman/iomap.c                |    1 -
 arch/xtensa/kernel/xtensa_ksyms.c            |    1 -
 arch/xtensa/platform-iss/setup.c             |    1 -
 drivers/ata/pata_winbond.c                   |    1 -
 drivers/atm/adummy.c                         |    1 -
 drivers/char/hw_random/via-rng.c             |    1 -
 drivers/char/pcmcia/synclink_cs.c            |    1 -
 drivers/char/tpm/tpm.h                       |    1 -
 drivers/char/watchdog/sc1200wdt.c            |    1 -
 drivers/char/watchdog/scx200_wdt.c           |    2 +-
 drivers/i2c/busses/i2c-at91.c                |    1 -
 drivers/i2c/busses/i2c-mpc.c                 |    1 -
 drivers/i2c/busses/i2c-pca-isa.c             |    1 -
 drivers/ieee1394/hosts.c                     |    1 -
 drivers/infiniband/core/cm.c                 |    1 -
 drivers/infiniband/core/iwcm.c               |    1 -
 drivers/infiniband/core/mad_priv.h           |    1 -
 drivers/infiniband/core/multicast.c          |    1 -
 drivers/infiniband/core/sa_query.c           |    1 -
 drivers/infiniband/core/user_mad.c           |    1 -
 drivers/infiniband/hw/ipath/ipath_fs.c       |    1 -
 drivers/infiniband/hw/ipath/ipath_layer.c    |    1 -
 drivers/infiniband/hw/ipath/ipath_stats.c    |    2 --
 drivers/infiniband/hw/ipath/ipath_sysfs.c    |    1 -
 drivers/infiniband/hw/mthca/mthca_memfree.h  |    1 -
 drivers/infiniband/ulp/ipoib/ipoib.h         |    1 -
 drivers/isdn/hisax/netjet.c                  |    1 -
 drivers/isdn/hysdn/hysdn_proclog.c           |    1 -
 drivers/media/dvb/cinergyT2/cinergyT2.c      |    2 +-
 drivers/media/video/adv7170.c                |    1 -
 drivers/media/video/adv7175.c                |    1 -
 drivers/media/video/bt819.c                  |    1 -
 drivers/media/video/bt856.c                  |    1 -
 drivers/media/video/bt866.c                  |    1 -
 drivers/media/video/cx88/cx88-tvaudio.c      |    1 -
 drivers/media/video/em28xx/em28xx-cards.c    |    1 -
 drivers/media/video/saa7111.c                |    1 -
 drivers/media/video/saa7114.c                |    1 -
 drivers/media/video/saa711x.c                |    1 -
 drivers/media/video/saa7185.c                |    1 -
 drivers/misc/hdpuftrs/hdpu_cpustate.c        |    1 -
 drivers/misc/hdpuftrs/hdpu_nexus.c           |    1 -
 drivers/mtd/devices/doc2000.c                |    1 -
 drivers/mtd/devices/doc2001.c                |    1 -
 drivers/mtd/devices/doc2001plus.c            |    1 -
 drivers/mtd/devices/docecc.c                 |    1 -
 drivers/mtd/inftlmount.c                     |    1 -
 drivers/mtd/nand/cs553x_nand.c               |    1 -
 drivers/mtd/nftlcore.c                       |    1 -
 drivers/net/atl1/atl1_param.c                |    1 -
 drivers/net/au1000_eth.c                     |    1 -
 drivers/net/fec_8xx/fec_main.c               |    1 -
 drivers/net/fec_8xx/fec_mii.c                |    1 -
 drivers/net/fs_enet/fs_enet-main.c           |    1 -
 drivers/net/fs_enet/mac-fcc.c                |    1 -
 drivers/net/fs_enet/mac-fec.c                |    1 -
 drivers/net/fs_enet/mac-scc.c                |    1 -
 drivers/net/fs_enet/mii-bitbang.c            |    1 -
 drivers/net/fs_enet/mii-fec.c                |    1 -
 drivers/net/ibm_emac/ibm_emac_core.c         |    1 -
 drivers/net/ixgb/ixgb_osdep.h                |    1 -
 drivers/net/lasi_82596.c                     |    1 -
 drivers/net/tokenring/madgemc.c              |    1 -
 drivers/net/tokenring/smctr.c                |    1 -
 drivers/net/tulip/21142.c                    |    1 -
 drivers/net/tulip/pnic.c                     |    1 -
 drivers/net/tulip/pnic2.c                    |    1 -
 drivers/net/tulip/timer.c                    |    1 -
 drivers/net/tulip/tulip.h                    |    1 +
 drivers/net/wan/lmc/lmc_media.c              |    1 -
 drivers/net/wan/lmc/lmc_proto.c              |    1 -
 drivers/net/wan/pc300_tty.c                  |    1 -
 drivers/parisc/hppb.c                        |    2 --
 drivers/pcmcia/cs.c                          |    1 -
 drivers/pcmcia/socket_sysfs.c                |    1 -
 drivers/sbus/sbus.c                          |    1 -
 drivers/scsi/aacraid/dpcsup.c                |    1 -
 drivers/scsi/aacraid/sa.c                    |    1 -
 drivers/scsi/aha1542.c                       |    1 -
 drivers/scsi/aic94xx/aic94xx_scb.c           |    1 -
 drivers/scsi/arcmsr/arcmsr_attr.c            |    1 -
 drivers/scsi/libsas/sas_expander.c           |    1 -
 drivers/scsi/libsrp.c                        |    1 -
 drivers/usb/net/kaweth.c                     |    1 -
 drivers/video/aty/radeon_i2c.c               |    1 -
 drivers/video/g364fb.c                       |    1 -
 drivers/video/platinumfb.c                   |    1 -
 drivers/video/stifb.c                        |    1 -
 drivers/video/valkyriefb.c                   |    1 -
 include/asm-arm/arch-ixp4xx/dma.h            |    1 -
 include/rdma/ib_mad.h                        |    2 --
 sound/core/init.c                            |    1 -
 sound/oss/au1550_ac97.c                      |    1 -
 sound/oss/soundcard.c                        |    1 +
 sound/pci/ca0106/ca0106_mixer.c              |    2 +-
 sound/pci/ca0106/ca0106_proc.c               |    2 +-
 sound/pci/cs46xx/dsp_spos.c                  |    1 -
 sound/pci/cs46xx/dsp_spos_scb_lib.c          |    1 -
 sound/pci/hda/hda_generic.c                  |    1 -
 sound/pci/hda/hda_proc.c                     |    1 -
 sound/pci/hda/patch_atihdmi.c                |    1 -
 sound/pci/hda/patch_si3054.c                 |    1 -
 sound/pci/hda/patch_via.c                    |    1 -
 117 files changed, 7 insertions(+), 118 deletions(-)

--- linux-2.6.21-rc5.orig/arch/alpha/kernel/err_common.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/arch/alpha/kernel/err_common.c	2007-03-26 13:54:33.000000000 +0200
@@ -7,7 +7,6 @@
  */
 
 #include <linux/init.h>
-#include <linux/pci.h>
 #include <linux/sched.h>
 
 #include <asm/io.h>
--- linux-2.6.21-rc5.orig/arch/alpha/kernel/err_ev6.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/arch/alpha/kernel/err_ev6.c	2007-03-26 13:54:33.000000000 +0200
@@ -7,7 +7,6 @@
  */
 
 #include <linux/init.h>
-#include <linux/pci.h>
 #include <linux/sched.h>
 
 #include <asm/io.h>
--- linux-2.6.21-rc5.orig/arch/alpha/kernel/err_ev7.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/arch/alpha/kernel/err_ev7.c	2007-03-26 13:54:33.000000000 +0200
@@ -7,7 +7,6 @@
  */
 
 #include <linux/init.h>
-#include <linux/pci.h>
 #include <linux/sched.h>
 
 #include <asm/io.h>
--- linux-2.6.21-rc5.orig/arch/i386/kernel/cpu/cpufreq/speedstep-lib.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/arch/i386/kernel/cpu/cpufreq/speedstep-lib.c	2007-03-26 13:54:33.000000000 +0200
@@ -13,7 +13,6 @@
 #include <linux/moduleparam.h>
 #include <linux/init.h>
 #include <linux/cpufreq.h>
-#include <linux/pci.h>
 #include <linux/slab.h>
 
 #include <asm/msr.h>
--- linux-2.6.21-rc5.orig/arch/i386/kernel/cpu/cpufreq/speedstep-smi.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/arch/i386/kernel/cpu/cpufreq/speedstep-smi.c	2007-03-26 13:54:33.000000000 +0200
@@ -17,10 +17,10 @@
 #include <linux/moduleparam.h>
 #include <linux/init.h>
 #include <linux/cpufreq.h>
-#include <linux/pci.h>
 #include <linux/slab.h>
 #include <linux/delay.h>
 #include <asm/ist.h>
+#include <asm/io.h>
 
 #include "speedstep-lib.h"
 
--- linux-2.6.21-rc5.orig/arch/ia64/sn/kernel/huberror.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/arch/ia64/sn/kernel/huberror.c	2007-03-26 13:54:33.000000000 +0200
@@ -8,7 +8,6 @@
 
 #include <linux/types.h>
 #include <linux/interrupt.h>
-#include <linux/pci.h>
 #include <asm/delay.h>
 #include <asm/sn/sn_sal.h>
 #include "ioerror.h"
--- linux-2.6.21-rc5.orig/arch/ia64/sn/kernel/xpnet.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/arch/ia64/sn/kernel/xpnet.c	2007-03-26 13:54:33.000000000 +0200
@@ -24,7 +24,6 @@
 
 #include <linux/module.h>
 #include <linux/kernel.h>
-#include <linux/pci.h>
 #include <linux/init.h>
 #include <linux/ioport.h>
 #include <linux/netdevice.h>
--- linux-2.6.21-rc5.orig/arch/m68knommu/kernel/dma.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/arch/m68knommu/kernel/dma.c	2007-03-26 13:54:33.000000000 +0200
@@ -8,7 +8,6 @@
 #include <linux/types.h>
 #include <linux/mm.h>
 #include <linux/string.h>
-#include <linux/pci.h>
 #include <asm/io.h>
 
 void *dma_alloc_coherent(struct device *dev, size_t size,
--- linux-2.6.21-rc5.orig/arch/mips/lib/iomap.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/arch/mips/lib/iomap.c	2007-03-26 13:54:33.000000000 +0200
@@ -6,7 +6,6 @@
  * (C) Copyright 2007 MIPS Technologies, Inc.
  *     written by Ralf Baechle <ralf@linux-mips.org>
  */
-#include <linux/pci.h>
 #include <linux/module.h>
 #include <asm/io.h>
 
--- linux-2.6.21-rc5.orig/arch/powerpc/platforms/pseries/ras.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/arch/powerpc/platforms/pseries/ras.c	2007-03-26 13:54:33.000000000 +0200
@@ -31,7 +31,6 @@
 #include <linux/timex.h>
 #include <linux/init.h>
 #include <linux/slab.h>
-#include <linux/pci.h>
 #include <linux/delay.h>
 #include <linux/irq.h>
 #include <linux/random.h>
--- linux-2.6.21-rc5.orig/arch/ppc/8260_io/enet.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/arch/ppc/8260_io/enet.c	2007-03-26 13:54:33.000000000 +0200
@@ -32,7 +32,6 @@
 #include <linux/ioport.h>
 #include <linux/slab.h>
 #include <linux/interrupt.h>
-#include <linux/pci.h>
 #include <linux/init.h>
 #include <linux/delay.h>
 #include <linux/netdevice.h>
--- linux-2.6.21-rc5.orig/arch/ppc/8260_io/fcc_enet.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/arch/ppc/8260_io/fcc_enet.c	2007-03-26 13:54:33.000000000 +0200
@@ -29,7 +29,6 @@
 #include <linux/ioport.h>
 #include <linux/slab.h>
 #include <linux/interrupt.h>
-#include <linux/pci.h>
 #include <linux/init.h>
 #include <linux/delay.h>
 #include <linux/netdevice.h>
--- linux-2.6.21-rc5.orig/arch/ppc/8xx_io/enet.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/arch/ppc/8xx_io/enet.c	2007-03-26 13:54:33.000000000 +0200
@@ -30,7 +30,6 @@
 #include <linux/ioport.h>
 #include <linux/slab.h>
 #include <linux/interrupt.h>
-#include <linux/pci.h>
 #include <linux/init.h>
 #include <linux/delay.h>
 #include <linux/netdevice.h>
--- linux-2.6.21-rc5.orig/arch/ppc/syslib/ppc4xx_sgdma.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/arch/ppc/syslib/ppc4xx_sgdma.c	2007-03-26 13:54:33.000000000 +0200
@@ -23,7 +23,6 @@
 #include <linux/mm.h>
 #include <linux/init.h>
 #include <linux/module.h>
-#include <linux/pci.h>
 
 #include <asm/system.h>
 #include <asm/io.h>
--- linux-2.6.21-rc5.orig/arch/sh64/mach-cayman/iomap.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/arch/sh64/mach-cayman/iomap.c	2007-03-26 13:54:33.000000000 +0200
@@ -9,7 +9,6 @@
  * License.  See the file "COPYING" in the main directory of this archive
  * for more details.
  */
-#include <linux/pci.h>
 #include <asm/io.h>
 #include <asm/cayman.h>
 
--- linux-2.6.21-rc5.orig/arch/xtensa/kernel/xtensa_ksyms.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/arch/xtensa/kernel/xtensa_ksyms.c	2007-03-26 13:54:33.000000000 +0200
@@ -18,7 +18,6 @@
 #include <linux/interrupt.h>
 #include <asm/irq.h>
 #include <linux/in6.h>
-#include <linux/pci.h>
 #include <linux/ide.h>
 
 #include <asm/uaccess.h>
--- linux-2.6.21-rc5.orig/arch/xtensa/platform-iss/setup.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/arch/xtensa/platform-iss/setup.c	2007-03-26 13:54:33.000000000 +0200
@@ -20,7 +20,6 @@
 #include <linux/init.h>
 #include <linux/errno.h>
 #include <linux/reboot.h>
-#include <linux/pci.h>
 #include <linux/kdev_t.h>
 #include <linux/types.h>
 #include <linux/major.h>
--- linux-2.6.21-rc5.orig/drivers/ata/pata_winbond.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/ata/pata_winbond.c	2007-03-26 13:54:33.000000000 +0200
@@ -8,7 +8,6 @@
 
 #include <linux/kernel.h>
 #include <linux/module.h>
-#include <linux/pci.h>
 #include <linux/init.h>
 #include <linux/blkdev.h>
 #include <linux/delay.h>
--- linux-2.6.21-rc5.orig/drivers/atm/adummy.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/atm/adummy.c	2007-03-26 13:54:33.000000000 +0200
@@ -6,7 +6,6 @@
 #include <linux/version.h>
 #include <linux/kernel.h>
 #include <linux/skbuff.h>
-#include <linux/pci.h>
 #include <linux/errno.h>
 #include <linux/types.h>
 #include <linux/string.h>
--- linux-2.6.21-rc5.orig/drivers/char/hw_random/via-rng.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/char/hw_random/via-rng.c	2007-03-26 13:54:33.000000000 +0200
@@ -26,7 +26,6 @@
 
 #include <linux/module.h>
 #include <linux/kernel.h>
-#include <linux/pci.h>
 #include <linux/hw_random.h>
 #include <asm/io.h>
 #include <asm/msr.h>
--- linux-2.6.21-rc5.orig/drivers/char/pcmcia/synclink_cs.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/char/pcmcia/synclink_cs.c	2007-03-26 13:54:33.000000000 +0200
@@ -42,7 +42,6 @@
 #include <linux/timer.h>
 #include <linux/time.h>
 #include <linux/interrupt.h>
-#include <linux/pci.h>
 #include <linux/tty.h>
 #include <linux/tty_flip.h>
 #include <linux/serial.h>
--- linux-2.6.21-rc5.orig/drivers/char/tpm/tpm.h	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/char/tpm/tpm.h	2007-03-26 13:54:33.000000000 +0200
@@ -19,7 +19,6 @@
  * 
  */
 #include <linux/module.h>
-#include <linux/pci.h>
 #include <linux/delay.h>
 #include <linux/fs.h>
 #include <linux/sched.h>
--- linux-2.6.21-rc5.orig/drivers/char/watchdog/sc1200wdt.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/char/watchdog/sc1200wdt.c	2007-03-26 13:54:33.000000000 +0200
@@ -38,7 +38,6 @@
 #include <linux/init.h>
 #include <linux/pnp.h>
 #include <linux/fs.h>
-#include <linux/pci.h>
 
 #include <asm/semaphore.h>
 #include <asm/io.h>
--- linux-2.6.21-rc5.orig/drivers/char/watchdog/scx200_wdt.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/char/watchdog/scx200_wdt.c	2007-03-26 13:54:33.000000000 +0200
@@ -25,7 +25,7 @@
 #include <linux/notifier.h>
 #include <linux/reboot.h>
 #include <linux/fs.h>
-#include <linux/pci.h>
+#include <linux/ioport.h>
 #include <linux/scx200.h>
 
 #include <asm/uaccess.h>
--- linux-2.6.21-rc5.orig/drivers/i2c/busses/i2c-at91.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/i2c/busses/i2c-at91.c	2007-03-26 13:54:33.000000000 +0200
@@ -17,7 +17,6 @@
 #include <linux/version.h>
 #include <linux/kernel.h>
 #include <linux/slab.h>
-#include <linux/pci.h>
 #include <linux/types.h>
 #include <linux/delay.h>
 #include <linux/i2c.h>
--- linux-2.6.21-rc5.orig/drivers/i2c/busses/i2c-mpc.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/i2c/busses/i2c-mpc.c	2007-03-26 13:54:33.000000000 +0200
@@ -17,7 +17,6 @@
 #include <linux/module.h>
 #include <linux/sched.h>
 #include <linux/init.h>
-#include <linux/pci.h>
 #include <linux/platform_device.h>
 
 #include <asm/io.h>
--- linux-2.6.21-rc5.orig/drivers/i2c/busses/i2c-pca-isa.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/i2c/busses/i2c-pca-isa.c	2007-03-26 21:30:22.000000000 +0200
@@ -25,7 +25,6 @@
 #include <linux/slab.h>
 #include <linux/init.h>
 #include <linux/interrupt.h>
-#include <linux/pci.h>
 #include <linux/wait.h>
 
 #include <linux/i2c.h>
--- linux-2.6.21-rc5.orig/drivers/ieee1394/hosts.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/ieee1394/hosts.c	2007-03-26 13:54:33.000000000 +0200
@@ -15,7 +15,6 @@
 #include <linux/list.h>
 #include <linux/init.h>
 #include <linux/slab.h>
-#include <linux/pci.h>
 #include <linux/timer.h>
 #include <linux/jiffies.h>
 #include <linux/mutex.h>
--- linux-2.6.21-rc5.orig/drivers/infiniband/core/cm.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/infiniband/core/cm.c	2007-03-26 13:54:33.000000000 +0200
@@ -40,7 +40,6 @@
 #include <linux/err.h>
 #include <linux/idr.h>
 #include <linux/interrupt.h>
-#include <linux/pci.h>
 #include <linux/random.h>
 #include <linux/rbtree.h>
 #include <linux/spinlock.h>
--- linux-2.6.21-rc5.orig/drivers/infiniband/core/iwcm.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/infiniband/core/iwcm.c	2007-03-26 13:54:33.000000000 +0200
@@ -39,7 +39,6 @@
 #include <linux/err.h>
 #include <linux/idr.h>
 #include <linux/interrupt.h>
-#include <linux/pci.h>
 #include <linux/rbtree.h>
 #include <linux/spinlock.h>
 #include <linux/workqueue.h>
--- linux-2.6.21-rc5.orig/drivers/infiniband/core/mad_priv.h	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/infiniband/core/mad_priv.h	2007-03-26 13:54:33.000000000 +0200
@@ -39,7 +39,6 @@
 
 #include <linux/completion.h>
 #include <linux/err.h>
-#include <linux/pci.h>
 #include <linux/workqueue.h>
 #include <rdma/ib_mad.h>
 #include <rdma/ib_smi.h>
--- linux-2.6.21-rc5.orig/drivers/infiniband/core/multicast.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/infiniband/core/multicast.c	2007-03-26 13:54:33.000000000 +0200
@@ -34,7 +34,6 @@
 #include <linux/dma-mapping.h>
 #include <linux/err.h>
 #include <linux/interrupt.h>
-#include <linux/pci.h>
 #include <linux/bitops.h>
 #include <linux/random.h>
 
--- linux-2.6.21-rc5.orig/drivers/infiniband/core/sa_query.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/infiniband/core/sa_query.c	2007-03-26 13:54:33.000000000 +0200
@@ -40,7 +40,6 @@
 #include <linux/random.h>
 #include <linux/spinlock.h>
 #include <linux/slab.h>
-#include <linux/pci.h>
 #include <linux/dma-mapping.h>
 #include <linux/kref.h>
 #include <linux/idr.h>
--- linux-2.6.21-rc5.orig/drivers/infiniband/core/user_mad.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/infiniband/core/user_mad.c	2007-03-26 13:54:33.000000000 +0200
@@ -40,7 +40,6 @@
 #include <linux/err.h>
 #include <linux/fs.h>
 #include <linux/cdev.h>
-#include <linux/pci.h>
 #include <linux/dma-mapping.h>
 #include <linux/poll.h>
 #include <linux/rwsem.h>
--- linux-2.6.21-rc5.orig/drivers/infiniband/hw/ipath/ipath_fs.c	2007-03-26 13:54:18.000000000 +0200
+++ linux-2.6.21-rc5/drivers/infiniband/hw/ipath/ipath_fs.c	2007-03-26 13:54:33.000000000 +0200
@@ -38,7 +38,6 @@
 #include <linux/pagemap.h>
 #include <linux/init.h>
 #include <linux/namei.h>
-#include <linux/pci.h>
 
 #include "ipath_kernel.h"
 
--- linux-2.6.21-rc5.orig/drivers/infiniband/hw/ipath/ipath_layer.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/infiniband/hw/ipath/ipath_layer.c	2007-03-26 13:54:33.000000000 +0200
@@ -37,7 +37,6 @@
  */
 
 #include <linux/io.h>
-#include <linux/pci.h>
 #include <asm/byteorder.h>
 
 #include "ipath_kernel.h"
--- linux-2.6.21-rc5.orig/drivers/infiniband/hw/ipath/ipath_stats.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/infiniband/hw/ipath/ipath_stats.c	2007-03-26 13:54:33.000000000 +0200
@@ -31,8 +31,6 @@
  * SOFTWARE.
  */
 
-#include <linux/pci.h>
-
 #include "ipath_kernel.h"
 
 struct infinipath_stats ipath_stats;
--- linux-2.6.21-rc5.orig/drivers/infiniband/hw/ipath/ipath_sysfs.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/infiniband/hw/ipath/ipath_sysfs.c	2007-03-26 13:54:33.000000000 +0200
@@ -32,7 +32,6 @@
  */
 
 #include <linux/ctype.h>
-#include <linux/pci.h>
 
 #include "ipath_kernel.h"
 #include "ipath_common.h"
--- linux-2.6.21-rc5.orig/drivers/infiniband/hw/mthca/mthca_memfree.h	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/infiniband/hw/mthca/mthca_memfree.h	2007-03-26 13:54:33.000000000 +0200
@@ -38,7 +38,6 @@
 #define MTHCA_MEMFREE_H
 
 #include <linux/list.h>
-#include <linux/pci.h>
 #include <linux/mutex.h>
 
 #define MTHCA_ICM_CHUNK_LEN \
--- linux-2.6.21-rc5.orig/drivers/infiniband/ulp/ipoib/ipoib.h	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/infiniband/ulp/ipoib/ipoib.h	2007-03-26 13:54:33.000000000 +0200
@@ -41,7 +41,6 @@
 #include <linux/skbuff.h>
 #include <linux/netdevice.h>
 #include <linux/workqueue.h>
-#include <linux/pci.h>
 #include <linux/kref.h>
 #include <linux/if_infiniband.h>
 #include <linux/mutex.h>
--- linux-2.6.21-rc5.orig/drivers/isdn/hisax/netjet.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/isdn/hisax/netjet.c	2007-03-26 13:54:33.000000000 +0200
@@ -19,7 +19,6 @@
 #include "isac.h"
 #include "hscx.h"
 #include "isdnl1.h"
-#include <linux/pci.h>
 #include <linux/interrupt.h>
 #include <linux/ppp_defs.h>
 #include <asm/io.h>
--- linux-2.6.21-rc5.orig/drivers/isdn/hysdn/hysdn_proclog.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/isdn/hysdn/hysdn_proclog.c	2007-03-26 13:54:33.000000000 +0200
@@ -13,7 +13,6 @@
 #include <linux/module.h>
 #include <linux/poll.h>
 #include <linux/proc_fs.h>
-#include <linux/pci.h>
 #include <linux/smp_lock.h>
 
 #include "hysdn_defs.h"
--- linux-2.6.21-rc5.orig/drivers/media/dvb/cinergyT2/cinergyT2.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/media/dvb/cinergyT2/cinergyT2.c	2007-03-26 13:54:33.000000000 +0200
@@ -26,11 +26,11 @@
 #include <linux/module.h>
 #include <linux/slab.h>
 #include <linux/usb.h>
-#include <linux/pci.h>
 #include <linux/input.h>
 #include <linux/dvb/frontend.h>
 #include <linux/mutex.h>
 #include <linux/mm.h>
+#include <asm/io.h>
 
 #include "dmxdev.h"
 #include "dvb_demux.h"
--- linux-2.6.21-rc5.orig/drivers/media/video/adv7170.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/media/video/adv7170.c	2007-03-26 13:54:33.000000000 +0200
@@ -37,7 +37,6 @@
 #include <linux/major.h>
 #include <linux/slab.h>
 #include <linux/mm.h>
-#include <linux/pci.h>
 #include <linux/signal.h>
 #include <asm/io.h>
 #include <asm/pgtable.h>
--- linux-2.6.21-rc5.orig/drivers/media/video/adv7175.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/media/video/adv7175.c	2007-03-26 13:54:33.000000000 +0200
@@ -33,7 +33,6 @@
 #include <linux/major.h>
 #include <linux/slab.h>
 #include <linux/mm.h>
-#include <linux/pci.h>
 #include <linux/signal.h>
 #include <asm/io.h>
 #include <asm/pgtable.h>
--- linux-2.6.21-rc5.orig/drivers/media/video/bt819.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/media/video/bt819.c	2007-03-26 13:54:33.000000000 +0200
@@ -37,7 +37,6 @@
 #include <linux/major.h>
 #include <linux/slab.h>
 #include <linux/mm.h>
-#include <linux/pci.h>
 #include <linux/signal.h>
 #include <asm/io.h>
 #include <asm/pgtable.h>
--- linux-2.6.21-rc5.orig/drivers/media/video/bt856.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/media/video/bt856.c	2007-03-26 13:54:33.000000000 +0200
@@ -37,7 +37,6 @@
 #include <linux/major.h>
 #include <linux/slab.h>
 #include <linux/mm.h>
-#include <linux/pci.h>
 #include <linux/signal.h>
 #include <asm/io.h>
 #include <asm/pgtable.h>
--- linux-2.6.21-rc5.orig/drivers/media/video/bt866.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/media/video/bt866.c	2007-03-26 13:54:33.000000000 +0200
@@ -37,7 +37,6 @@
 #include <linux/major.h>
 #include <linux/slab.h>
 #include <linux/mm.h>
-#include <linux/pci.h>
 #include <linux/signal.h>
 #include <asm/io.h>
 #include <asm/pgtable.h>
--- linux-2.6.21-rc5.orig/drivers/media/video/cx88/cx88-tvaudio.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/media/video/cx88/cx88-tvaudio.c	2007-03-26 13:54:33.000000000 +0200
@@ -43,7 +43,6 @@
 #include <linux/slab.h>
 #include <linux/mm.h>
 #include <linux/poll.h>
-#include <linux/pci.h>
 #include <linux/signal.h>
 #include <linux/ioport.h>
 #include <linux/types.h>
--- linux-2.6.21-rc5.orig/drivers/media/video/em28xx/em28xx-cards.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/media/video/em28xx/em28xx-cards.c	2007-03-26 13:54:33.000000000 +0200
@@ -23,7 +23,6 @@
 
 #include <linux/init.h>
 #include <linux/module.h>
-#include <linux/pci.h>
 #include <linux/delay.h>
 #include <linux/i2c.h>
 #include <linux/usb.h>
--- linux-2.6.21-rc5.orig/drivers/media/video/saa7111.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/media/video/saa7111.c	2007-03-26 13:54:33.000000000 +0200
@@ -36,7 +36,6 @@
 #include <linux/major.h>
 #include <linux/slab.h>
 #include <linux/mm.h>
-#include <linux/pci.h>
 #include <linux/signal.h>
 #include <asm/io.h>
 #include <asm/pgtable.h>
--- linux-2.6.21-rc5.orig/drivers/media/video/saa7114.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/media/video/saa7114.c	2007-03-26 13:54:33.000000000 +0200
@@ -39,7 +39,6 @@
 #include <linux/slab.h>
 
 #include <linux/mm.h>
-#include <linux/pci.h>
 #include <linux/signal.h>
 #include <asm/io.h>
 #include <asm/pgtable.h>
--- linux-2.6.21-rc5.orig/drivers/media/video/saa711x.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/media/video/saa711x.c	2007-03-26 13:54:33.000000000 +0200
@@ -30,7 +30,6 @@
 #include <linux/major.h>
 #include <linux/slab.h>
 #include <linux/mm.h>
-#include <linux/pci.h>
 #include <linux/signal.h>
 #include <asm/io.h>
 #include <asm/pgtable.h>
--- linux-2.6.21-rc5.orig/drivers/media/video/saa7185.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/media/video/saa7185.c	2007-03-26 13:54:33.000000000 +0200
@@ -33,7 +33,6 @@
 #include <linux/major.h>
 #include <linux/slab.h>
 #include <linux/mm.h>
-#include <linux/pci.h>
 #include <linux/signal.h>
 #include <asm/io.h>
 #include <asm/pgtable.h>
--- linux-2.6.21-rc5.orig/drivers/misc/hdpuftrs/hdpu_cpustate.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/misc/hdpuftrs/hdpu_cpustate.c	2007-03-26 13:54:33.000000000 +0200
@@ -18,7 +18,6 @@
 #include <linux/kernel.h>
 #include <linux/spinlock.h>
 #include <linux/miscdevice.h>
-#include <linux/pci.h>
 #include <linux/proc_fs.h>
 #include <linux/platform_device.h>
 #include <asm/uaccess.h>
--- linux-2.6.21-rc5.orig/drivers/misc/hdpuftrs/hdpu_nexus.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/misc/hdpuftrs/hdpu_nexus.c	2007-03-26 13:54:33.000000000 +0200
@@ -18,7 +18,6 @@
 #include <linux/kernel.h>
 #include <linux/proc_fs.h>
 #include <linux/hdpu_features.h>
-#include <linux/pci.h>
 
 #include <linux/platform_device.h>
 
--- linux-2.6.21-rc5.orig/drivers/mtd/devices/doc2000.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/mtd/devices/doc2000.c	2007-03-26 13:54:33.000000000 +0200
@@ -13,7 +13,6 @@
 #include <asm/io.h>
 #include <asm/uaccess.h>
 #include <linux/miscdevice.h>
-#include <linux/pci.h>
 #include <linux/delay.h>
 #include <linux/slab.h>
 #include <linux/sched.h>
--- linux-2.6.21-rc5.orig/drivers/mtd/devices/doc2001.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/mtd/devices/doc2001.c	2007-03-26 13:54:33.000000000 +0200
@@ -13,7 +13,6 @@
 #include <asm/io.h>
 #include <asm/uaccess.h>
 #include <linux/miscdevice.h>
-#include <linux/pci.h>
 #include <linux/delay.h>
 #include <linux/slab.h>
 #include <linux/init.h>
--- linux-2.6.21-rc5.orig/drivers/mtd/devices/doc2001plus.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/mtd/devices/doc2001plus.c	2007-03-26 13:54:33.000000000 +0200
@@ -17,7 +17,6 @@
 #include <asm/io.h>
 #include <asm/uaccess.h>
 #include <linux/miscdevice.h>
-#include <linux/pci.h>
 #include <linux/delay.h>
 #include <linux/slab.h>
 #include <linux/init.h>
--- linux-2.6.21-rc5.orig/drivers/mtd/devices/docecc.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/mtd/devices/docecc.c	2007-03-26 13:54:33.000000000 +0200
@@ -29,7 +29,6 @@
 #include <asm/io.h>
 #include <asm/uaccess.h>
 #include <linux/miscdevice.h>
-#include <linux/pci.h>
 #include <linux/delay.h>
 #include <linux/slab.h>
 #include <linux/init.h>
--- linux-2.6.21-rc5.orig/drivers/mtd/inftlmount.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/mtd/inftlmount.c	2007-03-26 13:54:33.000000000 +0200
@@ -31,7 +31,6 @@
 #include <asm/io.h>
 #include <asm/uaccess.h>
 #include <linux/miscdevice.h>
-#include <linux/pci.h>
 #include <linux/delay.h>
 #include <linux/slab.h>
 #include <linux/init.h>
--- linux-2.6.21-rc5.orig/drivers/mtd/nand/cs553x_nand.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/mtd/nand/cs553x_nand.c	2007-03-26 13:54:33.000000000 +0200
@@ -20,7 +20,6 @@
 #include <linux/init.h>
 #include <linux/module.h>
 #include <linux/delay.h>
-#include <linux/pci.h>
 #include <linux/mtd/mtd.h>
 #include <linux/mtd/nand.h>
 #include <linux/mtd/nand_ecc.h>
--- linux-2.6.21-rc5.orig/drivers/mtd/nftlcore.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/mtd/nftlcore.c	2007-03-26 13:54:33.000000000 +0200
@@ -17,7 +17,6 @@
 #include <asm/io.h>
 #include <asm/uaccess.h>
 #include <linux/miscdevice.h>
-#include <linux/pci.h>
 #include <linux/delay.h>
 #include <linux/slab.h>
 #include <linux/init.h>
--- linux-2.6.21-rc5.orig/drivers/net/atl1/atl1_param.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/net/atl1/atl1_param.c	2007-03-26 13:54:33.000000000 +0200
@@ -22,7 +22,6 @@
  */
 
 #include <linux/types.h>
-#include <linux/pci.h>
 #include <linux/moduleparam.h>
 #include "atl1.h"
 
--- linux-2.6.21-rc5.orig/drivers/net/au1000_eth.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/net/au1000_eth.c	2007-03-26 13:54:33.000000000 +0200
@@ -45,7 +45,6 @@
 #include <linux/bitops.h>
 #include <linux/slab.h>
 #include <linux/interrupt.h>
-#include <linux/pci.h>
 #include <linux/init.h>
 #include <linux/netdevice.h>
 #include <linux/etherdevice.h>
--- linux-2.6.21-rc5.orig/drivers/net/fec_8xx/fec_main.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/net/fec_8xx/fec_main.c	2007-03-26 13:54:33.000000000 +0200
@@ -19,7 +19,6 @@
 #include <linux/ioport.h>
 #include <linux/slab.h>
 #include <linux/interrupt.h>
-#include <linux/pci.h>
 #include <linux/init.h>
 #include <linux/delay.h>
 #include <linux/netdevice.h>
--- linux-2.6.21-rc5.orig/drivers/net/fec_8xx/fec_mii.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/net/fec_8xx/fec_mii.c	2007-03-26 13:54:33.000000000 +0200
@@ -19,7 +19,6 @@
 #include <linux/ioport.h>
 #include <linux/slab.h>
 #include <linux/interrupt.h>
-#include <linux/pci.h>
 #include <linux/init.h>
 #include <linux/delay.h>
 #include <linux/netdevice.h>
--- linux-2.6.21-rc5.orig/drivers/net/fs_enet/fs_enet-main.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/net/fs_enet/fs_enet-main.c	2007-03-26 13:54:33.000000000 +0200
@@ -24,7 +24,6 @@
 #include <linux/ioport.h>
 #include <linux/slab.h>
 #include <linux/interrupt.h>
-#include <linux/pci.h>
 #include <linux/init.h>
 #include <linux/delay.h>
 #include <linux/netdevice.h>
--- linux-2.6.21-rc5.orig/drivers/net/fs_enet/mac-fcc.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/net/fs_enet/mac-fcc.c	2007-03-26 13:54:33.000000000 +0200
@@ -21,7 +21,6 @@
 #include <linux/ioport.h>
 #include <linux/slab.h>
 #include <linux/interrupt.h>
-#include <linux/pci.h>
 #include <linux/init.h>
 #include <linux/delay.h>
 #include <linux/netdevice.h>
--- linux-2.6.21-rc5.orig/drivers/net/fs_enet/mac-fec.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/net/fs_enet/mac-fec.c	2007-03-26 13:54:33.000000000 +0200
@@ -21,7 +21,6 @@
 #include <linux/ioport.h>
 #include <linux/slab.h>
 #include <linux/interrupt.h>
-#include <linux/pci.h>
 #include <linux/init.h>
 #include <linux/delay.h>
 #include <linux/netdevice.h>
--- linux-2.6.21-rc5.orig/drivers/net/fs_enet/mac-scc.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/net/fs_enet/mac-scc.c	2007-03-26 13:54:33.000000000 +0200
@@ -21,7 +21,6 @@
 #include <linux/ioport.h>
 #include <linux/slab.h>
 #include <linux/interrupt.h>
-#include <linux/pci.h>
 #include <linux/init.h>
 #include <linux/delay.h>
 #include <linux/netdevice.h>
--- linux-2.6.21-rc5.orig/drivers/net/fs_enet/mii-bitbang.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/net/fs_enet/mii-bitbang.c	2007-03-26 13:54:33.000000000 +0200
@@ -22,7 +22,6 @@
 #include <linux/ioport.h>
 #include <linux/slab.h>
 #include <linux/interrupt.h>
-#include <linux/pci.h>
 #include <linux/init.h>
 #include <linux/delay.h>
 #include <linux/netdevice.h>
--- linux-2.6.21-rc5.orig/drivers/net/fs_enet/mii-fec.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/net/fs_enet/mii-fec.c	2007-03-26 13:54:33.000000000 +0200
@@ -21,7 +21,6 @@
 #include <linux/ioport.h>
 #include <linux/slab.h>
 #include <linux/interrupt.h>
-#include <linux/pci.h>
 #include <linux/init.h>
 #include <linux/delay.h>
 #include <linux/netdevice.h>
--- linux-2.6.21-rc5.orig/drivers/net/ibm_emac/ibm_emac_core.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/net/ibm_emac/ibm_emac_core.c	2007-03-26 13:54:33.000000000 +0200
@@ -27,7 +27,6 @@
 #include <linux/delay.h>
 #include <linux/init.h>
 #include <linux/types.h>
-#include <linux/pci.h>
 #include <linux/netdevice.h>
 #include <linux/etherdevice.h>
 #include <linux/skbuff.h>
--- linux-2.6.21-rc5.orig/drivers/net/ixgb/ixgb_osdep.h	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/net/ixgb/ixgb_osdep.h	2007-03-26 13:54:33.000000000 +0200
@@ -34,7 +34,6 @@
 #define _IXGB_OSDEP_H_
 
 #include <linux/types.h>
-#include <linux/pci.h>
 #include <linux/delay.h>
 #include <asm/io.h>
 #include <linux/interrupt.h>
--- linux-2.6.21-rc5.orig/drivers/net/lasi_82596.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/net/lasi_82596.c	2007-03-26 13:54:33.000000000 +0200
@@ -81,7 +81,6 @@
 #include <linux/etherdevice.h>
 #include <linux/skbuff.h>
 #include <linux/init.h>
-#include <linux/pci.h>
 #include <linux/types.h>
 #include <linux/bitops.h>
 
--- linux-2.6.21-rc5.orig/drivers/net/tokenring/madgemc.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/net/tokenring/madgemc.c	2007-03-26 13:54:33.000000000 +0200
@@ -23,7 +23,6 @@ static const char version[] = "madgemc.c
 #include <linux/mca.h>
 #include <linux/kernel.h>
 #include <linux/errno.h>
-#include <linux/pci.h>
 #include <linux/init.h>
 #include <linux/netdevice.h>
 #include <linux/trdevice.h>
--- linux-2.6.21-rc5.orig/drivers/net/tokenring/smctr.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/net/tokenring/smctr.c	2007-03-26 13:54:33.000000000 +0200
@@ -41,7 +41,6 @@
 #include <linux/time.h>
 #include <linux/errno.h>
 #include <linux/init.h>
-#include <linux/pci.h>
 #include <linux/mca-legacy.h>
 #include <linux/delay.h>
 #include <linux/netdevice.h>
--- linux-2.6.21-rc5.orig/drivers/net/tulip/21142.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/net/tulip/21142.c	2007-03-26 13:54:33.000000000 +0200
@@ -14,7 +14,6 @@
 
 */
 
-#include <linux/pci.h>
 #include <linux/delay.h>
 #include "tulip.h"
 
--- linux-2.6.21-rc5.orig/drivers/net/tulip/pnic.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/net/tulip/pnic.c	2007-03-26 13:54:33.000000000 +0200
@@ -15,7 +15,6 @@
 */
 
 #include <linux/kernel.h>
-#include <linux/pci.h>
 #include <linux/jiffies.h>
 #include "tulip.h"
 
--- linux-2.6.21-rc5.orig/drivers/net/tulip/pnic2.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/net/tulip/pnic2.c	2007-03-26 13:54:33.000000000 +0200
@@ -76,7 +76,6 @@
 
 
 
-#include <linux/pci.h>
 #include "tulip.h"
 #include <linux/delay.h>
 
--- linux-2.6.21-rc5.orig/drivers/net/tulip/timer.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/net/tulip/timer.c	2007-03-26 13:54:33.000000000 +0200
@@ -14,7 +14,6 @@
 
 */
 
-#include <linux/pci.h>
 #include "tulip.h"
 
 
--- linux-2.6.21-rc5.orig/drivers/net/tulip/tulip.h	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/net/tulip/tulip.h	2007-03-26 13:54:33.000000000 +0200
@@ -22,6 +22,7 @@
 #include <linux/netdevice.h>
 #include <linux/timer.h>
 #include <linux/delay.h>
+#include <linux/pci.h>
 #include <asm/io.h>
 #include <asm/irq.h>
 
--- linux-2.6.21-rc5.orig/drivers/net/wan/lmc/lmc_media.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/net/wan/lmc/lmc_media.c	2007-03-26 13:54:33.000000000 +0200
@@ -8,7 +8,6 @@
 #include <linux/ioport.h>
 #include <linux/slab.h>
 #include <linux/interrupt.h>
-#include <linux/pci.h>
 #include <linux/in.h>
 #include <linux/if_arp.h>
 #include <linux/netdevice.h>
--- linux-2.6.21-rc5.orig/drivers/net/wan/lmc/lmc_proto.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/net/wan/lmc/lmc_proto.c	2007-03-26 13:54:33.000000000 +0200
@@ -27,7 +27,6 @@
 #include <linux/ioport.h>
 #include <linux/slab.h>
 #include <linux/interrupt.h>
-#include <linux/pci.h>
 #include <linux/in.h>
 #include <linux/if_arp.h>
 #include <linux/netdevice.h>
--- linux-2.6.21-rc5.orig/drivers/net/wan/pc300_tty.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/net/wan/pc300_tty.c	2007-03-26 13:54:33.000000000 +0200
@@ -38,7 +38,6 @@
 
 #include <linux/module.h>
 #include <linux/kernel.h>
-#include <linux/pci.h>
 #include <linux/errno.h>
 #include <linux/string.h>
 #include <linux/init.h>
--- linux-2.6.21-rc5.orig/drivers/parisc/hppb.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/parisc/hppb.c	2007-03-26 13:54:33.000000000 +0200
@@ -22,8 +22,6 @@
 #include <asm/hardware.h>
 #include <asm/parisc-device.h>
 
-#include <linux/pci.h>
-
 struct hppb_card {
 	unsigned long hpa;
 	struct resource mmio_region;
--- linux-2.6.21-rc5.orig/drivers/pcmcia/cs.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/pcmcia/cs.c	2007-03-26 13:54:33.000000000 +0200
@@ -26,7 +26,6 @@
 #include <linux/ioport.h>
 #include <linux/delay.h>
 #include <linux/pm.h>
-#include <linux/pci.h>
 #include <linux/device.h>
 #include <linux/kthread.h>
 #include <linux/freezer.h>
--- linux-2.6.21-rc5.orig/drivers/pcmcia/socket_sysfs.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/pcmcia/socket_sysfs.c	2007-03-26 13:54:33.000000000 +0200
@@ -22,7 +22,6 @@
 #include <linux/ioport.h>
 #include <linux/delay.h>
 #include <linux/pm.h>
-#include <linux/pci.h>
 #include <linux/device.h>
 #include <linux/mutex.h>
 #include <asm/system.h>
--- linux-2.6.21-rc5.orig/drivers/sbus/sbus.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/sbus/sbus.c	2007-03-26 13:54:33.000000000 +0200
@@ -6,7 +6,6 @@
 #include <linux/kernel.h>
 #include <linux/slab.h>
 #include <linux/init.h>
-#include <linux/pci.h>
 #include <linux/device.h>
 
 #include <asm/system.h>
--- linux-2.6.21-rc5.orig/drivers/scsi/aacraid/dpcsup.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/scsi/aacraid/dpcsup.c	2007-03-26 13:54:33.000000000 +0200
@@ -32,7 +32,6 @@
 #include <linux/kernel.h>
 #include <linux/init.h>
 #include <linux/types.h>
-#include <linux/pci.h>
 #include <linux/spinlock.h>
 #include <linux/slab.h>
 #include <linux/completion.h>
--- linux-2.6.21-rc5.orig/drivers/scsi/aacraid/sa.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/scsi/aacraid/sa.c	2007-03-26 13:54:33.000000000 +0200
@@ -31,7 +31,6 @@
 #include <linux/kernel.h>
 #include <linux/init.h>
 #include <linux/types.h>
-#include <linux/pci.h>
 #include <linux/spinlock.h>
 #include <linux/slab.h>
 #include <linux/blkdev.h>
--- linux-2.6.21-rc5.orig/drivers/scsi/aha1542.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/scsi/aha1542.c	2007-03-26 13:54:33.000000000 +0200
@@ -35,7 +35,6 @@
 #include <linux/proc_fs.h>
 #include <linux/init.h>
 #include <linux/spinlock.h>
-#include <linux/pci.h>
 #include <linux/isapnp.h>
 #include <linux/blkdev.h>
 #include <linux/mca.h>
--- linux-2.6.21-rc5.orig/drivers/scsi/aic94xx/aic94xx_scb.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/scsi/aic94xx/aic94xx_scb.c	2007-03-26 13:54:33.000000000 +0200
@@ -24,7 +24,6 @@
  *
  */
 
-#include <linux/pci.h>
 #include <scsi/scsi_host.h>
 
 #include "aic94xx.h"
--- linux-2.6.21-rc5.orig/drivers/scsi/arcmsr/arcmsr_attr.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/scsi/arcmsr/arcmsr_attr.c	2007-03-26 13:54:33.000000000 +0200
@@ -49,7 +49,6 @@
 #include <linux/init.h>
 #include <linux/errno.h>
 #include <linux/delay.h>
-#include <linux/pci.h>
 
 #include <scsi/scsi_cmnd.h>
 #include <scsi/scsi_device.h>
--- linux-2.6.21-rc5.orig/drivers/scsi/libsas/sas_expander.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/scsi/libsas/sas_expander.c	2007-03-26 13:54:33.000000000 +0200
@@ -22,7 +22,6 @@
  *
  */
 
-#include <linux/pci.h>
 #include <linux/scatterlist.h>
 
 #include "sas_internal.h"
--- linux-2.6.21-rc5.orig/drivers/scsi/libsrp.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/scsi/libsrp.c	2007-03-26 13:54:33.000000000 +0200
@@ -22,7 +22,6 @@
 #include <linux/kfifo.h>
 #include <linux/scatterlist.h>
 #include <linux/dma-mapping.h>
-#include <linux/pci.h>
 #include <scsi/scsi.h>
 #include <scsi/scsi_cmnd.h>
 #include <scsi/scsi_tcq.h>
--- linux-2.6.21-rc5.orig/drivers/usb/net/kaweth.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/usb/net/kaweth.c	2007-03-26 13:54:33.000000000 +0200
@@ -55,7 +55,6 @@
 #include <linux/usb.h>
 #include <linux/types.h>
 #include <linux/ethtool.h>
-#include <linux/pci.h>
 #include <linux/dma-mapping.h>
 #include <linux/wait.h>
 #include <asm/uaccess.h>
--- linux-2.6.21-rc5.orig/drivers/video/aty/radeon_i2c.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/video/aty/radeon_i2c.c	2007-03-26 21:30:25.000000000 +0200
@@ -1,7 +1,6 @@
 #include <linux/module.h>
 #include <linux/kernel.h>
 #include <linux/delay.h>
-#include <linux/pci.h>
 #include <linux/fb.h>
 
 
--- linux-2.6.21-rc5.orig/drivers/video/g364fb.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/video/g364fb.c	2007-03-26 13:54:33.000000000 +0200
@@ -26,7 +26,6 @@
 #include <linux/interrupt.h>
 #include <linux/fb.h>
 #include <linux/init.h>
-#include <linux/pci.h>
 #include <asm/io.h>
 #include <asm/jazz.h>
 
--- linux-2.6.21-rc5.orig/drivers/video/platinumfb.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/video/platinumfb.c	2007-03-26 13:54:33.000000000 +0200
@@ -28,7 +28,6 @@
 #include <linux/interrupt.h>
 #include <linux/fb.h>
 #include <linux/init.h>
-#include <linux/pci.h>
 #include <linux/nvram.h>
 #include <asm/io.h>
 #include <asm/prom.h>
--- linux-2.6.21-rc5.orig/drivers/video/stifb.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/video/stifb.c	2007-03-26 13:54:33.000000000 +0200
@@ -64,7 +64,6 @@
 #include <linux/fb.h>
 #include <linux/init.h>
 #include <linux/ioport.h>
-#include <linux/pci.h>
 
 #include <asm/grfioctl.h>	/* for HP-UX compatibility */
 #include <asm/uaccess.h>
--- linux-2.6.21-rc5.orig/drivers/video/valkyriefb.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/drivers/video/valkyriefb.c	2007-03-26 13:54:33.000000000 +0200
@@ -51,7 +51,6 @@
 #include <linux/fb.h>
 #include <linux/selection.h>
 #include <linux/init.h>
-#include <linux/pci.h>
 #include <linux/nvram.h>
 #include <linux/adb.h>
 #include <linux/cuda.h>
--- linux-2.6.21-rc5.orig/include/asm-arm/arch-ixp4xx/dma.h	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/include/asm-arm/arch-ixp4xx/dma.h	2007-03-26 13:54:33.000000000 +0200
@@ -12,7 +12,6 @@
 #define __ASM_ARCH_DMA_H
 
 #include <linux/device.h>
-#include <linux/pci.h>
 #include <asm/page.h>
 #include <asm/sizes.h>
 #include <asm/hardware.h>
--- linux-2.6.21-rc5.orig/include/rdma/ib_mad.h	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/include/rdma/ib_mad.h	2007-03-26 13:54:33.000000000 +0200
@@ -39,8 +39,6 @@
 #if !defined( IB_MAD_H )
 #define IB_MAD_H
 
-#include <linux/pci.h>
-
 #include <rdma/ib_verbs.h>
 
 /* Management base version */
--- linux-2.6.21-rc5.orig/sound/core/init.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/sound/core/init.c	2007-03-26 13:54:33.000000000 +0200
@@ -26,7 +26,6 @@
 #include <linux/slab.h>
 #include <linux/time.h>
 #include <linux/ctype.h>
-#include <linux/pci.h>
 #include <linux/pm.h>
 
 #include <sound/core.h>
--- linux-2.6.21-rc5.orig/sound/oss/au1550_ac97.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/sound/oss/au1550_ac97.c	2007-03-26 13:54:33.000000000 +0200
@@ -47,7 +47,6 @@
 #include <linux/interrupt.h>
 #include <linux/kernel.h>
 #include <linux/poll.h>
-#include <linux/pci.h>
 #include <linux/bitops.h>
 #include <linux/spinlock.h>
 #include <linux/smp_lock.h>
--- linux-2.6.21-rc5.orig/sound/oss/soundcard.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/sound/oss/soundcard.c	2007-03-26 13:54:33.000000000 +0200
@@ -44,6 +44,7 @@
 #include <linux/smp_lock.h>
 #include <linux/module.h>
 #include <linux/mm.h>
+#include <linux/device.h>
 
 /*
  * This ought to be moved into include/asm/dma.h
--- linux-2.6.21-rc5.orig/sound/pci/ca0106/ca0106_mixer.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/sound/pci/ca0106/ca0106_mixer.c	2007-03-26 13:54:33.000000000 +0200
@@ -62,7 +62,6 @@
 #include <linux/delay.h>
 #include <linux/init.h>
 #include <linux/interrupt.h>
-#include <linux/pci.h>
 #include <linux/slab.h>
 #include <linux/moduleparam.h>
 #include <sound/core.h>
@@ -71,6 +70,7 @@
 #include <sound/ac97_codec.h>
 #include <sound/info.h>
 #include <sound/tlv.h>
+#include <asm/io.h>
 
 #include "ca0106.h"
 
--- linux-2.6.21-rc5.orig/sound/pci/ca0106/ca0106_proc.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/sound/pci/ca0106/ca0106_proc.c	2007-03-26 13:54:33.000000000 +0200
@@ -64,7 +64,6 @@
 #include <linux/delay.h>
 #include <linux/init.h>
 #include <linux/interrupt.h>
-#include <linux/pci.h>
 #include <linux/slab.h>
 #include <linux/moduleparam.h>
 #include <sound/core.h>
@@ -73,6 +72,7 @@
 #include <sound/ac97_codec.h>
 #include <sound/info.h>
 #include <sound/asoundef.h>
+#include <asm/io.h>
 
 #include "ca0106.h"
 
--- linux-2.6.21-rc5.orig/sound/pci/cs46xx/dsp_spos.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/sound/pci/cs46xx/dsp_spos.c	2007-03-26 13:54:33.000000000 +0200
@@ -23,7 +23,6 @@
 #include <sound/driver.h>
 #include <asm/io.h>
 #include <linux/delay.h>
-#include <linux/pci.h>
 #include <linux/pm.h>
 #include <linux/init.h>
 #include <linux/slab.h>
--- linux-2.6.21-rc5.orig/sound/pci/cs46xx/dsp_spos_scb_lib.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/sound/pci/cs46xx/dsp_spos_scb_lib.c	2007-03-26 13:54:33.000000000 +0200
@@ -24,7 +24,6 @@
 #include <sound/driver.h>
 #include <asm/io.h>
 #include <linux/delay.h>
-#include <linux/pci.h>
 #include <linux/pm.h>
 #include <linux/init.h>
 #include <linux/slab.h>
--- linux-2.6.21-rc5.orig/sound/pci/hda/hda_generic.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/sound/pci/hda/hda_generic.c	2007-03-26 13:54:33.000000000 +0200
@@ -23,7 +23,6 @@
 #include <sound/driver.h>
 #include <linux/init.h>
 #include <linux/slab.h>
-#include <linux/pci.h>
 #include <sound/core.h>
 #include "hda_codec.h"
 #include "hda_local.h"
--- linux-2.6.21-rc5.orig/sound/pci/hda/hda_proc.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/sound/pci/hda/hda_proc.c	2007-03-26 13:54:33.000000000 +0200
@@ -23,7 +23,6 @@
 
 #include <sound/driver.h>
 #include <linux/init.h>
-#include <linux/pci.h>
 #include <sound/core.h>
 #include "hda_codec.h"
 #include "hda_local.h"
--- linux-2.6.21-rc5.orig/sound/pci/hda/patch_atihdmi.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/sound/pci/hda/patch_atihdmi.c	2007-03-26 13:54:33.000000000 +0200
@@ -25,7 +25,6 @@
 #include <linux/init.h>
 #include <linux/delay.h>
 #include <linux/slab.h>
-#include <linux/pci.h>
 #include <sound/core.h>
 #include "hda_codec.h"
 #include "hda_local.h"
--- linux-2.6.21-rc5.orig/sound/pci/hda/patch_si3054.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/sound/pci/hda/patch_si3054.c	2007-03-26 13:54:33.000000000 +0200
@@ -26,7 +26,6 @@
 #include <linux/init.h>
 #include <linux/delay.h>
 #include <linux/slab.h>
-#include <linux/pci.h>
 #include <sound/core.h>
 #include "hda_codec.h"
 #include "hda_local.h"
--- linux-2.6.21-rc5.orig/sound/pci/hda/patch_via.c	2007-03-26 13:51:51.000000000 +0200
+++ linux-2.6.21-rc5/sound/pci/hda/patch_via.c	2007-03-26 13:54:33.000000000 +0200
@@ -35,7 +35,6 @@
 #include <linux/init.h>
 #include <linux/delay.h>
 #include <linux/slab.h>
-#include <linux/pci.h>
 #include <sound/core.h>
 #include "hda_codec.h"
 #include "hda_local.h"


-- 
Jean Delvare

Re: 2.6.21-rc4-mm1

[Andrew Morton]

On Mon, 26 Mar 2007 12:34:33 +0200 Eric Rannaud <eric.rannaud@gmail.com> wrote:

> On Mon, Mar 26, 2007 at 01:22:32AM -0800, Andrew Morton wrote:
> > On Mon, 26 Mar 2007 11:09:49 +0200 Cornelia Huck <cornelia.huck@de.ibm.com> wrote:
> > > > If so, do you think I should labour on with
> > > > uevent-improve-error-checking-and-handling.patch plus your fix, or should I
> > > > drop the lot?  (I'm inclined toward the latter, but I'm still not
> > > > sure which patch(es) need to be dropped).
> > > 
> > > This depends on what semantics uevent returning an error code should
> > > have. The firmware code was using it to suppress uevents, but
> > > uevent_suppress is a better idea now. So if we want uevent returning !=
> > > 0 to imply "something really bad happened", all uevent functions have
> > > to be audited and those that work like firmware_uevent have to be
> > > converted to uevent_suppress. This would be cleaner, but I'm not sure
> > > it's worth the work.
> > 
> > We're generally struggling to stay alive amongst all the bugs at present -
> > I'll drop all those patches.
> 
> My mistake, I wrote the guilty patch
> uevent-improve-error-checking-and-handling.patch assuming it was safe to
> treat the return value as an error code, since several uevent functions
> returns things like -ENOMEM.
> 
> Should I rework the patch as Cornelia suggests and resubmit later, when
> things have settled down a little?

Sure, when we've fixed all the bugs ;)

I think we now know what to test for - firmware loading simply collapsed
all over the place with these changes.

Re: 2.6.21-rc4-mm1

[Eric Rannaud]

On Mon, Mar 26, 2007 at 01:22:32AM -0800, Andrew Morton wrote:
> On Mon, 26 Mar 2007 11:09:49 +0200 Cornelia Huck <cornelia.huck@de.ibm.com> wrote:
> > > If so, do you think I should labour on with
> > > uevent-improve-error-checking-and-handling.patch plus your fix, or should I
> > > drop the lot?  (I'm inclined toward the latter, but I'm still not
> > > sure which patch(es) need to be dropped).
> > 
> > This depends on what semantics uevent returning an error code should
> > have. The firmware code was using it to suppress uevents, but
> > uevent_suppress is a better idea now. So if we want uevent returning !=
> > 0 to imply "something really bad happened", all uevent functions have
> > to be audited and those that work like firmware_uevent have to be
> > converted to uevent_suppress. This would be cleaner, but I'm not sure
> > it's worth the work.
> 
> We're generally struggling to stay alive amongst all the bugs at present -
> I'll drop all those patches.

My mistake, I wrote the guilty patch
uevent-improve-error-checking-and-handling.patch assuming it was safe to
treat the return value as an error code, since several uevent functions
returns things like -ENOMEM.

Should I rework the patch as Cornelia suggests and resubmit later, when
things have settled down a little?

Thanks.

Re: 2.6.21-rc4-mm1

[Andrew Morton]

On Mon, 26 Mar 2007 11:09:49 +0200 Cornelia Huck <cornelia.huck@de.ibm.com> wrote:

> On Fri, 23 Mar 2007 21:06:18 -0800,
> Andrew Morton <akpm@linux-foundation.org> wrote:
> 
> > Would I be right in guessing that this was all triggered by
> > uevent-improve-error-checking-and-handling.patch?
> 
> Looks like it, since it passed the uevent failures to the upper layer.

OK, thanks.

> > If so, do you think I should labour on with
> > uevent-improve-error-checking-and-handling.patch plus your fix, or should I
> > drop the lot?  (I'm inclined toward the latter, but I'm still not
> > sure which patch(es) need to be dropped).
> 
> This depends on what semantics uevent returning an error code should
> have. The firmware code was using it to suppress uevents, but
> uevent_suppress is a better idea now. So if we want uevent returning !=
> 0 to imply "something really bad happened", all uevent functions have
> to be audited and those that work like firmware_uevent have to be
> converted to uevent_suppress. This would be cleaner, but I'm not sure
> it's worth the work.

We're generally struggling to stay alive amongst all the bugs at present -
I'll drop all those patches.

Re: 2.6.21-rc4-mm1

[Cornelia Huck]

On Fri, 23 Mar 2007 21:06:18 -0800,
Andrew Morton <akpm@linux-foundation.org> wrote:

> Would I be right in guessing that this was all triggered by
> uevent-improve-error-checking-and-handling.patch?

Looks like it, since it passed the uevent failures to the upper layer.

> If so, do you think I should labour on with
> uevent-improve-error-checking-and-handling.patch plus your fix, or should I
> drop the lot?  (I'm inclined toward the latter, but I'm still not
> sure which patch(es) need to be dropped).

This depends on what semantics uevent returning an error code should
have. The firmware code was using it to suppress uevents, but
uevent_suppress is a better idea now. So if we want uevent returning !=
0 to imply "something really bad happened", all uevent functions have
to be audited and those that work like firmware_uevent have to be
converted to uevent_suppress. This would be cleaner, but I'm not sure
it's worth the work.

Re: 2.6.21-rc4-mm1

[Matt Mackall]

On Wed, Mar 21, 2007 at 11:39:17PM -0800, Andrew Morton wrote:
> On Wed, 21 Mar 2007 15:22:25 -0500 Matt Mackall <mpm@selenic.com> wrote:
> 
> > With the latest -mm, I'm now getting this:
> > 
> > Mar 21 15:06:52 cinder kernel: ipw2200: Detected Intel PRO/Wireless
> > 2200BG Network Connection
> > Mar 21 15:06:52 cinder kernel: firmware_loading_store: unexpected
> > value (0)
> > Mar 21 15:06:52 cinder kernel: ipw2200: ipw2200-bss.fw
> > request_firmware failed:
> > Reason -2
> > Mar 21 15:06:52 cinder kernel: ipw2200: Unable to load firmware: -2
> > Mar 21 15:06:52 cinder kernel: ipw2200: failed to register network
> > device
> 
> The firmware loading bug is caused by
> driver-core-handles-kobject_uevent-failure-while-device_add.patch
> 
> I've uploaded a revert patch to
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/hot-fixes/

For the record, with the following patches:

# hotfixes
mm-debug-check-for-the-fault-vs-invalidate-race.patch
mm-fix-fault-vs-invalidate-race-for-linear-mappings-fix-2.patch
mm-fix-fault-vs-invalidate-race-for-linear-mappings-fix.patch
revert-driver-core-handles-kobject_uevent-failure-while-device_add.patch
tty-in-tiocsctty-when-we-steal-a-tty-hang-it-up-fix.patch

...I just had a boot where firmware loading failed again. rmmod+insmod
fixed it.

-- 
Mathematics is the supreme nostalgia of our time.

Re: 2.6.21-rc4-mm1

[Andrew Morton]

On Fri, 23 Mar 2007 11:10:29 +0100 Cornelia Huck <cornelia.huck@de.ibm.com> wrote:

> On Thu, 22 Mar 2007 13:55:51 -0500,
> Larry Finger <larry.finger@lwfinger.net> wrote:
> 
> > Cornelia Huck wrote:
> > > On Thu, 22 Mar 2007 07:23:06 -0500,
> > > 
> > > This would indicate that dev_uevent had been called. But how could
> > > kobject_uevent then return an error without moaning about an uevent()
> > > error code? Maybe the following debug patch could shed some light on
> > > this (all moaning is prefixed with kobject_uevent_env, so it should be
> > > easy to spot)...
> > 
> > I applied the debug patch, but I don't see any error codes being returned. This time I also got the
> > General Protection Faults. An excerpt of the log is attached.
> 
> Hm, I think I have an idea about what happened.
> 
> The firmware class tried to suppress the first KOBJ_ADD uevent by
> returning -ENODEV in firmware_uevent if FW_STATUS_READY was not set.
> This only worked as long as the return code of kobject_uevent was not
> checked in device_add. hack-to-make-wireless-work.patch made that first
> uevent return successfully, but this possible triggered some udev rule
> too early, leading to firmware load failures.
> 
> The following (completely untested) patch uses uevent_suppress to stop
> the uevent from being generated during device_add. Does this work for
> you?
> 
> ---
>  drivers/base/firmware_class.c |    2 ++
>  1 file changed, 2 insertions(+)
> 
> --- linux-2.6.orig/drivers/base/firmware_class.c
> +++ linux-2.6/drivers/base/firmware_class.c
> @@ -333,6 +333,7 @@ static int fw_register_device(struct dev
>  	f_dev->parent = device;
>  	f_dev->class = &firmware_class;
>  	dev_set_drvdata(f_dev, fw_priv);
> +	f_dev->uevent_suppress = 1;
>  	retval = device_register(f_dev);
>  	if (retval) {
>  		printk(KERN_ERR "%s: device_register failed\n",
> @@ -385,6 +386,7 @@ static int fw_setup_device(struct firmwa
>                  set_bit(FW_STATUS_READY, &fw_priv->status);
>          else
>                  set_bit(FW_STATUS_READY_NOHOTPLUG, &fw_priv->status);
> +	f_dev->uevent_suppress = 0;
>  	*dev_p = f_dev;
>  	goto out;

hm.

Would I be right in guessing that this was all triggered by
uevent-improve-error-checking-and-handling.patch?

If so, do you think I should labour on with
uevent-improve-error-checking-and-handling.patch plus your fix, or should I
drop the lot?  (I'm inclined toward the latter, but I'm still not
sure which patch(es) need to be dropped).

Thanks.

Re: 2.6.21-rc4-mm1

[Larry Finger]

Zan Lynx wrote:
> 
> It may have partly been a problem of having half of softmac and half
> devicescape.  I'm not entirely sure what udev did.
> 
> I tried a patch for the Sonic Silicon that was posted and I turned off
> all the configuration for the softmac driver.
> 
> It isn't crashing right now but 802.11 isn't working either.  I may get
> a chance this weekend to try some things with it, and some different
> firmware sets.

That is my experience with a 4311. It does the open authentication and associates, but the WPA
authentication step times out and I never get connected.

> If the new bcm43xx drivers do not support 802.11b at all and never will,
> I missed the documentation.  Someone should add that to Kconfig.

Yes it should. Until bcm43xx-mac80211 got picked up by -mm, it was only used within the bcm43xx
group and that was understood in that circle. It has just been decided that the softmac version of
the driver will be renamed bcm4301 and be converted to use mac80211. When bcm43xx-mac80211 goes
mainline, bcm4301 will be restricted to 802.11b-only cards. That is the way we will support the
older cards. The reason for a separate driver is that the bcm4301 and bcm4303 do not have sufficient
memory to run the latest firmware (V4), and bcm43xx-mac80211 only uses that firmware; whereas
bcm4301 will use the older V3 firmware.

Larry

Re: 2.6.21-rc4-mm1

[Con Kolivas]

On Friday 23 March 2007 23:28, Andy Whitcroft wrote:
> Andy Whitcroft wrote:
> > Con Kolivas wrote:
> >> On Friday 23 March 2007 05:17, Andy Whitcroft wrote:
> >>> Ok, I have yet a third x86_64 machine is is blowing up with the latest
> >>> 2.6.21-rc4-mm1+hotfixes+rsdl-0.32 but working with
> >>> 2.6.21-rc4-mm1+hotfixes-RSDL.  I have results on various hotfix levels
> >>> so I have just fired off a set of tests across the affected machines on
> >>> that latest hotfix stack plus the RSDL backout and the results should
> >>> be in in the next hour or two.
> >>>
> >>> I think there is a strong correlation between RSDL and these hangs. 
> >>> Any suggestions as to the next step.
> >>
> >> Found a nasty in requeue_task
> >> +	if (list_empty(old_array->queue + old_prio))
> >> +		__clear_bit(old_prio, p->array->prio_bitmap);
> >>
> >> see anything wrong there? I do :P
> >>
> >> I'll queue that up with the other changes pending and hopefully that
> >> will fix your bug.
> >
> > Tests queued with your rdsl-0.33 patch (I am assuming its in there).
> > Will let you know how it looks.
>
> Hmmm, this is good for the original machine (as was 0.32) but not for
> either of the other two.  I am seeing panics as below on those two.

This machine seems most sensitive to it (first column):
elm3b6
amd64
newisys
4cpu
config: amd64

Can you throw this debugging patch at it please? The console output might be 
very helpful. On top of sched-rsdl-0.33 thanks!

---
 kernel/sched.c |   39 +++++++++++++++++++++++++++++++++++++++
 1 file changed, 39 insertions(+)

Index: linux-2.6.21-rc4-mm1/kernel/sched.c
===================================================================
--- linux-2.6.21-rc4-mm1.orig/kernel/sched.c	2007-03-24 08:32:19.000000000 +1100
+++ linux-2.6.21-rc4-mm1/kernel/sched.c	2007-03-24 08:42:04.000000000 +1100
@@ -659,6 +659,25 @@ static inline void set_task_entitlement(
 	p->time_slice = p->quota;
 }
 
+static int debug_rqbitmap(struct rq *rq)
+{
+	struct list_head *queue;
+	int idx = 0, error = 0;
+	struct prio_array *array = rq->active;
+
+	for (idx = 0; idx < MAX_PRIO; idx++) {
+		queue = array->queue + idx;
+		if (!list_empty(queue)) {
+			if (!test_bit(idx, rq->dyn_bitmap)) {
+				__set_bit(idx, rq->dyn_bitmap);
+				error = 1;
+				printk(KERN_ERR "MISSING DYNAMIC BIT %d\n", idx);
+			}
+		}
+	}
+	return error;
+}
+
 /*
  * There is no specific hard accounting. The dynamic bits can have
  * false positives. rt_tasks can only be on the active queue.
@@ -679,6 +698,7 @@ static void dequeue_task(struct task_str
 	list_del_init(&p->run_list);
 	if (list_empty(p->array->queue + p->prio))
 		__clear_bit(p->prio, p->array->prio_bitmap);
+	WARN_ON(debug_rqbitmap(rq));
 }
 
 /*
@@ -797,12 +817,14 @@ static void enqueue_task(struct task_str
 {
 	__enqueue_task(p, rq);
 	list_add_tail(&p->run_list, p->array->queue + p->prio);
+	WARN_ON(debug_rqbitmap(rq));
 }
 
 static inline void enqueue_task_head(struct task_struct *p, struct rq *rq)
 {
 	__enqueue_task(p, rq);
 	list_add(&p->run_list, p->array->queue + p->prio);
+	WARN_ON(debug_rqbitmap(rq));
 }
 
 /*
@@ -820,6 +842,7 @@ static void requeue_task(struct task_str
 			__clear_bit(old_prio, old_array->prio_bitmap);
 		set_dynamic_bit(p, rq);
 	}
+	WARN_ON(debug_rqbitmap(rq));
 }
 
 /*
@@ -906,6 +929,7 @@ static inline void __activate_task(struc
 {
 	enqueue_task(p, rq);
 	inc_nr_running(p, rq);
+	WARN_ON(debug_rqbitmap(rq));
 }
 
 /*
@@ -1006,6 +1030,7 @@ static void deactivate_task(struct task_
 {
 	dec_nr_running(p, rq);
 	dequeue_task(p, rq);
+	WARN_ON(debug_rqbitmap(rq));
 }
 
 /*
@@ -1718,9 +1743,11 @@ void fastcall wake_up_new_task(struct ta
 		 * Parent and child are on different CPUs, now get the
 		 * parent runqueue to update the parent's ->flags:
 		 */
+		WARN_ON(debug_rqbitmap(rq));
 		task_rq_unlock(rq, &flags);
 		this_rq = task_rq_lock(current, &flags);
 	}
+	WARN_ON(debug_rqbitmap(this_rq));
 	task_rq_unlock(this_rq, &flags);
 }
 
@@ -3357,6 +3384,7 @@ static inline void major_prio_rotation(s
 	rq->dyn_bitmap = rq->active->prio_bitmap;
 	rq->best_static_prio = MAX_PRIO - 1;
 	rq->prio_rotation++;
+	WARN_ON(debug_rqbitmap(rq));
 }
 
 /*
@@ -3399,6 +3427,8 @@ static inline void rotate_runqueue_prior
 		}
 		memset(rq->prio_quota, 0, ARRAY_SIZE(rq->prio_quota));
 		major_prio_rotation(rq);
+		WARN_ON(debug_rqbitmap(rq));
+
 	} else {
 		/* Minor rotation */
 		new_prio_level = rq->prio_level + 1;
@@ -3409,6 +3439,7 @@ static inline void rotate_runqueue_prior
 			__set_bit(new_prio_level, rq->dyn_bitmap);
 		}
 		rq_quota(rq, rq->prio_level) = 0;
+		WARN_ON(debug_rqbitmap(rq));
 	}
 	rq->prio_level = new_prio_level;
 	/*
@@ -3431,6 +3462,10 @@ static void task_running_tick(struct rq 
 		return;
 
 	spin_lock(&rq->lock);
+	if (!p->time_slice) {
+		printk(KERN_ERR "NO TIME_SLICE IN TRT \n");
+		p->time_slice++;
+	}
 	/*
 	 * Accounting is performed by both the task and the runqueue. This
 	 * allows frequently sleeping tasks to get their proper quota of
@@ -3460,6 +3495,7 @@ static void task_running_tick(struct rq 
 		set_tsk_need_resched(p);
 	}
 out_unlock:
+	WARN_ON(debug_rqbitmap(rq));
 	spin_unlock(&rq->lock);
 }
 
@@ -3479,6 +3515,7 @@ void scheduler_tick(void)
 
 	if (!idle_at_tick)
 		task_running_tick(rq, p, 1);
+	WARN_ON(debug_rqbitmap(rq));
 #ifdef CONFIG_SMP
 	update_load(rq);
 	rq->idle_at_tick = idle_at_tick;
@@ -3548,6 +3585,7 @@ static inline struct task_struct *next_d
 	struct prio_array *array = rq->active;
 	int expirations = 0;
 
+	WARN_ON(debug_rqbitmap(rq));
 retry:
 	if (idx >= MAX_PRIO) {
 		BUG_ON(++expirations > 1);
@@ -3601,6 +3639,7 @@ retry:
 	if (next->static_prio < rq->best_static_prio &&
 	    next->policy != SCHED_BATCH)
 		rq->best_static_prio = next->static_prio;
+	WARN_ON(debug_rqbitmap(rq));
 	return next;
 }
 


-- 
-ck

Re: 2.6.21-rc4-mm1

[Zan Lynx]

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

On Wed, 2007-03-21 at 11:13 -0500, Larry Finger wrote:
> Andrew Morton wrote:
> > On Tue, 20 Mar 2007 17:23:54 -0600 Zan Lynx <zlynx@acm.org> wrote:
> >> First impressions:
> >> Several of the same bugs as rc3-mm*:
> >>       * Freezes immediately if I touch the wlan0 device after loading
> >>         the new Broadcom wireless driver.
> 
> --snip--
> 
> >> 02:02.0 Network controller: Broadcom Corporation BCM4303 802.11b Wireless LAN Controller (rev 02)
> 
> I'm a little confused. The bcm43xx-mac80211 driver does not handle 802.11b devices, and the
> bcm43xx-softmac driver should not freeze. Which one was configured here?

It may have partly been a problem of having half of softmac and half
devicescape.  I'm not entirely sure what udev did.

I tried a patch for the Sonic Silicon that was posted and I turned off
all the configuration for the softmac driver.

It isn't crashing right now but 802.11 isn't working either.  I may get
a chance this weekend to try some things with it, and some different
firmware sets.

If the new bcm43xx drivers do not support 802.11b at all and never will,
I missed the documentation.  Someone should add that to Kconfig.
-- 
Zan Lynx <zlynx@acm.org>

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

RE: 2.6.21-rc4-mm1

[Fortier,Vincent [Montreal]]

> 
> Andy Whitcroft wrote:
> > Con Kolivas wrote:
> >> On Friday 23 March 2007 05:17, Andy Whitcroft wrote:
> >>> Ok, I have yet a third x86_64 machine is is blowing up with the 
> >>> latest
> >>> 2.6.21-rc4-mm1+hotfixes+rsdl-0.32 but working with 
> >>> 2.6.21-rc4-mm1+hotfixes-RSDL.  I have results on various hotfix 
> >>> levels so I have just fired off a set of tests across the affected

> >>> machines on that latest hotfix stack plus the RSDL backout and the

> >>> results should be in in the next hour or two.
> >>>
> >>> I think there is a strong correlation between RSDL and these
hangs.  
> >>> Any suggestions as to the next step.
> >> Found a nasty in requeue_task
> >> +	if (list_empty(old_array->queue + old_prio))
> >> +		__clear_bit(old_prio, p->array->prio_bitmap);
> >>
> >> see anything wrong there? I do :P
> >>
> >> I'll queue that up with the other changes pending and hopefully
that 
> >> will fix your bug.
> > 
> > Tests queued with your rdsl-0.33 patch (I am assuming its in there).
> > Will let you know how it looks.
> 
> Hmmm, this is good for the original machine (as was 0.32) but 
> not for either of the other two.  I am seeing panics as below 
> on those two.
> 
> -apw
> 

I don't know if this might help out or even if it is related but I get a
"similar" crash every time using my backported rsdl patch on a 2.6.19.7
kernel.  "Maybie" this type of BUG might be easier to trigger under that
specific kernel?  Here is a picture of the output:
http://linux-dev.qc.ec.gc.ca/kernel/debian/etch/x86_64/2.6.19/bug-2.6.19
.7-rsdl-033.jpg.

- vin

Re: 2.6.21-rc4-mm1

[Larry Finger]

Cornelia Huck wrote:
> On Thu, 22 Mar 2007 13:55:51 -0500,
> Larry Finger <larry.finger@lwfinger.net> wrote:
>> I applied the debug patch, but I don't see any error codes being returned. This time I also got the
>> General Protection Faults. An excerpt of the log is attached.
> 
> Hm, I think I have an idea about what happened.
> 
> The firmware class tried to suppress the first KOBJ_ADD uevent by
> returning -ENODEV in firmware_uevent if FW_STATUS_READY was not set.
> This only worked as long as the return code of kobject_uevent was not
> checked in device_add. hack-to-make-wireless-work.patch made that first
> uevent return successfully, but this possible triggered some udev rule
> too early, leading to firmware load failures.
> 
> The following (completely untested) patch uses uevent_suppress to stop
> the uevent from being generated during device_add. Does this work for
> you?

Yes it does. Good job. On my first reboot with the new code, the startup of X hung with the black
screen and the big X cursor, but that seems to have been a single occurrence. With the patch, the
bcm43xx firmware is loaded and the device is working.

Thanks,

Larry

Re: 2.6.21-rc4-mm1

[Andy Whitcroft]

Andy Whitcroft wrote:
> Con Kolivas wrote:
>> On Friday 23 March 2007 05:17, Andy Whitcroft wrote:
>>> Ok, I have yet a third x86_64 machine is is blowing up with the latest
>>> 2.6.21-rc4-mm1+hotfixes+rsdl-0.32 but working with
>>> 2.6.21-rc4-mm1+hotfixes-RSDL.  I have results on various hotfix levels
>>> so I have just fired off a set of tests across the affected machines on
>>> that latest hotfix stack plus the RSDL backout and the results should be
>>> in in the next hour or two.
>>>
>>> I think there is a strong correlation between RSDL and these hangs.  Any
>>> suggestions as to the next step.
>> Found a nasty in requeue_task
>> +	if (list_empty(old_array->queue + old_prio))
>> +		__clear_bit(old_prio, p->array->prio_bitmap);
>>
>> see anything wrong there? I do :P
>>
>> I'll queue that up with the other changes pending and hopefully that will fix 
>> your bug.
> 
> Tests queued with your rdsl-0.33 patch (I am assuming its in there).
> Will let you know how it looks.

Hmmm, this is good for the original machine (as was 0.32) but not for
either of the other two.  I am seeing panics as below on those two.

-apw

elm3b245:

NULL pointer dereference
 at 0000000000000020 RIP:
 [<ffffffff80497d94>] __sched_text_start+0x424/0x8a5
PGD 0
Oops: 0000 [1] SMP
last sysfs file: block/ram0/uevent
CPU 0
Modules linked in:
Pid: 1038, comm: udevd Not tainted 2.6.21-rc4-mm1-autokern1 #1
RIP: 0010:[<ffffffff80497d94>]  [<ffffffff80497d94>]
__sched_text_start+0x424/0x8a5
RSP: 0018:ffff81000316de68  EFLAGS: 00010017
RAX: 00000000000006c6 RBX: 0000000000000001 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 000000000000008c RDI: ffffffffffffffd0
RBP: ffff81000316def8 R08: 0000000000000064 R09: 0000000000000024
R10: ffff810001014ad8 R11: 0000000000000286 R12: ffff810001014218
R13: ffff810001013780 R14: ffff810001769450 R15: 0000000000000000
FS:  00002b75d89c66d0(0000) GS:ffffffff805aa000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 0000000000000020 CR3: 0000000000201000 CR4: 00000000000006e0
Process udevd (pid: 1038, threadinfo ffff81000316c000, task
ffff8100031cebb0)
Stack:  0000000000000000 0000000000000001 0000000000000000 ffff8100031cebb0
 ffffffffffffffd0 00000036e28ef568 ffff8100031ced48 0000000000000292
 ffff81000316def8 0000000000000246 ffff81000316def8 ffffffff8022af3d
Call Trace:
 [<ffffffff8022af3d>] put_files_struct+0xbd/0xc9
 [<ffffffff8022c773>] do_exit+0x7d2/0x7d6
 [<ffffffff8022c801>] sys_exit_group+0x0/0x14
 [<ffffffff8022c813>] sys_exit_group+0x12/0x14
 [<ffffffff8020968e>] system_call+0x7e/0x83


Code: 48 39 47 50 74 51 48 c7 47 40 00 00 00 00 8b 52 f4 48 b9 40
RIP  [<ffffffff80497d94>] __sched_text_start+0x424/0x8a5
 RSP <ffff81000316de68>
CR2: 0000000000000020
Fixing recursive fault but reboot is needed!


elm3b6:
Unable to handle kernel paging request at 000000000000fb6c RIP:
 [<ffffffff8020c573>] convert_rip_to_linear+0x53/0x91
PGD 180780067 PUD 182242067 PMD 0
Oops: 0000 [1] SMP
last sysfs file:
devices/pci0000:00/0000:00:0a.0/0000:02:04.0/host0/target0:0:6/0:0:6:0/type
CPU 0
Modules linked in:
Pid: 2442, comm: autorun Not tainted 2.6.21-rc4-mm1-autokern1 #1
RIP: 0010:[<ffffffff8020c573>]  [<ffffffff8020c573>]
convert_rip_to_linear+0x53/0x91
RSP: 0000:ffff810181a53cf8  EFLAGS: 00010002
RAX: 000000000000fb68 RBX: ffff810181a53e28 RCX: ffff8101823d6930
RDX: ffffffff8049fb6d RSI: ffff810182342180 RDI: ffff810182342440
RBP: ffff810181a53cf8 R08: 0000000080209bb9 R09: 000000000000008c
R10: 0000000000000000 R11: 0000000001200011 R12: 0000000000000000
R13: ffff810182342180 R14: ffff810181a53e28 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffffffff805b2000(0063) knlGS:00000000f7f1cb80
CS:  0010 DS: 002b ES: 002b CR0: 000000008005003b
CR2: 000000000000fb6c CR3: 0000000181a5b000 CR4: 00000000000006e0
Process autorun (pid: 2442, threadinfo ffff810181a52000, task
ffff8101823d6930)
Stack:  ffff810181a53d18 ffffffff80219075 ffff8101823d84a8 0000000000000020
 ffff810181a53e18 ffffffff80219ab4 ffff8101fff654d8 ffff810181a53d48
 ffffffff80264291 ffff8101823d6930 ffff810181a53e28 0000000000000046
Call Trace:
 [<ffffffff80219075>] is_prefetch+0x29/0x217
 [<ffffffff80219ab4>] do_page_fault+0x608/0x7f0
 [<ffffffff80264291>] page_dup_rmap+0x1d/0x24
 [<ffffffff8024567c>] search_module_extables+0x83/0x8f
 [<ffffffff80229b43>] oops_enter+0xe/0x10
 [<ffffffff8020ae62>] oops_begin+0x3c/0x70
 [<ffffffff80219b31>] do_page_fault+0x685/0x7f0
 [<ffffffff8022404d>] task_running_tick+0xad/0x290
 [<ffffffff8049fb6d>] error_exit+0x0/0x84
 [<ffffffff8049fb6d>] error_exit+0x0/0x84
 [<ffffffff8049dc11>] thread_return+0x22/0xd3
 [<ffffffff80209802>] int_careful+0xd/0x11


Code: 8b 48 04 0f b7 50 02 0f b6 c1 c1 e0 10 09 c2 89 c8 25 00 00
RIP  [<ffffffff8020c573>] convert_rip_to_linear+0x53/0x91
 RSP <ffff810181a53cf8>
CR2: 000000000000fb6c

Re: 2.6.21-rc4-mm1

[Cornelia Huck]

On Thu, 22 Mar 2007 13:55:51 -0500,
Larry Finger <larry.finger@lwfinger.net> wrote:

> Cornelia Huck wrote:
> > On Thu, 22 Mar 2007 07:23:06 -0500,
> > 
> > This would indicate that dev_uevent had been called. But how could
> > kobject_uevent then return an error without moaning about an uevent()
> > error code? Maybe the following debug patch could shed some light on
> > this (all moaning is prefixed with kobject_uevent_env, so it should be
> > easy to spot)...
> 
> I applied the debug patch, but I don't see any error codes being returned. This time I also got the
> General Protection Faults. An excerpt of the log is attached.

Hm, I think I have an idea about what happened.

The firmware class tried to suppress the first KOBJ_ADD uevent by
returning -ENODEV in firmware_uevent if FW_STATUS_READY was not set.
This only worked as long as the return code of kobject_uevent was not
checked in device_add. hack-to-make-wireless-work.patch made that first
uevent return successfully, but this possible triggered some udev rule
too early, leading to firmware load failures.

The following (completely untested) patch uses uevent_suppress to stop
the uevent from being generated during device_add. Does this work for
you?

---
 drivers/base/firmware_class.c |    2 ++
 1 file changed, 2 insertions(+)

--- linux-2.6.orig/drivers/base/firmware_class.c
+++ linux-2.6/drivers/base/firmware_class.c
@@ -333,6 +333,7 @@ static int fw_register_device(struct dev
 	f_dev->parent = device;
 	f_dev->class = &firmware_class;
 	dev_set_drvdata(f_dev, fw_priv);
+	f_dev->uevent_suppress = 1;
 	retval = device_register(f_dev);
 	if (retval) {
 		printk(KERN_ERR "%s: device_register failed\n",
@@ -385,6 +386,7 @@ static int fw_setup_device(struct firmwa
                 set_bit(FW_STATUS_READY, &fw_priv->status);
         else
                 set_bit(FW_STATUS_READY_NOHOTPLUG, &fw_priv->status);
+	f_dev->uevent_suppress = 0;
 	*dev_p = f_dev;
 	goto out;
 

Re: 2.6.21-rc4-mm1

[Andy Whitcroft]

Con Kolivas wrote:
> On Friday 23 March 2007 05:17, Andy Whitcroft wrote:
>> Ok, I have yet a third x86_64 machine is is blowing up with the latest
>> 2.6.21-rc4-mm1+hotfixes+rsdl-0.32 but working with
>> 2.6.21-rc4-mm1+hotfixes-RSDL.  I have results on various hotfix levels
>> so I have just fired off a set of tests across the affected machines on
>> that latest hotfix stack plus the RSDL backout and the results should be
>> in in the next hour or two.
>>
>> I think there is a strong correlation between RSDL and these hangs.  Any
>> suggestions as to the next step.
> 
> Found a nasty in requeue_task
> +	if (list_empty(old_array->queue + old_prio))
> +		__clear_bit(old_prio, p->array->prio_bitmap);
> 
> see anything wrong there? I do :P
> 
> I'll queue that up with the other changes pending and hopefully that will fix 
> your bug.

Tests queued with your rdsl-0.33 patch (I am assuming its in there).
Will let you know how it looks.

-apw

Re: 2.6.21-rc4-mm1

[Con Kolivas]

On Friday 23 March 2007 05:17, Andy Whitcroft wrote:
> Ok, I have yet a third x86_64 machine is is blowing up with the latest
> 2.6.21-rc4-mm1+hotfixes+rsdl-0.32 but working with
> 2.6.21-rc4-mm1+hotfixes-RSDL.  I have results on various hotfix levels
> so I have just fired off a set of tests across the affected machines on
> that latest hotfix stack plus the RSDL backout and the results should be
> in in the next hour or two.
>
> I think there is a strong correlation between RSDL and these hangs.  Any
> suggestions as to the next step.

Found a nasty in requeue_task
+	if (list_empty(old_array->queue + old_prio))
+		__clear_bit(old_prio, p->array->prio_bitmap);

see anything wrong there? I do :P

I'll queue that up with the other changes pending and hopefully that will fix 
your bug.

-- 
-ck

Re: 2.6.21-rc4-mm1

[Andrew Morton]

Please always do reply-to-all.

On Fri, 23 Mar 2007 00:27:09 +0100 "J.A. Magallón" <jamagallon@ono.com> wrote:

> On Mon, 19 Mar 2007 20:56:23 -0800, Andrew Morton <akpm@linux-foundation.org> wrote:
> 
> > 
> > Temporarily at
> > 
> >   http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
> > 
> > Will appear later at
> > 
> >   ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/
> > 
> 
> Is anybody having problems with optical drives and this kernel ?
> I can't get my dvdrw to spit any events to udevmonitor. If I mount it
> manually everything works fine.

Yes, I think one person reported something similar.

> Perhaps the problem is in hal/g-v-m or anything else, but I suppose that
> udevmonitor receives events directly from kernel, isn't it ?

Probably related to the not-yet-completely-solved firmware loader failures.

It would be good if someone could do a bisection search on this.  I face a
fun evening hunting down a horrendous ext3 performance regression which is
now in mainline.

Re: 2.6.21-rc4-mm1

[J.A. Magallón]

On Mon, 19 Mar 2007 20:56:23 -0800, Andrew Morton <akpm@linux-foundation.org> wrote:

> 
> Temporarily at
> 
>   http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
> 
> Will appear later at
> 
>   ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/
> 

Is anybody having problems with optical drives and this kernel ?
I can't get my dvdrw to spit any events to udevmonitor. If I mount it
manually everything works fine.

Perhaps the problem is in hal/g-v-m or anything else, but I suppose that
udevmonitor receives events directly from kernel, isn't it ?

TIA

--
J.A. Magallon <jamagallon()ono!com>     \               Software is like sex:
                                         \         It's better when it's free
Mandriva Linux release 2007.1 (Cooker) for i586
Linux 2.6.20-jam05 (gcc 4.1.2 20070302 (prerelease) (4.1.2-1mdv2007.1)) #1 SMP PREEMPT

Re: 2.6.21-rc4-mm1

[Con Kolivas]

On Friday 23 March 2007 05:17, Andy Whitcroft wrote:
> Andy Whitcroft wrote:
> > Con Kolivas wrote:
> >> On Thursday 22 March 2007 20:48, Andy Whitcroft wrote:
> >>> Andy Whitcroft wrote:
> >>>> Andy Whitcroft wrote:
> >>>>> Andrew Morton wrote:
> >>>>>> Temporarily at
> >>>>>>
> >>>>>>   http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
> >>>>>>
> >>>>>> Will appear later at
> >>>>>>
> >>>>>>
> >>>>>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21
> >>>>>>-rc 4/2.6.21-rc4-mm1/
> >>>>>
> >>>>> [All of the below is from the pre hot-fix runs.  The very few results
> >>>>> which are in for the hot-fix runs seem worse if anything.  :(  All
> >>>>> results should be out on TKO.]
> >>>>>
> >>>>>> - Restored the RSDL CPU scheduler (a new version thereof)
> >>>>>
> >>>>> Unsure if the above is the culprit but there seems to be a smattering
> >>>>> of BUG's in kernbench from the schedular on several systems, and
> >>>>> panics which do not fully dump out.
> >>>>>
> >>>>> elm3b239 is about 2/4 kernbench being the test in progress when we
> >>>>> blammo in both failed tests, elm3b234 doesn't boot at all.
> >>>>
> >>>> Well I have one result through for backing RSDL out on elm3b239 and
> >>>> that does indeed seem to give us a successful boot and test.  peterz
> >>>> has pointed me to an incremental patch from Con which I'll push
> >>>> through testing and see if that sorts it out.
> >>>
> >>> Ok, tested the patch below on top of 2.6.21-rc4-mm1 and this seems to
> >>> fix the problem:
> >>>
> >>> http://ck.kolivas.org/patches/staircase-deadline/2.6.21-rc4-mm1-rsdl-0.
> >>>32.p atch
> >>>
> >>> Hard to tell from that patch whether it will be fixed in the changes
> >>> already committed to the next -mm.
> >>>
> >>> Its possible that it may be fixed by the following patch:
> >>>
> >>>     sched-rsdl-improvements.patch
> >>>
> >>> Which has the following slipped in at the end of the changelog:
> >>>
> >>>     A tiny change checking for MAX_PRIO in normal_prio()
> >>>     may prevent oopses on bootup on large SMP due to
> >>>     forking off the idle task.
> >>>
> >>> Con, are all the changes in the 0.32 patch above with akpm?
> >>
> >> Yes he's queued everything in that patch you tested for the next -mm.
> >> Thanks very much for testing it.
> >
> > No worries.  I've just got through the results on the other machine in
> > the mix.  That machine seems to be fixed by backing out RSDL and not by
> > the fixup 0.32 patch ...
> >
> > This second machine seems to had hard very soon after user space starts
> > executing but without a panic.  I can't say that the symptoms are very
> > definitive, but I do have a good result from that machine without RSDL
> > and not with rsdl-0.32.
> >
> > The machine is a dual-core x86_64 machine: Dual Core AMD Opteron(tm)
> > Processor 275.
> >
> > I'll let you know if I find out anything else.  Shout if you want any
> > information or have anything you want poked or tested.
>
> Ok, I have yet a third x86_64 machine is is blowing up with the latest
> 2.6.21-rc4-mm1+hotfixes+rsdl-0.32 but working with
> 2.6.21-rc4-mm1+hotfixes-RSDL.  I have results on various hotfix levels
> so I have just fired off a set of tests across the affected machines on
> that latest hotfix stack plus the RSDL backout and the results should be
> in in the next hour or two.
>
> I think there is a strong correlation between RSDL and these hangs.  Any
> suggestions as to the next step.

If it's hitting the bug_on that I put in sched.c which you say it is then it 
is most certainly my fault. It implies a task has been queued without a 
corresponding bit being anywhere in the priority bitmaps. Somehow you only 
seem to be hitting it on big(ger) smp which is why I haven't seen it. It 
implies some complication occuring at sched or idle init/fork off these 
accounting not working. If I could reproduce it on qemu I'd step through the 
kernel init checking where each task is being queued and see if the bitmaps 
are being set. This is obviously time consuming and laborious so I don't 
expect you to do it. 

The next best thing is if you can send me the config of one of the machines 
that's oopsing I can try that on qemu but qemu is only good at debugging 
i386. If any of the machines that were oopsing were i386 that would be very 
helpful, otherwise x86_64 is the next best. Then I need to make a creative 
debugging patch for you to try which checks every queued/dequeued task and 
dumps all that information. I don't have that patch just yet so I need to 
find enough accumulated short stints at the pc to do that (still hurts a lot 
and worsens my condition).

Thanks!

-- 
-ck

Re: 2.6.21-rc4-mm1

[Larry Finger]

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

Cornelia Huck wrote:
> On Thu, 22 Mar 2007 07:23:06 -0500,
> 
> This would indicate that dev_uevent had been called. But how could
> kobject_uevent then return an error without moaning about an uevent()
> error code? Maybe the following debug patch could shed some light on
> this (all moaning is prefixed with kobject_uevent_env, so it should be
> easy to spot)...

I applied the debug patch, but I don't see any error codes being returned. This time I also got the
General Protection Faults. An excerpt of the log is attached.

Thanks,

Larry

[-- Attachment #2: messages --]
[-- Type: text/plain, Size: 15127 bytes --]

Mar 22 13:01:21 larrylap2 kernel: kobject 0000:01:00.0: registering. parent: firmware, set: devices
Mar 22 13:01:21 larrylap2 kernel: kobject_uevent_env: 0000:01:00.0
Mar 22 13:01:21 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0'
Mar 22 13:01:21 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0'
Mar 22 13:01:21 larrylap2 kernel: kobject_uevent_env: returning 0
Mar 22 13:01:21 larrylap2 kernel: kobject_uevent_env: 0000:01:00.0
Mar 22 13:01:21 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0'
Mar 22 13:01:21 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0'
Mar 22 13:01:21 larrylap2 kernel: kobject_uevent_env: returning 0
Mar 22 13:01:21 larrylap2 kernel: firmware_loading_store: unexpected value (0)
Mar 22 13:01:21 larrylap2 kernel: kobject_uevent_env: 0000:01:00.0
Mar 22 13:01:21 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0'
Mar 22 13:01:21 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0'
Mar 22 13:01:21 larrylap2 kernel: kobject_uevent_env: returning 0
Mar 22 13:01:21 larrylap2 kernel: kobject 0000:01:00.0: cleaning up
Mar 22 13:01:21 larrylap2 kernel: bcm43xx: Error: PCM "bcm43xx_pcm5.fw" not available or load failed.
Mar 22 13:01:21 larrylap2 kernel: bcm43xx: core_up for active 802.11 core failed (-2)
Mar 22 13:01:45 larrylap2 kernel: kobject 0000:01:00.0: registering. parent: firmware, set: devices
Mar 22 13:01:45 larrylap2 kernel: kobject_uevent_env: 0000:01:00.0
Mar 22 13:01:45 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0'
Mar 22 13:01:45 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0'
Mar 22 13:01:45 larrylap2 kernel: kobject_uevent_env: returning 0
Mar 22 13:01:45 larrylap2 kernel: kobject_uevent_env: 0000:01:00.0
Mar 22 13:01:45 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0'
Mar 22 13:01:45 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0'
Mar 22 13:01:45 larrylap2 kernel: kobject_uevent_env: returning 0
Mar 22 13:01:46 larrylap2 kernel: kobject_uevent_env: 0000:01:00.0
Mar 22 13:01:46 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0'
Mar 22 13:01:46 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0'
Mar 22 13:01:46 larrylap2 kernel: kobject_uevent_env: returning 0
Mar 22 13:01:46 larrylap2 kernel: kobject 0000:01:00.0: registering. parent: firmware, set: devices
Mar 22 13:01:46 larrylap2 kernel: firmware_loading_store: unexpected value (0)
Mar 22 13:01:46 larrylap2 kernel: kobject 0000:01:00.0: cleaning up
Mar 22 13:01:46 larrylap2 kernel: kobject_uevent_env: 0000:01:00.0
Mar 22 13:01:46 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0'
Mar 22 13:01:46 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0'
Mar 22 13:01:46 larrylap2 kernel: kobject_uevent_env: returning 0
Mar 22 13:01:46 larrylap2 kernel: kobject_uevent_env: 0000:01:00.0
Mar 22 13:01:46 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0'
Mar 22 13:01:46 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0'
Mar 22 13:01:46 larrylap2 kernel: kobject_uevent_env: returning 0
Mar 22 13:01:46 larrylap2 kernel: kobject_uevent_env: 0000:01:00.0
Mar 22 13:01:46 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0'
Mar 22 13:01:46 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0'
Mar 22 13:01:46 larrylap2 kernel: kobject_uevent_env: returning 0
Mar 22 13:01:46 larrylap2 kernel: kobject 0000:01:00.0: cleaning up
Mar 22 13:01:46 larrylap2 kernel: bcm43xx: Error: PCM "bcm43xx_pcm5.fw" not available or load failed.
Mar 22 13:01:46 larrylap2 kernel: bcm43xx: core_up for active 802.11 core failed (-2)
Mar 22 13:02:10 larrylap2 kernel: kobject 0000:01:00.0: registering. parent: firmware, set: devices
Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: 0000:01:00.0
Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0'
Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0'
Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: returning 0
Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: 0000:01:00.0
Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0'
Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0'
Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: returning 0
Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: 0000:01:00.0
Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0'
Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0'
Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: returning 0
Mar 22 13:02:10 larrylap2 kernel: kobject 0000:01:00.0: registering. parent: firmware, set: devices
Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: 0000:01:00.0
Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0'
Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0'
Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: returning 0
Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: 0000:01:00.0
Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0'
Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0'
Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: returning 0
Mar 22 13:02:10 larrylap2 kernel: kobject 0000:01:00.0: cleaning up
Mar 22 13:02:10 larrylap2 kernel: general protection fault: 0000 [2] SMP 
Mar 22 13:02:10 larrylap2 kernel: last sysfs file: class/firmware/0000:01:00.0/loading
Mar 22 13:02:10 larrylap2 kernel: CPU 0 
Mar 22 13:02:10 larrylap2 kernel: Modules linked in: snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device cpufreq_conservative cpufreq_ondemand cpufreq_userspace cpufreq_powersave powernow_k8 freq_table button battery ac nls_utf8 ntfs loop nfsd exportfs nfs lockd nfs_acl sunrpc sr_mod usb_storage libusual snd_hda_intel snd_hda_codec snd_pcm snd_timer snd ohci1394 sdhci ieee1394 soundcore mmc_core snd_page_alloc forcedeth ehci_hcd ide_cd cdrom ohci_hcd usbcore i2c_nforce2 bcm43xx firmware_class ieee80211softmac ieee80211 ieee80211_crypt ext3 mbcache jbd edd sg fan sata_nv libata amd74xx thermal processor sd_mod scsi_mod ide_disk ide_core
Mar 22 13:02:10 larrylap2 kernel: Pid: 4178, comm: cat Not tainted 2.6.21-rc4-mm1-mm1 #14
Mar 22 13:02:10 larrylap2 kernel: RIP: 0010:[<ffffffff80251f99>]  [<ffffffff80251f99>] module_put+0x1f/0x35
Mar 22 13:02:10 larrylap2 kernel: RSP: 0018:ffff810009161ea8  EFLAGS: 00010256
Mar 22 13:02:10 larrylap2 kernel: RAX: 6b6b6b6b6b6b6dab RBX: ffff810005e0c420 RCX: ffffffff803f6183
Mar 22 13:02:10 larrylap2 kernel: RDX: 0000000000000001 RSI: ffffffff802ec409 RDI: 6b6b6b6b6b6b6b6b
Mar 22 13:02:10 larrylap2 kernel: RBP: ffff810009161ea8 R08: 0000000000000000 R09: ffff81000879a888
Mar 22 13:02:10 larrylap2 kernel: R10: 0000000000000000 R11: ffffffff8811b020 R12: ffff810007c7d000
Mar 22 13:02:10 larrylap2 kernel: R13: ffff8100089c86f8 R14: ffff8100082ba048 R15: ffff8100034017c0
Mar 22 13:02:10 larrylap2 kernel: FS:  00002adf2d6ee6f0(0000) GS:ffffffff8051e000(0000) knlGS:00000000f70776d0
Mar 22 13:02:10 larrylap2 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Mar 22 13:02:10 larrylap2 kernel: CR2: 00002adf2d4133c0 CR3: 0000000009146000 CR4: 00000000000006e0
Mar 22 13:02:10 larrylap2 kernel: Process cat (pid: 4178, threadinfo ffff810009160000, task ffff810004d94080)
Mar 22 13:02:10 larrylap2 kernel: Stack:  ffff810009161ec8 ffffffff802cf4ba 0000000000000008 ffff8100082ba048
Mar 22 13:02:10 larrylap2 kernel:  ffff810009161f08 ffffffff80290a44 ffff8100086c2390 ffff8100089c86f8
Mar 22 13:02:10 larrylap2 kernel:  ffff810003590368 0000000000000000 ffff8100089c86f8 00007fff7d91b2d0
Mar 22 13:02:10 larrylap2 kernel: Call Trace:
Mar 22 13:02:10 larrylap2 kernel:  [<ffffffff802cf4ba>] release+0x3a/0x49
Mar 22 13:02:10 larrylap2 kernel:  [<ffffffff80290a44>] __fput+0xca/0x180
Mar 22 13:02:10 larrylap2 kernel:  [<ffffffff80290b0e>] fput+0x14/0x16
Mar 22 13:02:10 larrylap2 kernel:  [<ffffffff8028e1aa>] filp_close+0x66/0x71
Mar 22 13:02:10 larrylap2 kernel:  [<ffffffff8028f3c2>] sys_close+0x98/0xdd
Mar 22 13:02:10 larrylap2 kernel:  [<ffffffff80209f6e>] system_call+0x7e/0x83
Mar 22 13:02:10 larrylap2 kernel: 
Mar 22 13:02:10 larrylap2 kernel: 
Mar 22 13:02:10 larrylap2 kernel: Code: 48 ff 08 83 3f 02 75 0c 48 8b bf 50 22 00 00 e8 08 9d fd ff 
Mar 22 13:02:10 larrylap2 kernel: RIP  [<ffffffff80251f99>] module_put+0x1f/0x35
Mar 22 13:02:10 larrylap2 kernel:  RSP <ffff810009161ea8>
Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: 0000:01:00.0
Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0'
Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0'
Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: returning 0
Mar 22 13:02:10 larrylap2 kernel: kobject 0000:01:00.0: cleaning up
Mar 22 13:02:10 larrylap2 kernel: kobject 0000:01:00.0: registering. parent: firmware, set: devices
Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: 0000:01:00.0
Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0'
Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0'
Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: returning 0
Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: 0000:01:00.0
Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0'
Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0'
Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: returning 0
Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: 0000:01:00.0
Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0'
Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0'
Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: returning 0
Mar 22 13:02:10 larrylap2 kernel: firmware_loading_store: unexpected value (0)
Mar 22 13:02:10 larrylap2 kernel: kobject 0000:01:00.0: cleaning up
Mar 22 13:02:10 larrylap2 kernel: kobject 0000:01:00.0: registering. parent: firmware, set: devices
Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: 0000:01:00.0
Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0'
Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0'
Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: returning 0
Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: 0000:01:00.0
Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0'
Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0'
Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: returning 0
Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: 0000:01:00.0
Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0'
Mar 22 13:02:10 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0'
Mar 22 13:02:10 larrylap2 kernel: kobject_uevent_env: returning 0
Mar 22 13:02:10 larrylap2 kernel: bcm43xx: Error: InitVals "bcm43xx_initval06.fw" not available or load failed.
Mar 22 13:02:10 larrylap2 kernel: bcm43xx: core_up for active 802.11 core failed (-2)
Mar 22 13:02:10 larrylap2 kernel: kobject 0000:01:00.0: cleaning up
Mar 22 13:02:10 larrylap2 kernel: general protection fault: 0000 [3] SMP 
Mar 22 13:02:10 larrylap2 kernel: last sysfs file: class/firmware/0000:01:00.0/loading
Mar 22 13:02:10 larrylap2 kernel: CPU 0 
Mar 22 13:02:10 larrylap2 kernel: Modules linked in: snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device cpufreq_conservative cpufreq_ondemand cpufreq_userspace cpufreq_powersave powernow_k8 freq_table button battery ac nls_utf8 ntfs loop nfsd exportfs nfs lockd nfs_acl sunrpc sr_mod usb_storage libusual snd_hda_intel snd_hda_codec snd_pcm snd_timer snd ohci1394 sdhci ieee1394 soundcore mmc_core snd_page_alloc forcedeth ehci_hcd ide_cd cdrom ohci_hcd usbcore i2c_nforce2 bcm43xx firmware_class ieee80211softmac ieee80211 ieee80211_crypt ext3 mbcache jbd edd sg fan sata_nv libata amd74xx thermal processor sd_mod scsi_mod ide_disk ide_core
Mar 22 13:02:10 larrylap2 kernel: Pid: 4199, comm: cat Not tainted 2.6.21-rc4-mm1-mm1 #14
Mar 22 13:02:10 larrylap2 kernel: RIP: 0010:[<ffffffff80251f99>]  [<ffffffff80251f99>] module_put+0x1f/0x35
Mar 22 13:02:10 larrylap2 kernel: RSP: 0018:ffff810008bfdea8  EFLAGS: 00010256
Mar 22 13:02:10 larrylap2 kernel: RAX: 6b6b6b6b6b6b6dab RBX: ffff8100070eb308 RCX: ffffffff803f6183
Mar 22 13:02:10 larrylap2 kernel: RDX: 0000000000000001 RSI: ffffffff802ec409 RDI: 6b6b6b6b6b6b6b6b
Mar 22 13:02:10 larrylap2 kernel: RBP: ffff810008bfdea8 R08: 0000000000000000 R09: ffff810008745338
Mar 22 13:02:10 larrylap2 kernel: R10: 0000000000000000 R11: ffffffff8811b020 R12: ffff81000999c000
Mar 22 13:02:10 larrylap2 kernel: R13: ffff8100089945a8 R14: ffff81000883e828 R15: ffff8100034017c0
Mar 22 13:02:10 larrylap2 kernel: FS:  00002b325c21c6f0(0000) GS:ffffffff8051e000(0000) knlGS:00000000f70776d0
Mar 22 13:02:10 larrylap2 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Mar 22 13:02:10 larrylap2 kernel: CR2: 00002b325bf413c0 CR3: 0000000005a02000 CR4: 00000000000006e0
Mar 22 13:02:10 larrylap2 kernel: Process cat (pid: 4199, threadinfo ffff810008bfc000, task ffff810006b78140)
Mar 22 13:02:10 larrylap2 kernel: Stack:  ffff810008bfdec8 ffffffff802cf4ba 0000000000000008 ffff81000883e828
Mar 22 13:02:10 larrylap2 kernel:  ffff810008bfdf08 ffffffff80290a44 ffff8100086c26a8 ffff8100089945a8
Mar 22 13:02:10 larrylap2 kernel:  ffff810009010050 0000000000000000 ffff8100089945a8 00007fff4edeb7a0
Mar 22 13:02:10 larrylap2 kernel: Call Trace:
Mar 22 13:02:10 larrylap2 kernel:  [<ffffffff802cf4ba>] release+0x3a/0x49
Mar 22 13:02:10 larrylap2 kernel:  [<ffffffff80290a44>] __fput+0xca/0x180
Mar 22 13:02:10 larrylap2 kernel:  [<ffffffff80290b0e>] fput+0x14/0x16
Mar 22 13:02:10 larrylap2 kernel:  [<ffffffff8028e1aa>] filp_close+0x66/0x71
Mar 22 13:02:10 larrylap2 kernel:  [<ffffffff8028f3c2>] sys_close+0x98/0xdd
Mar 22 13:02:10 larrylap2 kernel:  [<ffffffff80209f6e>] system_call+0x7e/0x83
Mar 22 13:02:10 larrylap2 kernel: 
Mar 22 13:02:10 larrylap2 kernel: 
Mar 22 13:02:10 larrylap2 kernel: Code: 48 ff 08 83 3f 02 75 0c 48 8b bf 50 22 00 00 e8 08 9d fd ff 
Mar 22 13:02:10 larrylap2 kernel: RIP  [<ffffffff80251f99>] module_put+0x1f/0x35
Mar 22 13:02:10 larrylap2 kernel:  RSP <ffff810008bfdea8>

Re: 2.6.21-rc4-mm1

[Andy Whitcroft]

Andy Whitcroft wrote:
> Con Kolivas wrote:
>> On Thursday 22 March 2007 20:48, Andy Whitcroft wrote:
>>> Andy Whitcroft wrote:
>>>> Andy Whitcroft wrote:
>>>>> Andrew Morton wrote:
>>>>>> Temporarily at
>>>>>>
>>>>>>   http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
>>>>>>
>>>>>> Will appear later at
>>>>>>
>>>>>>  
>>>>>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc
>>>>>> 4/2.6.21-rc4-mm1/
>>>>> [All of the below is from the pre hot-fix runs.  The very few results
>>>>> which are in for the hot-fix runs seem worse if anything.  :(  All
>>>>> results should be out on TKO.]
>>>>>
>>>>>> - Restored the RSDL CPU scheduler (a new version thereof)
>>>>> Unsure if the above is the culprit but there seems to be a smattering of
>>>>> BUG's in kernbench from the schedular on several systems, and panics
>>>>> which do not fully dump out.
>>>>>
>>>>> elm3b239 is about 2/4 kernbench being the test in progress when we
>>>>> blammo in both failed tests, elm3b234 doesn't boot at all.
>>>> Well I have one result through for backing RSDL out on elm3b239 and that
>>>> does indeed seem to give us a successful boot and test.  peterz has
>>>> pointed me to an incremental patch from Con which I'll push through
>>>> testing and see if that sorts it out.
>>> Ok, tested the patch below on top of 2.6.21-rc4-mm1 and this seems to
>>> fix the problem:
>>>
>>> http://ck.kolivas.org/patches/staircase-deadline/2.6.21-rc4-mm1-rsdl-0.32.p
>>> atch
>>>
>>> Hard to tell from that patch whether it will be fixed in the changes
>>> already committed to the next -mm.
>>>
>>> Its possible that it may be fixed by the following patch:
>>>
>>>     sched-rsdl-improvements.patch
>>>
>>> Which has the following slipped in at the end of the changelog:
>>>
>>>     A tiny change checking for MAX_PRIO in normal_prio()
>>>     may prevent oopses on bootup on large SMP due to
>>>     forking off the idle task.
>>>
>>> Con, are all the changes in the 0.32 patch above with akpm?
>> Yes he's queued everything in that patch you tested for the next -mm. Thanks 
>> very much for testing it.
> 
> No worries.  I've just got through the results on the other machine in
> the mix.  That machine seems to be fixed by backing out RSDL and not by
> the fixup 0.32 patch ...
> 
> This second machine seems to had hard very soon after user space starts
> executing but without a panic.  I can't say that the symptoms are very
> definitive, but I do have a good result from that machine without RSDL
> and not with rsdl-0.32.
> 
> The machine is a dual-core x86_64 machine: Dual Core AMD Opteron(tm)
> Processor 275.
> 
> I'll let you know if I find out anything else.  Shout if you want any
> information or have anything you want poked or tested.

Ok, I have yet a third x86_64 machine is is blowing up with the latest
2.6.21-rc4-mm1+hotfixes+rsdl-0.32 but working with
2.6.21-rc4-mm1+hotfixes-RSDL.  I have results on various hotfix levels
so I have just fired off a set of tests across the affected machines on
that latest hotfix stack plus the RSDL backout and the results should be
in in the next hour or two.

I think there is a strong correlation between RSDL and these hangs.  Any
suggestions as to the next step.

-apw

Re: 2.6.21-rc4-mm1

[Cornelia Huck]

On Thu, 22 Mar 2007 07:23:06 -0500,
Larry Finger <larry.finger@lwfinger.net> wrote:

> Cornelia Huck wrote:
> > On Wed, 21 Mar 2007 23:39:17 -0800,
> > Andrew Morton <akpm@linux-foundation.org> wrote:
> > 
> >> On Wed, 21 Mar 2007 15:22:25 -0500 Matt Mackall <mpm@selenic.com> wrote:
> >>
> >>> With the latest -mm, I'm now getting this:
> >>>
> >>> Mar 21 15:06:52 cinder kernel: ipw2200: Detected Intel PRO/Wireless
> >>> 2200BG Network Connection
> >>> Mar 21 15:06:52 cinder kernel: firmware_loading_store: unexpected
> >>> value (0)
> >>> Mar 21 15:06:52 cinder kernel: ipw2200: ipw2200-bss.fw
> >>> request_firmware failed:
> >>> Reason -2
> >>> Mar 21 15:06:52 cinder kernel: ipw2200: Unable to load firmware: -2
> >>> Mar 21 15:06:52 cinder kernel: ipw2200: failed to register network
> >>> device
> >> The firmware loading bug is caused by
> >> driver-core-handles-kobject_uevent-failure-while-device_add.patch
> > 
> > Hm, this patch looks sane. It might be a good idea to enable
> > CONFIG_DEBUG_KOBJECT and find out why kobject_uevent() actually fails
> > in this case...
> 
> Attached is the appropriate portion of /var/log/messages with Kobject debugging enabled.

> Mar 22 07:01:42 larrylap2 kernel: kobject 0000:01:00.0: registering. parent: firmware, set: devices
> Mar 22 07:01:42 larrylap2 kernel: kobject_uevent_env
> Mar 22 07:01:42 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0'
> Mar 22 07:01:42 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0'
> Mar 22 07:01:42 larrylap2 kernel: kobject_uevent_env
> Mar 22 07:01:42 larrylap2 ntpd[3434]: frequency initialized -31.513 PPM from /var/lib/ntp/drift/ntp.drift
> Mar 22 07:01:43 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0'
> Mar 22 07:01:43 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0'
> Mar 22 07:01:43 larrylap2 kernel: firmware_loading_store: unexpected value (0)
> Mar 22 07:01:43 larrylap2 kernel: kobject_uevent_env
> Mar 22 07:01:43 larrylap2 kernel: fill_kobj_path: path = '/class/firmware/0000:01:00.0'
> Mar 22 07:01:43 larrylap2 kernel: fill_kobj_path: path = '/devices/pci0000:00/0000:00:02.0/0000:01:00.0'
> Mar 22 07:01:43 larrylap2 kernel: kobject 0000:01:00.0: cleaning up

(Repeating several times)

This would indicate that dev_uevent had been called. But how could
kobject_uevent then return an error without moaning about an uevent()
error code? Maybe the following debug patch could shed some light on
this (all moaning is prefixed with kobject_uevent_env, so it should be
easy to spot)...

---
 lib/kobject_uevent.c |   18 +++++++++++-------
 1 file changed, 11 insertions(+), 7 deletions(-)

--- linux-2.6.orig/lib/kobject_uevent.c
+++ linux-2.6/lib/kobject_uevent.c
@@ -85,11 +85,11 @@ int kobject_uevent_env(struct kobject *k
 	int retval = 0;
 	int j;
 
-	pr_debug("%s\n", __FUNCTION__);
+	pr_debug("%s: %s\n", __FUNCTION__, kobject_name(kobj));
 
 	action_string = action_to_string(action);
 	if (!action_string) {
-		pr_debug("kobject attempted to send uevent without action_string!\n");
+		pr_debug("%s: kobject attempted to send uevent without action_string!\n", __FUNCTION__);
 		return -EINVAL;
 	}
 
@@ -101,7 +101,7 @@ int kobject_uevent_env(struct kobject *k
 		} while (!top_kobj->kset && top_kobj->parent);
 	}
 	if (!top_kobj->kset) {
-		pr_debug("kobject attempted to send uevent without kset!\n");
+		pr_debug("%s: kobject attempted to send uevent without kset!\n", __FUNCTION__);
 		return -EINVAL;
 	}
 
@@ -111,7 +111,7 @@ int kobject_uevent_env(struct kobject *k
 	/*  skip the event, if the filter returns zero. */
 	if (uevent_ops && uevent_ops->filter)
 		if (!uevent_ops->filter(kset, kobj)) {
-			pr_debug("kobject filter function caused the event to drop!\n");
+			pr_debug("%s: kobject filter function caused the event to drop!\n", __FUNCTION__);
 			return 0;
 		}
 
@@ -121,18 +121,20 @@ int kobject_uevent_env(struct kobject *k
 	else
 		subsystem = kobject_name(&kset->kobj);
 	if (!subsystem) {
-		pr_debug("unset subsytem caused the event to drop!\n");
+		pr_debug("%s: unset subsytem caused the event to drop!\n", __FUNCTION__);
 		return 0;
 	}
 
 	/* environment index */
 	envp = kzalloc(NUM_ENVP * sizeof (char *), GFP_KERNEL);
-	if (!envp)
+	if (!envp) {
+		pr_debug("%s: couldn't alloc envp\n", __FUNCTION__);
 		return -ENOMEM;
-
+	}
 	/* environment values */
 	buffer = kmalloc(BUFFER_SIZE, GFP_KERNEL);
 	if (!buffer) {
+		pr_debug("%s: couldn't alloc buffer\n", __FUNCTION__);
 		retval = -ENOMEM;
 		goto exit;
 	}
@@ -140,6 +142,7 @@ int kobject_uevent_env(struct kobject *k
 	/* complete object path */
 	devpath = kobject_get_path(kobj, GFP_KERNEL);
 	if (!devpath) {
+		pr_debug("%s: couldn't get kobject path\n", __FUNCTION__);
 		retval = -ENOENT;
 		goto exit;
 	}
@@ -221,6 +224,7 @@ exit:
 	kfree(devpath);
 	kfree(buffer);
 	kfree(envp);
+	pr_debug("%s: returning %d\n", __FUNCTION__, retval);
 	return retval;
 }
 

Re: 2.6.21-rc4-mm1

[Andy Whitcroft]

Con Kolivas wrote:
> On Thursday 22 March 2007 20:48, Andy Whitcroft wrote:
>> Andy Whitcroft wrote:
>>> Andy Whitcroft wrote:
>>>> Andrew Morton wrote:
>>>>> Temporarily at
>>>>>
>>>>>   http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
>>>>>
>>>>> Will appear later at
>>>>>
>>>>>  
>>>>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc
>>>>> 4/2.6.21-rc4-mm1/
>>>> [All of the below is from the pre hot-fix runs.  The very few results
>>>> which are in for the hot-fix runs seem worse if anything.  :(  All
>>>> results should be out on TKO.]
>>>>
>>>>> - Restored the RSDL CPU scheduler (a new version thereof)
>>>> Unsure if the above is the culprit but there seems to be a smattering of
>>>> BUG's in kernbench from the schedular on several systems, and panics
>>>> which do not fully dump out.
>>>>
>>>> elm3b239 is about 2/4 kernbench being the test in progress when we
>>>> blammo in both failed tests, elm3b234 doesn't boot at all.
>>> Well I have one result through for backing RSDL out on elm3b239 and that
>>> does indeed seem to give us a successful boot and test.  peterz has
>>> pointed me to an incremental patch from Con which I'll push through
>>> testing and see if that sorts it out.
>> Ok, tested the patch below on top of 2.6.21-rc4-mm1 and this seems to
>> fix the problem:
>>
>> http://ck.kolivas.org/patches/staircase-deadline/2.6.21-rc4-mm1-rsdl-0.32.p
>> atch
>>
>> Hard to tell from that patch whether it will be fixed in the changes
>> already committed to the next -mm.
>>
>> Its possible that it may be fixed by the following patch:
>>
>>     sched-rsdl-improvements.patch
>>
>> Which has the following slipped in at the end of the changelog:
>>
>>     A tiny change checking for MAX_PRIO in normal_prio()
>>     may prevent oopses on bootup on large SMP due to
>>     forking off the idle task.
>>
>> Con, are all the changes in the 0.32 patch above with akpm?
> 
> Yes he's queued everything in that patch you tested for the next -mm. Thanks 
> very much for testing it.

No worries.  I've just got through the results on the other machine in
the mix.  That machine seems to be fixed by backing out RSDL and not by
the fixup 0.32 patch ...

This second machine seems to had hard very soon after user space starts
executing but without a panic.  I can't say that the symptoms are very
definitive, but I do have a good result from that machine without RSDL
and not with rsdl-0.32.

The machine is a dual-core x86_64 machine: Dual Core AMD Opteron(tm)
Processor 275.

I'll let you know if I find out anything else.  Shout if you want any
information or have anything you want poked or tested.

-apw

Re: 2.6.21-rc4-mm1

[Sam Ravnborg]

On Thu, Mar 22, 2007 at 04:25:53PM +0000, David Woodhouse wrote:
> On Thu, 2007-03-22 at 12:41 +0100, Sam Ravnborg wrote:
> > Yep - realized this when I took a closer look.
> > One thing striked my mind. It is correct that new things gets added
> > to i386 first these days?
> 
> Personally I tend to do PowerPC first, but most others seem to do i386,
> yes. There are still system calls being added to i386 and not x86_64...
> 
> init/missing_syscalls.h:947:3: warning: #warning syscall getcpu not implemented
> init/missing_syscalls.h:950:3: warning: #warning syscall epoll_pwait not implemented
> init/missing_syscalls.h:953:3: warning: #warning syscall lutimesat not implemented
> init/missing_syscalls.h:956:3: warning: #warning syscall revokeat not implemented
> init/missing_syscalls.h:959:3: warning: #warning syscall frevoke not implemented
> 
> > To me it looks like x86_64 is growing larger than i386 among the
> > developers these days so using asm-x86_64/unistd.h could be a better
> > choice?
> 
> Or perhaps the union of i386, x86_64 and powerpc. But I think i386 is
> good enough for now.
I kept i386 as default so all is good.

	Sam

Re: 2.6.21-rc4-mm1

[David Woodhouse]

On Thu, 2007-03-22 at 12:41 +0100, Sam Ravnborg wrote:
> Yep - realized this when I took a closer look.
> One thing striked my mind. It is correct that new things gets added
> to i386 first these days?

Personally I tend to do PowerPC first, but most others seem to do i386,
yes. There are still system calls being added to i386 and not x86_64...

init/missing_syscalls.h:947:3: warning: #warning syscall getcpu not implemented
init/missing_syscalls.h:950:3: warning: #warning syscall epoll_pwait not implemented
init/missing_syscalls.h:953:3: warning: #warning syscall lutimesat not implemented
init/missing_syscalls.h:956:3: warning: #warning syscall revokeat not implemented
init/missing_syscalls.h:959:3: warning: #warning syscall frevoke not implemented

> To me it looks like x86_64 is growing larger than i386 among the
> developers these days so using asm-x86_64/unistd.h could be a better
> choice?

Or perhaps the union of i386, x86_64 and powerpc. But I think i386 is
good enough for now.

-- 
dwmw2

Re: 2.6.21-rc4-mm1

[Sam Ravnborg]

On Thu, Mar 22, 2007 at 09:17:00AM +0000, David Woodhouse wrote:
> On Wed, 2007-03-21 at 12:59 +0100, Sam Ravnborg wrote:
> > I will give it a shot tonight.
> 
> Thanks. I'll delete the syscalls-2.6.git tree now that you have it.
> 
> > One issue I have with current approach is that the ARCH specific
> > things are in a single .h file. 
> 
> Que? There aren't really any arch-specific things, except for a list of
> syscalls to be ignored which are i386-specific. That's because we're
> pulling in the 'master' system call list from asm-i386/unistd.h, and we
> need to exclude some of those which we don't really need on other
> architectures.
Yep - realized this when I took a closer look.
One thing striked my mind. It is correct that new things gets added
to i386 first these days?
To me it looks like x86_64 is growing larger than i386 among the
developers these days so using asm-x86_64/unistd.h could be a better choice?

	Sam

Re: 2.6.21-rc4-mm1

[Cornelia Huck]

On Wed, 21 Mar 2007 23:39:17 -0800,
Andrew Morton <akpm@linux-foundation.org> wrote:

> On Wed, 21 Mar 2007 15:22:25 -0500 Matt Mackall <mpm@selenic.com> wrote:
> 
> > With the latest -mm, I'm now getting this:
> > 
> > Mar 21 15:06:52 cinder kernel: ipw2200: Detected Intel PRO/Wireless
> > 2200BG Network Connection
> > Mar 21 15:06:52 cinder kernel: firmware_loading_store: unexpected
> > value (0)
> > Mar 21 15:06:52 cinder kernel: ipw2200: ipw2200-bss.fw
> > request_firmware failed:
> > Reason -2
> > Mar 21 15:06:52 cinder kernel: ipw2200: Unable to load firmware: -2
> > Mar 21 15:06:52 cinder kernel: ipw2200: failed to register network
> > device
> 
> The firmware loading bug is caused by
> driver-core-handles-kobject_uevent-failure-while-device_add.patch

Hm, this patch looks sane. It might be a good idea to enable
CONFIG_DEBUG_KOBJECT and find out why kobject_uevent() actually fails
in this case...

Re: 2.6.21-rc4-mm1

[Con Kolivas]

On Thursday 22 March 2007 20:48, Andy Whitcroft wrote:
> Andy Whitcroft wrote:
> > Andy Whitcroft wrote:
> >> Andrew Morton wrote:
> >>> Temporarily at
> >>>
> >>>   http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
> >>>
> >>> Will appear later at
> >>>
> >>>  
> >>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc
> >>>4/2.6.21-rc4-mm1/
> >>
> >> [All of the below is from the pre hot-fix runs.  The very few results
> >> which are in for the hot-fix runs seem worse if anything.  :(  All
> >> results should be out on TKO.]
> >>
> >>> - Restored the RSDL CPU scheduler (a new version thereof)
> >>
> >> Unsure if the above is the culprit but there seems to be a smattering of
> >> BUG's in kernbench from the schedular on several systems, and panics
> >> which do not fully dump out.
> >>
> >> elm3b239 is about 2/4 kernbench being the test in progress when we
> >> blammo in both failed tests, elm3b234 doesn't boot at all.
> >
> > Well I have one result through for backing RSDL out on elm3b239 and that
> > does indeed seem to give us a successful boot and test.  peterz has
> > pointed me to an incremental patch from Con which I'll push through
> > testing and see if that sorts it out.
>
> Ok, tested the patch below on top of 2.6.21-rc4-mm1 and this seems to
> fix the problem:
>
> http://ck.kolivas.org/patches/staircase-deadline/2.6.21-rc4-mm1-rsdl-0.32.p
>atch
>
> Hard to tell from that patch whether it will be fixed in the changes
> already committed to the next -mm.
>
> Its possible that it may be fixed by the following patch:
>
>     sched-rsdl-improvements.patch
>
> Which has the following slipped in at the end of the changelog:
>
>     A tiny change checking for MAX_PRIO in normal_prio()
>     may prevent oopses on bootup on large SMP due to
>     forking off the idle task.
>
> Con, are all the changes in the 0.32 patch above with akpm?

Yes he's queued everything in that patch you tested for the next -mm. Thanks 
very much for testing it.

-- 
-ck

Re: 2.6.21-rc4-mm1

[Andy Whitcroft]

Andy Whitcroft wrote:
> Andy Whitcroft wrote:
>> Andrew Morton wrote:
>>> Temporarily at
>>>
>>>   http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
>>>
>>> Will appear later at
>>>
>>>   ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/
>>>
>>>
>>>
>> [All of the below is from the pre hot-fix runs.  The very few results
>> which are in for the hot-fix runs seem worse if anything.  :(  All
>> results should be out on TKO.]
>>
>>> - Restored the RSDL CPU scheduler (a new version thereof)
>> Unsure if the above is the culprit but there seems to be a smattering of
>> BUG's in kernbench from the schedular on several systems, and panics
>> which do not fully dump out.
>>
>> elm3b239 is about 2/4 kernbench being the test in progress when we
>> blammo in both failed tests, elm3b234 doesn't boot at all.
> 
> Well I have one result through for backing RSDL out on elm3b239 and that
> does indeed seem to give us a successful boot and test.  peterz has
> pointed me to an incremental patch from Con which I'll push through
> testing and see if that sorts it out.

Ok, tested the patch below on top of 2.6.21-rc4-mm1 and this seems to
fix the problem:

http://ck.kolivas.org/patches/staircase-deadline/2.6.21-rc4-mm1-rsdl-0.32.patch

Hard to tell from that patch whether it will be fixed in the changes
already committed to the next -mm.

Its possible that it may be fixed by the following patch:

    sched-rsdl-improvements.patch

Which has the following slipped in at the end of the changelog:

    A tiny change checking for MAX_PRIO in normal_prio()
    may prevent oopses on bootup on large SMP due to
    forking off the idle task.

Con, are all the changes in the 0.32 patch above with akpm?

-apw

Re: 2.6.21-rc4-mm1

[David Woodhouse]

On Wed, 2007-03-21 at 12:59 +0100, Sam Ravnborg wrote:
> I will give it a shot tonight.

Thanks. I'll delete the syscalls-2.6.git tree now that you have it.

> One issue I have with current approach is that the ARCH specific
> things are in a single .h file. 

Que? There aren't really any arch-specific things, except for a list of
syscalls to be ignored which are i386-specific. That's because we're
pulling in the 'master' system call list from asm-i386/unistd.h, and we
need to exclude some of those which we don't really need on other
architectures.

-- 
dwmw2

Re: 2.6.21-rc4-mm1

[Sam Ravnborg]

On Wed, Mar 21, 2007 at 04:01:11PM -0700, Andrew Morton wrote:
> On Wed, 21 Mar 2007 23:19:05 +0100
> Sam Ravnborg <sam@ravnborg.org> wrote:
> 
> > On Tue, Mar 20, 2007 at 09:47:14PM -0800, Andrew Morton wrote:
> > > On Tue, 20 Mar 2007 12:20:16 -0700 Kees Cook <kees@outflux.net> wrote:
> > > 
> > > > I can't 
> > > > get 2.6.21-rc4-mm1 to compile (with or without this fix):
> > > > 
> > > >   GEN     .version
> > > > init/.missing_syscalls.h.cmd:2: *** missing separator.  Stop.
> > > > make: *** [.tmp_vmlinux1] Error 2
> > > 
> > > How'd you manage that?
> > > 
> > > Sam, I think this is a you-thing rather than a dwmw2-thing?
> > Took a look. Things looked pretty OK but an updated patch
> > applied to kbuild.git.
> > Corrected a few things in the Makefile and combined the
> > patch from dwmw2 and Stephane.
> > 
> > kbuild.git pused out and patches follows.
> >
> 
> David has set up a git tree with this stuff, so you presumably
> have an out-of-date copy.
> 
> git://git.infradead.org/~dwmw2/syscalls-2.6.git
> 
> I don't know what's changed in there.  One never does, with git
> trees :(
I pulled that one and last patch in my serie was from that tree.

	Sam

Re: 2.6.21-rc4-mm1

[Andy Whitcroft]

Andy Whitcroft wrote:
> Andrew Morton wrote:
>> Temporarily at
>>
>>   http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
>>
>> Will appear later at
>>
>>   ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/
>>
>>
>>
> 
> [All of the below is from the pre hot-fix runs.  The very few results
> which are in for the hot-fix runs seem worse if anything.  :(  All
> results should be out on TKO.]
> 
>> - Restored the RSDL CPU scheduler (a new version thereof)
> 
> Unsure if the above is the culprit but there seems to be a smattering of
> BUG's in kernbench from the schedular on several systems, and panics
> which do not fully dump out.
> 
> elm3b239 is about 2/4 kernbench being the test in progress when we
> blammo in both failed tests, elm3b234 doesn't boot at all.

Well I have one result through for backing RSDL out on elm3b239 and that
does indeed seem to give us a successful boot and test.  peterz has
pointed me to an incremental patch from Con which I'll push through
testing and see if that sorts it out.

-apw

Re: 2.6.21-rc4-mm1

[Andrew Morton]

On Wed, 21 Mar 2007 15:22:25 -0500 Matt Mackall <mpm@selenic.com> wrote:

> With the latest -mm, I'm now getting this:
> 
> Mar 21 15:06:52 cinder kernel: ipw2200: Detected Intel PRO/Wireless
> 2200BG Network Connection
> Mar 21 15:06:52 cinder kernel: firmware_loading_store: unexpected
> value (0)
> Mar 21 15:06:52 cinder kernel: ipw2200: ipw2200-bss.fw
> request_firmware failed:
> Reason -2
> Mar 21 15:06:52 cinder kernel: ipw2200: Unable to load firmware: -2
> Mar 21 15:06:52 cinder kernel: ipw2200: failed to register network
> device

The firmware loading bug is caused by
driver-core-handles-kobject_uevent-failure-while-device_add.patch

I've uploaded a revert patch to
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/hot-fixes/

Re: 2.6.21-rc4-mm1

[Andrew Morton]

On Wed, 21 Mar 2007 23:19:05 +0100
Sam Ravnborg <sam@ravnborg.org> wrote:

> On Tue, Mar 20, 2007 at 09:47:14PM -0800, Andrew Morton wrote:
> > On Tue, 20 Mar 2007 12:20:16 -0700 Kees Cook <kees@outflux.net> wrote:
> > 
> > > I can't 
> > > get 2.6.21-rc4-mm1 to compile (with or without this fix):
> > > 
> > >   GEN     .version
> > > init/.missing_syscalls.h.cmd:2: *** missing separator.  Stop.
> > > make: *** [.tmp_vmlinux1] Error 2
> > 
> > How'd you manage that?
> > 
> > Sam, I think this is a you-thing rather than a dwmw2-thing?
> Took a look. Things looked pretty OK but an updated patch
> applied to kbuild.git.
> Corrected a few things in the Makefile and combined the
> patch from dwmw2 and Stephane.
> 
> kbuild.git pused out and patches follows.
>

David has set up a git tree with this stuff, so you presumably
have an out-of-date copy.

git://git.infradead.org/~dwmw2/syscalls-2.6.git

I don't know what's changed in there.  One never does, with git
trees :(

Re: 2.6.21-rc4-mm1

[Sam Ravnborg]

On Tue, Mar 20, 2007 at 09:47:14PM -0800, Andrew Morton wrote:
> On Tue, 20 Mar 2007 12:20:16 -0700 Kees Cook <kees@outflux.net> wrote:
> 
> > I can't 
> > get 2.6.21-rc4-mm1 to compile (with or without this fix):
> > 
> >   GEN     .version
> > init/.missing_syscalls.h.cmd:2: *** missing separator.  Stop.
> > make: *** [.tmp_vmlinux1] Error 2
> 
> How'd you manage that?
> 
> Sam, I think this is a you-thing rather than a dwmw2-thing?
Took a look. Things looked pretty OK but an updated patch
applied to kbuild.git.
Corrected a few things in the Makefile and combined the
patch from dwmw2 and Stephane.

kbuild.git pused out and patches follows.

	Sam

Re: 2.6.21-rc4-mm1

[Andrew Morton]

On Wed, 21 Mar 2007 15:22:25 -0500
Matt Mackall <mpm@selenic.com> wrote:

> With the latest -mm, I'm now getting this:
> 
> Mar 21 15:06:52 cinder kernel: ipw2200: Detected Intel PRO/Wireless
> 2200BG Network Connection
> Mar 21 15:06:52 cinder kernel: firmware_loading_store: unexpected
> value (0)
> Mar 21 15:06:52 cinder kernel: ipw2200: ipw2200-bss.fw
> request_firmware failed:
> Reason -2
> Mar 21 15:06:52 cinder kernel: ipw2200: Unable to load firmware: -2
> Mar 21 15:06:52 cinder kernel: ipw2200: failed to register network
> device
> 

Yes, someone seems to have thoroughly bollixed firmware loading.  I was
able to make it pretend to work for my ipw2200, but that obviously wasn't
sufficient.

I plan to do a bisection this evening, find the dud patch.

Re: 2.6.21-rc4-mm1

[Randy Dunlap]

On Wed, 21 Mar 2007 16:03:24 -0500 Larry Finger wrote:

> Matt Mackall wrote:
> > With the latest -mm, I'm now getting this:
> > 
> > Mar 21 15:06:52 cinder kernel: ipw2200: Detected Intel PRO/Wireless
> > 2200BG Network Connection
> > Mar 21 15:06:52 cinder kernel: firmware_loading_store: unexpected
> > value (0)
> > Mar 21 15:06:52 cinder kernel: ipw2200: ipw2200-bss.fw
> > request_firmware failed:
> > Reason -2
> > Mar 21 15:06:52 cinder kernel: ipw2200: Unable to load firmware: -2
> > Mar 21 15:06:52 cinder kernel: ipw2200: failed to register network
> > device
> 
> The problem for me is a general protection fault.
> 
> kernel: general protection fault: 0000 [1] SMP
> kernel: last sysfs file: class/firmware/0000:01:00.0/loading
> kernel: CPU 0
> kernel: Modules linked in: af_packet snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device
> cpufreq_conservative cpufreq_ondemand cpufreq_userspace cpufreq_powersave powernow_k8 freq_table
> button battery ac nls_utf8 ntfs loop nfsd exportfs nfs lockd nfs_acl sunrpc sr_mod usb_storage
> libusual snd_hda_intel snd_hda_codec sdhci snd_pcm snd_timer ohci1394 mmc_core snd ieee1394
> forcedeth soundcore snd_page_alloc ohci_hcd ide_cd ehci_hcd cdrom usbcore i2c_nforce2 bcm43xx
> firmware_class ieee80211softmac ieee80211 ieee80211_crypt ext3 mbcache jbd sg edd fan sata_nv libata
> amd74xx thermal processor sd_mod scsi_mod ide_disk ide_core
> kernel: Pid: 4026, comm: cat Not tainted 2.6.21-rc4-mm1-mm1 #6
> kernel: RIP: 0010:[<ffffffff80251f99>]  [<ffffffff80251f99>] module_put+0x1f/0x35
> kernel: RSP: 0018:ffff810006f85ea8  EFLAGS: 00010256
> kernel: RAX: 6b6b6b6b6b6b6dab RBX: ffff810005dbe1f0 RCX: ffffffff803f6160
> kernel: RDX: 0000000000000001 RSI: ffffffff802ec3dc RDI: 6b6b6b6b6b6b6b6b
> kernel: RBP: ffff810006f85ea8 R08: 0000000000000000 R09: ffff810005918888
> kernel: R10: 0000000000000000 R11: ffffffff8811b020 R12: ffff81000850d000
> kernel: R13: ffff810004ec25a8 R14: ffff810006f38c18 R15: ffff8100034017c0
> kernel: FS:  00002b621c2f86f0(0000) GS:ffffffff8051e000(0000) knlGS:0000000000000000
> kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
> kernel: CR2: 00002b621c01d3c0 CR3: 0000000008154000 CR4: 00000000000006e0
> kernel: Process cat (pid: 4026, threadinfo ffff810006f84000, task ffff810005dd3140)
> kernel: Stack:  ffff810006f85ec8 ffffffff802cf4ba 0000000000000008 ffff810006f38c18
> kernel:  ffff810006f85f08 ffffffff80290a44 ffff81000853bde0 ffff810004ec25a8
> kernel:  ffff8100035d1cb0 0000000000000000 ffff810004ec25a8 00007fff8ed0f6d0
> kernel: Call Trace:
> kernel:  [<ffffffff802cf4ba>] release+0x3a/0x49
> kernel:  [<ffffffff80290a44>] __fput+0xca/0x180
> kernel:  [<ffffffff80290b0e>] fput+0x14/0x16
> kernel:  [<ffffffff8028e1aa>] filp_close+0x66/0x71
> kernel:  [<ffffffff8028f3c2>] sys_close+0x98/0xdd
> kernel:  [<ffffffff80209f6e>] system_call+0x7e/0x83
> kernel:
> kernel:
> kernel: Code: 48 ff 08 83 3f 02 75 0c 48 8b bf 50 22 00 00 e8 08 9d fd ff
> kernel: RIP  [<ffffffff80251f99>] module_put+0x1f/0x35
> kernel:  RSP <ffff810006f85ea8>

which is 'decq' instruction in the local_dec() below:

void module_put(struct module *module)
{
	if (module) {
		unsigned int cpu = get_cpu();
		local_dec(&module->ref[cpu].count);
		/* Maybe they're waiting for us to drop reference? */
		if (unlikely(!module_is_live(module)))
			wake_up_process(module->waiter);
		put_cpu();
	}
}

0000000000000f4e <module_put>:
module_put():
     f4e:	55                   	push   %rbp
     f4f:	48 85 ff             	test   %rdi,%rdi
     f52:	48 89 e5             	mov    %rsp,%rbp
     f55:	74 2a                	je     f81 <module_put+0x33>
     f57:	65 8b 04 25 24 00 00 	mov    %gs:0x24,%eax
     f5e:	00 
     f5f:	89 c0                	mov    %eax,%eax
     f61:	48 c1 e0 07          	shl    $0x7,%rax
     f65:	48 8d 84 38 00 02 00 	lea    0x200(%rax,%rdi,1),%rax
     f6c:	00 
*    f6d:	48 ff 08             	decq   (%rax)
     f70:	83 3f 02             	cmpl   $0x2,(%rdi)
     f73:	75 0c                	jne    f81 <module_put+0x33>
     f75:	48 8b bf 10 06 00 00 	mov    0x610(%rdi),%rdi
     f7c:	e8 00 00 00 00       	callq  f81 <module_put+0x33>
			f7d: R_X86_64_PC32	wake_up_process+0xfffffffffffffffc
     f81:	c9                   	leaveq 
     f82:	c3                   	retq 


---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

Re: 2.6.21-rc4-mm1

[Larry Finger]

Matt Mackall wrote:
> With the latest -mm, I'm now getting this:
> 
> Mar 21 15:06:52 cinder kernel: ipw2200: Detected Intel PRO/Wireless
> 2200BG Network Connection
> Mar 21 15:06:52 cinder kernel: firmware_loading_store: unexpected
> value (0)
> Mar 21 15:06:52 cinder kernel: ipw2200: ipw2200-bss.fw
> request_firmware failed:
> Reason -2
> Mar 21 15:06:52 cinder kernel: ipw2200: Unable to load firmware: -2
> Mar 21 15:06:52 cinder kernel: ipw2200: failed to register network
> device

The problem for me is a general protection fault.

kernel: general protection fault: 0000 [1] SMP
kernel: last sysfs file: class/firmware/0000:01:00.0/loading
kernel: CPU 0
kernel: Modules linked in: af_packet snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device
cpufreq_conservative cpufreq_ondemand cpufreq_userspace cpufreq_powersave powernow_k8 freq_table
button battery ac nls_utf8 ntfs loop nfsd exportfs nfs lockd nfs_acl sunrpc sr_mod usb_storage
libusual snd_hda_intel snd_hda_codec sdhci snd_pcm snd_timer ohci1394 mmc_core snd ieee1394
forcedeth soundcore snd_page_alloc ohci_hcd ide_cd ehci_hcd cdrom usbcore i2c_nforce2 bcm43xx
firmware_class ieee80211softmac ieee80211 ieee80211_crypt ext3 mbcache jbd sg edd fan sata_nv libata
amd74xx thermal processor sd_mod scsi_mod ide_disk ide_core
kernel: Pid: 4026, comm: cat Not tainted 2.6.21-rc4-mm1-mm1 #6
kernel: RIP: 0010:[<ffffffff80251f99>]  [<ffffffff80251f99>] module_put+0x1f/0x35
kernel: RSP: 0018:ffff810006f85ea8  EFLAGS: 00010256
kernel: RAX: 6b6b6b6b6b6b6dab RBX: ffff810005dbe1f0 RCX: ffffffff803f6160
kernel: RDX: 0000000000000001 RSI: ffffffff802ec3dc RDI: 6b6b6b6b6b6b6b6b
kernel: RBP: ffff810006f85ea8 R08: 0000000000000000 R09: ffff810005918888
kernel: R10: 0000000000000000 R11: ffffffff8811b020 R12: ffff81000850d000
kernel: R13: ffff810004ec25a8 R14: ffff810006f38c18 R15: ffff8100034017c0
kernel: FS:  00002b621c2f86f0(0000) GS:ffffffff8051e000(0000) knlGS:0000000000000000
kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
kernel: CR2: 00002b621c01d3c0 CR3: 0000000008154000 CR4: 00000000000006e0
kernel: Process cat (pid: 4026, threadinfo ffff810006f84000, task ffff810005dd3140)
kernel: Stack:  ffff810006f85ec8 ffffffff802cf4ba 0000000000000008 ffff810006f38c18
kernel:  ffff810006f85f08 ffffffff80290a44 ffff81000853bde0 ffff810004ec25a8
kernel:  ffff8100035d1cb0 0000000000000000 ffff810004ec25a8 00007fff8ed0f6d0
kernel: Call Trace:
kernel:  [<ffffffff802cf4ba>] release+0x3a/0x49
kernel:  [<ffffffff80290a44>] __fput+0xca/0x180
kernel:  [<ffffffff80290b0e>] fput+0x14/0x16
kernel:  [<ffffffff8028e1aa>] filp_close+0x66/0x71
kernel:  [<ffffffff8028f3c2>] sys_close+0x98/0xdd
kernel:  [<ffffffff80209f6e>] system_call+0x7e/0x83
kernel:
kernel:
kernel: Code: 48 ff 08 83 3f 02 75 0c 48 8b bf 50 22 00 00 e8 08 9d fd ff
kernel: RIP  [<ffffffff80251f99>] module_put+0x1f/0x35
kernel:  RSP <ffff810006f85ea8>

Larry

Re: 2.6.21-rc4-mm1

[Larry Finger]

Matt Mackall wrote:
> With the latest -mm, I'm now getting this:
> 
> Mar 21 15:06:52 cinder kernel: ipw2200: Detected Intel PRO/Wireless
> 2200BG Network Connection
> Mar 21 15:06:52 cinder kernel: firmware_loading_store: unexpected
> value (0)
> Mar 21 15:06:52 cinder kernel: ipw2200: ipw2200-bss.fw
> request_firmware failed:
> Reason -2
> Mar 21 15:06:52 cinder kernel: ipw2200: Unable to load firmware: -2
> Mar 21 15:06:52 cinder kernel: ipw2200: failed to register network
> device
> 

I am seeing similar messages trying to load bcm43xx firmware with 2.6.21-rc4-mm1.

Larry

Re: 2.6.21-rc4-mm1

[Matt Mackall]

With the latest -mm, I'm now getting this:

Mar 21 15:06:52 cinder kernel: ipw2200: Detected Intel PRO/Wireless
2200BG Network Connection
Mar 21 15:06:52 cinder kernel: firmware_loading_store: unexpected
value (0)
Mar 21 15:06:52 cinder kernel: ipw2200: ipw2200-bss.fw
request_firmware failed:
Reason -2
Mar 21 15:06:52 cinder kernel: ipw2200: Unable to load firmware: -2
Mar 21 15:06:52 cinder kernel: ipw2200: failed to register network
device

-- 
Mathematics is the supreme nostalgia of our time.

Re: 2.6.21-rc4-mm1

[John W. Linville]

On Wed, Mar 21, 2007 at 07:34:28PM +0100, Michael Buesch wrote:
> On Wednesday 21 March 2007 19:14, Larry Finger wrote:
> > Andrew Morton wrote:
> > > On Tue, 20 Mar 2007 17:23:54 -0600 Zan Lynx <zlynx@acm.org> wrote:
> > > 
> > >> On Mon, 2007-03-19 at 20:56 -0800, Andrew Morton wrote:
> > >>> Temporarily at
> > >>>
> > >>>   http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
> > >>>
> > >>> Will appear later at
> > >>>
> > >>>   ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/
> > >> First impressions:
> > >> Several of the same bugs as rc3-mm*:
> > >>       * Freezes immediately if I touch the wlan0 device after loading
> > >>         the new Broadcom wireless driver.
> > 
> > The version of the ssb driver in 2.6.21-rc4-mm1 has a bug that causes a kernel oops if the bcm43xx
> > chip contains a USB (dangling) core. This bug has been fixed in Michael Buesch's tree, but
> > apparently not yet in Linville's wireless-dev tree. The patch is as follows:
> > 
> > commit 08531ff130bcc8181d9294a66e25010f48eefb97
> > Author: Michael Buesch <mb@bu3sch.de>
> > Date:   Wed Mar 7 23:01:08 2007 +0100
> > 
> >     ssb: Don't freeze unregistered devices.
> 
> No, that's a different fix for suspend.
> 
> This is the fix:
> http://bu3sch.de/gitweb?p=wireless-dev.git;a=commitdiff;h=b87f743f3643ea162892dce0bbc91e6f026a49bf
> 
> Pull request was sent to John.

That's "ssb-ohci: Completely disable the driver on non-embedded
systems", also in wireless-dev as of yesterday.

Thanks,

John
-- 
John W. Linville
linville@tuxdriver.com

Re: 2.6.21-rc4-mm1

[John W. Linville]

On Wed, Mar 21, 2007 at 01:14:55PM -0500, Larry Finger wrote:
> Andrew Morton wrote:
> > On Tue, 20 Mar 2007 17:23:54 -0600 Zan Lynx <zlynx@acm.org> wrote:
> > 
> >> On Mon, 2007-03-19 at 20:56 -0800, Andrew Morton wrote:
> >>> Temporarily at
> >>>
> >>>   http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
> >>>
> >>> Will appear later at
> >>>
> >>>   ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/
> >> First impressions:
> >> Several of the same bugs as rc3-mm*:
> >>       * Freezes immediately if I touch the wlan0 device after loading
> >>         the new Broadcom wireless driver.
> 
> The version of the ssb driver in 2.6.21-rc4-mm1 has a bug that causes a kernel oops if the bcm43xx
> chip contains a USB (dangling) core. This bug has been fixed in Michael Buesch's tree, but
> apparently not yet in Linville's wireless-dev tree. The patch is as follows:

FWIW, that patch is in my tree as of yesterday.  Presumably it should
be in the next -mm.

John
-- 
John W. Linville
linville@tuxdriver.com

Re: 2.6.21-rc4-mm1

[Greg KH]

On Tue, Mar 20, 2007 at 06:47:04PM -0700, Randy Dunlap wrote:
> On Mon, 19 Mar 2007 20:56:23 -0800 Andrew Morton wrote:
> 
> > 
> > Temporarily at
> > 
> >   http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
> > 
> > Will appear later at
> > 
> >   ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/
> 
> 
> UIO_CIF should depend on PCI ??
> 
> With CONFIG_PCI=n, I get:
> 
> ERROR: "pci_module_init" [drivers/uio/uio_cif.ko] undefined!
> ERROR: "pci_release_regions" [drivers/uio/uio_cif.ko] undefined!
> make[1]: *** [__modpost] Error 1
> make: *** [modules] Error 2

Thanks, I've made that change now.

greg k-h

Re: 2.6.21-rc4-mm1

[Michael Buesch]

On Wednesday 21 March 2007 19:14, Larry Finger wrote:
> Andrew Morton wrote:
> > On Tue, 20 Mar 2007 17:23:54 -0600 Zan Lynx <zlynx@acm.org> wrote:
> > 
> >> On Mon, 2007-03-19 at 20:56 -0800, Andrew Morton wrote:
> >>> Temporarily at
> >>>
> >>>   http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
> >>>
> >>> Will appear later at
> >>>
> >>>   ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/
> >> First impressions:
> >> Several of the same bugs as rc3-mm*:
> >>       * Freezes immediately if I touch the wlan0 device after loading
> >>         the new Broadcom wireless driver.
> 
> The version of the ssb driver in 2.6.21-rc4-mm1 has a bug that causes a kernel oops if the bcm43xx
> chip contains a USB (dangling) core. This bug has been fixed in Michael Buesch's tree, but
> apparently not yet in Linville's wireless-dev tree. The patch is as follows:
> 
> commit 08531ff130bcc8181d9294a66e25010f48eefb97
> Author: Michael Buesch <mb@bu3sch.de>
> Date:   Wed Mar 7 23:01:08 2007 +0100
> 
>     ssb: Don't freeze unregistered devices.

No, that's a different fix for suspend.

This is the fix:
http://bu3sch.de/gitweb?p=wireless-dev.git;a=commitdiff;h=b87f743f3643ea162892dce0bbc91e6f026a49bf

Pull request was sent to John.

-- 
Greetings Michael.

Re: 2.6.21-rc4-mm1

[Larry Finger]

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

Andrew Morton wrote:
> On Tue, 20 Mar 2007 17:23:54 -0600 Zan Lynx <zlynx@acm.org> wrote:
> 
>> On Mon, 2007-03-19 at 20:56 -0800, Andrew Morton wrote:
>>> Temporarily at
>>>
>>>   http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
>>>
>>> Will appear later at
>>>
>>>   ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/
>> First impressions:
>> Several of the same bugs as rc3-mm*:
>>       * Freezes immediately if I touch the wlan0 device after loading
>>         the new Broadcom wireless driver.

The version of the ssb driver in 2.6.21-rc4-mm1 has a bug that causes a kernel oops if the bcm43xx
chip contains a USB (dangling) core. This bug has been fixed in Michael Buesch's tree, but
apparently not yet in Linville's wireless-dev tree. The patch is as follows:

commit 08531ff130bcc8181d9294a66e25010f48eefb97
Author: Michael Buesch <mb@bu3sch.de>
Date:   Wed Mar 7 23:01:08 2007 +0100

    ssb: Don't freeze unregistered devices.

    Signed-off-by: Michael Buesch <mb@bu3sch.de>

diff --git a/drivers/ssb/core.c b/drivers/ssb/core.c
index 2facada..c956edf 100644
--- a/drivers/ssb/core.c
+++ b/drivers/ssb/core.c
@@ -163,6 +163,8 @@ int ssb_devices_freeze(struct ssb_bus *bus)
 		dev = &(bus->devices[i]);
 		if (!dev->dev->driver)
 			continue;
+		if (!device_is_registered(dev->dev))
+			continue;
 		drv = drv_to_ssb_drv(dev->dev->driver);
 		if (drv && drv->suspend) {
 			err = drv->suspend(dev, state);
@@ -185,6 +187,8 @@ int ssb_devices_thaw(struct ssb_bus *bus)
 		dev = &(bus->devices[i]);
 		if (!dev->dev->driver)
 			continue;
+		if (!device_is_registered(dev->dev))
+			continue;
 		drv = drv_to_ssb_drv(dev->dev->driver);
 		if (drv && drv->resume) {
 			err = drv->resume(dev);

Larry


[-- Attachment #2: usb_freeze --]
[-- Type: text/plain, Size: 939 bytes --]

commit 08531ff130bcc8181d9294a66e25010f48eefb97
Author: Michael Buesch <mb@bu3sch.de>
Date:   Wed Mar 7 23:01:08 2007 +0100

    ssb: Don't freeze unregistered devices.
    
    Signed-off-by: Michael Buesch <mb@bu3sch.de>

diff --git a/drivers/ssb/main.c b/drivers/ssb/main.c
index 2facada..c956edf 100644
--- a/drivers/ssb/main.c
+++ b/drivers/ssb/main.c
@@ -163,6 +163,8 @@ int ssb_devices_freeze(struct ssb_bus *bus)
 		dev = &(bus->devices[i]);
 		if (!dev->dev->driver)
 			continue;
+		if (!device_is_registered(dev->dev))
+			continue;
 		drv = drv_to_ssb_drv(dev->dev->driver);
 		if (drv && drv->suspend) {
 			err = drv->suspend(dev, state);
@@ -185,6 +187,8 @@ int ssb_devices_thaw(struct ssb_bus *bus)
 		dev = &(bus->devices[i]);
 		if (!dev->dev->driver)
 			continue;
+		if (!device_is_registered(dev->dev))
+			continue;
 		drv = drv_to_ssb_drv(dev->dev->driver);
 		if (drv && drv->resume) {
 			err = drv->resume(dev);

Re: 2.6.21-rc4-mm1

[Larry Finger]

Andrew Morton wrote:
> On Tue, 20 Mar 2007 17:23:54 -0600 Zan Lynx <zlynx@acm.org> wrote:
> 
>> On Mon, 2007-03-19 at 20:56 -0800, Andrew Morton wrote:
>>> Temporarily at
>>>
>>>   http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
>>>
>>> Will appear later at
>>>
>>>   ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/
>> First impressions:
>> Several of the same bugs as rc3-mm*:
>>       * Freezes immediately if I touch the wlan0 device after loading
>>         the new Broadcom wireless driver.

--snip--

>> 02:02.0 Network controller: Broadcom Corporation BCM4303 802.11b Wireless LAN Controller (rev 02)

I'm a little confused. The bcm43xx-mac80211 driver does not handle 802.11b devices, and the
bcm43xx-softmac driver should not freeze. Which one was configured here?

Larry

Re: 2.6.21-rc4-mm1

[Sam Ravnborg]

On Tue, Mar 20, 2007 at 09:47:14PM -0800, Andrew Morton wrote:
> On Tue, 20 Mar 2007 12:20:16 -0700 Kees Cook <kees@outflux.net> wrote:
> 
> > I can't 
> > get 2.6.21-rc4-mm1 to compile (with or without this fix):
> > 
> >   GEN     .version
> > init/.missing_syscalls.h.cmd:2: *** missing separator.  Stop.
> > make: *** [.tmp_vmlinux1] Error 2
> 
> How'd you manage that?
> 
> Sam, I think this is a you-thing rather than a dwmw2-thing?
I will give it a shot tonight.
One issue I have with current approach is that the ARCH specific things are
in a single .h file.

	Sam

Re: 2.6.21-rc4-mm1

[David Woodhouse]

On Tue, 2007-03-20 at 21:47 -0800, Andrew Morton wrote:
> On Tue, 20 Mar 2007 12:20:16 -0700 Kees Cook <kees@outflux.net> wrote:
> 
> > I can't 
> > get 2.6.21-rc4-mm1 to compile (with or without this fix):
> > 
> >   GEN     .version
> > init/.missing_syscalls.h.cmd:2: *** missing separator.  Stop.
> > make: *** [.tmp_vmlinux1] Error 2

What if you remove init/.missing_syscalls.h.cmd _and_ apply the patch,
then try again?

-- 
dwmw2

Re: 2.6.21-rc4-mm1

[Reuben Farrelly]

On 20/03/2007 3:56 PM, Andrew Morton wrote:
> Temporarily at
> 
>   http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
> 
> Will appear later at
> 
>   ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/
> 
> 
> 
> - Restored the RSDL CPU scheduler (a new version thereof)

Just booted into this kernel, and hit this, which locked up the machine:

This is tornado.reub.net (Linux x86_64 2.6.21-rc4-mm1) 20:16:58

tornado login: ------------[ cut here ]------------
kernel BUG at kernel/sched.c:3505!
invalid opcode: 0000 [1] SMP
last sysfs file: devices/pci0000:00/0000:00:1f.3/i2c-adapter/i2c-0/0-002e/pwm3
CPU 1
Modules linked in: firmware_class eeprom lm85 hwmon_vid i2c_i801 8021q 
iptable_filter iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nfnetlink 
iptable_mangle ip_tables nfs lockd sunrpc ohci1394 ieee1394 usb_storage
Pid: 8250, comm: clamd Not tainted 2.6.21-rc4-mm1 #1
RIP: 0010:[<ffffffff8025d2cb>]  [<ffffffff8025d2cb>] __sched_text_start+0x3cb/0x8b3
RSP: 0000:ffff8100023cfee0  EFLAGS: 00010002
RAX: 000000000000008c RBX: ffff810001e040e8 RCX: 000000000000000c
RDX: 0000000000000000 RSI: 000000000000008c RDI: ffff810001e049b8
RBP: ffff8100023cff70 R08: 000000000000008c R09: ffff810001e049a8
R10: 0000000000000034 R11: 0000000000000000 R12: ffff810001e03f00
R13: 0000000000000002 R14: 00000000ffffffff R15: 000000521b55f827
FS:  00002b1dfda2ec00(0000) GS:ffff81000208ec40(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 00002aaaaafcf000 CR3: 0000000004ac3000 CR4: 00000000000006e0
Process clamd (pid: 8250, threadinfo ffff8100023ce000, task ffff810004c090a0)
Stack:  ffff810004c090a0 ffffffff8025fdb7 ffff810004c090a0 00007fffae43e955
  ffff810004c09248 00000001023cff28 ffffffff8029635d 0000000000c5aac0
  0000000000000005 00002b1dfc7d6d5a ffffffff8025fdb7 0000000000000000
Call Trace:
  [<ffffffff8025fdb7>] trace_hardirqs_on_thunk+0x35/0x37
  [<ffffffff8029635d>] trace_hardirqs_on+0x12a/0x15d
  [<ffffffff8025fdb7>] trace_hardirqs_on_thunk+0x35/0x37
  [<ffffffff8025a7e0>] retint_careful+0x12/0x2e


Code: 0f 0b eb fe 49 8b 94 24 e0 01 00 00 49 8b 84 24 d8 01 00 00
RIP  [<ffffffff8025d2cb>] __sched_text_start+0x3cb/0x8b3
  RSP <ffff8100023cfee0>
BUG: spinlock lockup on CPU#0, swapper/0, ffff810001e03f00
BUG: spinlock lockup on CPU#1, clamd/8250, ffff810001e03f00

every few minutes the last two lines would be repeated.

This kernel does not include the hotfixes (the gentoo portage ebuild for this 
release does not yet include them), however I am uncertain if they fix this 
problem or not anyway.

Also, what happened to the -mm announcements sent to 
linux-kernel-announce@vger.kernel.org?  Maybe I'm the only person to miss them :-)

Reuben

Re: 2.6.21-rc4-mm1

[Edward Shishkin]

Andrew Morton wrote:

>On Tue, 20 Mar 2007 17:23:54 -0600 Zan Lynx <zlynx@acm.org> wrote:
>
>  
>
>>On Mon, 2007-03-19 at 20:56 -0800, Andrew Morton wrote:
>>    
>>
>>>Temporarily at
>>>
>>>  http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
>>>
>>>Will appear later at
>>>
>>>  ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/
>>>      
>>>
>>First impressions:
>>Several of the same bugs as rc3-mm*:
>>      * Freezes immediately if I touch the wlan0 device after loading
>>        the new Broadcom wireless driver.
>>    
>>
>
>cc linux-wireless
>
>  
>
>>      * Freezes immediately if I allow Bluetooth to configure.
>>    
>>
>
>cc bluez-devel
>
>  
>
>>      * All freezes simply stop, no BUG or panic happens, no watchdog,
>>        soft or NMI ever triggers.  Thinking about it, I wonder if
>>        disabling EDAC_K8 would help here?  Does it steal NMI?  I'll try
>>        that later.
>>    
>>
>
>Mabe that will be fixed by the just-uploaded
>ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/hot-fixes/tty-in-tiocsctty-when-we-steal-a-tty-hang-it-up-fix.patch
>
>  
>
>>      * I am using Reiser4 and after one of the above freezes and hard
>>        power cycle, files that were in use *read*only* are filled with
>>        zeros.
>>

did you enable compression announced not so long ago?
anyway, it would be better to check your fs by fsck.reiser4

>>  For example, while testing and experiencing the above
>>        freezes, I lost /etc/ld.so.preload
>>        and /lib/security/pam_limits.so.  What the heck?
>>    
>>
>
>cc reiserfs-dev
>  
>

Re: 2.6.21-rc4-mm1

[Andrew Morton]

On Tue, 20 Mar 2007 17:23:54 -0600 Zan Lynx <zlynx@acm.org> wrote:

> On Mon, 2007-03-19 at 20:56 -0800, Andrew Morton wrote:
> > Temporarily at
> > 
> >   http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
> > 
> > Will appear later at
> > 
> >   ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/
> 
> First impressions:
> Several of the same bugs as rc3-mm*:
>       * Freezes immediately if I touch the wlan0 device after loading
>         the new Broadcom wireless driver.

cc linux-wireless

>       * Freezes immediately if I allow Bluetooth to configure.

cc bluez-devel

>       * All freezes simply stop, no BUG or panic happens, no watchdog,
>         soft or NMI ever triggers.  Thinking about it, I wonder if
>         disabling EDAC_K8 would help here?  Does it steal NMI?  I'll try
>         that later.

Mabe that will be fixed by the just-uploaded
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/hot-fixes/tty-in-tiocsctty-when-we-steal-a-tty-hang-it-up-fix.patch

>       * I am using Reiser4 and after one of the above freezes and hard
>         power cycle, files that were in use *read*only* are filled with
>         zeros.  For example, while testing and experiencing the above
>         freezes, I lost /etc/ld.so.preload
>         and /lib/security/pam_limits.so.  What the heck?

cc reiserfs-dev

<most of remainder retained, sorry>

> Good points:
>       * Runs longer than 5 minutes, since I am typing this while using
>         it.
>       * I like RDSL so far.
> 
> Advice on who to annoy with further bug reports is welcome.  Bluetooth
> people?  USB people?  Broadcom driver people, probably.
> 
> The system is a Athlon64 laptop, nForce3 motherboard.
> Current lspci, dmesg (cannot get the frozen dmesgs, sorry) and .config
> follow:
> 00:00.0 Host bridge: nVidia Corporation nForce3 Host Bridge (rev a4)
> 00:01.0 ISA bridge: nVidia Corporation nForce3 LPC Bridge (rev a6)
> 00:01.1 SMBus: nVidia Corporation nForce3 SMBus (rev a4)
> 00:02.0 USB Controller: nVidia Corporation nForce3 USB 1.1 (rev a5)
> 00:02.1 USB Controller: nVidia Corporation nForce3 USB 1.1 (rev a5)
> 00:02.2 USB Controller: nVidia Corporation nForce3 USB 2.0 (rev a2)
> 00:06.0 Multimedia audio controller: nVidia Corporation nForce3 Audio (rev a2)
> 00:06.1 Modem: nVidia Corporation nForce3 Audio (rev a2)
> 00:08.0 IDE interface: nVidia Corporation nForce3 IDE (rev a5)
> 00:0a.0 PCI bridge: nVidia Corporation nForce3 PCI Bridge (rev a2)
> 00:0b.0 PCI bridge: nVidia Corporation nForce3 AGP Bridge (rev a4)
> 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
> 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
> 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
> 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
> 01:00.0 VGA compatible controller: nVidia Corporation NV17 [GeForce4 420 Go 32M] (rev a3)
> 02:00.0 FireWire (IEEE 1394): Texas Instruments TSB43AB21 IEEE-1394a-2000 Controller (PHY/Link)
> 02:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
> 02:02.0 Network controller: Broadcom Corporation BCM4303 802.11b Wireless LAN Controller (rev 02)
> 02:04.0 CardBus bridge: Texas Instruments PCI1620 PC Card Controller (rev 01)
> 02:04.1 CardBus bridge: Texas Instruments PCI1620 PC Card Controller (rev 01)
> 02:04.2 System peripheral: Texas Instruments PCI1620 Firmware Loading Function (rev 01)
> 
> [    0.000000] Linux version 2.6.21-rc4-mm1 (root@zephyr) (gcc version 4.2.0-alpha20070307 (prerelease) (Gentoo 4.2.0_alpha20070307)) #1 SMP PREEMPT Tue Mar 20 14:25:42 MDT 2007
> [    0.000000] Command line: root=/dev/sda2 rootfstype=reiser4 ro i8042.nomux elevator=cfq resume=/dev/sda3 single
> [    0.000000] BIOS-provided physical RAM map:
> [    0.000000]  BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
> [    0.000000]  BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
> [    0.000000]  BIOS-e820: 00000000000d0000 - 0000000000100000 (reserved)
> [    0.000000]  BIOS-e820: 0000000000100000 - 000000003ff70000 (usable)
> [    0.000000]  BIOS-e820: 000000003ff70000 - 000000003ff7f000 (ACPI data)
> [    0.000000]  BIOS-e820: 000000003ff7f000 - 000000003ff80000 (ACPI NVS)
> [    0.000000]  BIOS-e820: 000000003ff80000 - 0000000040000000 (reserved)
> [    0.000000]  BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
> [    0.000000] Entering add_active_range(0, 0, 159) 0 entries of 256 used
> [    0.000000] Entering add_active_range(0, 256, 262000) 1 entries of 256 used
> [    0.000000] end_pfn_map = 1048576
> [    0.000000] DMI present.
> [    0.000000] ACPI: RSDP 000F7240, 0014 (r0 PTLTD )
> [    0.000000] ACPI: RSDT 3FF7A87E, 0034 (r1 PTLTD    RSDT    6040000  LTP        0)
> [    0.000000] ACPI: FACP 3FF7EE13, 0074 (r1 NVIDIA CK8       6040000 PTL_    F4240)
> [    0.000000] ACPI: DSDT 3FF7A8B2, 4561 (r1 NVIDIA      CK8  6040000 MSFT  100000E)
> [    0.000000] ACPI: FACS 3FF7FFC0, 0040
> [    0.000000] ACPI: APIC 3FF7EE87, 005A (r1 NVIDIA NV_APIC_  6040000  LTP        0)
> [    0.000000] ACPI: BOOT 3FF7EEE1, 0028 (r1 PTLTD  $SBFTBL$  6040000  LTP        1)
> [    0.000000] ACPI: SSDT 3FF7EF09, 00F7 (r1 PTLTD  POWERNOW  6040000  LTP        1)
> [    0.000000] Entering add_active_range(0, 0, 159) 0 entries of 256 used
> [    0.000000] Entering add_active_range(0, 256, 262000) 1 entries of 256 used
> [    0.000000] No mptable found.
> [    0.000000] sizeof(struct page) = 88
> [    0.000000] Zone PFN ranges:
> [    0.000000]   DMA             0 ->     4096
> [    0.000000]   DMA32        4096 ->  1048576
> [    0.000000]   Normal    1048576 ->  1048576
> [    0.000000] Movable zone start PFN for each node
> [    0.000000] early_node_map[2] active PFN ranges
> [    0.000000]     0:        0 ->      159
> [    0.000000]     0:      256 ->   262000
> [    0.000000] On node 0 totalpages: 261903
> [    0.000000] Node 0 memmap at 0xffff810001000000 size 23068672 first pfn 0xffff810001000000
> [    0.000000]   DMA zone: 88 pages used for memmap
> [    0.000000]   DMA zone: 2335 pages reserved
> [    0.000000]   DMA zone: 1576 pages, LIFO batch:0
> [    0.000000]   DMA32 zone: 5540 pages used for memmap
> [    0.000000]   DMA32 zone: 252364 pages, LIFO batch:31
> [    0.000000]   Normal zone: 0 pages used for memmap
> [    0.000000]   Movable zone: 0 pages used for memmap
> [    0.000000] Nvidia board detected. Ignoring ACPI timer override.
> [    0.000000] If you got timer trouble try acpi_use_timer_override
> [    0.000000] ACPI: PM-Timer IO Port: 0x8008
> [    0.000000] ACPI: Local APIC address 0xfee00000
> [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
> [    0.000000] Processor #0 (Bootup-CPU)
> [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
> [    0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
> [    0.000000] IOAPIC[0]: apic_id 2, address 0xfec00000, GSI 0-23
> [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
> [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
> [    0.000000] ACPI: BIOS IRQ0 pin2 override ignored.
> [    0.000000] ACPI: IRQ9 used by override.
> [    0.000000] Setting APIC routing to flat
> [    0.000000] Using ACPI (MADT) for SMP configuration information
> [    0.000000] Nosave address range: 000000000009f000 - 00000000000a0000
> [    0.000000] Nosave address range: 00000000000a0000 - 00000000000d0000
> [    0.000000] Nosave address range: 00000000000d0000 - 0000000000100000
> [    0.000000] Allocating PCI resources starting at 50000000 (gap: 40000000:bff80000)
> [    0.000000] SMP: Allowing 1 CPUs, 0 hotplug CPUs
> [    0.000000] PERCPU: Allocating 37312 bytes of per cpu data
> [    0.000000] Built 1 zonelists.  Total pages: 253940
> [    0.000000] Kernel command line: root=/dev/sda2 rootfstype=reiser4 ro i8042.nomux elevator=cfq resume=/dev/sda3 single
> [    0.000000] Initializing CPU#0
> [    0.000000] PID hash table entries: 4096 (order: 12, 32768 bytes)
> [   17.397762] time.c: Detected 2194.378 MHz processor.
> [   17.399354] Console: colour VGA+ 80x25
> [   17.402298] Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar
> [   17.402371] ... MAX_LOCKDEP_SUBCLASSES:    8
> [   17.402423] ... MAX_LOCK_DEPTH:          30
> [   17.402476] ... MAX_LOCKDEP_KEYS:        2048
> [   17.402528] ... CLASSHASH_SIZE:           1024
> [   17.402581] ... MAX_LOCKDEP_ENTRIES:     8192
> [   17.402633] ... MAX_LOCKDEP_CHAINS:      16384
> [   17.402685] ... CHAINHASH_SIZE:          8192
> [   17.402744]  memory used by lock dependency info: 1648 kB
> [   17.402798]  per task-struct memory footprint: 1680 bytes
> [   17.402853] ------------------------
> [   17.402903] | Locking API testsuite:
> [   17.402954] ----------------------------------------------------------------------------
> [   17.403028]                                  | spin |wlock |rlock |mutex | wsem | rsem |
> [   17.403101]   --------------------------------------------------------------------------
> [   17.403179]                      A-A deadlock:  ok  |  ok  |  ok  |  ok  |  ok  |  ok  |
> [   17.404370]                  A-B-B-A deadlock:  ok  |  ok  |  ok  |  ok  |  ok  |  ok  |
> [   17.405486]              A-B-B-C-C-A deadlock:  ok  |  ok  |  ok  |  ok  |  ok  |  ok  |
> [   17.406652]              A-B-C-A-B-C deadlock:  ok  |  ok  |  ok  |  ok  |  ok  |  ok  |
> [   17.407826]          A-B-B-C-C-D-D-A deadlock:  ok  |  ok  |  ok  |  ok  |  ok  |  ok  |
> [   17.409052]          A-B-C-D-B-D-D-A deadlock:  ok  |  ok  |  ok  |  ok  |  ok  |  ok  |
> [   17.410280]          A-B-C-D-B-C-D-A deadlock:  ok  |  ok  |  ok  |  ok  |  ok  |  ok  |
> [   17.411514]                     double unlock:  ok  |  ok  |  ok  |  ok  |  ok  |  ok  |
> [   17.412580]                   initialize held:  ok  |  ok  |  ok  |  ok  |  ok  |  ok  |
> [   17.413647]                  bad unlock order:  ok  |  ok  |  ok  |  ok  |  ok  |  ok  |
> [   17.414777]   --------------------------------------------------------------------------
> [   17.414851]               recursive read-lock:             |  ok  |             |  ok  |
> [   17.415334]            recursive read-lock #2:             |  ok  |             |  ok  |
> [   17.415824]             mixed read-write-lock:             |  ok  |             |  ok  |
> [   17.416312]             mixed write-read-lock:             |  ok  |             |  ok  |
> [   17.416807]   --------------------------------------------------------------------------
> [   17.416880]      hard-irqs-on + irq-safe-A/12:  ok  |  ok  |  ok  |
> [   17.417444]      soft-irqs-on + irq-safe-A/12:  ok  |  ok  |  ok  |
> [   17.418018]      hard-irqs-on + irq-safe-A/21:  ok  |  ok  |  ok  |
> [   17.418583]      soft-irqs-on + irq-safe-A/21:  ok  |  ok  |  ok  |
> [   17.419156]        sirq-safe-A => hirqs-on/12:  ok  |  ok  |  ok  |
> [   17.419730]        sirq-safe-A => hirqs-on/21:  ok  |  ok  |  ok  |
> [   17.420294]          hard-safe-A + irqs-on/12:  ok  |  ok  |  ok  |
> [   17.420865]          soft-safe-A + irqs-on/12:  ok  |  ok  |  ok  |
> [   17.421432]          hard-safe-A + irqs-on/21:  ok  |  ok  |  ok  |
> [   17.422003]          soft-safe-A + irqs-on/21:  ok  |  ok  |  ok  |
> [   17.422568]     hard-safe-A + unsafe-B #1/123:  ok  |  ok  |  ok  |
> [   17.423164]     soft-safe-A + unsafe-B #1/123:  ok  |  ok  |  ok  |
> [   17.423759]     hard-safe-A + unsafe-B #1/132:  ok  |  ok  |  ok  |
> [   17.424347]     soft-safe-A + unsafe-B #1/132:  ok  |  ok  |  ok  |
> [   17.424943]     hard-safe-A + unsafe-B #1/213:  ok  |  ok  |  ok  |
> [   17.425530]     soft-safe-A + unsafe-B #1/213:  ok  |  ok  |  ok  |
> [   17.426126]     hard-safe-A + unsafe-B #1/231:  ok  |  ok  |  ok  |
> [   17.426713]     soft-safe-A + unsafe-B #1/231:  ok  |  ok  |  ok  |
> [   17.427296]     hard-safe-A + unsafe-B #1/312:  ok  |  ok  |  ok  |
> [   17.427874]     soft-safe-A + unsafe-B #1/312:  ok  |  ok  |  ok  |
> [   17.428446]     hard-safe-A + unsafe-B #1/321:  ok  |  ok  |  ok  |
> [   17.429035]     soft-safe-A + unsafe-B #1/321:  ok  |  ok  |  ok  |
> [   17.429618]     hard-safe-A + unsafe-B #2/123:  ok  |  ok  |  ok  |
> [   17.430205]     soft-safe-A + unsafe-B #2/123:  ok  |  ok  |  ok  |
> [   17.430798]     hard-safe-A + unsafe-B #2/132:  ok  |  ok  |  ok  |
> [   17.431376]     soft-safe-A + unsafe-B #2/132:  ok  |  ok  |  ok  |
> [   17.431969]     hard-safe-A + unsafe-B #2/213:  ok  |  ok  |  ok  |
> [   17.432550]     soft-safe-A + unsafe-B #2/213:  ok  |  ok  |  ok  |
> [   17.433143]     hard-safe-A + unsafe-B #2/231:  ok  |  ok  |  ok  |
> [   17.433726]     soft-safe-A + unsafe-B #2/231:  ok  |  ok  |  ok  |
> [   17.434307]     hard-safe-A + unsafe-B #2/312:  ok  |  ok  |  ok  |
> [   17.434894]     soft-safe-A + unsafe-B #2/312:  ok  |  ok  |  ok  |
> [   17.435479]     hard-safe-A + unsafe-B #2/321:  ok  |  ok  |  ok  |
> [   17.436063]     soft-safe-A + unsafe-B #2/321:  ok  |  ok  |  ok  |
> [   17.436647]       hard-irq lock-inversion/123:  ok  |  ok  |  ok  |
> [   17.437237]       soft-irq lock-inversion/123:  ok  |  ok  |  ok  |
> [   17.437831]       hard-irq lock-inversion/132:  ok  |  ok  |  ok  |
> [   17.438410]       soft-irq lock-inversion/132:  ok  |  ok  |  ok  |
> [   17.439004]       hard-irq lock-inversion/213:  ok  |  ok  |  ok  |
> [   17.439586]       soft-irq lock-inversion/213:  ok  |  ok  |  ok  |
> [   17.440180]       hard-irq lock-inversion/231:  ok  |  ok  |  ok  |
> [   17.440765]       soft-irq lock-inversion/231:  ok  |  ok  |  ok  |
> [   17.441347]       hard-irq lock-inversion/312:  ok  |  ok  |  ok  |
> [   17.441934]       soft-irq lock-inversion/312:  ok  |  ok  |  ok  |
> [   17.442520]       hard-irq lock-inversion/321:  ok  |  ok  |  ok  |
> [   17.443105]       soft-irq lock-inversion/321:  ok  |  ok  |  ok  |
> [   17.443694]       hard-irq read-recursion/123:  ok  |
> [   17.443943]       soft-irq read-recursion/123:  ok  |
> [   17.444193]       hard-irq read-recursion/132:  ok  |
> [   17.444441]       soft-irq read-recursion/132:  ok  |
> [   17.444700]       hard-irq read-recursion/213:  ok  |
> [   17.444949]       soft-irq read-recursion/213:  ok  |
> [   17.445199]       hard-irq read-recursion/231:  ok  |
> [   17.445448]       soft-irq read-recursion/231:  ok  |
> [   17.445707]       hard-irq read-recursion/312:  ok  |
> [   17.445956]       soft-irq read-recursion/312:  ok  |
> [   17.446206]       hard-irq read-recursion/321:  ok  |
> [   17.446454]       soft-irq read-recursion/321:  ok  |
> [   17.446711] -------------------------------------------------------
> [   17.446767] Good, all 218 testcases passed! |
> [   17.446820] ---------------------------------
> [   17.447871] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
> [   17.448711] Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
> [   17.448901] Checking aperture...
> [   17.448953] CPU 0: aperture @ e8000000 size 128 MB
> [   17.470739] Memory: 1013752k/1048000k available (3200k kernel code, 33568k reserved, 1519k data, 212k init)
> [   17.530543] Calibrating delay using timer specific routine.. 4390.56 BogoMIPS (lpj=2195280)
> [   17.530799] Mount-cache hash table entries: 256
> [   17.531328] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
> [   17.531387] CPU: L2 Cache: 1024K (64 bytes/line)
> [   17.531462] SMP alternatives: switching to UP code
> [   17.531743] Freeing SMP alternatives: 28k freed
> [   17.531816] ACPI: Core revision 20070126
> [   17.536624] Parsing all Control Methods:
> [   17.536769] Table [DSDT](id 0001) - 650 Objects with 66 Devices 205 Methods 24 Regions
> [   17.538016] Parsing all Control Methods:
> [   17.538146] Table [SSDT](id 0002) - 3 Objects with 0 Devices 1 Methods 0 Regions
> [   17.538263]  tbxface-0587 [02] tb_load_namespace     : ACPI Tables successfully acquired
> [   17.558729] evxfevnt-0091 [02] enable                : Transition to ACPI mode successful
> [   17.569330] Using local APIC timer interrupts.
> [   17.614892] result 12468058
> [   17.614942] Detected 12.468 MHz APIC timer.
> [   17.615526] Brought up 1 CPUs
> [   17.615800] PM: Adding info for No Bus:platform
> [   17.616047] NET: Registered protocol family 16
> [   17.616280] No dock devices found.
> [   17.616370] PM: Adding info for No Bus:vtcon0
> [   17.616570] ACPI: bus type pci registered
> [   17.616634] PCI: Using configuration type 1
> [   17.618818] evgpeblk-0952 [04] ev_create_gpe_block   : GPE 00 to 1F [_GPE] 4 regs on int 0x9
> [   17.618981] evgpeblk-0952 [04] ev_create_gpe_block   : GPE 20 to 5F [_GPE] 8 regs on int 0x9
> [   17.619507] evgpeblk-1049 [03] ev_initialize_gpe_bloc: Found 5 Wake, Enabled 1 Runtime GPEs in this block
> [   17.619786] evgpeblk-1049 [03] ev_initialize_gpe_bloc: Found 0 Wake, Enabled 1 Runtime GPEs in this block
> [   17.620361] Completing Region/Field/Buffer/Package initialization:.....................................................................
> [   17.624273] Initialized 24/24 Regions 2/2 Fields 29/29 Buffers 14/21 Packages (662 nodes)
> [   17.624393] Initializing Device/Processor/Thermal objects by executing _INI methods:.
> [   17.624561] Executed 1 _INI methods requiring 0 _STA executions (examined 70 objects)
> [   17.624693] ACPI: Interpreter enabled
> [   17.624745] ACPI: (supports S0 S3 S4 S5)
> [   17.624983] ACPI: Using IOAPIC for interrupt routing
> [   17.625149] PM: Adding info for acpi:acpi_system:00
> [   17.625225] PM: Adding info for acpi:button_power:00
> [   17.625289] PM: Adding info for acpi:ACPI0007:00
> [   17.625374] PM: Adding info for acpi:device:00
> [   17.625455] PM: Adding info for acpi:pnp0c14:00
> [   17.625608] PM: Adding info for acpi:PNP0C0C:00
> [   17.625690] PM: Adding info for acpi:PNP0C0D:00
> [   17.625774] PM: Adding info for acpi:PNP0A03:00
> [   17.625928] PM: Adding info for acpi:device:01
> [   17.626084] PM: Adding info for acpi:device:02
> [   17.626170] PM: Adding info for acpi:device:03
> [   17.626256] PM: Adding info for acpi:device:04
> [   17.626338] PM: Adding info for acpi:device:05
> [   17.626447] PM: Adding info for acpi:device:06
> [   17.626525] PM: Adding info for acpi:device:07
> [   17.626610] PM: Adding info for acpi:device:08
> [   17.626686] PM: Adding info for acpi:device:09
> [   17.626768] PM: Adding info for acpi:device:0a
> [   17.626847] PM: Adding info for acpi:device:0b
> [   17.626934] PM: Adding info for acpi:device:0c
> [   17.627011] PM: Adding info for acpi:device:0d
> [   17.627094] PM: Adding info for acpi:device:0e
> [   17.627176] PM: Adding info for acpi:device:0f
> [   17.627258] PM: Adding info for acpi:device:10
> [   17.627336] PM: Adding info for acpi:device:11
> [   17.627427] PM: Adding info for acpi:device:12
> [   17.627506] PM: Adding info for acpi:device:13
> [   17.627590] PM: Adding info for acpi:device:14
> [   17.627672] PM: Adding info for acpi:device:15
> [   17.627753] PM: Adding info for acpi:ACPI0003:00
> [   17.627832] PM: Adding info for acpi:PNP0C02:00
> [   17.627913] PM: Adding info for acpi:PNP0C01:00
> [   17.628002] PM: Adding info for acpi:PNP0C09:00
> [   17.667388] PM: Adding info for acpi:PNP0C0A:00
> [   17.667474] PM: Adding info for acpi:PNP0C02:01
> [   17.667555] PM: Adding info for acpi:PNP0000:00
> [   17.667629] PM: Adding info for acpi:PNP0100:00
> [   17.667708] PM: Adding info for acpi:PNP0200:00
> [   17.667782] PM: Adding info for acpi:PNP0800:00
> [   17.667862] PM: Adding info for acpi:PNP0B00:00
> [   17.667936] PM: Adding info for acpi:PNP0C04:00
> [   17.668093] PM: Adding info for acpi:PNP0303:00
> [   17.668243] PM: Adding info for acpi:PNP0F13:00
> [   17.668330] PM: Adding info for acpi:PNP0A05:00
> [   17.668800] PM: Adding info for acpi:PNP0700:00
> [   17.673598] PM: Adding info for acpi:PNP0401:00
> [   17.673814] PM: Adding info for acpi:device:16
> [   17.673974] PM: Adding info for acpi:device:17
> [   17.674122] PM: Adding info for acpi:device:18
> [   17.674287] PM: Adding info for acpi:video:00
> [   17.674407] PM: Adding info for acpi:device:19
> [   17.674526] PM: Adding info for acpi:device:1a
> [   17.674640] PM: Adding info for acpi:device:1b
> [   17.675014] PM: Adding info for acpi:PNP0C0F:00
> [   17.675187] PM: Adding info for acpi:PNP0C0F:01
> [   17.675371] PM: Adding info for acpi:PNP0C0F:02
> [   17.675544] PM: Adding info for acpi:PNP0C0F:03
> [   17.675724] PM: Adding info for acpi:PNP0C0F:04
> [   17.675894] PM: Adding info for acpi:PNP0C0F:05
> [   17.676072] PM: Adding info for acpi:PNP0C0F:06
> [   17.676245] PM: Adding info for acpi:PNP0C0F:07
> [   17.676430] PM: Adding info for acpi:PNP0C0F:08
> [   17.676616] PM: Adding info for acpi:PNP0C0F:09
> [   17.676795] PM: Adding info for acpi:PNP0C0F:0a
> [   17.676968] PM: Adding info for acpi:PNP0C0F:0b
> [   17.677150] PM: Adding info for acpi:PNP0C0F:0c
> [   17.677354] PM: Adding info for acpi:PNP0C0F:0d
> [   17.677428] PM: Adding info for acpi:thermal:00
> [   17.677487] PM: Adding info for acpi:thermal:01
> [   17.677838] ACPI: PCI Root Bridge [PCI0] (0000:00)
> [   17.677936] PM: Adding info for No Bus:pci0000:00
> [   17.678314] 0000:00:08.0: cannot adjust BAR0 (not I/O)
> [   17.678371] 0000:00:08.0: cannot adjust BAR1 (not I/O)
> [   17.678427] 0000:00:08.0: cannot adjust BAR2 (not I/O)
> [   17.678481] 0000:00:08.0: cannot adjust BAR3 (not I/O)
> [   17.679034] PCI: Bus #03 (-#06) is hidden behind  bridge #02 (-#02) (try 'pci=assign-busses')
> [   17.679109] Please report the result to linux-kernel to fix this permanently
> [   17.679229] PCI: Bus #07 (-#0a) is hidden behind  bridge #02 (-#02) (try 'pci=assign-busses')
> [   17.679304] Please report the result to linux-kernel to fix this permanently
> [   17.679476] Boot video device is 0000:01:00.0
> [   17.679535] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
> [   17.679678] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P2P0._PRT]
> [   17.679749] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGP0._PRT]
> [   17.680943] PM: Adding info for pci:0000:00:00.0
> [   17.682179] PM: Adding info for pci:0000:00:01.0
> [   17.683404] PM: Adding info for pci:0000:00:01.1
> [   17.684622] PM: Adding info for pci:0000:00:02.0
> [   17.685836] PM: Adding info for pci:0000:00:02.1
> [   17.687056] PM: Adding info for pci:0000:00:02.2
> [   17.688272] PM: Adding info for pci:0000:00:06.0
> [   17.689498] PM: Adding info for pci:0000:00:06.1
> [   17.690712] PM: Adding info for pci:0000:00:08.0
> [   17.691935] PM: Adding info for pci:0000:00:0a.0
> [   17.693149] PM: Adding info for pci:0000:00:0b.0
> [   17.694382] PM: Adding info for pci:0000:00:18.0
> [   17.695596] PM: Adding info for pci:0000:00:18.1
> [   17.696821] PM: Adding info for pci:0000:00:18.2
> [   17.698035] PM: Adding info for pci:0000:00:18.3
> [   17.698147] PM: Adding info for pci:0000:02:00.0
> [   17.698253] PM: Adding info for pci:0000:02:01.0
> [   17.698373] PM: Adding info for pci:0000:02:02.0
> [   17.698479] PM: Adding info for pci:0000:02:04.0
> [   17.698590] PM: Adding info for pci:0000:02:04.1
> [   17.698697] PM: Adding info for pci:0000:02:04.2
> [   17.698814] PM: Adding info for pci:0000:01:00.0
> [   17.699206] ACPI: PCI Interrupt Link [LNK1] (IRQs 16 18 19) *0
> [   17.699725] ACPI: PCI Interrupt Link [LNK2] (IRQs 16 18 19) *0
> [   17.700246] ACPI: PCI Interrupt Link [LNK3] (IRQs 17) *0
> [   17.700706] ACPI: PCI Interrupt Link [LNK4] (IRQs 16 18 19) *0, disabled.
> [   17.701249] ACPI: PCI Interrupt Link [LNK5] (IRQs 16 18 19) *0
> [   17.701754] ACPI: PCI Interrupt Link [LSMB] (IRQs 20 21 22) *0
> [   17.702253] ACPI: PCI Interrupt Link [LUS0] (IRQs 20 21 22) *0
> [   17.702761] ACPI: PCI Interrupt Link [LUS1] (IRQs 20 21 22) *0
> [   17.703260] ACPI: PCI Interrupt Link [LUS2] (IRQs 20 21 22) *0
> [   17.703775] ACPI: PCI Interrupt Link [LMAC] (IRQs 20 21 22) *0, disabled.
> [   17.704311] ACPI: PCI Interrupt Link [LACI] (IRQs 20 21 22) *0
> [   17.704816] ACPI: PCI Interrupt Link [LMCI] (IRQs 20 21 22) *0
> [   17.705333] ACPI: PCI Interrupt Link [LPID] (IRQs 20 21 22) *0, disabled.
> [   17.705879] ACPI: PCI Interrupt Link [LTID] (IRQs 20 21 22) *0, disabled.
> [   17.706254] Linux Plug and Play Support v0.97 (c) Adam Belay
> [   17.706334] pnp: PnP ACPI init
> [   17.706401] PM: Adding info for No Bus:pnp0
> [   17.706597] PM: Adding info for pnp:00:00
> [   17.707281] PM: Adding info for pnp:00:01
> [   17.707475] PM: Adding info for pnp:00:02
> [   17.728319] PM: Adding info for pnp:00:03
> [   17.728404] PM: Adding info for pnp:00:04
> [   17.728465] PM: Adding info for pnp:00:05
> [   17.728541] PM: Adding info for pnp:00:06
> [   17.728606] PM: Adding info for pnp:00:07
> [   17.728716] PM: Adding info for pnp:00:08
> [   17.728822] PM: Adding info for pnp:00:09
> [   17.729092] PM: Adding info for pnp:00:0a
> [   17.731090] PM: Adding info for pnp:00:0b
> [   17.732020] pnp: PnP ACPI: found 12 devices
> [   17.732153] Generic PHY: Registered new driver
> [   17.732403] SCSI subsystem initialized
> [   17.732504] libata version 2.20 loaded.
> [   17.732614] PCI: Using ACPI for IRQ routing
> [   17.732668] PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
> [   17.732752] PCI: Cannot allocate resource region 0 of device 0000:00:00.0
> [   17.733015] agpgart: Detected AGP bridge 0
> [   17.733072] agpgart: Setting up Nforce3 AGP.
> [   17.737586] PM: Adding info for No Bus:agpgart
> [   17.737683] agpgart: AGP aperture is 128M @ 0xe8000000
> [   17.737871] pnp: 00:01: ioport range 0x8000-0x807f has been reserved
> [   17.737929] pnp: 00:01: ioport range 0x8080-0x80ff has been reserved
> [   17.737986] pnp: 00:01: ioport range 0x8400-0x847f has been reserved
> [   17.738044] pnp: 00:01: ioport range 0x8480-0x84ff has been reserved
> [   17.738101] pnp: 00:01: ioport range 0x8800-0x887f has been reserved
> [   17.738158] pnp: 00:01: ioport range 0x8880-0x88ff has been reserved
> [   17.738216] Time: tsc clocksource has been installed.
> [   17.738275] pnp: 00:01: ioport range 0x2040-0x207f has been reserved
> [   17.738332] pnp: 00:01: ioport range 0x2000-0x203f has been reserved
> [   17.738396] pnp: 00:02: iomem range 0xfff80000-0xffffffff has been reserved
> [   17.738455] pnp: 00:02: iomem range 0xfec00000-0xfec00fff has been reserved
> [   17.738514] pnp: 00:02: iomem range 0xfee00000-0xfeefffff has been reserved
> [   17.738572] pnp: 00:02: iomem range 0xfed00000-0xfed00fff has been reserved
> [   17.738673] PM: Adding info for No Bus:mem
> [   17.738725] PM: Adding info for No Bus:kmem
> [   17.738768] PM: Adding info for No Bus:null
> [   17.738816] PM: Adding info for No Bus:port
> [   17.738858] PM: Adding info for No Bus:zero
> [   17.738905] PM: Adding info for No Bus:full
> [   17.738947] PM: Adding info for No Bus:random
> [   17.738997] PM: Adding info for No Bus:urandom
> [   17.739039] PM: Adding info for No Bus:kmsg
> [   17.739158] PCI: Failed to allocate mem resource #10:4000000@e4000000 for 0000:02:04.0
> [   17.739235] PCI: Failed to allocate mem resource #10:4000000@e4000000 for 0000:02:04.1
> [   17.739313] PCI: Bus 3, cardbus bridge: 0000:02:04.0
> [   17.739367]   IO window: 00003000-000030ff
> [   17.739421]   IO window: 00003400-000034ff
> [   17.739476]   PREFETCH window: 50000000-53ffffff
> [   17.739531] PCI: Bus 7, cardbus bridge: 0000:02:04.1
> [   17.739585]   IO window: 00003800-000038ff
> [   17.739639]   IO window: 00003c00-00003cff
> [   17.739693]   PREFETCH window: 54000000-57ffffff
> [   17.739748] PCI: Bridge: 0000:00:0a.0
> [   17.739800]   IO window: 3000-7fff
> [   17.739853]   MEM window: e0100000-e17fffff
> [   17.739906]   PREFETCH window: 50000000-57ffffff
> [   17.739962] PCI: Bridge: 0000:00:0b.0
> [   17.740013]   IO window: disabled.
> [   17.740067]   MEM window: e2000000-e2ffffff
> [   17.740121]   PREFETCH window: f0000000-f80fffff
> [   17.740183] PCI: Setting latency timer of device 0000:00:0a.0 to 64
> [   17.740708] ACPI: PCI Interrupt Link [LNK1] enabled at IRQ 19
> [   17.740772] ACPI: PCI Interrupt 0000:02:04.0[A] -> Link [LNK1] -> GSI 19 (level, low) -> IRQ 19
> [   17.741334] ACPI: PCI Interrupt Link [LNK2] enabled at IRQ 18
> [   17.741394] ACPI: PCI Interrupt 0000:02:04.1[B] -> Link [LNK2] -> GSI 18 (level, low) -> IRQ 18
> [   17.741573] NET: Registered protocol family 2
> [   17.751310] IP route cache hash table entries: 32768 (order: 6, 262144 bytes)
> [   17.751620] TCP established hash table entries: 65536 (order: 10, 4194304 bytes)
> [   17.757500] TCP bind hash table entries: 65536 (order: 9, 3670016 bytes)
> [   17.762325] TCP: Hash tables configured (established 65536 bind 65536)
> [   17.762418] TCP reno registered
> [   17.765663] Simple Boot Flag at 0x37 set to 0x1
> [   17.765831] PM: Adding info for No Bus:mcelog
> [   17.765911] PM: Adding info for No Bus:msr0
> [   17.765974] PM: Adding info for No Bus:cpu0
> [   17.766279] PM: Adding info for platform:pcspkr
> [   17.766553] PM: Adding info for No Bus:snapshot
> [   17.766602] audit: initializing netlink socket (disabled)
> [   17.766677] audit(1174429488.298:1): initialized
> [   17.766920] Total HugeTLB memory allocated, 0
> [   17.767309] Loading Reiser4. See www.namesys.com for a description of Reiser4.
> [   17.767640] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
> [   17.768058] io scheduler noop registered
> [   17.768111] io scheduler anticipatory registered
> [   17.768164] io scheduler deadline registered
> [   17.768257] io scheduler cfq registered (default)
> [   17.769736] ACPI: AC Adapter [ACAD] (on-line)
> [   17.791230] ACPI: Battery Slot [BAT1] (battery present)
> [   17.791428] input: Power Button (FF) as /class/input/input0
> [   17.791490] ACPI: Power Button (FF) [PWRF]
> [   17.791611] input: Power Button (CM) as /class/input/input1
> [   17.791667] ACPI: Power Button (CM) [PWRB]
> [   17.791799] input: Lid Switch as /class/input/input2
> [   17.791854] ACPI: Lid Switch [LID]
> [   17.792327] ACPI: Video Device [VGA] (multi-head: yes  rom: no  post: no)
> [   17.793720] ACPI: CPU0 (power states: C1[C1] C2[C2])
> [   17.793997] cpuidle: using driver acpi_idle
> [   17.825473] ACPI Exception (thermal-0412): AE_NOT_FOUND, Invalid active threshold [0] [20070126]
> [   17.828471] ACPI: Thermal Zone [THRM] (62 C)
> [   17.828571] PM: Adding info for No Bus:tty
> [   17.828615] PM: Adding info for No Bus:console
> [   17.828663] PM: Adding info for No Bus:ptmx
> [   17.828702] PM: Adding info for No Bus:tty0
> [   17.828765] PM: Adding info for No Bus:vcs
> [   17.828811] PM: Adding info for No Bus:vcsa
> [   17.828858] PM: Adding info for No Bus:tty1
> [   17.828908] PM: Adding info for No Bus:tty2
> [   17.828949] PM: Adding info for No Bus:tty3
> [   17.828996] PM: Adding info for No Bus:tty4
> [   17.829035] PM: Adding info for No Bus:tty5
> [   17.829089] PM: Adding info for No Bus:tty6
> [   17.829132] PM: Adding info for No Bus:tty7
> [   17.829183] PM: Adding info for No Bus:tty8
> [   17.829228] PM: Adding info for No Bus:tty9
> [   17.829280] PM: Adding info for No Bus:tty10
> [   17.829323] PM: Adding info for No Bus:tty11
> [   17.829374] PM: Adding info for No Bus:tty12
> [   17.829418] PM: Adding info for No Bus:tty13
> [   17.829474] PM: Adding info for No Bus:tty14
> [   17.829518] PM: Adding info for No Bus:tty15
> [   17.829570] PM: Adding info for No Bus:tty16
> [   17.829614] PM: Adding info for No Bus:tty17
> [   17.829667] PM: Adding info for No Bus:tty18
> [   17.829713] PM: Adding info for No Bus:tty19
> [   17.829767] PM: Adding info for No Bus:tty20
> [   17.829820] PM: Adding info for No Bus:tty21
> [   17.829874] PM: Adding info for No Bus:tty22
> [   17.829922] PM: Adding info for No Bus:tty23
> [   17.829976] PM: Adding info for No Bus:tty24
> [   17.830024] PM: Adding info for No Bus:tty25
> [   17.830083] PM: Adding info for No Bus:tty26
> [   17.830130] PM: Adding info for No Bus:tty27
> [   17.830185] PM: Adding info for No Bus:tty28
> [   17.830230] PM: Adding info for No Bus:tty29
> [   17.830286] PM: Adding info for No Bus:tty30
> [   17.830332] PM: Adding info for No Bus:tty31
> [   17.830387] PM: Adding info for No Bus:tty32
> [   17.830433] PM: Adding info for No Bus:tty33
> [   17.830489] PM: Adding info for No Bus:tty34
> [   17.830540] PM: Adding info for No Bus:tty35
> [   17.830600] PM: Adding info for No Bus:tty36
> [   17.830647] PM: Adding info for No Bus:tty37
> [   17.830705] PM: Adding info for No Bus:tty38
> [   17.830751] PM: Adding info for No Bus:tty39
> [   17.830807] PM: Adding info for No Bus:tty40
> [   17.830855] PM: Adding info for No Bus:tty41
> [   17.830912] PM: Adding info for No Bus:tty42
> [   17.830960] PM: Adding info for No Bus:tty43
> [   17.831015] PM: Adding info for No Bus:tty44
> [   17.831063] PM: Adding info for No Bus:tty45
> [   17.831138] PM: Adding info for No Bus:tty46
> [   17.831181] PM: Adding info for No Bus:tty47
> [   17.831235] PM: Adding info for No Bus:tty48
> [   17.831280] PM: Adding info for No Bus:tty49
> [   17.831334] PM: Adding info for No Bus:tty50
> [   17.831378] PM: Adding info for No Bus:tty51
> [   17.831429] PM: Adding info for No Bus:tty52
> [   17.831474] PM: Adding info for No Bus:tty53
> [   17.831527] PM: Adding info for No Bus:tty54
> [   17.831574] PM: Adding info for No Bus:tty55
> [   17.831633] PM: Adding info for No Bus:tty56
> [   17.831683] PM: Adding info for No Bus:tty57
> [   17.831740] PM: Adding info for No Bus:tty58
> [   17.831787] PM: Adding info for No Bus:tty59
> [   17.831844] PM: Adding info for No Bus:tty60
> [   17.831893] PM: Adding info for No Bus:tty61
> [   17.831952] PM: Adding info for No Bus:tty62
> [   17.832002] PM: Adding info for No Bus:tty63
> [   17.832160] PM: Adding info for No Bus:rtc
> [   17.832208] Real Time Clock Driver v1.12ac
> [   17.832270] PM: Adding info for No Bus:hpet
> [   17.832420] PM: Adding info for No Bus:watchdog
> [   17.832457] Software Watchdog Timer: 0.07 initialized. soft_noboot=0 soft_margin=60 sec (nowayout= 0)
> [   17.832534] Linux agpgart interface v0.102 (c) Dave Jones
> [   17.832589] Hangcheck: starting hangcheck timer 0.9.0 (tick is 180 seconds, margin is 60 seconds).
> [   17.832664] Hangcheck: Using get_cycles().
> [   17.833305] loop: loaded (max 8 devices)
> [   17.833391] Marvell 88E1101: Registered new driver
> [   17.833475] Marvell 88E1111: Registered new driver
> [   17.833560] Marvell 88E1145: Registered new driver
> [   17.833652] Davicom DM9161E: Registered new driver
> [   17.833736] Davicom DM9131: Registered new driver
> [   17.833821] Cicada Cis8204: Registered new driver
> [   17.833905] Cicada Cis8201: Registered new driver
> [   17.833997] LXT970: Registered new driver
> [   17.834087] LXT971: Registered new driver
> [   17.834171] QS6612: Registered new driver
> [   17.834254] SMSC LAN83C185: Registered new driver
> [   17.834402] PM: Adding info for No Bus:lo
> [   17.834607] 8139too Fast Ethernet driver 0.9.28
> [   17.834685] ACPI: PCI Interrupt 0000:02:01.0[A] -> Link [LNK2] -> GSI 18 (level, low) -> IRQ 18
> [   17.835148] PM: Adding info for No Bus:eth0
> [   17.835216] eth0: RealTek RTL8139 at 0xffffc20000018800, 00:0f:b0:07:dc:49, IRQ 18
> [   17.835290] eth0:  Identified 8139 chip type 'RTL-8101'
> [   17.835500] pata_amd 0000:00:08.0: version 0.3.8
> [   17.835526] PCI: Setting latency timer of device 0000:00:08.0 to 64
> [   17.835636] ata1: PATA max UDMA/133 cmd 0x00000000000101f0 ctl 0x00000000000103f6 bmdma 0x0000000000012080 irq 14
> [   17.835753] ata2: PATA max UDMA/133 cmd 0x0000000000010170 ctl 0x0000000000010376 bmdma 0x0000000000012088 irq 15
> [   17.835848] scsi0 : pata_amd
> [   17.835912] PM: Adding info for No Bus:host0
> [   17.990015] ata1.00: ATA-6: HTS721010G9AT00, MCZOA51A, max UDMA/100
> [   17.990073] ata1.00: 195371568 sectors, multi 16: LBA48 
> [   17.993003] ata1.00: configured for UDMA/100
> [   17.993061] scsi1 : pata_amd
> [   17.993119] PM: Adding info for No Bus:host1
> [   18.297591] ata2.00: ATAPI, max MWDMA2
> [   18.451340] ata2.00: configured for MWDMA2
> [   18.451405] PM: Adding info for No Bus:target0:0:0
> [   18.451680] scsi 0:0:0:0: Direct-Access     ATA      HTS721010G9AT00  MCZO PQ: 0 ANSI: 5
> [   18.452894] PM: Adding info for scsi:0:0:0:0
> [   18.453120] sd 0:0:0:0: [sda] 195371568 512-byte hardware sectors (100030 MB)
> [   18.453193] sd 0:0:0:0: [sda] Write Protect is off
> [   18.453248] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
> [   18.453271] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> [   18.453648] sd 0:0:0:0: [sda] 195371568 512-byte hardware sectors (100030 MB)
> [   18.453717] sd 0:0:0:0: [sda] Write Protect is off
> [   18.453771] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
> [   18.453793] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> [   18.453901]  sda: sda1 sda2 sda3
> [   18.471748] sd 0:0:0:0: [sda] Attached SCSI disk
> [   18.471874] PM: Adding info for No Bus:target1:0:0
> [   18.472353] scsi 1:0:0:0: CD-ROM            HL-DT-ST DVD+RW GCA-4040N 1.19 PQ: 0 ANSI: 5
> [   18.472434] PM: Adding info for scsi:1:0:0:0
> [   18.474384] sr0: scsi3-mmc drive: 40x/24x writer cd/rw xa/form2 cdda tray
> [   18.474443] Uniform CD-ROM driver Revision: 3.20
> [   18.474628] sr 1:0:0:0: Attached scsi CD-ROM sr0
> [   18.474809] Yenta: CardBus bridge found at 0000:02:04.0 [103c:006d]
> [   18.474880] PCI: Bus 3, cardbus bridge: 0000:02:04.0
> [   18.474934]   IO window: 00003000-000030ff
> [   18.474988]   IO window: 00003400-000034ff
> [   18.475043]   PREFETCH window: 50000000-53ffffff
> [   18.475103]   MEM window: e0400000-e07fffff
> [   18.475159] Yenta: Enabling burst memory read transactions
> [   18.475215] Yenta: Using CSCINT to route CSC interrupts to PCI
> [   18.475270] Yenta: Routing CardBus interrupts to PCI
> [   18.475327] Yenta TI: socket 0000:02:04.0, mfunc 0x01111d22, devctl 0x64
> [   18.698633] Yenta: ISA IRQ mask 0x0cf8, PCI irq 19
> [   18.698687] Socket status: 30000086
> [   18.698742] Yenta: Raising subordinate bus# of parent bus (#02) from #02 to #06
> [   18.698816] pcmcia: parent PCI bridge I/O window: 0x3000 - 0x7fff
> [   18.698886] pcmcia: parent PCI bridge Memory window: 0xe0100000 - 0xe17fffff
> [   18.698945] pcmcia: parent PCI bridge Memory window: 0x50000000 - 0x57ffffff
> [   18.699145] PM: Adding info for No Bus:pcmcia_socket0
> [   18.949375] Yenta: CardBus bridge found at 0000:02:04.1 [103c:006d]
> [   18.949447] Yenta: Using CSCINT to route CSC interrupts to PCI
> [   18.949502] Yenta: Routing CardBus interrupts to PCI
> [   18.949560] Yenta TI: socket 0000:02:04.1, mfunc 0x01111d22, devctl 0x64
> [   19.172901] Yenta: ISA IRQ mask 0x0cf8, PCI irq 18
> [   19.172955] Socket status: 30000006
> [   19.173009] Yenta: Raising subordinate bus# of parent bus (#02) from #06 to #0a
> [   19.173083] pcmcia: parent PCI bridge I/O window: 0x3000 - 0x7fff
> [   19.173140] pcmcia: parent PCI bridge Memory window: 0xe0100000 - 0xe17fffff
> [   19.173198] pcmcia: parent PCI bridge Memory window: 0x50000000 - 0x57ffffff
> [   19.173373] PM: Adding info for No Bus:pcmcia_socket1
> [   19.423712] PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
> [   19.423836] PM: Adding info for platform:i8042
> [   19.433971] serio: i8042 KBD port at 0x60,0x64 irq 1
> [   19.434082] PM: Adding info for serio:serio0
> [   19.434178] serio: i8042 AUX port at 0x60,0x64 irq 12
> [   19.434240] PM: Adding info for serio:serio1
> [   19.434351] PM: Adding info for No Bus:psaux
> [   19.434390] mice: PS/2 mouse device common for all mice
> [   19.434590] async_tx: api initialized (sync-only)
> [   19.434645] xor: automatically using best checksumming function: generic_sse
> [   19.439565]    generic_sse:  6560.000 MB/sec
> [   19.439618] xor: using function: generic_sse (6560.000 MB/sec)
> [   19.439674] EDAC MC: Ver: 2.0.1 Mar 20 2007
> [   19.440144] EDAC MC0: Giving out device to k8_edac Athlon64/Opteron: DEV 0000:00:18.2
> [   19.440257] cpuidle: using governor ladder
> [   19.440389] TCP cubic registered
> [   19.440440] Initializing XFRM netlink socket
> [   19.440515] NET: Registered protocol family 1
> [   19.440575] NET: Registered protocol family 17
> [   19.440642] NET: Registered protocol family 15
> [   19.440746] powernow-k8: Found 1 AMD Athlon(tm) 64 Processor 3400+ processors (version 2.00.00)
> [   19.440940] powernow-k8:    0 : fid 0xe (2200 MHz), vid 0x2
> [   19.440995] powernow-k8:    1 : fid 0xa (1800 MHz), vid 0xa
> [   19.441050] powernow-k8:    2 : fid 0x0 (800 MHz), vid 0x12
> [   19.441737] swsusp: Resume From Partition /dev/sda3
> [   19.441739] PM: Checking swsusp image.
> [   19.444558] Marking TSC unstable due to possible TSC halt in C2
> [   19.444618] Time: acpi_pm clocksource has been installed.
> [   19.458341] PM: Resume from disk failed.
> [   19.499700] input: AT Translated Set 2 keyboard as /class/input/input3
> [   19.576971] reiser4: sda2: found disk format 4.0.0.
> [   25.172977] VFS: Mounted root (reiser4 filesystem) readonly.
> [   25.173099] Freeing unused kernel memory: 212k freed
> [   25.223972] PM: Adding info for No Bus:vcs1
> [   25.453962] PM: Adding info for No Bus:vcsa1
> [   26.020896] PM: Removing info for No Bus:vcs1
> [   26.021468] PM: Removing info for No Bus:vcsa1
> [   26.021876] PM: Adding info for No Bus:vcs1
> [   26.022218] PM: Adding info for No Bus:vcsa1
> [   26.022602] PM: Removing info for No Bus:vcs1
> [   26.022952] PM: Removing info for No Bus:vcsa1
> [   26.233012] PM: Adding info for No Bus:vcs1
> [   26.233388] PM: Adding info for No Bus:vcsa1
> [   26.233839] PM: Removing info for No Bus:vcs1
> [   26.234049] PM: Removing info for No Bus:vcsa1
> [   26.235514] PM: Adding info for No Bus:vcs1
> [   26.235956] PM: Adding info for No Bus:vcsa1
> [   26.236402] PM: Removing info for No Bus:vcs1
> [   26.236784] PM: Removing info for No Bus:vcsa1
> [   26.237017] PM: Adding info for No Bus:vcs1
> [   26.237587] PM: Adding info for No Bus:vcsa1
> [   26.238069] PM: Removing info for No Bus:vcs1
> [   26.238457] PM: Removing info for No Bus:vcsa1
> [   26.302723] PM: Adding info for No Bus:vcs1
> [   26.303340] PM: Adding info for No Bus:vcsa1
> [   29.773194] sd 0:0:0:0: Attached scsi generic sg0 type 0
> [   29.773218] sr 1:0:0:0: Attached scsi generic sg1 type 5
> [   29.936763] usbcore: registered new interface driver usbfs
> [   29.936876] usbcore: registered new interface driver hub
> [   29.936938] usbcore: registered new device driver usb
> [   29.938045] ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
> [   29.938092] PCI: Enabling device 0000:00:02.0 (0004 -> 0006)
> [   29.938715] ACPI: PCI Interrupt Link [LUS0] enabled at IRQ 22
> [   29.938727] ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [LUS0] -> GSI 22 (level, low) -> IRQ 22
> [   29.938746] PCI: Setting latency timer of device 0000:00:02.0 to 64
> [   29.938750] ohci_hcd 0000:00:02.0: OHCI Host Controller
> [   29.943103] ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 1
> [   30.154957] ohci_hcd 0000:00:02.0: irq 22, io mem 0xe0000000
> [   30.190412] PM: Adding info for No Bus:timer
> [   30.208166] usb usb1: new device found, idVendor=0000, idProduct=0000
> [   30.208171] usb usb1: new device strings: Mfr=3, Product=2, SerialNumber=1
> [   30.208173] usb usb1: Product: OHCI Host Controller
> [   30.208175] usb usb1: Manufacturer: Linux 2.6.21-rc4-mm1 ohci_hcd
> [   30.208177] usb usb1: SerialNumber: 0000:00:02.0
> [   30.208266] PM: Adding info for usb:usb1
> [   30.208743] PM: Adding info for No Bus:usbdev1.1_ep00
> [   30.208769] usb usb1: configuration #1 chosen from 1 choice
> [   30.209010] PM: Adding info for usb:1-0:1.0
> [   30.209168] hub 1-0:1.0: USB hub found
> [   30.209274] hub 1-0:1.0: 3 ports detected
> [   30.310069] PM: Adding info for No Bus:usbdev1.1_ep81
> [   30.310414] PM: Adding info for No Bus:usbdev1.1
> [   30.310803] PCI: Enabling device 0000:00:02.1 (0004 -> 0006)
> [   30.311309] ACPI: PCI Interrupt Link [LUS1] enabled at IRQ 21
> [   30.311320] ACPI: PCI Interrupt 0000:00:02.1[B] -> Link [LUS1] -> GSI 21 (level, low) -> IRQ 21
> [   30.311341] PCI: Setting latency timer of device 0000:00:02.1 to 64
> [   30.311344] ohci_hcd 0000:00:02.1: OHCI Host Controller
> [   30.311377] ohci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 2
> [   30.523351] ohci_hcd 0000:00:02.1: irq 21, io mem 0xe0001000
> [   30.576281] usb usb2: new device found, idVendor=0000, idProduct=0000
> [   30.576285] usb usb2: new device strings: Mfr=3, Product=2, SerialNumber=1
> [   30.576288] usb usb2: Product: OHCI Host Controller
> [   30.576290] usb usb2: Manufacturer: Linux 2.6.21-rc4-mm1 ohci_hcd
> [   30.576292] usb usb2: SerialNumber: 0000:00:02.1
> [   30.576318] PM: Adding info for usb:usb2
> [   30.576410] PM: Adding info for No Bus:usbdev2.1_ep00
> [   30.576433] usb usb2: configuration #1 chosen from 1 choice
> [   30.576451] PM: Adding info for usb:2-0:1.0
> [   30.576485] hub 2-0:1.0: USB hub found
> [   30.576499] hub 2-0:1.0: 3 ports detected
> [   30.677124] PM: Adding info for No Bus:usbdev2.1_ep81
> [   30.677190] PM: Adding info for No Bus:usbdev2.1
> [   30.677819] ACPI: PCI Interrupt Link [LUS2] enabled at IRQ 20
> [   30.677832] ACPI: PCI Interrupt 0000:00:02.2[C] -> Link [LUS2] -> GSI 20 (level, low) -> IRQ 20
> [   30.677853] PCI: Setting latency timer of device 0000:00:02.2 to 64
> [   30.677856] ehci_hcd 0000:00:02.2: EHCI Host Controller
> [   30.677889] ehci_hcd 0000:00:02.2: new USB bus registered, assigned bus number 3
> [   30.677932] PCI: cache line size of 64 is not supported by device 0000:00:02.2
> [   30.677957] ehci_hcd 0000:00:02.2: irq 20, io mem 0xe0004000
> [   30.677962] ehci_hcd 0000:00:02.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
> [   30.678054] usb usb3: new device found, idVendor=0000, idProduct=0000
> [   30.678057] usb usb3: new device strings: Mfr=3, Product=2, SerialNumber=1
> [   30.678059] usb usb3: Product: EHCI Host Controller
> [   30.678061] usb usb3: Manufacturer: Linux 2.6.21-rc4-mm1 ehci_hcd
> [   30.678063] usb usb3: SerialNumber: 0000:00:02.2
> [   30.678072] PM: Adding info for usb:usb3
> [   30.678141] PM: Adding info for No Bus:usbdev3.1_ep00
> [   30.678162] usb usb3: configuration #1 chosen from 1 choice
> [   30.678184] PM: Adding info for usb:3-0:1.0
> [   30.678207] hub 3-0:1.0: USB hub found
> [   30.678380] hub 3-0:1.0: 6 ports detected
> [   30.778960] PM: Adding info for No Bus:usbdev3.1_ep81
> [   30.779025] PM: Adding info for No Bus:usbdev3.1
> [   30.783028] ACPI: PCI Interrupt Link [LACI] enabled at IRQ 22
> [   30.783033] ACPI: PCI Interrupt 0000:00:06.0[A] -> Link [LACI] -> GSI 22 (level, low) -> IRQ 22
> [   30.783069] PCI: Setting latency timer of device 0000:00:06.0 to 64
> [   30.867183] input: PS/2 Mouse as /class/input/input4
> [   30.879995] input: AlpsPS/2 ALPS GlidePoint as /class/input/input5
> [   30.886726] AC'97 0 analog subsections not ready
> [   31.288300] usb 2-2: new full speed USB device using ohci_hcd and address 2
> [   31.446880] intel8x0_measure_ac97_clock: measured 50191 usecs
> [   31.446884] intel8x0: clocking to 47393
> [   31.446930] PM: Adding info for No Bus:card0
> [   31.447154] PM: Adding info for No Bus:pcmC0D2p
> [   31.447411] PM: Adding info for No Bus:pcmC0D1c
> [   31.447441] PM: Adding info for No Bus:pcmC0D0p
> [   31.447539] PM: Adding info for No Bus:pcmC0D0c
> [   31.447565] PM: Adding info for ac97:0-0:AD1981B
> [   31.447601] PM: Adding info for No Bus:controlC0
> [   31.508940] usb 2-2: new device found, idVendor=049f, idProduct=0086
> [   31.508945] usb 2-2: new device strings: Mfr=1, Product=2, SerialNumber=0
> [   31.508948] usb 2-2: Product: Bluetooth by hp
> [   31.508950] usb 2-2: Manufacturer: ACTIONTEC
> [   31.508975] PM: Adding info for usb:2-2
> [   31.509068] PM: Adding info for No Bus:usbdev2.2_ep00
> [   31.509092] usb 2-2: configuration #1 chosen from 1 choice
> [   31.512951] PM: Adding info for usb:2-2:1.0
> [   31.513032] PM: Adding info for No Bus:usbdev2.2_ep81
> [   31.513073] PM: Adding info for No Bus:usbdev2.2_ep02
> [   31.513107] PM: Adding info for No Bus:usbdev2.2_ep82
> [   31.513141] PM: Adding info for usb:2-2:1.1
> [   31.513182] PM: Adding info for No Bus:usbdev2.2_ep03
> [   31.513221] PM: Adding info for No Bus:usbdev2.2_ep83
> [   31.513249] PM: Adding info for usb:2-2:1.2
> [   31.513329] PM: Adding info for No Bus:usbdev2.2
> [   31.717722] hci_usb: Unknown symbol hci_suspend_dev
> [   31.717763] hci_usb: Unknown symbol hci_free_dev
> [   31.717983] hci_usb: Unknown symbol hci_resume_dev
> [   31.718035] hci_usb: Unknown symbol hci_alloc_dev
> [   31.718136] hci_usb: Unknown symbol hci_unregister_dev
> [   31.718243] hci_usb: Unknown symbol hci_register_dev
> [   31.781354] hci_usb: Unknown symbol hci_suspend_dev
> [   31.781394] hci_usb: Unknown symbol hci_free_dev
> [   31.781614] hci_usb: Unknown symbol hci_resume_dev
> [   31.781666] hci_usb: Unknown symbol hci_alloc_dev
> [   31.781767] hci_usb: Unknown symbol hci_unregister_dev
> [   31.781874] hci_usb: Unknown symbol hci_register_dev
> [   31.787382] hci_usb: Unknown symbol hci_suspend_dev
> [   31.787422] hci_usb: Unknown symbol hci_free_dev
> [   31.787642] hci_usb: Unknown symbol hci_resume_dev
> [   31.787694] hci_usb: Unknown symbol hci_alloc_dev
> [   31.787795] hci_usb: Unknown symbol hci_unregister_dev
> [   31.787901] hci_usb: Unknown symbol hci_register_dev
> [   33.005970] NET: Registered protocol family 10
> [   34.776248] ReiserFS: sda1: found reiserfs format "3.6" with standard journal
> [   34.776310] ReiserFS: sda1: using ordered data mode
> [   34.776796] ReiserFS: sda1: journal params: device sda1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
> [   34.778707] ReiserFS: sda1: checking transaction log (sda1)
> [   34.810342] ReiserFS: sda1: Using r5 hash to sort names
> [   35.034524] Adding 2843496k swap on /dev/disk/by-uuid/fd35277a-8dc7-4afe-8257-fda61b757344.  Priority:100 extents:1 across:2843496k
> [   42.116195] PM: Removing info for No Bus:vcs1
> [   42.116521] PM: Removing info for No Bus:vcsa1
> [   42.146081] PM: Adding info for No Bus:vcs1
> [   42.146219] PM: Adding info for No Bus:vcsa1
> [ 1061.733883] su[2639]: segfault at 0000000000000008 rip 0000003103c098b2 rsp 00007fffb0fea590 error 4
> [ 1601.898867] PM: Removing info for No Bus:vcs1
> [ 1601.899098] PM: Removing info for No Bus:vcsa1
> [ 1601.905470] PM: Adding info for No Bus:vcs1
> [ 1601.905622] PM: Adding info for No Bus:vcsa1
> [ 1606.464599] PM: Adding info for No Bus:vcs2
> [ 1606.464845] PM: Adding info for No Bus:vcsa2
> [ 1606.466860] PM: Removing info for No Bus:vcs2
> [ 1606.466969] PM: Removing info for No Bus:vcsa2
> [ 1606.473400] PM: Adding info for No Bus:vcs3
> [ 1606.473561] PM: Adding info for No Bus:vcsa3
> [ 1606.475560] PM: Removing info for No Bus:vcs3
> [ 1606.475667] PM: Removing info for No Bus:vcsa3
> [ 1606.478811] PM: Adding info for No Bus:vcs4
> [ 1606.478973] PM: Adding info for No Bus:vcsa4
> [ 1606.479291] PM: Removing info for No Bus:vcs4
> [ 1606.479321] PM: Removing info for No Bus:vcsa4
> [ 1606.479397] PM: Adding info for No Bus:vcs5
> [ 1606.479420] PM: Adding info for No Bus:vcsa5
> [ 1606.479450] PM: Removing info for No Bus:vcs5
> [ 1606.479472] PM: Removing info for No Bus:vcsa5
> [ 1606.479549] PM: Adding info for No Bus:vcs6
> [ 1606.479572] PM: Adding info for No Bus:vcsa6
> [ 1606.479604] PM: Removing info for No Bus:vcs6
> [ 1606.479626] PM: Removing info for No Bus:vcsa6
> [ 1606.479694] PM: Adding info for No Bus:vcs7
> [ 1606.479716] PM: Adding info for No Bus:vcsa7
> [ 1606.479745] PM: Removing info for No Bus:vcs7
> [ 1606.479767] PM: Removing info for No Bus:vcsa7
> [ 1606.479835] PM: Adding info for No Bus:vcs8
> [ 1606.479859] PM: Adding info for No Bus:vcsa8
> [ 1606.479928] PM: Removing info for No Bus:vcs8
> [ 1606.479951] PM: Removing info for No Bus:vcsa8
> [ 1606.480018] PM: Adding info for No Bus:vcs9
> [ 1606.480041] PM: Adding info for No Bus:vcsa9
> [ 1606.480071] PM: Removing info for No Bus:vcs9
> [ 1606.480093] PM: Removing info for No Bus:vcsa9
> [ 1606.480160] PM: Adding info for No Bus:vcs10
> [ 1606.480183] PM: Adding info for No Bus:vcsa10
> [ 1606.480212] PM: Removing info for No Bus:vcs10
> [ 1606.480234] PM: Removing info for No Bus:vcsa10
> [ 1606.480302] PM: Adding info for No Bus:vcs11
> [ 1606.480325] PM: Adding info for No Bus:vcsa11
> [ 1606.480354] PM: Removing info for No Bus:vcs11
> [ 1606.480376] PM: Removing info for No Bus:vcsa11
> [ 1606.910477] PM: Adding info for No Bus:vcs2
> [ 1606.910514] PM: Adding info for No Bus:vcsa2
> [ 1606.917302] PM: Removing info for No Bus:vcs2
> [ 1606.917349] PM: Removing info for No Bus:vcsa2
> [ 1606.919043] PM: Adding info for No Bus:vcs3
> [ 1606.919071] PM: Adding info for No Bus:vcsa3
> [ 1606.927621] PM: Adding info for No Bus:vcs4
> [ 1606.927658] PM: Adding info for No Bus:vcsa4
> [ 1606.928858] PM: Removing info for No Bus:vcs3
> [ 1606.928892] PM: Removing info for No Bus:vcsa3
> [ 1606.935224] PM: Removing info for No Bus:vcs4
> [ 1606.935269] PM: Removing info for No Bus:vcsa4
> [ 1606.937061] PM: Adding info for No Bus:vcs5
> [ 1606.937089] PM: Adding info for No Bus:vcsa5
> [ 1606.947922] PM: Removing info for No Bus:vcs5
> [ 1606.947970] PM: Removing info for No Bus:vcsa5
> [ 1606.951331] PM: Adding info for No Bus:vcs6
> [ 1606.951366] PM: Adding info for No Bus:vcsa6
> [ 1606.958845] PM: Removing info for No Bus:vcs6
> [ 1606.958892] PM: Removing info for No Bus:vcsa6
> [ 1606.961602] PM: Adding info for No Bus:vcs7
> [ 1606.961636] PM: Adding info for No Bus:vcsa7
> [ 1606.972031] PM: Removing info for No Bus:vcs7
> [ 1606.972082] PM: Removing info for No Bus:vcsa7
> [ 1606.973903] PM: Adding info for No Bus:vcs8
> [ 1606.973933] PM: Adding info for No Bus:vcsa8
> [ 1606.982366] PM: Removing info for No Bus:vcs8
> [ 1606.982413] PM: Removing info for No Bus:vcsa8
> [ 1606.986078] PM: Adding info for No Bus:vcs9
> [ 1606.986113] PM: Adding info for No Bus:vcsa9
> [ 1607.000479] PM: Adding info for No Bus:vcs10
> [ 1607.000514] PM: Adding info for No Bus:vcsa10
> [ 1607.000750] PM: Removing info for No Bus:vcs9
> [ 1607.000782] PM: Removing info for No Bus:vcsa9
> [ 1607.025869] PM: Adding info for No Bus:vcs11
> [ 1607.025904] PM: Adding info for No Bus:vcsa11
> [ 1607.031896] PM: Removing info for No Bus:vcs11
> [ 1607.031941] PM: Removing info for No Bus:vcsa11
> [ 1607.043139] PM: Removing info for No Bus:vcs10
> [ 1607.043185] PM: Removing info for No Bus:vcsa10
> [ 1608.025861] eth0: link up, 100Mbps, full-duplex, lpa 0xC1E1
> [ 1608.343434] PM: Removing info for No Bus:vcs1
> [ 1608.343599] PM: Removing info for No Bus:vcsa1
> [ 1608.348965] PM: Adding info for No Bus:vcs1
> [ 1608.349084] PM: Adding info for No Bus:vcsa1
> [ 1608.350359] PM: Removing info for No Bus:vcs1
> [ 1608.350447] PM: Removing info for No Bus:vcsa1
> [ 1608.350790] PM: Adding info for No Bus:vcs1
> [ 1608.350809] PM: Adding info for No Bus:vcsa1
> [ 1608.350872] PM: Removing info for No Bus:vcs1
> [ 1608.350891] PM: Removing info for No Bus:vcsa1
> [ 1608.350927] PM: Adding info for No Bus:vcs1
> [ 1608.350945] PM: Adding info for No Bus:vcsa1
> [ 1608.351049] PM: Removing info for No Bus:vcs1
> [ 1608.351068] PM: Removing info for No Bus:vcsa1
> [ 1608.353580] PM: Adding info for No Bus:vcs1
> [ 1608.353616] PM: Adding info for No Bus:vcsa1
> [ 1617.090942] eth0: no IPv6 routers present
> [ 1617.123609] ata1.00: configured for UDMA/100
> [ 1617.123618] ata1: EH complete
> [ 1617.140588] sd 0:0:0:0: [sda] 195371568 512-byte hardware sectors (100030 MB)
> [ 1617.140902] sd 0:0:0:0: [sda] Write Protect is off
> [ 1617.140905] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
> [ 1617.149976] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> [ 1620.665587] process `named' is using obsolete setsockopt SO_BSDCOMPAT
> [ 1620.742991] PM: Adding info for No Bus:vcs7
> [ 1620.744509] PM: Adding info for No Bus:vcsa7
> [ 1620.792323] PM: Removing info for No Bus:vcs7
> [ 1620.793678] PM: Removing info for No Bus:vcsa7
> [ 1621.266697] PM: Adding info for No Bus:vcs7
> [ 1621.268278] PM: Adding info for No Bus:vcsa7
> [ 1622.859425] PM: Adding info for No Bus:mixer
> [ 1622.939896] PM: Adding info for No Bus:adsp
> [ 1622.955211] PM: Adding info for No Bus:dsp
> [ 1622.958759] PM: Adding info for No Bus:audio
> [ 1624.113602] esound-esd[57956]: segfault at 000000000000ac44 rip 00000036a8c55b2b rsp 00007fff9723d8f0 error 4
> [ 1625.283022] PM: Adding info for No Bus:vcs2
> [ 1625.284318] PM: Adding info for No Bus:vcsa2
> [ 1625.285611] PM: Adding info for No Bus:vcs3
> [ 1625.286744] PM: Adding info for No Bus:vcsa3
> [ 1625.289092] PM: Adding info for No Bus:vcs4
> [ 1625.290316] PM: Adding info for No Bus:vcsa4
> [ 1625.292624] PM: Adding info for No Bus:vcs5
> [ 1625.293892] PM: Adding info for No Bus:vcsa5
> [ 1625.296159] PM: Adding info for No Bus:vcs6
> [ 1625.297535] PM: Adding info for No Bus:vcsa6
> [ 1651.450090] esd[58205]: segfault at 000000000000ac44 rip 00000036a8c55b2b rsp 00007fffebe7fcd0 error 4
> [ 1658.130375] ISO 9660 Extensions: Microsoft Joliet Level 3
> [ 1658.254107] ISO 9660 Extensions: RRIP_1991A
> [ 1660.022177] [ACPI Debug]  String: [0x12] "=====QUERY_25====="
> [ 1663.057766] 
> [ 1663.057769] =======================================================
> [ 1663.057775] [ INFO: possible circular locking dependency detected ]
> [ 1663.057778] 2.6.21-rc4-mm1 #1
> [ 1663.057780] -------------------------------------------------------
> [ 1663.057783] evolution-data-/58416 is trying to acquire lock:
> [ 1663.057785]  (&mm->mmap_sem){----}, at: [<ffffffff80269eda>] do_page_fault+0x35a/0x800
> [ 1663.057795] 
> [ 1663.057796] but task is already holding lock:
> [ 1663.057798]  (&data->latch){----}, at: [<ffffffff8036a835>] read_unix_file+0x95/0x450
> [ 1663.057806] 
> [ 1663.057807] which lock already depends on the new lock.
> [ 1663.057808] 
> [ 1663.057809] 
> [ 1663.057810] the existing dependency chain (in reverse order) is:
> [ 1663.057812] 
> [ 1663.057813] -> #1 (&data->latch){----}:
> [ 1663.057816]        [<ffffffff802ae4c1>] __lock_acquire+0xd61/0x1010
> [ 1663.057823]        [<ffffffff802ae7b9>] lock_acquire+0x49/0x70
> [ 1663.057829]        [<ffffffff8036c721>] get_exclusive_access+0x11/0x20
> [ 1663.057836]        [<ffffffff802a8c9f>] down_write+0x2f/0x40
> [ 1663.057843]        [<ffffffff8036c721>] get_exclusive_access+0x11/0x20
> [ 1663.057849]        [<ffffffff8036ac50>] mmap_unix_file+0x60/0x140
> [ 1663.057855]        [<ffffffff8020dbf7>] do_mmap_pgoff+0x4f7/0x800
> [ 1663.057862]        [<ffffffff802acfd6>] mark_held_locks+0x76/0xa0
> [ 1663.057868]        [<ffffffff80267754>] _spin_unlock_irq+0x24/0x50
> [ 1663.057873]        [<ffffffff8026775f>] _spin_unlock_irq+0x2f/0x50
> [ 1663.057879]        [<ffffffff80234db3>] elf_map+0xa3/0x100
> [ 1663.057886]        [<ffffffff80217de2>] load_elf_binary+0x902/0x1c30
> [ 1663.057893]        [<ffffffff8028de20>] load_aout_binary+0x0/0x960
> [ 1663.057899]        [<ffffffff802174e0>] load_elf_binary+0x0/0x1c30
> [ 1663.057905]        [<ffffffff802406b3>] search_binary_handler+0xf3/0x2b0
> [ 1663.057912]        [<ffffffff8024f322>] load_script+0x212/0x240
> [ 1663.057919]        [<ffffffff802174e0>] load_elf_binary+0x0/0x1c30
> [ 1663.057925]        [<ffffffff8024f110>] load_script+0x0/0x240
> [ 1663.057930]        [<ffffffff802406b3>] search_binary_handler+0xf3/0x2b0
> [ 1663.057936]        [<ffffffff8023f9f8>] do_execve+0x188/0x250
> [ 1663.057942]        [<ffffffff802a1a10>] __call_usermodehelper+0x0/0x80
> [ 1663.057950]        [<ffffffff80255034>] sys_execve+0x44/0x70
> [ 1663.057956]        [<ffffffff80260044>] kernel_execve+0x64/0xd0
> [ 1663.057963]        [<ffffffff802a1a10>] __call_usermodehelper+0x0/0x80
> [ 1663.057969]        [<ffffffff802a1e0b>] ____call_usermodehelper+0x15b/0x170
> [ 1663.057975]        [<ffffffff8025ffd8>] child_rip+0xa/0x12
> [ 1663.057981]        [<ffffffff80267754>] _spin_unlock_irq+0x24/0x50
> [ 1663.057987]        [<ffffffff8025f6c0>] restore_args+0x0/0x30
> [ 1663.057993]        [<ffffffff802a1cb0>] ____call_usermodehelper+0x0/0x170
> [ 1663.057999]        [<ffffffff8025ffce>] child_rip+0x0/0x12
> [ 1663.058004]        [<ffffffffffffffff>] 0xffffffffffffffff
> [ 1663.058042] 
> [ 1663.058043] -> #0 (&mm->mmap_sem){----}:
> [ 1663.058045]        [<ffffffff802ac62b>] print_circular_bug_header+0xdb/0x100
> [ 1663.058051]        [<ffffffff802ae390>] __lock_acquire+0xc30/0x1010
> [ 1663.058057]        [<ffffffff802ae7b9>] lock_acquire+0x49/0x70
> [ 1663.058062]        [<ffffffff80269eda>] do_page_fault+0x35a/0x800
> [ 1663.058068]        [<ffffffff802a8bc2>] down_read+0x32/0x40
> [ 1663.058074]        [<ffffffff80269eda>] do_page_fault+0x35a/0x800
> [ 1663.058080]        [<ffffffff80264207>] thread_return+0xef/0x148
> [ 1663.058088]        [<ffffffff802676fd>] _spin_unlock_irqrestore+0x3d/0x70
> [ 1663.058094]        [<ffffffff80267d2d>] error_exit+0x0/0x96
> [ 1663.058100]        [<ffffffff8020ccbf>] file_read_actor+0x6f/0x190
> [ 1663.058105]        [<ffffffff80240a6f>] __lock_page+0x5f/0x70
> [ 1663.058111]        [<ffffffff8020bcd7>] do_generic_mapping_read+0x1f7/0x500
> [ 1663.058117]        [<ffffffff8020cc50>] file_read_actor+0x0/0x190
> [ 1663.058123]        [<ffffffff802162ca>] generic_file_aio_read+0x19a/0x1f0
> [ 1663.058129]        [<ffffffff8020c91f>] do_sync_read+0xcf/0x120
> [ 1663.058135]        [<ffffffff802a61f0>] autoremove_wake_function+0x0/0x30
> [ 1663.058141]        [<ffffffff802675f9>] _spin_unlock+0x29/0x50
> [ 1663.058146]        [<ffffffff8034f6fe>] reiser4_grab+0xae/0xd0
> [ 1663.058155]        [<ffffffff8036a879>] read_unix_file+0xd9/0x450
> [ 1663.058161]        [<ffffffff8020acea>] vfs_read+0xba/0x180
> [ 1663.058166]        [<ffffffff80212b2e>] sys_pread64+0x5e/0x90
> [ 1663.058172]        [<ffffffff8025f11e>] system_call+0x7e/0x83
> [ 1663.058178]        [<ffffffffffffffff>] 0xffffffffffffffff
> [ 1663.058184] 
> [ 1663.058185] other info that might help us debug this:
> [ 1663.058186] 
> [ 1663.058188] 1 lock held by evolution-data-/58416:
> [ 1663.058190]  #0:  (&data->latch){----}, at: [<ffffffff8036a835>] read_unix_file+0x95/0x450
> [ 1663.058196] 
> [ 1663.058196] stack backtrace:
> [ 1663.058198] 
> [ 1663.058198] Call Trace:
> [ 1663.058204]  [<ffffffff802ac214>] print_circular_bug_tail+0x74/0x90
> [ 1663.058208]  [<ffffffff802ac62b>] print_circular_bug_header+0xdb/0x100
> [ 1663.058211]  [<ffffffff802ae390>] __lock_acquire+0xc30/0x1010
> [ 1663.058216]  [<ffffffff802ae7b9>] lock_acquire+0x49/0x70
> [ 1663.058219]  [<ffffffff80269eda>] do_page_fault+0x35a/0x800
> [ 1663.058223]  [<ffffffff802a8bc2>] down_read+0x32/0x40
> [ 1663.058226]  [<ffffffff80269eda>] do_page_fault+0x35a/0x800
> [ 1663.058232]  [<ffffffff80264207>] thread_return+0xef/0x148
> [ 1663.058236]  [<ffffffff802676fd>] _spin_unlock_irqrestore+0x3d/0x70
> [ 1663.058240]  [<ffffffff80267d2d>] error_exit+0x0/0x96
> [ 1663.058245]  [<ffffffff8020ccbf>] file_read_actor+0x6f/0x190
> [ 1663.058248]  [<ffffffff80240a6f>] __lock_page+0x5f/0x70
> [ 1663.058253]  [<ffffffff8020bcd7>] do_generic_mapping_read+0x1f7/0x500
> [ 1663.058256]  [<ffffffff8020cc50>] file_read_actor+0x0/0x190
> [ 1663.058263]  [<ffffffff802162ca>] generic_file_aio_read+0x19a/0x1f0
> [ 1663.058267]  [<ffffffff8020c91f>] do_sync_read+0xcf/0x120
> [ 1663.058272]  [<ffffffff802a61f0>] autoremove_wake_function+0x0/0x30
> [ 1663.058276]  [<ffffffff802675f9>] _spin_unlock+0x29/0x50
> [ 1663.058280]  [<ffffffff8034f6fe>] reiser4_grab+0xae/0xd0
> [ 1663.058284]  [<ffffffff8036a879>] read_unix_file+0xd9/0x450
> [ 1663.058290]  [<ffffffff8020acea>] vfs_read+0xba/0x180
> [ 1663.058294]  [<ffffffff80212b2e>] sys_pread64+0x5e/0x90
> [ 1663.058298]  [<ffffffff8025f11e>] system_call+0x7e/0x83
> [ 1663.058301] 
> [ 1714.279224] process `rndc' is using obsolete setsockopt SO_BSDCOMPAT
> [ 1717.959422] eth0: link up, 100Mbps, full-duplex, lpa 0xC1E1
> [ 1721.544091] process `named' is using obsolete setsockopt SO_BSDCOMPAT
> [ 1725.344372] eth0: no IPv6 routers present
> 

Re: 2.6.21-rc4-mm1

[Andrew Morton]

On Tue, 20 Mar 2007 12:20:16 -0700 Kees Cook <kees@outflux.net> wrote:

> I can't 
> get 2.6.21-rc4-mm1 to compile (with or without this fix):
> 
>   GEN     .version
> init/.missing_syscalls.h.cmd:2: *** missing separator.  Stop.
> make: *** [.tmp_vmlinux1] Error 2

How'd you manage that?

Sam, I think this is a you-thing rather than a dwmw2-thing?

Re: 2.6.21-rc4-mm1

[Randy Dunlap]

On Mon, 19 Mar 2007 20:56:23 -0800 Andrew Morton wrote:

> 
> Temporarily at
> 
>   http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
> 
> Will appear later at
> 
>   ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/


UIO_CIF should depend on PCI ??

With CONFIG_PCI=n, I get:

ERROR: "pci_module_init" [drivers/uio/uio_cif.ko] undefined!
ERROR: "pci_release_regions" [drivers/uio/uio_cif.ko] undefined!
make[1]: *** [__modpost] Error 1
make: *** [modules] Error 2

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

Re: 2.6.21-rc4-mm1

[J.A. Magallón]

On Tue, 20 Mar 2007 17:36:57 +0100, "J.A. Magallón" <jamagallon@ono.com> wrote:

> On Mon, 19 Mar 2007 20:56:23 -0800, Andrew Morton <akpm@linux-foundation.org> wrote:
> 
> > 
> > Temporarily at
> > 
> >   http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
> > 
> > Will appear later at
> > 
> >   ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/
> > 
> 
> (oops, I forgot LKML)
> 
> I have no udev events for my dvd-rw...
> When I insert a disc in the dvd reader:
> 
> werewolf:~# udevmonitor
> udevmonitor prints the received event from the kernel [UEVENT]
> and the event which udev sends out after rule processing [UDEV]
> 
> UEVENT[1174385162.607021] mount    /block/sr1 (block)
> UDEV  [1174385162.610056] mount    /block/sr1 (block)
> 
> If I insert it in the dvd-rw drive, nothing happens.
> 

I realized that my scsi devices were like this:

werewolf:~# lsscsi
[0:0:0:0]    cd/dvd  HL-DT-ST DVDRAM GSA-H10N  JL10  /dev/.tmp-11-0
[0:0:1:0]    disk    IOMEGA   ZIP 250          51.G  /dev/sda
[1:0:0:0]    disk    ATA      ST3120022A       3.06  /dev/sdb
[1:0:1:0]    cd/dvd  TOSHIBA  DVD-ROM SD-M1712 1004  /dev/.tmp-11-1
[2:0:0:0]    disk    ATA      ST3200822AS      3.01  /dev/sdc
[7:0:0:0]    disk    LG       USBDrive         1100  /dev/sdd

After a service udev force-reload:

werewolf:~# lsscsi
[0:0:0:0]    cd/dvd  HL-DT-ST DVDRAM GSA-H10N  JL10  /dev/sr0
[0:0:1:0]    disk    IOMEGA   ZIP 250          51.G  /dev/sda
[1:0:0:0]    disk    ATA      ST3120022A       3.06  /dev/sdb
[1:0:1:0]    cd/dvd  TOSHIBA  DVD-ROM SD-M1712 1004  /dev/sr1
[2:0:0:0]    disk    ATA      ST3200822AS      3.01  /dev/sdc
[7:0:0:0]    disk    LG       USBDrive         1100  /dev/sdd

If I insert a disc in /dev/sr1 and eject it:

werewolf:~# lsscsi
[0:0:0:0]    cd/dvd  HL-DT-ST DVDRAM GSA-H10N  JL10  /dev/sr0
[0:0:1:0]    disk    IOMEGA   ZIP 250          51.G  /dev/sda
[1:0:0:0]    disk    ATA      ST3120022A       3.06  /dev/sdb
[1:0:1:0]    cd/dvd  TOSHIBA  DVD-ROM SD-M1712 1004  /dev/.tmp-11-1
[2:0:0:0]    disk    ATA      ST3200822AS      3.01  /dev/sdc
[7:0:0:0]    disk    LG       USBDrive         1100  /dev/sdd

If I reload the disc in the TOSHIBA, it is automounted but the strange
device is still there.

Trying with /dev/sr0 still gives no events. What is happening here ?
It is the kernel or is udev setup ?

TIA

--
J.A. Magallon <jamagallon()ono!com>     \               Software is like sex:
                                         \         It's better when it's free
Mandriva Linux release 2007.1 (Cooker) for i586
Linux 2.6.20-jam05 (gcc 4.1.2 20070302 (prerelease) (4.1.2-1mdv2007.1)) #2 SMP PREEMPT

Re: 2.6.21-rc4-mm1

[Randy Dunlap]

On Mon, 19 Mar 2007 20:56:23 -0800 Andrew Morton wrote:

> 
> Temporarily at
> 
>   http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
> 
> Will appear later at
> 
>   ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/


I think that this:

config EEPROM_93CX6
	tristate "EEPROM 93CX6 support"
	---help---
	This is a driver for the EEPROM chipsets 93c46 and 93c66.
	The driver supports both read as well as write commands.

should not be in lib/Kconfig.  lib/ is not for drivers.
or (simpler) s/driver/library/
but I think I'd rather see it in drivers/misc/.


and the help text needs to be indented 2 more spaces...

---
~Randy
boilerplate:
*** Remember to use Documentation/SubmitChecklist when testing your code ***

Re: 2.6.21-rc4-mm1

[J.A. Magallón]

On Mon, 19 Mar 2007 20:56:23 -0800, Andrew Morton <akpm@linux-foundation.org> wrote:

> 
> Temporarily at
> 
>   http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
> 

After applying hot-fixes, I get this:

MODPOST vmlinux
WARNING: init/built-in.o - Section mismatch: reference to .init.text: from .text between 'rest_init' (at offset 0xfa) and 'try_name'
WARNING: arch/i386/kernel/built-in.o - Section mismatch: reference to .init.text:cpu_set_gdt from .text between 'initialize_secondary' (at offset 0xbce3) and 'mp_find_ioapic'
WARNING: mm/built-in.o - Section mismatch: reference to .init.data:initkmem_list3 from .text between 'set_up_list3s' (at offset 0x1b384) and 's_start'

If you need anything, just ask (.config or the like)

--
J.A. Magallon <jamagallon()ono!com>     \               Software is like sex:
                                         \         It's better when it's free
Mandriva Linux release 2007.1 (Cooker) for i586
Linux 2.6.20-jam05 (gcc 4.1.2 20070302 (prerelease) (4.1.2-1mdv2007.1)) #2 SMP PREEMPT

Re: 2.6.21-rc4-mm1

[Randy Dunlap]

On Tue, 20 Mar 2007 12:20:16 -0700 Kees Cook wrote:

> On Tue, Mar 20, 2007 at 10:31:51AM -0700, Randy Dunlap wrote:
> >   LD      .tmp_vmlinux1
> > kernel/built-in.o:(.data+0xfc0): undefined reference to `maps_protect'
> > make: *** [.tmp_vmlinux1] Error 1
> > 
> > with CONFIG_PROC_FS=n
> 
> Gah!  Apologies.  This should fix it, but I can't test it since I can't 
> get 2.6.21-rc4-mm1 to compile (with or without this fix):
> 
>   GEN     .version
> init/.missing_syscalls.h.cmd:2: *** missing separator.  Stop.
> make: *** [.tmp_vmlinux1] Error 2
> 
> 
> Signed-off-by: Kees Cook <kees@outflux.net>

Yes, that works_for_me.

Acked-by: Randy Dunlap <randy.dunlap@oracle.com>

> ---
> diff -uNrp linux-2.6.21-rc4-mm1/kernel/sysctl.c linux-2.6.21-rc4-mm1-kees/kernel/sysctl.c
> --- linux-2.6.21-rc4-mm1/kernel/sysctl.c	2007-03-20 10:45:06.000000000 -0700
> +++ linux-2.6.21-rc4-mm1-kees/kernel/sysctl.c	2007-03-20 11:36:06.000000000 -0700
> @@ -77,9 +77,12 @@ extern int pid_max_min, pid_max_max;
>  extern int sysctl_drop_caches;
>  extern int percpu_pagelist_fraction;
>  extern int compat_log;
> -extern int maps_protect;
>  extern int print_fatal_signals;
>  
> +#ifdef CONFIG_PROC_FS
> +extern int maps_protect;
> +#endif
> +
>  #if defined(CONFIG_ADAPTIVE_READAHEAD)
>  extern int readahead_ratio;
>  extern int readahead_hit_rate;
> @@ -619,6 +622,7 @@ static ctl_table kern_table[] = {
>  		.proc_handler	= &proc_dointvec,
>  	},
>  #endif
> +#ifdef CONFIG_PROC_FS
>  	{
>  		.ctl_name       = CTL_UNNUMBERED,
>  		.procname       = "maps_protect",
> @@ -627,6 +631,7 @@ static ctl_table kern_table[] = {
>  		.mode           = 0644,
>  		.proc_handler   = &proc_dointvec,
>  	},
> +#endif
>  
>  	{ .ctl_name = 0 }
>  };


---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

Re: 2.6.21-rc4-mm1

[Stéphane Jourdois]

Kees Cook a écrit :
> Gah!  Apologies.  This should fix it, but I can't test it since I can't 
> get 2.6.21-rc4-mm1 to compile (with or without this fix):
> 
>   GEN     .version
> init/.missing_syscalls.h.cmd:2: *** missing separator.  Stop.
> make: *** [.tmp_vmlinux1] Error 2

Hi,

Would you please try the following patch, after removing
init/.missing_syscalls.h.cmd ?

http://lkml.org/lkml/2007/3/20/79

thanks.

- Stéphane.

-- 
 ///  Stephane Jourdois     /"\  ASCII RIBBON CAMPAIGN \\\
(((    Consultant securite  \ /    AGAINST HTML MAIL    )))
 \\\   24 rue Cauchy         X                         ///
  \\\  75015  Paris         / \    +33 6 8643 3085    ///

Re: 2.6.21-rc4-mm1

[Jiri Slaby]

Pavel Machek napsal(a):
> Hi!
> 
>>>> Also, it might be useful to add a temporary /proc/freeze-unfreeze thing
>>>> which will simply do a freeze/unfreeze cycle.  Then we can apply various
>>>> workloads to the machine while madly stressing the freezer code.  
>>> echo testproc > /sys/power/disk; echo disk > /sys/power/state ... is
>>> pretty much what you want.
>> Ok, I'll try this.
> 
> It will not help you -- probably -- it is equivalent to just running
> s2ram. But it should make "successful" testing easier, because you no
> longer need machine with working suspend to test refrigerator.

Aha, I didn't read it carefully. Suspend is working, but not in this kernel.
I haven't tried s2ram in this version. Should I (I'm away from it) -- would
it show something?

regards,
-- 
http://www.fi.muni.cz/~xslaby/            Jiri Slaby
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8  22A0 32CC 55C3 39D4 7A7E

Re: 2.6.21-rc4-mm1

[Rafael J. Wysocki]

On Tuesday, 20 March 2007 20:40, Jiri Slaby wrote:
> Pavel Machek napsal(a):
> > Hi!
> > 
> >>> Andrew Morton napsal(a):
> >>>>   http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
> >>> I'm getting this while trying to swsusp:
> >>> Stopping tasks ...
> >>> Stopping kernel threads timed out after 20 seconds (1 tasks refusing to freeze):
> >>>  swapper
> >>>  Restarting tasks ... done.
> >>>
> >>> What to test? Enable PM_DEBUG?
> > 
> > Is it repeatable? Freezer normally works better than that.
> 
> Yes, at least it happened 3 times consecutively, when I tried to asleep the
> machine, then I turned it off.
> 
> >> Also, it might be useful to add a temporary /proc/freeze-unfreeze thing
> >> which will simply do a freeze/unfreeze cycle.  Then we can apply various
> >> workloads to the machine while madly stressing the freezer code.  
> > 
> > echo testproc > /sys/power/disk; echo disk > /sys/power/state ... is
> > pretty much what you want.
> 
> Ok, I'll try this.

Can I see .config please?

Rafael

Re: 2.6.21-rc4-mm1

[Pavel Machek]

Hi!

> >> Also, it might be useful to add a temporary /proc/freeze-unfreeze thing
> >> which will simply do a freeze/unfreeze cycle.  Then we can apply various
> >> workloads to the machine while madly stressing the freezer code.  
> > 
> > echo testproc > /sys/power/disk; echo disk > /sys/power/state ... is
> > pretty much what you want.
> 
> Ok, I'll try this.

It will not help you -- probably -- it is equivalent to just running
s2ram. But it should make "successful" testing easier, because you no
longer need machine with working suspend to test refrigerator.
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Re: 2.6.21-rc4-mm1

[Jiri Slaby]

Pavel Machek napsal(a):
> Hi!
> 
>>> Andrew Morton napsal(a):
>>>>   http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
>>> I'm getting this while trying to swsusp:
>>> Stopping tasks ...
>>> Stopping kernel threads timed out after 20 seconds (1 tasks refusing to freeze):
>>>  swapper
>>>  Restarting tasks ... done.
>>>
>>> What to test? Enable PM_DEBUG?
> 
> Is it repeatable? Freezer normally works better than that.

Yes, at least it happened 3 times consecutively, when I tried to asleep the
machine, then I turned it off.

>> Also, it might be useful to add a temporary /proc/freeze-unfreeze thing
>> which will simply do a freeze/unfreeze cycle.  Then we can apply various
>> workloads to the machine while madly stressing the freezer code.  
> 
> echo testproc > /sys/power/disk; echo disk > /sys/power/state ... is
> pretty much what you want.

Ok, I'll try this.

thanks,
-- 
http://www.fi.muni.cz/~xslaby/            Jiri Slaby
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8  22A0 32CC 55C3 39D4 7A7E

Re: 2.6.21-rc4-mm1

[Kees Cook]

On Tue, Mar 20, 2007 at 10:31:51AM -0700, Randy Dunlap wrote:
>   LD      .tmp_vmlinux1
> kernel/built-in.o:(.data+0xfc0): undefined reference to `maps_protect'
> make: *** [.tmp_vmlinux1] Error 1
> 
> with CONFIG_PROC_FS=n

Gah!  Apologies.  This should fix it, but I can't test it since I can't 
get 2.6.21-rc4-mm1 to compile (with or without this fix):

  GEN     .version
init/.missing_syscalls.h.cmd:2: *** missing separator.  Stop.
make: *** [.tmp_vmlinux1] Error 2


Signed-off-by: Kees Cook <kees@outflux.net>
---
diff -uNrp linux-2.6.21-rc4-mm1/kernel/sysctl.c linux-2.6.21-rc4-mm1-kees/kernel/sysctl.c
--- linux-2.6.21-rc4-mm1/kernel/sysctl.c	2007-03-20 10:45:06.000000000 -0700
+++ linux-2.6.21-rc4-mm1-kees/kernel/sysctl.c	2007-03-20 11:36:06.000000000 -0700
@@ -77,9 +77,12 @@ extern int pid_max_min, pid_max_max;
 extern int sysctl_drop_caches;
 extern int percpu_pagelist_fraction;
 extern int compat_log;
-extern int maps_protect;
 extern int print_fatal_signals;
 
+#ifdef CONFIG_PROC_FS
+extern int maps_protect;
+#endif
+
 #if defined(CONFIG_ADAPTIVE_READAHEAD)
 extern int readahead_ratio;
 extern int readahead_hit_rate;
@@ -619,6 +622,7 @@ static ctl_table kern_table[] = {
 		.proc_handler	= &proc_dointvec,
 	},
 #endif
+#ifdef CONFIG_PROC_FS
 	{
 		.ctl_name       = CTL_UNNUMBERED,
 		.procname       = "maps_protect",
@@ -627,6 +631,7 @@ static ctl_table kern_table[] = {
 		.mode           = 0644,
 		.proc_handler   = &proc_dointvec,
 	},
+#endif
 
 	{ .ctl_name = 0 }
 };




-- 
Kees Cook                                            @outflux.net

Re: 2.6.21-rc4-mm1

[Pavel Machek]

Hi!

> > Andrew Morton napsal(a):
> > >   http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
> > 
> > I'm getting this while trying to swsusp:
> > Stopping tasks ...
> > Stopping kernel threads timed out after 20 seconds (1 tasks refusing to freeze):
> >  swapper
> >  Restarting tasks ... done.
> > 
> > What to test? Enable PM_DEBUG?

Is it repeatable? Freezer normally works better than that.

> hm, OK.  Rafael has been working on fixing the process freezer and it'll
> take some time to get it to where we want it to be, I expect.

> Rafael, I think that we could afford to add heaps of debug in there at this
> stage to help us track down problems like this.
> 
> Also, it might be useful to add a temporary /proc/freeze-unfreeze thing
> which will simply do a freeze/unfreeze cycle.  Then we can apply various
> workloads to the machine while madly stressing the freezer code.  

echo testproc > /sys/power/disk; echo disk > /sys/power/state ... is
pretty much what you want.
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Re: 2.6.21-rc4-mm1

[Randy Dunlap]

On Mon, 19 Mar 2007 20:56:23 -0800 Andrew Morton wrote:

> 
> Temporarily at
> 
>   http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
> 
> Will appear later at
> 
>   ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/
> Changes since 2.6.21-rc3-mm1:

  LD      .tmp_vmlinux1
kernel/built-in.o:(.data+0xfc0): undefined reference to `maps_protect'
make: *** [.tmp_vmlinux1] Error 1

with CONFIG_PROC_FS=n

Kees?


---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

Re: 2.6.21-rc4-mm1

[J.A. Magallón]

On Mon, 19 Mar 2007 20:56:23 -0800, Andrew Morton <akpm@linux-foundation.org> wrote:

> 
> Temporarily at
> 
>   http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
> 
> Will appear later at
> 
>   ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/
> 

(oops, I forgot LKML)

I have no udev events for my dvd-rw...
When I insert a disc in the dvd reader:

werewolf:~# udevmonitor
udevmonitor prints the received event from the kernel [UEVENT]
and the event which udev sends out after rule processing [UDEV]

UEVENT[1174385162.607021] mount    /block/sr1 (block)
UDEV  [1174385162.610056] mount    /block/sr1 (block)

If I insert it in the dvd-rw drive, nothing happens.

extracts from dmesg:
(I have just noticed the message for the 40 wire cable, I will check)
(btw, why the h**l ata busses start nubering in 1 and scsi ones in 0 :((((,
it ata also begun in 0 life will be much easier...)

ata_piix 0000:00:1f.1: version 2.10ac1
ata1: PATA max UDMA/133 cmd 0x000101f0 ctl 0x000103f6 bmdma 0x0001f000 irq 14
ata2: PATA max UDMA/133 cmd 0x00010170 ctl 0x00010376 bmdma 0x0001f008 irq 15
scsi0 : ata_piix
ata1.00: ATAPI, max UDMA/33
ata1.01: ATAPI, max MWDMA0, CDB intr
ata1.00: configured for UDMA/33
ata1.01: configured for PIO3
scsi1 : ata_piix
ata2.00: ATA-6: ST3120022A, 3.06, max UDMA/100
ata2.00: 234441648 sectors, multi 16: LBA48 
ata2.01: ATAPI, max UDMA/33
ata2.00: limited to UDMA/33 due to 40-wire cable
ata2.00: configured for UDMA/33
ata2.01: configured for UDMA/33
scsi 0:0:0:0: CD-ROM            HL-DT-ST DVDRAM GSA-H10N  JL10 PQ: 0 ANSI: 5
sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 0:0:0:0: Attached scsi CD-ROM sr0
scsi 0:0:1:0: Direct-Access     IOMEGA   ZIP 250          51.G PQ: 0 ANSI: 5
sd 0:0:1:0: [sda] Attached SCSI removable disk
scsi 1:0:0:0: Direct-Access     ATA      ST3120022A       3.06 PQ: 0 ANSI: 5
sd 1:0:0:0: [sdb] 234441648 512-byte hardware sectors (120034 MB)
sd 1:0:0:0: [sdb] Attached SCSI disk
scsi 1:0:1:0: CD-ROM            TOSHIBA  DVD-ROM SD-M1712 1004 PQ: 0 ANSI: 5
sr1: scsi3-mmc drive: 48x/48x cd/rw xa/form2 cdda tray
sr 1:0:1:0: Attached scsi CD-ROM sr1
ata_piix 0000:00:1f.2: MAP [ P0 -- P1 -- ]
ata3: SATA max UDMA/133 cmd 0x0001c000 ctl 0x0001c402 bmdma 0x0001d000 irq 18
ata4: SATA max UDMA/133 cmd 0x0001c800 ctl 0x0001cc02 bmdma 0x0001d008 irq 18
scsi2 : ata_piix
ata3.00: ATA-6: ST3200822AS, 3.01, max UDMA/133
ata3.00: 390721968 sectors, multi 16: LBA48 
ata3.00: configured for UDMA/133
scsi3 : ata_piix
ATA: abnormal status 0x7F on port 0x0001c807
scsi 2:0:0:0: Direct-Access     ATA      ST3200822AS      3.01 PQ: 0 ANSI: 5
sd 2:0:0:0: [sdc] 390721968 512-byte hardware sectors (200050 MB)
sd 2:0:0:0: [sdc] Write Protect is off
sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 2:0:0:0: [sdc] 390721968 512-byte hardware sectors (200050 MB)
sd 2:0:0:0: [sdc] Write Protect is off
sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sdc: sdc1 sdc2 sdc3
sd 2:0:0:0: [sdc] Attached SCSI disk

--
J.A. Magallon <jamagallon()ono!com>     \               Software is like sex:
                                         \         It's better when it's free
Mandriva Linux release 2007.1 (Cooker) for i586
Linux 2.6.20-jam05 (gcc 4.1.2 20070302 (prerelease) (4.1.2-1mdv2007.1)) #1 SMP PREEMPT

Re: 2.6.21-rc4-mm1

[Andrew Morton]

On Tue, 20 Mar 2007 15:31:02 +0100 Jiri Slaby <jirislaby@gmail.com> wrote:

> Andrew Morton napsal(a):
> >   http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
> 
> I'm getting this while trying to swsusp:
> Stopping tasks ...
> Stopping kernel threads timed out after 20 seconds (1 tasks refusing to freeze):
>  swapper
>  Restarting tasks ... done.
> 
> What to test? Enable PM_DEBUG?

hm, OK.  Rafael has been working on fixing the process freezer and it'll
take some time to get it to where we want it to be, I expect.

Rafael, I think that we could afford to add heaps of debug in there at this
stage to help us track down problems like this.

Also, it might be useful to add a temporary /proc/freeze-unfreeze thing
which will simply do a freeze/unfreeze cycle.  Then we can apply various
workloads to the machine while madly stressing the freezer code.  

Re: 2.6.21-rc4-mm1

[Jiri Slaby]

Andrew Morton napsal(a):
>   http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/

I'm getting this while trying to swsusp:
Stopping tasks ...
Stopping kernel threads timed out after 20 seconds (1 tasks refusing to freeze):
 swapper
 Restarting tasks ... done.

What to test? Enable PM_DEBUG?

regards,
-- 
http://www.fi.muni.cz/~xslaby/            Jiri Slaby
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8  22A0 32CC 55C3 39D4 7A7E

Re: 2.6.21-rc4-mm1

[Andy Whitcroft]

Andrew Morton wrote:
> Temporarily at
> 
>   http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
> 
> Will appear later at
> 
>   ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/
> 
> 
> 

[All of the below is from the pre hot-fix runs.  The very few results
which are in for the hot-fix runs seem worse if anything.  :(  All
results should be out on TKO.]

> - Restored the RSDL CPU scheduler (a new version thereof)

Unsure if the above is the culprit but there seems to be a smattering of
BUG's in kernbench from the schedular on several systems, and panics
which do not fully dump out.

elm3b239 is about 2/4 kernbench being the test in progress when we
blammo in both failed tests, elm3b234 doesn't boot at all.


>From elm3b239:
------------[ cut here ]------------
kernel BUG at kernel/sched.c:3505!
invalid opcode: 0000 [1] SMP
last sysfs file: devices/pci0000:00/0000:00:00.0/irq
CPU 19
Modules linked in: loop dm_mod md_mod sg
Pid: 59, comm: migration/19 Not tainted 2.6.21-rc4-mm1-autokern1 #1
RIP: 0010:[<ffffffff804924f6>]  [<ffffffff804924f6>]
__sched_text_start+0x3a6/0x882
RSP: 0018:ffff810100cefe20  EFLAGS: 00010002
RAX: 000000000000008c RBX: ffff81002b0f64d8 RCX: 000000000000000c
RDX: 0000000000000000 RSI: 000000000000008c RDI: ffff81002b0f6da8
RBP: ffff810100cefeb0 R08: 000000000000008c R09: ffff81002b0f6d98
R10: 0000000000000034 R11: ffffffff8021ab20 R12: ffff81002b0f5a40
R13: 0000000000000002 R14: 000000725eb99ef7 R15: 0000000000000013
FS:  0000000000000000(0000) GS:ffff810100c42bc0(0000) knlGS:0000000000000000
CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
CR2: 00002ba9c431ab70 CR3: 00000001060fc000 CR4: 00000000000006e0
Process migration/19 (pid: 59, threadinfo ffff810100cee000, task
ffff810100ced8e0)
Stack:  0000000000000001 0000000000000001 ffff81010b681e98 ffff810100ced8e0
 ffff810100cefe80 ffff810100ceda78 0000000300000000 ffff81010b681e88
 ffff81010b681e90 0000000000000286 0000000000000013 0000000000000000
Call Trace:
 [<ffffffff80224a00>] migration_thread+0x1b0/0x250
 [<ffffffff80224850>] migration_thread+0x0/0x250
 [<ffffffff8023c85b>] kthread+0xdb/0x120
 [<ffffffff8020a7a8>] child_rip+0xa/0x12
 [<ffffffff8023c780>] kthread+0x0/0x120
 [<ffffffff8020a79e>] child_rip+0x0/0x12


Code: 0f 0b eb fe 49 8b 94 24 b8 01 00 00 49 8b 84 24 b0 01 00 00
RIP  [<ffffffff804924f6>] __sched_text_start+0x3a6/0x882
 RSP <ffff810100cefe20>


------------[ cut here ]------------
kernel BUG at kernel/sched.c:3505!
invalid opcode: 0000 [1] SMP
last sysfs file: devices/pci0000:00/0000:00:00.0/irq
CPU 21
Modules linked in: loop dm_mod md_mod sg
Pid: 15583, comm: cc1 Not tainted 2.6.21-rc4-mm1-autokern1 #1
RIP: 0010:[<ffffffff80496686>]  [<ffffffff80496686>]
__sched_text_start+0x3a6/0x882
RSP: 0000:ffff81010aca7ee0  EFLAGS: 00010002
RAX: 000000000000008c RBX: ffff81002b111358 RCX: 000000000000000c
RDX: 0000000000000000 RSI: 000000000000008c RDI: ffff81002b111c28
RBP: ffff81010aca7f70 R08: 000000000000008c R09: ffff81002b111c18
R10: 0000000000000034 R11: 0000000000000001 R12: ffff81002b1108c0
R13: 0000000000000002 R14: 0000006cb9bdff1a R15: 0000000000000015
FS:  00002b6ef0bc66d0(0000) GS:ffff810100d02e40(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00002b6ef20c1000 CR3: 0000000106e2b000 CR4: 00000000000006e0
Process cc1 (pid: 15583, threadinfo ffff81010aca6000, task ffff810105b03620)
Stack:  0000000000000100 0000000000000100 ffff81010964c148 ffff810105b03620
 ffffffff8054c9b7 ffff810105b037c0 0000000b0000000e ffff81010b216d80
 0000000000000000 00002b6ef20b7d00 00002b6ef20c1000 0000000000000400
Call Trace:
 [<ffffffff80209f17>] retint_careful+0xd/0x21


Code: 0f 0b eb fe 49 8b 94 24 b8 01 00 00 49 8b 84 24 b0 01 00 00
RIP  [<ffffffff80496686>] __sched_text_start+0x3a6/0x882
 RSP <ffff81010aca7ee0>



>From elm3b245:

------------[ cut here ]------------
kernel BUG at kernel/sched.c:3505!
invalid opcode: 0000 [1] SMP
last sysfs file:
CPU 0
Modules linked in:
Pid: 1, comm: init Not tainted 2.6.21-rc4-mm1-autokern1 #1
RIP: 0010:[<ffffffff8049cbb7>]  [<ffffffff8049cbb7>]
__sched_text_start+0x377/0x819
RSP: 0018:ffff81010037dee0  EFLAGS: 00010002
RAX: 000000000000008c RBX: 0000000000000002 RCX: 0000000000000000
RDX: 0000000000000034 RSI: 000000000000008c RDI: ffff810002c15210
RBP: ffff81010037df70 R08: 000000000000008c R09: 000000000000000c
R10: ffff810002c15200 R11: ffffffff8020968e R12: ffff810002c14940
R13: 00007fff1da16360 R14: ffff810002c14780 R15: 0000000000000000
FS:  00002b428d88d6d0(0000) GS:ffffffff805af000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 0000000000586a48 CR3: 0000000008c2f000 CR4: 00000000000006e0
Process init (pid: 1, threadinfo ffff81010037c000, task ffff810003369450)
Stack:  000003e10059d1b0 ffff81010037df28 ffffffff80276dd3 ffff810003369450
 ffff810008313880 0000003727988fe6 ffff8100033695f0 00007fff1da16250
 00007fff1da16360 000000000059bb70 ffffffff8020968e ffff81010037df48
Call Trace:
 [<ffffffff80276dd3>] generic_file_llseek+0x87/0x96
 [<ffffffff8020968e>] system_call+0x7e/0x83
 [<ffffffff80207db2>] sys_clone+0x23/0x25
 [<ffffffff802096f8>] sysret_careful+0xd/0x10


Code: 0f 0b eb fe 49 8b 96 b8 01 00 00 49 8b 86 b0 01 00 00 be 8c
RIP  [<ffffffff8049cbb7>] __sched_text_start+0x377/0x819
 RSP <ffff81010037dee0>

Re: 2.6.21-rc4-mm1

[Michal Piotrowski]

Andrew Morton napisał(a):
> Temporarily at
> 
>   http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
> 

Some new details about
http://www.ussg.iu.edu/hypermail/linux/kernel/0703.2/1367.html

I can reproduce it by running this on AutoTest

for profiler in ('oprofile', ):
	try:
		print "Testing profiler %s ..." % profiler
		job.profilers.add(profiler)
		job.run_test('aiostress',)
		job.profilers.delete(profiler)
	except:
		print "Test of profiler %s failed" % profiler
		raise

I guess that oprofile triggers it.

BUG: using smp_processor_id() in preemptible [00000001] code: mount/4934
caller is avail_to_resrv_perfctr_nmi_bit+0x2b/0x43
 [<c0105256>] show_trace_log_lvl+0x1a/0x2f
 [<c010597b>] show_trace+0x12/0x14
 [<c0105a3d>] dump_stack+0x16/0x18
 [<c0212f43>] debug_smp_processor_id+0xb3/0xc8
 [<c0116a26>] avail_to_resrv_perfctr_nmi_bit+0x2b/0x43
 [<fdc829b9>] nmi_create_files+0x2a/0x10e [oprofile]
 [<fdc81f52>] oprofile_create_files+0xe6/0xec [oprofile]
 [<fdc82157>] oprofilefs_fill_super+0x78/0x7e [oprofile]
 [<c018296e>] get_sb_single+0x59/0x9f
 [<fdc8208f>] oprofilefs_get_sb+0x1c/0x1e [oprofile]
 [<c01823d2>] vfs_kern_mount+0x81/0xf1
 [<c0182492>] do_kern_mount+0x38/0xde
 [<c01962b1>] do_mount+0x605/0x693
 [<c01963bf>] sys_mount+0x80/0xb5
 [<c0104270>] syscall_call+0x7/0xb
 =======================

l *avail_to_resrv_perfctr_nmi_bit+0x2b/0x43
0xc01169fb is in avail_to_resrv_perfctr_nmi_bit (/mnt/md0/devel/linux-mm/arch/i386/kernel/nmi.c:124).
119             return 0;
120     }
121
122     /* checks for a bit availability (hack for oprofile) */
123     int avail_to_resrv_perfctr_nmi_bit(unsigned int counter)
124     {
125             BUG_ON(counter > NMI_MAX_COUNTER_BITS);
126
127             return (!test_bit(counter, &__get_cpu_var(perfctr_nmi_owner)));
128     }


BUG: using smp_processor_id() in preemptible [00000001] code: mount/4934
caller is avail_to_resrv_perfctr_nmi_bit+0x2b/0x43
 [<c0105256>] show_trace_log_lvl+0x1a/0x2f
 [<c010597b>] show_trace+0x12/0x14
 [<c0105a3d>] dump_stack+0x16/0x18
 [<c0212f43>] debug_smp_processor_id+0xb3/0xc8
 [<c0116a26>] avail_to_resrv_perfctr_nmi_bit+0x2b/0x43
 [<fdc829b9>] nmi_create_files+0x2a/0x10e [oprofile]
 [<fdc81f52>] oprofile_create_files+0xe6/0xec [oprofile]
 [<fdc82157>] oprofilefs_fill_super+0x78/0x7e [oprofile]
 [<c018296e>] get_sb_single+0x59/0x9f
 [<fdc8208f>] oprofilefs_get_sb+0x1c/0x1e [oprofile]
 [<c01823d2>] vfs_kern_mount+0x81/0xf1
 [<c0182492>] do_kern_mount+0x38/0xde
 [<c01962b1>] do_mount+0x605/0x693
 [<c01963bf>] sys_mount+0x80/0xb5
 [<c0104270>] syscall_call+0x7/0xb
 =======================
BUG: using smp_processor_id() in preemptible [00000001] code: mount/4934
caller is avail_to_resrv_perfctr_nmi_bit+0x2b/0x43
 [<c0105256>] show_trace_log_lvl+0x1a/0x2f
 [<c010597b>] show_trace+0x12/0x14
 [<c0105a3d>] dump_stack+0x16/0x18
 [<c0212f43>] debug_smp_processor_id+0xb3/0xc8
 [<c0116a26>] avail_to_resrv_perfctr_nmi_bit+0x2b/0x43
 [<fdc829b9>] nmi_create_files+0x2a/0x10e [oprofile]
 [<fdc81f52>] oprofile_create_files+0xe6/0xec [oprofile]
 [<fdc82157>] oprofilefs_fill_super+0x78/0x7e [oprofile]
 [<c018296e>] get_sb_single+0x59/0x9f
 [<fdc8208f>] oprofilefs_get_sb+0x1c/0x1e [oprofile]
 [<c01823d2>] vfs_kern_mount+0x81/0xf1
 [<c0182492>] do_kern_mount+0x38/0xde
 [<c01962b1>] do_mount+0x605/0x693
 [<c01963bf>] sys_mount+0x80/0xb5
 [<c0104270>] syscall_call+0x7/0xb
 =======================
BUG: using smp_processor_id() in preemptible [00000001] code: mount/4934
caller is avail_to_resrv_perfctr_nmi_bit+0x2b/0x43
 [<c0105256>] show_trace_log_lvl+0x1a/0x2f
 [<c010597b>] show_trace+0x12/0x14
 [<c0105a3d>] dump_stack+0x16/0x18
 [<c0212f43>] debug_smp_processor_id+0xb3/0xc8
 [<c0116a26>] avail_to_resrv_perfctr_nmi_bit+0x2b/0x43
 [<fdc829b9>] nmi_create_files+0x2a/0x10e [oprofile]
 [<fdc81f52>] oprofile_create_files+0xe6/0xec [oprofile]
 [<fdc82157>] oprofilefs_fill_super+0x78/0x7e [oprofile]
 [<c018296e>] get_sb_single+0x59/0x9f
 [<fdc8208f>] oprofilefs_get_sb+0x1c/0x1e [oprofile]
 [<c01823d2>] vfs_kern_mount+0x81/0xf1
 [<c0182492>] do_kern_mount+0x38/0xde
 [<c01962b1>] do_mount+0x605/0x693
 [<c01963bf>] sys_mount+0x80/0xb5
 [<c0104270>] syscall_call+0x7/0xb
 =======================
SELinux: initialized (dev oprofilefs, type oprofilefs), uses genfs_contexts

=================================
[ INFO: inconsistent lock state ]
2.6.21-rc4-mm1 #5
---------------------------------
inconsistent {hardirq-on-W} -> {in-hardirq-W} usage.
init/1 [HC1[1]:SC0[0]:HE0:SE1] takes:
 (oprofilefs_lock){+-..}, at: [<fdc82b6e>] nmi_cpu_setup+0x15/0x4f [oprofile]
{hardirq-on-W} state was registered at:
  [<c0140c15>] __lock_acquire+0x4e8/0xceb
  [<c0141491>] lock_acquire+0x79/0x93
  [<c033eb3f>] _spin_lock+0x35/0x42
  [<fdc82347>] oprofilefs_ulong_from_user+0x4e/0x74 [oprofile]
  [<fdc81fc7>] depth_write+0x27/0x43 [oprofile]
  [<c0180afa>] vfs_write+0xd1/0x15a
  [<c018112a>] sys_write+0x3d/0x72
  [<c0104270>] syscall_call+0x7/0xb
  [<ffffffff>] 0xffffffff
irq event stamp: 1022800
hardirqs last  enabled at (1022799): [<c01042b8>] restore_nocheck+0x12/0x15
hardirqs last disabled at (1022800): [<c0104cf1>] call_function_interrupt+0x29/0x38
softirqs last  enabled at (1022784): [<c0128eb4>] __do_softirq+0xe4/0xea
softirqs last disabled at (1022779): [<c0128ef3>] do_softirq+0x39/0x55

l *0xc01042b8
0xc01042b8 is at include2/asm/bitops.h:246.
241     static int test_bit(int nr, const volatile void * addr);
242     #endif
243
244     static __always_inline int constant_test_bit(int nr, const volatile unsigned long *addr)
245     {
246             return ((1UL << (nr & 31)) & (addr[nr >> 5])) != 0;
247     }
248
249     static inline int variable_test_bit(int nr, const volatile unsigned long * addr)
250     {

l *0xc0104cf1
0xc0104cf1 is at include2/asm/bitops.h:246.
241     static int test_bit(int nr, const volatile void * addr);
242     #endif
243
244     static __always_inline int constant_test_bit(int nr, const volatile unsigned long *addr)
245     {
246             return ((1UL << (nr & 31)) & (addr[nr >> 5])) != 0;
247     }
248
249     static inline int variable_test_bit(int nr, const volatile unsigned long * addr)
250     {

l *0xc0128eb4
0xc0128eb4 is in __do_softirq (/mnt/md0/devel/linux-mm/kernel/softirq.c:252).
247
248             trace_softirq_exit();
249
250             account_system_vtime(current);
251             _local_bh_enable();
252     }
253
254     #ifndef __ARCH_HAS_DO_SOFTIRQ
255
256     asmlinkage void do_softirq(void)

l *0xc0128ef3
0xc0128ef3 is in do_softirq (/mnt/md0/devel/linux-mm/kernel/softirq.c:271).
266             pending = local_softirq_pending();
267
268             if (pending)
269                     __do_softirq();
270
271             local_irq_restore(flags);
272     }
273
274     EXPORT_SYMBOL(do_softirq);
275


other info that might help us debug this:
2 locks held by init/1:
 #0:  (tasklist_lock){..??}, at: [<c01261b6>] do_wait+0x54/0xba4
 #1:  (policy_rwlock){..??}, at: [<c01ef326>] security_compute_av+0x4f/0xbf

l *0xc01261b6
0xc01261b6 is in do_wait (include2/asm/current.h:11).
6
7       struct task_struct;
8
9       static __always_inline struct task_struct *get_current(void)
10      {
11              return read_pda(pcurrent);
12      }
13
14      #define current get_current()
15

l *0xc01ef326
0xc01ef326 is in security_compute_av (/mnt/md0/devel/linux-mm/security/selinux/ss/services.c:527).
522                     return 0;
523             }
524
525             POLICY_RDLOCK;
526
527             scontext = sidtab_search(&sidtab, ssid);
528             if (!scontext) {
529                     printk(KERN_ERR "security_compute_av:  unrecognized SID %d\n",
530                            ssid);
531                     rc = -EINVAL;


stack backtrace:
 [<c0105256>] show_trace_log_lvl+0x1a/0x2f
 [<c010597b>] show_trace+0x12/0x14
 [<c0105a3d>] dump_stack+0x16/0x18
 [<c013f327>] print_usage_bug+0x140/0x14a
 [<c013fbbf>] mark_lock+0xc9/0x510
 [<c0140b86>] __lock_acquire+0x459/0xceb
 [<c0141491>] lock_acquire+0x79/0x93
 [<c033eb3f>] _spin_lock+0x35/0x42
 [<fdc82b6e>] nmi_cpu_setup+0x15/0x4f [oprofile]
 [<c0113b63>] smp_call_function_interrupt+0x3a/0x56
 [<c0104cfb>] call_function_interrupt+0x33/0x38
 [<c01ef380>] security_compute_av+0xa9/0xbf
 [<c01e2649>] avc_has_perm_noaudit+0x1cf/0x490
 [<c01e34da>] avc_has_perm+0x28/0x58
 [<c01e3cd7>] task_has_perm+0x2d/0x2f
 [<c01e6e74>] selinux_task_wait+0x2f/0x31
 [<c0126295>] do_wait+0x133/0xba4
 [<c0126d36>] sys_wait4+0x30/0x32
 [<c0126d5f>] sys_waitpid+0x27/0x29
 [<c01041e6>] sysenter_past_esp+0x5f/0x99
 =======================

http://www.stardust.webpages.pl/files/tbf/bitis-gabonica/2.6.21-rc4-mm1/mm-dmesg
http://www.stardust.webpages.pl/files/tbf/bitis-gabonica/2.6.21-rc4-mm1/mm-config

Regards,
Michal

-- 
Michal K. K. Piotrowski
LTG - Linux Testers Group (PL)
(http://www.stardust.webpages.pl/ltg/)
LTG - Linux Testers Group (EN)
(http://www.stardust.webpages.pl/linux_testers_group_en/)

2.6.21-rc4-mm1

[Andrew Morton]

Temporarily at

  http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/

Will appear later at

  ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/



- Restored the RSDL CPU scheduler (a new version thereof)



Boilerplate:

- See the `hot-fixes' directory for any important updates to this patchset.

- To fetch an -mm tree using git, use (for example)

  git-fetch git://git.kernel.org/pub/scm/linux/kernel/git/smurf/linux-trees.git tag v2.6.16-rc2-mm1
  git-checkout -b local-v2.6.16-rc2-mm1 v2.6.16-rc2-mm1

- -mm kernel commit activity can be reviewed by subscribing to the
  mm-commits mailing list.

        echo "subscribe mm-commits" | mail majordomo@vger.kernel.org

- If you hit a bug in -mm and it is not obvious which patch caused it, it is
  most valuable if you can perform a bisection search to identify which patch
  introduced the bug.  Instructions for this process are at

        http://www.zip.com.au/~akpm/linux/patches/stuff/bisecting-mm-trees.txt

  But beware that this process takes some time (around ten rebuilds and
  reboots), so consider reporting the bug first and if we cannot immediately
  identify the faulty patch, then perform the bisection search.

- When reporting bugs, please try to Cc: the relevant maintainer and mailing
  list on any email.

- When reporting bugs in this kernel via email, please also rewrite the
  email Subject: in some manner to reflect the nature of the bug.  Some
  developers filter by Subject: when looking for messages to read.

- Occasional snapshots of the -mm lineup are uploaded to
  ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/mm/ and are announced on
  the mm-commits list.


Changes since 2.6.21-rc3-mm1:


 origin.patch
 git-acpi.patch
 git-alsa.patch
 git-arm-master.patch
 git-arm.patch
 git-avr32.patch
 git-cifs.patch
 git-cpufreq.patch
 git-powerpc.patch
 git-drm.patch
 git-dvb.patch
 git-gfs2-nmw.patch
 git-hid.patch
 git-ia64.patch
 git-ieee1394.patch
 git-infiniband.patch
 git-input.patch
 git-kbuild.patch
 git-kvm.patch
 git-leds.patch
 git-libata-all.patch
 git-md-accel.patch
 git-mmc.patch
 git-mtd.patch
 git-ubi.patch
 git-netdev-all.patch
 git-ioat.patch
 git-ocfs2.patch
 git-parisc.patch
 git-selinux.patch
 git-pciseg.patch
 git-s390.patch
 git-sh.patch
 git-scsi-misc.patch
 git-scsi-rc-fixes.patch
 git-unionfs.patch
 git-wireless.patch
 git-ipwireless_cs.patch
 git-gccbug.patch

 git trees

-uml-hostfs-fix-double-free.patch
-uml-hostfs-make-hostfs=-option-work-as-a-jail-as-intended.patch
-uml-fix-a-memory-leak-in-the-multicast-driver.patch
-uml-remove-dead-code-about-os_usr1_signal-and-os_usr1_process.patch
-uml-mark-both-consoles-as-con_anytime.patch
-uml-fix-confusion-irq-early-reenabling.patch
-uml-activate_fd-return-enomem-only-when-appropriate.patch
-uml-fix-errno-usage.patch
-x86_64-fix-2618-regression-ptrace_oldsetoptions-should-be-accepted.patch
-bluetooth-fix-socket-locking-in-hci_sock_dev_event.patch
-add-epoll-compat_-code-to-fs-compatc.patch
-check_partition-fix-error-check.patch
-uml-arch_prctl-should-set-thread-fs.patch
-connector-bugfix-for-cn_call_callback.patch
-26-altix-console-fix-for-config_debug_shirq-usage.patch
-ecryptfs-nested-locking-annotation.patch
-swsusp-disable-nonboot-cpus-before-entering-platform-suspend.patch
-paravirt-build-fixes.patch
-acpi-disabled-due-to-dmi-failure-or-blacklisted-year-should-be-noted-as-is-done-with-other-acpi-blacklisting.patch
-git-alsa-oops-fix.patch
-avr32-dma-mappingh.patch
-gregkh-driver-device-symlink.patch
-gregkh-driver-platform-reorder-platform_device_del.patch
-gregkh-driver-remove-devfs-from-maintainers.patch
-gregkh-driver-driver-core-export-device_rename.patch
-gregkh-driver-uio-irq.patch
-scheduled-removal-of-sa_xxx-interrupt-flags-fixups-4.patch
-make-drivers-char-drm-drm_vmcdrm_io_prot-static.patch
-fix-saa7146_clipping_mem-size.patch
-drivers-media-video-cpia_ppc-dont-use-_work_nar.patch
-dvb-core-fix-several-locking-related-problems.patch
-saa7134-fix-modules=n-compilation.patch
-ivtv-warning-fix.patch
-jdelvare-i2c-i2c-03-use-i2c_adapterdevparent-for-messages.patch
-jdelvare-i2c-i2c-i801-restore-initial-state.patch
-jdelvare-i2c-ds1374-check-for-workqueue-creation.patch
-crash-on-evdev-disconnect.patch
-expose-set_mode-method-so-it-can-be-wrapped.patch
-ata_piix-remove-ugly-layering-violation.patch
-pata_cmd640-multiple-updates.patch
-ide-cmd64x-fix-recovery-time-calculation-take2.patch
-mtd-maps-ck804xromc-pci_module_init-to-pci_register_driver.patch
-mtd-chips-oops-in-cfi_amdstd_sync.patch
-mtd-esb2-check-for-closed-rom-window.patch
-dilnetpc-fix-warning.patch
-mtd-correct-misspelled-preprocessor-variable.patch
-git-netdev-all-ipw2200-fix.patch
-mv643xx-ethernet-driver-irq-registration-fix.patch
-via-rhine-set-avoid_d3-for-broken-bioses.patch
-netxen-fix-warnings.patch
-e1000-fix-be-ready-for-incoming-irq-at-pci_request_irq.patch
-e1000-fix-firmware-handover-bits.patch
-e1000-fix-stop-raw-interrupts-disabled-nag-from-rt.patch
-tulip-fix-shutdown-dma-irq-race.patch
-tulip-fix-for-64-bit-mips.patch
-tulip-natsemi-dp83840a-phy-fix.patch
-nfs-fix-congestion-control-v4.patch
-nfs-nfs_getattr-cant-call-nfs_sync_mapping_range-for-non-regular-files.patch
-gregkh-pci-pci-allow-multiple-calls-to-pcim_pin_device.patch
-gregkh-pci-pcie-fix-section-mismatch-warning.patch
-gregkh-pci-pci-aer-fix-section-mismatch-warning.patch
-gregkh-pci-pci-fix-section-mismatch-warning.patch
-scatterlisth-needs-typesh.patch
-cleanup-the-includes-of-linux-pcih.patch
-gregkh-usb-usb-at91_udc-fix-more-modpost-bogosity.patch
-gregkh-usb-usb-storage-removed-duplicate-supertop-unusual_dev-entry.patch
-gregkh-usb-usb-storage-nokia-6288-unusual_devs-entry.patch
-gregkh-usb-usb-goku_udc-remove-crude-cache-coherency-code.patch
-gregkh-usb-usb-set-the-correct-interval-for-interrupt-urbs.patch
-gregkh-usb-uhci-fix-port-resume-problem.patch
-gregkh-usb-usb-ratelimit-debounce-error-messages.patch
-gregkh-usb-usb-kill-dead-code-from-hubc.patch
-gregkh-usb-usb-new-device-ids-for-cp2101-driver.patch
-gregkh-usb-usb-add-ql355p-power-supply-ids-to-fdti_sio.patch
-gregkh-usb-usb-add-additional-pids-in-ftdi_sio.patch
-gregkh-usb-usb-serial-fix-shutdown-device_unregister-order.patch
-gregkh-usb-usb-ftdi_sio-use-port_probe-port_remove-thereby-fixing-access-to-the-latency_timer.patch
-gregkh-usb-usb-rts-dtr-signal-patch-for-airprime-driver.patch
-gregkh-usb-usb-fix-usb-serial-device-naming-bug.patch
-gregkh-usb-usb-further-fix-for-usb-serial.patch
-gregkh-usb-usb-ipaqc-additional-devices.patch
-gregkh-usb-usbnet-dm9501-add-corega-fether-usb-txc-support.patch
-usbatm-create-sysfs-link-device-from-atm-class-device.patch
-usb-elan-ftdi-check-for-workqueue-creation-v2.patch
-cxacru-export-detailed-device-info-through-sysfs-updated.patch
-maintainers-add-myself-for-cxacru-in-drivers-usb-atm.patch
-x86_64-mm-defconfig-update.patch
-x86_64-mm-i386-defconfig-update.patch
-x86_64-wire-up-compat-sched_rr_get_interval2.patch
-x86_64-fix-section-mismatch-warnings.patch

 Merged into mainline or a subsystem tree

+return-eperm-not-echild-on-security_task_wait-failure.patch
+splice-dont-steal.patch
+splice-dont-readpage.patch
+shmem-fix-bug-in-shmem_writepage.patch
+shmem-dont-release-lock-for-hole-punching.patch

 Possible 2.6.21 queue.

-macintosh-mangle-caps-lock-events-on-adb-keyboards.patch

 Dropped

+git-alsa-fixup.patch

 Fix rejects in git-alsa.

+drivers-char-agp-convert-to-generic-boolean.patch

 AGP cleanup

+git-arm-master.patch

 New ARM tree

+remove-unused-header-file-arch-arm-mach-s3c2410-basth.patch

 Cleanup

+cifs-remove-unneeded-checks.patch

 CIFS cleanup

+remove-unused-header-file-arch-ppc-syslib-cpc710h.patch
+remove-unused-header-file-arch-powerpc-platforms-83xx-mpc834x_itxh.patch
+powerpc-fix-breakage-caused-by-72486f1f8f0a2bc828b9d30cf4690cf2dd6807fc.patch
+ibmebus-uevent-support.patch
+ocotea-board-ntpd-complains-that-the-frequency-error-exceeds-the-tolerance.patch

 ppc stuff

+gregkh-driver-driver-core-fix-device_add-error-path.patch
+gregkh-driver-driver-core-fix-namespace-issue-with-devices-assigned-to-classes.patch
+gregkh-driver-dev_printk-and-new-style-class-devices.patch
+gregkh-driver-driver-core-use-attribute-groups-in-struct-device_type.patch
+gregkh-driver-named-device_type.patch
+gregkh-driver-uio-hilscher-cif-card-driver.patch

 Driver tree updates

+kobject-kobject_shadow_add-cleanup.patch
+driver-core-handles-kobject_uevent-failure-while-device_add.patch
+driver-core-handle-sysfs_op-failure-while-device_add.patch

 Driver things

+jdelvare-i2c-i2c-i801-restore-initial-state.patch
+jdelvare-i2c-ds1374-check-for-workqueue-creation.patch
+jdelvare-i2c-i2c-09-i2c-class-attribute-cleanup.patch
+jdelvare-i2c-i2c-10-rename-dev_to_i2c_adapter.patch
+jdelvare-i2c-scx200_acb-fix-pci-device-reference-count.patch
+jdelvare-i2c-i2c-parport-fix-race-on-unload.patch
+jdelvare-i2c-i2c-parport-light-to-platform-driver.patch
+jdelvare-i2c-i2c-elektor-to-isa-driver.patch
+jdelvare-i2c-i2c-pca-isa-to-isa-driver.patch
+jdelvare-i2c-i2c-algo-bit-document-udelay.patch
+jdelvare-i2c-i2c-01-i2c-stack-can-probe.patch
+jdelvare-i2c-i2c-02-i2c-stack-can-remove.patch
+jdelvare-i2c-i2c-03-i2c-document-probe-and-remove.patch
+jdelvare-i2c-i2c-04-i2c_board_info-and-i2c_new_device.patch
+jdelvare-i2c-i2c-05-i2c_add_numbered_adapter.patch
+jdelvare-i2c-i2c-06-export_symbol-cleanup.patch
+jdelvare-i2c-i2c-07-i2c_bit_add_numbered_bus.patch
+jdelvare-i2c-i2c-isa-exports-only-to-i2c-isa.patch
+jdelvare-i2c-i2c-del-driver-returns-void.patch
+jdelvare-i2c-i2c-rpx-will-be-removed.patch

 I2C tree updates

+jdelvare-hwmon-hwmon-w83627hf-cleanups.patch
+jdelvare-hwmon-hwmon-w83627hf-to-platform-driver.patch
+jdelvare-hwmon-hwmon-sysfs-interface-add-fan-target.patch
+jdelvare-hwmon-hwmon-smsc47m1-to-platform-driver.patch
+jdelvare-hwmon-hwmon-smsc47m1-use-drvname-consistently.patch
+jdelvare-hwmon-hwmon-max6650-new-driver.patch
+jdelvare-hwmon-hwmon-lm78-to-platform-driver.patch
+jdelvare-hwmon-hwmon-lm78-less-client-centric.patch
+jdelvare-hwmon-hwmon-lm78-use-dynamic-attributes.patch
+jdelvare-hwmon-hwmon-lm75-use-dynamic-attributes.patch

 hwmon tree updates

-fix-locking-in-mousedev.patch

 Dropped - git-input changes broke it.

+ata_generic-remove-all-the-crud-again-and-use-cable.patch
+pata_ali-remove-all-the-crap-again-and-switch-to.patch
+pata_amd-remove-all-the-crud-and-restore-the-cable-detect.patch
+pata_cs5535-re-remove-all-the-crap-and-switch-to-the-cable.patch
+pata_cypress-re-remove-all-the-crap-and-switch-back-to.patch
+pata_netcell-re-remove-all-the-crud.patch
+pata_qdi-restore-cable-detect.patch
+pata_sl82c105-restore-cable-detect-method.patch
+pata_winbond-restore-cable-method.patch
+libata-acpi-add-infrastructure-for-drivers-to-use.patch
+pata_optidma-rework-for-cable-detect-and-to-remove.patch
+pata_acpi-restore-driver.patch
+ata-ncq-is-broken-on-maxtor-6l250s0.patch

 pata/sata things

+ide-ide-fix-pio-setup-on-resume-for-atapi.patch
+ide-it821x-pio-mode-setup-fixes.patch
+ide-siimage-swdma-mask-fix.patch
+ide-ide-cris-fix-speedproc-and-swdma-mask.patch
+ide-ide-dma-off-quietly-fix.patch
+ide-ide-no-mdma-udma-sharing-filter.patch
+ide-ide-tune-dma-2.patch
+ide-cs5530-sc1200-dma-cleanup.patch
+ide-cs5530-sc1200-add-speedproc.patch
+ide-sl82c105-add-speedproc.patch
+ide-ide-dma-enable.patch
+ide-ide-check-dma-words-validity.patch
+ide-ide-remove-ide-use-dma.patch

 IDE tree updates

+revert-rm-pointless-dmaengine-exports.patch

 Revert a merged patch to make git-md-accel.patch easier to apply.

-git-md-accel-fixup.patch

 Unneeded

+git-md-accel-fix.patch

 Fix git-md-accel tree

-remove-fs-jffs2-ioctlc.patch

 Dropped

+mmc-consolidate-voltage-definitions.patch
+mmc-fix-handling-of-low-voltage-cards.patch
+remove-mmc_deselect_cards.patch

 MMC things

+mtd-pmc-msp71xx-flash-rootfs-mappings.patch
+jffs2-delete-everything-related-to-obsolete-jffs2_proc.patch
+romfs-printk-format-warnings.patch

 MTD stuff

+baycom_ser_fdx-also-allow-i-o-ports-=-0x1000-and-enhanced.patch
+remove-unused-header-file-drivers-net-skfp-h-lnkstath.patch
+tulip-fix-shutdown-dma-irq-race.patch
+sun3-3x-lance-trivial-fix-improved.patch
+remove-unused-header-file-drivers-net-wan-lmc-lmc_mediah.patch
+smc-superio-chip-lpc47n227-not-identified-properly.patch

 netdev things

+pcmcia-delete-obsolete-pcmcia_ioctl-feature.patch

 PCMCIA cleanup

+gregkh-pci-pciehp-event-handling-rework.patch
+gregkh-pci-pciehp-adapt-to-device-driver-model.patch
+gregkh-pci-pci-scatterlisth-needs-typesh.patch
+gregkh-pci-pci-cleanup-the-includes-of-linux-pcih.patch

 PCI tree updates

-resurrect-sdev.patch
-bug-in-gdthc-crashing-machine.patch

 Dropped

+make-elv_register-output-atomic.patch

 Block cleanup

+unionfs-sioq-not-__exit.patch

 unionfs fixlet

+gregkh-usb-usb-fix-usb-serial-regression.patch
+gregkh-usb-usb-two-more-device-ids-for-dm9601-usbnet-driver.patch
+gregkh-usb-usb-razr-v3i-unusual_devs.patch
+gregkh-usb-usb-necessary-update-for-mos7720-driver.patch
+gregkh-usb-airprime-usb-id-for-novatel-ev620-mini-pci-e-card.patch
+gregkh-usb-ub-bind-to-first-endpoint-not-to-last.patch
+gregkh-usb-libusual-change-block-scope-variable-to-function-scope.patch
+gregkh-usb-usbcore-move-usb_autosuspend_work.patch
+gregkh-usb-usb-unnecessary-gfp_atomic-in-mos7720-driver.patch
+gregkh-usb-usbatm-create-sysfs-link-device-from-atm-class-device-to-usb-interface.patch
+gregkh-usb-usb-cxacru-export-detailed-device-info-through-sysfs.patch
+gregkh-usb-usb-maintainers-cxacru.patch
+gregkh-usb-usb-fix-race-in-hcd-removal.patch
+gregkh-usb-ehci-fsl-change-si_ctrl-pri_ctrl-register-offsets-according-to-errata.patch
+gregkh-usb-mos7720-update.patch
+gregkh-usb-usb-help-text-for-mos-7720-driver.patch
+gregkh-usb-usb-fix-gadget-serial-response-on-usb_cdc_req_set_line_coding.patch
+gregkh-usb-usb-separate-autosuspend-from-external-suspend.patch
+gregkh-usb-usb-allow-autosuspend-delay-to-equal-0.patch
+gregkh-usb-ehci-add-delay-to-bus_resume-before-accessing-ports.patch
+gregkh-usb-usb-usb_serial_driver-insufficient-for-clean-disconnect-handling.patch

 USB tree updates

+usb-serial-io_edgeport-convert-to-generic-boolean.patch
+usb-serial-whiteheat-convert-to-generic-boolean.patch

 USB stuff

+hack-to-make-wireless-work.patch

 The wireless tree seems to have broken the firmware loader.  Work around it.

+i386-x86_64-early_printkc-make-simnow_init-static.patch
+make-arch-i386-kernel-vmicvmi_pmd_clear-static.patch
+i386-fix-gdts-number-of-quadwords-in.patch
+i386-fix-usage-of-mtune-when-x86_generic=y-or-config_mcore2=y.patch
+x86_64-configurable-fake-numa-node-sizes-fix.patch
+lguest-the-host-code-lgko-cleanup-allocate-separate-pages-for-switcher-code.patch
+lguest-the-host-code-lgko-cleanup-clean-up-regs-save-restore.patch
+lguest-the-host-code-lgko-pin-stack-page-optimization.patch
+lguest-use-read-only-pages-rather-than-segments-to-protect-high-mapped-switcher.patch
+lguest-optimize-away-copy-in-and-out-of-per-cpu-guest-pages.patch
+lguest-dont-crash-host-on-nmi.patch
+lguest-trivial-guest-block-driver-lguest-block-device-speedup.patch
+lguest-documentatation-and-example-launcher-bridging-support-in-example-code.patch
+lguest-documentatation-and-example-launcher-bridging-support-in-example-codelguest-documentation-fixes.patch
+x86_64-remove-duplicated-code-for-reading-control-registers.patch
+introduce-load_tls-to-the-for-loop.patch
+remove-unused-set_seg_base.patch
+clarify-config_reorder-explanation.patch
+mm-inconsistent-use-of-node-ids.patch
+dma_ops-as-const.patch
+allow-i386-crash-kernels-to-handle-x86_64-dumps.patch
+allow-i386-crash-kernels-to-handle-x86_64-dumps-fix.patch
+prevent-acpi-quirk-warning-mass-spamming-in-logs.patch
+prevent-acpi-quirk-warning-mass-spamming-in-logs-tidy.patch

 x86/x86_64 updates

-xfs-use-xfs_get_buf_noaddr-for-iclogs.patch
-xfs-stop-using-kmalloc-in-xfs_buf_get_noaddr.patch

 Dropped - they need updating.

+uhci-fix-problem-caused-by-lack-of-terminating-qh.patch

 USB fix

+move-free-pages-between-lists-on-steal-fix-2.patch
+move-free-pages-between-lists-on-steal-avoid-unsafe-use-of-struct-pages-in-move_freepages-when-config_holes_in_zone-is-set.patch

 Fix move-free-pages-between-lists-on-steal.atch some more

+fix-corruption-of-memmap-on-ia64-sparsemem-when-mem_section-is-not-a-power-of-2.patch

 ia64 fix

-mm-debug-check-for-the-fault-vs-invalidate-race.patch
-mm-debug-check-for-the-fault-vs-invalidate-race-tidy.patch

 Drop this debug patch: the fault-vs-invalidate patches cause the BUG_ON() to
 trigger.

+mm-merge-nopfn-into-fault-fix.patch

 Fix mm-merge-nopfn-into-fault.patch

+lumpy-reclaim-v4.patch
+lumpy-back-out-removal-of-active-check-in-isolate_lru_pages.patch
+lumpy-only-count-taken-pages-as-scanned.patch

 Lumpy reclaim came back

+mm-filemapc-fix-mark_page_accessed-logic.patch

 Tighten use-once logic

+bias-the-location-of-pages-freed-for-min_free_kbytes-in-the-same-max_order_nr_pages-blocks.patch
+bias-the-location-of-pages-freed-for-min_free_kbytes-in-the-same-max_order_nr_pages-blocks-tidy.patch

 More page allocator work

+blackfin-arch-balance-parenthesis-in-macros.patch

 blackfin fix

+remove-unused-header-file-arch-m68k-atari-atasoundh.patch

 m68k cleanup

+remove-unused-header-file-drivers-serial-crisv10h.patch
+cris-check-for-memory-allocation.patch

 Cris updates

+remove-unused-header-file-arch-um-kernel-tt-include-mode_kern-tth.patch

 UML cleanup

+ext3-dirindex-error-pointer-issues-fix.patch

 Fix ext3-dirindex-error-pointer-issues.patch

+fix-race-between-proc_readdir-and-remove_proc_entry.patch
+proc-remove-pathetic-deleted-warn_on.patch

 Fiddle with /proc races some more

+complain-about-missing-system-calls.patch
+complain-about-missing-system-calls-update.patch
+proc-maps-protection.patch
+proc-maps-protection-fix.patch
+proc-maps-protection-tidy.patch
+proc-maps-protection-fix-2.patch
+remove-unused-header-file-include-linux-elfnoteh.patch
+remove-unused-header-file-drivers-message-i2o-i2o_lanh.patch
+remove-unused-header-file-drivers-char-digih.patch
+array_size-check-for-type.patch
+drivers-char-synclinkc-check-kmalloc-return-value.patch
+procfs-reorder-struct-pid_dentry-to-save-space-on-64bit-archs-and-constify-them.patch
+vfs-delay-the-dentry-name-generation-on-sockets-and.patch
+tty-i386-x86_64-arbitary-speed-support.patch
+kprobes-make-kprobesymbol_name-const.patch
+fix-cycladesh-for-x86_64-and-probably-others.patch
+fix-cycladesh-for-x86_64-and-probably-others-fix.patch
+cyclades-remove-custom-types.patch
+splice-partial-write-handling-fix.patch
+small-fixes-for-jsm-driver.patch
+jsm-driver-fix-for-linuxpps-support.patch
+serial-allocate-minor-device-numbers-for.patch
+as-fix-antic_expire-check.patch
+rtc-add-rtc-rs5c313-driver.patch
+rtc-add-rtc-rs5c313-driver-tidy.patch
+rtc-add-rtc-rs5c313-driver-is-busted.patch
+rtc-add-rtc-class-driver-for-the-maxim-max6900.patch
+fix-rmmod-read-write-races-in-proc-entries.patch
+getrusage-fill-ru_inblock-and-ru_oublock-fields-if-possible.patch
+futex-restartable-futex_wait.patch
+futex-restartable-futex_wait-fix.patch
+proc-oom_score-oops-re-badness.patch
+fixes-and-cleanups-for-earlyprintk-aka-boot-console.patch
+tty-remove-unnecessary-export-of-proc_clear_tty.patch
+tty-simplify-calling-of-put_pid.patch
+tty-introduce-no_tty-and-use-it-in-selinux.patch
+tty-in-tiocsctty-when-we-steal-a-tty-hang-it-up.patch
+reiserfs-proc-support-requires-proc_fs.patch

 Misc

+make-drivers-isdn-capi-capiutilccdebbuf_alloc-static.patch
+drivers-isdn-hardware-eicon-remove-unused-header-files.patch

 ISDN updates

+lists-add-list-splice-tail.patch
+sched-remove-sleepavg-from-proc.patch
+sched-remove-noninteractive-flag.patch
+sched-dont-renice-kernel-threads.patch
+sched-implement-rsdl-cpu-scheduler.patch
+sched-document-rsdl-cpu-scheduler.patch

 RSDL CPU scheduler

-rcu-split-classic-rcu.patch
-rcu-softirq-for-rcu.patch
-rcu-fix-barriers.patch
-rcu-preemptible-rcu.patch
-rcu-debug-trace-for-rcu.patch

 Dropped.  It's too early to merge preemptible RCU, and the ther patches had
 dependencies on it.

-utrace-prep.patch
+proc-maps-protection-vs-utrace.patch
+utrace-utrace-tracehook-um.patch
-revert-utrace-prep-2.patch
+avr32-implement-utrace-support.patch
+utrace-printk-borkage.patch
+ptrace-needs-proc_fs.patch

 utrace updates

+some-grammatical-fixups-and-additions-to-atomich-kernel-doc.patch

 Cleanup

+udf-possible-null-pointer-dereference-while-load_partition.patch

 UDF fix

+add-ability-to-keep-track-of-callers-of-symbol_getput.patch
+add-ability-to-keep-track-of-callers-of-symbol_getput-update.patch
+update-mtd-use-of-symbol_getput.patch
+update-dvb-use-of-symbol_getput.patch

 Fiddle with symbol_get()

+attach_pid-with-struct-pid-parameter.patch
+statically-initialize-struct-pid-for-swapper.patch
+explicitly-set-pgid-and-sid-of-init-process.patch
+use-struct-pid-parameter-in-copy_process.patch
+# remove-the-likelypid-check-in-copy_process.patch: Oleg issues
+remove-the-likelypid-check-in-copy_process.patch
+use-task_pgrp-task_session-in-copy_process.patch
+kill-unused-sesssion-and-group-values-in-rocket-driver.patch
+fix-some-coding-style-errors-in-autofs.patch
+replace-pid_t-in-autofs-with-struct-pid-reference.patch

 PID management updates

+revoke-special-mmap-handling.patch
+revoke-special-mmap-handling-vs-fault-vs-invalidate.patch
+revoke-core-code.patch
+revoke-core-code-misc-fixes.patch
+revoke-core-code-fix-shared-mapping-revoke.patch
+revoke-core-code-move-magic.patch
+revoke-support-for-ext2-and-ext3.patch
+revoke-add-documentation.patch
+revoke-wire-up-i386-system-calls.patch

 revoke() syscall

+readahead-state-based-method-check-node-id.patch
+readahead-state-based-method-decouple-readahead_ratio-from-growth_limit.patch
+readahead-state-based-method-cancel-lookahead-gracefully.patch
+readahead-thrashing-recovery-method-check-unbalanced-aging.patch
+readahead-thrashing-recovery-method-refill-holes.patch
+readahead-call-scheme-cleanup.patch
+readahead-call-scheme-catch-thrashing-on-lookahead-time.patch
+readahead-remove-parameter-ra_max-from-thrashing_recovery_readahead.patch
+readahead-remove-parameter-ra_max-from-adjust_rala.patch
+readahead-state-based-method-protect-against-tiny-size.patch
+readahead-rename-state_based_readahead-to-clock_based_readahead.patch
+readahead-account-i-o-block-times-for-stock-readahead.patch
+readahead-rescue_pages-updates.patch
+readahead-remove-noaction-shrink-events.patch

 Update the readahead patches in -mm.

+remove-unused-header-file-drivers-video-riva-nv4refh.patch
+fbdev-avoid-vertical-overflow-when-making-space-for-the-logo.patch
+fbdev-fb_do_show_logo-updates.patch
+fbdev-correct-image-offsets-when-rotating-logo.patch
+radeonfb-add-support-for-radeon-xpress-200m.patch

 fbdev updates

+statistics-infrastructure-simplify-statistics-debugfs-write-function.patch

 Update statistics patches in -mm.

-ia64-enable-config_debug_spinlock_sleep.patch
-msi-debug-code.patch

 Dropped.




All 934 patches:

ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/patch-list