2.6.28-rcX in pretty bad shape on parisc

2.6.28-rcX in pretty bad shape on parisc

[Helge Deller]

Hello PA hackers,

I've tried various -rc candidates in the last few weeks, and sadly the 
parisc kernel is in pretty bad shape.

At the beginning I started to get problems only when I had USB 
keyboard/mouse attached to the PA machine. This lead to bugzilla 
http://bugzilla.kernel.org/show_bug.cgi?id=11913

Now, with -rc4 and -rc5 things got even worse.

Crashes happen often just directly at the beginning.
I'm sure it's not USB related any more, and I assume we have some 
strange mm-problem somewhere.
The kernel crashes at various places, and mostly a null-pointer is involved.

Right now I'm clueless...

Helge

PS: I'm happy that I just recently bought this one: 
http://www.gembird.cn/main.asp?mode=item&N=5915
------------

Here ist just one of the latest crashes (c3k, UP, CONFIG_SMP not set, 
2.6.28-rc5):
.....
SuperIO: ACPI at 0x7e0
SuperIO: USB regulator enabled
PDC Stable Storage facility v0.30
Backtrace:
  [<1018b6a4>] __kmalloc+0xa4/0xec
  [<101718f4>] kstrdup+0x38/0x6c
  [<101d9090>] sysfs_new_dirent+0x54/0xf4
  [<101da0dc>] sysfs_do_create_link+0xcc/0x19c
  [<106cd644>] pdc_stable_init+0x1cc/0x2b4
  [<1010d998>] do_one_initcall+0x70/0x190
  [<106b9cf8>] do_initcalls+0x30/0x4c
  [<106b9df8>] kernel_init+0x64/0xac
  [<10113c5c>] ret_from_kernel_thread+0x1c/0x24


Kernel Fault: Code=26 regs=8f820500 (Addr=00000000)

      YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
PSW: 00000000000001001111111000001110 Not tainted
r00-03  0004fe0e 00000000 1018b18c 8ed92000
r04-07  8f8068ec 8f8020c0 8f806800 ffffffff
r08-11  8f800180 8f8020e4 000000d0 1066aa60
r12-15  00000000 ffffffff 00000000 f0400004
r16-19  f0000884 f000017c f0000174 00000000
r20-23  00000000 00000000 8ed9201c 00000001
r24-27  00000000 00000000 00002000 10607260
r28-31  00000000 00000000 8f820500 1018ae38
sr00-03  00000000 00000000 00000000 00000000
sr04-07  00000000 00000000 00000000 00000000

IASQ: 00000000 00000000 IAOQ: 1018b1b0 1018b1b4
  IIR: 0e931280    ISR: 00000000  IOR: 00000000
  CPU:        0   CR30: 8f820000 CR31: ffffffff
  ORIG_R28: 8f80f888
  IAOQ[0]: cache_alloc_refill+0x10c/0x208
  IAOQ[1]: cache_alloc_refill+0x110/0x208
  RP(r2): cache_alloc_refill+0xe8/0x208
Backtrace:
  [<1018b6a4>] __kmalloc+0xa4/0xec
  [<101718f4>] kstrdup+0x38/0x6c
  [<101d9090>] sysfs_new_dirent+0x54/0xf4
  [<101da0dc>] sysfs_do_create_link+0xcc/0x19c
  [<106cd644>] pdc_stable_init+0x1cc/0x2b4
  [<1010d998>] do_one_initcall+0x70/0x190
  [<106b9cf8>] do_initcalls+0x30/0x4c
  [<106b9df8>] kernel_init+0x64/0xac
  [<10113c5c>] ret_from_kernel_thread+0x1c/0x24

Kernel panic - not syncing: Kernel Fault

Re: 2.6.28-rcX in pretty bad shape on parisc

[Thibaut VARENE]

On Tue, Nov 18, 2008 at 9:04 PM, Helge Deller <deller@gmx.de> wrote:

> Here ist just one of the latest crashes (c3k, UP, CONFIG_SMP not set,
> 2.6.28-rc5):
> .....
> SuperIO: ACPI at 0x7e0
> SuperIO: USB regulator enabled
> PDC Stable Storage facility v0.30
> Backtrace:
>  [<1018b6a4>] __kmalloc+0xa4/0xec
>  [<101718f4>] kstrdup+0x38/0x6c
>  [<101d9090>] sysfs_new_dirent+0x54/0xf4
>  [<101da0dc>] sysfs_do_create_link+0xcc/0x19c
>  [<106cd644>] pdc_stable_init+0x1cc/0x2b4

Wild guess since my baby's into this mess: somebody fucked
up^W^Wmodified some code in sysfs and didn't care enough about the
consequences.

Last time this code was touched it was Greg KH updating it for sysfs
changes, and the backtrace seems to point in that area again, hence
the guess...

HTH

T-Bone

-- 
Thibaut VARENE
http://www.parisc-linux.org/~varenet/

Re: 2.6.28-rcX in pretty bad shape on parisc

[James Bottomley]

On Tue, 2008-11-18 at 21:04 +0100, Helge Deller wrote:
> I've tried various -rc candidates in the last few weeks, and sadly the 
> parisc kernel is in pretty bad shape.
> 
> At the beginning I started to get problems only when I had USB 
> keyboard/mouse attached to the PA machine. This lead to bugzilla 
> http://bugzilla.kernel.org/show_bug.cgi?id=11913
> 
> Now, with -rc4 and -rc5 things got even worse.
> 
> Crashes happen often just directly at the beginning.
> I'm sure it's not USB related any more, and I assume we have some 
> strange mm-problem somewhere.

I'd be really dubious about that.  Our pa8900 ... the most mm unstable
system we have ... is running -rc5 just fine.  The only warning before
boot is the usual SMP one.

Linux ion 2.6.28-rc5 #20 SMP Tue Nov 18 18:16:35 PST 2008 parisc64

Why don't we compare configs?  This is mine for ion:

http://parisc-linux.org/~jejb/config-2.6.28-rc5-ion

I suspect we have some nasty interaction in the device driver subsystem
(ion, the pa8900, isn't running either USB or PDC stable).

James

Re: 2.6.28-rcX in pretty bad shape on parisc

[Domenico Andreoli]

On Wed, Nov 19, 2008 at 11:31:42AM +0900, James Bottomley wrote:
> On Tue, 2008-11-18 at 21:04 +0100, Helge Deller wrote:
> > I've tried various -rc candidates in the last few weeks, and sadly the 
> > parisc kernel is in pretty bad shape.
> > 
> > At the beginning I started to get problems only when I had USB 
> > keyboard/mouse attached to the PA machine. This lead to bugzilla 
> > http://bugzilla.kernel.org/show_bug.cgi?id=11913
> > 
> > Now, with -rc4 and -rc5 things got even worse.
> > 
> > Crashes happen often just directly at the beginning.
> > I'm sure it's not USB related any more, and I assume we have some 
> > strange mm-problem somewhere.
> 
> I'd be really dubious about that.  Our pa8900 ... the most mm unstable
> system we have ... is running -rc5 just fine.  The only warning before
> boot is the usual SMP one.

my j5600 is also running fine

> Linux ion 2.6.28-rc5 #20 SMP Tue Nov 18 18:16:35 PST 2008 parisc64

parisc64 SMP? have you all the cpu online?

> Why don't we compare configs?  This is mine for ion:
> 
> http://parisc-linux.org/~jejb/config-2.6.28-rc5-ion

https://mnl.crema.unimi.it/~cavok/config-2.6.28-rc5

ciao,
Domenico

-----[ Domenico Andreoli, aka cavok
 --[ http://www.dandreoli.com/gpgkey.asc
   ---[ 3A0F 2F80 F79C 678A 8936  4FEE 0677 9033 A20E BC50

Re: 2.6.28-rcX in pretty bad shape on parisc

[James Bottomley]

On Wed, 2008-11-19 at 10:13 +0100, Domenico Andreoli wrote:
> On Wed, Nov 19, 2008 at 11:31:42AM +0900, James Bottomley wrote:
> > On Tue, 2008-11-18 at 21:04 +0100, Helge Deller wrote:
> > > I've tried various -rc candidates in the last few weeks, and sadly the 
> > > parisc kernel is in pretty bad shape.
> > > 
> > > At the beginning I started to get problems only when I had USB 
> > > keyboard/mouse attached to the PA machine. This lead to bugzilla 
> > > http://bugzilla.kernel.org/show_bug.cgi?id=11913
> > > 
> > > Now, with -rc4 and -rc5 things got even worse.
> > > 
> > > Crashes happen often just directly at the beginning.
> > > I'm sure it's not USB related any more, and I assume we have some 
> > > strange mm-problem somewhere.
> > 
> > I'd be really dubious about that.  Our pa8900 ... the most mm unstable
> > system we have ... is running -rc5 just fine.  The only warning before
> > boot is the usual SMP one.
> 
> my j5600 is also running fine
> 
> > Linux ion 2.6.28-rc5 #20 SMP Tue Nov 18 18:16:35 PST 2008 parisc64
> 
> parisc64 SMP? have you all the cpu online?

Yes, all four (two sockets, two cores).

James

Re: 2.6.28-rcX in pretty bad shape on parisc

[John David Anglin]

> > > I'd be really dubious about that.  Our pa8900 ... the most mm unstable
> > > system we have ... is running -rc5 just fine.  The only warning before
> > > boot is the usual SMP one.
> > 
> > my j5600 is also running fine
> > 
> > > Linux ion 2.6.28-rc5 #20 SMP Tue Nov 18 18:16:35 PST 2008 parisc64
> > 
> > parisc64 SMP? have you all the cpu online?
> 
> Yes, all four (two sockets, two cores).

I haven't tried 2.6.28-rc5 but I have tried Kyle's last parisc tree.
While it boots on SMP PA8800 (Mako), it can't do a full GCC build
without a SEGV or some kind of file system issue.  There's an
occasional unexpected SEGV with 2.6.22.19, but otherwise it is stable.
It can successfully build GCC at -j4 most of the time.

Dave
-- 
J. David Anglin                                  dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)

Re: 2.6.28-rcX in pretty bad shape on parisc

[Helge Deller]

Thibaut VARENE wrote:
> On Tue, Nov 18, 2008 at 9:04 PM, Helge Deller <deller@gmx.de> wrote:
> 
>> Here ist just one of the latest crashes (c3k, UP, CONFIG_SMP not set,
>> 2.6.28-rc5):
>> .....
>> SuperIO: ACPI at 0x7e0
>> SuperIO: USB regulator enabled
>> PDC Stable Storage facility v0.30
>> Backtrace:
>>  [<1018b6a4>] __kmalloc+0xa4/0xec
>>  [<101718f4>] kstrdup+0x38/0x6c
>>  [<101d9090>] sysfs_new_dirent+0x54/0xf4
>>  [<101da0dc>] sysfs_do_create_link+0xcc/0x19c
>>  [<106cd644>] pdc_stable_init+0x1cc/0x2b4
> 
> Wild guess since my baby's into this mess: somebody fucked
> up^W^Wmodified some code in sysfs and didn't care enough about the
> consequences.

I'm not sure it's sysfs either.
This crash happens in sysfs, but other in memory, locking, ...
It's just random where and when it crashes.

Helge

Re: 2.6.28-rcX in pretty bad shape on parisc

[Helge Deller]

James Bottomley wrote:
>> Why don't we compare configs?  This is mine for ion:
>> http://parisc-linux.org/~jejb/config-2.6.28-rc5-ion

 > Domenico Andreoli wrote:
> https://mnl.crema.unimi.it/~cavok/config-2.6.28-rc5

Helge:
and here is mine (32bit(!), usually works on C3000, B160L, 715/64 and 
Tadpole PARISC laptop - similiar to B160L):
http://gsyprf10.external.hp.com/~deller/config.2.6.28-rc5

Re: 2.6.28-rcX in pretty bad shape on parisc

[Helge Deller]

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

Helge Deller wrote:
> James Bottomley wrote:
>>> Why don't we compare configs?  This is mine for ion:
>>> http://parisc-linux.org/~jejb/config-2.6.28-rc5-ion
> 
>  > Domenico Andreoli wrote:
>> https://mnl.crema.unimi.it/~cavok/config-2.6.28-rc5
> 
> Helge:
> and here is mine (32bit(!), usually works on C3000, B160L, 715/64 and 
> Tadpole PARISC laptop - similiar to B160L):
> http://gsyprf10.external.hp.com/~deller/config.2.6.28-rc5

James,
I tried your config on my c3k.
Only modifications I did are to enable built-in network and scsi, so 
that I'm able to tftpboot into the new kernel.
.config and config-diff-file are attached.

Here is what I got:
Freeing unused kernel memory:
Badness at kernel/smp.c:333...(well known)...
220k freed
eth0: Setting full-duplex based on MII#1 link partner capability of 45e1.
Backtrace:
  [<000000004023c274>] proc_flush_task+0x4/0x3d8

Bad Address (null pointer deref?): Code=6 regs=00000000bf83cb58 
(Addr=0000045000000000)

      YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
PSW: 00001000000001000000011100001111 Tainted: G        W
r00-03  000000000804070f 0000000040492000 0000000040253bef 0000000000000000
r04-07  0000000040003000 0000000040670964 0000000000002168 000000000000085a
r08-11  000000004029d2dc 000000004029dac0 00000000402a060c 00000000400011a0
r12-15  0000000040000f00 00000000000000f0 00000000fb2cfa4c 000000004029db68
r16-19  000000004029d1ec 000000004029d66a 00000000406a008c 000000004025e6e0
r20-23  0000000000000000 0000045000000000 00000000ffffffff 0000000000000012
r24-27  0000000040003000 0000000000000000 0000000040001110 0000000000000002
r28-31  0000000040492000 0000000040001110 00000000fb2cfe40 0000000040253c27
sr00-03  0000000000000800 0000000000000800 0000000000000000 0000000000000800
sr04-07  0000000000000800 0000000000000800 0000000000000800 0000000000000800

IASQ: 0000000000000450 0000000000000450 IAOQ: 0000045000000000 
0000045000000004
  IIR: 43ffff80    ISR: 0000000000000800  IOR: 0000000040673375
  CPU:        0   CR30: 00000000bf854000 CR31: 0000000011111111
  ORIG_R28: fffffffffffff000
  IAOQ[0]: 0x45000000000
  IAOQ[1]: 0x45000000004
  RP(r2): ext3_free_data+0x194/0x1b8
Backtrace: 
                                        [<000000004023c274>] 
proc_flush_task+0x4/0x3d8

Kernel panic - not syncing: Bad Address (null pointer deref?)

----

Another boot showed:
Bad Address (null pointer deref?): Code=6 regs=00000000bf83cb58 
(Addr=0000045000000000)

      YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
PSW: 00001000000001000000011100001111 Tainted: G        W
r00-03  000000000804070f 0000000040490000 0000000040253bef 0000000000000000
r04-07  0000000040003000 0000000040670964 0000000000002168 000000000000085a
r08-11  000000004029d2dc 000000004029dac0 00000000402a060c 00000000400011a0
r12-15  0000000040000f00 00000000000000f0 00000000fb3e2a4c 000000004029db68
r16-19  000000004029d1ec 000000004029d66a 00000000406a008c 000000004025e6e0
r20-23  0000000000000000 0000045000000000 00000000ffffffff 0000000000000012
r24-27  0000000040003000 0000000000000000 0000000040001110 0000000000000002
r28-31  0000000040490000 0000000040001110 00000000fb3e2e40 0000000040253c27
sr00-03  0000000000000800 0000000000000800 0000000000000000 0000000000000800
sr04-07  0000000000000800 0000000000000800 0000000000000800 0000000000000800

IASQ: 0000000000000450 0000000000000450 IAOQ: 0000045000000000 
0000045000000004
  IIR: 43ffff80    ISR: 0000000000000800  IOR: 0000000040673375
  CPU:        0   CR30: 00000000bf854000 CR31: 00000000da1345e2
  ORIG_R28: fffffffffffff000
  IAOQ[0]: 0x45000000000
  IAOQ[1]: 0x45000000004
  RP(r2): ext3_direct_IO+0x224/0x298
Backtrace:
  [<000000004023c274>] proc_flush_task+0x4/0x3d8

---

After that I turned off fastboot on my c3k and let PDC check the memory.
PDC reported no problems. All 2GB are OK.

Helge

[-- Attachment #2: config.2.6.28-rc5 --]
[-- Type: text/plain, Size: 39421 bytes --]

#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.28-rc5
# Tue Nov 18 16:34:18 2008
#
CONFIG_PARISC=y
CONFIG_MMU=y
CONFIG_STACK_GROWSUP=y
CONFIG_RWSEM_GENERIC_SPINLOCK=y
# CONFIG_ARCH_HAS_ILOG2_U32 is not set
# CONFIG_ARCH_HAS_ILOG2_U64 is not set
CONFIG_GENERIC_FIND_NEXT_BIT=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_GENERIC_TIME=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_IRQ_PER_CPU=y
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"

#
# General setup
#
CONFIG_EXPERIMENTAL=y
CONFIG_BROKEN_ON_SMP=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_LOCALVERSION=""
# CONFIG_LOCALVERSION_AUTO is not set
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
CONFIG_BSD_PROCESS_ACCT=y
# CONFIG_BSD_PROCESS_ACCT_V3 is not set
# CONFIG_TASKSTATS is not set
# CONFIG_AUDIT is not set
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_LOG_BUF_SHIFT=16
# CONFIG_CGROUPS is not set
# CONFIG_GROUP_SCHED is not set
CONFIG_SYSFS_DEPRECATED=y
CONFIG_SYSFS_DEPRECATED_V2=y
# CONFIG_RELAY is not set
CONFIG_NAMESPACES=y
# CONFIG_UTS_NS is not set
# CONFIG_IPC_NS is not set
# 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=y
CONFIG_SYSCTL=y
# CONFIG_EMBEDDED is not set
CONFIG_SYSCTL_SYSCALL=y
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_COMPAT_BRK=y
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_PCI_QUIRKS=y
CONFIG_SLAB=y
# CONFIG_SLUB is not set
# CONFIG_SLOB is not set
CONFIG_PROFILING=y
# CONFIG_MARKERS is not set
CONFIG_OPROFILE=m
CONFIG_HAVE_OPROFILE=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=y
# CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not set
CONFIG_KMOD=y
CONFIG_BLOCK=y
# CONFIG_LBD is not set
# CONFIG_BLK_DEV_IO_TRACE is not set
# CONFIG_LSF is not set
# CONFIG_BLK_DEV_BSG is not set
# CONFIG_BLK_DEV_INTEGRITY is not set

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

#
# Processor type and features
#
# CONFIG_PA7000 is not set
CONFIG_PA7100LC=y
# CONFIG_PA7200 is not set
# CONFIG_PA7300LC is not set
# CONFIG_PA8X00 is not set
CONFIG_PA11=y
CONFIG_PARISC_PAGE_SIZE_4KB=y
# CONFIG_PARISC_PAGE_SIZE_16KB is not set
# CONFIG_PARISC_PAGE_SIZE_64KB is not set
# CONFIG_SMP is not set
CONFIG_ARCH_FLATMEM_ENABLE=y
# CONFIG_PREEMPT_NONE is not set
CONFIG_PREEMPT_VOLUNTARY=y
# CONFIG_PREEMPT 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 is not set
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
# CONFIG_DISCONTIGMEM_MANUAL is not set
# CONFIG_SPARSEMEM_MANUAL is not set
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
CONFIG_PAGEFLAGS_EXTENDED=y
CONFIG_SPLIT_PTLOCK_CPUS=4096
# CONFIG_RESOURCES_64BIT is not set
# CONFIG_PHYS_ADDR_T_64BIT is not set
CONFIG_ZONE_DMA_FLAG=0
CONFIG_VIRT_TO_BUS=y
CONFIG_UNEVICTABLE_LRU=y
CONFIG_HPUX=y

#
# Bus options (PCI, PCMCIA, EISA, GSC, ISA)
#
CONFIG_GSC=y
# CONFIG_HPPB is not set
CONFIG_IOMMU_CCIO=y
CONFIG_GSC_LASI=y
CONFIG_GSC_WAX=y
CONFIG_EISA=y
CONFIG_EISA_NAMES=y
# CONFIG_ISA is not set
CONFIG_PCI=y
# CONFIG_ARCH_SUPPORTS_MSI is not set
# CONFIG_PCI_LEGACY is not set
# CONFIG_PCI_DEBUG is not set
CONFIG_GSC_DINO=y
CONFIG_PCI_LBA=y
CONFIG_IOSAPIC=y
CONFIG_IOMMU_SBA=y
CONFIG_IOMMU_HELPER=y
CONFIG_PCCARD=y
# CONFIG_PCMCIA_DEBUG is not set
CONFIG_PCMCIA=y
CONFIG_PCMCIA_LOAD_CIS=y
CONFIG_PCMCIA_IOCTL=y
CONFIG_CARDBUS=y

#
# PC-card bridges
#
CONFIG_YENTA=y
CONFIG_YENTA_O2=y
CONFIG_YENTA_RICOH=y
CONFIG_YENTA_TI=y
CONFIG_YENTA_ENE_TUNE=y
CONFIG_YENTA_TOSHIBA=y
CONFIG_PD6729=y
CONFIG_I82092=y
CONFIG_PCCARD_NONSTATIC=y
# CONFIG_HOTPLUG_PCI is not set

#
# PA-RISC specific drivers
#
CONFIG_SUPERIO=y
CONFIG_CHASSIS_LCD_LED=y
# CONFIG_PDC_CHASSIS is not set
# CONFIG_PDC_CHASSIS_WARN is not set
CONFIG_PDC_STABLE=y

#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
# CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS is not set
# CONFIG_HAVE_AOUT is not set
CONFIG_BINFMT_SOM=y
CONFIG_BINFMT_MISC=m
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_UNIX=y
CONFIG_XFRM=y
CONFIG_XFRM_USER=m
# CONFIG_XFRM_SUB_POLICY is not set
# CONFIG_XFRM_MIGRATE is not set
# CONFIG_XFRM_STATISTICS is not set
CONFIG_NET_KEY=m
# CONFIG_NET_KEY_MIGRATE is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
CONFIG_IP_FIB_HASH=y
CONFIG_IP_PNP=y
CONFIG_IP_PNP_DHCP=y
CONFIG_IP_PNP_BOOTP=y
# CONFIG_IP_PNP_RARP 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=m
CONFIG_INET_ESP=m
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_XFRM_TUNNEL is not set
# CONFIG_INET_TUNNEL is not set
# CONFIG_INET_XFRM_MODE_TRANSPORT is not set
# CONFIG_INET_XFRM_MODE_TUNNEL is not set
# CONFIG_INET_XFRM_MODE_BEET is not set
# CONFIG_INET_LRO is not set
CONFIG_INET_DIAG=m
CONFIG_INET_TCP_DIAG=m
# 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 is not set
# CONFIG_NETWORK_SECMARK is not set
# CONFIG_NETFILTER is not set
# CONFIG_IP_DCCP is not set
# CONFIG_IP_SCTP is not set
# CONFIG_TIPC is not set
# CONFIG_ATM is not set
# CONFIG_BRIDGE is not set
# CONFIG_NET_DSA is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
CONFIG_LLC=m
CONFIG_LLC2=m
# 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 is not set

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_HAMRADIO is not set
# CONFIG_CAN is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
# CONFIG_AF_RXRPC is not set
# CONFIG_PHONET is not set
# CONFIG_WIRELESS is not set
CONFIG_WIRELESS_EXT=y
CONFIG_IEEE80211=m
CONFIG_IEEE80211_CRYPT_WEP=m
# CONFIG_RFKILL is not set
# CONFIG_NET_9P is not set

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
# CONFIG_STANDALONE is not set
# CONFIG_PREVENT_FIRMWARE_BUILD is not set
CONFIG_FW_LOADER=y
CONFIG_FIRMWARE_IN_KERNEL=y
CONFIG_EXTRA_FIRMWARE=""
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_DEBUG_DEVRES is not set
# CONFIG_SYS_HYPERVISOR is not set
# CONFIG_CONNECTOR is not set
# CONFIG_MTD is not set
CONFIG_PARPORT=y
CONFIG_PARPORT_PC=m
# CONFIG_PARPORT_SERIAL is not set
# CONFIG_PARPORT_PC_FIFO is not set
# CONFIG_PARPORT_PC_SUPERIO is not set
CONFIG_PARPORT_PC_PCMCIA=m
CONFIG_PARPORT_GSC=y
# CONFIG_PARPORT_AX88796 is not set
CONFIG_PARPORT_1284=y
CONFIG_PARPORT_NOT_PC=y
CONFIG_BLK_DEV=y
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=y
CONFIG_BLK_DEV_CRYPTOLOOP=y
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_SX8 is not set
# CONFIG_BLK_DEV_UB is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=6144
# CONFIG_BLK_DEV_XIP is not set
# CONFIG_CDROM_PKTCDVD is not set
# CONFIG_ATA_OVER_ETH is not set
# CONFIG_BLK_DEV_HD is not set
CONFIG_MISC_DEVICES=y
# CONFIG_PHANTOM is not set
# CONFIG_EEPROM_93CX6 is not set
# CONFIG_SGI_IOC4 is not set
# CONFIG_TIFM_CORE is not set
# CONFIG_ENCLOSURE_SERVICES is not set
# CONFIG_HP_ILO is not set
# CONFIG_C2PORT is not set
CONFIG_HAVE_IDE=y
CONFIG_IDE=y

#
# Please see Documentation/ide/ide.txt for help/info on IDE drives
#
CONFIG_IDE_ATAPI=y
# CONFIG_BLK_DEV_IDE_SATA is not set
CONFIG_IDE_GD=y
CONFIG_IDE_GD_ATA=y
# CONFIG_IDE_GD_ATAPI is not set
CONFIG_BLK_DEV_IDECS=y
# CONFIG_BLK_DEV_DELKIN is not set
CONFIG_BLK_DEV_IDECD=y
CONFIG_BLK_DEV_IDECD_VERBOSE_ERRORS=y
# CONFIG_BLK_DEV_IDETAPE is not set
CONFIG_BLK_DEV_IDESCSI=y
# CONFIG_IDE_TASK_IOCTL is not set
CONFIG_IDE_PROC_FS=y

#
# IDE chipset support/bugfixes
#
# CONFIG_BLK_DEV_PLATFORM is not set
CONFIG_BLK_DEV_IDEDMA_SFF=y

#
# PCI IDE chipsets support
#
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_PCIBUS_ORDER=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_BLK_DEV_GENERIC=y
# CONFIG_BLK_DEV_OPTI621 is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_JMICRON is not set
# CONFIG_BLK_DEV_SC1200 is not set
# CONFIG_BLK_DEV_PIIX is not set
# CONFIG_BLK_DEV_IT8213 is not set
# CONFIG_BLK_DEV_IT821X is not set
CONFIG_BLK_DEV_NS87415=y
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_VIA82CXXX is not set
# CONFIG_BLK_DEV_TC86C001 is not set
CONFIG_BLK_DEV_IDEDMA=y

#
# SCSI device support
#
# CONFIG_RAID_ATTRS is not set
CONFIG_SCSI=y
CONFIG_SCSI_DMA=y
# CONFIG_SCSI_TGT is not set
# CONFIG_SCSI_NETLINK is not set
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 is not set
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 is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set
# CONFIG_SCSI_SCAN_ASYNC is not set
CONFIG_SCSI_WAIT_SCAN=m

#
# SCSI Transports
#
CONFIG_SCSI_SPI_ATTRS=y
# CONFIG_SCSI_FC_ATTRS is not set
# CONFIG_SCSI_ISCSI_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_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AHA1740 is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_AIC94XX is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_ARCMSR is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_MEGARAID_SAS is not set
# CONFIG_SCSI_HPTIOP is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_PPA is not set
# CONFIG_SCSI_IMM is not set
# CONFIG_SCSI_MVSAS is not set
CONFIG_SCSI_LASI700=y
CONFIG_53C700_LE_ON_BE=y
# CONFIG_SCSI_STEX is not set
CONFIG_SCSI_SYM53C8XX_2=y
CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=1
CONFIG_SCSI_SYM53C8XX_DEFAULT_TAGS=16
CONFIG_SCSI_SYM53C8XX_MAX_TAGS=64
CONFIG_SCSI_SYM53C8XX_MMIO=y
# CONFIG_SCSI_IPR is not set
CONFIG_SCSI_ZALON=y
CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS=8
CONFIG_SCSI_NCR53C8XX_MAX_TAGS=32
CONFIG_SCSI_NCR53C8XX_SYNC=20
# CONFIG_SCSI_QLOGIC_1280 is not set
# CONFIG_SCSI_QLA_FC is not set
# CONFIG_SCSI_QLA_ISCSI is not set
# CONFIG_SCSI_LPFC is not set
# CONFIG_SCSI_SIM710 is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set
# CONFIG_SCSI_SRP is not set
# CONFIG_SCSI_LOWLEVEL_PCMCIA is not set
CONFIG_SCSI_DH=y
# CONFIG_SCSI_DH_RDAC is not set
# CONFIG_SCSI_DH_HP_SW is not set
# CONFIG_SCSI_DH_EMC is not set
# CONFIG_SCSI_DH_ALUA is not set
CONFIG_ATA=y
# CONFIG_ATA_NONSTANDARD is not set
CONFIG_SATA_PMP=y
# CONFIG_SATA_AHCI is not set
# CONFIG_SATA_SIL24 is not set
CONFIG_ATA_SFF=y
# CONFIG_SATA_SVW is not set
# CONFIG_ATA_PIIX is not set
# CONFIG_SATA_MV is not set
# CONFIG_SATA_NV is not set
# CONFIG_PDC_ADMA is not set
# CONFIG_SATA_QSTOR is not set
# CONFIG_SATA_PROMISE is not set
# CONFIG_SATA_SX4 is not set
# CONFIG_SATA_SIL is not set
# CONFIG_SATA_SIS is not set
# CONFIG_SATA_ULI is not set
# CONFIG_SATA_VIA is not set
# CONFIG_SATA_VITESSE is not set
# CONFIG_SATA_INIC162X is not set
# CONFIG_PATA_ALI is not set
# CONFIG_PATA_AMD is not set
# CONFIG_PATA_ARTOP is not set
# CONFIG_PATA_ATIIXP is not set
# CONFIG_PATA_CMD640_PCI is not set
# CONFIG_PATA_CMD64X is not set
# CONFIG_PATA_CS5520 is not set
# CONFIG_PATA_CS5530 is not set
# CONFIG_PATA_CYPRESS is not set
# CONFIG_PATA_EFAR is not set
# CONFIG_ATA_GENERIC is not set
# CONFIG_PATA_HPT366 is not set
# CONFIG_PATA_HPT37X is not set
# CONFIG_PATA_HPT3X2N is not set
# CONFIG_PATA_HPT3X3 is not set
# CONFIG_PATA_IT821X is not set
# CONFIG_PATA_IT8213 is not set
# CONFIG_PATA_JMICRON is not set
# CONFIG_PATA_TRIFLEX is not set
# CONFIG_PATA_MARVELL is not set
# CONFIG_PATA_MPIIX is not set
# CONFIG_PATA_OLDPIIX is not set
# CONFIG_PATA_NETCELL is not set
# CONFIG_PATA_NINJA32 is not set
# CONFIG_PATA_NS87410 is not set
# CONFIG_PATA_NS87415 is not set
# CONFIG_PATA_OPTI is not set
# CONFIG_PATA_OPTIDMA is not set
# CONFIG_PATA_PCMCIA is not set
# CONFIG_PATA_PDC_OLD is not set
# CONFIG_PATA_RADISYS is not set
# CONFIG_PATA_RZ1000 is not set
# CONFIG_PATA_SC1200 is not set
# CONFIG_PATA_SERVERWORKS is not set
# CONFIG_PATA_PDC2027X is not set
# CONFIG_PATA_SIL680 is not set
# CONFIG_PATA_SIS is not set
# CONFIG_PATA_VIA is not set
# CONFIG_PATA_WINBOND is not set
# CONFIG_PATA_SCH is not set
CONFIG_MD=y
CONFIG_BLK_DEV_MD=y
# CONFIG_MD_AUTODETECT is not set
CONFIG_MD_LINEAR=y
CONFIG_MD_RAID0=y
CONFIG_MD_RAID1=y
CONFIG_MD_RAID10=y
CONFIG_MD_RAID456=y
CONFIG_MD_RAID5_RESHAPE=y
# CONFIG_MD_MULTIPATH is not set
# CONFIG_MD_FAULTY is not set
CONFIG_BLK_DEV_DM=y
# CONFIG_DM_DEBUG is not set
# CONFIG_DM_CRYPT is not set
# CONFIG_DM_SNAPSHOT is not set
# CONFIG_DM_MIRROR is not set
# CONFIG_DM_ZERO is not set
# CONFIG_DM_MULTIPATH is not set
# CONFIG_DM_DELAY is not set
# CONFIG_DM_UEVENT is not set
# CONFIG_FUSION is not set

#
# IEEE 1394 (FireWire) support
#

#
# Enable only one of the two stacks, unless you know what you are doing
#
# CONFIG_FIREWIRE is not set
# CONFIG_IEEE1394 is not set
# CONFIG_I2O is not set
CONFIG_NETDEVICES=y
CONFIG_DUMMY=m
CONFIG_BONDING=m
# CONFIG_MACVLAN is not set
# CONFIG_EQUALIZER is not set
CONFIG_TUN=m
# CONFIG_VETH is not set
# CONFIG_ARCNET is not set
# CONFIG_PHYLIB is not set
CONFIG_NET_ETHERNET=y
CONFIG_MII=m
CONFIG_LASI_82596=y
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_CASSINI is not set
# CONFIG_NET_VENDOR_3COM is not set
# CONFIG_NET_VENDOR_SMC is not set
CONFIG_NET_TULIP=y
# CONFIG_DE2104X is not set
CONFIG_TULIP=y
# CONFIG_TULIP_MWI is not set
# CONFIG_TULIP_MMIO is not set
# CONFIG_TULIP_NAPI is not set
# CONFIG_DE4X5 is not set
# CONFIG_WINBOND_840 is not set
# CONFIG_DM9102 is not set
# CONFIG_ULI526X is not set
# CONFIG_PCMCIA_XIRCOM is not set
# CONFIG_DEPCA is not set
# CONFIG_HP100 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_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_AC3200 is not set
# CONFIG_B44 is not set
# CONFIG_FORCEDETH is not set
# CONFIG_CS89x0 is not set
# CONFIG_EEPRO100 is not set
# CONFIG_E100 is not set
# CONFIG_LNE390 is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
# CONFIG_NE2K_PCI is not set
# CONFIG_NE3210 is not set
# CONFIG_ES3210 is not set
# CONFIG_8139CP is not set
# CONFIG_8139TOO is not set
# CONFIG_R6040 is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE is not set
# CONFIG_SC92031 is not set
# CONFIG_NET_POCKET is not set
# CONFIG_ATL2 is not set
# CONFIG_NETDEV_1000 is not set
# CONFIG_NETDEV_10000 is not set
# CONFIG_TR is not set

#
# Wireless LAN
#
# CONFIG_WLAN_PRE80211 is not set
CONFIG_WLAN_80211=y
# CONFIG_PCMCIA_RAYCS is not set
# CONFIG_IPW2100 is not set
# CONFIG_IPW2200 is not set
# CONFIG_LIBERTAS is not set
CONFIG_HERMES=m
# CONFIG_PLX_HERMES is not set
# CONFIG_TMD_HERMES is not set
# CONFIG_NORTEL_HERMES is not set
# CONFIG_PCI_HERMES is not set
CONFIG_PCMCIA_HERMES=m
# CONFIG_PCMCIA_SPECTRUM is not set
# CONFIG_ATMEL is not set
# CONFIG_AIRO_CS is not set
# CONFIG_PCMCIA_WL3501 is not set
# CONFIG_PRISM54 is not set
# CONFIG_USB_ZD1201 is not set
# CONFIG_USB_NET_RNDIS_WLAN is not set
# CONFIG_IWLWIFI_LEDS is not set
CONFIG_HOSTAP=m
CONFIG_HOSTAP_FIRMWARE=y
CONFIG_HOSTAP_FIRMWARE_NVRAM=y
# CONFIG_HOSTAP_PLX is not set
CONFIG_HOSTAP_PCI=m
CONFIG_HOSTAP_CS=m

#
# USB Network Adapters
#
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET is not set
CONFIG_NET_PCMCIA=y
# CONFIG_PCMCIA_3C589 is not set
# CONFIG_PCMCIA_3C574 is not set
# CONFIG_PCMCIA_FMVJ18X is not set
# CONFIG_PCMCIA_PCNET is not set
# CONFIG_PCMCIA_NMCLAN is not set
# CONFIG_PCMCIA_SMC91C92 is not set
# CONFIG_PCMCIA_XIRC2PS is not set
# CONFIG_PCMCIA_AXNET is not set
# CONFIG_WAN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PLIP is not set
CONFIG_PPP=m
# CONFIG_PPP_MULTILINK is not set
# CONFIG_PPP_FILTER is not set
CONFIG_PPP_ASYNC=m
CONFIG_PPP_SYNC_TTY=m
CONFIG_PPP_DEFLATE=m
CONFIG_PPP_BSDCOMP=m
# CONFIG_PPP_MPPE is not set
CONFIG_PPPOE=m
# CONFIG_PPPOL2TP is not set
# CONFIG_SLIP is not set
CONFIG_SLHC=m
# CONFIG_NET_FC is not set
# CONFIG_NETCONSOLE is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set
# CONFIG_ISDN is not set
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y
# CONFIG_INPUT_FF_MEMLESS is not set
CONFIG_INPUT_POLLDEV=y

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
CONFIG_KEYBOARD_ATKBD_HP_KEYCODES=y
# CONFIG_KEYBOARD_ATKBD_RDI_KEYCODES is not set
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_KEYBOARD_STOWAWAY is not set
# CONFIG_KEYBOARD_HIL_OLD is not set
CONFIG_KEYBOARD_HIL=m
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
CONFIG_MOUSE_PS2_ALPS=y
CONFIG_MOUSE_PS2_LOGIPS2PP=y
CONFIG_MOUSE_PS2_SYNAPTICS=y
CONFIG_MOUSE_PS2_LIFEBOOK=y
CONFIG_MOUSE_PS2_TRACKPOINT=y
# CONFIG_MOUSE_PS2_ELANTECH is not set
# CONFIG_MOUSE_PS2_TOUCHKIT is not set
CONFIG_MOUSE_SERIAL=y
# CONFIG_MOUSE_APPLETOUCH is not set
# CONFIG_MOUSE_BCM5974 is not set
# CONFIG_MOUSE_VSXXXAA is not set
CONFIG_MOUSE_HIL=m
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TABLET is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
CONFIG_INPUT_MISC=y
# CONFIG_INPUT_ATI_REMOTE is not set
# CONFIG_INPUT_ATI_REMOTE2 is not set
# CONFIG_INPUT_KEYSPAN_REMOTE is not set
# CONFIG_INPUT_POWERMATE is not set
# CONFIG_INPUT_YEALINK is not set
# CONFIG_INPUT_CM109 is not set
CONFIG_INPUT_UINPUT=m
CONFIG_HP_SDC_RTC=m

#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_SERPORT=y
# CONFIG_SERIO_PARKBD is not set
CONFIG_SERIO_GSCPS2=y
CONFIG_HP_SDC=m
CONFIG_HIL_MLC=m
# CONFIG_SERIO_PCIPS2 is not set
CONFIG_SERIO_LIBPS2=y
# CONFIG_SERIO_RAW is not set
# CONFIG_GAMEPORT is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_CONSOLE_TRANSLATIONS=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
CONFIG_VT_HW_CONSOLE_BINDING=y
CONFIG_DEVKMEM=y
# CONFIG_SERIAL_NONSTANDARD is not set
# CONFIG_NOZOMI is not set

#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_SERIAL_8250_GSC=y
CONFIG_SERIAL_8250_PCI=y
CONFIG_SERIAL_8250_CS=y
CONFIG_SERIAL_8250_NR_UARTS=17
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
CONFIG_SERIAL_8250_EXTENDED=y
CONFIG_SERIAL_8250_MANY_PORTS=y
CONFIG_SERIAL_8250_SHARE_IRQ=y
# CONFIG_SERIAL_8250_DETECT_IRQ is not set
# CONFIG_SERIAL_8250_RSA is not set

#
# Non-8250 serial port support
#
CONFIG_SERIAL_MUX=y
CONFIG_SERIAL_MUX_CONSOLE=y
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
# CONFIG_SERIAL_JSM is not set
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=64
CONFIG_PRINTER=m
# CONFIG_LP_CONSOLE is not set
CONFIG_PPDEV=m
# CONFIG_IPMI_HANDLER is not set
# CONFIG_HW_RANDOM is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set

#
# PCMCIA character devices
#
# CONFIG_SYNCLINK_CS is not set
# CONFIG_CARDMAN_4000 is not set
# CONFIG_CARDMAN_4040 is not set
# CONFIG_IPWIRELESS is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_TCG_TPM is not set
CONFIG_DEVPORT=y
# CONFIG_I2C is not set
# CONFIG_SPI is not set
# CONFIG_W1 is not set
CONFIG_POWER_SUPPLY=y
# CONFIG_POWER_SUPPLY_DEBUG is not set
# CONFIG_PDA_POWER is not set
# CONFIG_BATTERY_DS2760 is not set
# CONFIG_HWMON is not set
# CONFIG_THERMAL is not set
# CONFIG_THERMAL_HWMON is not set
# CONFIG_WATCHDOG is not set
CONFIG_SSB_POSSIBLE=y

#
# Sonics Silicon Backplane
#
# CONFIG_SSB is not set

#
# Multifunction device drivers
#
# CONFIG_MFD_CORE is not set
# CONFIG_MFD_SM501 is not set
# CONFIG_HTC_PASIC3 is not set
# CONFIG_MFD_TMIO is not set
# CONFIG_REGULATOR is not set

#
# Multimedia devices
#

#
# Multimedia core support
#
# CONFIG_VIDEO_DEV is not set
# CONFIG_DVB_CORE is not set
# CONFIG_VIDEO_MEDIA is not set

#
# Multimedia drivers
#
# CONFIG_DAB is not set

#
# Graphics support
#
# CONFIG_AGP is not set
# CONFIG_DRM is not set
# CONFIG_VGASTATE is not set
CONFIG_VIDEO_OUTPUT_CONTROL=y
CONFIG_FB=y
# CONFIG_FIRMWARE_EDID is not set
# CONFIG_FB_DDC is not set
# CONFIG_FB_BOOT_VESA_SUPPORT is not set
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
# CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set
# CONFIG_FB_SYS_FILLRECT is not set
# CONFIG_FB_SYS_COPYAREA is not set
# CONFIG_FB_SYS_IMAGEBLIT is not set
CONFIG_FB_FOREIGN_ENDIAN=y
CONFIG_FB_BOTH_ENDIAN=y
# CONFIG_FB_BIG_ENDIAN is not set
# CONFIG_FB_LITTLE_ENDIAN is not set
# CONFIG_FB_SYS_FOPS is not set
# CONFIG_FB_SVGALIB is not set
# CONFIG_FB_MACMODES is not set
# CONFIG_FB_BACKLIGHT is not set
CONFIG_FB_MODE_HELPERS=y
CONFIG_FB_TILEBLITTING=y

#
# Frame buffer hardware drivers
#
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
CONFIG_FB_STI=y
# CONFIG_FB_S1D13XXX is not set
# CONFIG_FB_NVIDIA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_S3 is not set
# CONFIG_FB_SAVAGE is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_VIA is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
CONFIG_FB_VOODOO1=m
# CONFIG_FB_VT8623 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_ARK is not set
# CONFIG_FB_PM3 is not set
# CONFIG_FB_CARMINE is not set
# CONFIG_FB_VIRTUAL is not set
# CONFIG_FB_METRONOME is not set
# CONFIG_FB_MB862XX is not set
# CONFIG_BACKLIGHT_LCD_SUPPORT is not set

#
# Display device support
#
# CONFIG_DISPLAY_SUPPORT is not set

#
# Console display driver support
#
CONFIG_DUMMY_CONSOLE=y
CONFIG_DUMMY_CONSOLE_COLUMNS=128
CONFIG_DUMMY_CONSOLE_ROWS=48
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
# CONFIG_FRAMEBUFFER_CONSOLE_ROTATION is not set
CONFIG_STI_CONSOLE=y
CONFIG_FONTS=y
# CONFIG_FONT_8x8 is not set
CONFIG_FONT_8x16=y
# CONFIG_FONT_6x11 is not set
# CONFIG_FONT_7x14 is not set
# CONFIG_FONT_PEARL_8x8 is not set
# CONFIG_FONT_ACORN_8x8 is not set
# CONFIG_FONT_MINI_4x6 is not set
# CONFIG_FONT_SUN8x16 is not set
# CONFIG_FONT_SUN12x22 is not set
# CONFIG_FONT_10x18 is not set
CONFIG_LOGO=y
# CONFIG_LOGO_LINUX_MONO is not set
# CONFIG_LOGO_LINUX_VGA16 is not set
# CONFIG_LOGO_LINUX_CLUT224 is not set
CONFIG_LOGO_PARISC_CLUT224=y
CONFIG_SOUND=m
CONFIG_SOUND_OSS_CORE=y
CONFIG_SND=m
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
CONFIG_SND_SEQUENCER=m
# CONFIG_SND_SEQ_DUMMY is not set
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
CONFIG_SND_PCM_OSS_PLUGINS=y
CONFIG_SND_SEQUENCER_OSS=y
CONFIG_SND_DYNAMIC_MINORS=y
CONFIG_SND_SUPPORT_OLD_API=y
CONFIG_SND_VERBOSE_PROCFS=y
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set
CONFIG_SND_VMASTER=y
CONFIG_SND_AC97_CODEC=m
CONFIG_SND_DRIVERS=y
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_VIRMIDI is not set
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_MTS64 is not set
# CONFIG_SND_SERIAL_U16550 is not set
# CONFIG_SND_MPU401 is not set
# CONFIG_SND_PORTMAN2X4 is not set
# CONFIG_SND_AC97_POWER_SAVE is not set
CONFIG_SND_PCI=y
CONFIG_SND_AD1889=m
# CONFIG_SND_ALS300 is not set
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_ATIIXP is not set
# CONFIG_SND_ATIIXP_MODEM is not set
# CONFIG_SND_AU8810 is not set
# CONFIG_SND_AU8820 is not set
# CONFIG_SND_AU8830 is not set
# CONFIG_SND_AW2 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_BT87X is not set
# CONFIG_SND_CA0106 is not set
# CONFIG_SND_CMIPCI is not set
# CONFIG_SND_OXYGEN is not set
# CONFIG_SND_CS4281 is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_DARLA20 is not set
# CONFIG_SND_GINA20 is not set
# CONFIG_SND_LAYLA20 is not set
# CONFIG_SND_DARLA24 is not set
# CONFIG_SND_GINA24 is not set
# CONFIG_SND_LAYLA24 is not set
# CONFIG_SND_MONA is not set
# CONFIG_SND_MIA is not set
# CONFIG_SND_ECHO3G is not set
# CONFIG_SND_INDIGO is not set
# CONFIG_SND_INDIGOIO is not set
# CONFIG_SND_INDIGODJ is not set
# CONFIG_SND_EMU10K1 is not set
# CONFIG_SND_EMU10K1X is not set
# CONFIG_SND_ENS1370 is not set
# CONFIG_SND_ENS1371 is not set
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_FM801 is not set
# CONFIG_SND_HDA_INTEL is not set
# CONFIG_SND_HDSP is not set
# CONFIG_SND_HDSPM is not set
# CONFIG_SND_HIFIER is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_ICE1724 is not set
# CONFIG_SND_INTEL8X0 is not set
# CONFIG_SND_INTEL8X0M is not set
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_MAESTRO3 is not set
# CONFIG_SND_MIXART is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_PCXHR is not set
# CONFIG_SND_RIPTIDE is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
# CONFIG_SND_RME9652 is not set
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_TRIDENT is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VIA82XX_MODEM is not set
# CONFIG_SND_VIRTUOSO is not set
# CONFIG_SND_VX222 is not set
# CONFIG_SND_YMFPCI is not set
CONFIG_SND_USB=y
# CONFIG_SND_USB_AUDIO is not set
# CONFIG_SND_USB_CAIAQ is not set
# CONFIG_SND_PCMCIA is not set
CONFIG_SND_GSC=y
CONFIG_SND_HARMONY=m
# CONFIG_SND_SOC is not set
# CONFIG_SOUND_PRIME is not set
CONFIG_AC97_BUS=m
CONFIG_HID_SUPPORT=y
CONFIG_HID=y
# CONFIG_HID_DEBUG is not set
CONFIG_HIDRAW=y

#
# USB Input Devices
#
CONFIG_USB_HID=y
# CONFIG_HID_PID is not set
# CONFIG_USB_HIDDEV is not set

#
# Special HID drivers
#
# CONFIG_HID_COMPAT is not set
CONFIG_HID_A4TECH=y
CONFIG_HID_APPLE=y
CONFIG_HID_BELKIN=y
CONFIG_HID_BRIGHT=y
CONFIG_HID_CHERRY=y
CONFIG_HID_CHICONY=y
CONFIG_HID_CYPRESS=y
CONFIG_HID_DELL=y
CONFIG_HID_EZKEY=y
CONFIG_HID_GYRATION=y
CONFIG_HID_LOGITECH=y
# CONFIG_LOGITECH_FF is not set
# CONFIG_LOGIRUMBLEPAD2_FF is not set
CONFIG_HID_MICROSOFT=y
CONFIG_HID_MONTEREY=y
CONFIG_HID_PANTHERLORD=y
# CONFIG_PANTHERLORD_FF is not set
CONFIG_HID_PETALYNX=y
CONFIG_HID_SAMSUNG=y
CONFIG_HID_SONY=y
CONFIG_HID_SUNPLUS=y
# CONFIG_THRUSTMASTER_FF is not set
# CONFIG_ZEROPLUS_FF is not set
CONFIG_USB_SUPPORT=y
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB=y
# CONFIG_USB_DEBUG is not set
CONFIG_USB_ANNOUNCE_NEW_DEVICES=y

#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_DEVICE_CLASS is not set
# CONFIG_USB_DYNAMIC_MINORS is not set
# CONFIG_USB_OTG is not set
CONFIG_USB_MON=y
# CONFIG_USB_WUSB is not set
# CONFIG_USB_WUSB_CBAF is not set

#
# USB Host Controller Drivers
#
# CONFIG_USB_C67X00_HCD is not set
# CONFIG_USB_EHCI_HCD is not set
# CONFIG_USB_ISP116X_HCD is not set
# CONFIG_USB_ISP1760_HCD is not set
CONFIG_USB_OHCI_HCD=y
# CONFIG_USB_OHCI_BIG_ENDIAN_DESC is not set
# CONFIG_USB_OHCI_BIG_ENDIAN_MMIO is not set
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_UHCI_HCD=y
# CONFIG_USB_SL811_HCD is not set
# CONFIG_USB_R8A66597_HCD is not set
# CONFIG_USB_WHCI_HCD is not set
# CONFIG_USB_HWA_HCD is not set

#
# USB Device Class drivers
#
# CONFIG_USB_ACM is not set
# CONFIG_USB_PRINTER is not set
# CONFIG_USB_WDM is not set
# CONFIG_USB_TMC is not set

#
# NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may also be needed;
#

#
# see USB_STORAGE Help for more information
#
# CONFIG_USB_STORAGE is not set
# CONFIG_USB_LIBUSUAL is not set

#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MICROTEK is not set

#
# USB port drivers
#
# CONFIG_USB_USS720 is not set
# CONFIG_USB_SERIAL is not set

#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_ADUTUX is not set
# CONFIG_USB_SEVSEG is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_BERRY_CHARGE is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_CYPRESS_CY7C63 is not set
# CONFIG_USB_CYTHERM is not set
# CONFIG_USB_PHIDGET is not set
# CONFIG_USB_IDMOUSE is not set
# CONFIG_USB_FTDI_ELAN is not set
# CONFIG_USB_APPLEDISPLAY is not set
# CONFIG_USB_LD is not set
# CONFIG_USB_TRANCEVIBRATOR is not set
# CONFIG_USB_IOWARRIOR is not set
# CONFIG_USB_TEST is not set
# CONFIG_USB_ISIGHTFW is not set
# CONFIG_USB_VST is not set
# CONFIG_USB_GADGET is not set
# CONFIG_UWB is not set
# CONFIG_MMC is not set
# CONFIG_MEMSTICK is not set
CONFIG_NEW_LEDS=y
CONFIG_LEDS_CLASS=y

#
# LED drivers
#

#
# LED Triggers
#
CONFIG_LEDS_TRIGGERS=y
CONFIG_LEDS_TRIGGER_TIMER=y
CONFIG_LEDS_TRIGGER_IDE_DISK=y
CONFIG_LEDS_TRIGGER_HEARTBEAT=y
# CONFIG_LEDS_TRIGGER_BACKLIGHT is not set
CONFIG_LEDS_TRIGGER_DEFAULT_ON=y
# CONFIG_ACCESSIBILITY is not set
# CONFIG_INFINIBAND is not set
CONFIG_RTC_LIB=y
CONFIG_RTC_CLASS=y
CONFIG_RTC_HCTOSYS=y
CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
# CONFIG_RTC_DEBUG is not set

#
# RTC interfaces
#
CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y
# CONFIG_RTC_INTF_DEV_UIE_EMUL is not set
# CONFIG_RTC_DRV_TEST is not set

#
# SPI RTC drivers
#

#
# Platform RTC drivers
#
# CONFIG_RTC_DRV_DS1286 is not set
# CONFIG_RTC_DRV_DS1511 is not set
# CONFIG_RTC_DRV_DS1553 is not set
# CONFIG_RTC_DRV_DS1742 is not set
# CONFIG_RTC_DRV_STK17TA8 is not set
# CONFIG_RTC_DRV_M48T86 is not set
# CONFIG_RTC_DRV_M48T35 is not set
# CONFIG_RTC_DRV_M48T59 is not set
# CONFIG_RTC_DRV_BQ4802 is not set
# CONFIG_RTC_DRV_V3020 is not set

#
# on-CPU RTC drivers
#
CONFIG_RTC_DRV_PARISC=y
CONFIG_DMADEVICES=y

#
# DMA Devices
#
CONFIG_AUXDISPLAY=y
# CONFIG_KS0108 is not set
# CONFIG_UIO is not set
# CONFIG_STAGING is not set
CONFIG_STAGING_EXCLUDE_BUILD=y

#
# File systems
#
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
CONFIG_EXT2_FS_SECURITY=y
# CONFIG_EXT2_FS_XIP is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
# CONFIG_EXT4_FS is not set
CONFIG_JBD=y
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_OCFS2_FS is not set
CONFIG_DNOTIFY=y
CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
# CONFIG_QUOTA is not set
CONFIG_AUTOFS_FS=y
# CONFIG_AUTOFS4_FS is not set
# CONFIG_FUSE_FS is not set

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
# CONFIG_ZISOFS is not set
# CONFIG_UDF_FS is not set

#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=y
# CONFIG_MSDOS_FS is not set
CONFIG_VFAT_FS=y
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
# 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 is not set
# CONFIG_HUGETLB_PAGE is not set
# CONFIG_CONFIGFS_FS is not set

#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_ECRYPT_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_ROOT_NFS=y
CONFIG_NFSD=y
CONFIG_NFSD_V3=y
# CONFIG_NFSD_V3_ACL is not set
CONFIG_NFSD_V4=y
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=y
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=y
CONFIG_SUNRPC_GSS=y
# CONFIG_SUNRPC_REGISTER_V4 is not set
CONFIG_RPCSEC_GSS_KRB5=y
CONFIG_RPCSEC_GSS_SPKM3=m
CONFIG_SMB_FS=m
CONFIG_SMB_NLS_DEFAULT=y
CONFIG_SMB_NLS_REMOTE="cp437"
CONFIG_CIFS=m
# CONFIG_CIFS_STATS is not set
CONFIG_CIFS_WEAK_PW_HASH=y
# CONFIG_CIFS_UPCALL is not set
CONFIG_CIFS_XATTR=y
CONFIG_CIFS_POSIX=y
# CONFIG_CIFS_DEBUG2 is not set
# CONFIG_CIFS_EXPERIMENTAL 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 is not set
CONFIG_MSDOS_PARTITION=y
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y
CONFIG_NLS_CODEPAGE_737=m
CONFIG_NLS_CODEPAGE_775=m
CONFIG_NLS_CODEPAGE_850=m
CONFIG_NLS_CODEPAGE_852=m
CONFIG_NLS_CODEPAGE_855=m
CONFIG_NLS_CODEPAGE_857=m
CONFIG_NLS_CODEPAGE_860=m
CONFIG_NLS_CODEPAGE_861=m
CONFIG_NLS_CODEPAGE_862=m
CONFIG_NLS_CODEPAGE_863=m
CONFIG_NLS_CODEPAGE_864=m
CONFIG_NLS_CODEPAGE_865=m
CONFIG_NLS_CODEPAGE_866=m
CONFIG_NLS_CODEPAGE_869=m
CONFIG_NLS_CODEPAGE_936=m
CONFIG_NLS_CODEPAGE_950=m
CONFIG_NLS_CODEPAGE_932=m
CONFIG_NLS_CODEPAGE_949=m
CONFIG_NLS_CODEPAGE_874=m
CONFIG_NLS_ISO8859_8=m
CONFIG_NLS_CODEPAGE_1250=y
CONFIG_NLS_CODEPAGE_1251=m
CONFIG_NLS_ASCII=m
CONFIG_NLS_ISO8859_1=y
CONFIG_NLS_ISO8859_2=m
CONFIG_NLS_ISO8859_3=m
CONFIG_NLS_ISO8859_4=m
CONFIG_NLS_ISO8859_5=m
CONFIG_NLS_ISO8859_6=m
CONFIG_NLS_ISO8859_7=m
CONFIG_NLS_ISO8859_9=m
CONFIG_NLS_ISO8859_13=m
CONFIG_NLS_ISO8859_14=m
CONFIG_NLS_ISO8859_15=m
CONFIG_NLS_KOI8_R=m
CONFIG_NLS_KOI8_U=m
CONFIG_NLS_UTF8=y
# CONFIG_DLM is not set

#
# Kernel hacking
#
# CONFIG_PRINTK_TIME is not set
CONFIG_ENABLE_WARN_DEPRECATED=y
CONFIG_ENABLE_MUST_CHECK=y
CONFIG_FRAME_WARN=1024
CONFIG_MAGIC_SYSRQ=y
CONFIG_UNUSED_SYMBOLS=y
# CONFIG_DEBUG_FS is not set
# CONFIG_HEADERS_CHECK is not set
CONFIG_DEBUG_KERNEL=y
CONFIG_DEBUG_SHIRQ=y
CONFIG_DETECT_SOFTLOCKUP=y
CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC=y
CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC_VALUE=1
# CONFIG_SCHED_DEBUG is not set
# CONFIG_SCHEDSTATS is not set
CONFIG_TIMER_STATS=y
# CONFIG_DEBUG_OBJECTS is not set
# CONFIG_DEBUG_SLAB is not set
CONFIG_DEBUG_RT_MUTEXES=y
CONFIG_DEBUG_PI_LIST=y
CONFIG_RT_MUTEX_TESTER=y
CONFIG_DEBUG_SPINLOCK=y
CONFIG_DEBUG_MUTEXES=y
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_BOOT_PRINTK_DELAY is not set
# CONFIG_RCU_TORTURE_TEST is not set
# CONFIG_RCU_CPU_STALL_DETECTOR is not set
# CONFIG_BACKTRACE_SELF_TEST is not set
# CONFIG_DEBUG_BLOCK_EXT_DEVT is not set
# CONFIG_FAULT_INJECTION is not set
CONFIG_SYSCTL_SYSCALL_CHECK=y

#
# Tracers
#
# CONFIG_SCHED_TRACER is not set
# CONFIG_CONTEXT_SWITCH_TRACER is not set
# CONFIG_BOOT_TRACER is not set
CONFIG_DYNAMIC_PRINTK_DEBUG=y
# CONFIG_SAMPLES is not set
# CONFIG_DEBUG_RODATA is not set

#
# Security options
#
CONFIG_KEYS=y
CONFIG_KEYS_DEBUG_PROC_KEYS=y
# CONFIG_SECURITY is not set
# CONFIG_SECURITYFS is not set
CONFIG_SECURITY_FILE_CAPABILITIES=y
CONFIG_XOR_BLOCKS=y
CONFIG_ASYNC_CORE=y
CONFIG_ASYNC_MEMCPY=y
CONFIG_ASYNC_XOR=y
CONFIG_CRYPTO=y

#
# Crypto core or helper
#
# CONFIG_CRYPTO_FIPS is not set
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_AEAD=y
CONFIG_CRYPTO_BLKCIPHER=y
CONFIG_CRYPTO_HASH=y
CONFIG_CRYPTO_RNG=y
CONFIG_CRYPTO_MANAGER=y
# CONFIG_CRYPTO_GF128MUL is not set
CONFIG_CRYPTO_NULL=m
# CONFIG_CRYPTO_CRYPTD is not set
CONFIG_CRYPTO_AUTHENC=m
CONFIG_CRYPTO_TEST=m

#
# Authenticated Encryption with Associated Data
#
# CONFIG_CRYPTO_CCM is not set
# CONFIG_CRYPTO_GCM is not set
# CONFIG_CRYPTO_SEQIV is not set

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

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

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

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

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

#
# Random Number Generation
#
# CONFIG_CRYPTO_ANSI_CPRNG is not set
CONFIG_CRYPTO_HW=y
# CONFIG_CRYPTO_DEV_HIFN_795X is not set

#
# Library routines
#
CONFIG_BITREVERSE=y
CONFIG_CRC_CCITT=m
# CONFIG_CRC16 is not set
CONFIG_CRC_T10DIF=y
# CONFIG_CRC_ITU_T is not set
CONFIG_CRC32=y
# CONFIG_CRC7 is not set
CONFIG_LIBCRC32C=m
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=y
CONFIG_PLIST=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y

[-- Attachment #3: config.diff --]
[-- Type: text/x-patch, Size: 7234 bytes --]

--- config-2.6.28-rc5-ion	2008-11-19 03:20:23.000000000 +0100
+++ .config	2008-11-19 18:01:22.000000000 +0100
@@ -1,7 +1,7 @@
 #
 # Automatically generated make config: don't edit
 # Linux kernel version: 2.6.28-rc5
-# Tue Nov 18 16:29:29 2008
+# Wed Nov 19 18:01:22 2008
 #
 CONFIG_PARISC=y
 CONFIG_MMU=y
@@ -483,7 +483,7 @@
 # SCSI device support
 #
 CONFIG_RAID_ATTRS=m
-CONFIG_SCSI=m
+CONFIG_SCSI=y
 CONFIG_SCSI_DMA=y
 # CONFIG_SCSI_TGT is not set
 CONFIG_SCSI_NETLINK=y
@@ -492,12 +492,12 @@
 #
 # SCSI support type (disk, tape, CD-ROM)
 #
-CONFIG_BLK_DEV_SD=m
+CONFIG_BLK_DEV_SD=y
 CONFIG_CHR_DEV_ST=m
 # CONFIG_CHR_DEV_OSST is not set
-CONFIG_BLK_DEV_SR=m
+CONFIG_BLK_DEV_SR=y
 # CONFIG_BLK_DEV_SR_VENDOR is not set
-CONFIG_CHR_DEV_SG=m
+CONFIG_CHR_DEV_SG=y
 CONFIG_CHR_DEV_SCH=m
 CONFIG_SCSI_ENCLOSURE=m
 
@@ -513,11 +513,12 @@
 #
 # SCSI Transports
 #
-CONFIG_SCSI_SPI_ATTRS=m
+CONFIG_SCSI_SPI_ATTRS=y
 CONFIG_SCSI_FC_ATTRS=m
 CONFIG_SCSI_ISCSI_ATTRS=m
 CONFIG_SCSI_SAS_ATTRS=m
 CONFIG_SCSI_SAS_LIBSAS=m
+# CONFIG_SCSI_SAS_ATA is not set
 CONFIG_SCSI_SAS_HOST_SMP=y
 CONFIG_SCSI_SAS_LIBSAS_DEBUG=y
 # CONFIG_SCSI_SRP_ATTRS is not set
@@ -561,15 +562,16 @@
 # CONFIG_SCSI_IZIP_EPP16 is not set
 # CONFIG_SCSI_IZIP_SLOW_CTR is not set
 CONFIG_SCSI_MVSAS=m
-CONFIG_SCSI_LASI700=m
+CONFIG_SCSI_LASI700=y
 CONFIG_53C700_LE_ON_BE=y
 CONFIG_SCSI_STEX=m
-CONFIG_SCSI_SYM53C8XX_2=m
+CONFIG_SCSI_SYM53C8XX_2=y
 CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=1
 CONFIG_SCSI_SYM53C8XX_DEFAULT_TAGS=16
 CONFIG_SCSI_SYM53C8XX_MAX_TAGS=64
 CONFIG_SCSI_SYM53C8XX_MMIO=y
-CONFIG_SCSI_ZALON=m
+# CONFIG_SCSI_IPR is not set
+CONFIG_SCSI_ZALON=y
 CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS=8
 CONFIG_SCSI_NCR53C8XX_MAX_TAGS=32
 CONFIG_SCSI_NCR53C8XX_SYNC=20
@@ -586,7 +588,65 @@
 CONFIG_SCSI_DH_HP_SW=m
 CONFIG_SCSI_DH_EMC=m
 CONFIG_SCSI_DH_ALUA=m
-# CONFIG_ATA is not set
+CONFIG_ATA=y
+# CONFIG_ATA_NONSTANDARD is not set
+# CONFIG_SATA_PMP is not set
+# CONFIG_SATA_AHCI is not set
+# CONFIG_SATA_SIL24 is not set
+CONFIG_ATA_SFF=y
+# CONFIG_SATA_SVW is not set
+# CONFIG_ATA_PIIX is not set
+# CONFIG_SATA_MV is not set
+# CONFIG_SATA_NV is not set
+# CONFIG_PDC_ADMA is not set
+# CONFIG_SATA_QSTOR is not set
+# CONFIG_SATA_PROMISE is not set
+# CONFIG_SATA_SX4 is not set
+# CONFIG_SATA_SIL is not set
+# CONFIG_SATA_SIS is not set
+# CONFIG_SATA_ULI is not set
+# CONFIG_SATA_VIA is not set
+# CONFIG_SATA_VITESSE is not set
+# CONFIG_SATA_INIC162X is not set
+# CONFIG_PATA_ALI is not set
+# CONFIG_PATA_AMD is not set
+# CONFIG_PATA_ARTOP is not set
+# CONFIG_PATA_ATIIXP is not set
+# CONFIG_PATA_CMD640_PCI is not set
+# CONFIG_PATA_CMD64X is not set
+# CONFIG_PATA_CS5520 is not set
+# CONFIG_PATA_CS5530 is not set
+# CONFIG_PATA_CYPRESS is not set
+# CONFIG_PATA_EFAR is not set
+# CONFIG_ATA_GENERIC is not set
+# CONFIG_PATA_HPT366 is not set
+# CONFIG_PATA_HPT37X is not set
+# CONFIG_PATA_HPT3X2N is not set
+# CONFIG_PATA_HPT3X3 is not set
+# CONFIG_PATA_IT821X is not set
+# CONFIG_PATA_IT8213 is not set
+# CONFIG_PATA_JMICRON is not set
+# CONFIG_PATA_TRIFLEX is not set
+# CONFIG_PATA_MARVELL is not set
+# CONFIG_PATA_MPIIX is not set
+# CONFIG_PATA_OLDPIIX is not set
+# CONFIG_PATA_NETCELL is not set
+# CONFIG_PATA_NINJA32 is not set
+# CONFIG_PATA_NS87410 is not set
+# CONFIG_PATA_NS87415 is not set
+# CONFIG_PATA_OPTI is not set
+# CONFIG_PATA_OPTIDMA is not set
+# CONFIG_PATA_PDC_OLD is not set
+# CONFIG_PATA_RADISYS is not set
+# CONFIG_PATA_RZ1000 is not set
+# CONFIG_PATA_SC1200 is not set
+# CONFIG_PATA_SERVERWORKS is not set
+# CONFIG_PATA_PDC2027X is not set
+# CONFIG_PATA_SIL680 is not set
+# CONFIG_PATA_SIS is not set
+# CONFIG_PATA_VIA is not set
+# CONFIG_PATA_WINBOND is not set
+# CONFIG_PATA_SCH is not set
 CONFIG_MD=y
 CONFIG_BLK_DEV_MD=m
 CONFIG_MD_LINEAR=m
@@ -648,8 +708,8 @@
 # CONFIG_REALTEK_PHY is not set
 # CONFIG_MDIO_BITBANG is not set
 CONFIG_NET_ETHERNET=y
-CONFIG_MII=m
-CONFIG_LASI_82596=m
+CONFIG_MII=y
+CONFIG_LASI_82596=y
 CONFIG_HAPPYMEAL=m
 # CONFIG_SUNGEM is not set
 CONFIG_CASSINI=m
@@ -657,12 +717,12 @@
 CONFIG_VORTEX=m
 # CONFIG_TYPHOON is not set
 CONFIG_NET_TULIP=y
-CONFIG_DE2104X=m
-CONFIG_TULIP=m
+CONFIG_DE2104X=y
+CONFIG_TULIP=y
 # CONFIG_TULIP_MWI is not set
 CONFIG_TULIP_MMIO=y
 # CONFIG_TULIP_NAPI is not set
-CONFIG_DE4X5=m
+CONFIG_DE4X5=y
 CONFIG_WINBOND_840=m
 # CONFIG_DM9102 is not set
 CONFIG_ULI526X=m
@@ -675,7 +735,7 @@
 # CONFIG_IBM_NEW_EMAC_MAL_CLR_ICINTSTAT is not set
 # CONFIG_IBM_NEW_EMAC_MAL_COMMON_ERR is not set
 CONFIG_NET_PCI=y
-CONFIG_PCNET32=m
+CONFIG_PCNET32=y
 # CONFIG_AMD8111_ETH is not set
 # CONFIG_ADAPTEC_STARFIRE is not set
 CONFIG_B44=m
@@ -905,8 +965,6 @@
 # CONFIG_PPDEV is not set
 # CONFIG_IPMI_HANDLER is not set
 CONFIG_HW_RANDOM=y
-CONFIG_GEN_RTC=y
-# CONFIG_GEN_RTC_X is not set
 # CONFIG_R3964 is not set
 # CONFIG_APPLICOM is not set
 CONFIG_RAW_DRIVER=m
@@ -1433,6 +1491,7 @@
 # CONFIG_NEW_LEDS is not set
 # CONFIG_ACCESSIBILITY is not set
 # CONFIG_INFINIBAND is not set
+CONFIG_RTC_LIB=y
 CONFIG_RTC_CLASS=y
 CONFIG_RTC_HCTOSYS=y
 CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
@@ -1495,23 +1554,26 @@
 #
 # File systems
 #
-CONFIG_EXT2_FS=m
-# CONFIG_EXT2_FS_XATTR is not set
-# CONFIG_EXT2_FS_XIP is not set
-CONFIG_EXT3_FS=m
+CONFIG_EXT2_FS=y
+CONFIG_EXT2_FS_XATTR=y
+CONFIG_EXT2_FS_POSIX_ACL=y
+CONFIG_EXT2_FS_SECURITY=y
+CONFIG_EXT2_FS_XIP=y
+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_EXT3_FS_POSIX_ACL=y
+CONFIG_EXT3_FS_SECURITY=y
 CONFIG_EXT4_FS=m
 # CONFIG_EXT4DEV_COMPAT is not set
 CONFIG_EXT4_FS_XATTR=y
 # CONFIG_EXT4_FS_POSIX_ACL is not set
 # CONFIG_EXT4_FS_SECURITY is not set
-CONFIG_JBD=m
-# CONFIG_JBD_DEBUG is not set
+CONFIG_FS_XIP=y
+CONFIG_JBD=y
+CONFIG_JBD_DEBUG=y
 CONFIG_JBD2=m
-# CONFIG_JBD2_DEBUG is not set
-CONFIG_FS_MBCACHE=m
+CONFIG_JBD2_DEBUG=y
+CONFIG_FS_MBCACHE=y
 CONFIG_REISERFS_FS=m
 # CONFIG_REISERFS_CHECK is not set
 CONFIG_REISERFS_PROC_INFO=y
@@ -1620,11 +1682,11 @@
 CONFIG_MSDOS_PARTITION=y
 CONFIG_NLS=y
 CONFIG_NLS_DEFAULT="iso8859-1"
-CONFIG_NLS_CODEPAGE_437=m
+CONFIG_NLS_CODEPAGE_437=y
 CONFIG_NLS_CODEPAGE_737=m
 CONFIG_NLS_CODEPAGE_775=m
-CONFIG_NLS_CODEPAGE_850=m
-CONFIG_NLS_CODEPAGE_852=m
+CONFIG_NLS_CODEPAGE_850=y
+CONFIG_NLS_CODEPAGE_852=y
 CONFIG_NLS_CODEPAGE_855=m
 CONFIG_NLS_CODEPAGE_857=m
 CONFIG_NLS_CODEPAGE_860=m
@@ -1641,11 +1703,11 @@
 CONFIG_NLS_CODEPAGE_949=m
 CONFIG_NLS_CODEPAGE_874=m
 CONFIG_NLS_ISO8859_8=m
-CONFIG_NLS_CODEPAGE_1250=m
-CONFIG_NLS_CODEPAGE_1251=m
-CONFIG_NLS_ASCII=m
-CONFIG_NLS_ISO8859_1=m
-CONFIG_NLS_ISO8859_2=m
+CONFIG_NLS_CODEPAGE_1250=y
+CONFIG_NLS_CODEPAGE_1251=y
+CONFIG_NLS_ASCII=y
+CONFIG_NLS_ISO8859_1=y
+CONFIG_NLS_ISO8859_2=y
 CONFIG_NLS_ISO8859_3=m
 CONFIG_NLS_ISO8859_4=m
 CONFIG_NLS_ISO8859_5=m
@@ -1654,10 +1716,10 @@
 CONFIG_NLS_ISO8859_9=m
 CONFIG_NLS_ISO8859_13=m
 CONFIG_NLS_ISO8859_14=m
-CONFIG_NLS_ISO8859_15=m
+CONFIG_NLS_ISO8859_15=y
 CONFIG_NLS_KOI8_R=m
 CONFIG_NLS_KOI8_U=m
-CONFIG_NLS_UTF8=m
+CONFIG_NLS_UTF8=y
 # CONFIG_DLM is not set
 
 #
@@ -1821,7 +1883,7 @@
 CONFIG_BITREVERSE=y
 CONFIG_CRC_CCITT=m
 CONFIG_CRC16=m
-CONFIG_CRC_T10DIF=m
+CONFIG_CRC_T10DIF=y
 # CONFIG_CRC_ITU_T is not set
 CONFIG_CRC32=y
 # CONFIG_CRC7 is not set

Re: 2.6.28-rcX in pretty bad shape on parisc

[John David Anglin]

> Why don't we compare configs?  This is mine for ion:
> 
> http://parisc-linux.org/~jejb/config-2.6.28-rc5-ion
> 
> I suspect we have some nasty interaction in the device driver subsystem
> (ion, the pa8900, isn't running either USB or PDC stable).

I tried this on what was ior:

HARD Booted.
palo ipl 1.14 root@penalosa Wed Oct  8 15:04:37 UTC 2008

Partition Start(MB) End(MB) Id Type
1               1     101   f0 Palo
2             102    1082   82 swap
3            1083   34726   83 ext2

PALO(F0) partition contains:
PALO is formatted EXT2/3
Command line for kernel: 'root=/dev/sda3 panic=5 console=ttyS1 palo_kernel=1/vmlinux'
Selected kernel: /vmlinux from partition 1

...

VFS: Cannot open root device "sda3" or unknown-block(0,0)
Please append a correct "root=" boot option; here are the available partitions:
DEBUG_BLOCK_EXT_DEVT is enabled, you need to specify explicit textual name for "root=" boot option.
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
Rebooting in 5 seconds..

What's missing?

Dave
-- 
J. David Anglin                                  dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)

Re: 2.6.28-rcX in pretty bad shape on parisc

[Helge Deller]

Helge Deller wrote:
> James Bottomley wrote:
>>> Why don't we compare configs?  This is mine for ion:
>>> http://parisc-linux.org/~jejb/config-2.6.28-rc5-ion
> 
>  > Domenico Andreoli wrote:
>> https://mnl.crema.unimi.it/~cavok/config-2.6.28-rc5
> 
> Helge:
> and here is mine (32bit(!), usually works on C3000, B160L, 715/64 and 
> Tadpole PARISC laptop - similiar to B160L):
> http://gsyprf10.external.hp.com/~deller/config.2.6.28-rc5

I don't want to flood the mailing list with my problem.

But I continued with testing:
1) I modified James's ion-config for netbooting and built it. Crashed 
same way as Dave just reported in another mail (DEBUG_BLOCK_EXT_DEVT is 
enabled, you need to specify explicit textual name for "root=" boot option.)

2) To avoid possible cross-compiler bugs I built James's ion-config 
(with no modifications at all!) on the c3k natively. It booted yesterday 
nicely without any problems from local disk. Today, I booted the same 
kernel, again with no modifications or changes at all, just the same 
kernel which already was on the disk, and it brought up a Slab corruption:


HARD Booted.
palo ipl 1.14 root@penalosa Wed Oct  8 15:04:37 UTC 2008

Partition Start(MB) End(MB) Id Type
1               1     257   82 swap
2             258     278   f0 Palo
3             279    2048   83 ext2
4            2049    8678   83 ext2

PALO(F0) partition contains:
     0/vmlinux32 14996734 bytes @ 0x10140000
     0/ramdisk 6264632 bytes @ 0x10f8d4fe

Information: No console specified on kernel command line. This is normal.
PALO will choose the console currently used by firmware (serial).
Command line for kernel: 'root=/dev/sda3 HOME=/ console=ttyS0 TERM=vt102 
palo_kernel=3/boot/vmlinux'
Selected kernel: /boot/vmlinux from partition 3
ELF64 executable
Entry 00100000 first 00100000 n 3
Segment 0 load 00100000 size 5140480 mediaptr 0x1000
Segment 1 load 0063c000 size 381320 mediaptr 0x4e8000
Segment 2 load 0069c000 size 215488 mediaptr 0x546000
Branching to kernel entry point 0x00100000.  If this is the last
message you see, you may need to switch your console.  This is
a common symptom -- search the FAQ and mailing list at parisc-linux.org

Linux version 2.6.28-rc5 (root@c3000) (gcc version 4.1.3 20080623 
(prerelease) (Debian 4.1.2-23)) #4 SMP Wed 8
unwind_init: start = 0x405042e4, end = 0x40536d34, entries = 12965
FP[0] enabled: Rev 1 Model 19
The 64-bit Kernel has started...
console [ttyB0] enabled
Initialized PDC Console for debugging.
Determining PDC firmware type: System Map.
model 00005dc0 00000481 00000000 00000002 777c3e84 100000f0 00000008 
000000b2 000000b2
vers  00000301
CPUID vers 19 rev 11 (0x0000026b)
capabilities 0x7
model 9000/785/C3700
Total Memory: 2048 MB
SMP: bootstrap CPU ID is 0
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 517120
Kernel command line: root=/dev/sda3 HOME=/ console=ttyS0 TERM=vt102 
palo_kernel=3/boot/vmlinux
PID hash table entries: 4096 (order: 12, 32768 bytes)
Console: colour dummy device 160x64
------------------------
| Locking API testsuite:
----------------------------------------------------------------------------
                                  | spin |wlock |rlock |mutex | wsem | 
rsem |
 
--------------------------------------------------------------------------
                      A-A deadlock:failed|failed|  ok 
|failed|failed|failed|
                  A-B-B-A deadlock:failed|failed|  ok 
|failed|failed|failed|
              A-B-B-C-C-A deadlock:failed|failed|  ok 
|failed|failed|failed|
              A-B-C-A-B-C deadlock:failed|failed|  ok 
|failed|failed|failed|
          A-B-B-C-C-D-D-A deadlock:failed|failed|  ok 
|failed|failed|failed|
          A-B-C-D-B-D-D-A deadlock:failed|failed|  ok 
|failed|failed|failed|
          A-B-C-D-B-C-D-A deadlock:failed|failed|  ok 
|failed|failed|failed|
                     double unlock:failed|failed|failed|  ok 
|failed|failed|
                   initialize 
held:failed|failed|failed|failed|failed|failed|
                  bad unlock order:  ok  |  ok  |  ok  |  ok  |  ok  | 
ok  |
 
--------------------------------------------------------------------------
               recursive read-lock:             |  ok  | 
|failed|
            recursive read-lock #2:             |  ok  | 
|failed|
             mixed read-write-lock:             |failed| 
|failed|
             mixed write-read-lock:             |failed| 
|failed|
 
--------------------------------------------------------------------------
      hard-irqs-on + irq-safe-A/12:failed|failed|  ok  |
      soft-irqs-on + irq-safe-A/12:failed|failed|  ok  |
      hard-irqs-on + irq-safe-A/21:failed|failed|  ok  |
      soft-irqs-on + irq-safe-A/21:failed|failed|  ok  |
        sirq-safe-A => hirqs-on/12:failed|failed|  ok  |
        sirq-safe-A => hirqs-on/21:failed|failed|  ok  |
          hard-safe-A + irqs-on/12:failed|failed|  ok  |
          soft-safe-A + irqs-on/12:failed|failed|  ok  |
          hard-safe-A + irqs-on/21:failed|failed|  ok  |
          soft-safe-A + irqs-on/21:failed|failed|  ok  |
     hard-safe-A + unsafe-B #1/123:failed|failed|  ok  |
     soft-safe-A + unsafe-B #1/123:failed|failed|  ok  |
     hard-safe-A + unsafe-B #1/132:failed|failed|  ok  |
     soft-safe-A + unsafe-B #1/132:failed|failed|  ok  |
     hard-safe-A + unsafe-B #1/213:failed|failed|  ok  |
     soft-safe-A + unsafe-B #1/213:failed|failed|  ok  |
     hard-safe-A + unsafe-B #1/231:failed|failed|  ok  |
     soft-safe-A + unsafe-B #1/231:failed|failed|  ok  |
     hard-safe-A + unsafe-B #1/312:failed|failed|  ok  |
     soft-safe-A + unsafe-B #1/312:failed|failed|  ok  |
     hard-safe-A + unsafe-B #1/321:failed|failed|  ok  |
     soft-safe-A + unsafe-B #1/321:failed|failed|  ok  |
     hard-safe-A + unsafe-B #2/123:failed|failed|  ok  |
     soft-safe-A + unsafe-B #2/123:failed|failed|  ok  |
     hard-safe-A + unsafe-B #2/132:failed|failed|  ok  |
     soft-safe-A + unsafe-B #2/132:failed|failed|  ok  |
     hard-safe-A + unsafe-B #2/213:failed|failed|  ok  |
     soft-safe-A + unsafe-B #2/213:failed|failed|  ok  |
     hard-safe-A + unsafe-B #2/231:failed|failed|  ok  |
     soft-safe-A + unsafe-B #2/231:failed|failed|  ok  |
     hard-safe-A + unsafe-B #2/312:failed|failed|  ok  |
     soft-safe-A + unsafe-B #2/312:failed|failed|  ok  |
     hard-safe-A + unsafe-B #2/321:failed|failed|  ok  |
     soft-safe-A + unsafe-B #2/321:failed|failed|  ok  |
       hard-irq lock-inversion/123:failed|failed|  ok  |
       soft-irq lock-inversion/123:failed|failed|  ok  |
       hard-irq lock-inversion/132:failed|failed|  ok  |
       soft-irq lock-inversion/132:failed|failed|  ok  |
       hard-irq lock-inversion/213:failed|failed|  ok  |
       soft-irq lock-inversion/213:failed|failed|  ok  |
       hard-irq lock-inversion/231:failed|failed|  ok  |
       soft-irq lock-inversion/231:failed|failed|  ok  |
       hard-irq lock-inversion/312:failed|failed|  ok  |
       soft-irq lock-inversion/312:failed|failed|  ok  |
       hard-irq lock-inversion/321:failed|failed|  ok  |
       soft-irq lock-inversion/321:failed|failed|  ok  |
       hard-irq read-recursion/123:  ok  |
       soft-irq read-recursion/123:  ok  |
       hard-irq read-recursion/132:  ok  |
       soft-irq read-recursion/132:  ok  |
       hard-irq read-recursion/213:  ok  |
       soft-irq read-recursion/213:  ok  |
       hard-irq read-recursion/231:  ok  |
       soft-irq read-recursion/231:  ok  |
       hard-irq read-recursion/312:  ok  |
       soft-irq read-recursion/312:  ok  |
       hard-irq read-recursion/321:  ok  |
       soft-irq read-recursion/321:  ok  |
--------------------------------------------------------
144 out of 218 testcases failed, as expected. |
----------------------------------------------------
Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)
Memory: 2054144k/2097152k available (3352k kernel code, 42608k reserved, 
1619k data, 212k init)
virtual kernel memory layout:
     vmalloc : 0x0000000000008000 - 0x000000003f000000   (1007 MB)
     memory  : 0x0000000040000000 - 0x00000000c0000000   (2048 MB)
       .init : 0x000000004069c000 - 0x00000000406d1000   ( 212 kB)
       .data : 0x00000000404462d8 - 0x00000000405db000   (1619 kB)
       .text : 0x0000000040100000 - 0x00000000404462d8   (3352 kB)
Calibrating delay loop... 1495.04 BogoMIPS (lpj=2990080)
Mount-cache hash table entries: 256
Brought up 1 CPUs
net_namespace: 840 bytes
NET: Registered protocol family 16
Searching for devices...
Found devices:
1. Astro BC Runway Port at 0xfffffffffed00000 [10] { 12, 0x0, 0x582, 
0x0000b }
2. Elroy PCI Bridge at 0xfffffffffed30000 [10/0] { 13, 0x0, 0x782, 0x0000a }
3. Elroy PCI Bridge at 0xfffffffffed32000 [10/1] { 13, 0x0, 0x782, 0x0000a }
4. Elroy PCI Bridge at 0xfffffffffed38000 [10/4] { 13, 0x0, 0x782, 0x0000a }
5. Elroy PCI Bridge at 0xfffffffffed3c000 [10/6] { 13, 0x0, 0x782, 0x0000a }
6. Allegro W2 at 0xfffffffffffa0000 [32] { 0, 0x0, 0x5dc, 0x00004 }
7. Memory at 0xfffffffffed10200 [49] { 1, 0x0, 0x09c, 0x00009 }
CPU(s): 1 x PA8700 (PCX-W2) at 750.000000 MHz
Setting cache flush threshold to 180000 (1 CPUs online)
SBA found Astro 2.1 at 0xfffffffffed00000
Elroy version TR4.0 (0x5) found at 0xfffffffffed30000
PCI: Enabled native mode for NS87415 (pif=0x8f)
Elroy version TR4.0 (0x5) found at 0xfffffffffed32000
iosapic: no IRTE for 0000:01:04.0 (IRQ not connected?)
iosapic: no IRTE for 0000:01:05.0 (IRQ not connected?)
Elroy version TR4.0 (0x5) found at 0xfffffffffed38000
Elroy version TR4.0 (0x5) found at 0xfffffffffed3c000
iosapic: hpa not registered for 0000:03:02.0
powersw: Soft power switch at 0xfffffff0f0400804 enabled.
SCSI subsystem initialized
NET: Registered protocol family 2
IP route cache hash table entries: 65536 (order: 7, 524288 bytes)
TCP established hash table entries: 262144 (order: 10, 4194304 bytes)
TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
TCP: Hash tables configured (established 262144 bind 65536)
TCP reno registered
NET: Registered protocol family 1
Performance monitoring counters enabled for Allegro W2
Initializing RT-Tester: OK
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
msgmni has been set to 4012
alg: No test for stdrng (krng)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
SuperIO: Found NS87560 Legacy I/O device at 0000:00:0e.1 (IRQ 68)
SuperIO: Serial port 1 at 0x3f8
SuperIO: Serial port 2 at 0x2f8
SuperIO: Parallel port at 0x378
SuperIO: Floppy controller at 0x3f0
SuperIO: ACPI at 0x7e0
SuperIO: USB regulator enabled
Linux agpgart interface v0.103
Serial: 8250/16550 driver4 ports, IRQ sharing disabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 3) is a 16550A
console handover: boot [ttyB0] -> real [ttyS0]
serial8250: ttyS1 at I/O 0x2f8 (irq = 4) is a 16550A
brd: module loaded
sym0: <896> rev 0x7 at pci 0000:00:0f.0 irq 69
sym0: PA-RISC Firmware, ID 7, Fast-40, SE, parity checking
sym0: SCSI BUS has been reset.
sym0: SCSI BUS mode change from SE to SE.
sym0: SCSI BUS has been reset.
scsi0 : sym-2.2.3
sym1: <896> rev 0x7 at pci 0000:00:0f.1 irq 69
sym1: PA-RISC Firmware, ID 7, Fast-40, LVD, parity checking
sym1: SCSI BUS has been reset.
scsi1 : sym-2.2.3
scsi 1:0:5:0: Direct-Access     SEAGATE  ST39102LC        HP01 PQ: 0 ANSI: 2
  target1:0:5: tagged command queuing enabled, command queue depth 16.
  target1:0:5: Beginning Domain Validation
  target1:0:5: asynchronous
  target1:0:5: wide asynchronous
  target1:0:5: FAST-40 WIDE SCSI 80.0 MB/s ST (25 ns, offset 15)
  target1:0:5: Domain Validation skipping write tests
  target1:0:5: Ending Domain Validation
scsi 1:0:6:0: Direct-Access     HP 36.4G ST336607LC       HPC3 PQ: 0 ANSI: 3
  target1:0:6: tagged command queuing enabled, command queue depth 16.
  target1:0:6: Beginning Domain Validation
  target1:0:6: asynchronous
  target1:0:6: wide asynchronous
  target1:0:6: FAST-40 WIDE SCSI 80.0 MB/s ST (25 ns, offset 31)
  target1:0:6: Domain Validation skipping write tests
  target1:0:6: Ending Domain Validation
Driver 'sd' needs updating - please use bus_type methods
sd 1:0:5:0: [sda] 17773524 512-byte hardware sectors: (9.10 GB/8.47 GiB)
sd 1:0:5:0: [sda] Write Protect is off
sd 1:0:5:0: [sda] Write cache: disabled, read cache: enabled, supports 
DPO and FUA
sd 1:0:5:0: [sda] 17773524 512-byte hardware sectors: (9.10 GB/8.47 GiB)
sd 1:0:5:0: [sda] Write Protect is off
sd 1:0:5:0: [sda] Write cache: disabled, read cache: enabled, supports 
DPO and FUA
  sda: sda1 sda2 sda3 sda4
sd 1:0:5:0: [sda] Attached SCSI disk
sd 1:0:6:0: [sdb] 71132960 512-byte hardware sectors: (36.4 GB/33.9 GiB)
sd 1:0:6:0: [sdb] Write Protect is off
sd 1:0:6:0: [sdb] Write cache: disabled, read cache: enabled, supports 
DPO and FUA
sd 1:0:6:0: [sdb] 71132960 512-byte hardware sectors: (36.4 GB/33.9 GiB)
sd 1:0:6:0: [sdb] Write Protect is off
sd 1:0:6:0: [sdb] Write cache: disabled, read cache: enabled, supports 
DPO and FUA
  sdb: sdb1 sdb2 sdb3 sdb4
sd 1:0:6:0: [sdb] Attached SCSI disk
sd 1:0:5:0: Attached scsi generic sg0 type 0
sd 1:0:6:0: Attached scsi generic sg1 type 0
HP SDC: No SDC found.
HP SDC MLC: Registering the System Domain Controller's HIL MLC.
HP SDC MLC: Request for raw HIL ISR hook denied
mice: PS/2 mouse device common for all mice
rtc-parisc rtc-parisc: rtc core: registered rtc-parisc as rtc0
TCP cubic registered
rtc-parisc rtc-parisc: setting system clock to 2008-11-20 07:34:21 UTC 
(1227166461)
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory:
Badness at kernel/smp.c:333
<...here is the known smp badness bug...>
212k freed
INIT: version 2.86 booting
.udev/ already exists on the static /dev! (warning).
Starting the hotplug events dispatcher: udevd.
Synthesizing the initial hotplug events...done.
Waiting for /dev to be fully populated...Linux Tulip driver version 
1.1.15 (Feb 27, 2007)
tulip0: no phy info, aborting mtable build
tulip0:  MII transceiver #1 config 1000 status 782d advertising 01e1.
eth0: Digital DS21142/43 Tulip rev 65 at MMIO 0xfffffffff2008000, 
00:30:6e:48:aa:64, IRQ 66.
tulip1:  EEPROM default media type Autosense.
tulip1:  Index #0 - Media MII (#11) described by a 21142 MII PHY (3) block.
tulip1:  Index #1 - Media 10base2 (#1) described by a 21142 Serial PHY 
(2) block.
tulip1:  Index #2 - Media AUI (#2) described by a 21142 Serial PHY (2) 
block.
tulip1:  MII transceiver #1 config 3100 status 7849 advertising 0101.
eth1: Digital DS21142/43 Tulip rev 33 at MMIO 0xfffffffff3004000, 
00:60:b0:7a:12:89, IRQ 72.
Slab corruption: size-128 start=00000000be8ab1d0, len=128
Redzone: 0x9d70000001/0x9f911029d74e35b.
Last user: [<0000000000000000>](0x0)
000: 00 00 00 00 00 00 00 02 00 00 00 00 00 0a 71 0c
010: 00 00 00 00 00 00 01 e8 00 00 00 00 00 00 00 30
020: 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 04
Redzone: 0x9f911029d74e35b/0x9f911029d74e35b.
Last user: [<ffffffffffffffff>](0xfffffffffffffffc)
000: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
010: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
Next obj: start=00000000be8ab268, len=128
Redzone: 0xd84156c5635688c0/0xd84156c5635688c0.
Last user: [<0000000040185f34>](add_notes_attrs+0x8c/0x1c0)
000: 00 00 00 00 bd c3 09 d8 00 00 00 01 00 00 00 00
010: 00 00 00 00 bd c1 4a 78 00 00 00 00 00 00 00 00
slab error in cache_alloc_debugcheck_after(): cache `size-128': double 
free, or memory outside object was oven
Backtrace:
  [<000000004011a6c4>] show_stack+0x14/0x20
  [<000000004011a6e8>] dump_stack+0x18/0x28
  [<00000000401cc054>] __slab_error+0x3c/0x48
  [<00000000401cc850>] cache_alloc_debugcheck_after+0x1d0/0x2f8
  [<00000000401cebf0>] kmem_cache_alloc+0xd0/0x1a8
  [<00000000401d7b9c>] __register_chrdev_region+0x54/0x210
  [<00000000401d7da0>] register_chrdev+0x48/0x190
  [<00000000000cf068>] init_oss_soundcore+0x28/0x60 [soundcore]
  [<00000000000cf0bc>] init_soundcore+0x1c/0x98 [soundcore]
  [<00000000401177f0>] do_one_initcall+0x50/0x1d0
  [<0000000040188988>] sys_init_module+0x100/0x2a8
  [<0000000040104ef8>] syscall_exit+0x0/0x14

00000000be8ab1c8: redzone 1:0x9d70000001, redzone 2:0x9f911029d74e35b
acenic.c: v0.92 08/05/2002  Jes Sorensen, linux-acenic@SunSITE.dk
                             http://home.cern.ch/~jes/gige/acenic.html
0000:02:01.0: Alteon AceNIC Gigabit Ethernet at 0xfffffffff3000000, irq 71
   Tigon II (Rev. 6), Firmware: 12.4.11, MAC: 00:30:6e:0f:91:d8
   PCI bus width: 64 bits, speed: 33MHz, latency: 248 clks
   Disabling PCI memory write and invalidate
0000:02:01.0: Firmware up and running
done.
Setting parameters of disc: (none).
Setting the system clock.
System Clock set to: Thu Nov 20 07:34:43 UTC 2008.
<...continues to boot until a login prompt>

My conclusion is:
There is some problem somewhere.
It does not show up always. Changing some kernel configuration may bring 
the bug up or it may not.
James, I think if you reboot your ion machine a few times or modify some 
kernel configs, you probably will hit the bug as well.

Helge

Re: 2.6.28-rcX in pretty bad shape on parisc

[Thibaut VARENE]

On Thu, Nov 20, 2008 at 8:55 AM, Helge Deller <deller@gmx.de> wrote:

> 2) To avoid possible cross-compiler bugs I built James's ion-config (with no
> modifications at all!) on the c3k natively. It booted yesterday nicely
> without any problems from local disk. Today, I booted the same kernel, again
> with no modifications or changes at all, just the same kernel which already
> was on the disk, and it brought up a Slab corruption:
[snip]
> My conclusion is:
> There is some problem somewhere.
> It does not show up always. Changing some kernel configuration may bring the
> bug up or it may not.
> James, I think if you reboot your ion machine a few times or modify some
> kernel configs, you probably will hit the bug as well.

Well on that topic, I've seen for a while (at least with 2.6.22.*) a
similar case where the same unmodified kernel binary would, from time
to time, fail to boot the machine (stuck with the timer_interrupt
delayed message). ISTR that happened most frequently on my A500-5X.
That may be something else, but the point is the symptom that "a given
kernel behaves differently across reboots" is not something new, if
that helps...

T-Bone

-- 
Thibaut VARENE
http://www.parisc-linux.org/~varenet/

Re: 2.6.28-rcX in pretty bad shape on parisc

[John David Anglin]

> But I continued with testing:
> 1) I modified James's ion-config for netbooting and built it. Crashed 
> same way as Dave just reported in another mail (DEBUG_BLOCK_EXT_DEVT is 
> enabled, you need to specify explicit textual name for "root=" boot option.)

In my case, the "root=" option was specified in the palo command line,
and I still got the error.  Tried booting several times and the same error
occurred each time.

Dave
-- 
J. David Anglin                                  dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)

Re: 2.6.28-rcX in pretty bad shape on parisc

[John David Anglin]

> VFS: Cannot open root device "sda3" or unknown-block(0,0)
> Please append a correct "root=" boot option; here are the available partitions:
> DEBUG_BLOCK_EXT_DEVT is enabled, you need to specify explicit textual name for "root=" boot option.
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
> Rebooting in 5 seconds..

I would guess this is because the kernel is in the palo partition.  2.6.27
doesn't have this problem...

Dave
-- 
J. David Anglin                                  dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)

Re: 2.6.28-rcX in pretty bad shape on parisc

[Grant Grundler]

On Thu, Nov 20, 2008 at 11:57:00AM -0500, John David Anglin wrote:
> > VFS: Cannot open root device "sda3" or unknown-block(0,0)
> > Please append a correct "root=" boot option; here are the available partitions:
> > DEBUG_BLOCK_EXT_DEVT is enabled, you need to specify explicit textual name for "root=" boot option.
> > Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
> > Rebooting in 5 seconds..
> 
> I would guess this is because the kernel is in the palo partition.  2.6.27
> doesn't have this problem...

I'm not seeing this with 2.6.28-rc3 or 2.6.28-rc5.
But I don't have DEBUG_BLOCK_EXT_DEVT enabled either.

The palo partition is just another ext2 filesystem from the kernel
point of view.

Maybe the full device pathname (e.g. root=/dev/sda3) is required?
It fully failed to associate sda3 with a known block device.

hth,
grant

Re: 2.6.28-rcX in pretty bad shape on parisc

[Grant Grundler]

On Wed, Nov 19, 2008 at 11:31:42AM +0900, James Bottomley wrote:
> On Tue, 2008-11-18 at 21:04 +0100, Helge Deller wrote:
> > I've tried various -rc candidates in the last few weeks, and sadly the 
> > parisc kernel is in pretty bad shape.
> > 
> > At the beginning I started to get problems only when I had USB 
> > keyboard/mouse attached to the PA machine. This lead to bugzilla 
> > http://bugzilla.kernel.org/show_bug.cgi?id=11913
> > 
> > Now, with -rc4 and -rc5 things got even worse.
> > 
> > Crashes happen often just directly at the beginning.
> > I'm sure it's not USB related any more, and I assume we have some 
> > strange mm-problem somewhere.
> 
> I'd be really dubious about that.  Our pa8900 ... the most mm unstable
> system we have ... is running -rc5 just fine.  The only warning before
> boot is the usual SMP one.

I'm not. During a normal kernel build:
/bin/sh: line 1:  2985 Trace/breakpoint trap   ( cat /dev/null ) > sound/mips/modules.order
make[2]: *** [sound/mips/modules.order] Error 133

Restarting the build allowed it to finish.
This is 2.6.28-rc5 trying to build itself again. I didn't see this
with -rc3 though it possible it's just chance that I didn't.

Config file is on:
   http://iou.parisc-linux.org/~grundler/2.6.28-rc5-config-j6000

(or gsyprf11:~grundler/public_html/2.6.28-rc5-config-j6000)



> Linux ion 2.6.28-rc5 #20 SMP Tue Nov 18 18:16:35 PST 2008 parisc64
> 
> Why don't we compare configs?  This is mine for ion:
> 
> http://parisc-linux.org/~jejb/config-2.6.28-rc5-ion
> 
> I suspect we have some nasty interaction in the device driver subsystem
> (ion, the pa8900, isn't running either USB or PDC stable).

That's possible. But the IOMMU code hasn't changed. I'm inclined
to believe another VM bug has crept in.

I agree with Dave that kernel hasn't gotten more stable since 2.6.22
kernel that we keep running on gsyprf11.

hth,
grant

Re: 2.6.28-rcX in pretty bad shape on parisc

[Grant Grundler]

On Fri, Nov 21, 2008 at 10:57:54PM -0700, Grant Grundler wrote:
> Maybe the full device pathname (e.g. root=/dev/sda3) is required?

ok....this was rubish.  Prevous message showed:
    Command line for kernel: 'root=/dev/sda3 panic=5 console=ttyS1

I don't know what the problem is here.


thanks,
grant

Re: 2.6.28-rcX in pretty bad shape on parisc

[John David Anglin]

> On Fri, Nov 21, 2008 at 10:57:54PM -0700, Grant Grundler wrote:
> > Maybe the full device pathname (e.g. root=/dev/sda3) is required?
> 
> ok....this was rubish.  Prevous message showed:
>     Command line for kernel: 'root=/dev/sda3 panic=5 console=ttyS1
> 
> I don't know what the problem is here.

Added a couple of printks:

VFS: name="/dev/root", p="cramfs"
err=-6
VFS: Cannot open root device "sda3" or unknown-block(0,0)
Please append a correct "root=" boot option; here are the available partitions:
DEBUG_BLOCK_EXT_DEVT is enabled, you need to specify explicit textual name for "root=" boot option.
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

Note: there are no partitions printed.

Dave
-- 
J. David Anglin                                  dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)

Re: 2.6.28-rcX in pretty bad shape on parisc

[John David Anglin]

On Sat, 22 Nov 2008, John David Anglin wrote:

> Added a couple of printks:
> 
> VFS: name="/dev/root", p="cramfs"
> err=-6
> VFS: Cannot open root device "sda3" or unknown-block(0,0)
> Please append a correct "root=" boot option; here are the available partitions:

Boots if I add initrd=1/initrd.img.  Have to say the error message isn't
very helpful.

Dave
-- 
J. David Anglin                                  dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)

Re: 2.6.28-rcX in pretty bad shape on parisc

[James Bottomley]

On Sat, 2008-11-22 at 16:37 -0500, John David Anglin wrote:
> On Sat, 22 Nov 2008, John David Anglin wrote:
> 
> > Added a couple of printks:
> > 
> > VFS: name="/dev/root", p="cramfs"
> > err=-6
> > VFS: Cannot open root device "sda3" or unknown-block(0,0)
> > Please append a correct "root=" boot option; here are the available partitions:
> 
> Boots if I add initrd=1/initrd.img.  Have to say the error message isn't
> very helpful.

Um, I think you're using a configuration where SCSI is modular?  So it
finds the root disk if you have an initrd (by loading the modules) and
it can't if you don't.

James

Re: 2.6.28-rcX in pretty bad shape on parisc

[Grant Grundler]

On Tue, Nov 18, 2008 at 09:04:32PM +0100, Helge Deller wrote:
> Hello PA hackers,
>
> I've tried various -rc candidates in the last few weeks, and sadly the 
> parisc kernel is in pretty bad shape.
>
> At the beginning I started to get problems only when I had USB 
> keyboard/mouse attached to the PA machine. This lead to bugzilla 
> http://bugzilla.kernel.org/show_bug.cgi?id=11913

I don't have any USB devices attached (serial console) on j6000.
Also getting occasional:
Backtrace:

with no other output when a process (usually hppa64-gcc) segfaults "randomly".
This is with kernel builds.

> Now, with -rc4 and -rc5 things got even worse.

I've tried both -rc3 and -rc5. I'm going to try 2.6.27.7 as well.

> Crashes happen often just directly at the beginning.
> I'm sure it's not USB related any more, and I assume we have some strange 
> mm-problem somewhere.

I'm inclined to agree though it's just a guess.

> The kernel crashes at various places, and mostly a null-pointer is 
> involved.

I haven't crashed the kernel per se, just getting segfaults reminiscent
of when we still had issues with mm not playing well with VIVT caches.

> Right now I'm clueless...

Sorry, I'm not better. :(
All I can do is try to work backwards a bit...but we've been in
pretty bad shape with various types of breakage since 2.6.22 about.

grant

Re: 2.6.28-rcX in pretty bad shape on parisc

[John David Anglin]

> On Tue, Nov 18, 2008 at 09:04:32PM +0100, Helge Deller wrote:
> > Hello PA hackers,
> >
> > I've tried various -rc candidates in the last few weeks, and sadly the 
> > parisc kernel is in pretty bad shape.
> >
> > At the beginning I started to get problems only when I had USB 
> > keyboard/mouse attached to the PA machine. This lead to bugzilla 
> > http://bugzilla.kernel.org/show_bug.cgi?id=11913
> 
> I don't have any USB devices attached (serial console) on j6000.
> Also getting occasional:
> Backtrace:
> 
> with no other output when a process (usually hppa64-gcc) segfaults "randomly".
> This is with kernel builds.
> 
> > Now, with -rc4 and -rc5 things got even worse.
> 
> I've tried both -rc3 and -rc5. I'm going to try 2.6.27.7 as well.

Try rc6.  It seems better than rc5.  With rc5 and JEB's ion config
on rp3340, bash dumped core four times building rc6.  In general, I see
more random segfaults in bash and make than any other applications.

rc6 is certainly not perfect.  I managed a full GCC build but in the
testsuite (ada) I has this error in the build log:

...
Running chapter cc ...
sed: option requires an argument -- e
Usage: sed [OPTION]... {script-only-if-no-other-script} [input-file]...

  -n, --quiet, --silent
		 suppress automatic printing of pattern space
  -e script, --expression=script
		 add the script to the commands to be executed
  -f script-file, --file=script-file
		 add the contents of script-file to the commands to be executed
  -i[SUFFIX], --in-place[=SUFFIX]
		 edit files in place (makes backup if extension supplied)
  -l N, --line-length=N
		 specify the desired line-wrap length for the `l' command
  --posix
		 disable all GNU extensions.
  -r, --regexp-extended
		 use extended regular expressions in the script.
  -s, --separate
		 consider files as separate rather than as a single continuous
		 long stream.
  -u, --unbuffered
		 load minimal amounts of data from the input files and flush
		 the output buffers more often
      --help     display this help and exit
      --version  output version information and exit

If no -e, --expression, -f, or --file option is given, then the first
non-option argument is taken as the sed script to interpret.  All
remaining arguments are names of input files; if no input files are
specified, then the standard input is read.

E-mail bug reports to: bonzini@gnu.org .
Be sure to include the word ``sed'' somewhere in the ``Subject:'' field.
FAIL:   cc30002

In the ada log:

BUILD cc30002.adb
gnatmake --GCC="/home/dave/gnu/gcc/objdir/gcc/xgcc -B/home/dave/gnu/gcc/objdir/g
cc/" -gnatws -O2 -I/home/dave/gnu/gcc/objdir/gcc/testsuite/ada/acats/support cc3
0002.adb -largs --GCC="/home/dave/gnu/gcc/objdir/gcc/xgcc -B/home/dave/gnu/gcc/o
bjdir/gcc/"
/home/dave/gnu/gcc/objdir/gcc/xgcc -c -B/home/dave/gnu/gcc/objdir/gcc/ -gnatws -
O2 -I/home/dave/gnu/gcc/objdir/gcc/testsuite/ada/acats/support cc30002.adb
/home/dave/gnu/gcc/objdir/gcc/xgcc -c -B/home/dave/gnu/gcc/objdir/gcc/ -gnatws -
O2 -I/home/dave/gnu/gcc/objdir/gcc/testsuite/ada/acats/support cc30002_0.adb
/home/dave/gnu/gcc/objdir/gcc/xgcc -c -B/home/dave/gnu/gcc/objdir/gcc/ -gnatws -
O2 -I/home/dave/gnu/gcc/objdir/gcc/testsuite/ada/acats/support cc30002_1.adb
/home/dave/gnu/gcc/objdir/gcc/xgcc -c -B/home/dave/gnu/gcc/objdir/gcc/ -gnatws -
O2 -I/home/dave/gnu/gcc/objdir/gcc/testsuite/ada/acats/support cc30002_2.adb
/home/dave/gnu/gcc/objdir/gcc/xgcc -c -B/home/dave/gnu/gcc/objdir/gcc/ -gnatws -
O2 -I/home/dave/gnu/gcc/objdir/gcc/testsuite/ada/acats/support cc30002_3.ads
gnatbind -I/home/dave/gnu/gcc/objdir/gcc/testsuite/ada/acats/support -x cc30002.
ali
gnatlink cc30002.ali --GCC=/home/dave/gnu/gcc/objdir/gcc/xgcc -B/home/dave/gnu/g
cc/objdir/gcc/
RUN 
/home/dave/gnu/gcc/gcc/gcc/testsuite/ada/acats/run_all.sh: line 16: /home/dave/g
nu/gcc/objdir/gcc/testsuite/ada/acats/tests/cc/cc30002/: is a directory
FAIL:   cc30002

The file cc30002 is there:

dave@mx3210:~/gnu/gcc/objdir/gcc/testsuite/ada/acats/tests/cc/cc30002$ ls
cc30002      cc30002.lst    cc30002_1.adb  cc30002_2.ads
cc30002.adb  cc30002_0.adb  cc30002_1.ads  cc30002_3.ads
cc30002.log  cc30002_0.ads  cc30002_2.adb

and the test passes if run.  I've never seen cc30002 fail before.

The error building rc6 was:

  ...
  LD [M]  fs/exportfs/exportfs.o

  malloc: ../../../bash/lib/sh/stringvec.c:73: assertion botched
  free: called with unallocated block argument
  Aborting.../bin/sh: line 1:  7965 Aborted                 (core dumped) ( cat /dev/null; echo kernel/fs/exportfs/exportfs.ko ) > fs/exportfs/modules.order
  make[2]: *** [fs/exportfs/modules.order] Error 134
  make[1]: *** [fs/exportfs] Error 2
  make: *** [fs] Error 2

Dave
-- 
J. David Anglin                                  dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)

Re: 2.6.28-rcX in pretty bad shape on parisc

[John David Anglin]

> > Boots if I add initrd=1/initrd.img.  Have to say the error message isn't
> > very helpful.
> 
> Um, I think you're using a configuration where SCSI is modular?  So it
> finds the root disk if you have an initrd (by loading the modules) and
> it can't if you don't.

The loop fails in the first iteration because the mount fails with
ENXIO.  It's not clear whether this is intentional but the code doesn't
check for it.

Dave
-- 
J. David Anglin                                  dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)

Re: 2.6.28-rcX in pretty bad shape on parisc

[John David Anglin]

> The error building rc6 was:
> 
>   ...
>   LD [M]  fs/exportfs/exportfs.o
> 
>   malloc: ../../../bash/lib/sh/stringvec.c:73: assertion botched

This just happened with rc6, so the bug isn't fixed.

Dave
-- 
J. David Anglin                                  dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)

Re: 2.6.28-rcX in pretty bad shape on parisc

[John David Anglin]

> >   malloc: ../../../bash/lib/sh/stringvec.c:73: assertion botched
> 
> This just happened with rc6, so the bug isn't fixed.

Continued testing rc6.  After three segv loops caused by /bin/sh
segfaulting and the kernel stacktrace filling the file system with
log messages, I rebuilt rc6 with Helge's fix.  Now I things are
better when bash segfaults.  However, it drops core so often that
the system is unusable for serious work.  The problem appears more
like a glibc bug than a kernel fault, but it's not clear.

Here's one segv:

dave@mx3210:/var/log$ dpkg -l libc6
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name           Version        Description
+++-==============-==============-============================================
ii  libc6          2.7-16         GNU C Library: Shared libraries

dave@mx3210:~/gnu/gcc/objdir/libiberty$ gdb -c core /bin/sh
GNU gdb (GDB) 6.8.50.20080915-cvs
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "hppa-unknown-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
(no debugging symbols found)
BFD: Warning: /home/dave/gnu/gcc/objdir/libiberty/core is truncated: expected core file size >= 1654784, found: 1585152.
Reading symbols from /lib/libncurses.so.5...(no debugging symbols found)...done.
Loaded symbols for /lib/libncurses.so.5
Reading symbols from /lib/libdl.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/libdl.so.2
Reading symbols from /lib/libc.so.6...
(no debugging symbols found)...done.
Loaded symbols for /lib/libc.so.6
Reading symbols from /lib/ld.so.1...(no debugging symbols found)...done.
Loaded symbols for /lib/ld.so.1

Core was generated by `/bin/sh -c if [ x"-fPIC" != x ]; then \
  gcc -c -DHAVE_CONFIG_H -g -fkeep-inli'.
Program terminated with signal 11, Segmentation fault.
#0  0x401ed4e4 in ?? () from /lib/ld.so.1
(gdb) bt
#0  0x401ed4e4 in ?? () from /lib/ld.so.1
#1  0x401f3b58 in ?? () from /lib/ld.so.1
#2  0x00046398 in ?? ()
#3  0x00048640 in wait_for ()
#4  0x00038494 in execute_command_internal ()
#5  0x00038608 in execute_command ()
#6  0x000374a4 in execute_command_internal ()
#7  0x00073994 in parse_and_execute ()
#8  0x000259fc in ?? ()
#9  0x00026988 in main ()
(gdb) disass 0x401ed4d4 0x401ed4f4
Dump of assembler code from 0x401ed4d4 to 0x401ed4f4:
0x401ed4d4:	ldw 0(r3),r20
0x401ed4d8:	ldw 4(ret0),ret0
0x401ed4dc:	add,l r20,ret0,r25
0x401ed4e0:	ldw 2c(r3),ret0
0x401ed4e4:	ldw 4(ret0),ret1
0x401ed4e8:	ldw 8(r5),ret0
0x401ed4ec:	addil L%800,r19,r1
0x401ed4f0:	add,l r25,ret0,r25
End of assembler dump.
(gdb) p/x $ret0
$1 = 0x0
(gdb) info shared
>From        To          Syms Read   Shared Object Library
0x402fca40  0x4031e490  Yes         /lib/libncurses.so.5
0x405f5d10  0x405f70ec  Yes         /lib/libdl.so.2
0x4061beb0  0x4070d630  Yes         /lib/libc.so.6
0x401e0370  0x401f8c80  Yes         /lib/ld.so.1

The segv looks to be in _dl_fixup at 0xf3b8 in /lib/ld.so.1.

Dave
-- 
J. David Anglin                                  dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)

Re: 2.6.28-rcX in pretty bad shape on parisc

[Carlos O'Donell]

On Mon, Nov 24, 2008 at 9:54 PM, John David Anglin
<dave@hiauly1.hia.nrc.ca> wrote:
> The segv looks to be in _dl_fixup at 0xf3b8 in /lib/ld.so.1.

The dynamic loader is sensitive to VM bugs, as are several of the
glibc tests. Too bad you probably can't run the glibc testsuite on
this kernel.

Given your earlier comments it would seen the segfault is not
reproducible and happens often and randomly?

The _dl_fixup routine is very complicated, and eventually responsible
for mapping in a new shared library. This could tickle any number of
VM bugs.

The only way I know how to solve this class of problem is to start
bisecting the kernel until it works again and determine what commit
made the stability worse.

$0.02.

I'm still organizing the new house Kristine and I are renting, and my
rack is only partly cabled up at this point. I'll try to get on that
ASAP so I can also have a look at the latest kernel.

Cheers,
Carlos.

Re: 2.6.28-rcX in pretty bad shape on parisc

[Guy Martin]

Hi Carlos,

It has been happening to me as far back as 2.6.25 IIRC.
It occurs only on SMP kernels and on various models (K410, L2000).

I've tried to bissect that as well but kernel before 2.6.25 aren't really useable SMP due to the global irq bug or so.

To me that is a bug that as always been there. It is random but some builds almost always fail. Not always at the same place tho.

Cheers,
  Guy

On Tue, 25 Nov 2008 08:33:24 -0500
"Carlos O'Donell" <carlos@systemhalted.org> wrote:

> On Mon, Nov 24, 2008 at 9:54 PM, John David Anglin
> <dave@hiauly1.hia.nrc.ca> wrote:
> > The segv looks to be in _dl_fixup at 0xf3b8 in /lib/ld.so.1.
> 
> The dynamic loader is sensitive to VM bugs, as are several of the
> glibc tests. Too bad you probably can't run the glibc testsuite on
> this kernel.
> 
> Given your earlier comments it would seen the segfault is not
> reproducible and happens often and randomly?
> 
> The _dl_fixup routine is very complicated, and eventually responsible
> for mapping in a new shared library. This could tickle any number of
> VM bugs.
> 
> The only way I know how to solve this class of problem is to start
> bisecting the kernel until it works again and determine what commit
> made the stability worse.
> 
> $0.02.
> 
> I'm still organizing the new house Kristine and I are renting, and my
> rack is only partly cabled up at this point. I'll try to get on that
> ASAP so I can also have a look at the latest kernel.
> 
> Cheers,
> Carlos.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-parisc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


-- 
Guy Martin
Gentoo Linux - HPPA port lead

Re: 2.6.28-rcX in pretty bad shape on parisc

[Carlos O'Donell]

On Tue, Nov 25, 2008 at 8:58 AM, Guy Martin <gmsoft@tuxicoman.be> wrote:
> It has been happening to me as far back as 2.6.25 IIRC.
> It occurs only on SMP kernels and on various models (K410, L2000).
>
> I've tried to bissect that as well but kernel before 2.6.25 aren't really useable SMP due to the global irq bug or so.
>
> To me that is a bug that as always been there. It is random but some builds almost always fail. Not always at the same place tho.

Can you build glibc, run the testsuite, and see if anything fails
semi-consistently?

Cheers,
Carlos.

Re: 2.6.28-rcX in pretty bad shape on parisc

[Guy Martin]

Hi Carlos,

Sure I will. Any particular version you want me to test ?

Also, I was quite lost with the flow of emails about kernel bugs lately.
What kernel version should I use and which what patch set ?

Cheers,
 Guy

On Tue, 25 Nov 2008 09:07:42 -0500
"Carlos O'Donell" <carlos@systemhalted.org> wrote:

> On Tue, Nov 25, 2008 at 8:58 AM, Guy Martin <gmsoft@tuxicoman.be>
> wrote:
> > It has been happening to me as far back as 2.6.25 IIRC.
> > It occurs only on SMP kernels and on various models (K410, L2000).
> >
> > I've tried to bissect that as well but kernel before 2.6.25 aren't
> > really useable SMP due to the global irq bug or so.
> >
> > To me that is a bug that as always been there. It is random but
> > some builds almost always fail. Not always at the same place tho.
> 
> Can you build glibc, run the testsuite, and see if anything fails
> semi-consistently?
> 
> Cheers,
> Carlos.


-- 
Guy Martin
Gentoo Linux - HPPA port lead

Re: 2.6.28-rcX in pretty bad shape on parisc

[John David Anglin]

Hi,

I just pulled and built Kyle's parisc-2.6 tree.  It essentially 2.6.28-rc6
plus four extra patches (three parisc specific).

I am seeing these warnings in a 64-bit kernel build:

drivers/input/keyboard/hilkbd.c: In function 'hil_init_chip':
drivers/input/keyboard/hilkbd.c:317: warning: format '%08lx' expects type 'long unsigned int', but argument 2 has type 'resource_size_t'

drivers/net/lasi_82596.c: In function 'lan_init_chip':
drivers/net/lasi_82596.c:164: warning: format '%lx' expects type 'long unsigned 
int', but argument 3 has type 'resource_size_t'
drivers/net/lasi_82596.c:169: warning: format '%lx' expects type 'long unsigned 
int', but argument 2 has type 'resource_size_t'

drivers/parisc/ccio-dma.c: In function 'ccio_init_resource':
drivers/parisc/ccio-dma.c:1403: warning: format '%08lx' expects type 'long unsig
ned int', but argument 3 has type 'resource_size_t'drivers/parisc/ccio-dma.c:1403: warning: format '%08lx' expects type 'long unsigned int', but argument 4 has type 'resource_size_t'
drivers/parisc/ccio-dma.c: In function 'ccio_probe':
drivers/parisc/ccio-dma.c:1554: warning: format '%lx' expects type 'long unsigned int', but argument 3 has type 'resource_size_t'

drivers/parisc/hppb.c: In function 'hppb_probe':
drivers/parisc/hppb.c:65: warning: format '%x' expects type 'unsigned int', but argument 2 has type 'resource_size_t'
drivers/parisc/hppb.c:77: warning: format '%08x' expects type 'unsigned int', but argument 3 has type 'resource_size_t'
drivers/parisc/hppb.c:77: warning: format '%08x' expects type 'unsigned int', but argument 4 has type 'resource_size_t'

drivers/parisc/dino.c:822: warning: format '%lx' expects type 'long unsigned int', but argument 4 has type 'resource_size_t'
drivers/parisc/dino.c:822: warning: format '%lx' expects type 'long unsigned int', but argument 5 has type 'resource_size_t'
drivers/parisc/dino.c: In function 'dino_common_init':
drivers/parisc/dino.c:902: warning: format '%lx' expects type 'long unsigned int', but argument 3 has type 'resource_size_t'
drivers/parisc/dino.c:902: warning: format '%lx' expects type 'long unsigned int', but argument 4 has type 'resource_size_t'

drivers/parisc/asp.c: In function 'asp_init_chip':
drivers/parisc/asp.c:85: warning: format '%lx' expects type 'long unsigned int', but argument 4 has type 'resource_size_t'

drivers/parport/parport_gsc.c: In function 'parport_init_chip':
drivers/parport/parport_gsc.c:356: warning: format '%lx' expects type 'long unsigned int', but argument 2 has type 'resource_size_t'

drivers/serial/8250_gsc.c: In function 'serial_init_chip':
drivers/serial/8250_gsc.c:44: warning: format '%lx' expects type 'long unsigned 
int', but argument 2 has type 'resource_size_t'

sound/parisc/harmony.c: In function 'snd_harmony_create':
sound/parisc/harmony.c:938: warning: format '%lx' expects type 'long unsigned in
t', but argument 2 has type 'resource_size_t'

'resource_size_t' is defined in linux/types.h:

#ifdef CONFIG_PHYS_ADDR_T_64BIT
typedef u64 phys_addr_t;
#else
typedef u32 phys_addr_t;
#endif

typedef phys_addr_t resource_size_t;

CONFIG_PHYS_ADDR_T_64BIT is defined in linux/autoconf.h, so I have to think
it is not being included, resulting in incorrect defines for phys_addr_t.
Is this what needs to be done?

Dave
-- 
J. David Anglin                                  dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)

Re: 2.6.28-rcX in pretty bad shape on parisc

[Helge Deller]

John David Anglin wrote:
> Hi,
> 
> I just pulled and built Kyle's parisc-2.6 tree.  It essentially 2.6.28-rc6
> plus four extra patches (three parisc specific).
> 
> I am seeing these warnings in a 64-bit kernel build:
> 
> drivers/input/keyboard/hilkbd.c: In function 'hil_init_chip':
> drivers/input/keyboard/hilkbd.c:317: warning: format '%08lx' expects type 'long unsigned int', but argument 2 has type 'resource_size_t'
> 
> drivers/net/lasi_82596.c: In function 'lan_init_chip':
> drivers/net/lasi_82596.c:164: warning: format '%lx' expects type 'long unsigned 
> int', but argument 3 has type 'resource_size_t'
> drivers/net/lasi_82596.c:169: warning: format '%lx' expects type 'long unsigned 
> int', but argument 2 has type 'resource_size_t'
> 
> drivers/parisc/ccio-dma.c: In function 'ccio_init_resource':
> drivers/parisc/ccio-dma.c:1403: warning: format '%08lx' expects type 'long unsig
> ned int', but argument 3 has type 'resource_size_t'drivers/parisc/ccio-dma.c:1403: warning: format '%08lx' expects type 'long unsigned int', but argument 4 has type 'resource_size_t'
> drivers/parisc/ccio-dma.c: In function 'ccio_probe':
> drivers/parisc/ccio-dma.c:1554: warning: format '%lx' expects type 'long unsigned int', but argument 3 has type 'resource_size_t'
> 
> drivers/parisc/hppb.c: In function 'hppb_probe':
> drivers/parisc/hppb.c:65: warning: format '%x' expects type 'unsigned int', but argument 2 has type 'resource_size_t'
> drivers/parisc/hppb.c:77: warning: format '%08x' expects type 'unsigned int', but argument 3 has type 'resource_size_t'
> drivers/parisc/hppb.c:77: warning: format '%08x' expects type 'unsigned int', but argument 4 has type 'resource_size_t'
> 
> drivers/parisc/dino.c:822: warning: format '%lx' expects type 'long unsigned int', but argument 4 has type 'resource_size_t'
> drivers/parisc/dino.c:822: warning: format '%lx' expects type 'long unsigned int', but argument 5 has type 'resource_size_t'
> drivers/parisc/dino.c: In function 'dino_common_init':
> drivers/parisc/dino.c:902: warning: format '%lx' expects type 'long unsigned int', but argument 3 has type 'resource_size_t'
> drivers/parisc/dino.c:902: warning: format '%lx' expects type 'long unsigned int', but argument 4 has type 'resource_size_t'
> 
> drivers/parisc/asp.c: In function 'asp_init_chip':
> drivers/parisc/asp.c:85: warning: format '%lx' expects type 'long unsigned int', but argument 4 has type 'resource_size_t'
> 
> drivers/parport/parport_gsc.c: In function 'parport_init_chip':
> drivers/parport/parport_gsc.c:356: warning: format '%lx' expects type 'long unsigned int', but argument 2 has type 'resource_size_t'
> 
> drivers/serial/8250_gsc.c: In function 'serial_init_chip':
> drivers/serial/8250_gsc.c:44: warning: format '%lx' expects type 'long unsigned 
> int', but argument 2 has type 'resource_size_t'
> 
> sound/parisc/harmony.c: In function 'snd_harmony_create':
> sound/parisc/harmony.c:938: warning: format '%lx' expects type 'long unsigned in
> t', but argument 2 has type 'resource_size_t'
> 
> 'resource_size_t' is defined in linux/types.h:
> 
> #ifdef CONFIG_PHYS_ADDR_T_64BIT
> typedef u64 phys_addr_t;
> #else
> typedef u32 phys_addr_t;
> #endif
> 
> typedef phys_addr_t resource_size_t;
> 
> CONFIG_PHYS_ADDR_T_64BIT is defined in linux/autoconf.h, so I have to think
> it is not being included, resulting in incorrect defines for phys_addr_t.
> Is this what needs to be done?

Citing Documentation/printk-formats.txt:
If <type> is dependent on a config option for its size (e.g., sector_t,
blkcnt_t, phys_addr_t, resource_size_t) or is architecture-dependent
for its size (e.g., tcflag_t), use a format specifier of its largest
possible type and explicitly cast to it.  Example:

         printk("test: sector number/total blocks: %llu/%llu\n",
                 (unsigned long long)sector, (unsigned long 
long)blockcount);

So, we should convert everything to (unsigned long long).
I was planning to send such patches soon, but didn't had time yet.

Helge

Re: 2.6.28-rcX in pretty bad shape on parisc

[Thibaut VARENE]

On Tue, Dec 2, 2008 at 1:00 AM, John David Anglin
<dave@hiauly1.hia.nrc.ca> wrote:

>
> Are there some standard 32 and 64 bit defines for format strings?  Or, do we
> always want 16 hex digits?

In traps.c we used to do this for the regs dump:

#ifdef __LP64__
#define RFMT "%016lx"
#else
#define RFMT "%08lx"
#endif

and then sprintf(p, " " RFMT, (i+j) == 0 ? 0 : regs->gr[i + j]);

I guess a similar trick could do, to some extent?

HTH

T-Bone

Re: 2.6.28-rcX in pretty bad shape on parisc

[John David Anglin]

> So, we should convert everything to (unsigned long long).
> I was planning to send such patches soon, but didn't had time yet.

All the warnings are for addresses.  We also need to change the format
specifier depending on whether addresses are 32 or 64 bits.  For example,

hil_init_chip(struct parisc_device *dev)
{
        if (!dev->irq) {
		printk(KERN_WARNING "HIL: IRQ not found for HIL bus at 0x%08lx\n", dev->hpa.start);

Are there some standard 32 and 64 bit defines for format strings?  Or, do we
always want 16 hex digits?

Dave
-- 
J. David Anglin                                  dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)

Re: 2.6.28-rcX in pretty bad shape on parisc

[Helge Deller]

Thibaut VARENE wrote:
> On Tue, Dec 2, 2008 at 1:00 AM, John David Anglin
> <dave@hiauly1.hia.nrc.ca> wrote:
> 
>> Are there some standard 32 and 64 bit defines for format strings?  Or, do we
>> always want 16 hex digits?
> 
> In traps.c we used to do this for the regs dump:
> 
> #ifdef __LP64__
> #define RFMT "%016lx"
> #else
> #define RFMT "%08lx"
> #endif
> 
> and then sprintf(p, " " RFMT, (i+j) == 0 ? 0 : regs->gr[i + j]);
> 
> I guess a similar trick could do, to some extent?

An alternative possibility would be to use pointers, e.g.
printk("addr 0x%p\n", (void *)x);
That way it would 32 or 64bit addresses, depending if we have a 32 or 
64bit kernel.

Helge

Re: 2.6.28-rcX in pretty bad shape on parisc

[John David Anglin]

> Given your earlier comments it would seen the segfault is not
> reproducible and happens often and randomly?

I gave 2.6.28-rc7-git5 a try this evening.  Hit the same error.
While its occurence may be random, the identical fault occurred
multiple times in a short period of testing.

I see this bit of code in _dl_fixup:

0x401ed464 <_dl_fixup+172>:	mfctl tr3,r21
0x401ed468 <_dl_fixup+176>:	ldw -3e0(r21),ret0
0x401ed46c <_dl_fixup+180>:	cmpib,<> 0,ret0,0x401ed628 <_dl_fixup+624>

and

0x401ed5fc <_dl_fixup+580>:	ldi 1,r24
0x401ed600 <_dl_fixup+584>:	ldi 0,r23
0x401ed604 <_dl_fixup+588>:	mfctl tr3,r26
0x401ed608 <_dl_fixup+592>:	copy r24,r25
0x401ed60c <_dl_fixup+596>:	ldo -3dc(r26),r26
0x401ed610 <_dl_fixup+600>:	copy r19,r4
0x401ed614 <_dl_fixup+604>:	be,l 100(sr2,r0),sr0,r31
0x401ed618 <_dl_fixup+608>:	ldi d2,r20

So, the code is using the thread register (cr27).  Not sure what syscall
this is.  However, the problem might be TLS releated.

Dave
-- 
J. David Anglin                                  dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)

Re: 2.6.28-rcX in pretty bad shape on parisc

[Kyle McMartin]

On Mon, Dec 01, 2008 at 11:54:25AM +0100, Thibaut VARENE wrote:
> On Tue, Dec 2, 2008 at 1:00 AM, John David Anglin
> <dave@hiauly1.hia.nrc.ca> wrote:
> 
> >
> > Are there some standard 32 and 64 bit defines for format strings?  Or, do we
> > always want 16 hex digits?
> 
> In traps.c we used to do this for the regs dump:
> 
> #ifdef __LP64__
> #define RFMT "%016lx"
> #else
> #define RFMT "%08lx"
> #endif
> 
> and then sprintf(p, " " RFMT, (i+j) == 0 ? 0 : regs->gr[i + j]);
> 
> I guess a similar trick could do, to some extent?

The prettiest way to do it would be to add a %p handler for
resource_size_t args, cheat on the pointing bit, and clean up the
in-tree users of %llx/ull-casts.

Re: 2.6.28-rcX in pretty bad shape on parisc

[Grant Grundler]

On Sun, Dec 07, 2008 at 11:50:02PM -0500, John David Anglin wrote:
> > Given your earlier comments it would seen the segfault is not
> > reproducible and happens often and randomly?
> 
> I gave 2.6.28-rc7-git5 a try this evening.  Hit the same error.
> While its occurence may be random, the identical fault occurred
> multiple times in a short period of testing.

I routinely get a segfault the first time I attempt to compile linux-2.6
kernel after reboot.  If I "find linux-2.6 | xargs cksum", the kernel
builds fine.

> I see this bit of code in _dl_fixup:
> 
> 0x401ed464 <_dl_fixup+172>:	mfctl tr3,r21
> 0x401ed468 <_dl_fixup+176>:	ldw -3e0(r21),ret0
> 0x401ed46c <_dl_fixup+180>:	cmpib,<> 0,ret0,0x401ed628 <_dl_fixup+624>
> 
> and
> 
> 0x401ed5fc <_dl_fixup+580>:	ldi 1,r24
> 0x401ed600 <_dl_fixup+584>:	ldi 0,r23
> 0x401ed604 <_dl_fixup+588>:	mfctl tr3,r26
> 0x401ed608 <_dl_fixup+592>:	copy r24,r25
> 0x401ed60c <_dl_fixup+596>:	ldo -3dc(r26),r26
> 0x401ed610 <_dl_fixup+600>:	copy r19,r4
> 0x401ed614 <_dl_fixup+604>:	be,l 100(sr2,r0),sr0,r31
> 0x401ed618 <_dl_fixup+608>:	ldi d2,r20
> 
> So, the code is using the thread register (cr27).  Not sure what syscall
> this is.  However, the problem might be TLS releated.

I have no idea if TLS makes a difference to kernel builds.

thanks,
grant

Re: 2.6.28-rcX in pretty bad shape on parisc

[Carlos O'Donell]

On Sun, Dec 7, 2008 at 11:50 PM, John David Anglin
<dave@hiauly1.hia.nrc.ca> wrote:
>> Given your earlier comments it would seen the segfault is not
>> reproducible and happens often and randomly?
>
> I gave 2.6.28-rc7-git5 a try this evening.  Hit the same error.
> While its occurence may be random, the identical fault occurred
> multiple times in a short period of testing.
>
> I see this bit of code in _dl_fixup:
>
> 0x401ed464 <_dl_fixup+172>:     mfctl tr3,r21
> 0x401ed468 <_dl_fixup+176>:     ldw -3e0(r21),ret0
> 0x401ed46c <_dl_fixup+180>:     cmpib,<> 0,ret0,0x401ed628 <_dl_fixup+624>
>
> and
>
> 0x401ed5fc <_dl_fixup+580>:     ldi 1,r24
> 0x401ed600 <_dl_fixup+584>:     ldi 0,r23
> 0x401ed604 <_dl_fixup+588>:     mfctl tr3,r26
> 0x401ed608 <_dl_fixup+592>:     copy r24,r25
> 0x401ed60c <_dl_fixup+596>:     ldo -3dc(r26),r26
> 0x401ed610 <_dl_fixup+600>:     copy r19,r4
> 0x401ed614 <_dl_fixup+604>:     be,l 100(sr2,r0),sr0,r31
> 0x401ed618 <_dl_fixup+608>:     ldi d2,r20
>
> So, the code is using the thread register (cr27).  Not sure what syscall
> this is.  However, the problem might be TLS releated.

The thread register has always been used to track thread specific
information, even in linuxthreads.

The syscall is __NR_futex.

If you can produce a synthetic testcase that calls __NR_futex and
crashes the kernel then we'll have something for the kernel hackers to
look at?

Cheers,
Carlos.

Re: 2.6.28-rcX in pretty bad shape on parisc

[John David Anglin]

> > So, the code is using the thread register (cr27).  Not sure what syscall
> > this is.  However, the problem might be TLS releated.
> 
> The thread register has always been used to track thread specific
> information, even in linuxthreads.
> 
> The syscall is __NR_futex.
> 
> If you can produce a synthetic testcase that calls __NR_futex and
> crashes the kernel then we'll have something for the kernel hackers to
> look at?

How long have futex's been used on hppa?  I guess we really need to try
run the glibc testsuite on a new kernel.

Dave
-- 
J. David Anglin                                  dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)

Re: 2.6.28-rcX in pretty bad shape on parisc

[Carlos O'Donell]

On Mon, Dec 8, 2008 at 9:54 AM, John David Anglin
<dave@hiauly1.hia.nrc.ca> wrote:
>> > So, the code is using the thread register (cr27).  Not sure what syscall
>> > this is.  However, the problem might be TLS releated.
>>
>> The thread register has always been used to track thread specific
>> information, even in linuxthreads.
>>
>> The syscall is __NR_futex.
>>
>> If you can produce a synthetic testcase that calls __NR_futex and
>> crashes the kernel then we'll have something for the kernel hackers to
>> look at?
>
> How long have futex's been used on hppa?  I guess we really need to try
> run the glibc testsuite on a new kernel.

The futex function has been available almost since futex's first appeared

The futex API is exported to userspace and can be used by any application.

e.g. man futex
~~~
NAME
       futex - Fast Userspace Locking system call

SYNOPSIS
       #include <linux/futex.h>
       #include <sys/time.h>

       int futex(int *uaddr, int op, int val, const struct timespec *timeout,
                 int *uaddr2, int val3);
~~~

Yes, the glibc testsuite is one of the best ways to exercise a lot of
kernel syscalls.

Cheers,
Carlos.

Re: 2.6.28-rcX in pretty bad shape on parisc

[John David Anglin]

> On Sun, Dec 07, 2008 at 11:50:02PM -0500, John David Anglin wrote:
> > > Given your earlier comments it would seen the segfault is not
> > > reproducible and happens often and randomly?
> > 
> > I gave 2.6.28-rc7-git5 a try this evening.  Hit the same error.
> > While its occurence may be random, the identical fault occurred
> > multiple times in a short period of testing.
> 
> I routinely get a segfault the first time I attempt to compile linux-2.6
> kernel after reboot.  If I "find linux-2.6 | xargs cksum", the kernel
> builds fine.

Actually, my first segfault with 2.6.28-rc7-git5 was in the initial boot
in mountnfs.  I rebooted and it didn't reoccur.  Again, this was a page
fault:

do_page_fault() pid=3502 command='mountnfs' type=15 address=0x00000364

     YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
PSW: 00000000000001001111111100001111 Tainted: G        W
r00-03  000000ff0004ff0f 00000000fb3a9ee8 0000000040213b5b 00000000000cf6a0
r04-07  0000000000000000 0000000000000360 00000000000e0c28 00000000000e08a8
...
IASQ: 0000000000621800 0000000000621800 IAOQ: 000000004020d40f 000000004020d413
 IIR: 0ca81095    ISR: 0000000000621800  IOR: 0000000000000364
 CPU:        1   CR30: 000000007e084000 CR31: ffffffffffffffff

dave@hiauly6:~/opt/gnu/bin$ disasm 0x0ca81095
   0:   0c a8 10 95     ldw 4(r5),r21

Sometimes I have the feeling that with 2.6.22.19) you get one segfault
and then it runs normally for a long time.

Dave
-- 
J. David Anglin                                  dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)

Re: 2.6.28-rcX in pretty bad shape on parisc

[John David Anglin]

> The prettiest way to do it would be to add a %p handler for
> resource_size_t args, cheat on the pointing bit, and clean up the
> in-tree users of %llx/ull-casts.

I went through the warnings that I saw yesterday implementing Helge's
%p suggestion.  It's not beautiful but it works.   I'll post tonight.

I only fixed the occurences that popped up in my build.  I'm sure that
more are lurking.

Feel free to implement %p handler.

I also fixed some other warnings and will post for comment when I separate
the diffs.

Dave
-- 
J. David Anglin                                  dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)

Re: 2.6.28-rcX in pretty bad shape on parisc

[John David Anglin]

> > How long have futex's been used on hppa?  I guess we really need to try
> > run the glibc testsuite on a new kernel.
> 
> The futex function has been available almost since futex's first appeared
> 
> The futex API is exported to userspace and can be used by any application.
> 
> e.g. man futex
> ~~~
> NAME
>        futex - Fast Userspace Locking system call

This is only supposition but a broken futex call might cause the type of
problems we are seeing.

Dave
-- 
J. David Anglin                                  dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)

Re: 2.6.28-rcX in pretty bad shape on parisc

[Kyle McMartin]

On Mon, Dec 08, 2008 at 10:23:28AM -0500, John David Anglin wrote:
> > The prettiest way to do it would be to add a %p handler for
> > resource_size_t args, cheat on the pointing bit, and clean up the
> > in-tree users of %llx/ull-casts.
> 
> I went through the warnings that I saw yesterday implementing Helge's
> %p suggestion.  It's not beautiful but it works.   I'll post tonight.
> 
> I only fixed the occurences that popped up in my build.  I'm sure that
> more are lurking.
> 
> Feel free to implement %p handler.
> 
> I also fixed some other warnings and will post for comment when I separate
> the diffs.
> 

sadly %p can't work, since void * doesn't hold resource_size_t with
CONFIG_RESOURCES_64BIT on 32-bit, since resource_size_t would be ULL,
which is why the %p handler would work (although you'd either have to
pass &(resource_size_t) or do a bit of ick around the va_args to snatch
the correct width instead of just void *).

but yeah, that's a global kernel issue, not limited to our little niche.

i'll apply your patch, and another one to make CONFIG_RESOURCES_64BIT
depend on !PARISC, since it really only applies to PAE on x86 and some
niche crap embeddeded powerpc.

cheers, kyle

Re: 2.6.28-rcX in pretty bad shape on parisc

[John David Anglin]

> sadly %p can't work, since void * doesn't hold resource_size_t with
> CONFIG_RESOURCES_64BIT on 32-bit, since resource_size_t would be ULL,
> which is why the %p handler would work (although you'd either have to
> pass &(resource_size_t) or do a bit of ick around the va_args to snatch
> the correct width instead of just void *).

Sigh, you are right.  However, all the warnings apply to addresses,
so I think the type for these addresses is wrong.  I can't really
imagine a 32-bit kernel running with a 64-bit address space would
be useful.

Dave
-- 
J. David Anglin                                  dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)

Re: 2.6.28-rcX in pretty bad shape on parisc

[Kyle McMartin]

On Mon, Dec 08, 2008 at 10:57:54AM -0500, John David Anglin wrote:
> > sadly %p can't work, since void * doesn't hold resource_size_t with
> > CONFIG_RESOURCES_64BIT on 32-bit, since resource_size_t would be ULL,
> > which is why the %p handler would work (although you'd either have to
> > pass &(resource_size_t) or do a bit of ick around the va_args to snatch
> > the correct width instead of just void *).
> 
> Sigh, you are right.  However, all the warnings apply to addresses,
> so I think the type for these addresses is wrong.  I can't really
> imagine a 32-bit kernel running with a 64-bit address space would
> be useful.
> 

Exactly, the config option (in the 64-bit on 32-bit sense) is limited in
utility to PAE on x86, where the physical address space is really
36-bit, (and they cheat by using double-sized ptes to cram in a 64-bit
address.) Last time I tried to submit a patch to make it automatic in
Kconfig it was met with resounding bikeshedding.

Re: 2.6.28-rcX in pretty bad shape on parisc

[Kyle McMartin]

On Mon, Dec 08, 2008 at 11:00:21AM -0500, Kyle McMartin wrote:
> On Mon, Dec 08, 2008 at 10:57:54AM -0500, John David Anglin wrote:
> > > sadly %p can't work, since void * doesn't hold resource_size_t with
> > > CONFIG_RESOURCES_64BIT on 32-bit, since resource_size_t would be ULL,
> > > which is why the %p handler would work (although you'd either have to
> > > pass &(resource_size_t) or do a bit of ick around the va_args to snatch
> > > the correct width instead of just void *).
> > 
> > Sigh, you are right.  However, all the warnings apply to addresses,
> > so I think the type for these addresses is wrong.  I can't really
> > imagine a 32-bit kernel running with a 64-bit address space would
> > be useful.
> > 
> 
> Exactly, the config option (in the 64-bit on 32-bit sense) is limited in
> utility to PAE on x86, where the physical address space is really
> 36-bit, (and they cheat by using double-sized ptes to cram in a 64-bit
> address.) Last time I tried to submit a patch to make it automatic in
> Kconfig it was met with resounding bikeshedding.
> 

To reiterate though, I'm not at all adverse to making this option just
go away on parisc32...

Re: 2.6.28-rcX in pretty bad shape on parisc

[Carlos O'Donell]

On Mon, Dec 8, 2008 at 10:02 AM, Carlos O'Donell
<carlos@systemhalted.org> wrote:
> On Mon, Dec 8, 2008 at 9:54 AM, John David Anglin
> <dave@hiauly1.hia.nrc.ca> wrote:
>>> > So, the code is using the thread register (cr27).  Not sure what syscall
>>> > this is.  However, the problem might be TLS releated.
>>>
>>> The thread register has always been used to track thread specific
>>> information, even in linuxthreads.
>>>
>>> The syscall is __NR_futex.
>>>
>>> If you can produce a synthetic testcase that calls __NR_futex and
>>> crashes the kernel then we'll have something for the kernel hackers to
>>> look at?
>>
>> How long have futex's been used on hppa?  I guess we really need to try
>> run the glibc testsuite on a new kernel.
>
> The futex function has been available almost since futex's first appeared

I realized I didn't answer your question here.

The futex function should only be called when compiling glibc with nptl enabled.

Otherwise nothing in glibc should make futex calls.

Broken futex calls shouldn't crash the kernel.

Cheers,
Carlos.

Re: 2.6.28-rcX in pretty bad shape on parisc

[John David Anglin]

> >> How long have futex's been used on hppa?  I guess we really need to try
> >> run the glibc testsuite on a new kernel.
> >
> > The futex function has been available almost since futex's first appeared
> 
> I realized I didn't answer your question here.
> 
> The futex function should only be called when compiling glibc with nptl enabled.
> 
> Otherwise nothing in glibc should make futex calls.
> 
> Broken futex calls shouldn't crash the kernel.

The kernel doesn't crash since Helge's stack backtrace fix.  We are
just getting a lot of segfaults in application code.

I'm fairly certain libc6 in debian testing is still built with linuxthreads.
I'm not sure libc is actually making futex calls, but one is compiled
into _dl_fixup.  I suppose I could add a printk in the kernel to see
if futex's are being used.

I'm currently building debian libc6.  In a quick attempt, I wasn't
successful in building the glibc cvs source.  It pushes hard to get
you to configure with nptl.  My build with linuxthreads failed with
a type size problem.

I'll try the testsuite with this build on my current kernel.  If that
works, I'll flip to 2.6.28.

Dave
-- 
J. David Anglin                                  dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)

Re: 2.6.28-rcX in pretty bad shape on parisc

[Carlos O'Donell]

On Mon, Dec 8, 2008 at 5:39 PM, John David Anglin
<dave@hiauly1.hia.nrc.ca> wrote:
>> Otherwise nothing in glibc should make futex calls.
>>
>> Broken futex calls shouldn't crash the kernel.
>
> The kernel doesn't crash since Helge's stack backtrace fix.  We are
> just getting a lot of segfaults in application code.

Excellent. That is certainly progress.

> I'm fairly certain libc6 in debian testing is still built with linuxthreads.
> I'm not sure libc is actually making futex calls, but one is compiled
> into _dl_fixup.  I suppose I could add a printk in the kernel to see
> if futex's are being used.

Yes, your assembly dump shows a futex syscall in _dl_fixup, and AFAIK
there should not be one there.

I used printk *very* effectively in the kernel/futex.c code to debug
futex issues with the NPTL bringup.

Remember that the futex is essentially the address of the userspace
object, so it's rather easy to trace.

> I'm currently building debian libc6.  In a quick attempt, I wasn't
> successful in building the glibc cvs source.  It pushes hard to get
> you to configure with nptl.  My build with linuxthreads failed with
> a type size problem.
>
> I'll try the testsuite with this build on my current kernel.  If that
> works, I'll flip to 2.6.28.

Thanks, please keep me posted.

Cheers,
Carlos.

resource_size_t printk woes...

[Kyle McMartin]

On Mon, Dec 08, 2008 at 11:00:51AM -0500, Kyle McMartin wrote:
>

Something like this was what I had in mind... seems to (x)compile,
haven't actually run-time tested it. Kills the warnings, at least. ;-)

Needs some more thinking before I might hit upstream with it.

diff --git a/drivers/parisc/ccio-dma.c b/drivers/parisc/ccio-dma.c
index dcc1e99..ccb7858 100644
--- a/drivers/parisc/ccio-dma.c
+++ b/drivers/parisc/ccio-dma.c
@@ -1551,7 +1551,7 @@ static int __init ccio_probe(struct parisc_device *dev)
 
 	ioc->name = dev->id.hversion == U2_IOA_RUNWAY ? "U2" : "UTurn";
 
-	printk(KERN_INFO "Found %s at 0x%lx\n", ioc->name, dev->hpa.start);
+	printk(KERN_INFO "Found %s at %pZ\n", ioc->name, &(dev->hpa.start));
 
 	for (i = 0; i < ioc_count; i++) {
 		ioc_p = &(*ioc_p)->next;
diff --git a/drivers/parisc/lba_pci.c b/drivers/parisc/lba_pci.c
index a28c894..0221545 100644
--- a/drivers/parisc/lba_pci.c
+++ b/drivers/parisc/lba_pci.c
@@ -1413,8 +1413,8 @@ lba_driver_probe(struct parisc_device *dev)
 		default: version = "TR4+";
 		}
 
-		printk(KERN_INFO "Elroy version %s (0x%x) found at 0x%lx\n",
-		       version, func_class & 0xf, (long)dev->hpa.start);
+		printk(KERN_INFO "Elroy version %s (0x%x) found at %pZ\n",
+		       version, func_class & 0xf, &(dev->hpa.start));
 
 		if (func_class < 2) {
 			printk(KERN_WARNING "Can't support LBA older than "
@@ -1442,14 +1442,14 @@ lba_driver_probe(struct parisc_device *dev)
 		/* We could use one printk for both Elroy and Mercury,
                  * but for the mask for func_class.
                  */ 
-		printk(KERN_INFO "%s version TR%d.%d (0x%x) found at 0x%lx\n",
+		printk(KERN_INFO "%s version TR%d.%d (0x%x) found at %pZ\n",
 		       IS_MERCURY(dev) ? "Mercury" : "Quicksilver", major,
-		       minor, func_class, (long)dev->hpa.start);
+		       minor, func_class, &(dev->hpa.start));
 
 		cfg_ops = &mercury_cfg_ops;
 	} else {
-		printk(KERN_ERR "Unknown LBA found at 0x%lx\n",
-			(long)dev->hpa.start);
+		printk(KERN_ERR "Unknown LBA found at %pZ\n",
+			&(dev->hpa.start));
 		return -ENODEV;
 	}
 
diff --git a/drivers/parisc/sba_iommu.c b/drivers/parisc/sba_iommu.c
index bc73b96..4ad4d52 100644
--- a/drivers/parisc/sba_iommu.c
+++ b/drivers/parisc/sba_iommu.c
@@ -1938,8 +1938,8 @@ sba_driver_callback(struct parisc_device *dev)
 			global_ioc_cnt *= 2;
 	}
 
-	printk(KERN_INFO "%s found %s at 0x%llx\n",
-		MODULE_NAME, version, (unsigned long long)dev->hpa.start);
+	printk(KERN_INFO "%s found %s at %pZ\n",
+		MODULE_NAME, version, &(dev->hpa.start));
 
 	sba_dev = kzalloc(sizeof(struct sba_device), GFP_KERNEL);
 	if (!sba_dev) {
diff --git a/lib/vsprintf.c b/lib/vsprintf.c
index a013bbc..342496f 100644
--- a/lib/vsprintf.c
+++ b/lib/vsprintf.c
@@ -607,6 +607,12 @@ static char *pointer(const char *fmt, char *buf, char *end, void *ptr, int field
 		return symbol_string(buf, end, ptr, field_width, precision, flags);
 	case 'R':
 		return resource_string(buf, end, ptr, field_width, precision, flags);
+	case 'Z':
+		{
+			resource_size_t rsz = *((resource_size_t *)ptr);
+			return number(buf, end, (unsigned long long)rsz, 16,
+				field_width, -1, SPECIAL | SMALL | ZEROPAD);
+		}
 	}
 	flags |= SMALL;
 	if (field_width == -1) {

Re: 2.6.28-rcX in pretty bad shape on parisc

[Kyle McMartin]

On Mon, Dec 08, 2008 at 12:50:01AM -0700, Grant Grundler wrote:
> > So, the code is using the thread register (cr27).  Not sure what syscall
> > this is.  However, the problem might be TLS releated.
> 
> I have no idea if TLS makes a difference to kernel builds.
> 

I don't think Debian is using NPTL yet due to $issues previously
discussed...

linuxthreads being broken in newer glibc sounds unsuprisingly though.

regards, Kyle

Re: resource_size_t printk woes...

[John David Anglin]

> On Mon, Dec 08, 2008 at 11:00:51AM -0500, Kyle McMartin wrote:

> diff --git a/lib/vsprintf.c b/lib/vsprintf.c
> index a013bbc..342496f 100644
> --- a/lib/vsprintf.c
> +++ b/lib/vsprintf.c
> @@ -607,6 +607,12 @@ static char *pointer(const char *fmt, char *buf, char *end, void *ptr, int field
>  		return symbol_string(buf, end, ptr, field_width, precision, flags);
>  	case 'R':
>  		return resource_string(buf, end, ptr, field_width, precision, flags);

Hmmm, what's this?  It appears this provides a model for printing just
the start value.  The size of the character array depends on the sizeof
resource_size_t.  There's also a flag dependence.

Attached below is the change that I had.  Think this includes some
additional locations to update.

Dave
-- 
J. David Anglin                                  dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)

diff -upr a/drivers/input/keyboard/hilkbd.c b/drivers/input/keyboard/hilkbd.c
--- a/drivers/input/keyboard/hilkbd.c	2008-12-01 22:59:23.000000000 -0500
+++ b/drivers/input/keyboard/hilkbd.c	2008-12-07 17:10:53.000000000 -0500
@@ -314,7 +314,7 @@ static int __init
 hil_init_chip(struct parisc_device *dev)
 {
 	if (!dev->irq) {
-		printk(KERN_WARNING "HIL: IRQ not found for HIL bus at 0x%08lx\n", dev->hpa.start);
+		printk(KERN_WARNING "HIL: IRQ not found for HIL bus at 0x%p\n", (void *)dev->hpa.start);
 		return -ENODEV;
 	}
 
diff -upr a/drivers/net/lasi_82596.c b/drivers/net/lasi_82596.c
--- a/drivers/net/lasi_82596.c	2008-12-01 22:59:23.000000000 -0500
+++ b/drivers/net/lasi_82596.c	2008-12-07 17:13:51.000000000 -0500
@@ -160,13 +160,13 @@ lan_init_chip(struct parisc_device *dev)
 	int i;
 
 	if (!dev->irq) {
-		printk(KERN_ERR "%s: IRQ not found for i82596 at 0x%lx\n",
-			__FILE__, dev->hpa.start);
+		printk(KERN_ERR "%s: IRQ not found for i82596 at 0x%p\n",
+			__FILE__, (void *)dev->hpa.start);
 		return -ENODEV;
 	}
 
-	printk(KERN_INFO "Found i82596 at 0x%lx, IRQ %d\n", dev->hpa.start,
-			dev->irq);
+	printk(KERN_INFO "Found i82596 at 0x%p, IRQ %d\n",
+		(void *)dev->hpa.start, dev->irq);
 
 	netdevice = alloc_etherdev(sizeof(struct i596_private));
 	if (!netdevice)
diff -upr a/drivers/parisc/asp.c b/drivers/parisc/asp.c
--- a/drivers/parisc/asp.c	2008-12-01 22:59:23.000000000 -0500
+++ b/drivers/parisc/asp.c	2008-12-07 17:22:30.000000000 -0500
@@ -81,8 +81,8 @@ asp_init_chip(struct parisc_device *dev)
 	asp.name = (asp.version == 1) ? "Asp" : "Cutoff";
 	asp.hpa = ASP_INTERRUPT_ADDR;
 
-	printk(KERN_INFO "%s version %d at 0x%lx found.\n", 
-		asp.name, asp.version, dev->hpa.start);
+	printk(KERN_INFO "%s version %d at 0x%p found.\n", 
+		asp.name, asp.version, (void *)dev->hpa.start);
 
 	/* the IRQ ASP should use */
 	ret = -EBUSY;
diff -upr a/drivers/parisc/ccio-dma.c b/drivers/parisc/ccio-dma.c
--- a/drivers/parisc/ccio-dma.c	2008-12-01 22:59:23.000000000 -0500
+++ b/drivers/parisc/ccio-dma.c	2008-12-07 19:13:51.000000000 -0500
@@ -1399,8 +1401,8 @@ ccio_init_resource(struct resource *res,
 	 */
 	result = insert_resource(&iomem_resource, res);
 	if (result < 0) {
-		printk(KERN_ERR "%s() failed to claim CCIO bus address space (%08lx,%08lx)\n", 
-			__func__, res->start, res->end);
+		printk(KERN_ERR "%s() failed to claim CCIO bus address space (0x%p,0x%p)\n", 
+			__func__, (void *)res->start, (void *)res->end);
 	}
 }
 
@@ -1551,7 +1553,8 @@ static int __init ccio_probe(struct pari
 
 	ioc->name = dev->id.hversion == U2_IOA_RUNWAY ? "U2" : "UTurn";
 
-	printk(KERN_INFO "Found %s at 0x%lx\n", ioc->name, dev->hpa.start);
+	printk(KERN_INFO "Found %s at 0x%p\n", ioc->name,
+		(void *)dev->hpa.start);
 
 	for (i = 0; i < ioc_count; i++) {
 		ioc_p = &(*ioc_p)->next;
diff -upr a/drivers/parisc/dino.c b/drivers/parisc/dino.c
--- a/drivers/parisc/dino.c	2008-12-01 22:59:23.000000000 -0500
+++ b/drivers/parisc/dino.c	2008-12-07 19:31:24.000000000 -0500
@@ -819,7 +821,7 @@ dino_bridge_init(struct dino_device *din
 
 		result = ccio_request_resource(dino_dev->hba.dev, &res[i]);
 		if (result < 0) {
-			printk(KERN_ERR "%s: failed to claim PCI Bus address space %d (0x%lx-0x%lx)!\n", name, i, res[i].start, res[i].end);
+			printk(KERN_ERR "%s: failed to claim PCI Bus address space %d (0x%p-0x%p)!\n", name, i, (void *)res[i].start, (void *)res[i].end);
 			return result;
 		}
 	}
@@ -898,8 +900,9 @@ static int __init dino_common_init(struc
 	res->flags = IORESOURCE_IO; /* do not mark it busy ! */
 	if (request_resource(&ioport_resource, res) < 0) {
 		printk(KERN_ERR "%s: request I/O Port region failed "
-		       "0x%lx/%lx (hpa 0x%p)\n",
-		       name, res->start, res->end, dino_dev->hba.base_addr);
+		       "0x%p/%p (hpa 0x%p)\n",
+		       name, (void *)res->start, (void *)res->end,
+		       dino_dev->hba.base_addr);
 		return 1;
 	}
 
diff -upr a/drivers/parisc/hppb.c b/drivers/parisc/hppb.c
--- a/drivers/parisc/hppb.c	2008-12-01 22:59:23.000000000 -0500
+++ b/drivers/parisc/hppb.c	2008-12-07 17:19:14.000000000 -0500
@@ -62,7 +62,7 @@ static int hppb_probe(struct parisc_devi
 		}
 		card = card->next;
 	}
-        printk(KERN_INFO "Found GeckoBoa at 0x%x\n", dev->hpa.start);
+        printk(KERN_INFO "Found GeckoBoa at 0x%p\n", (void *)dev->hpa.start);
 
 	card->hpa = dev->hpa.start;
 	card->mmio_region.name = "HP-PB Bus";
@@ -73,8 +73,10 @@ static int hppb_probe(struct parisc_devi
 
 	status = ccio_request_resource(dev, &card->mmio_region);
 	if(status < 0) {
-		printk(KERN_ERR "%s: failed to claim HP-PB bus space (%08x, %08x)\n",
-			__FILE__, card->mmio_region.start, card->mmio_region.end);
+		printk(KERN_ERR "%s: failed to claim HP-PB bus space (0x%p, 0x%p)\n",
+			__FILE__,
+			(void *)card->mmio_region.start,
+			(void *)card->mmio_region.end);
 	}
 
         return 0;
diff -upr a/drivers/parport/parport_gsc.c b/drivers/parport/parport_gsc.c
--- a/drivers/parport/parport_gsc.c	2008-12-01 22:59:23.000000000 -0500
+++ b/drivers/parport/parport_gsc.c	2008-12-07 17:23:13.000000000 -0500
@@ -352,8 +352,8 @@ static int __devinit parport_init_chip(s
 	unsigned long port;
 
 	if (!dev->irq) {
-		printk(KERN_WARNING "IRQ not found for parallel device at 0x%lx\n",
-			dev->hpa.start);
+		printk(KERN_WARNING "IRQ not found for parallel device at 0x%p\n",
+			(void *)dev->hpa.start);
 		return -ENODEV;
 	}
 
diff -upr a/drivers/serial/8250_gsc.c b/drivers/serial/8250_gsc.c
--- a/drivers/serial/8250_gsc.c	2008-12-01 22:59:23.000000000 -0500
+++ b/drivers/serial/8250_gsc.c	2008-12-07 17:24:15.000000000 -0500
@@ -39,9 +39,9 @@ static int __init serial_init_chip(struc
 		 */
 		if (parisc_parent(dev)->id.hw_type != HPHW_IOA)
 			printk(KERN_INFO
-				"Serial: device 0x%lx not configured.\n"
+				"Serial: device 0x%p not configured.\n"
 				"Enable support for Wax, Lasi, Asp or Dino.\n",
-				dev->hpa.start);
+				(void *)dev->hpa.start);
 		return -ENODEV;
 	}
 
diff -upr a/sound/parisc/harmony.c b/sound/parisc/harmony.c
--- a/sound/parisc/harmony.c	2008-12-01 22:59:23.000000000 -0500
+++ b/sound/parisc/harmony.c	2008-12-07 17:24:55.000000000 -0500
@@ -934,8 +934,8 @@ snd_harmony_create(struct snd_card *card
 	h->irq = -1;
 	h->iobase = ioremap_nocache(padev->hpa.start, HARMONY_SIZE);
 	if (h->iobase == NULL) {
-		printk(KERN_ERR PFX "unable to remap hpa 0x%lx\n",
-		       padev->hpa.start);
+		printk(KERN_ERR PFX "unable to remap hpa 0x%p\n",
+		       (void *)padev->hpa.start);
 		err = -EBUSY;
 		goto free_and_ret;
 	}

Re: resource_size_t printk woes...

[Helge Deller]

John David Anglin wrote:
>> On Mon, Dec 08, 2008 at 11:00:51AM -0500, Kyle McMartin wrote:
> Attached below is the change that I had.  Think this includes some
> additional locations to update.

Kyle,
in case you plan to include this patch from Dave in your linux-2.6 tree,
please DON'T INCLUDE this change to the "hilkbd.c" file:
  a/drivers/input/keyboard/hilkbd.c   2008-12-01 22:59:23.000000000 -0500
	-               printk(KERN_WARNING "HIL: IRQ not found for HIL bus at 0x%08lx\n", dev->hpa.start);
	+               printk(KERN_WARNING "HIL: IRQ not found for HIL bus at 0x%p\n", (void *)dev->hpa.start);

Reason:
I've sent another patch for hilkbd.c to the linux-input mailing list, 
which already includes this change (and I had forgotten about Dave's posting):
[PATCH] input/keyboard/hilkbd.c: fix crash when removing hilkbd module 
         http://permalink.gmane.org/gmane.linux.kernel.input/6266 
If you apply Dave's hilkbd changes, it may conflict if Linus pulls your parisc tree.
All other changes from Dave are OK.

Helge

PS: For the record, this are the other patches which I sent to linux-input:
[PATCH] input/HIL drivers: add MODULE_ALIAS() 
         http://permalink.gmane.org/gmane.linux.kernel.input/6267 
 
[PATCH] drivers/input/serio/hp_sdc.c: fix crash when removing hp_sdc module 
         http://permalink.gmane.org/gmane.linux.kernel.input/6268 

Re: resource_size_t printk woes...

[John David Anglin]

Hi Helge,

I just want to say that I like Kyle's approach.  There already exists
the 'R' modifier for %p.  This outputs a pair of resource_size_t values.
We just need a modifier to handle the printing of the start value in
a manner similar to that for the 'R' modifier.  So, I think this issue
needs another go around.

Dave
-- 
J. David Anglin                                  dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)

Re: resource_size_t printk woes...

[Helge Deller]

John David Anglin wrote:
> Hi Helge,
> 
> I just want to say that I like Kyle's approach.  There already exists
> the 'R' modifier for %p.  This outputs a pair of resource_size_t values.
> We just need a modifier to handle the printing of the start value in
> a manner similar to that for the 'R' modifier.  So, I think this issue
> needs another go around.

Sadly none of the approaches is really nice, as with Kyle's approach we'd
loose the type-checking of printk.
But yes, maybe that's the best choice of all bad ones.
Will you try/come up with a patch to vsprintf.c?

Helge

Re: resource_size_t printk woes...

[John David Anglin]

> John David Anglin wrote:
> > Hi Helge,
> > 
> > I just want to say that I like Kyle's approach.  There already exists
> > the 'R' modifier for %p.  This outputs a pair of resource_size_t values.
> > We just need a modifier to handle the printing of the start value in
> > a manner similar to that for the 'R' modifier.  So, I think this issue
> > needs another go around.
> 
> Sadly none of the approaches is really nice, as with Kyle's approach we'd
> loose the type-checking of printk.
> But yes, maybe that's the best choice of all bad ones.
> Will you try/come up with a patch to vsprintf.c?

I was think of something like this (untested):

diff --git a/lib/vsprintf.c b/lib/vsprintf.c
index a013bbc..3c47705 100644
--- a/lib/vsprintf.c
+++ b/lib/vsprintf.c
@@ -551,8 +551,6 @@ static char *symbol_string(char *buf, char *end, void *ptr, int field_width, int
 #endif
 }
 
-static char *resource_string(char *buf, char *end, struct resource *res, int field_width, int precision, int flags)
-{
 #ifndef IO_RSRC_PRINTK_SIZE
 #define IO_RSRC_PRINTK_SIZE	4
 #endif
@@ -561,6 +559,8 @@ static char *resource_string(char *buf, char *end, struct resource *res, int fie
 #define MEM_RSRC_PRINTK_SIZE	8
 #endif
 
+static char *resource_string(char *buf, char *end, struct resource *res, int field_width, int precision, int flags)
+{
 	/* room for the actual numbers, the two "0x", -, [, ] and the final zero */
 	char sym[4*sizeof(resource_size_t) + 8];
 	char *p = sym, *pend = sym + sizeof(sym);
@@ -581,6 +581,24 @@ static char *resource_string(char *buf, char *end, struct resource *res, int fie
 	return string(buf, end, sym, field_width, precision, flags);
 }
 
+static char *resource_start_string(char *buf, char *end, struct resource *res, int field_width, int precision, int flags)
+{
+	/* room for the number, the "0x", and the final zero */
+	char sym[2*sizeof(resource_size_t) + 3];
+	char *p = sym, *pend = sym + sizeof(sym);
+	int size = -1;
+
+	if (res->flags & IORESOURCE_IO)
+		size = IO_RSRC_PRINTK_SIZE;
+	else if (res->flags & IORESOURCE_MEM)
+		size = MEM_RSRC_PRINTK_SIZE;
+
+	p = number(p, pend, res->start, 16, size, -1, SPECIAL | SMALL | ZEROPAD);
+	*p = 0;
+
+	return string(buf, end, sym, field_width, precision, flags);
+}
+
 /*
  * Show a '%p' thing.  A kernel extension is that the '%p' is followed
  * by an extra set of alphanumeric characters that are extended format
@@ -592,6 +610,7 @@ static char *resource_string(char *buf, char *end, struct resource *res, int fie
  * - 'S' For symbolic direct pointers
  * - 'R' For a struct resource pointer, it prints the range of
  *       addresses (not the name nor the flags)
+ * - 'Z' For a struct resource pointer, it prints the start address
  *
  * Note: The difference between 'S' and 'F' is that on ia64 and ppc64
  * function pointers are really function descriptors, which contain a
@@ -607,6 +626,8 @@ static char *pointer(const char *fmt, char *buf, char *end, void *ptr, int field
 		return symbol_string(buf, end, ptr, field_width, precision, flags);
 	case 'R':
 		return resource_string(buf, end, ptr, field_width, precision, flags);
+	case 'Z':
+		return resource_start_string(buf, end, ptr, field_width, precision, flags);
 	}
 	flags |= SMALL;
 	if (field_width == -1) {

So, one would just pass the resource pointer.  This has the advantage that
it handles 4 and 8 hex digits when appropriate.  However, it is limited to
just printing the start address.  In most cases, that's all that is done.

The 'R' modifier can be used to print both the start and end values.  There
are a few cases where a range is printed.

Dave
-- 
J. David Anglin                                  dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)

Re: resource_size_t printk woes...

[John David Anglin]

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

On Thu, 01 Jan 2009, John David Anglin wrote:

> I was think of something like this (untested):

While trying to test this, I hit the following with Kyle's 2.6.28-rc7
parisc tree:

Debian GNU/Linux 5.0 mx3210 ttyS1

mx3210 login: Backtrace:
 [<000000004014240c>] dequeue_entity+0x34/0x190
 [<0000000040144154>] __set_se_shares+0x74/0xb8
 [<0000000040146674>] tg_shares_up+0x214/0x2c0
 [<000000004013e254>] walk_tg_tree+0xac/0x110
 [<0000000040148ea8>] update_shares+0x78/0x90
 [<0000000040149198>] try_to_wake_up+0x2d8/0x2e0
 [<0000000040149234>] wake_up_process+0x24/0x38
 [<000000004018962c>] softlockup_tick+0x234/0x250
 [<000000004015fe68>] run_local_timers+0x38/0x48
 [<000000004015ff48>] update_process_times+0x50/0xc8
 [<000000004011d208>] timer_interrupt+0x208/0x210
 [<0000000040189f30>] handle_IRQ_event+0x70/0xd0
 [<000000004018a05c>] __do_IRQ+0xcc/0x280
 [<000000004011d8d0>] do_cpu_irq_mask+0x1a8/0x298
 [<0000000040104074>] intr_return+0x0/0x4
 [<000000004011d208>] timer_interrupt+0x208/0x210


Bad Address (null pointer deref?): Code=15 regs=000000007f54dc30 (Addr=c000000053c33ffd)

     YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
PSW: 00001000000001100000000000001110 Tainted: G        W 
r00-03  000000000806000e 000000007f54daf0 000000004014240c 000000007f54db90
r04-07  00000000405b86a0 e840d00053c33f8d e840d00053c33f8d e840d00053c33f8d
r08-11  0000000000000010 0000000000000002 000000007f54da20 000000007ed15178
r12-15  0000000000001000 0000000000000400 0000000000000400 0000000000000001
r16-19  000000004276c1d0 00000000405baea0 0000000000001001 000000007fb1f740
r20-23  0000000000000000 0000000080080000 0000000000000000 0000000000000000
r24-27  0000000000000000 000000004013e254 e840d00053c33f8d 00000000405b86a0
r28-31  00000000081b0244 000000007f54db60 000000007f54dc30 000000007fb1f740
sr00-03  0000000003840000 0000000000000000 0000000000000000 0000000003840000
sr04-07  0000000000000000 0000000000000000 0000000000000000 0000000000000000

IASQ: 0000000000000000 0000000000000000 IAOQ: 000000004013e550 000000004013e554
 IIR: 535c00e0    ISR: 000000002840d000  IOR: c000000053c33ffd
 CPU:        2   CR30: 000000007f524000 CR31: 0000000040554000
ORIG_R28: d84156c5635688c0
IAOQ[0]: update_curr+0x28/0x150
IAOQ[1]: update_curr+0x2c/0x150
RP(r2): dequeue_entity+0x34/0x190

000000004013e528 <update_curr>:
    4013e528:   08 03 02 41     copy r3,r1
    4013e52c:   0f c2 12 c1     std rp,-10(sp)
    4013e530:   08 1e 02 43     copy sp,r3
    4013e534:   73 c1 01 48     std,ma r1,a0(sp)
    4013e538:   70 66 00 30     std r6,18(r3)
    4013e53c:   08 1a 02 46     copy r26,r6
    4013e540:   0c 68 12 d0     std r8,8(r3)
    4013e544:   70 67 00 20     std r7,10(r3)
    4013e548:   70 65 00 40     std r5,20(r3)
    4013e54c:   70 64 00 50     std r4,28(r3)
    4013e550:   53 5c 00 e0     ldd 70(r26),ret0

Not sure what's going on with r26.

Config attached.

Dave
-- 
J. David Anglin                                  dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)

[-- Attachment #2: config-mx3210.gz --]
[-- Type: application/x-gunzip, Size: 11059 bytes --]

Re: resource_size_t printk woes...

[John David Anglin]

> On Thu, 01 Jan 2009, John David Anglin wrote:
> 
> > I was think of something like this (untested):
> 
> While trying to test this, I hit the following with Kyle's 2.6.28-rc7
> parisc tree:
> 
> Debian GNU/Linux 5.0 mx3210 ttyS1

And other one:

mx3210 login: Slab corruption: names_cache start=000000007cc71000, len=4096
000: 00 00 00 00 7f 45 cb c0 00 00 00 00 40 5b 86 a0
010: 00 00 00 00 00 00 00 02 00 00 00 00 7f 41 0d 00
020: 00 00 00 00 7f 48 01 18 00 00 00 00 00 00 00 01
030: 00 00 00 00 7f 45 b2 88 00 00 00 00 40 5e f8 a0
040: 00 00 00 00 00 10 36 64 00 00 00 00 00 00 00 00
050: 00 00 00 00 00 00 00 00 00 00 00 00 00 22 34 e4
Slab corruption: biovec-128 start=000000007cc7a308, len=2048
Redzone: 0x0/0x1812c.
Last user: [<000000007cc7a750>](0x7cc7a750)
000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
010: 00 00 00 00 00 00 00 00 00 00 00 00 40 10 40 78
020: 00 00 00 00 40 10 40 7c 00 00 00 00 40 4f bb 00
030: 00 00 00 00 42 76 81 e0 00 00 00 00 42 76 70 40
040: 00 00 00 00 40 5b 86 a0 6b 6b 6b 6b 6b 6b 6b 6b
050: 00 00 00 00 00 00 00 00 00 00 00 00 03 c0 08 a1
Prev obj: start=000000007cc798d0, len=2048
Redzone: 0x0/0xff0804ff0f.
Last user: [<00000000405bcea0>](0x405bcea0)
000: 00 00 00 00 00 00 00 00 00 00 00 00 00 22 34 e4
010: 41 2e 84 80 00 00 00 00 00 00 00 00 00 1e 84 80
slab error in cache_alloc_debugcheck_after(): cache `biovec-128': double free, or memory outside object was overwritten
Backtrace:
 [<000000004011bd1c>] show_stack+0x14/0x20
 [<00000000401144f0>] dump_stack+0x18/0x28
 [<00000000401c65dc>] __slab_error+0x3c/0x48
 [<00000000401c6db0>] cache_alloc_debugcheck_after+0x190/0x308
 [<00000000401c91d8>] kmem_cache_alloc+0xd8/0x190
 [<000000004019552c>] mempool_alloc_slab+0x1c/0x28
 [<0000000040195720>] mempool_alloc+0x88/0x1b8
 [<00000000402039e0>] bvec_alloc_bs+0x88/0x138
 [<0000000040203b14>] bio_alloc_bioset+0x84/0x140
 [<0000000040203cf0>] bio_alloc+0x20/0x50
 [<00000000402086e4>] mpage_alloc+0x44/0xd0
 [<0000000040208c8c>] __mpage_writepage+0x41c/0x788
 [<000000004019c7ec>] write_cache_pages+0x33c/0x438
 [<0000000040208808>] mpage_writepages+0x48/0xb0
 [<00000000142ca3a4>] ext2_writepages+0x1c/0x28 [ext2]
 [<000000004019c974>] do_writepages+0x44/0x78

000000007cc7a300: redzone 1:0x0, redzone 2:0x1812c
------------[ cut here ]------------
kernel BUG at mm/slab.c:2895!

     YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
PSW: 00001000000001001111111100001110 Tainted: G        W 
r00-03  000000ff0804ff0e 00000000405baea0 00000000401c6b0c 000000007cc7a300
r04-07  00000000405b86a0 0000000000000000 000000007ed64740 d84156c5635688c0
r08-11  00000000404063c0 000000007cc7a2c0 00000000401955ac 00000000405c2ea0
r12-15  00000000405c0ea0 0000000040574f50 0000000000000000 000000004050bb80
r16-19  00000000405ba6a0 0000000000000000 00000000ffffffff 00000000000f6ab4
r20-23  000000006d207700 00000000001fa11d 00000000000f1c19 0000000066957700
r24-27  00000000401955ac 00000000001fa11d 000000007cc7a300 00000000405b86a0
r28-31  00000000000f6ab4 0000000040575500 0000000040575530 0000000000000003
sr00-03  00000000006c9800 0000000000000000 0000000000000000 00000000006c9800
sr04-07  0000000000000000 0000000000000000 0000000000000000 0000000000000000

IASQ: 0000000000000000 0000000000000000 IAOQ: 00000000401c6bb8 00000000401c6bbc
 IIR: 03ffe01f    ISR: 0000000010340000  IOR: 000000015d575538
 CPU:        0   CR30: 0000000040574000 CR31: 0000000040554000
ORIG_R28: 000000004058f6a0
IAOQ[0]: cache_free_debugcheck+0x360/0x3c8
IAOQ[1]: cache_free_debugcheck+0x364/0x3c8
RP(r2): cache_free_debugcheck+0x2b4/0x3c8
Backtrace:
 [<00000000401c733c>] kmem_cache_free+0x4c/0x150
 [<00000000401955ac>] mempool_free_slab+0x1c/0x28
 [<0000000040195690>] mempool_free+0xd8/0xe0
 [<0000000040204a30>] bio_free+0x40/0x90
 [<0000000040204a9c>] bio_fs_destructor+0x1c/0x28
 [<00000000402023f8>] bio_put+0x88/0xa0
 [<0000000040209b64>] mpage_end_io_write+0xcc/0x138
 [<00000000402024e0>] bio_endio+0x70/0x90
 [<000000004025bd60>] req_bio_endio+0xf8/0x158
 [<000000004025befc>] __end_that_request_first+0x13c/0x3f8
 [<000000004025c1f4>] end_that_request_data+0x3c/0xa8
 [<000000004025d058>] blk_end_io+0x38/0xf8
 [<000000004025d178>] blk_end_request+0x18/0x28
 [<00000000081183e4>] scsi_end_request+0x4c/0x110 [scsi_mod]
 [<0000000008118c8c>] scsi_io_completion+0x12c/0x538 [scsi_mod]
 [<000000000810ed44>] scsi_finish_command+0xd4/0x148 [scsi_mod]

Backtrace:
 [<000000004011bd1c>] show_stack+0x14/0x20
 [<00000000401144f0>] dump_stack+0x18/0x28
 [<000000004011c508>] die_if_kernel+0x138/0x240
 [<000000004011ce88>] handle_interruption+0x878/0x910
 [<00000000401c6bb8>] cache_free_debugcheck+0x360/0x3c8
 [<00000000401c733c>] kmem_cache_free+0x4c/0x150
 [<00000000401955ac>] mempool_free_slab+0x1c/0x28
 [<0000000040195690>] mempool_free+0xd8/0xe0
 [<0000000040204a30>] bio_free+0x40/0x90
 [<0000000040204a9c>] bio_fs_destructor+0x1c/0x28
 [<00000000402023f8>] bio_put+0x88/0xa0
 [<0000000040209b64>] mpage_end_io_write+0xcc/0x138
 [<00000000402024e0>] bio_endio+0x70/0x90
 [<000000004025bd60>] req_bio_endio+0xf8/0x158
 [<000000004025befc>] __end_that_request_first+0x13c/0x3f8
 [<000000004025c1f4>] end_that_request_data+0x3c/0xa8

Dave
-- 
J. David Anglin                                  dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)

Re: resource_size_t printk woes...

[Helge Deller]

John David Anglin wrote:
>> On Thu, 01 Jan 2009, John David Anglin wrote:
>>
>>> I was think of something like this (untested):
>> While trying to test this, I hit the following with Kyle's 2.6.28-rc7
>> parisc tree:
>>
>> Debian GNU/Linux 5.0 mx3210 ttyS1
> 
> And other one:
> 
> mx3210 login: Slab corruption: names_cache start=000000007cc71000, len=4096
> 000: 00 00 00 00 7f 45 cb c0 00 00 00 00 40 5b 86 a0

Hi Dave,

telling you to try vanilla 2.6.28 was a stupid idea.
I forgot that I had exactly the same problem (slab corruption):
http://bugzilla.kernel.org/show_bug.cgi?id=11913
when I started the thread 
"2.6.28-rcX in pretty bad shape on parisc"
here on the list as well.

The solution for me was to use another default config.
James posted this one, which started to get everything working for me:
http://parisc-linux.org/~jejb/config-2.6.28-rc5-ion
Try this one instead (e.g. with Kyle's tree).

I assume something in your .config is different than what is in
James' .config. It would be interesting to know what it
is. I didn't checked further at that time.

Helge

> 010: 00 00 00 00 00 00 00 02 00 00 00 00 7f 41 0d 00
> 020: 00 00 00 00 7f 48 01 18 00 00 00 00 00 00 00 01
> 030: 00 00 00 00 7f 45 b2 88 00 00 00 00 40 5e f8 a0
> 040: 00 00 00 00 00 10 36 64 00 00 00 00 00 00 00 00
> 050: 00 00 00 00 00 00 00 00 00 00 00 00 00 22 34 e4
> Slab corruption: biovec-128 start=000000007cc7a308, len=2048
> Redzone: 0x0/0x1812c.
> Last user: [<000000007cc7a750>](0x7cc7a750)
> 000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 010: 00 00 00 00 00 00 00 00 00 00 00 00 40 10 40 78
> 020: 00 00 00 00 40 10 40 7c 00 00 00 00 40 4f bb 00
> 030: 00 00 00 00 42 76 81 e0 00 00 00 00 42 76 70 40
> 040: 00 00 00 00 40 5b 86 a0 6b 6b 6b 6b 6b 6b 6b 6b
> 050: 00 00 00 00 00 00 00 00 00 00 00 00 03 c0 08 a1
> Prev obj: start=000000007cc798d0, len=2048
> Redzone: 0x0/0xff0804ff0f.
> Last user: [<00000000405bcea0>](0x405bcea0)
> 000: 00 00 00 00 00 00 00 00 00 00 00 00 00 22 34 e4
> 010: 41 2e 84 80 00 00 00 00 00 00 00 00 00 1e 84 80
> slab error in cache_alloc_debugcheck_after(): cache `biovec-128': double free, or memory outside object was overwritten
> Backtrace:
>  [<000000004011bd1c>] show_stack+0x14/0x20
>  [<00000000401144f0>] dump_stack+0x18/0x28
>  [<00000000401c65dc>] __slab_error+0x3c/0x48
>  [<00000000401c6db0>] cache_alloc_debugcheck_after+0x190/0x308
>  [<00000000401c91d8>] kmem_cache_alloc+0xd8/0x190
>  [<000000004019552c>] mempool_alloc_slab+0x1c/0x28
>  [<0000000040195720>] mempool_alloc+0x88/0x1b8
>  [<00000000402039e0>] bvec_alloc_bs+0x88/0x138
>  [<0000000040203b14>] bio_alloc_bioset+0x84/0x140
>  [<0000000040203cf0>] bio_alloc+0x20/0x50
>  [<00000000402086e4>] mpage_alloc+0x44/0xd0
>  [<0000000040208c8c>] __mpage_writepage+0x41c/0x788
>  [<000000004019c7ec>] write_cache_pages+0x33c/0x438
>  [<0000000040208808>] mpage_writepages+0x48/0xb0
>  [<00000000142ca3a4>] ext2_writepages+0x1c/0x28 [ext2]
>  [<000000004019c974>] do_writepages+0x44/0x78
> 
> 000000007cc7a300: redzone 1:0x0, redzone 2:0x1812c
> ------------[ cut here ]------------
> kernel BUG at mm/slab.c:2895!
> 
>      YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
> PSW: 00001000000001001111111100001110 Tainted: G        W 
> r00-03  000000ff0804ff0e 00000000405baea0 00000000401c6b0c 000000007cc7a300
> r04-07  00000000405b86a0 0000000000000000 000000007ed64740 d84156c5635688c0
> r08-11  00000000404063c0 000000007cc7a2c0 00000000401955ac 00000000405c2ea0
> r12-15  00000000405c0ea0 0000000040574f50 0000000000000000 000000004050bb80
> r16-19  00000000405ba6a0 0000000000000000 00000000ffffffff 00000000000f6ab4
> r20-23  000000006d207700 00000000001fa11d 00000000000f1c19 0000000066957700
> r24-27  00000000401955ac 00000000001fa11d 000000007cc7a300 00000000405b86a0
> r28-31  00000000000f6ab4 0000000040575500 0000000040575530 0000000000000003
> sr00-03  00000000006c9800 0000000000000000 0000000000000000 00000000006c9800
> sr04-07  0000000000000000 0000000000000000 0000000000000000 0000000000000000
> 
> IASQ: 0000000000000000 0000000000000000 IAOQ: 00000000401c6bb8 00000000401c6bbc
>  IIR: 03ffe01f    ISR: 0000000010340000  IOR: 000000015d575538
>  CPU:        0   CR30: 0000000040574000 CR31: 0000000040554000
> ORIG_R28: 000000004058f6a0
> IAOQ[0]: cache_free_debugcheck+0x360/0x3c8
> IAOQ[1]: cache_free_debugcheck+0x364/0x3c8
> RP(r2): cache_free_debugcheck+0x2b4/0x3c8
> Backtrace:
>  [<00000000401c733c>] kmem_cache_free+0x4c/0x150
>  [<00000000401955ac>] mempool_free_slab+0x1c/0x28
>  [<0000000040195690>] mempool_free+0xd8/0xe0
>  [<0000000040204a30>] bio_free+0x40/0x90
>  [<0000000040204a9c>] bio_fs_destructor+0x1c/0x28
>  [<00000000402023f8>] bio_put+0x88/0xa0
>  [<0000000040209b64>] mpage_end_io_write+0xcc/0x138
>  [<00000000402024e0>] bio_endio+0x70/0x90
>  [<000000004025bd60>] req_bio_endio+0xf8/0x158
>  [<000000004025befc>] __end_that_request_first+0x13c/0x3f8
>  [<000000004025c1f4>] end_that_request_data+0x3c/0xa8
>  [<000000004025d058>] blk_end_io+0x38/0xf8
>  [<000000004025d178>] blk_end_request+0x18/0x28
>  [<00000000081183e4>] scsi_end_request+0x4c/0x110 [scsi_mod]
>  [<0000000008118c8c>] scsi_io_completion+0x12c/0x538 [scsi_mod]
>  [<000000000810ed44>] scsi_finish_command+0xd4/0x148 [scsi_mod]
> 
> Backtrace:
>  [<000000004011bd1c>] show_stack+0x14/0x20
>  [<00000000401144f0>] dump_stack+0x18/0x28
>  [<000000004011c508>] die_if_kernel+0x138/0x240
>  [<000000004011ce88>] handle_interruption+0x878/0x910
>  [<00000000401c6bb8>] cache_free_debugcheck+0x360/0x3c8
>  [<00000000401c733c>] kmem_cache_free+0x4c/0x150
>  [<00000000401955ac>] mempool_free_slab+0x1c/0x28
>  [<0000000040195690>] mempool_free+0xd8/0xe0
>  [<0000000040204a30>] bio_free+0x40/0x90
>  [<0000000040204a9c>] bio_fs_destructor+0x1c/0x28
>  [<00000000402023f8>] bio_put+0x88/0xa0
>  [<0000000040209b64>] mpage_end_io_write+0xcc/0x138
>  [<00000000402024e0>] bio_endio+0x70/0x90
>  [<000000004025bd60>] req_bio_endio+0xf8/0x158
>  [<000000004025befc>] __end_that_request_first+0x13c/0x3f8
>  [<000000004025c1f4>] end_that_request_data+0x3c/0xa8
> 
> Dave

Re: resource_size_t printk woes...

[John David Anglin]

> Hi Dave,
> 
> telling you to try vanilla 2.6.28 was a stupid idea.
> I forgot that I had exactly the same problem (slab corruption):
> http://bugzilla.kernel.org/show_bug.cgi?id=11913
> when I started the thread 
> "2.6.28-rcX in pretty bad shape on parisc"
> here on the list as well.
> 
> The solution for me was to use another default config.
> James posted this one, which started to get everything working for me:
> http://parisc-linux.org/~jejb/config-2.6.28-rc5-ion
> Try this one instead (e.g. with Kyle's tree).
> 
> I assume something in your .config is different than what is in
> James' .config. It would be interesting to know what it
> is. I didn't checked further at that time.

The config that I have been using is based on James' ion config, plus
the defaults from running make oldconfig.

I actually was running 2.6.28 before I started experimenting yesterday.
It had run about three days building gcc without major problems.  As
noted by Grant, there is usually one unexplained segv (usually in make
or bash), then the system seems to run reasonably well for an extended
period.

If bash segvs, the system goes into an infinite loop of segvs due to the
way it handles signals, and the fact that the kernel restarts the faulting
instruction.  This fills the root file system with log messages...

I'm running a hacked version of bash which exits immediately to avoid this
problem.

Dave
-- 
J. David Anglin                                  dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)

Re: resource_size_t printk woes...

[John David Anglin]

> I assume something in your .config is different than what is in
> James' .config. It would be interesting to know what it
> is. I didn't checked further at that time.

On this, there is a problem with config's for my c3000.  2.6.28 builds
and boots fine with a config based on Kyle's allegro config.  However,
it crashes with thw config that I'd being using.  This is just a guess,
but I think IDE support is broken (machine has a cd drive).

Dave
-- 
J. David Anglin                                  dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)

Re: resource_size_t printk woes...

[Grant Grundler]

On Fri, Jan 02, 2009 at 11:43:03AM -0500, John David Anglin wrote:
...
> On this, there is a problem with config's for my c3000.  2.6.28 builds
> and boots fine with a config based on Kyle's allegro config.  However,
> it crashes with thw config that I'd being using.  This is just a guess,
> but I think IDE support is broken (machine has a cd drive).

That's posible. Can you look for HPMC PIM dump?
If so, I can take a look at it.

thanks,
grant