Opened 6 years ago
Closed 6 years ago
#14273 closed bug (fixed)
atheroswifi spamming syslog
Reported by: | korli | Owned by: | waddlesplash |
---|---|---|---|
Priority: | normal | Milestone: | Unscheduled |
Component: | Drivers/Network/atheroswifi | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
using hrev52097 x86_64
the driver works nice!
KERN: [atheroswifi] (ath_pci) ath_edma_rxbuf_alloc: nothing on rxbuf?! KERN: [atheroswifi] (ath_pci) ath_edma_rxfifo_alloc: Q1: alloc failed: i=1, nbufs=128? KERN: [atheroswifi] (ath_pci) ath_edma_rxbuf_alloc: nothing on rxbuf?! KERN: [atheroswifi] (ath_pci) ath_edma_rxfifo_alloc: Q1: alloc failed: i=0, nbufs=128? KERN: [atheroswifi] (ath_pci) ath_edma_rxbuf_alloc: nothing on rxbuf?!
KERN: PCI: [dom 0, bus 2] bus 2, device 0, function 0: vendor 168c, device 0032, revision 01 KERN: PCI: class_base 02, class_function 80, class_api 00 KERN: PCI: vendor 168c: Qualcomm Atheros KERN: PCI: device 0032: AR9485 Wireless Network Adapter KERN: PCI: info: Network controller KERN: PCI: line_size 10, latency 00, header_type 00, BIST 00 KERN: PCI: ROM base host dea80000, pci dea80000, size 00010000 KERN: PCI: cardbus_CIS 00000000, subsystem_id 2086, subsystem_vendor_id 1a3b KERN: PCI: interrupt_line 05, interrupt_pin 01, min_grant 00, max_latency 00 KERN: PCI: base reg 0: host dea00000, pci dea0KERN: 0000, size 00080000, flags 04 KERN: PCI: base reg 1: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 2: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 3: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 4: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 5: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: Capabilities: PM, MSI, PCIe KERN: PCI: Extended capabilities: Advanced Error Reporting, Virtual Channel, Serial Number
Attachments (1)
Change History (3)
by , 6 years ago
Attachment: | syslog_asusrose.old added |
---|
comment:1 by , 6 years ago
So the "nothing on rxbuf" message comes from ath_edma_rxbuf_alloc, and that's called from ath_edma_rxfifo_alloc, and that's (probably) being called from ath_edma_startrecv; but there's a comment there stating it "probably is a no-op".
But then again, the other "spamming syslog" ticket in which the driver is said to work (#14270) has no messages like this one, so perhaps it is needed in that case.
Note:
See TracTickets
for help on using tickets.
syslog