Page 2 of 2 FirstFirst 12
Results 11 to 20 of 20

Thread: i915 very high interrupt load

  1. #11

    Default Re: i915 very high interrupt load

    Quote Originally Posted by mrmazda View Post
    I don't consider reverting to the default DDX driver to be hacking. It's newer technology than the drivers provided by xf86-video-* (yet more than 7 years old), which to me implies it should be enjoying more developer devotion. The reason the default doesn't get used much has to do with maintaining support for antique and non-AMD/Intel/NVidia graphics, which the Modesetting DDX driver mostly doesn't support. AFAICT, choosing the optimal DDX driver for antiques is too complicated for the Xorg automagic system.
    All powersave and screensaver/lock was disabled, monitor was never turned off automaticaly and nothing was locked,
    but I turned it off by power button yesterday evening and when i turned it on this morning the high interrupt load startet.

  2. #12
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    2,066
    Blog Entries
    1

    Default Re: i915 very high interrupt load

    Quote Originally Posted by highlander34 View Post
    All powersave and screensaver/lock was disabled, monitor was never turned off automaticaly and nothing was locked,
    but I turned it off by power button yesterday evening and when i turned it on this morning the high interrupt load startet.
    Bought a LG 24EB23PM-B back in 2014 and never experienced problems with the i3-4130 or the i7-6700K since then:

    Code:
    erlangen:~ # inxi -G
    Graphics:  Device-1: Intel HD Graphics 530 driver: i915 v: kernel 
               Display: server: X.Org 1.20.9 driver: intel unloaded: fbdev,modesetting,vesa resolution: 1920x1200~60Hz 
               OpenGL: renderer: Mesa DRI Intel HD Graphics 530 (SKL GT2) v: 4.6 Mesa 20.2.1 
    erlangen:~ #

    Packages installed:

    Code:
    erlangen:~ # zypper se -is intel
    Loading repository data...
    Reading installed packages...
    
    S  | Name                  | Type    | Version                        | Arch   | Repository
    ---+-----------------------+---------+--------------------------------+--------+---------------------------
    i+ | intel-hybrid-driver   | package | 1.0.2-5.3                      | x86_64 | openSUSE-20191106-0
    i  | intel-media-driver    | package | 20.3.0-1.1                     | x86_64 | openSUSE-20191106-0
    i  | intel-vaapi-driver    | package | 2.4.1-2.1                      | x86_64 | openSUSE-20191106-0
    i  | kernel-firmware-intel | package | 20201005-3.1                   | noarch | openSUSE-Tumbleweed-Update
    i  | libdrm_intel1         | package | 2.4.102-2.1                    | x86_64 | openSUSE-20191106-0
    i+ | libvulkan_intel       | package | 20.2.1-265.1                   | x86_64 | openSUSE-20191106-0
    i  | ucode-intel           | package | 20200616-1.2                   | x86_64 | openSUSE-20191106-0
    i+ | xf86-video-intel      | package | 2.99.917+git8674.25c9a2fcc-5.4 | x86_64 | openSUSE-20191106-0
    erlangen:~ #
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), openSUSE Tumbleweed, KDE Plasma 5

  3. #13

    Default Re: i915 very high interrupt load - how to reproduce

    I switched the DDX driver by uninstalling the xorg-x11-driver-video and xf86-video-* packages as described in
    https://forums.opensuse.org/showthre...-driver-primer

    The problem did not change, but I found an easy way to reproduce the interrupt storm immediately:

    Code:
    while true; do echo "$(date +%T) $(cat /proc/interrupts | grep "i915")"; sleep 1; done
    11:02:46  137:          0          0          0          0        394         64          0          0  IR-PCI-MSI 32768-edge      i915 
    11:02:47  137:          0          0          0          0        394         64          0          0  IR-PCI-MSI 32768-edge      i915 
    11:02:48  137:          0          0          0          0        394         64          0          0  IR-PCI-MSI 32768-edge      i915 
    11:02:49  137:          0          0          0          0        394         64          0          0  IR-PCI-MSI 32768-edge      i915 
    11:02:50  137:          0          0          0          0        394         64          0          0  IR-PCI-MSI 32768-edge      i915 
    monitor is turned off (still with electrical power)
    11:02:51  137:          0          0          0          0        394         64          0          0  IR-PCI-MSI 32768-edge      i915 
    11:02:52  137:          0          0          0          0        394         64          0          0  IR-PCI-MSI 32768-edge      i915 
    11:02:53  137:          0          0          0          0        394         64          0          0  IR-PCI-MSI 32768-edge      i915 
    11:02:54  137:          0          0          0          0        394         64          0          0  IR-PCI-MSI 32768-edge      i915 
    11:02:55  137:          0          0          0          0        394         64          0          0  IR-PCI-MSI 32768-edge      i915 
    11:02:56  137:          0          0          0          0        394         64          0          0  IR-PCI-MSI 32768-edge      i915 
    11:02:57  137:          0          0          0          0        394         64          0          0  IR-PCI-MSI 32768-edge      i915 
    11:02:58  137:          0          0          0          0        394         64          0          0  IR-PCI-MSI 32768-edge      i915 
    11:02:59  137:          0          0          0          0        394         64          0          0  IR-PCI-MSI 32768-edge      i915 
    11:03:00  137:          0          0          0          0        394         68          0          0  IR-PCI-MSI 32768-edge      i915 
    11:03:01  137:          0          0          0          0        394         68          0          0  IR-PCI-MSI 32768-edge      i915 
    monitor is turned on
    11:03:02  137:          0          0          0          0        394     690164          0          0  IR-PCI-MSI 32768-edge      i915 
    11:03:03  137:          0          0          0          0        394    1868443          0          0  IR-PCI-MSI 32768-edge      i915 
    11:03:04  137:          0          0          0          0        394    3106460          0          0  IR-PCI-MSI 32768-edge      i915 
    11:03:05  137:          0          0          0          0        394    4354082          0          0  IR-PCI-MSI 32768-edge      i915 
    11:03:07  137:          0          0          0          0        394    5492762          0          0  IR-PCI-MSI 32768-edge      i915
    
    No powersave, no screensaver, no mouse move or anything else.

    Tested with BENQ PD2705 and Lenovo 24" Thinkvision, both connected with Displayport cable

    I think the i915 module is broken and does not handle the new Intel 10100 CPU correctly, or maybe Gigabyte B460D3H board

  4. #14
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    2,066
    Blog Entries
    1

    Default Re: i915 very high interrupt load - how to reproduce

    Quote Originally Posted by highlander34 View Post
    No powersave, no screensaver, no mouse move or anything else.

    Tested with BENQ PD2705 and Lenovo 24" Thinkvision, both connected with Displayport cable

    I think the i915 module is broken and does not handle the new Intel 10100 CPU correctly, or maybe Gigabyte B460D3H board
    Guessing does not solve problems. Did you ever test with a live stick or another distribution?

    BTW: The HP Laptop 15-da0xxx suspends/resumes without any issues even when an old fashioned LG TV is attached. But it chokes when NetworkManager is enabled.
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), openSUSE Tumbleweed, KDE Plasma 5

  5. #15

    Default Re: i915 very high interrupt load - how to reproduce

    Quote Originally Posted by karlmistelberger View Post
    Guessing does not solve problems. Did you ever test with a live stick or another distribution?

    BTW: The HP Laptop 15-da0xxx suspends/resumes without any issues even when an old fashioned LG TV is attached. But it chokes when NetworkManager is enabled.
    I tested with Suse 42.3 on a USB disk:

    Code:
    lsmod | grep -i i915
    i915                 1339392  0  
    drm_kms_helper        155648  1 i915 
    drm                   393216  2 i915,drm_kms_helper 
    i2c_algo_bit           16384  1 i915 
    video                  45056  1 i915 
    button                 16384  1 i915
    
    
    in the /proc/interrupts there is no "i915" interrupt assigned

    Code:
                CPU0       CPU1       CPU2       CPU3       CPU4       CPU5       CPU6       CPU7        
       0:         32          0          0          0          0          0          0          0  IR-IO-APIC    2-edge      timer 
       1:         14          0          0          0       1619          0          0          0  IR-IO-APIC    1-edge      i8042 
       5:          0          0          0          0          0          0          0          0  IR-IO-APIC    5-edge      parport0 
       8:          0          0          0          0          1          0          0          0  IR-IO-APIC    8-edge      rtc0 
       9:          0          0          0          0          0          0          0          0  IR-IO-APIC    9-fasteoi   acpi 
     120:          0          0          0          0          0          0          0          0  DMAR-MSI    0-edge      dmar0 
     121:          0          0          0          0          0          0          0          0  DMAR-MSI    1-edge      dmar1 
     122:          0          0          0          0          0          0          0          0  IR-PCI-MSI 442368-edge      aerdrv 
     123:          0          0          0          0          0          0          0          0  IR-PCI-MSI 475136-edge      aerdrv 
     124:         12          0          0         27         65        245          0          0  IR-PCI-MSI 376832-edge      ahci[0000:00:17.0] 
     125:         25          0          0          0          0          0          0          0  IR-PCI-MSI 2621440-edge      nvme0q0, nvme0q1 
     126:      15879          0          0          0      54579          0          0          0  IR-PCI-MSI 327680-edge      xhci_hcd 
     127:          0         35          0          0          0          0          0          0  IR-PCI-MSI 2621441-edge      nvme0q2 
     128:          0          0         27          0          0          0          0          0  IR-PCI-MSI 2621442-edge      nvme0q3 
     129:          0          0          0         90          0          0          0          0  IR-PCI-MSI 2621443-edge      nvme0q4 
     130:          0          0          0          0        126          0          0          0  IR-PCI-MSI 2621444-edge      nvme0q5 
     131:          0          0          0          0          0        160          0          0  IR-PCI-MSI 2621445-edge      nvme0q6 
     132:          0          0          0          0          0          0         38          0  IR-PCI-MSI 2621446-edge      nvme0q7 
     133:          0          0          0          0          0          0          0        542  IR-PCI-MSI 2621447-edge      nvme0q8 
     134:        321          0          0          0       1338          0          0          0  IR-PCI-MSI 514048-edge      snd_hda_intel 
     NMI:          0          0          0          0          0          0          0          0   Non-maskable interrupts 
     LOC:      11583      13083      11632      12737      13101      12511       9613      11004   Local timer interrupts 
     SPU:          0          0          0          0          0          0          0          0   Spurious interrupts 
     PMI:          0          0          0          0          0          0          0          0   Performance monitoring interrupts 
     IWI:          0          0          0          0          0          0          0          0   IRQ work interrupts 
     RTR:          0          0          0          0          0          0          0          0   APIC ICR read retries 
     RES:       1252        606        371        284        495        275        235        254   Rescheduling interrupts 
     CAL:       2477       2429       2623       2711       2179       3395       2478       2287   Function call interrupts 
     TLB:       1505       1461       1712       1725       1137       2376       1574       1319   TLB shootdowns 
     TRM:          0          0          0          0          0          0          0          0   Thermal event interrupts 
     THR:          0          0          0          0          0          0          0          0   Threshold APIC interrupts 
     DFR:          0          0          0          0          0          0          0          0   Deferred Error APIC interrupts 
     MCE:          0          0          0          0          0          0          0          0   Machine check exceptions 
     MCP:          3          3          3          3          3          3          3          3   Machine check polls 
     ERR:          0 
     MIS:          0 
     PIN:          0          0          0          0          0          0          0          0   Posted-interrupt notification event 
     PIW:          0          0          0          0          0          0          0          0   Posted-interrupt wakeup event
    
    I could not reproduce the interrupt problem on opensuse 42.3
    at least not in the same way with monitor off/on as on 15.2

    Suse 15.2 has also much more firmware for i915 than suse 42.3:
    Code:
     ls -l /lib/firmware/i915/ /mnt/c/lib/firmware/i915/  
    /lib/firmware/i915/: 
    total 8352 
    lrwxrwxrwx 1 root root     19 Mar  1  2020 bxt_dmc_ver1.bin -> bxt_dmc_ver1_07.bin 
    -rw-r--r-- 1 root root   8380 Mar  1  2020 bxt_dmc_ver1_07.bin 
    -rw-r--r-- 1 root root 176256 Mar  1  2020 bxt_guc_32.0.3.bin 
    -rw-r--r-- 1 root root 181888 Mar  1  2020 bxt_guc_33.0.0.bin 
    -rw-r--r-- 1 root root 140928 Mar  1  2020 bxt_guc_ver8_7.bin 
    -rw-r--r-- 1 root root 146432 Mar  1  2020 bxt_guc_ver9_29.bin 
    -rw-r--r-- 1 root root 149824 Mar  1  2020 bxt_huc_2.0.0.bin 
    -rw-r--r-- 1 root root 154432 Mar  1  2020 bxt_huc_ver01_07_1398.bin 
    -rw-r--r-- 1 root root 146880 Mar  1  2020 bxt_huc_ver01_8_2893.bin 
    -rw-r--r-- 1 root root 182912 Mar  1  2020 cml_guc_33.0.0.bin 
    -rw-r--r-- 1 root root 226048 Mar  1  2020 cml_huc_4.0.0.bin 
    -rw-r--r-- 1 root root  11224 Mar  1  2020 cnl_dmc_ver1_06.bin 
    -rw-r--r-- 1 root root  11268 Mar  1  2020 cnl_dmc_ver1_07.bin 
    -rw-r--r-- 1 root root 396288 Mar  1  2020 ehl_guc_33.0.4.bin 
    -rw-r--r-- 1 root root 498880 Mar  1  2020 ehl_huc_9.0.0.bin 
    -rw-r--r-- 1 root root   8800 Mar  1  2020 glk_dmc_ver1_04.bin 
    -rw-r--r-- 1 root root 176640 Mar  1  2020 glk_guc_32.0.3.bin 
    -rw-r--r-- 1 root root 182336 Mar  1  2020 glk_guc_33.0.0.bin 
    -rw-r--r-- 1 root root 226048 Mar  1  2020 glk_huc_4.0.0.bin 
    -rw-r--r-- 1 root root 222080 Mar  1  2020 glk_huc_ver03_01_2893.bin 
    -rw-r--r-- 1 root root  25716 Mar  1  2020 icl_dmc_ver1_07.bin 
    -rw-r--r-- 1 root root  25952 Mar  1  2020 icl_dmc_ver1_09.bin 
    -rw-r--r-- 1 root root 380096 Mar  1  2020 icl_guc_32.0.3.bin 
    -rw-r--r-- 1 root root 385280 Mar  1  2020 icl_guc_33.0.0.bin 
    -rw-r--r-- 1 root root 498880 Mar  1  2020 icl_huc_9.0.0.bin 
    -rw-r--r-- 1 root root 488960 Mar  1  2020 icl_huc_ver8_4_3238.bin 
    lrwxrwxrwx 1 root root     19 Mar  1  2020 kbl_dmc_ver1.bin -> kbl_dmc_ver1_01.bin 
    -rw-r--r-- 1 root root   8616 Mar  1  2020 kbl_dmc_ver1_01.bin 
    -rw-r--r-- 1 root root   8840 Mar  1  2020 kbl_dmc_ver1_04.bin 
    -rw-r--r-- 1 root root 176448 Mar  1  2020 kbl_guc_32.0.3.bin 
    -rw-r--r-- 1 root root 182912 Mar  1  2020 kbl_guc_33.0.0.bin 
    -rw-r--r-- 1 root root 142656 Mar  1  2020 kbl_guc_ver9_14.bin 
    -rw-r--r-- 1 root root 147776 Mar  1  2020 kbl_guc_ver9_39.bin 
    -rw-r--r-- 1 root root 226048 Mar  1  2020 kbl_huc_4.0.0.bin 
    -rw-r--r-- 1 root root 218688 Mar  1  2020 kbl_huc_ver02_00_1810.bin 
    lrwxrwxrwx 1 root root     19 Mar  1  2020 skl_dmc_ver1.bin -> skl_dmc_ver1_26.bin 
    -rw-r--r-- 1 root root   8824 Mar  1  2020 skl_dmc_ver1_23.bin 
    -rw-r--r-- 1 root root   8928 Mar  1  2020 skl_dmc_ver1_26.bin 
    -rw-r--r-- 1 root root   8928 Mar  1  2020 skl_dmc_ver1_27.bin 
    -rw-r--r-- 1 root root 175552 Mar  1  2020 skl_guc_32.0.3.bin 
    -rw-r--r-- 1 root root 182080 Mar  1  2020 skl_guc_33.0.0.bin 
    -rw-r--r-- 1 root root 109636 Mar  1  2020 skl_guc_ver1.bin 
    -rw-r--r-- 1 root root 128320 Mar  1  2020 skl_guc_ver4.bin 
    lrwxrwxrwx 1 root root     18 Mar  1  2020 skl_guc_ver6.bin -> skl_guc_ver6_1.bin 
    -rw-r--r-- 1 root root 129024 Mar  1  2020 skl_guc_ver6_1.bin 
    -rw-r--r-- 1 root root 147520 Mar  1  2020 skl_guc_ver9_33.bin 
    -rw-r--r-- 1 root root 136320 Mar  1  2020 skl_huc_2.0.0.bin 
    -rw-r--r-- 1 root root 140992 Mar  1  2020 skl_huc_ver01_07_1398.bin 
    -rw-r--r-- 1 root root  18436 Mar  1  2020 tgl_dmc_ver2_04.bin 
    -rw-r--r-- 1 root root 417728 Mar  1  2020 tgl_guc_35.2.0.bin 
    -rw-r--r-- 1 root root 521408 Mar  1  2020 tgl_huc_7.0.3.bin 
    
    /mnt/c/lib/firmware/i915/: 
    total 1232 
    lrwxrwxrwx 1 root root     19 Mar  7  2019 bxt_dmc_ver1.bin -> bxt_dmc_ver1_07.bin 
    -rw-r--r-- 1 root root   8380 May 30  2017 bxt_dmc_ver1_07.bin 
    -rw-r--r-- 1 root root 140928 May 30  2017 bxt_guc_ver8_7.bin 
    -rw-r--r-- 1 root root 154432 May 30  2017 bxt_huc_ver01_07_1398.bin 
    lrwxrwxrwx 1 root root     19 Mar  7  2019 kbl_dmc_ver1.bin -> kbl_dmc_ver1_01.bin 
    -rw-r--r-- 1 root root   8616 May 30  2017 kbl_dmc_ver1_01.bin 
    -rw-r--r-- 1 root root 142656 May 30  2017 kbl_guc_ver9_14.bin 
    -rw-r--r-- 1 root root 218688 May 30  2017 kbl_huc_ver02_00_1810.bin 
    lrwxrwxrwx 1 root root     19 Mar  7  2019 skl_dmc_ver1.bin -> skl_dmc_ver1_26.bin 
    -rw-r--r-- 1 root root   8824 May 30  2017 skl_dmc_ver1_23.bin 
    -rw-r--r-- 1 root root   8928 May 30  2017 skl_dmc_ver1_26.bin 
    -rw-r--r-- 1 root root 109636 May 30  2017 skl_guc_ver1.bin 
    -rw-r--r-- 1 root root 128320 May 30  2017 skl_guc_ver4.bin 
    lrwxrwxrwx 1 root root     18 Mar  7  2019 skl_guc_ver6.bin -> skl_guc_ver6_1.bin 
    -rw-r--r-- 1 root root 129024 May 30  2017 skl_guc_ver6_1.bin 
    -rw-r--r-- 1 root root 140992 May 30  2017 skl_huc_ver01_07_1398.bin
    
    This is the boot.msg of suse 15.2 for i915
    Code:
    6>[    3.028247] i915 0000:00:02.0: vgaarb: deactivate vga console 
    <6>[    3.029735] Console: switching to colour dummy device 80x25 
    <6>[    3.031764] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). 
    <6>[    3.031772] [drm] Driver supports precise vblank timestamp query. 
    <6>[    3.032462] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem 
    <6>[    3.032824] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) 
    <6>[    3.046195] [drm] Initialized i915 1.6.0 20190822 for 0000:00:02.0 on minor 0 
    <6>[    3.048070] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no) 
    <6>[    3.048334] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input1 
    <7>[    3.064656] sr 1:0:0:0: Attached scsi CD-ROM sr0 
    <6>[    3.079815] fbcon: i915drmfb (fb0) is primary device 
    <6>[    3.127662] Console: switching to colour frame buffer device 160x45 
    <6>[    3.166826] i915 0000:00:02.0: fb0: i915drmfb frame buffer device
    
    i

  6. #16

    Default Re: i915 very high interrupt load - how to reproduce

    This is the boot.msg of suse 15.2 for i915
    Code:
    6>[    3.028247] i915 0000:00:02.0: vgaarb: deactivate vga console 
    <6>[    3.029735] Console: switching to colour dummy device 80x25 
    <6>[    3.031764] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). 
    <6>[    3.031772] [drm] Driver supports precise vblank timestamp query. 
    <6>[    3.032462] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem 
    <6>[    3.032824] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) 
    <6>[    3.046195] [drm] Initialized i915 1.6.0 20190822 for 0000:00:02.0 on minor 0 
    <6>[    3.048070] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no) 
    <6>[    3.048334] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input1 
    <7>[    3.064656] sr 1:0:0:0: Attached scsi CD-ROM sr0 
    <6>[    3.079815] fbcon: i915drmfb (fb0) is primary device 
    <6>[    3.127662] Console: switching to colour frame buffer device 160x45 
    <6>[    3.166826] i915 0000:00:02.0: fb0: i915drmfb frame buffer device
    
    I removed the i915/kbl_dmc_ver1_04.bin file from the initrd and loading failed on boot,
    but this changed nothing on the interrupt problem

    Downgrade to kernel 4.4.240 or kick suse15.2 and return to 42.3?


  7. #17
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    2,066
    Blog Entries
    1

    Default Re: i915 very high interrupt load - how to reproduce

    Quote Originally Posted by highlander34 View Post
    Downgrade to kernel 4.4.240 or kick suse15.2 and return to 42.3?
    When I encountered problems with i915 I moved forward to Tumbleweed: https://forums.opensuse.org/showthre...highlight=i915 Backporting is slow and complicated. You may be better off using Tumbleweed. I never experienced trouble with i915 since 2016.
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), openSUSE Tumbleweed, KDE Plasma 5

  8. #18
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    22,262
    Blog Entries
    1

    Default Re: i915 very high interrupt load

    ...or perhaps submit a bug report?
    openSUSE Leap 15.2; KDE Plasma 5

  9. #19

    Default Re: i915 very high interrupt load

    Quote Originally Posted by deano_ferrari View Post
    ...or perhaps submit a bug report?
    I have filed a bug report https://gitlab.freedesktop.org/drm/intel/-/issues/2609

    should I create it here too?

  10. #20

    Default Re: i915 very high interrupt load

    Quote Originally Posted by highlander34 View Post
    I have filed a bug report https://gitlab.freedesktop.org/drm/intel/-/issues/2609

    should I create it here too?
    Yes.

    And try to use new kernel + new firmware from Kernel:stable repo.

Page 2 of 2 FirstFirst 12

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •