Over 300GB logs size due to "AER PCIe Bus" errors

Got a new PC and installed Debian on it. After a week, I realized that /var/log grew up in size up to 300GB - kern.log was full of such messages:
db kernel: [7.936] pcieport 0000:00:1b.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
db kernel: [7.936] pcieport 0000:00:1b.4: AER: device [8086:a2eb] error status/mask=00000001/00002000
db kernel: [7.936] pcieport 0000:00:1b.4: AER: [ 0] RxErr                 
db kernel: [7.936] pcieport 0000:00:1b.4: AER: Corrected error received: 0000:00:1b.4
Launched lspci to see which device is causing the error to appear: it was a PCI wireless card. Found the fix quickly in the Internet: to add "pci=nommconf" to kernel parameters. Other resources recommend "pci=noaer", but this do not resolve the problem - it only surpress AER messages from the devices.

The Debian fix:
1) In /etc/default/grub set pci=nommconf in line:
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
so it will become:
GRUB_CMDLINE_LINUX_DEFAULT="quiet pci=nommconf"
2) Regenerate kernel files and update grub:
update-grub
3) Finally reboot:
reboot
This snippet, which explains problem in depth, was taken from stackexchange answer to a similar problem:
I can give at least a few details, even though I cannot fully explain what happens.
As described for example here, the CPU communicates with the PCIe bus controller by transaction layer packets (TLPs). The hardware detects when there are faulty ones, and the Linux kernel reports that as messages.
The kernel option pci=nommconf disables Memory-Mapped PCI Configuration Space, which is available in Linux since kernel 2.6. Very roughly, all PCI devices have an area that describe this device (which you see with lspci -vv), and the originally method to access this area involves going through I/O ports, while PCIe allows this space to be mapped to memory for simpler access.
That means in this particular case, something goes wrong when the PCIe controller uses this method to access the configuraton space of a particular device. It may be a hardware bug in the device, in the PCIe root controller on the motherboard, in the specific interaction of those two, or something else.
By using pci=nommconf, the configuration space of all devices will be accessed in the original way, and changing the access methods works around this problem. So if you want, it's both resolving and suppressing it.