Atmel website | ARM Community | AVR freaks | Technical Support
Banner
 FAQ •  Search •  Register •  Login 

All times are UTC + 1 hour [ DST ]




Post new topic Reply to topic  [ 12 posts ] 
Author Message
 Post subject: Kernel hang after Uncompressing ....done booting the kernel
PostPosted: Sun Jul 08, 2007 6:44 pm 
Offline

Joined: Thu Sep 14, 2006 10:12 pm
Posts: 11
My board is an at91rm9200 based board, AT45DB642D dataflash
We successfully build u-boot and linux-2.6.17 kernel and everythink is OK
But when we try compil another kernel (like 2.6.21) the kernel doesn't start, we got:

Uncompressing Linux,...........................done, booting the kernel

Any idea ??

Regards


Top
 Profile  
 
 Post subject: Re: Kernel hang after Uncompressing ....done booting the ke
PostPosted: Mon Jul 09, 2007 5:06 am 
Offline

Joined: Thu Apr 19, 2007 10:15 pm
Posts: 204
Location: USA
Hi there

I'm seeing the same issue with 2.6.22-rc1 on an at91sam9260. During the compile there was a warning message from module ./init/main.c that compiler version gcc-4.1.0 is "known to miscompile the kernel". And that is the version of the compiler I was using. I plan on trying a different compiler version tomorrow.

The warning message is not in the 2.6.19 kernel source. The warning is in 2.6.20.

Regards


Top
 Profile  
 
 Post subject: Kernel hang after Uncompressing Linu ....done booting the ke
PostPosted: Mon Jul 09, 2007 7:47 am 
Offline

Joined: Thu Sep 14, 2006 10:12 pm
Posts: 11
Thanks for the response
But I got the problem even with linux kernel > 2.6.17

I tried to use 3.4.3(gnuarm) and 4.1.1(crosstool) arm gcc on both kernel
I had the same issue

Any idea ?

Thanks


Top
 Profile  
 
 Post subject:
PostPosted: Mon Jul 09, 2007 8:54 am 
Offline

Joined: Thu Feb 03, 2005 11:41 am
Posts: 87
Location: Erfurt/Germany
Hi,

you must asure to pass the right machine ID to kernel from u-boot. A search will tell you how it should be done.

--
Mike

_________________
Senior IT Consultant
Germany


Top
 Profile  
 
 Post subject: Kernel hang after Uncompressing Linux....done booting the ke
PostPosted: Mon Jul 09, 2007 1:33 pm 
Offline

Joined: Thu Sep 14, 2006 10:12 pm
Posts: 11
Thanks for the reply

When you said " pass the right machine ID to kernel from u-boot", can you please explain the procedure ?

Because when I use 2.6.17 kernel, I just overwrite the board-dk.c file with mine, and did the same (with some modification to fit the new kernel fonctions) with 2.6.21

I will apreciate to have the procedure

Thanks again


Top
 Profile  
 
 Post subject:
PostPosted: Mon Jul 09, 2007 6:08 pm 
Offline

Joined: Thu Feb 03, 2005 11:41 am
Posts: 87
Location: Erfurt/Germany
Hi,

try adding behind this line in kernel/printk.c (around line 538):

Code:
printed_len = vscnprintf(printk_buf, sizeof(printk_buf), fmt, args);



the line

Code:
printascii(printk_buf);



This will show you any messages which generated before the output starts. So you can see what really the problem is.

Maybe you have to enable printascii somewhere.

--
Mike

_________________
Senior IT Consultant
Germany


Top
 Profile  
 
 Post subject:
PostPosted: Tue Jul 10, 2007 5:39 am 
Offline

Joined: Thu Apr 19, 2007 10:15 pm
Posts: 204
Location: USA
Hi there

For my variation of this synptom, I see the following:

    Starting kernel ...

    Uncompressing Linux......................................................................................... done, booting the kernel.
    <5>Linux version 2.6.22-rc1-PCSC-Quantum-0.6 (gerard@spiff) (gcc version 4.2.0)
    #27 Mon Jul 9 20:23:45 PDT 2007
    CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
    Machine: PCSC AT91SAM9260-MC
    Memory policy: ECC disabled, Data cache writethrough
    <7>On node 0 totalpages: 16384
    <7> DMA zone: 128 pages used for memmap
    <7> DMA zone: 0 pages reserved
    <7> DMA zone: 16256 pages, LIFO batch:3
    <7> Normal zone: 0 pages used for memmap

... and that's all folks.
Had to do a `make menuconfig` and enable low-level kernel debugging.
Guess I need to try this on a working kernel, like 2.6.19
Thanks Mike for this trick.

Obkar,
Are you getting any warning messages about section mismatch at the end of the kernel build, just before the image is made?
    SYSMAP System.map
    SYSMAP .tmp_System.map
    MODPOST vmlinux
    WARNING: init/built-in.o - Section mismatch: reference to .init.text: from .text between 'rest_init' (at offset 0x160) and 'try_name'
    WARNING: mm/built-in.o - Section mismatch: reference to .init.text: from .text between 'kmem_cache_create' (at offset 0x17800) and 'cache_reap'
    WARNING: mm/built-in.o - Section mismatch: reference to .init.text: from .text between 'kmem_cache_create' (at offset 0x17834) and 'cache_reap'



There were 2 section mismatches in my drivers (when built with 2.6.22) that I was able to eliminate/fix. But I have no clue about these.


Regards


Top
 Profile  
 
 Post subject:
PostPosted: Tue Jul 10, 2007 8:17 am 
Offline

Joined: Thu Apr 19, 2007 10:15 pm
Posts: 204
Location: USA
Hi there

A good 2.6.19 kernel boot prints out:
    Starting kernel ...

    Uncompressing Linux........................................................................................ done, booting the kernel.
    <5>Linux version 2.6.19-PCSC-Quantum-0.5 (gerard@susie) (gcc version 4.1.2) #2 Mon Jul 9 23:02:21 PDT 2007
    CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
    Machine: PCSC AT91SAM9260-MC
    Memory policy: ECC disabled, Data cache writethrough
    <7>On node 0 totalpages: 16384
    <7> DMA zone: 128 pages used for memmap
    <7> DMA zone: 0 pages reserved
    <7> DMA zone: 16256 pages, LIFO batch:3
    <7> Normal zone: 0 pages used for memmap
    Clocks: CPU 147 MHz, master 73 MHz, main 18.432 MHz
    CPU0: D VIVT write-back cache
    CPU0: I cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
    CPU0: D cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
    Built 1 zonelists. Total pages: 16256
    <5>Kernel command line: mem=16M console=ttyS0,115200 ip=192.168.2.13:::255.255.255.0:quantum03:eth0:on
    <6>AT91: 96 gpio irqs in 3 banks
    PID hash table entries: 256 (order: 8, 1024 bytes)
    Console: colour dummy device 80x30


Regards


Top
 Profile  
 
 Post subject:
PostPosted: Tue Jul 10, 2007 9:51 am 
Offline

Joined: Thu Sep 14, 2006 10:12 pm
Posts: 11
Hello everybody,

To blue_z:
here are the end of the compilation

KSYM .tmp_kallsyms2.S
AS .tmp_kallsyms2.o
LD vmlinux
SYSMAP System.map
SYSMAP .tmp_System.map
MODPOST vmlinux
OBJCOPY arch/arm/boot/Image
Kernel: arch/arm/boot/Image is ready
GZIP arch/arm/boot/compressed/piggy.gz
AS arch/arm/boot/compressed/piggy.o
LD arch/arm/boot/compressed/vmlinux
OBJCOPY arch/arm/boot/zImage
Kernel: arch/arm/boot/zImage is ready
UIMAGE arch/arm/boot/uImage
Image Name: Linux-2.6.21
Created: Tue Jul 10 01:40:34 2007
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1333552 Bytes = 1302.30 kB = 1.27 MB
Load Address: 0x20008000
Entry Point: 0x20008000
Image arch/arm/boot/uImage is ready

To mwolfram:
I did what you told me (enable degug, add the line you write) and here for the first time I get:

U-Boot 1.1.4 (Jan 16 2007 - 20:34:30)

U-Boot code: 21F80000 -> 21F97008 BSS: -> 21FB4004
RAM Configuration:
Bank #0: 20000000 32 MB
Atmel: Flash: 0 kB
DataFlash:AT45DB642
Nb pages: 8192
Page Size: 1056
Size= 8650752 bytes
Logical address: 0xC0000000
Area 0: C0000000 to C0007FFF (RO)
Area 1: C0008000 to C001FFFF (RO)
Area 2: C0020000 to C0027FFF
Area 3: C0028000 to C083FFFF
In: serial
Out: serial
Err: serial
Hit any key to stop autoboot: 0
No Link
No Link
MAC: error during MII initialization (unplugged network cable?)
## Booting image at c0040000 ...
Image Name: Linux-2.6.21
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1333552 Bytes = 1.3 MB
Load Address: 20008000
Entry Point: 20008000
Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux.............................................................
......................... done, booting the kernel.
<5>Linux version 2.6.21 (larbi@Larbi) (gcc version 3.4.3) #3 PREEMPT Tue Jul 10
01:39:58 CEST 2007
CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0007177
Machine: Atmel AT91RM9200-DK
Memory policy: ECC disabled, Data cache writeback
<7>On node 0 totalpages: 8192
<7> DMA zone: 64 pages used for memmap
<7> DMA zone: 0 pages reserved
<7> DMA zone: 8128 pages, LIFO batch:0
<7> Normal zone: 0 pages used for memmap
Clocks: CPU 179 MHz, master 59 MHz, main 18.432 MHz
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
CPU0: D cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
Built 1 zonelists. Total pages: 8128
<5>Kernel command line: mem=32M console=ttyS0,115200 rootdelay=8 root=/dev/sda1
rw
<6>AT91: 96 gpio irqs in 3 banks
PID hash table entries: 128 (order: 7, 512 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
<6>Memory: 32MB = 32MB total
<5>Memory: 29708KB available (2464K code, 180K data, 84K init)
<7>Calibrating delay loop... 89.70 BogoMIPS (lpj=448512)
Mount-cache hash table entries: 512
<6>CPU: Testing write buffer coherency: ok
<6>NET: Registered protocol family 16
<5>SCSI subsystem initialized
<6>usbcore: registered new interface driver usbfs
<6>usbcore: registered new interface driver hub
<6>usbcore: registered new device driver usb
<6>Bluetooth: Core ver 2.11
<6>NET: Registered protocol family 31
<6>Bluetooth: HCI device and connection manager initialized
<6>Bluetooth: HCI socket layer initialized
<6>NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 1024 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
<6>TCP: Hash tables configured (established 1024 bind 1024)
<6>TCP reno registered
<4>NetWinder Floating Point Emulator V0.97 (double precision)
<6>JFFS2 version 2.2. (NAND) (C) 2001-2006 Red Hat, Inc.
<6>io scheduler noop registered
<6>io scheduler anticipatory registered (default)
<6>at91_spi: Baud rate set to 5990400
<6>AT91 SPI driver loaded
<6>PPP generic driver version 2.4.2
<6>NET: Registered protocol family 24
<6>eth0: Link down.
<6>eth0: AT91 ethernet at 0xfefbc000 int=24 10-HalfDuplex (aa:bb:cc:00:11:22)
<6>eth0: Micrel KS8721 PHY
at91_dataflash: AT45DB642 detected [spi0] (8650752 bytes)
<5>Creating 3 MTD partitions on "AT45DB642.spi0":
<5>0x00000000-0x00042000 : "bootloader"
<5>0x00042000-0x0018c000 : "kernel"
<5>0x0018c000-0x00840000 : "filesystem"
<7>ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
<7>ohci_hcd: block sizes: ed 64 td 64
<7>at91_ohci at91_ohci: start
<6>at91_ohci at91_ohci: AT91 OHCI
<7>drivers/usb/core/inode.c: creating file 'devices'
<7>drivers/usb/core/inode.c: creating file '001'
<6>at91_ohci at91_ohci: new USB bus registered, assigned bus number 1
<7>at91_ohci at91_ohci: supports USB remote wakeup
<6>at91_ohci at91_ohci: irq 23, io mem 0x00300000
<7>at91_ohci at91_ohci: created debug files
<7>at91_ohci at91_ohci: resetting from state 'reset', control = 0x0
<7>at91_ohci at91_ohci: OHCI controller state
<7>at91_ohci at91_ohci: OHCI 1.0, NO legacy support registers
<7>at91_ohci at91_ohci: control 0x083 HCFS=operational CBSR=3
<7>at91_ohci at91_ohci: cmdstatus 0x00000 SOC=0
<7>at91_ohci at91_ohci: intrstatus 0x00000004 SF
<7>at91_ohci at91_ohci: intrenable 0x8000001a MIE UE RD WDH
<7>at91_ohci at91_ohci: hcca frame #0024
<7>at91_ohci at91_ohci: roothub.a 02000202 POTPGT=2 NPS NDP=2(2)
<7>at91_ohci at91_ohci: roothub.b 00000000 PPCM=0000 DR=0000
<7>at91_ohci at91_ohci: roothub.status 00008000 DRWE
<7>at91_ohci at91_ohci: roothub.portstatus [0] 0x00000100 PPS
<7>at91_ohci at91_ohci: roothub.portstatus [1] 0x00000100 PPS
<7>usb usb1: default language 0x0409
<7>usb usb1: new device strings: Mfr=3, Product=2, SerialNumber=1
<6>usb usb1: Product: AT91 OHCI
<6>usb usb1: Manufacturer: Linux 2.6.21 ohci_hcd
<6>usb usb1: SerialNumber: at91
<7>usb usb1: uevent
<7>usb usb1: usb_probe_device
<6>usb usb1: configuration #1 chosen from 1 choice
<7>usb usb1: adding 1-0:1.0 (config #1, interface 0)
<7>usb 1-0:1.0: uevent
<7>hub 1-0:1.0: usb_probe_interface
<7>hub 1-0:1.0: usb_probe_interface - got id
<6>hub 1-0:1.0: USB hub found
<6>hub 1-0:1.0: 2 ports detected
<7>hub 1-0:1.0: standalone hub
<7>hub 1-0:1.0: no power switching (usb 1.0)
<7>hub 1-0:1.0: global over-current protection
<7>hub 1-0:1.0: power on to power good time: 4ms
<7>hub 1-0:1.0: local power source is good
<7>hub 1-0:1.0: no over-current condition exists
<7>hub 1-0:1.0: trying to enable port power on non-switchable hub
<7>hub 1-0:1.0: state 7 ports 2 chg 0000 evt 0000
<7>drivers/usb/core/inode.c: creating file '001'
<6>Initializing USB Mass Storage driver...
<6>usbcore: registered new interface driver usb-storage
<6>USB Mass Storage support registered.
<6>mice: PS/2 mouse device common for all mice
<6>i2c /dev entries driver
<6>at91_i2c at91_i2c: AT91 i2c bus driver.
<6>Bluetooth: HCI USB driver ver 2.9
<6>usbcore: registered new interface driver hci_usb
<6>Bluetooth: HCI UART driver ver 2.2
<6>Bluetooth: HCI H4 protocol initialized
<6>Bluetooth: HCI BCSP protocol initialized
<6>TCP cubic registered
<6>NET: Registered protocol family 1
<6>NET: Registered protocol family 17
<6>Bluetooth: L2CAP ver 2.8
<6>Bluetooth: L2CAP socket layer initialized
<6>Bluetooth: SCO (Voice Link) ver 0.5
<6>Bluetooth: SCO socket layer initialized
<6>Bluetooth: RFCOMM socket layer initialized
<6>Bluetooth: RFCOMM TTY layer initialized
<6>Bluetooth: RFCOMM ver 1.8
<6>Bluetooth: BNEP (Ethernet Emulation) ver 1.2
<6>Bluetooth: BNEP filters: protocol multicast
<7>hub 1-0:1.0: state 7 ports 2 chg 0000 evt 0004
<7>at91_ohci at91_ohci: GetStatus roothub.portstatus [1] = 0x00010301 CSC LSDA P
PS CCS
<7>hub 1-0:1.0: port 2, status 0301, change 0001, 1.5 Mb/s
<6>Waiting 8sec before mounting root device...
<7>hub 1-0:1.0: debounce: port 2: total 100ms stable 100ms status 0x301
<7>at91_ohci at91_ohci: GetStatus roothub.portstatus [1] = 0x00100303 PRSC LSDA
PPS PES CCS
<6>usb 1-2: new low speed USB device using at91_ohci and address 2
<7>at91_ohci at91_ohci: urb c1c0f120 path 2 ep0in 5ec20000 cc 5 --> status -62
<7>at91_ohci at91_ohci: urb c1c0f120 path 2 ep0in 5ec20000 cc 5 --> status -62
<7>at91_ohci at91_ohci: urb c1c0f120 path 2 ep0in 5ec20000 cc 5 --> status -62
<7>at91_ohci at91_ohci: GetStatus roothub.portstatus [1] = 0x00100303 PRSC LSDA
PPS PES CCS
<3>usb 1-2: device descriptor read/64, error -62
<7>at91_ohci at91_ohci: urb c1c0f120 path 2 ep0in 5ec20000 cc 5 --> status -62
<7>at91_ohci at91_ohci: urb c1c0f120 path 2 ep0in 5ec20000 cc 5 --> status -62
<7>at91_ohci at91_ohci: urb c1c0f120 path 2 ep0in 5ec20000 cc 5 --> status -62
<7>at91_ohci at91_ohci: GetStatus roothub.portstatus [1] = 0x00100303 PRSC LSDA
PPS PES CCS
<3>usb 1-2: device descriptor read/64, error -62
<7>at91_ohci at91_ohci: GetStatus roothub.portstatus [1] = 0x00100303 PRSC LSDA
PPS PES CCS
<6>usb 1-2: new low speed USB device using at91_ohci and address 3
<7>at91_ohci at91_ohci: urb c1c0f120 path 2 ep0in 5ec20000 cc 5 --> status -62
<7>at91_ohci at91_ohci: urb c1c0f120 path 2 ep0in 5ec20000 cc 5 --> status -62
<7>at91_ohci at91_ohci: urb c1c0f120 path 2 ep0in 5ec20000 cc 5 --> status -62
<7>at91_ohci at91_ohci: GetStatus roothub.portstatus [1] = 0x00100303 PRSC LSDA
PPS PES CCS
<3>usb 1-2: device descriptor read/64, error -62
<7>at91_ohci at91_ohci: urb c1c0f120 path 2 ep0in 5ec20000 cc 5 --> status -62
<7>at91_ohci at91_ohci: urb c1c0f120 path 2 ep0in 5ec20000 cc 5 --> status -62
<7>at91_ohci at91_ohci: urb c1c0f120 path 2 ep0in 5ec20000 cc 5 --> status -62
<7>at91_ohci at91_ohci: GetStatus roothub.portstatus [1] = 0x00100303 PRSC LSDA
PPS PES CCS
<3>usb 1-2: device descriptor read/64, error -62
<7>at91_ohci at91_ohci: GetStatus roothub.portstatus [1] = 0x00100303 PRSC LSDA
PPS PES CCS
<6>usb 1-2: new low speed USB device using at91_ohci and address 4
<7>at91_ohci at91_ohci: urb c1c0f120 path 2 ep0out 5ec20000 cc 5 --> status -62
<7>at91_ohci at91_ohci: urb c1c0f120 path 2 ep0out 5ec20000 cc 5 --> status -62
<3>usb 1-2: device not accepting address 4, error -62
<7>at91_ohci at91_ohci: GetStatus roothub.portstatus [1] = 0x00100303 PRSC LSDA
PPS PES CCS
<6>usb 1-2: new low speed USB device using at91_ohci and address 5
<7>at91_ohci at91_ohci: urb c1c0f120 path 2 ep0out 5ec20000 cc 5 --> status -62
<7>at91_ohci at91_ohci: urb c1c0f120 path 2 ep0out 5ec20000 cc 5 --> status -62
<3>usb 1-2: device not accepting address 5, error -62
<7>hub 1-0:1.0: state 7 ports 2 chg 0000 evt 0004
<3>Root-NFS: No NFS server available, giving up.
<3>VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "sda1" or unknown-block(2,0)
Please append a correct "root=" boot option
<0>Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0

What do you you think about that ?
Thanks for your help again


Top
 Profile  
 
 Post subject:
PostPosted: Tue Jul 10, 2007 10:03 am 
Offline

Joined: Thu Sep 14, 2006 10:12 pm
Posts: 11
Hi again ,
Sorry for posting all this stuff

Here is the result when I plug my usb key:

<6>Waiting 8sec before mounting root device...
<5>scsi 0:0:0:0: Direct-Access JetFlash TS1GJFV30 8.07 PQ: 0 ANSI: 2
<5>SCSI device sda: 2007038 512-byte hdwr sectors (1028 MB)
<7>at91_ohci at91_ohci: urb c1cdcb60 path 1.2 ep2in 93120000 cc 9 --> status -12
1
<5>sda: Write Protect is off
<7>sda: Mode Sense: 03 00 00 00
<3>sda: assuming drive cache: write through
<5>SCSI device sda: 2007038 512-byte hdwr sectors (1028 MB)
<7>at91_ohci at91_ohci: urb c1cdcb60 path 1.2 ep2in 92120000 cc 9 --> status -12
1
<5>sda: Write Protect is off
<7>sda: Mode Sense: 03 00 00 00
<3>sda: assuming drive cache: write through
<6> sda: sda1
<5>sd 0:0:0:0: Attached scsi removable disk sda
<7>usb-storage: device scan complete
<6>kjournald starting. Commit interval 5 seconds
<6>EXT3 FS on sda1, internal journal
<6>EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem).
<6>Freeing init memory: 84K
<4>Warning: unable to open an initial console.

Thanks


Top
 Profile  
 
 Post subject:
PostPosted: Tue Jul 10, 2007 12:07 pm 
Offline

Joined: Thu Sep 14, 2006 10:12 pm
Posts: 11
Hello

Problem was solved

Just add on the kernel configuration file
device drivers -->
charactere device support -->
serial drivers -->
* AT91/AT32 on-chip ...
*support for console on AT91/AT32 serial port

and everythink goes smooth like the 2.6.17 kernel

Thanks again for the people who answered me

By the way, is it possible to have a step by step instruction to register the board and create all necessery files

Thanks again


Top
 Profile  
 
 Post subject:
PostPosted: Wed Jul 11, 2007 11:54 pm 
Offline

Joined: Thu Apr 19, 2007 10:15 pm
Posts: 204
Location: USA
Hi there

Well Oblar fixed his problem, and I found a workaround by going to the 2.6.22 kernel that was released a few days ago. The section mismatch warnings have also been fixed (except for one in at91sam926x_timer_init) with this release.

Using the printascii() in 2.6.22-rc1, I was only able to narrow down the hangup to somewhere in arch/arm/mm/mmu.c/devicemaps_init(). That routine does not allow I/O during its execution, so debugging it is essentially impossible.

So be careful using kernel version 2.6.22-rc1. Linux 2.6.22 has been released, but the at91 patch is not yet available. I hacked the -rc1 patch to get the modules I needed.

Regards


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 12 posts ] 

All times are UTC + 1 hour [ DST ]


Who is online

Users browsing this forum: No registered users and 26 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to: