2008-12-17 12:25:59

by Stephen Rothwell

[permalink] [raw]
Subject: linux-next: Tree for December 17

Hi all,

Changes since 20081216:

Undropped tree:
v4l-dvb
lblnet

Dropped trees (temporarily):
scsi (build problem)
mtd (build problems)
semaphore-removal (due to unfixed conflicts against Linus' tree)
cpu_alloc (build problem)
perfmon3 (concerns from the x86 team)
nommu (build problem)
boot-params (build problems)
audit (difficult conflicts)

The pci tree lost its conflict.

The net tree lost a conflict.

----------------------------------------------------------------------------

I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git
(patches at
http://www.kernel.org/pub/linux/kernel/people/sfr/linux-next/). If you
are tracking the linux-next tree using git, you should not use "git pull"
to do so as that will try to merge the new linux-next release with the
old one. You should use "git fetch" as mentioned in the FAQ on the wiki
(see below).

You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log files
in the Next directory. Between each merge, the tree was built with
a ppc64_defconfig for powerpc and an allmodconfig for x86_64. After the
final fixups (if any), it is also built with powerpc allnoconfig,
44x_defconfig and allyesconfig (minus CONFIG_PROFILE_ALL_BRANCHES) and
i386, sparc and sparc64 defconfig.

Below is a summary of the state of the merge.

We are up to 133 trees (counting Linus' and 15 trees of patches pending for
Linus' tree), more are welcome (even if they are currently empty).
Thanks to those who have contributed, and to those who haven't, please do.

Status of my local build tests will be at
http://kisskb.ellerman.id.au/linux-next . If maintainers want to give
advice about cross compilers/configs that work, we are always open to add
more builds.

Thanks to Jan Dittmer for adding the linux-next tree to his build tests
at http://l4x.org/k/ , the guys at http://test.kernel.org/ and Randy
Dunlap for doing many randconfig builds.

There is a wiki covering stuff to do with linux-next at
http://linux.f-seidel.de/linux-next/pmwiki/ . Thanks to Frank Seidel.

--
Cheers,
Stephen Rothwell [email protected]

$ git checkout master
$ git reset --hard stable
Merging origin/master
Merging arm-current/master
Merging m68k-current/for-linus
Merging powerpc-merge/merge
Merging sparc-current/master
Merging scsi-rc-fixes/master
Merging net-current/master
Merging sound-current/for-linus
Merging pci-current/for-linus
Merging wireless-current/master
Merging kbuild-current/master
Merging quilt/driver-core.current
Merging quilt/usb.current
Merging cpufreq-current/fixes
Merging input-current/for-linus
Merging md-current/for-2.6.26
Merging audit-current/for-linus
Merging dwmw2/master
Merging arm/devel
Merging avr32/avr32-arch
Merging blackfin/for-linus
Merging cris/for-next
Merging ia64/test
Merging m68k/for-next
Merging m68knommu/for-next
Merging mips/mips-for-linux-next
Merging parisc/master
Merging powerpc/next
Merging 4xx/next
Merging galak/next
Merging pxa/for-next
Merging s390/features
CONFLICT (content): Merge conflict in drivers/char/Makefile
Merging sh/master
Merging sparc/master
Merging x86/auto-x86-next
Merging xtensa/master
Merging quilt/driver-core
CONFLICT (content): Merge conflict in arch/powerpc/platforms/85xx/mpc85xx_mds.c
Merging quilt/usb
Merging tip-core/auto-core-next
Merging cpus4096/auto-cpus4096-next
CONFLICT (content): Merge conflict in scripts/recordmcount.pl
Merging ftrace/auto-ftrace-next
Merging genirq/auto-genirq-next
Merging safe-poison-pointers/auto-safe-poison-pointers-next
Merging sched/auto-sched-next
Merging stackprotector/auto-stackprotector-next
Merging timers/auto-timers-next
Merging pci/linux-next
Merging quilt/device-mapper
CONFLICT (content): Merge conflict in drivers/md/dm.c
Merging hid/for-next
Merging quilt/i2c
Merging quilt/jdelvare-hwmon
Merging quilt/kernel-doc
Merging jfs/next
Merging kbuild/master
Merging quilt/ide
Merging libata/NEXT
Merging nfs/linux-next
Merging xfs/master
CONFLICT (content): Merge conflict in fs/xfs/xfs_rename.c
Merging infiniband/for-next
Merging acpi/test
Merging nfsd/nfsd-next
Merging ieee1394/for-next
Merging ubi/linux-next
Merging kvm/master
CONFLICT (content): Merge conflict in arch/x86/kernel/reboot.c
Merging dlm/next
Merging ocfs2/linux-next
Merging ext4/next
Merging async_tx/next
Merging udf/for_next
Merging net/master
CONFLICT (delete/modify): arch/sparc64/kernel/idprom.c deleted in HEAD and modified in net/master. Version net/master of arch/sparc64/kernel/idprom.c left in tree.
CONFLICT (content): Merge conflict in fs/lockd/host.c
CONFLICT (content): Merge conflict in fs/lockd/mon.c
$ git rm -f arch/sparc64/kernel/idprom.c
Applying: net: async_tx merge fix
Merging mtd/master
CONFLICT (content): Merge conflict in arch/arm/mach-pxa/corgi.c
CONFLICT (content): Merge conflict in arch/arm/mach-pxa/poodle.c
CONFLICT (content): Merge conflict in arch/arm/mach-pxa/spitz.c
Merging wireless/master
Merging crypto/master
Merging vfs/for-next
Merging sound/for-next
CONFLICT (content): Merge conflict in sound/drivers/pcsp/pcsp.c
Applying: sound: fixup for timers tree interaction
Merging cpufreq/next
Merging v9fs/for-next
Merging rr_cpumask/master
CONFLICT (content): Merge conflict in arch/x86/kernel/io_apic.c
CONFLICT (content): Merge conflict in kernel/sched.c
CONFLICT (content): Merge conflict in kernel/sched_stats.h
Merging quilt/rr
CONFLICT (content): Merge conflict in kernel/sched.c
Merging cifs/master
CONFLICT (content): Merge conflict in fs/cifs/connect.c
Applying: cifs: update for new IP4/6 address printing
Merging mmc/next
Merging gfs2/master
Merging input/next
Merging semaphore/semaphore
Merging bkl-removal/bkl-removal
CONFLICT (content): Merge conflict in fs/ioctl.c
Merging ubifs/linux-next
Merging lsm/for-next
Merging block/for-next
CONFLICT (content): Merge conflict in fs/bio.c
Merging embedded/master
Merging firmware/master
CONFLICT (content): Merge conflict in drivers/net/tg3.c
CONFLICT (content): Merge conflict in firmware/Makefile
CONFLICT (content): Merge conflict in firmware/WHENCE
Merging pcmcia/master
Merging battery/master
Merging leds/for-mm
Merging backlight/for-mm
Merging kgdb/kgdb-next
Merging slab/for-next
Merging uclinux/for-next
Merging md/for-next
Merging kmemcheck/auto-kmemcheck-next
CONFLICT (content): Merge conflict in MAINTAINERS
CONFLICT (content): Merge conflict in arch/x86/mm/Makefile
CONFLICT (content): Merge conflict in mm/slab.c
CONFLICT (content): Merge conflict in mm/slub.c
Merging generic-ipi/auto-generic-ipi-next
Merging mfd/for-next
Merging hdlc/hdlc-next
Merging drm/drm-next
Merging voltage/for-next
Merging security-testing/next
CONFLICT (content): Merge conflict in drivers/char/tty_audit.c
CONFLICT (content): Merge conflict in fs/cifs/cifs_fs_sb.h
CONFLICT (content): Merge conflict in fs/ocfs2/namei.c
CONFLICT (content): Merge conflict in fs/xfs/linux-2.6/xfs_cred.h
CONFLICT (content): Merge conflict in fs/xfs/linux-2.6/xfs_globals.h
CONFLICT (content): Merge conflict in fs/xfs/linux-2.6/xfs_ioctl.c
CONFLICT (content): Merge conflict in fs/xfs/xfs_vnodeops.h
Merging lblnet/master
CONFLICT (content): Merge conflict in Documentation/feature-removal-schedule.txt
Merging quilt/ttydev
CONFLICT (content): Merge conflict in fs/devpts/inode.c
Merging agp/agp-next
Merging oprofile/auto-oprofile-next
Merging fastboot/auto-fastboot-next
Merging sparseirq/auto-sparseirq-next
Merging iommu/auto-iommu-next
Merging uwb/for-upstream
Merging watchdog/master
CONFLICT (content): Merge conflict in drivers/watchdog/iTCO_wdt.c
Merging proc/proc
Merging bdev/master
Merging dwmw2-iommu/master
Merging cputime/cputime
CONFLICT (content): Merge conflict in kernel/sched.c
Merging osd/linux-next
Merging fatfs/master
Merging fuse/for-next
Merging jc_docs/docs-next
Merging boot-params/master
CONFLICT (content): Merge conflict in arch/arm/kernel/setup.c
CONFLICT (content): Merge conflict in arch/parisc/kernel/setup.c
CONFLICT (content): Merge conflict in arch/sh/boards/mach-migor/setup.c
CONFLICT (content): Merge conflict in init/main.c
$ git reset --hard
Merging trivial/for-next
Merging quilt/staging
CONFLICT (delete/modify): drivers/staging/winbond/linux/wbusb.c deleted in quilt/staging and modified in HEAD. Version HEAD of drivers/staging/winbond/linux/wbusb.c left in tree.
CONFLICT (content): Merge conflict in drivers/staging/wlan-ng/p80211netdev.c
CONFLICT (content): Merge conflict in drivers/staging/wlan-ng/p80211wext.c
$ git rm -f drivers/staging/winbond/linux/wbusb.c
Merging scsi-post-merge/master
Merging v4l-dvb/master
Created commit e1ad45d: Revert "Merge commit 'mtd/master'"


Attachments:
(No filename) (8.49 kB)
(No filename) (197.00 B)
Download all attachments
Subject: Re: linux-next: Tree for December 17 (Radeon DRM BUG)

tOn Thursday 18 December 2008, Dave Airlie wrote:
> On Thu, 2008-12-18 at 20:00 +0100, Bartlomiej Zolnierkiewicz wrote:
> > On Thursday 18 December 2008, Dave Airlie wrote:
> > > On Thu, Dec 18, 2008 at 10:14 AM, Kevin Winchester
> > > <[email protected]> wrote:
> > > > Stephen Rothwell wrote:
> > > >>
> > > >> Hi all,
> > > >>
> > > >>
> > > >
> > > > I get the following BUG in the radeon drm code with today's linux-next when
> > > > I run "startx". I have not built or tested linux-next in a while, but the
> > > > problem definitely does not occur in mainline.
> >
> > [...]
> >
> > This reminds me that drm tree in linux-next still results in BSOD (Black
> > Screen Of Death) on starting X for me (as reported on Saturday [1]).
> >
> > Actually there is more to it as I discovered that my custom X radeon driver
> > (which is xorg-x11-drv-ati-6.9.0-61.fc10.i386 with "radeon: no need for this
> > anymore" from radeon-gem-cs change reverted, please see [2] for my previous
> > monologue) works fine while following stock driver versions:
> >
> > xorg-x11-drv-ati-6.8.0-19.fc9.i386
> > xorg-x11-drv-ati-6.9.0-61.fc10.i386
> > xorg-x11-drv-ati-6.9.0-62.fc10.i386
> >
> > result in BSOD. OTOH they all work with next-20081128 (modulo hangs with
> > fc10 ones when "radeon: no need for this anymore" change is not reverted).
> >
> > [ BTW xorg-x11-drv-ati-6.9.0-62.fc10.i386 still causes hangs when used with
> > non-Fedora kernels and Fedora/kms kernel still has performance problems ]
> >
> > IOW there are a lot of compatibility issues in recent drm/radeon changes.
> >
> > Dave, could you please start looking into these problems? I'm sure that we
> > all want recent drm changes + kms in 2.6.29 but given tight schedule and the
> > way things are looking right now I'm quite sceptical...
> >
> > [1] http://lkml.org/lkml/2008/12/13/76
> > [2] http://lkml.org/lkml/2008/12/13/77
> >
>
> Bart,
>
> please file bugs in RH bugzilla for Fedora issues. Fedora is shipping
> drivers that aren't upstream, and I'm attempting to resolve the issues
> as they arise. However not having a bug to track stuff in means it just
> goes far enough out of my inbox that I forget about it.

OK, I'll try to put all issues into RH bugzilla once I find some time.

[ OTOH the hang issue mentioned above happens only with vanilla kernels,
Fedora kernels are not affected because they ship KMS. Anyway, you
could have just told me that you prefer to have a RH bugzilla bug for
it two weeks ago (and indeed KMS performance issue should have been
handled through bugzilla -- however this one is of lower priority). ]

> The revert isn't a fix for -ati, and I haven't seen any reports of
> performance problems with profiles attached in my bugzilla.

"isn't a fix" is a brave statement since it makes a difference between hang
within minutes and rock stable operation (sure the revert itself may not be
a proper fix but it works and is a good starting point). I spend quite some
time narrowing down the bug and this is not exactly the reaction I expected.

[ Well, I can fix/workaround the issues that I encounter quite quickly and I
don't really have to put extra time into narrowing them down so they can be
fixed in upstream distro if distro people don't see a value in such work. ]

> I'm booting drm-next on more various radeon hw today to see what I can
> reproduce, most of the kms changes for 2.6.29 are nothing to do with
> radeon at all, we are only upstreaming KMS for Intel hw, so I'm not sure
> what the sceptical bit is about. Its much more likely this is

F9 -> F10 upgrade has been a nightmare for me thanks to radeon/kms
changes (which are still Fedora specific stuff and it is good to hear
that they will not be upstreamed now).

On top of it drm-next tree has been broken for me since next-20081203
(yes, that is two weeks period!).

It could be just my luck and things may be working perfectly for 99.9%
of other people but are you still surprised that I'm sceptical?

> multi-master changes before KMS that are interacting badly.

Yes, multi-master changes are to blame but currently KMS patch depends on
them (though maybe it could be made independent -- I don't know this).

If you want me to try some debugging I will be happy to help but please
start taking more serious approach, and if you don't have the idea where
the problem is or don't have time to work on it currently please just
drop the broken changes from drm-next tree for now.

Thanks,
Bart

2008-12-18 23:40:29

by David Airlie

[permalink] [raw]
Subject: Re: linux-next: Tree for December 17 (Radeon DRM BUG)

On Thu, 2008-12-18 at 23:09 +0100, Bartlomiej Zolnierkiewicz wrote:
> tOn Thursday 18 December 2008, Dave Airlie wrote:
> > On Thu, 2008-12-18 at 20:00 +0100, Bartlomiej Zolnierkiewicz wrote:
> > > On Thursday 18 December 2008, Dave Airlie wrote:
> > > > On Thu, Dec 18, 2008 at 10:14 AM, Kevin Winchester
> > > > <[email protected]> wrote:
> > > > > Stephen Rothwell wrote:
> > > > >>
> > > > >> Hi all,
> > > > >>
> > > > >>
> > > > >
> > > > > I get the following BUG in the radeon drm code with today's linux-next when
> > > > > I run "startx". I have not built or tested linux-next in a while, but the
> > > > > problem definitely does not occur in mainline.
> > >
> > > [...]
> > >
> > > This reminds me that drm tree in linux-next still results in BSOD (Black
> > > Screen Of Death) on starting X for me (as reported on Saturday [1]).
> > >
> > > Actually there is more to it as I discovered that my custom X radeon driver
> > > (which is xorg-x11-drv-ati-6.9.0-61.fc10.i386 with "radeon: no need for this
> > > anymore" from radeon-gem-cs change reverted, please see [2] for my previous
> > > monologue) works fine while following stock driver versions:
> > >
> > > xorg-x11-drv-ati-6.8.0-19.fc9.i386
> > > xorg-x11-drv-ati-6.9.0-61.fc10.i386
> > > xorg-x11-drv-ati-6.9.0-62.fc10.i386
> > >
> > > result in BSOD. OTOH they all work with next-20081128 (modulo hangs with
> > > fc10 ones when "radeon: no need for this anymore" change is not reverted).
> > >
> > > [ BTW xorg-x11-drv-ati-6.9.0-62.fc10.i386 still causes hangs when used with
> > > non-Fedora kernels and Fedora/kms kernel still has performance problems ]
> > >
> > > IOW there are a lot of compatibility issues in recent drm/radeon changes.
> > >
> > > Dave, could you please start looking into these problems? I'm sure that we
> > > all want recent drm changes + kms in 2.6.29 but given tight schedule and the
> > > way things are looking right now I'm quite sceptical...
> > >
> > > [1] http://lkml.org/lkml/2008/12/13/76
> > > [2] http://lkml.org/lkml/2008/12/13/77
> > >
> >
> > Bart,
> >
> > please file bugs in RH bugzilla for Fedora issues. Fedora is shipping
> > drivers that aren't upstream, and I'm attempting to resolve the issues
> > as they arise. However not having a bug to track stuff in means it just
> > goes far enough out of my inbox that I forget about it.
>
> OK, I'll try to put all issues into RH bugzilla once I find some time.
>
> [ OTOH the hang issue mentioned above happens only with vanilla kernels,
> Fedora kernels are not affected because they ship KMS. Anyway, you
> could have just told me that you prefer to have a RH bugzilla bug for
> it two weeks ago (and indeed KMS performance issue should have been
> handled through bugzilla -- however this one is of lower priority). ]

I know, literally I didn't see a mail in my inbox and forgot about this
bug until it showed up again, so I should mention Fedora BZ for Fedora
bugs earlier indeed..

drm-next should be fine in the next iteration, there was a missing patch
hunk in the last commit, and then a locking bug after that.

I'll try and look at the other stability issues you are seeing with
Fedora today,

however halving the amount of video RAM everyone gets as a fix for an
issue you are seeing is clearly not the answer, I'd like to actually
track down the root cause of where it went wrong.

Dave.

>
> > The revert isn't a fix for -ati, and I haven't seen any reports of
> > performance problems with profiles attached in my bugzilla.
>
> "isn't a fix" is a brave statement since it makes a difference between hang
> within minutes and rock stable operation (sure the revert itself may not be
> a proper fix but it works and is a good starting point). I spend quite some
> time narrowing down the bug and this is not exactly the reaction I expected.
>
> [ Well, I can fix/workaround the issues that I encounter quite quickly and I
> don't really have to put extra time into narrowing them down so they can be
> fixed in upstream distro if distro people don't see a value in such work. ]
>
> > I'm booting drm-next on more various radeon hw today to see what I can
> > reproduce, most of the kms changes for 2.6.29 are nothing to do with
> > radeon at all, we are only upstreaming KMS for Intel hw, so I'm not sure
> > what the sceptical bit is about. Its much more likely this is
>
> F9 -> F10 upgrade has been a nightmare for me thanks to radeon/kms
> changes (which are still Fedora specific stuff and it is good to hear
> that they will not be upstreamed now).
>
> On top of it drm-next tree has been broken for me since next-20081203
> (yes, that is two weeks period!).
>
> It could be just my luck and things may be working perfectly for 99.9%
> of other people but are you still surprised that I'm sceptical?
>
> > multi-master changes before KMS that are interacting badly.
>
> Yes, multi-master changes are to blame but currently KMS patch depends on
> them (though maybe it could be made independent -- I don't know this).
>
> If you want me to try some debugging I will be happy to help but please
> start taking more serious approach, and if you don't have the idea where
> the problem is or don't have time to work on it currently please just
> drop the broken changes from drm-next tree for now.
>
> Thanks,
> Bart

Subject: Re: linux-next: Tree for December 17 (Radeon DRM BUG)

On Friday 19 December 2008, Dave Airlie wrote:
> On Thu, 2008-12-18 at 23:09 +0100, Bartlomiej Zolnierkiewicz wrote:
> > tOn Thursday 18 December 2008, Dave Airlie wrote:
> > > On Thu, 2008-12-18 at 20:00 +0100, Bartlomiej Zolnierkiewicz wrote:
> > > > On Thursday 18 December 2008, Dave Airlie wrote:
> > > > > On Thu, Dec 18, 2008 at 10:14 AM, Kevin Winchester
> > > > > <[email protected]> wrote:
> > > > > > Stephen Rothwell wrote:
> > > > > >>
> > > > > >> Hi all,
> > > > > >>
> > > > > >>
> > > > > >
> > > > > > I get the following BUG in the radeon drm code with today's linux-next when
> > > > > > I run "startx". I have not built or tested linux-next in a while, but the
> > > > > > problem definitely does not occur in mainline.
> > > >
> > > > [...]
> > > >
> > > > This reminds me that drm tree in linux-next still results in BSOD (Black
> > > > Screen Of Death) on starting X for me (as reported on Saturday [1]).
> > > >
> > > > Actually there is more to it as I discovered that my custom X radeon driver
> > > > (which is xorg-x11-drv-ati-6.9.0-61.fc10.i386 with "radeon: no need for this
> > > > anymore" from radeon-gem-cs change reverted, please see [2] for my previous
> > > > monologue) works fine while following stock driver versions:
> > > >
> > > > xorg-x11-drv-ati-6.8.0-19.fc9.i386
> > > > xorg-x11-drv-ati-6.9.0-61.fc10.i386
> > > > xorg-x11-drv-ati-6.9.0-62.fc10.i386
> > > >
> > > > result in BSOD. OTOH they all work with next-20081128 (modulo hangs with
> > > > fc10 ones when "radeon: no need for this anymore" change is not reverted).
> > > >
> > > > [ BTW xorg-x11-drv-ati-6.9.0-62.fc10.i386 still causes hangs when used with
> > > > non-Fedora kernels and Fedora/kms kernel still has performance problems ]
> > > >
> > > > IOW there are a lot of compatibility issues in recent drm/radeon changes.
> > > >
> > > > Dave, could you please start looking into these problems? I'm sure that we
> > > > all want recent drm changes + kms in 2.6.29 but given tight schedule and the
> > > > way things are looking right now I'm quite sceptical...
> > > >
> > > > [1] http://lkml.org/lkml/2008/12/13/76
> > > > [2] http://lkml.org/lkml/2008/12/13/77
> > > >
> > >
> > > Bart,
> > >
> > > please file bugs in RH bugzilla for Fedora issues. Fedora is shipping
> > > drivers that aren't upstream, and I'm attempting to resolve the issues
> > > as they arise. However not having a bug to track stuff in means it just
> > > goes far enough out of my inbox that I forget about it.
> >
> > OK, I'll try to put all issues into RH bugzilla once I find some time.
> >
> > [ OTOH the hang issue mentioned above happens only with vanilla kernels,
> > Fedora kernels are not affected because they ship KMS. Anyway, you
> > could have just told me that you prefer to have a RH bugzilla bug for
> > it two weeks ago (and indeed KMS performance issue should have been
> > handled through bugzilla -- however this one is of lower priority). ]
>
> I know, literally I didn't see a mail in my inbox and forgot about this
> bug until it showed up again, so I should mention Fedora BZ for Fedora
> bugs earlier indeed..
>
> drm-next should be fine in the next iteration, there was a missing patch
> hunk in the last commit, and then a locking bug after that.

The drm problem is indeed fixed in today's linux-next (I remembered to
check that it includes drm-next this time ;-). Thanks!

> I'll try and look at the other stability issues you are seeing with
> Fedora today,
>
> however halving the amount of video RAM everyone gets as a fix for an
> issue you are seeing is clearly not the answer, I'd like to actually
> track down the root cause of where it went wrong.

Same opinion here. As I see now that limitation was added temporarily
to the driver and later removed. I will do some more testing...

Thanks,
Bart

2008-12-19 23:07:42

by Kevin Winchester

[permalink] [raw]
Subject: Re: linux-next: Tree for December 17 (Radeon DRM BUG)

Dave Airlie wrote:
> On Thu, Dec 18, 2008 at 10:14 AM, Kevin Winchester
> <[email protected]> wrote:
>
>> Stephen Rothwell wrote:
>>
>>> Hi all,
>>>
>>>
>>>
>> I get the following BUG in the radeon drm code with today's linux-next when
>> I run "startx". I have not built or tested linux-next in a while, but the
>> problem definitely does not occur in mainline.
>>
>
> Do you have another X server running or just console?
>
Just console.
> can you get a full dmesg with
>
> echo 1 > /sys/module/drm/parameters/debug
>
>
[ 0.000000] Linux version 2.6.28-rc8-next-20081217 (kevin@winchester)
(gcc version 4.1.2 (Gentoo 4.1.2 p1.1)) #192 Wed Dec 17 17:04:30 AST 2008
[ 0.000000] Command line: root=/dev/sda1 hpet=force
[ 0.000000] KERNEL supported cpus:
[ 0.000000] AMD AuthenticAMD
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
[ 0.000000] BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000ce000 - 00000000000d8000 (reserved)
[ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 000000004fff0000 (usable)
[ 0.000000] BIOS-e820: 000000004fff0000 - 000000004fff8000 (ACPI data)
[ 0.000000] BIOS-e820: 000000004fff8000 - 0000000050000000 (ACPI NVS)
[ 0.000000] BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
[ 0.000000] BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
[ 0.000000] BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
[ 0.000000] DMI 2.3 present.
[ 0.000000] AMI BIOS detected: BIOS may corrupt low RAM, working it
around.
[ 0.000000] last_pfn = 0x4fff0 max_arch_pfn = 0x3ffffffff
[ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new
0x7010600070106
[ 0.000000] init_memory_mapping: 0000000000000000-000000004fff0000
[ 0.000000] 0000000000 - 004fe00000 page 2M
[ 0.000000] 004fe00000 - 004fff0000 page 4k
[ 0.000000] kernel direct mapping tables up to 4fff0000 @ 10000-14000
[ 0.000000] last_map_addr: 4fff0000 end: 4fff0000
[ 0.000000] ACPI: RSDP 000FA0C0, 0014 (r0 AMI )
[ 0.000000] ACPI: RSDT 4FFF0000, 002C (r1 AMIINT VIA_K8 10
MSFT 97)
[ 0.000000] ACPI: FACP 4FFF0030, 0081 (r1 AMIINT VIA_K8 11
MSFT 97)
[ 0.000000] ACPI: DSDT 4FFF0120, 36C5 (r1 VIA VIA_K8 1000
MSFT 100000D)
[ 0.000000] ACPI: FACS 4FFF8000, 0040
[ 0.000000] ACPI: APIC 4FFF00C0, 0054 (r1 AMIINT VIA_K8 9
MSFT 97)
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] (5 early reservations) ==> bootmem [0000000000 - 004fff0000]
[ 0.000000] #0 [0000000000 - 0000001000] BIOS data page ==>
[0000000000 - 0000001000]
[ 0.000000] #1 [0000006000 - 0000008000] TRAMPOLINE ==>
[0000006000 - 0000008000]
[ 0.000000] #2 [0000200000 - 000078c910] TEXT DATA BSS ==>
[0000200000 - 000078c910]
[ 0.000000] #3 [000009fc00 - 0000100000] BIOS reserved ==>
[000009fc00 - 0000100000]
[ 0.000000] #4 [0000010000 - 0000012000] PGTABLE ==>
[0000010000 - 0000012000]
[ 0.000000] found SMP MP-table at [ffff8800000fba70] 000fba70
[ 0.000000] [ffffe20000000000-ffffe200011fffff] PMD ->
[ffff880001200000-ffff8800023fffff] on node 0
[ 0.000000] Zone PFN ranges:
[ 0.000000] DMA 0x00000010 -> 0x00001000
[ 0.000000] DMA32 0x00001000 -> 0x00100000
[ 0.000000] Normal 0x00100000 -> 0x00100000
[ 0.000000] Movable zone start PFN for each node
[ 0.000000] early_node_map[2] active PFN ranges
[ 0.000000] 0: 0x00000010 -> 0x0000009f
[ 0.000000] 0: 0x00000100 -> 0x0004fff0
[ 0.000000] On node 0 totalpages: 327551
[ 0.000000] DMA zone: 56 pages used for memmap
[ 0.000000] DMA zone: 1523 pages reserved
[ 0.000000] DMA zone: 2404 pages, LIFO batch:0
[ 0.000000] DMA32 zone: 4424 pages used for memmap
[ 0.000000] DMA32 zone: 319144 pages, LIFO batch:31
[ 0.000000] Normal zone: 0 pages used for memmap
[ 0.000000] Movable zone: 0 pages used for memmap
[ 0.000000] ACPI: PM-Timer IO Port: 0x808
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
[ 0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
[ 0.000000] IOAPIC[0]: apic_id 2, version 0, address 0xfec00000, GSI 0-23
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
[ 0.000000] ACPI: IRQ0 used by override.
[ 0.000000] ACPI: IRQ2 used by override.
[ 0.000000] ACPI: IRQ9 used by override.
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] Allocating PCI resources starting at 60000000 (gap:
50000000:aec00000)
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on.
Total pages: 321548
[ 0.000000] Kernel command line: root=/dev/sda1 hpet=force
[ 0.000000] Initializing CPU#0
[ 0.000000] PID hash table entries: 4096 (order: 12, 32768 bytes)
[ 0.000000] TSC: Unable to calibrate against PIT
[ 0.000000] TSC: using PMTIMER reference calibration
[ 0.000000] Detected 1800.008 MHz processor.
[ 0.000999] Console: colour VGA+ 80x25
[ 0.000999] console [tty0] enabled
[ 0.000999] Dentry cache hash table entries: 262144 (order: 9,
2097152 bytes)
[ 0.000999] Inode-cache hash table entries: 131072 (order: 8, 1048576
bytes)
[ 0.000999] Checking aperture...
[ 0.000999] AGP bridge at 00:00:00
[ 0.000999] Aperture from AGP @ d0000000 old size 32 MB
[ 0.000999] Aperture from AGP @ d0000000 size 128 MB (APSIZE f20)
[ 0.000999] Node 0: aperture @ d0000000 size 128 MB
[ 0.000999] Memory: 1282288k/1310656k available (2672k kernel code,
452k absent, 27308k reserved, 2032k data, 260k init)
[ 0.000999] SLUB: Genslabs=12, HWalign=64, Order=0-3, MinObjects=0,
CPUs=1, Nodes=1
[ 0.001024] Calibrating delay loop (skipped), value calculated using
timer frequency.. 3600.01 BogoMIPS (lpj=1800008)
[ 0.001173] Mount-cache hash table entries: 256
[ 0.001538] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64
bytes/line)
[ 0.001589] CPU: L2 Cache: 512K (64 bytes/line)
[ 0.001637] tseg: 0000000000
[ 0.001674] CPU: AMD Athlon(tm) 64 Processor 2800+ stepping 0a
[ 0.001802] ACPI: Core revision 20081031
[ 0.010007] ftrace: converting mcount calls to 0f 1f 44 00 00
[ 0.010070] ftrace: allocating 15382 entries in 122 pages
[ 0.013765] Setting APIC routing to flat
[ 0.013997] alloc irq_2_pin on cpu 0 node 0
[ 0.013997] alloc irq_2_pin on cpu 0 node 0
[ 0.013997] alloc irq_2_pin on cpu 0 node 0
[ 0.013997] alloc irq_2_pin on cpu 0 node 0
[ 0.013997] alloc irq_2_pin on cpu 0 node 0
[ 0.013997] alloc irq_2_pin on cpu 0 node 0
[ 0.013997] alloc irq_2_pin on cpu 0 node 0
[ 0.013997] alloc irq_2_pin on cpu 0 node 0
[ 0.013997] alloc irq_2_pin on cpu 0 node 0
[ 0.013997] alloc irq_2_pin on cpu 0 node 0
[ 0.013997] alloc irq_2_pin on cpu 0 node 0
[ 0.013997] alloc irq_2_pin on cpu 0 node 0
[ 0.013997] alloc irq_2_pin on cpu 0 node 0
[ 0.013997] alloc irq_2_pin on cpu 0 node 0
[ 0.013997] alloc irq_2_pin on cpu 0 node 0
[ 0.013997] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=0 pin2=0
[ 0.023996] net_namespace: 576 bytes
[ 0.023996] NET: Registered protocol family 16
[ 0.024021] node 0 link 0: io port [0, ffffff]
[ 0.024025] TOM: 0000000050000000 aka 1280M
[ 0.024074] node 0 link 0: mmio [a0000, bffff]
[ 0.024077] node 0 link 0: mmio [50000000, ffffffff]
[ 0.024081] bus: [00,ff] on node 0 link 0
[ 0.024083] bus: 00 index 0 io port: [0, ffff]
[ 0.024086] bus: 00 index 1 mmio: [a0000, bffff]
[ 0.024088] bus: 00 index 2 mmio: [50000000, fcffffffff]
[ 0.024098] ACPI: bus type pci registered
[ 0.024160] PCI: Using configuration type 1 for base access
[ 0.028819] bio: create slab <bio-0> at 0
[ 0.029724] ACPI: EC: Look up EC in DSDT
[ 0.032014] ACPI Warning (dsobject-0501): Package List length (65)
larger than NumElements count (2), truncated
[ 0.032110] [20081031]
[ 0.036779] ACPI: Interpreter enabled
[ 0.036829] ACPI: (supports S0 S1 S3 S5)
[ 0.036997] ACPI: Using IOAPIC for interrupt routing
[ 0.042058] ACPI: No dock devices found.
[ 0.042126] ACPI: PCI Root Bridge [PCI0] (0000:00)
[ 0.042289] pci 0000:00:00.0: reg 10 32bit mmio: [0xd0000000-0xd7ffffff]
[ 0.042376] pci 0000:00:01.0: supports D1
[ 0.042407] pci 0000:00:06.0: reg 10 io port: [0xec00-0xecff]
[ 0.042413] pci 0000:00:06.0: reg 14 32bit mmio: [0xcfffff00-0xcfffffff]
[ 0.042432] pci 0000:00:06.0: reg 30 32bit mmio: [0xcff80000-0xcffbffff]
[ 0.042447] pci 0000:00:06.0: supports D1 D2
[ 0.042450] pci 0000:00:06.0: PME# supported from D1 D2 D3hot D3cold
[ 0.042502] pci 0000:00:06.0: PME# disabled
[ 0.042577] pci 0000:00:0b.0: reg 10 io port: [0xe800-0xe8ff]
[ 0.042583] pci 0000:00:0b.0: reg 14 32bit mmio: [0xcffffe00-0xcffffeff]
[ 0.042602] pci 0000:00:0b.0: reg 30 32bit mmio: [0xcffc0000-0xcffdffff]
[ 0.042617] pci 0000:00:0b.0: supports D1 D2
[ 0.042620] pci 0000:00:0b.0: PME# supported from D1 D2 D3hot D3cold
[ 0.042671] pci 0000:00:0b.0: PME# disabled
[ 0.042759] pci 0000:00:0f.0: reg 20 io port: [0xfc00-0xfc0f]
[ 0.042820] pci 0000:00:10.0: reg 20 io port: [0xd800-0xd81f]
[ 0.042842] pci 0000:00:10.0: supports D1 D2
[ 0.042845] pci 0000:00:10.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.042896] pci 0000:00:10.0: PME# disabled
[ 0.042979] pci 0000:00:10.1: reg 20 io port: [0xdc00-0xdc1f]
[ 0.043022] pci 0000:00:10.1: supports D1 D2
[ 0.043024] pci 0000:00:10.1: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.043076] pci 0000:00:10.1: PME# disabled
[ 0.043160] pci 0000:00:10.2: reg 20 io port: [0xe000-0xe01f]
[ 0.043182] pci 0000:00:10.2: supports D1 D2
[ 0.043184] pci 0000:00:10.2: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.043236] pci 0000:00:10.2: PME# disabled
[ 0.043319] pci 0000:00:10.3: reg 20 io port: [0xe400-0xe41f]
[ 0.043341] pci 0000:00:10.3: supports D1 D2
[ 0.043343] pci 0000:00:10.3: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.043395] pci 0000:00:10.3: PME# disabled
[ 0.043772] pci 0000:00:10.4: reg 10 32bit mmio: [0xcffffc00-0xcffffcff]
[ 0.043806] pci 0000:00:10.4: supports D1 D2
[ 0.043808] pci 0000:00:10.4: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.043859] pci 0000:00:10.4: PME# disabled
[ 0.043959] pci 0000:00:11.0: Force enabled HPET at 0xfed00000
[ 0.044010] pci 0000:00:11.5: reg 10 io port: [0xd400-0xd4ff]
[ 0.044046] pci 0000:00:11.5: supports D1 D2
[ 0.044144] pci 0000:01:00.0: reg 10 32bit mmio: [0xb0000000-0xbfffffff]
[ 0.044149] pci 0000:01:00.0: reg 14 io port: [0xc800-0xc8ff]
[ 0.044154] pci 0000:01:00.0: reg 18 32bit mmio: [0xcfef0000-0xcfefffff]
[ 0.044163] pci 0000:01:00.0: reg 30 32bit mmio: [0xcfec0000-0xcfedffff]
[ 0.044175] pci 0000:01:00.0: supports D1 D2
[ 0.044196] pci 0000:00:01.0: bridge io port: [0xc000-0xcfff]
[ 0.044200] pci 0000:00:01.0: bridge 32bit mmio: [0xcfe00000-0xcfefffff]
[ 0.044204] pci 0000:00:01.0: bridge 32bit mmio pref:
[0xafd00000-0xcfcfffff]
[ 0.044211] pci 0000:00: bus on NUMA node 0
[ 0.044220] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[ 0.063160] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12
14 15)
[ 0.063692] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12
14 15)
[ 0.064218] ACPI: PCI Interrupt Link [LNKC] (IRQs *3 4 5 6 7 10 11 12
14 15)
[ 0.064744] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 *5 6 7 10 11 12
14 15)
[ 0.065271] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12
14 15) *0, disabled.
[ 0.066221] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12
14 15) *0, disabled.
[ 0.066818] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12
14 15) *0, disabled.
[ 0.067403] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12
14 15) *0, disabled.
[ 0.068029] ACPI: Power Resource [URP1] (off)
[ 0.068113] ACPI: Power Resource [URP2] (off)
[ 0.068197] ACPI: Power Resource [FDDP] (off)
[ 0.068280] ACPI: Power Resource [LPTP] (off)
[ 0.068739] SCSI subsystem initialized
[ 0.068838] libata version 3.00 loaded.
[ 0.069007] usbcore: registered new interface driver usbfs
[ 0.069098] usbcore: registered new interface driver hub
[ 0.069201] usbcore: registered new device driver usb
[ 0.069434] PCI: Using ACPI for IRQ routing
[ 0.069494] pci 0000:00:00.0: BAR 0: can't allocate resource
[ 0.073101] agpgart-amd64 0000:00:00.0: AGP bridge [1106:3188]
[ 0.083981] agpgart-amd64 0000:00:00.0: AGP aperture is 128M @ 0xd0000000
[ 0.084201] hpet clockevent registered
[ 0.084209] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
[ 0.084378] hpet0: 3 comparators, 32-bit 14.318180 MHz counter
[ 0.088994] pnp: PnP ACPI init
[ 0.089049] ACPI: bus type pnp registered
[ 0.091981] pnp: PnP ACPI: found 6 devices
[ 0.092033] ACPI: ACPI bus type pnp unregistered
[ 0.092094] system 00:01: ioport range 0x290-0x297 has been reserved
[ 0.092144] system 00:01: ioport range 0x3f0-0x3f1 has been reserved
[ 0.092194] system 00:01: ioport range 0x4d0-0x4d1 has been reserved
[ 0.092244] system 00:01: ioport range 0x400-0x40f has been reserved
[ 0.092294] system 00:01: ioport range 0x820-0x821 has been reserved
[ 0.092345] system 00:01: iomem range 0xfee00000-0xfee00fff has been
reserved
[ 0.097682] pci 0000:00:01.0: PCI bridge, secondary bus 0000:01
[ 0.097733] pci 0000:00:01.0: IO window: 0xc000-0xcfff
[ 0.097783] pci 0000:00:01.0: MEM window: 0xcfe00000-0xcfefffff
[ 0.097834] pci 0000:00:01.0: PREFETCH window:
0x000000afd00000-0x000000cfcfffff
[ 0.097907] pci 0000:00:01.0: setting latency timer to 64
[ 0.097912] pci 0000:00: bus resource 0 io: [0x00-0xffff]
[ 0.097915] pci 0000:00: bus resource 1 mem:
[0x000000-0xffffffffffffffff]
[ 0.097918] pci 0000:01: bus resource 0 io: [0xc000-0xcfff]
[ 0.097920] pci 0000:01: bus resource 1 mem: [0xcfe00000-0xcfefffff]
[ 0.097923] pci 0000:01: bus resource 2 mem: [0xafd00000-0xcfcfffff]
[ 0.097926] pci 0000:01: bus resource 3 mem: [0x0-0x0]
[ 0.097973] NET: Registered protocol family 2
[ 0.109032] IP route cache hash table entries: 65536 (order: 7,
524288 bytes)
[ 0.110146] TCP established hash table entries: 262144 (order: 10,
4194304 bytes)
[ 0.118296] TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
[ 0.119398] TCP: Hash tables configured (established 262144 bind 65536)
[ 0.119449] TCP reno registered
[ 0.122093] NET: Registered protocol family 1
[ 0.127358] alg: No test for stdrng (krng)
[ 0.127546] Block layer SCSI generic (bsg) driver version 0.4 loaded
(major 253)
[ 0.127610] io scheduler noop registered
[ 0.127729] io scheduler cfq registered (default)
[ 0.127793] PCI: VIA PCI bridge detected. Disabling DAC.
[ 0.127963] pci 0000:01:00.0: Boot video device
[ 0.128186] input: Power Button (FF) as
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input0
[ 0.128249] ACPI: Power Button (FF) [PWRF]
[ 0.128414] input: Power Button (CM) as
/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input1
[ 0.128477] ACPI: Power Button (CM) [PWRB]
[ 0.128659] input: Sleep Button (CM) as
/devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input2
[ 0.128728] ACPI: Sleep Button (CM) [SLPB]
[ 0.129298] processor ACPI_CPU:00: registered as cooling_device0
[ 0.142204] Linux agpgart interface v0.103
[ 0.142301] [drm] Initialized drm 1.1.0 20060810
[ 0.142711] alloc irq_2_pin on cpu 0 node 0
[ 0.142724] pci 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 0.143012] [drm] Initialized radeon 1.29.0 20080528 on minor 0
[ 0.143532] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 0.143606] r8169 0000:00:0b.0: PCI INT A -> GSI 16 (level, low) ->
IRQ 16
[ 0.143671] r8169 0000:00:0b.0: PCI: Disallowing DAC for device
[ 0.143729] r8169 0000:00:0b.0: no PCI Express capability
[ 0.143950] eth0: RTL8110s at 0xffffc2000001ee00, 00:11:09:e8:d8:73,
XID 04000000 IRQ 16
[ 0.147372] Driver 'sd' needs updating - please use bus_type methods
[ 0.149500] Driver 'sr' needs updating - please use bus_type methods
[ 0.149633] pata_via 0000:00:0f.0: version 0.3.3
[ 0.149649] alloc irq_2_pin on cpu 0 node 0
[ 0.149655] pata_via 0000:00:0f.0: PCI INT A -> GSI 20 (level, low)
-> IRQ 20
[ 0.149971] scsi0 : pata_via
[ 0.150206] scsi1 : pata_via
[ 0.153808] ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xfc00
irq 14
[ 0.153859] ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xfc08
irq 15
[ 0.311432] ata1.00: HPA detected: current 156299375, native 156301488
[ 0.311486] ata1.00: ATA-6: WDC WD800JB-00JJC0, 05.01C05, max UDMA/100
[ 0.311536] ata1.00: 156299375 sectors, multi 16: LBA
[ 0.311729] ata1.01: ATA-6: WDC WD800JB-00JJA0, 05.01C05, max UDMA/100
[ 0.311779] ata1.01: 156301488 sectors, multi 16: LBA
[ 0.315304] ata1.00: configured for UDMA/100
[ 0.318295] ata1.01: configured for UDMA/100
[ 0.491281] ata2.00: ATAPI: HL-DT-ST DVDRAM GSA-4163B, A104, max UDMA/33
[ 0.491361] ata2.01: ATAPI: HL-DT-STDVD-ROM GDR8163B, 0L23, max UDMA/33
[ 0.513166] ata2.00: configured for UDMA/33
[ 0.535162] ata2.01: configured for UDMA/33
[ 0.537923] isa bounce pool size: 16 pages
[ 0.538137] scsi 0:0:0:0: Direct-Access ATA WDC WD800JB-00JJ
05.0 PQ: 0 ANSI: 5
[ 0.538395] sd 0:0:0:0: [sda] 156299375 512-byte hardware sectors:
(80.0 GB/74.5 GiB)
[ 0.538478] sd 0:0:0:0: [sda] Write Protect is off
[ 0.538527] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 0.538557] sd 0:0:0:0: [sda] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[ 0.538698] sd 0:0:0:0: [sda] 156299375 512-byte hardware sectors:
(80.0 GB/74.5 GiB)
[ 0.538774] sd 0:0:0:0: [sda] Write Protect is off
[ 0.538822] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 0.538851] sd 0:0:0:0: [sda] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[ 0.538922] sda: sda1 sda2 sda3
[ 0.545579] sd 0:0:0:0: [sda] Attached SCSI disk
[ 0.545759] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 0.545957] scsi 0:0:1:0: Direct-Access ATA WDC WD800JB-00JJ
05.0 PQ: 0 ANSI: 5
[ 0.546207] sd 0:0:1:0: [sdb] 156301488 512-byte hardware sectors:
(80.0 GB/74.5 GiB)
[ 0.546284] sd 0:0:1:0: [sdb] Write Protect is off
[ 0.546331] sd 0:0:1:0: [sdb] Mode Sense: 00 3a 00 00
[ 0.546359] sd 0:0:1:0: [sdb] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[ 0.546483] sd 0:0:1:0: [sdb] 156301488 512-byte hardware sectors:
(80.0 GB/74.5 GiB)
[ 0.546558] sd 0:0:1:0: [sdb] Write Protect is off
[ 0.546606] sd 0:0:1:0: [sdb] Mode Sense: 00 3a 00 00
[ 0.546633] sd 0:0:1:0: [sdb] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[ 0.546698] sdb: sdb1 sdb2 < sdb5<7>Switched to high resolution mode
on CPU 0
[ 0.587465] sdb6 >
[ 0.587880] sd 0:0:1:0: [sdb] Attached SCSI disk
[ 0.588043] sd 0:0:1:0: Attached scsi generic sg1 type 0
[ 0.591926] scsi 1:0:0:0: CD-ROM HL-DT-ST DVDRAM GSA-4163B
A104 PQ: 0 ANSI: 5
[ 0.604515] sr0: scsi3-mmc drive: 40x/40x writer dvd-ram cd/rw
xa/form2 cdda tray
[ 0.604577] Uniform CD-ROM driver Revision: 3.20
[ 0.604765] sr 1:0:0:0: Attached scsi CD-ROM sr0
[ 0.604864] sr 1:0:0:0: Attached scsi generic sg2 type 5
[ 0.613074] scsi 1:0:1:0: CD-ROM HL-DT-ST DVD-ROM GDR8163B
0L23 PQ: 0 ANSI: 5
[ 0.620399] sr1: scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda tray
[ 0.620585] sr 1:0:1:0: Attached scsi CD-ROM sr1
[ 0.620691] sr 1:0:1:0: Attached scsi generic sg3 type 5
[ 0.620861] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 0.620952] alloc irq_2_pin on cpu 0 node 0
[ 0.620963] ehci_hcd 0000:00:10.4: PCI INT C -> GSI 21 (level, low)
-> IRQ 21
[ 0.621065] ehci_hcd 0000:00:10.4: EHCI Host Controller
[ 0.621168] ehci_hcd 0000:00:10.4: new USB bus registered, assigned
bus number 1
[ 0.621318] ehci_hcd 0000:00:10.4: irq 21, io mem 0xcffffc00
[ 0.627007] ehci_hcd 0000:00:10.4: USB 2.0 started, EHCI 1.00
[ 0.627192] usb usb1: configuration #1 chosen from 1 choice
[ 0.627302] hub 1-0:1.0: USB hub found
[ 0.627376] hub 1-0:1.0: 8 ports detected
[ 0.627653] uhci_hcd: USB Universal Host Controller Interface driver
[ 0.627819] uhci_hcd 0000:00:10.0: PCI INT A -> GSI 21 (level, low)
-> IRQ 21
[ 0.627877] uhci_hcd 0000:00:10.0: UHCI Host Controller
[ 0.627974] uhci_hcd 0000:00:10.0: new USB bus registered, assigned
bus number 2
[ 0.628075] uhci_hcd 0000:00:10.0: irq 21, io base 0x0000d800
[ 0.628265] usb usb2: configuration #1 chosen from 1 choice
[ 0.628372] hub 2-0:1.0: USB hub found
[ 0.628433] hub 2-0:1.0: 2 ports detected
[ 0.628627] uhci_hcd 0000:00:10.1: PCI INT A -> GSI 21 (level, low)
-> IRQ 21
[ 0.628681] uhci_hcd 0000:00:10.1: UHCI Host Controller
[ 0.628785] uhci_hcd 0000:00:10.1: new USB bus registered, assigned
bus number 3
[ 0.628865] uhci_hcd 0000:00:10.1: irq 21, io base 0x0000dc00
[ 0.629057] usb usb3: configuration #1 chosen from 1 choice
[ 0.629161] hub 3-0:1.0: USB hub found
[ 0.629217] hub 3-0:1.0: 2 ports detected
[ 0.629412] uhci_hcd 0000:00:10.2: PCI INT B -> GSI 21 (level, low)
-> IRQ 21
[ 0.629467] uhci_hcd 0000:00:10.2: UHCI Host Controller
[ 0.629564] uhci_hcd 0000:00:10.2: new USB bus registered, assigned
bus number 4
[ 0.629645] uhci_hcd 0000:00:10.2: irq 21, io base 0x0000e000
[ 0.629835] usb usb4: configuration #1 chosen from 1 choice
[ 0.629938] hub 4-0:1.0: USB hub found
[ 0.629995] hub 4-0:1.0: 2 ports detected
[ 0.630191] uhci_hcd 0000:00:10.3: PCI INT B -> GSI 21 (level, low)
-> IRQ 21
[ 0.630245] uhci_hcd 0000:00:10.3: UHCI Host Controller
[ 0.630341] uhci_hcd 0000:00:10.3: new USB bus registered, assigned
bus number 5
[ 0.630423] uhci_hcd 0000:00:10.3: irq 21, io base 0x0000e400
[ 0.630613] usb usb5: configuration #1 chosen from 1 choice
[ 0.630725] hub 5-0:1.0: USB hub found
[ 0.630796] hub 5-0:1.0: 2 ports detected
[ 0.631117] usbcore: registered new interface driver usblp
[ 0.631166] Initializing USB Mass Storage driver...
[ 0.631282] usbcore: registered new interface driver usb-storage
[ 0.631331] USB Mass Storage support registered.
[ 0.642090] rtc_cmos 00:03: RTC can wake from S4
[ 0.642192] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
[ 0.642278] rtc0: alarms up to one year, y3k, 114 bytes nvram, hpet irqs
[ 0.642424] ACPI: I/O resource vt596_smbus [0x400-0x407] conflicts
with ACPI region SMOV [0x400-0x406]
[ 0.642487] ACPI: Device needs an ACPI driver
[ 0.642643] cpuidle: using governor ladder
[ 0.642690] cpuidle: using governor menu
[ 0.642871] usbcore: registered new interface driver usbhid
[ 0.642920] usbhid: v2.6:USB HID core driver
[ 0.643059] Advanced Linux Sound Architecture Driver Version 1.0.18a.
[ 0.643475] alloc irq_2_pin on cpu 0 node 0
[ 0.643484] VIA 82xx Audio 0000:00:11.5: PCI INT C -> GSI 22 (level,
low) -> IRQ 22
[ 0.643697] VIA 82xx Audio 0000:00:11.5: setting latency timer to 64
[ 1.135012] usb 5-1: new low speed USB device using uhci_hcd and
address 2
[ 1.158129] ALSA device list:
[ 1.158184] #0: VIA 8237 with ALC655 at 0xd400, irq 22
[ 1.158272] TCP cubic registered
[ 1.158320] NET: Registered protocol family 17
[ 1.158388] powernow-k8: Found 1 AMD Athlon(tm) 64 Processor 2800+
processors (1 cpu cores) (version 2.20.00)
[ 1.158528] powernow-k8: 0 : fid 0xa (1800 MHz), vid 0x2
[ 1.158576] powernow-k8: 1 : fid 0x2 (1000 MHz), vid 0x12
[ 1.159128] rtc_cmos 00:03: setting system clock to 2008-12-19
20:00:06 UTC (1229716806)
[ 1.171597] kjournald starting. Commit interval 5 seconds
[ 1.171657] EXT3-fs: mounted filesystem with ordered data mode.
[ 1.171719] VFS: Mounted root (ext3 filesystem) readonly.
[ 1.171784] Freeing unused kernel memory: 260k freed
[ 1.172218] Write protecting the kernel read-only data: 1536k
[ 1.295600] usb 5-1: configuration #1 chosen from 1 choice
[ 1.314287] input: Logitech USB Mouse as
/devices/pci0000:00/0000:00:10.3/usb5/5-1/5-1:1.0/input/input3
[ 1.317076] generic-usb 0003:046D:C00C.0001: input: USB HID v1.10
Mouse [Logitech USB Mouse] on usb-0000:00:10.3-1/input0
[ 1.523025] usb 5-2: new low speed USB device using uhci_hcd and
address 3
[ 1.693636] usb 5-2: configuration #1 chosen from 1 choice
[ 1.711019] input: Microsoft Microsoft? Digital Media Pro Keyboard as
/devices/pci0000:00/0000:00:10.3/usb5/5-2/5-2:1.0/input/input4
[ 1.719101] generic-usb 0003:045E:00B0.0002: input: USB HID v1.11
Keyboard [Microsoft Microsoft? Digital Media Pro Keyboard] on
usb-0000:00:10.3-2/input0
[ 1.748587] input: Microsoft Microsoft? Digital Media Pro Keyboard as
/devices/pci0000:00/0000:00:10.3/usb5/5-2/5-2:1.1/input/input5
[ 1.754101] generic-usb 0003:045E:00B0.0003: input: USB HID v1.11
Device [Microsoft Microsoft? Digital Media Pro Keyboard] on
usb-0000:00:10.3-2/input1
[ 2.024888] Marking TSC unstable due to cpufreq changes
[ 2.584024] Clocksource tsc unstable (delta = -222214091 ns)
[ 4.281970] EXT3 FS on sda1, internal journal
[ 4.743154] kjournald starting. Commit interval 5 seconds
[ 4.743171] EXT3-fs warning: maximal mount count reached, running
e2fsck is recommended
[ 4.743441] EXT3 FS on sda3, internal journal
[ 4.743451] EXT3-fs: mounted filesystem with ordered data mode.
[ 4.791567] Adding 987988k swap on /dev/sda2. Priority:-1 extents:1
across:987988k
[ 15.790778] r8169: eth0: link up

2008-12-20 01:59:15

by Kevin Winchester

[permalink] [raw]
Subject: Re: linux-next: Tree for December 17 (Radeon DRM BUG)

Dave Airlie wrote:
> On Thu, Dec 18, 2008 at 10:14 AM, Kevin Winchester
> <[email protected]> wrote:
>> Stephen Rothwell wrote:
>>> Hi all,
>>>
>>>
>> I get the following BUG in the radeon drm code with today's linux-next when
>> I run "startx". I have not built or tested linux-next in a while, but the
>> problem definitely does not occur in mainline.
>
> Do you have another X server running or just console?
>
> can you get a full dmesg with
>
> echo 1 > /sys/module/drm/parameters/debug
>

I just tried today's next (20081219) and the problem seems to be fixed.

Thank you,

--
Kevin Winchester

2008-12-17 18:18:58

by Kamalesh Babulal

[permalink] [raw]
Subject: [BUILD-FAILURE] next-20081217-s390x-'struct device' has no member named 'knode_parent'

Hi,
next-20081217 kernel build fails due to the changes made to
struct device by moving knode_parent to device_private under
struct device.

drivers/s390/cio/device.c: In function 'io_subchannel_register':
drivers/s390/cio/device.c:913: error: 'struct device' has no member named 'knode_parent'
make[2]: *** [drivers/s390/cio/device.o] Error 1
make[1]: *** [drivers/s390/cio] Error 2
make: *** [drivers/s390] Error 2

#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.28-rc8-next-20081217
# Wed Dec 17 07:20:49 2008
#
CONFIG_SCHED_MC=y
CONFIG_MMU=y
CONFIG_ZONE_DMA=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_HAVE_LATENCYTOP_SUPPORT=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
# CONFIG_ARCH_HAS_ILOG2_U32 is not set
# CONFIG_ARCH_HAS_ILOG2_U64 is not set
CONFIG_GENERIC_HWEIGHT=y
CONFIG_GENERIC_TIME=y
CONFIG_GENERIC_TIME_VSYSCALL=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_BUG=y
CONFIG_NO_IOMEM=y
CONFIG_NO_DMA=y
CONFIG_GENERIC_LOCKBREAK=y
CONFIG_PGSTE=y
CONFIG_S390=y
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"

#
# General setup
#
CONFIG_EXPERIMENTAL=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=n
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
# CONFIG_BSD_PROCESS_ACCT is not set
# CONFIG_TASKSTATS is not set
CONFIG_AUDIT=y
# CONFIG_AUDITSYSCALL is not set
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_LOG_BUF_SHIFT=17
CONFIG_CGROUPS=y
# CONFIG_CGROUP_DEBUG is not set
CONFIG_CGROUP_NS=y
# CONFIG_CGROUP_FREEZER is not set
# CONFIG_CGROUP_DEVICE is not set
# CONFIG_CPUSETS is not set
CONFIG_GROUP_SCHED=y
CONFIG_FAIR_GROUP_SCHED=y
# CONFIG_RT_GROUP_SCHED is not set
CONFIG_USER_SCHED=y
# CONFIG_CGROUP_SCHED is not set
# CONFIG_CGROUP_CPUACCT is not set
# CONFIG_RESOURCE_COUNTERS is not set
CONFIG_SYSFS_DEPRECATED=y
CONFIG_SYSFS_DEPRECATED_V2=y
# CONFIG_RELAY is not set
CONFIG_NAMESPACES=y
CONFIG_UTS_NS=y
CONFIG_IPC_NS=y
# CONFIG_USER_NS is not set
# CONFIG_PID_NS is not set
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SYSCTL=y
# CONFIG_EMBEDDED is not set
CONFIG_SYSCTL_SYSCALL=y
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
# CONFIG_COMPAT_BRK is not set
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_ANON_INODES=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_AIO=y
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_SLAB=y
# CONFIG_SLUB is not set
# CONFIG_SLOB is not set
# CONFIG_PROFILING is not set
CONFIG_HAVE_OPROFILE=y
CONFIG_KPROBES=y
CONFIG_KRETPROBES=y
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_KRETPROBES=y
CONFIG_HAVE_ARCH_TRACEHOOK=y
CONFIG_USE_GENERIC_SMP_HELPERS=y
# CONFIG_HAVE_GENERIC_DMA_COHERENT is not set
CONFIG_SLABINFO=y
CONFIG_RT_MUTEXES=y
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0
CONFIG_MODULES=y
# CONFIG_MODULE_FORCE_LOAD is not set
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
CONFIG_MODVERSIONS=y
# CONFIG_MODULE_SRCVERSION_ALL is not set
CONFIG_INIT_ALL_POSSIBLE=y
CONFIG_STOP_MACHINE=y
CONFIG_BLOCK=y
# CONFIG_BLK_DEV_IO_TRACE is not set
CONFIG_BLK_DEV_BSG=y
# CONFIG_BLK_DEV_INTEGRITY is not set
CONFIG_BLOCK_COMPAT=y

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_DEFAULT_AS is not set
CONFIG_DEFAULT_DEADLINE=y
# CONFIG_DEFAULT_CFQ is not set
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="deadline"
CONFIG_PREEMPT_NOTIFIERS=y
CONFIG_CLASSIC_RCU=y
# CONFIG_FREEZER is not set

#
# Base setup
#

#
# Processor type and features
#
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ=y
CONFIG_HIGH_RES_TIMERS=y
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
CONFIG_64BIT=y
CONFIG_SMP=y
CONFIG_NR_CPUS=32
CONFIG_HOTPLUG_CPU=y
CONFIG_COMPAT=y
CONFIG_SYSVIPC_COMPAT=y
CONFIG_AUDIT_ARCH=y
CONFIG_S390_SWITCH_AMODE=y
CONFIG_S390_EXEC_PROTECT=y

#
# Code generation options
#
# CONFIG_MARCH_G5 is not set
CONFIG_MARCH_Z900=y
# CONFIG_MARCH_Z990 is not set
# CONFIG_MARCH_Z9_109 is not set
# CONFIG_MARCH_Z10 is not set
CONFIG_PACK_STACK=y
# CONFIG_SMALL_STACK is not set
CONFIG_CHECK_STACK=y
CONFIG_STACK_GUARD=256
# CONFIG_WARN_STACK is not set
CONFIG_ARCH_POPULATES_NODE_MAP=y

#
# Kernel preemption
#
# CONFIG_PREEMPT_NONE is not set
# CONFIG_PREEMPT_VOLUNTARY is not set
CONFIG_PREEMPT=y
# CONFIG_PREEMPT_RCU is not set
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_SPARSEMEM_DEFAULT=y
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
CONFIG_ARCH_ENABLE_MEMORY_HOTREMOVE=y
CONFIG_SELECT_MEMORY_MODEL=y
# CONFIG_FLATMEM_MANUAL is not set
# CONFIG_DISCONTIGMEM_MANUAL is not set
CONFIG_SPARSEMEM_MANUAL=y
CONFIG_SPARSEMEM=y
CONFIG_HAVE_MEMORY_PRESENT=y
CONFIG_SPARSEMEM_EXTREME=y
CONFIG_SPARSEMEM_VMEMMAP_ENABLE=y
CONFIG_SPARSEMEM_VMEMMAP=y
CONFIG_MEMORY_HOTPLUG=y
CONFIG_MEMORY_HOTPLUG_SPARSE=y
CONFIG_MEMORY_HOTREMOVE=y
CONFIG_PAGEFLAGS_EXTENDED=y
CONFIG_SPLIT_PTLOCK_CPUS=4
CONFIG_MIGRATION=y
CONFIG_RESOURCES_64BIT=y
CONFIG_PHYS_ADDR_T_64BIT=y
CONFIG_ZONE_DMA_FLAG=1
CONFIG_BOUNCE=y
CONFIG_VIRT_TO_BUS=y
CONFIG_UNEVICTABLE_LRU=y

#
# I/O subsystem configuration
#
CONFIG_MACHCHK_WARNING=y
CONFIG_QDIO=y
CONFIG_CHSC_SCH=m

#
# Misc
#
CONFIG_IPL=y
# CONFIG_IPL_TAPE is not set
CONFIG_IPL_VM=y
CONFIG_BINFMT_ELF=y
CONFIG_COMPAT_BINFMT_ELF=y
# CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS is not set
# CONFIG_HAVE_AOUT is not set
CONFIG_BINFMT_MISC=m
CONFIG_FORCE_MAX_ZONEORDER=9
# CONFIG_PROCESS_DEBUG is not set
CONFIG_PFAULT=y
# CONFIG_SHARED_KERNEL is not set
# CONFIG_CMM is not set
# CONFIG_PAGE_STATES is not set
CONFIG_VIRT_TIMER=y
CONFIG_VIRT_CPU_ACCOUNTING=y
# CONFIG_APPLDATA_BASE is not set
CONFIG_HZ_100=y
# CONFIG_HZ_250 is not set
# CONFIG_HZ_300 is not set
# CONFIG_HZ_1000 is not set
CONFIG_HZ=100
CONFIG_SCHED_HRTICK=y
CONFIG_S390_HYPFS_FS=y
CONFIG_KEXEC=y
# CONFIG_ZFCPDUMP is not set
CONFIG_S390_GUEST=y
CONFIG_NET=y

#
# Networking options
#
# CONFIG_NET_NS is not set
CONFIG_COMPAT_NET_DEV_OPS=y
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
CONFIG_UNIX=y
CONFIG_XFRM=y
# CONFIG_XFRM_USER is not set
# CONFIG_XFRM_SUB_POLICY is not set
# CONFIG_XFRM_MIGRATE is not set
# CONFIG_XFRM_STATISTICS is not set
CONFIG_NET_KEY=y
# CONFIG_NET_KEY_MIGRATE is not set
CONFIG_IUCV=y
CONFIG_AFIUCV=m
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
CONFIG_IP_FIB_HASH=y
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_ARPD is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_XFRM_TUNNEL is not set
CONFIG_INET_TUNNEL=y
CONFIG_INET_XFRM_MODE_TRANSPORT=y
CONFIG_INET_XFRM_MODE_TUNNEL=y
CONFIG_INET_XFRM_MODE_BEET=y
CONFIG_INET_LRO=y
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
# CONFIG_TCP_CONG_ADVANCED is not set
CONFIG_TCP_CONG_CUBIC=y
CONFIG_DEFAULT_TCP_CONG="cubic"
# CONFIG_TCP_MD5SIG is not set
CONFIG_IPV6=y
# CONFIG_IPV6_PRIVACY is not set
# CONFIG_IPV6_ROUTER_PREF is not set
# CONFIG_IPV6_OPTIMISTIC_DAD is not set
# CONFIG_INET6_AH is not set
# CONFIG_INET6_ESP is not set
# CONFIG_INET6_IPCOMP is not set
# CONFIG_IPV6_MIP6 is not set
# CONFIG_INET6_XFRM_TUNNEL is not set
# CONFIG_INET6_TUNNEL is not set
CONFIG_INET6_XFRM_MODE_TRANSPORT=y
CONFIG_INET6_XFRM_MODE_TUNNEL=y
CONFIG_INET6_XFRM_MODE_BEET=y
# CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION is not set
CONFIG_IPV6_SIT=y
CONFIG_IPV6_NDISC_NODETYPE=y
# CONFIG_IPV6_TUNNEL is not set
# CONFIG_IPV6_MULTIPLE_TABLES is not set
# CONFIG_IPV6_MROUTE is not set
# CONFIG_NETWORK_SECMARK is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
CONFIG_NETFILTER_ADVANCED=y

#
# Core Netfilter Configuration
#
CONFIG_NETFILTER_NETLINK=m
CONFIG_NETFILTER_NETLINK_QUEUE=m
CONFIG_NETFILTER_NETLINK_LOG=m
CONFIG_NF_CONNTRACK=m
# CONFIG_NF_CT_ACCT is not set
# CONFIG_NF_CONNTRACK_MARK is not set
# CONFIG_NF_CONNTRACK_EVENTS is not set
# CONFIG_NF_CT_PROTO_DCCP is not set
# CONFIG_NF_CT_PROTO_SCTP is not set
# CONFIG_NF_CT_PROTO_UDPLITE is not set
# CONFIG_NF_CONNTRACK_AMANDA is not set
# CONFIG_NF_CONNTRACK_FTP is not set
# CONFIG_NF_CONNTRACK_H323 is not set
# CONFIG_NF_CONNTRACK_IRC is not set
# CONFIG_NF_CONNTRACK_NETBIOS_NS is not set
# CONFIG_NF_CONNTRACK_PPTP is not set
# CONFIG_NF_CONNTRACK_SANE is not set
# CONFIG_NF_CONNTRACK_SIP is not set
# CONFIG_NF_CONNTRACK_TFTP is not set
# CONFIG_NF_CT_NETLINK is not set
# CONFIG_NETFILTER_XTABLES is not set
# CONFIG_IP_VS is not set

#
# IP: Netfilter Configuration
#
# CONFIG_NF_DEFRAG_IPV4 is not set
# CONFIG_NF_CONNTRACK_IPV4 is not set
# CONFIG_IP_NF_QUEUE is not set
# CONFIG_IP_NF_IPTABLES is not set
# CONFIG_IP_NF_ARPTABLES is not set

#
# IPv6: Netfilter Configuration
#
# CONFIG_NF_CONNTRACK_IPV6 is not set
# CONFIG_IP6_NF_QUEUE is not set
# CONFIG_IP6_NF_IPTABLES is not set
# CONFIG_IP_DCCP is not set
CONFIG_IP_SCTP=m
# CONFIG_SCTP_DBG_MSG is not set
# CONFIG_SCTP_DBG_OBJCNT is not set
# CONFIG_SCTP_HMAC_NONE is not set
# CONFIG_SCTP_HMAC_SHA1 is not set
CONFIG_SCTP_HMAC_MD5=y
# CONFIG_TIPC is not set
# CONFIG_ATM is not set
# CONFIG_BRIDGE is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
CONFIG_NET_SCHED=y

#
# Queueing/Scheduling
#
CONFIG_NET_SCH_CBQ=m
# CONFIG_NET_SCH_HTB is not set
# CONFIG_NET_SCH_HFSC is not set
CONFIG_NET_SCH_PRIO=m
CONFIG_NET_SCH_MULTIQ=y
CONFIG_NET_SCH_RED=m
CONFIG_NET_SCH_SFQ=m
CONFIG_NET_SCH_TEQL=m
CONFIG_NET_SCH_TBF=m
CONFIG_NET_SCH_GRED=m
CONFIG_NET_SCH_DSMARK=m
# CONFIG_NET_SCH_NETEM is not set
# CONFIG_NET_SCH_DRR is not set
# CONFIG_NET_SCH_INGRESS is not set

#
# Classification
#
CONFIG_NET_CLS=y
# CONFIG_NET_CLS_BASIC is not set
CONFIG_NET_CLS_TCINDEX=m
CONFIG_NET_CLS_ROUTE4=m
CONFIG_NET_CLS_ROUTE=y
CONFIG_NET_CLS_FW=m
CONFIG_NET_CLS_U32=m
# CONFIG_CLS_U32_PERF is not set
CONFIG_CLS_U32_MARK=y
CONFIG_NET_CLS_RSVP=m
CONFIG_NET_CLS_RSVP6=m
CONFIG_NET_CLS_FLOW=m
# CONFIG_NET_CLS_CGROUP is not set
# CONFIG_NET_EMATCH is not set
CONFIG_NET_CLS_ACT=y
CONFIG_NET_ACT_POLICE=y
# CONFIG_NET_ACT_GACT is not set
# CONFIG_NET_ACT_MIRRED is not set
CONFIG_NET_ACT_NAT=m
# CONFIG_NET_ACT_PEDIT is not set
# CONFIG_NET_ACT_SIMP is not set
# CONFIG_NET_ACT_SKBEDIT is not set
# CONFIG_NET_CLS_IND is not set
CONFIG_NET_SCH_FIFO=y
# CONFIG_DCB is not set

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_NET_TCPPROBE is not set
CONFIG_CAN=m
CONFIG_CAN_RAW=m
CONFIG_CAN_BCM=m

#
# CAN Device Drivers
#
CONFIG_CAN_VCAN=m
# CONFIG_CAN_DEBUG_DEVICES is not set
# CONFIG_AF_RXRPC is not set
# CONFIG_PHONET is not set
# CONFIG_RFKILL is not set
# CONFIG_NET_9P is not set
# CONFIG_PCMCIA is not set
CONFIG_CCW=y

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=y
# CONFIG_FIRMWARE_IN_KERNEL is not set
CONFIG_EXTRA_FIRMWARE=""
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_DEBUG_DEVRES is not set
CONFIG_SYS_HYPERVISOR=y
# CONFIG_CONNECTOR is not set
CONFIG_BLK_DEV=y
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=m
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
CONFIG_BLK_DEV_NBD=m
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=4096
CONFIG_BLK_DEV_XIP=y
# CONFIG_CDROM_PKTCDVD is not set
# CONFIG_ATA_OVER_ETH is not set

#
# S/390 block device drivers
#
CONFIG_BLK_DEV_XPRAM=m
# CONFIG_DCSSBLK is not set
CONFIG_DASD=y
CONFIG_DASD_PROFILE=y
CONFIG_DASD_ECKD=y
CONFIG_DASD_FBA=y
CONFIG_DASD_DIAG=y
CONFIG_DASD_EER=y
CONFIG_VIRTIO_BLK=m
CONFIG_MISC_DEVICES=y
# CONFIG_EEPROM_93CX6 is not set
# CONFIG_ENCLOSURE_SERVICES is not set
# CONFIG_C2PORT is not set

#
# SCSI device support
#
# CONFIG_RAID_ATTRS is not set
CONFIG_SCSI=y
# CONFIG_SCSI_DMA is not set
# CONFIG_SCSI_TGT is not set
CONFIG_SCSI_NETLINK=y
CONFIG_SCSI_PROC_FS=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
CONFIG_CHR_DEV_ST=y
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=y
CONFIG_BLK_DEV_SR_VENDOR=y
CONFIG_CHR_DEV_SG=y
# CONFIG_CHR_DEV_SCH is not set

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_CONSTANTS=y
CONFIG_SCSI_LOGGING=y
CONFIG_SCSI_SCAN_ASYNC=y
CONFIG_SCSI_WAIT_SCAN=m

#
# SCSI Transports
#
# CONFIG_SCSI_SPI_ATTRS is not set
CONFIG_SCSI_FC_ATTRS=y
# CONFIG_SCSI_ISCSI_ATTRS is not set
# CONFIG_SCSI_SAS_ATTRS is not set
# CONFIG_SCSI_SAS_LIBSAS is not set
# CONFIG_SCSI_SRP_ATTRS is not set
CONFIG_SCSI_LOWLEVEL=y
# CONFIG_ISCSI_TCP is not set
# CONFIG_SCSI_DEBUG is not set
CONFIG_ZFCP=y
CONFIG_SCSI_DH=m
CONFIG_SCSI_DH_RDAC=m
CONFIG_SCSI_DH_HP_SW=m
CONFIG_SCSI_DH_EMC=m
CONFIG_SCSI_DH_ALUA=m
# CONFIG_SCSI_OSD_INITIATOR is not set
CONFIG_MD=y
CONFIG_BLK_DEV_MD=y
CONFIG_MD_AUTODETECT=y
CONFIG_MD_LINEAR=m
CONFIG_MD_RAID0=m
CONFIG_MD_RAID1=m
# CONFIG_MD_RAID10 is not set
# CONFIG_MD_RAID456 is not set
CONFIG_MD_MULTIPATH=m
# CONFIG_MD_FAULTY is not set
CONFIG_BLK_DEV_DM=y
# CONFIG_DM_DEBUG is not set
CONFIG_DM_CRYPT=y
CONFIG_DM_SNAPSHOT=y
CONFIG_DM_MIRROR=y
CONFIG_DM_ZERO=y
CONFIG_DM_MULTIPATH=m
# CONFIG_DM_DELAY is not set
# CONFIG_DM_UEVENT is not set
CONFIG_NETDEVICES=y
# CONFIG_IFB is not set
CONFIG_DUMMY=m
CONFIG_BONDING=m
# CONFIG_MACVLAN is not set
CONFIG_EQUALIZER=m
CONFIG_TUN=m
CONFIG_VETH=m
CONFIG_NET_ETHERNET=y
# CONFIG_MII is not set
# CONFIG_IBM_NEW_EMAC_ZMII is not set
# CONFIG_IBM_NEW_EMAC_RGMII is not set
# CONFIG_IBM_NEW_EMAC_TAH is not set
# CONFIG_IBM_NEW_EMAC_EMAC4 is not set
# CONFIG_IBM_NEW_EMAC_NO_FLOW_CTRL is not set
# CONFIG_IBM_NEW_EMAC_MAL_CLR_ICINTSTAT is not set
# CONFIG_IBM_NEW_EMAC_MAL_COMMON_ERR is not set
CONFIG_NETDEV_1000=y
CONFIG_NETDEV_10000=y
# CONFIG_TR is not set
# CONFIG_WAN is not set

#
# S/390 network device drivers
#
CONFIG_LCS=m
CONFIG_CTCM=m
# CONFIG_NETIUCV is not set
# CONFIG_SMSGIUCV is not set
# CONFIG_CLAW is not set
CONFIG_QETH=y
CONFIG_QETH_L2=y
CONFIG_QETH_L3=y
CONFIG_QETH_IPV6=y
CONFIG_CCWGROUP=y
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
# CONFIG_NETCONSOLE is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set
CONFIG_VIRTIO_NET=m

#
# Character devices
#
CONFIG_DEVKMEM=y
CONFIG_UNIX98_PTYS=y
# CONFIG_DEVPTS_MULTIPLE_INSTANCES is not set
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256
CONFIG_HVC_DRIVER=y
CONFIG_HVC_IUCV=y
CONFIG_VIRTIO_CONSOLE=y
CONFIG_HW_RANDOM=m
CONFIG_HW_RANDOM_VIRTIO=m
# CONFIG_R3964 is not set
CONFIG_RAW_DRIVER=m
CONFIG_MAX_RAW_DEVS=256
# CONFIG_HANGCHECK_TIMER is not set

#
# S/390 character device drivers
#
CONFIG_TN3270=y
CONFIG_TN3270_TTY=y
CONFIG_TN3270_FS=m
CONFIG_TN3270_CONSOLE=y
CONFIG_TN3215=y
CONFIG_TN3215_CONSOLE=y
CONFIG_CCW_CONSOLE=y
CONFIG_SCLP_TTY=y
CONFIG_SCLP_CONSOLE=y
CONFIG_SCLP_VT220_TTY=y
CONFIG_SCLP_VT220_CONSOLE=y
CONFIG_SCLP_CPI=m
CONFIG_S390_TAPE=m

#
# S/390 tape interface support
#
CONFIG_S390_TAPE_BLOCK=y

#
# S/390 tape hardware support
#
CONFIG_S390_TAPE_34XX=m
# CONFIG_S390_TAPE_3590 is not set
# CONFIG_VMLOGRDR is not set
# CONFIG_VMCP is not set
# CONFIG_MONREADER is not set
CONFIG_MONWRITER=m
CONFIG_S390_VMUR=m
# CONFIG_POWER_SUPPLY is not set
# CONFIG_THERMAL is not set
# CONFIG_THERMAL_HWMON is not set
# CONFIG_WATCHDOG is not set
# CONFIG_REGULATOR is not set
# CONFIG_MEMSTICK is not set
# CONFIG_NEW_LEDS is not set
CONFIG_ACCESSIBILITY=y
# CONFIG_STAGING is not set

#
# File systems
#
CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not set
# CONFIG_EXT2_FS_XIP is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
# CONFIG_EXT3_FS_POSIX_ACL is not set
# CONFIG_EXT3_FS_SECURITY is not set
# CONFIG_EXT4_FS is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
CONFIG_FS_POSIX_ACL=y
CONFIG_FILE_LOCKING=y
# CONFIG_XFS_FS is not set
# CONFIG_GFS2_FS is not set
# CONFIG_OCFS2_FS is not set
CONFIG_DNOTIFY=y
CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set
# CONFIG_FUSE_FS is not set
CONFIG_GENERIC_ACL=y

#
# CD-ROM/DVD Filesystems
#
# CONFIG_ISO9660_FS is not set
# CONFIG_UDF_FS is not set

#
# DOS/FAT/NT Filesystems
#
# CONFIG_MSDOS_FS is not set
# CONFIG_VFAT_FS is not set
# CONFIG_NTFS_FS is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_PROC_SYSCTL=y
CONFIG_PROC_PAGE_MONITOR=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
CONFIG_TMPFS_POSIX_ACL=y
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_CONFIGFS_FS=m

#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_OMFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
CONFIG_NETWORK_FILESYSTEMS=y
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
# CONFIG_NFS_V3_ACL is not set
# CONFIG_NFS_V4 is not set
CONFIG_NFSD=y
CONFIG_NFSD_V3=y
# CONFIG_NFSD_V3_ACL is not set
# CONFIG_NFSD_V4 is not set
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=y
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=y
# CONFIG_SUNRPC_REGISTER_V4 is not set
# CONFIG_RPCSEC_GSS_KRB5 is not set
# CONFIG_RPCSEC_GSS_SPKM3 is not set
# CONFIG_SMB_FS is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set

#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
# CONFIG_OSF_PARTITION is not set
# CONFIG_AMIGA_PARTITION is not set
# CONFIG_ATARI_PARTITION is not set
CONFIG_IBM_PARTITION=y
# CONFIG_MAC_PARTITION is not set
CONFIG_MSDOS_PARTITION=y
# CONFIG_BSD_DISKLABEL is not set
# CONFIG_MINIX_SUBPARTITION is not set
# CONFIG_SOLARIS_X86_PARTITION is not set
# CONFIG_UNIXWARE_DISKLABEL is not set
# CONFIG_LDM_PARTITION is not set
# CONFIG_SGI_PARTITION is not set
# CONFIG_ULTRIX_PARTITION is not set
# CONFIG_SUN_PARTITION is not set
# CONFIG_KARMA_PARTITION is not set
# CONFIG_EFI_PARTITION is not set
# CONFIG_SYSV68_PARTITION is not set
# CONFIG_NLS is not set
CONFIG_DLM=m
# CONFIG_DLM_DEBUG is not set

#
# Kernel hacking
#
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
# CONFIG_PRINTK_TIME is not set
CONFIG_ENABLE_WARN_DEPRECATED=y
CONFIG_ENABLE_MUST_CHECK=y
CONFIG_FRAME_WARN=2048
CONFIG_MAGIC_SYSRQ=y
# CONFIG_UNUSED_SYMBOLS is not set
CONFIG_DEBUG_FS=y
# CONFIG_HEADERS_CHECK is not set
CONFIG_DEBUG_KERNEL=y
# CONFIG_SCHED_DEBUG is not set
# CONFIG_SCHEDSTATS is not set
# CONFIG_TIMER_STATS is not set
# CONFIG_DEBUG_OBJECTS is not set
# CONFIG_DEBUG_SLAB is not set
CONFIG_DEBUG_PREEMPT=y
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_RT_MUTEX_TESTER is not set
CONFIG_DEBUG_SPINLOCK=y
CONFIG_DEBUG_MUTEXES=y
# CONFIG_DEBUG_LOCK_ALLOC is not set
# CONFIG_PROVE_LOCKING is not set
# CONFIG_LOCK_STAT is not set
CONFIG_DEBUG_SPINLOCK_SLEEP=y
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
# CONFIG_DEBUG_KOBJECT is not set
CONFIG_DEBUG_BUGVERBOSE=y
# CONFIG_DEBUG_INFO is not set
# CONFIG_DEBUG_VM is not set
# CONFIG_DEBUG_WRITECOUNT is not set
CONFIG_DEBUG_MEMORY_INIT=y
# CONFIG_DEBUG_LIST is not set
# CONFIG_DEBUG_SG is not set
# CONFIG_DEBUG_NOTIFIERS is not set
# CONFIG_FRAME_POINTER is not set
# CONFIG_RCU_TORTURE_TEST is not set
# CONFIG_RCU_CPU_STALL_DETECTOR is not set
# CONFIG_KPROBES_SANITY_TEST is not set
# CONFIG_BACKTRACE_SELF_TEST is not set
# CONFIG_DEBUG_BLOCK_EXT_DEVT is not set
# CONFIG_LKDTM is not set
# CONFIG_FAULT_INJECTION is not set
# CONFIG_LATENCYTOP is not set
CONFIG_SYSCTL_SYSCALL_CHECK=y
CONFIG_HAVE_FUNCTION_TRACER=y

#
# Tracers
#
# CONFIG_FUNCTION_TRACER is not set
# CONFIG_IRQSOFF_TRACER is not set
# CONFIG_PREEMPT_TRACER is not set
# CONFIG_SCHED_TRACER is not set
# CONFIG_CONTEXT_SWITCH_TRACER is not set
# CONFIG_BOOT_TRACER is not set
# CONFIG_TRACE_BRANCH_PROFILING is not set
# CONFIG_STACK_TRACER is not set
# CONFIG_DYNAMIC_PRINTK_DEBUG is not set
CONFIG_SAMPLES=y
# CONFIG_SAMPLE_KOBJECT is not set
# CONFIG_SAMPLE_KPROBES is not set
# CONFIG_DEBUG_PAGEALLOC is not set

#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set
# CONFIG_SECURITYFS is not set
# CONFIG_SECURITY_FILE_CAPABILITIES is not set
CONFIG_CRYPTO=y

#
# Crypto core or helper
#
CONFIG_CRYPTO_FIPS=y
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_ALGAPI2=y
CONFIG_CRYPTO_AEAD=m
CONFIG_CRYPTO_AEAD2=y
CONFIG_CRYPTO_BLKCIPHER=y
CONFIG_CRYPTO_BLKCIPHER2=y
CONFIG_CRYPTO_HASH=m
CONFIG_CRYPTO_HASH2=y
CONFIG_CRYPTO_RNG=m
CONFIG_CRYPTO_RNG2=y
CONFIG_CRYPTO_MANAGER=y
CONFIG_CRYPTO_MANAGER2=y
CONFIG_CRYPTO_GF128MUL=m
# CONFIG_CRYPTO_NULL is not set
# CONFIG_CRYPTO_CRYPTD is not set
CONFIG_CRYPTO_AUTHENC=m
# CONFIG_CRYPTO_TEST is not set

#
# Authenticated Encryption with Associated Data
#
CONFIG_CRYPTO_CCM=m
CONFIG_CRYPTO_GCM=m
CONFIG_CRYPTO_SEQIV=m

#
# Block modes
#
CONFIG_CRYPTO_CBC=y
CONFIG_CRYPTO_CTR=m
CONFIG_CRYPTO_CTS=m
CONFIG_CRYPTO_ECB=m
# CONFIG_CRYPTO_LRW is not set
CONFIG_CRYPTO_PCBC=m
# CONFIG_CRYPTO_XTS is not set

#
# Hash modes
#
CONFIG_CRYPTO_HMAC=m
# CONFIG_CRYPTO_XCBC is not set

#
# Digest
#
CONFIG_CRYPTO_CRC32C=m
# CONFIG_CRYPTO_MD4 is not set
CONFIG_CRYPTO_MD5=m
# CONFIG_CRYPTO_MICHAEL_MIC is not set
CONFIG_CRYPTO_RMD128=m
CONFIG_CRYPTO_RMD160=m
CONFIG_CRYPTO_RMD256=m
CONFIG_CRYPTO_RMD320=m
CONFIG_CRYPTO_SHA1=m
# CONFIG_CRYPTO_SHA256 is not set
# CONFIG_CRYPTO_SHA512 is not set
# CONFIG_CRYPTO_TGR192 is not set
# CONFIG_CRYPTO_WP512 is not set

#
# Ciphers
#
CONFIG_CRYPTO_AES=m
# CONFIG_CRYPTO_ANUBIS is not set
# CONFIG_CRYPTO_ARC4 is not set
# CONFIG_CRYPTO_BLOWFISH is not set
CONFIG_CRYPTO_CAMELLIA=m
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST6 is not set
# CONFIG_CRYPTO_DES is not set
CONFIG_CRYPTO_FCRYPT=m
# CONFIG_CRYPTO_KHAZAD is not set
CONFIG_CRYPTO_SALSA20=m
CONFIG_CRYPTO_SEED=m
# CONFIG_CRYPTO_SERPENT is not set
# CONFIG_CRYPTO_TEA is not set
# CONFIG_CRYPTO_TWOFISH is not set

#
# Compression
#
# CONFIG_CRYPTO_DEFLATE is not set
CONFIG_CRYPTO_LZO=m

#
# Random Number Generation
#
CONFIG_CRYPTO_ANSI_CPRNG=m
CONFIG_CRYPTO_HW=y
CONFIG_ZCRYPT=m
# CONFIG_ZCRYPT_MONOLITHIC is not set
# CONFIG_CRYPTO_SHA1_S390 is not set
# CONFIG_CRYPTO_SHA256_S390 is not set
CONFIG_CRYPTO_SHA512_S390=m
# CONFIG_CRYPTO_DES_S390 is not set
# CONFIG_CRYPTO_AES_S390 is not set
CONFIG_S390_PRNG=m

#
# Library routines
#
CONFIG_BITREVERSE=m
CONFIG_GENERIC_FIND_LAST_BIT=y
# CONFIG_CRC_CCITT is not set
# CONFIG_CRC16 is not set
CONFIG_CRC_T10DIF=y
# CONFIG_CRC_ITU_T is not set
CONFIG_CRC32=m
CONFIG_CRC7=m
CONFIG_LIBCRC32C=m
CONFIG_LZO_COMPRESS=m
CONFIG_LZO_DECOMPRESS=m
CONFIG_PLIST=y
CONFIG_HAVE_KVM=y
CONFIG_VIRTUALIZATION=y
CONFIG_KVM=m
CONFIG_VIRTIO=y
CONFIG_VIRTIO_RING=y
CONFIG_VIRTIO_BALLOON=m
CONFIG_USB_STORAGE_CYPRESS_ATACB=n
--
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.

2008-12-18 00:14:25

by Randy Dunlap

[permalink] [raw]
Subject: Re: linux-next: Tree for December 17 (DVB)

On Wed, 17 Dec 2008 23:25:36 +1100 Stephen Rothwell wrote:

> Hi all,
>
> Changes since 20081216:
>
> Undropped tree:
> v4l-dvb


build-r7329.out:/local/linsrc/linux-next-20081217/drivers/media/video/tuner-core.c:1111: error: 'tuner_ioctl' undeclared here (not in a function)
build-r7329.out:make[4]: *** [drivers/media/video/tuner-core.o] Error 1

config attached.


---
~Randy


Attachments:
config-r7329 (61.99 kB)

2008-12-18 00:14:38

by Kevin Winchester

[permalink] [raw]
Subject: Re: linux-next: Tree for December 17 (Radeon DRM BUG)

Stephen Rothwell wrote:
> Hi all,
>
>

I get the following BUG in the radeon drm code with today's linux-next
when I run "startx". I have not built or tested linux-next in a while,
but the problem definitely does not occur in mainline.

Dec 17 20:02:41 winchester [ 43.741709] BUG: unable to handle kernel
NULL pointer dereference at 0000000000000000
Dec 17 20:02:41 winchester [ 43.741723] IP: [<ffffffff8038411d>]
radeon_cp_init+0x311/0x9f6
Dec 17 20:02:41 winchester [ 43.741740] PGD 4d501067 PUD 4d533067 PMD 0
Dec 17 20:02:41 winchester [ 43.741747] Oops: 0002 [#1]
Dec 17 20:02:41 winchester [ 43.741751] last sysfs file:
/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/resource
Dec 17 20:02:41 winchester [ 43.741757] CPU 0
Dec 17 20:02:41 winchester [ 43.741760] Modules linked in:
Dec 17 20:02:41 winchester [ 43.741766] Pid: 3630, comm: X Not tainted
2.6.28-rc8-next-20081217 #192
Dec 17 20:02:41 winchester [ 43.741771] RIP:
0010:[<ffffffff8038411d>] [<ffffffff8038411d>] radeon_cp_init+0x311/0x9f6
Dec 17 20:02:41 winchester [ 43.741780] RSP: 0018:ffff88004d575e18
EFLAGS: 00010282
Dec 17 20:02:41 winchester [ 43.741784] RAX: ffff88004f36d640 RBX:
ffff88004f257400 RCX: ffff88004f36d640
Dec 17 20:02:41 winchester [ 43.741789] RDX: 0000002000000002 RSI:
ffff88004f3fd000 RDI: ffff88004f085800
Dec 17 20:02:41 winchester [ 43.741793] RBP: ffff88004d575e38 R08:
ffff88004d559600 R09: ffff88004d575ef8
Dec 17 20:02:41 winchester [ 43.741798] R10: 0000000000000000 R11:
0000000000003202 R12: ffff88004f085800
Dec 17 20:02:41 winchester [ 43.741802] R13: ffff88004eb9d500 R14:
0000000000000000 R15: ffff88004eb9db00
Dec 17 20:02:41 winchester [ 43.741808] FS: 00007f845ffa26f0(0000)
GS:ffffffff80699e40(0000) knlGS:0000000000000000
Dec 17 20:02:41 winchester [ 43.741813] CS: 0010 DS: 0000 ES: 0000
CR0: 000000008005003b
Dec 17 20:02:41 winchester [ 43.741817] CR2: 0000000000000000 CR3:
000000004d55f000 CR4: 00000000000006e0
Dec 17 20:02:41 winchester [ 43.741822] DR0: 0000000000000000 DR1:
0000000000000000 DR2: 0000000000000000
Dec 17 20:02:41 winchester [ 43.741826] DR3: 0000000000000000 DR6:
00000000ffff0ff0 DR7: 0000000000000400
Dec 17 20:02:41 winchester [ 43.741832] Process X (pid: 3630,
threadinfo ffff88004d574000, task ffff88004f287330)
Dec 17 20:02:41 winchester [ 43.741835] Stack:
Dec 17 20:02:41 winchester [ 43.741838] 00000000fffffff4
0000000040786440 ffff88004f085800 ffffffff80383e0c
Dec 17 20:02:41 winchester [ 43.741845] ffff88004d575e98
ffffffff8037249e ffff88004d575e48 ffff88004d575e48
Dec 17 20:02:41 winchester [ 43.741852] 00007fff67fbf5a0
ffff88004eb9d500 ffff88004f08583c ffff88004d559600
Dec 17 20:02:41 winchester [ 43.741860] Call Trace:
Dec 17 20:02:41 winchester [ 43.741865] [<ffffffff80383e0c>] ?
radeon_cp_init+0x0/0x9f6
Dec 17 20:02:41 winchester [ 43.741871] [<ffffffff8037249e>]
drm_ioctl+0x1de/0x270
Dec 17 20:02:41 winchester [ 43.741881] [<ffffffff80298d2e>]
vfs_ioctl+0x4a/0x55
Dec 17 20:02:41 winchester [ 43.741890] [<ffffffff8029911a>]
do_vfs_ioctl+0x3b2/0x3ff
Dec 17 20:02:41 winchester [ 43.741896] [<ffffffff8028d0fa>] ?
fsnotify_modify+0x4e/0x53
Dec 17 20:02:41 winchester [ 43.741904] [<ffffffff802991ac>]
sys_ioctl+0x45/0x80
Dec 17 20:02:41 winchester [ 43.741910] [<ffffffff8028de98>] ?
sys_write+0x62/0x72
Dec 17 20:02:41 winchester [ 43.741917] [<ffffffff8020b94b>]
system_call_fastpath+0x16/0x1b
Dec 17 20:02:41 winchester [ 43.741925] Code: 00 00 49 8b 45 60 48 89
83 f8 00 00 00 49 8b 45 68 48 89 83 00 01 00 00 49 8b 45 70 48 89 83 08
01 00 00 e8 7e da fe ff 48 85 c0 <49> 89 06 48 c7 c6 b0 4e 4d 80 48 c7
c7 13 4a 5c 80 0f 84 a7 fd
Dec 17 20:02:41 winchester [ 43.741970] RIP [<ffffffff8038411d>]
radeon_cp_init+0x311/0x9f6
Dec 17 20:02:41 winchester [ 43.741977] RSP <ffff88004d575e18>
Dec 17 20:02:41 winchester [ 43.741980] CR2: 0000000000000000
Dec 17 20:02:41 winchester [ 43.741984] ---[ end trace
dc6d31ddec008340 ]---
Dec 17 20:02:41 winchester [ 43.761235] [drm:drm_release] *ERROR*
Device busy: 1

What other information can I provide?

--
Kevin Winchester

2008-12-18 06:48:19

by Dave Airlie

[permalink] [raw]
Subject: Re: linux-next: Tree for December 17 (Radeon DRM BUG)

On Thu, Dec 18, 2008 at 10:14 AM, Kevin Winchester
<[email protected]> wrote:
> Stephen Rothwell wrote:
>>
>> Hi all,
>>
>>
>
> I get the following BUG in the radeon drm code with today's linux-next when
> I run "startx". I have not built or tested linux-next in a while, but the
> problem definitely does not occur in mainline.

Do you have another X server running or just console?

can you get a full dmesg with

echo 1 > /sys/module/drm/parameters/debug

Dave.

>
> Dec 17 20:02:41 winchester [ 43.741709] BUG: unable to handle kernel NULL
> pointer dereference at 0000000000000000
> Dec 17 20:02:41 winchester [ 43.741723] IP: [<ffffffff8038411d>]
> radeon_cp_init+0x311/0x9f6
> Dec 17 20:02:41 winchester [ 43.741740] PGD 4d501067 PUD 4d533067 PMD 0
> Dec 17 20:02:41 winchester [ 43.741747] Oops: 0002 [#1]
> Dec 17 20:02:41 winchester [ 43.741751] last sysfs file:
> /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/resource
> Dec 17 20:02:41 winchester [ 43.741757] CPU 0
> Dec 17 20:02:41 winchester [ 43.741760] Modules linked in:
> Dec 17 20:02:41 winchester [ 43.741766] Pid: 3630, comm: X Not tainted
> 2.6.28-rc8-next-20081217 #192
> Dec 17 20:02:41 winchester [ 43.741771] RIP: 0010:[<ffffffff8038411d>]
> [<ffffffff8038411d>] radeon_cp_init+0x311/0x9f6
> Dec 17 20:02:41 winchester [ 43.741780] RSP: 0018:ffff88004d575e18
> EFLAGS: 00010282
> Dec 17 20:02:41 winchester [ 43.741784] RAX: ffff88004f36d640 RBX:
> ffff88004f257400 RCX: ffff88004f36d640
> Dec 17 20:02:41 winchester [ 43.741789] RDX: 0000002000000002 RSI:
> ffff88004f3fd000 RDI: ffff88004f085800
> Dec 17 20:02:41 winchester [ 43.741793] RBP: ffff88004d575e38 R08:
> ffff88004d559600 R09: ffff88004d575ef8
> Dec 17 20:02:41 winchester [ 43.741798] R10: 0000000000000000 R11:
> 0000000000003202 R12: ffff88004f085800
> Dec 17 20:02:41 winchester [ 43.741802] R13: ffff88004eb9d500 R14:
> 0000000000000000 R15: ffff88004eb9db00
> Dec 17 20:02:41 winchester [ 43.741808] FS: 00007f845ffa26f0(0000)
> GS:ffffffff80699e40(0000) knlGS:0000000000000000
> Dec 17 20:02:41 winchester [ 43.741813] CS: 0010 DS: 0000 ES: 0000 CR0:
> 000000008005003b
> Dec 17 20:02:41 winchester [ 43.741817] CR2: 0000000000000000 CR3:
> 000000004d55f000 CR4: 00000000000006e0
> Dec 17 20:02:41 winchester [ 43.741822] DR0: 0000000000000000 DR1:
> 0000000000000000 DR2: 0000000000000000
> Dec 17 20:02:41 winchester [ 43.741826] DR3: 0000000000000000 DR6:
> 00000000ffff0ff0 DR7: 0000000000000400
> Dec 17 20:02:41 winchester [ 43.741832] Process X (pid: 3630, threadinfo
> ffff88004d574000, task ffff88004f287330)
> Dec 17 20:02:41 winchester [ 43.741835] Stack:
> Dec 17 20:02:41 winchester [ 43.741838] 00000000fffffff4 0000000040786440
> ffff88004f085800 ffffffff80383e0c
> Dec 17 20:02:41 winchester [ 43.741845] ffff88004d575e98 ffffffff8037249e
> ffff88004d575e48 ffff88004d575e48
> Dec 17 20:02:41 winchester [ 43.741852] 00007fff67fbf5a0 ffff88004eb9d500
> ffff88004f08583c ffff88004d559600
> Dec 17 20:02:41 winchester [ 43.741860] Call Trace:
> Dec 17 20:02:41 winchester [ 43.741865] [<ffffffff80383e0c>] ?
> radeon_cp_init+0x0/0x9f6
> Dec 17 20:02:41 winchester [ 43.741871] [<ffffffff8037249e>]
> drm_ioctl+0x1de/0x270
> Dec 17 20:02:41 winchester [ 43.741881] [<ffffffff80298d2e>]
> vfs_ioctl+0x4a/0x55
> Dec 17 20:02:41 winchester [ 43.741890] [<ffffffff8029911a>]
> do_vfs_ioctl+0x3b2/0x3ff
> Dec 17 20:02:41 winchester [ 43.741896] [<ffffffff8028d0fa>] ?
> fsnotify_modify+0x4e/0x53
> Dec 17 20:02:41 winchester [ 43.741904] [<ffffffff802991ac>]
> sys_ioctl+0x45/0x80
> Dec 17 20:02:41 winchester [ 43.741910] [<ffffffff8028de98>] ?
> sys_write+0x62/0x72
> Dec 17 20:02:41 winchester [ 43.741917] [<ffffffff8020b94b>]
> system_call_fastpath+0x16/0x1b
> Dec 17 20:02:41 winchester [ 43.741925] Code: 00 00 49 8b 45 60 48 89 83
> f8 00 00 00 49 8b 45 68 48 89 83 00 01 00 00 49 8b 45 70 48 89 83 08 01 00
> 00 e8 7e da fe ff 48 85 c0 <49> 89 06 48 c7 c6 b0 4e 4d 80 48 c7 c7 13 4a 5c
> 80 0f 84 a7 fd
> Dec 17 20:02:41 winchester [ 43.741970] RIP [<ffffffff8038411d>]
> radeon_cp_init+0x311/0x9f6
> Dec 17 20:02:41 winchester [ 43.741977] RSP <ffff88004d575e18>
> Dec 17 20:02:41 winchester [ 43.741980] CR2: 0000000000000000
> Dec 17 20:02:41 winchester [ 43.741984] ---[ end trace dc6d31ddec008340
> ]---
> Dec 17 20:02:41 winchester [ 43.761235] [drm:drm_release] *ERROR* Device
> busy: 1
>
> What other information can I provide?
>
> --
> Kevin Winchester
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>

2008-12-18 09:48:00

by Martin Schwidefsky

[permalink] [raw]
Subject: Re: [BUILD-FAILURE] next-20081217-s390x-'struct device' has no member named 'knode_parent'

On Wed, 2008-12-17 at 23:47 +0530, Kamalesh Babulal wrote:
> drivers/s390/cio/device.c: In function 'io_subchannel_register':
> drivers/s390/cio/device.c:913: error: 'struct device' has no member
> named 'knode_parent'
> make[2]: *** [drivers/s390/cio/device.o] Error 1
> make[1]: *** [drivers/s390/cio] Error 2
> make: *** [drivers/s390] Error 2

Should be fixed now by the following patch from Cornelia:

commit efe46b59567ae999ff7d344170d21f093159ad80
Author: Cornelia Huck <[email protected]>
Date: Thu Dec 18 10:26:55 2008 +0100

[S390] cio: Use device_is_registered().

Check if a ccw device is registered via device_is_registered()
and not via the old kludge of checking the membership in driver
core internal klists.

Signed-off-by: Cornelia Huck <[email protected]>
Signed-off-by: Martin Schwidefsky <[email protected]>

You'll find the fix in the features branch of git390 which will be
included in the next linux-next kernel.

--
blue skies,
Martin.

"Reality continues to ruin my life." - Calvin.

2008-12-18 17:18:18

by Kamalesh Babulal

[permalink] [raw]
Subject: Re: [BUILD-FAILURE] next-20081217-s390x-'struct device' has no member named 'knode_parent'

* Martin Schwidefsky <[email protected]> [2008-12-18 10:47:45]:

> On Wed, 2008-12-17 at 23:47 +0530, Kamalesh Babulal wrote:
> > drivers/s390/cio/device.c: In function 'io_subchannel_register':
> > drivers/s390/cio/device.c:913: error: 'struct device' has no member
> > named 'knode_parent'
> > make[2]: *** [drivers/s390/cio/device.o] Error 1
> > make[1]: *** [drivers/s390/cio] Error 2
> > make: *** [drivers/s390] Error 2
>
> Should be fixed now by the following patch from Cornelia:
>
> commit efe46b59567ae999ff7d344170d21f093159ad80
> Author: Cornelia Huck <[email protected]>
> Date: Thu Dec 18 10:26:55 2008 +0100
>
> [S390] cio: Use device_is_registered().
>
> Check if a ccw device is registered via device_is_registered()
> and not via the old kludge of checking the membership in driver
> core internal klists.
>
> Signed-off-by: Cornelia Huck <[email protected]>
> Signed-off-by: Martin Schwidefsky <[email protected]>
>
> You'll find the fix in the features branch of git390 which will be
> included in the next linux-next kernel.

Hi Martin,

Thanks, the patch fixes the build failure.I tested the patch with
today's next (20081218), which also has the same build failure.

>
> --
> blue skies,
> Martin.
>
> "Reality continues to ruin my life." - Calvin.
>
>

--
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.

2008-12-18 17:20:11

by Randy Dunlap

[permalink] [raw]
Subject: Re: linux-next: Tree for December 17 (DVB)

On Wed, 17 Dec 2008 16:13:11 -0800 Randy Dunlap wrote:

> On Wed, 17 Dec 2008 23:25:36 +1100 Stephen Rothwell wrote:
>
> > Hi all,
> >
> > Changes since 20081216:
> >
> > Undropped tree:
> > v4l-dvb
>
>
> build-r7329.out:/local/linsrc/linux-next-20081217/drivers/media/video/tuner-core.c:1111: error: 'tuner_ioctl' undeclared here (not in a function)
> build-r7329.out:make[4]: *** [drivers/media/video/tuner-core.o] Error 1
>
> config attached.


Same build error in next-20081218.


---
~Randy

Subject: Re: linux-next: Tree for December 17 (Radeon DRM BUG)

On Thursday 18 December 2008, Dave Airlie wrote:
> On Thu, Dec 18, 2008 at 10:14 AM, Kevin Winchester
> <[email protected]> wrote:
> > Stephen Rothwell wrote:
> >>
> >> Hi all,
> >>
> >>
> >
> > I get the following BUG in the radeon drm code with today's linux-next when
> > I run "startx". I have not built or tested linux-next in a while, but the
> > problem definitely does not occur in mainline.

[...]

This reminds me that drm tree in linux-next still results in BSOD (Black
Screen Of Death) on starting X for me (as reported on Saturday [1]).

Actually there is more to it as I discovered that my custom X radeon driver
(which is xorg-x11-drv-ati-6.9.0-61.fc10.i386 with "radeon: no need for this
anymore" from radeon-gem-cs change reverted, please see [2] for my previous
monologue) works fine while following stock driver versions:

xorg-x11-drv-ati-6.8.0-19.fc9.i386
xorg-x11-drv-ati-6.9.0-61.fc10.i386
xorg-x11-drv-ati-6.9.0-62.fc10.i386

result in BSOD. OTOH they all work with next-20081128 (modulo hangs with
fc10 ones when "radeon: no need for this anymore" change is not reverted).

[ BTW xorg-x11-drv-ati-6.9.0-62.fc10.i386 still causes hangs when used with
non-Fedora kernels and Fedora/kms kernel still has performance problems ]

IOW there are a lot of compatibility issues in recent drm/radeon changes.

Dave, could you please start looking into these problems? I'm sure that we
all want recent drm changes + kms in 2.6.29 but given tight schedule and the
way things are looking right now I'm quite sceptical...

[1] http://lkml.org/lkml/2008/12/13/76
[2] http://lkml.org/lkml/2008/12/13/77

Thanks,
Bart

2008-12-18 20:49:45

by David Airlie

[permalink] [raw]
Subject: Re: linux-next: Tree for December 17 (Radeon DRM BUG)

On Thu, 2008-12-18 at 20:00 +0100, Bartlomiej Zolnierkiewicz wrote:
> On Thursday 18 December 2008, Dave Airlie wrote:
> > On Thu, Dec 18, 2008 at 10:14 AM, Kevin Winchester
> > <[email protected]> wrote:
> > > Stephen Rothwell wrote:
> > >>
> > >> Hi all,
> > >>
> > >>
> > >
> > > I get the following BUG in the radeon drm code with today's linux-next when
> > > I run "startx". I have not built or tested linux-next in a while, but the
> > > problem definitely does not occur in mainline.
>
> [...]
>
> This reminds me that drm tree in linux-next still results in BSOD (Black
> Screen Of Death) on starting X for me (as reported on Saturday [1]).
>
> Actually there is more to it as I discovered that my custom X radeon driver
> (which is xorg-x11-drv-ati-6.9.0-61.fc10.i386 with "radeon: no need for this
> anymore" from radeon-gem-cs change reverted, please see [2] for my previous
> monologue) works fine while following stock driver versions:
>
> xorg-x11-drv-ati-6.8.0-19.fc9.i386
> xorg-x11-drv-ati-6.9.0-61.fc10.i386
> xorg-x11-drv-ati-6.9.0-62.fc10.i386
>
> result in BSOD. OTOH they all work with next-20081128 (modulo hangs with
> fc10 ones when "radeon: no need for this anymore" change is not reverted).
>
> [ BTW xorg-x11-drv-ati-6.9.0-62.fc10.i386 still causes hangs when used with
> non-Fedora kernels and Fedora/kms kernel still has performance problems ]
>
> IOW there are a lot of compatibility issues in recent drm/radeon changes.
>
> Dave, could you please start looking into these problems? I'm sure that we
> all want recent drm changes + kms in 2.6.29 but given tight schedule and the
> way things are looking right now I'm quite sceptical...
>
> [1] http://lkml.org/lkml/2008/12/13/76
> [2] http://lkml.org/lkml/2008/12/13/77
>

Bart,

please file bugs in RH bugzilla for Fedora issues. Fedora is shipping
drivers that aren't upstream, and I'm attempting to resolve the issues
as they arise. However not having a bug to track stuff in means it just
goes far enough out of my inbox that I forget about it.

The revert isn't a fix for -ati, and I haven't seen any reports of
performance problems with profiles attached in my bugzilla.

I'm booting drm-next on more various radeon hw today to see what I can
reproduce, most of the kms changes for 2.6.29 are nothing to do with
radeon at all, we are only upstreaming KMS for Intel hw, so I'm not sure
what the sceptical bit is about. Its much more likely this is
multi-master changes before KMS that are interacting badly.


Dave.


> Thanks,
> Bart