On Mon Oct 29, 2012, Luc Michel wrote:
> Hi,
> 
> 2012/10/28 Thomas Fjellstrom <[email protected]>:
> > So I've reinstalled with 64bit debian. theres more irqs, but some of the
> > ones you suggested earlier don't exist (some do). Setting the affinity
> > didn't really help with performance. Now I also have both threads
> > showing, but one seems to be constantly stuck at 100% cpu use, and
> > things feel a bit slow.
> > 
> > The stock debian 2.6.32 kernel seems to perform better. the debian 3.2
> > kernel from sid, and this custom 3.6.3 kernel I just compiled both show
> > strangeness.
> > 
> > I can't really explain it.
> 
> Is your comBios up to date?

Yeah, thats the first thing I checked before doing the reinstall on the weekend.

> If it can help,here is my 3.6.2 x86_64 kernel config that works well for
> me. It's not highly optimized but does the job.
> http://divers.grrrkesta.fr/net6501-config-3.6.2.gz

I'll have to give that a try. I based my current one off of a nice fellow who
sent me his. I just enabled a few extra iptables modules, and gzip
compression.

I don't know if it'll be useful, but here's my /proc/interupts as it currently
is:

root@firewall:~# cat /proc/interrupts 
           CPU0       CPU1       
  0:    8577366          0   IO-APIC-edge      timer
  2:          0          0    XT-PIC-XT-PIC    cascade
  4:        316          0   IO-APIC-edge      serial
 16:          0          0   IO-APIC-fasteoi   gpio_pch, ehci_hcd:usb2, 
ohci_hcd:usb6, ohci_hcd:usb7, ohci_hcd:usb8
 18:          0          0   IO-APIC-fasteoi   pch-dma
 19:          0          0   IO-APIC-fasteoi   pch-dma, ehci_hcd:usb1, 
ohci_hcd:usb3, ohci_hcd:usb4, ohci_hcd:usb5
 44:     168431          0   PCI-MSI-edge      ahci
 45:   14054838          0   PCI-MSI-edge      eth0-rx-0
 46:    9213934          0   PCI-MSI-edge      eth0-tx-0
 47:          2          0   PCI-MSI-edge      eth0
 48:      86095    9315103   PCI-MSI-edge      eth1-rx-0
 49:      29026   12455531   PCI-MSI-edge      eth1-tx-0
 50:          2          0   PCI-MSI-edge      eth1
 54:     189364          0   PCI-MSI-edge      eth3-rx-0
 55:     228140          0   PCI-MSI-edge      eth3-tx-0
 56:         10          0   PCI-MSI-edge      eth3
NMI:          0          0   Non-maskable interrupts
LOC:         59    8577359   Local timer interrupts
SPU:          0          0   Spurious interrupts
PMI:          0          0   Performance monitoring interrupts
IWI:          0          0   IRQ work interrupts
RTR:          0          0   APIC ICR read retries
RES:      19124      21141   Rescheduling interrupts
CAL:      35507      42339   Function call interrupts
TLB:          0          0   TLB shootdowns
TRM:          0          0   Thermal event interrupts
THR:          0          0   Threshold APIC interrupts
MCE:          0          0   Machine check exceptions
MCP:        286        286   Machine check polls
ERR:          0
MIS:          0

I think the strangest thing is that the performance of the local
networking, as in when the box is transferring things itself,
its pretty slow. Machines on the inside of the network however
do just fine, even accessing external sites, I tend to get my full
rated 50/3. Its just the soekris that doesn't.

Things seem to work better with the stock debian 2.6.32 kernel.
But I haven't throughly tested that.

Some more possibly useless info:

eth0 is the WAN connection
eth1 is LAN
eth3 is Wifi-LAN

eth1 and eth3 are in a plain bridge config.
I'm using shorewall to manage my firewall.

It's storage is a 32G Sandisk P4 3 mSATA flash card.
lshw stalls for a while when scanning pci over sysfs. The kernel
shows some odd messages over dmesg about PCI devices.

these ones are from an older kernel (not the one I'm currently running):

[    0.327863] pci 0000:02:00.0: BAR 6: no parent found for of device 
[0x98000000-0x9801ffff]
[    0.377380] pci 0000:02:06.0: BAR 6: no parent found for of device 
[0x98000000-0x9801ffff]
[    1.741414] Couldn't register serial port 0000:02:0a.4: -28
[    6.087764] sdhci-pci 0000:02:04.1: Invalid iomem size. You may experience 
problems.

I'm assuming the sdhci bits are because it isn't hooked up at all.
The reason it doesn't show up at all on my current kernel is I didn't
include the driver in this config.

pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]
pci 0000:02:00.0: no compatible bridge window for [mem 0x98000000-0x9801ffff 
pref]
pci 0000:02:06.0: no compatible bridge window for [mem 0x98000000-0x9801ffff 
pref]
vmalloc: allocation failure: 0 bytes
modprobe: page allocation failure: order:0, mode:0xd2

It seems the second and third items there are the sdhci device again,
probably not useful information.

> Regards,
> 
> --
> Luc Michel
> _______________________________________________
> Soekris-tech mailing list
> [email protected]
> http://lists.soekris.com/mailman/listinfo/soekris-tech


-- 
Thomas Fjellstrom
[email protected]
_______________________________________________
Soekris-tech mailing list
[email protected]
http://lists.soekris.com/mailman/listinfo/soekris-tech

Reply via email to