Opened 3 years ago
Closed 19 months ago
#17272 closed bug (fixed)
Slow network transfer
| Reported by: | jens | Owned by: | nobody |
|---|---|---|---|
| Priority: | normal | Milestone: | Unscheduled |
| Component: | Drivers/Network/ipro1000 | Version: | R1/beta3 |
| Keywords: | Cc: | mmlr | |
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
This is similar to #14344.
- ping to google is fine
- curl to google is very slow (minutes)
- package updater times out
- direct wired connection to router
- both with DHCP enabled or disabled
- with Google's DNS servers (8.8.8.8 and 8.8.4.4)
- a Debian installation on the same machine works fine
This is a fresh install from haiku-r1beta3-x86_64-anyboot.iso , and the machine is a Lenovo ThinkCentre 7360 whp. I can provide logs and information about the chipset as required. This machine has #4555 as well, in case it is a chipset problem.
Attachments (2)
Change History (36)
comment:1 by , 3 years ago
comment:2 by , 3 years ago
Please check your CPU usage: Is the machine using a lot even at idle? (Where is it going if so?)
comment:3 by , 3 years ago
| Component: | Network & Internet/IPv4 → Drivers/Network/ipro1000 |
|---|---|
| Owner: | changed from to |
Looks like Lenovo ThinkCentre 7360 whp uses intel 82567LM nic.
comment:4 by , 3 years ago
Updated to haiku-master-hrev55436-x86_64-anyboot.zip CPU are idle from what I can tell. This is directly after boot. The curl was successful once, but I didn't time that. After that it timed out.
comment:5 by , 3 years ago
Probably related to More than 99% interrupts of vector 16 are unhandled message.
comment:6 by , 3 years ago
Please enter KDL using /bin/kernel_debugger and type ints followed by es to exit KDL. After a few seconds output of ints should be written to the end of the syslog. You can then post this output here.
comment:7 by , 3 years ago
Extra info: previously fixed but related issues:
comment:8 by , 3 years ago
The kernel debugger draws some white space at the top of the screen and freezes right away, both if I start it from /bin/kernel_debugger and with Alt-Sysreq-D. (I can interact with the kernel debugger during boot without problem.)
comment:9 by , 3 years ago
In this case try to blacklist usb_keyboard kernel add-on in the bootloader and try again.
comment:10 by , 3 years ago
Although, if you can interact with KDL during boot that could be enough to get ints output.
comment:11 by , 3 years ago
"ints" during boot:
KERN: kdebug> intsint 219, enabled 1, handled 0, unhandled 0 KERN: kernel_x86_64:_ZL20apic_timer_interruptPv (0xffffffff80165780), data 0x0000000000000000, handled 0 KERN: KERN: int 221, enabled 1, handled 0, unhandled 0 KERN: kernel_x86_64:_ZL17x86_ici_interruptPv (0xffffffff8015dfe0), data 0x0000000000000000, handled 0 KERN: KERN: int 222, enabled 1, handled 0, unhandled 0 KERN: kernel_x86_64:_ZL23x86_smp_error_interruptPv (0xffffffff8015e000), data 0x0000000000000000, handled 0 KERN: KERN: int 223, enabled 1, handled 0, unhandled 0 KERN: kernel_x86_64:_ZL22x86_spurious_interruptPv (0xffffffff8015dfd0), data 0x0000000000000000, handled 0 KERN: KERN: kdebug> coACPI: Enabled 13 GPEs in block 00 to 3F
Do you have the path to usb_keyboard? I dug around in the menues a bit, but I am not familiar with the OS architecture. I found the usb_hid driver, but that disabled all input. The hardware doesn't have a legacy PS/2 connector, so I can't try that.
comment:12 by , 3 years ago
It shows 0 unhandled interrupts, probably this is to early.
find /system/add-ons/ -name usb_keyboard /system/add-ons/kernel/debugger/usb_keyboard
Version 0, edited 3 years ago by (next)
comment:13 by , 3 years ago
With usb_keyboard disabled I get the debugger startup message, but all input freezes. As far as I can see there is no legacy PS/2 emulation option in the bios.
I could try a serial terminal if that helps, but I'll need to get an appropriate cable.
Or can the kernel debugger execute commands from a file?
follow-up: 15 comment:14 by , 3 years ago
With usb_keyboard disabled I get the debugger startup message, but all input freezes.
Did you invoke KDL with kernel_debugger or with Alt-SysReq-D?
I could try a serial terminal if that helps
This should help, yes.
Or can the kernel debugger execute commands from a file?
It can't but this sounds like a handy feature to have it it's possible.
comment:15 by , 3 years ago
Replying to diver:
With usb_keyboard disabled I get the debugger startup message, but all input freezes.
Did you invoke KDL with
kernel_debuggeror withAlt-SysReq-D?
I used /bin/kernel_debugger.
comment:16 by , 3 years ago
Ok, with a serial cable attached I was able to do "ints":
kdebug> ints int 1, enabled 1, handled 1, unhandled 1 ps2:_ZL13ps2_interruptPv (0xffffffff81a35900), data 0x0000000000000000, handled 1 int 2, enabled 0, handled 0, unhandled 0 kernel_x86_64:_ZL30ioapic_source_override_handlerPv (0xffffffff801629b0), data 0x0000000000000000, handled 0 int 9, enabled 1, handled 0, unhandled 0 acpi:AcpiEvSciXruptHandler (0xffffffff814c00e0), data 0xffffffff82279ac0, handled 0 int 12, enabled 1, handled 1, unhandled 0 ps2:_ZL13ps2_interruptPv (0xffffffff81a35900), data 0x0000000000000000, handled 1 int 16, enabled 3, handled 0, unhandled 71138001 ehci:_ZN4EHCI16InterruptHandlerEPv (0xffffffff81906200), data 0xffffffff8260ce00, handled 0 uhci:_ZN4UHCI16InterruptHandlerEPv (0xffffffff81948670), data 0xffffffff824fd600, handled 0 uhci:_ZN4UHCI16InterruptHandlerEPv (0xffffffff81948670), data 0xffffffff824fdc00, handled 0 int 17, enabled 2, handled 0, unhandled 0 uhci:_ZN4UHCI16InterruptHandlerEPv (0xffffffff81948670), data 0xffffffff824fd400, handled 0 uhci:_ZN4UHCI16InterruptHandlerEPv (0xffffffff81948670), data 0xffffffff824fda00, handled 0 int 18, enabled 5, handled 996, unhandled 0 ata_adapter:_ZL19ata_adapter_inthandPv (0xffffffff81512d90), data 0xffffffff82604340, handled 0 ata_adapter:_ZL19ata_adapter_inthandPv (0xffffffff81512d90), data 0xffffffff82604390, handled 0 ehci:_ZN4EHCI16InterruptHandlerEPv (0xffffffff81906200), data 0xffffffff824fd000, handled 0 uhci:_ZN4UHCI16InterruptHandlerEPv (0xffffffff81948670), data 0xffffffff824fd200, handled 996 uhci:_ZN4UHCI16InterruptHandlerEPv (0xffffffff81948670), data 0xffffffff824fd800, handled 0 int 24, enabled 1, handled 10321, unhandled 0 ahci:_ZN14AHCIController9InterruptEPv (0xffffffff814fcf30), data 0xffffffff82269900, handled 10321 int 25, enabled 1, handled 29056, unhandled 1 intel_extreme:_ZL23intel_interrupt_handlerPv (0xffffffff81659160), data 0xffffffff8249ed90, handled 29056 int 26, enabled 1, handled 446, unhandled 0 ipro1000:iflib_fast_intr_rxtx (0xffffffff8a73fe20), data 0xffffffff822bfca0, handled 446 int 27, enabled 1, handled 15292, unhandled 2 hda:_ZL21hda_interrupt_handlerP14hda_controller (0xffffffff81ac35c0), data 0xffffffff81acc280, handled 15292 int 219, enabled 1, handled 215308, unhandled 0 kernel_x86_64:_ZL20apic_timer_interruptPv (0xffffffff80165780), data 0x0000000000000000, handled 215305 int 221, enabled 1, handled 68587, unhandled 0 kernel_x86_64:_ZL17x86_ici_interruptPv (0xffffffff8015dfe0), data 0x0000000000000000, handled 68587 int 222, enabled 1, handled 0, unhandled 0 kernel_x86_64:_ZL23x86_smp_error_interruptPv (0xffffffff8015e000), data 0x0000000000000000, handled 0 int 223, enabled 1, handled 0, unhandled 0 kernel_x86_64:_ZL22x86_spurious_interruptPv (0xffffffff8015dfd0), data 0x0000000000000000, handled 0
This is after a "ping google" "curl google".
follow-up: 25 comment:17 by , 3 years ago
So I guess it could be an usb related interrupt storm:
int 16, enabled 3, handled 0, unhandled 71138001 ehci:_ZN4EHCI16InterruptHandlerEPv (0xffffffff81906200), data 0xffffffff8260ce00, handled 0 uhci:_ZN4UHCI16InterruptHandlerEPv (0xffffffff81948670), data 0xffffffff824fd600, handled 0 uhci:_ZN4UHCI16InterruptHandlerEPv (0xffffffff81948670), data 0xffffffff824fdc00, handled 0
You can try to blacklist ehci and uhci (or both) drivers and see if this changes anything.
comment:18 by , 3 years ago
After blacklisting maybe you could also check for bios/firmware updates as a long shot (even though Debian works).
follow-up: 20 comment:19 by , 3 years ago
blacklisting ehci: no difference
blacklisting uhci: no mouse control, so can't launch programs
kdebug> ints int 1, enabled 1, handled 60, unhandled 0, ACTIVE ps2:_ZL13ps2_interruptPv (0xffffffff81b39900), data 0x0000000000000000, handled 60 int 2, enabled 0, handled 0, unhandled 0 kernel_x86_64:_ZL30ioapic_source_override_handlerPv (0xffffffff801629b0), data 0x0000000000000000, handled 0 int 9, enabled 1, handled 0, unhandled 0 acpi:AcpiEvSciXruptHandler (0xffffffff814c00e0), data 0xffffffff82272ac0, handled 0 int 12, enabled 1, handled 2466, unhandled 0 ps2:_ZL13ps2_interruptPv (0xffffffff81b39900), data 0x0000000000000000, handled 2466 int 16, enabled -100, handled 0, unhandled 10001 ehci:_ZN4EHCI16InterruptHandlerEPv (0xffffffff81906200), data 0xffffffff82262800, handled 0 int 18, enabled 3, handled 0, unhandled 0 ata_adapter:_ZL19ata_adapter_inthandPv (0xffffffff81512d90), data 0xffffffff82600de0, handled 0 ata_adapter:_ZL19ata_adapter_inthandPv (0xffffffff81512d90), data 0xffffffff82600e30, handled 0 ehci:_ZN4EHCI16InterruptHandlerEPv (0xffffffff81906200), data 0xffffffff82262a00, handled 0 int 24, enabled 1, handled 9015, unhandled 0 ahci:_ZN14AHCIController9InterruptEPv (0xffffffff814fcf30), data 0xffffffff82261900, handled 9015 int 25, enabled 1, handled 6427, unhandled 0 intel_extreme:_ZL23intel_interrupt_handlerPv (0xffffffff8198f160), data 0xffffffff8b4dc708, handled 6427 int 26, enabled 1, handled 67, unhandled 0 ipro1000:iflib_fast_intr_rxtx (0xffffffff8a73fe20), data 0xffffffff822b34a0, handled 67 int 27, enabled 1, handled 3538, unhandled 0 hda:_ZL21hda_interrupt_handlerP14hda_controller (0xffffffff8a7d15c0), data 0xffffffff8a7da280, handled 3538 int 219, enabled 1, handled 52076, unhandled 0 kernel_x86_64:_ZL20apic_timer_interruptPv (0xffffffff80165780), data 0x0000000000000000, handled 52076 int 221, enabled 1, handled 40184, unhandled 0 kernel_x86_64:_ZL17x86_ici_interruptPv (0xffffffff8015dfe0), data 0x0000000000000000, handled 40184 int 222, enabled 1, handled 0, unhandled 0 kernel_x86_64:_ZL23x86_smp_error_interruptPv (0xffffffff8015e000), data 0x0000000000000000, handled 0 int 223, enabled 1, handled 0, unhandled 0 kernel_x86_64:_ZL22x86_spurious_interruptPv (0xffffffff8015dfd0), data 0x0000000000000000, handled 0
There may be a bios update, but I have to work out what version I have right now, and how I can write it to a floppy ... if I even have a floppy somewhere.
follow-up: 26 comment:20 by , 3 years ago
You can try to setup openssh access and blacklist uhci driver.
comment:21 by , 3 years ago
Made a freedos usb drive and flashed the latest bios from Lenovo's website, but get no difference.
comment:22 by , 3 years ago
I considered that, wouldn't that run into network problems as well? I'll try tomorrow.
comment:23 by , 3 years ago
If ehci or uhci drivers are the cause (and you blacklisted them) you shouldn't run into network problems hopefully.
comment:24 by , 3 years ago
| Cc: | added |
|---|
comment:25 by , 3 years ago
Replying to diver:
So I guess it could be an usb related interrupt storm:
int 16, enabled 3, handled 0, unhandled 71138001 ehci:_ZN4EHCI16InterruptHandlerEPv (0xffffffff81906200), data 0xffffffff8260ce00, handled 0 uhci:_ZN4UHCI16InterruptHandlerEPv (0xffffffff81948670), data 0xffffffff824fd600, handled 0 uhci:_ZN4UHCI16InterruptHandlerEPv (0xffffffff81948670), data 0xffffffff824fdc00, handled 0You can try to blacklist
ehcianduhci(or both) drivers and see if this changes anything.
Note that the global interrupt 16 is shared between PCI device 0:25 (the network controller) and 0:26 (the USB controllers). Given the context, I'd say the problem is with the network controller.
The driver attaches relatively late and then switches interrupts to MSI 26, where we see the handler in the ints output with some handled interrupts.
It looks to me like there are interrupts happening during boot which go unhandled while the driver is not yet attached and they may just stop after that. Can get the output of ints a couple of times, continuing each time and using the network? Just to see if the unhandled interrupts actually continue to increase after the driver switched to MSI.
Turning off network booting in the firmware might work around the problem as that might leave the network controller uninitialized.
If it isn't an interrupt issue, then the original problem description sounds a lot like an MTU issue. Can you try reducing the MTU with ifconfig /dev/net/... mtu 1400 and see if that makes a difference?
comment:26 by , 3 years ago
Replying to diver:
You can try to setup openssh access and blacklist
uhcidriver.
Ok, configured sshd, blacklisted uhci, logged in with ssh, did a 'curl google.com'. First one took a long time but succeeded, second one timed out.
opened debugger, ints:
int 16, enabled -100, handled 0, unhandled 10001 ehci:_ZN4EHCI16InterruptHandlerEPv (0xffffffff81906200), data 0xffffffff82262800, handled 0
another curl, timed out, ints:
int 16, enabled -100, handled 0, unhandled 10001 ehci:_ZN4EHCI16InterruptHandlerEPv (0xffffffff81906200), data 0xffffffff82262800, handled 0
(so no additional interrupts?)
another curl, another ints:
int 16, enabled -100, handled 0, unhandled 10001 ehci:_ZN4EHCI16InterruptHandlerEPv (0xffffffff81906200), data 0xffffffff82262800, handled 0
Disabled net-boot in the BIOS (if you mean that), booted normally, curl:
int 16, enabled 3, handled 0, unhandled 40843059 ehci:_ZN4EHCI16InterruptHandlerEPv (0xffffffff81906200), data 0xffffffff8260de00, handled 0 uhci:_ZN4UHCI16InterruptHandlerEPv (0xffffffff81948670), data 0xffffffff824fd600, handled 0 uhci:_ZN4UHCI16InterruptHandlerEPv (0xffffffff81948670), data 0xffffffff824fdc00, handled 0
another curl
int 16, enabled 3, handled 0, unhandled 72871017 ehci:_ZN4EHCI16InterruptHandlerEPv (0xffffffff81906200), data 0xffffffff8260de00, handled 0 uhci:_ZN4UHCI16InterruptHandlerEPv (0xffffffff81948670), data 0xffffffff824fd600, handled 0 uhci:_ZN4UHCI16InterruptHandlerEPv (0xffffffff81948670), data 0xffffffff824fdc00, handled 0
comment:27 by , 3 years ago
Disabled both ehci and uhci, same problem, ints:
kdebug> ints int 1, enabled 1, handled 25, unhandled 0, ACTIVE ps2:_ZL13ps2_interruptPv (0xffffffff81a39900), data 0x0000000000000000, handled 25 int 2, enabled 0, handled 0, unhandled 0 kernel_x86_64:_ZL30ioapic_source_override_handlerPv (0xffffffff801629b0), data 0x0000000000000000, handled 0 int 9, enabled 1, handled 0, unhandled 0 acpi:AcpiEvSciXruptHandler (0xffffffff814c00e0), data 0xffffffff8226aac0, handled 0 int 12, enabled 1, handled 267, unhandled 0 ps2:_ZL13ps2_interruptPv (0xffffffff81a39900), data 0x0000000000000000, handled 267 int 18, enabled 2, handled 0, unhandled 0 ata_adapter:_ZL19ata_adapter_inthandPv (0xffffffff81512d90), data 0xffffffff824e5ed0, handled 0 ata_adapter:_ZL19ata_adapter_inthandPv (0xffffffff81512d90), data 0xffffffff824e5f20, handled 0 int 24, enabled 1, handled 9065, unhandled 0 ahci:_ZN14AHCIController9InterruptEPv (0xffffffff814fcf30), data 0xffffffff82259900, handled 9065 int 25, enabled 1, handled 5783, unhandled 0 intel_extreme:_ZL23intel_interrupt_handlerPv (0xffffffff81659160), data 0xffffffff8ac62d98, handled 5783 int 26, enabled 1, handled 376, unhandled 0 ipro1000:iflib_fast_intr_rxtx (0xffffffff89d3de20), data 0xffffffff822b48a0, handled 376 int 27, enabled 1, handled 3196, unhandled 0 hda:_ZL21hda_interrupt_handlerP14hda_controller (0xffffffff811425c0), data 0xffffffff8114b280, handled 3196 int 219, enabled 1, handled 40345, unhandled 0 kernel_x86_64:_ZL20apic_timer_interruptPv (0xffffffff80165780), data 0x0000000000000000, handled 40345 int 221, enabled 1, handled 37399, unhandled 0 kernel_x86_64:_ZL17x86_ici_interruptPv (0xffffffff8015dfe0), data 0x0000000000000000, handled 37399 int 222, enabled 1, handled 0, unhandled 0 kernel_x86_64:_ZL23x86_smp_error_interruptPv (0xffffffff8015e000), data 0x0000000000000000, handled 0 int 223, enabled 1, handled 0, unhandled 0 kernel_x86_64:_ZL22x86_spurious_interruptPv (0xffffffff8015dfd0), data 0x0000000000000000, handled 0
comment:28 by , 3 years ago
IIRC turning off ACPI in the bootloader also turns off MSI. See if that changes anything.
comment:29 by , 3 years ago
That doesn't boot past the startup screen. All the icons light up, but nothing after the last one. last few lines of the serial console:
package_daemon [14313807: 119] active package: "mesa_devel-17.1.10-6-x86_64.hpkg" package_daemon [14321163: 119] active package: "libpcre-8.44-1-x86_64.hpkg" package_daemon [14328036: 119] active package: "lcms-2.12-1-x86_64.hpkg" package_daemon [14334578: 119] active package: "git-2.30.2-2-x86_64.hpkg" package_daemon [14341289: 119] active package: "curl-7.76.1-1-x86_64.hpkg" package_daemon [14347999: 119] The latest volume state is also the currently active one package_daemon [14355925: 119] Volume::InitialVerify((nil), (nil)) package_daemon [14418876: 119] More than 99% interrupts of vector 11 are unhandled Volume::InitialVerify(): volume at "/boot/system" is consistent package_daemon [14432645: 119] Failed to open packages activation file /boot/home/config/packages/administrative/activated-packages: No such file or directory package_daemon [14446518: 119] Failed to get activated packages info from activated packages file. Assuming all package files in package directory are activated. package_daemon [14460840: 119] latest volume state: package_daemon [14465552: 119] The latest volume state is also the currently active one package_daemon [14473463: 119] Volume::InitialVerify(0x120a619b5c20, (nil)) package_daemon [14483358: 119] Volume::InitialVerify(): volume at "/boot/home/config" is consistent More than 99% interrupts of vector 11 are unhandled
Interestingly I don't have the NMI from #4555 during startup.
comment:30 by , 3 years ago
The one where the unhandled interrupts don't increase only stopped because the interrupt vector is disabled as it is not shared by multiple drivers anymore. In the other trace it clearly still increases.
Can you dump the PCI info in KDL as well to check what the interrupt status of the network controller is?
Did you also try the MTU setting?
comment:31 by , 3 years ago
Tried the mtu setting this morning, no difference.
Do you mean this?
kdebug> pcistatus domain 0, bus 0, dev 0, func 0, PCI device status 0x3090 Received Master-Abort Received Target-Abort domain 0, bus 0, dev 2, func 0, PCI device status 0x0090 domain 0, bus 0, dev 2, func 1, PCI device status 0x0090 domain 0, bus 0, dev 3, func 0, PCI device status 0x0018 domain 0, bus 0, dev 3, func 2, PCI device status 0x00b0 domain 0, bus 0, dev 3, func 3, PCI device status 0x00b0 domain 0, bus 0, dev 25, func 0, PCI device status 0x0018 domain 0, bus 0, dev 26, func 0, PCI device status 0x0290 domain 0, bus 0, dev 26, func 1, PCI device status 0x0290 domain 0, bus 0, dev 26, func 2, PCI device status 0x0290 domain 0, bus 0, dev 26, func 7, PCI device status 0x0290 domain 0, bus 0, dev 27, func 0, PCI device status 0x0010 domain 0, bus 0, dev 29, func 0, PCI device status 0x0290 domain 0, bus 0, dev 29, func 1, PCI device status 0x0290 domain 0, bus 0, dev 29, func 2, PCI device status 0x0290 domain 0, bus 0, dev 29, func 7, PCI device status 0x0290 domain 0, bus 0, dev 30, func 0, PCI device status 0x4810 Signalled System Error Signalled Target-Abort domain 0, bus 0, dev 30, func 0, PCI bridge secondary status 0x2280 Received Master-Abort domain 0, bus 0, dev 30, func 0, PCI bridge control 0x0827 domain 0, bus 0, dev 31, func 0, PCI device status 0x0210 domain 0, bus 0, dev 31, func 2, PCI device status 0x02b0 domain 0, bus 0, dev 31, func 3, PCI device status 0x0280 kdebug> pcirefresh PCI: [dom 0, bus 0] bus 0, device 0, function 0: vendor 8086, device 2e10, revision 03 KERN: PCI: class_base 06, class_function 00, class_api 00 KERN: PCI: vendor 8086: Intel Corporation KERN: PCI: device 2e10: 4 Series Chipset DRAM Controller KERN: PCI: info: Bridge (Host bridge) KERN: PCI: line_size 00, latency 00, header_type 00, BIST 00 KERN: PCI: ROM base host 00000000, pci 00000000, size 00000000 KERN: PCI: cardbus_CIS 00000000, subsystem_id 3048, subsystem_vendor_id 17aa KERN: PCI: interrupt_line 00, interrupt_pin 00, min_grant 00, max_latency 00 KERN: PCI: base reg 0: host 00000000, pci 00000000, size 00000000, flags 00 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: vendspec KERN: PCI: [dom 0, bus 0] bus 0, device 2, function 0: vendor 8086, device 2e12, revision 03 KERN: PCI: class_base 03, class_function 00, class_api 00 KERN: PCI: vendor 8086: Intel Corporation KERN: PCI: device 2e12: 4 Series Chipset Integrated Graphics Controller (ThinkCentre M6258) KERN: PCI: info: Display controller (VGA compatible controller, VGA controller) KERN: PCI: line_size 00, latency 00, header_type 80, BIST 00 KERN: PCI: ROM base host 00000000, pci 00000000, size 00000000 KERN: PCI: cardbus_CIS 00000000, subsystem_id 3048, subsystem_vendor_id 17aa KERN: PCI: interrupt_line 10, interrupt_pin 01, min_grant 00, max_latency 00 KERN: PCI: base reg 0: host fc000000, pci fc000000, size 00400000, flags 04 KERN: PCI: base reg 1: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 2: host e0000000, pci e0000000, size 10000000, flags 0c KERN: PCI: base reg 3: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 4: host 00001c70, pci 00001c70, size 00000008, flags 01 KERN: PCI: base reg 5: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: Capabilities: MSI, PM KERN: PCI: [dom 0, bus 0] bus 0, device 2, function 1: vendor 8086, device 2e13, revision 03 KERN: PCI: class_base 03, class_function 80, class_api 00 KERN: PCI: vendor 8086: Intel Corporation KERN: PCI: device 2e13: 4 Series Chipset Integrated Graphics Controller KERN: PCI: info: Display controller KERN: PCI: line_size 00, latency 00, header_type 80, BIST 00 KERN: PCI: ROM base host 00000000, pci 00000000, size 00000000 KERN: PCI: cardbus_CIS 00000000, subsystem_id 3048, subsystem_vendor_id 17aa KERN: PCI: interrupt_line 00, interrupt_pin 00, min_grant 00, max_latency 00 KERN: PCI: base reg 0: host fc400000, pci fc400000, size 00100000, 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 KERN: PCI: [dom 0, bus 0] bus 0, device 3, function 0: vendor 8086, device 2e14, revision 03 KERN: PCI: class_base 07, class_function 80, class_api 00 KERN: PCI: vendor 8086: Intel Corporation KERN: PCI: device 2e14: 4 Series Chipset HECI Controller KERN: PCI: info: Communication controller KERN: PCI: line_size 00, latency 00, header_type 80, BIST 00 KERN: PCI: ROM base host 00000000, pci 00000000, size 00000000 KERN: PCI: cardbus_CIS 00000000, subsystem_id 3048, subsystem_vendor_id 17aa KERN: PCI: interrupt_line 10, interrupt_pin 01, min_grant 00, max_latency 00 KERN: PCI: base reg 0: host fc524000, pci fc524000, size 00000010, 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 KERN: PCI: [dom 0, bus 0] bus 0, device 3, function 2: vendor 8086, device 2e16, revision 03 KERN: PCI: class_base 01, class_function 01, class_api 85 KERN: PCI: vendor 8086: Intel Corporation KERN: PCI: device 2e16: 4 Series Chipset PT IDER Controller KERN: PCI: info: Mass storage controller (IDE interface, PCI native mode-only co KERN: PCI: line_size 00, latency 00, header_type 00, BIST 00 KERN: PCI: ROM base host 00000000, pci 00000000, size 00000000 KERN: PCI: cardbus_CIS 00000000, subsystem_id 3048, subsystem_vendor_id 17aa KERN: PCI: interrupt_line 12, interrupt_pin 03, min_grant 00, max_latency 00 KERN: PCI: base reg 0: host 00001c88, pci 00001c88, size 00000008, flags 01 KERN: PCI: base reg 1: host 00001c7c, pci 00001c7c, size 00000004, flags 01 KERN: PCI: base reg 2: host 00001c80, pci 00001c80, size 00000008, flags 01 KERN: PCI: base reg 3: host 00001c78, pci 00001c78, size 00000004, flags 01 KERN: PCI: base reg 4: host 00001c40, pci 00001c40, size 00000010, flags 01 KERN: PCI: base reg 5: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: Capabilities: PM, MSI KERN: PCI: [dom 0, bus 0] bus 0, device 3, function 3: vendor 8086, device 2e17, revision 03 KERN: PCI: class_base 07, class_function 00, class_api 02 KERN: PCI: vendor 8086: Intel Corporation KERN: PCI: device 2e17: 4 Series Chipset Serial KT Controller KERN: PCI: info: Communication controller (Serial controller, 16550) KERN: PCI: line_size 00, latency 00, header_type 00, BIST 00 KERN: PCI: ROM base host 00000000, pci 00000000, size 00000000 KERN: PCI: cardbus_CIS 00000000, subsystem_id 3048, subsystem_vendor_id 17aa KERN: PCI: interrupt_line 11, interrupt_pin 02, min_grant 00, max_latency 00 KERN: PCI: base reg 0: host 00001c90, pci 00001c90, size 00000008, flags 01 KERN: PCI: base reg 1: host fc526000, pci fc526000, size 00001000, 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 KERN: PCI: [dom 0, bus 0] bus 0, device 25, function 0: vendor 8086, device 10de, revision 02 KERN: PCI: class_base 02, class_function 00, class_api 00 KERN: PCI: vendor 8086: Intel Corporation KERN: PCI: device 10de: 82567LM-3 Gigabit Network Connection KERN: PCI: info: Network controller (Ethernet controller) KERN: PCI: line_size 00, latency 00, header_type 00, BIST 00 KERN: PCI: ROM base host 00000000, pci 00000000, size 00000000 KERN: PCI: cardbus_CIS 00000000, subsystem_id 3048, subsystem_vendor_id 17aa KERN: PCI: interrupt_line 10, interrupt_pin 01, min_grant 00, max_latency 00 KERN: PCI: base reg 0: host fc500000, pci fc500000, size 00020000, flags 00 KERN: PCI: base reg 1: host fc527000, pci fc527000, size 00001000, flags 00 KERN: PCI: base reg 2: host 00001820, pci 00001820, size 00000020, flags 01 KERN: PCI: base reg 3: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 4: host 00000000, pcKERN: i 00000000, size 00000000, flags 00 KERN: PCI: base reg 5: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: Capabilities: PM, MSI, AdvancedFeatures KERN: PCI: [dom 0, bus 0] bus 0, device 26, function 0: vendor 8086, device 3a67, revision 02 KERN: PCI: class_base 0c, class_function 03, class_api 00 KERN: PCI: vendor 8086: Intel Corporation KERN: PCI: device 3a67: 82801JD/DO (ICH10 Family) USB UHCI Controller #4 KERN: PCI: info: Serial bus controller (USB controller, UHCI) KERN: PCI: line_size 00, latency 00, header_type 80, BIST 00 KERN: PCI: ROM base host 00000000, pci 00000000, size 00000000 KERN: PCI: cardbus_CIS 00000000, subsystem_id 3048, subsystem_vendor_id 17aa KERN: PCI: interrupt_line 10, interrupt_pin 01, min_grant 00, max_latency 00 KERN: PCI: base reg 0: host 00000000, pci 00000000, size 00000000, flags 00 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 00001840, pci 00001840, size 00000020, flags 01 KERN: PCI: base reg 5: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: Capabilities: AdvancedFeatures KERN: PCI: [dom 0, bus 0] bus 0, device 26, function 1: vendor 8086, device 3a68, revision 02 KERN: PCI: class_base 0c, class_function 03, class_api 00 KERN: PCI: vendor 8086: Intel Corporation KERN: PCI: device 3a68: 82801JD/DO (ICH10 Family) USB UHCI Controller #5 KERN: PCI: info: Serial bus controller (USB controller, UHCI) KERN: PCI: line_size 00, latency 00, header_type 00, BIST 00 KERN: PCI: ROM base host 00000000, pci 00000000, size 00000000 KERN: PCI: cardbus_CIS 00000000, subsystem_id 3048, subsystem_vendor_id 17aa KERN: PCI: interrupt_line 11, interrupt_pin 02, min_grant 00, max_latency 00 KERN: PCI: base reg 0: host 00000000, pci 00000000, size 00000000, flags 00 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 00001860, pci 00001860, size 00000020, flags 01 KERN: PCI: base reg 5: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: Capabilities: AdvancedFeatures KERN: PCI: [dom 0, bus 0] bus 0, device 26, function 2: vendor 8086, device 3a69, revision 02 KERN: PCI: class_base 0c, class_function 03, class_api 00 KERN: PCI: vendor 8086: Intel Corporation KERN: PCI: device 3a69: 82801JD/DO (ICH10 Family) USB UHCI Controller #6 KERN: PCI: info: Serial bus controller (USB controller, UHCI) KERN: PCI: line_size 00, latency 00, header_type 00, BIST 00 KERN: PCI: ROM base host 00000000, pci 00000000, size 00000000 KERN: PCI: cardbus_CIS 00000000, subsystem_id 3048, subsystem_vendor_id 17aa KERN: PCI: interrupt_line 12, interrupt_pin 03, min_grant 00, max_latency 00 KERN: PCI: base reg 0: host 00000000, pci 00000000, size 00000000, flags 00 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 00001880, pci 00001880, size 00000020, flags 01 KERN: PCI: base reg 5: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: Capabilities: AdvancedFeatures KERN: PCI: [dom 0, bus 0] bus 0, device 26, function 7: vendor 8086, device 3a6c, revision 02 KERN: PCI: class_base 0c, class_function 03, class_api 20 KERN: PCI: vendor 8086: Intel Corporation KERN: PCI: device 3a6c: 82801JD/DO (ICH10 Family) USB2 EHCI Controller #2 KERN: PCI: info: Serial bus controller (USB controller, EHCI) KERN: PCI: line_size 00, latency 00, header_type 00, BIST 00 KERN: PCI: ROM base host 00000000, pci 00000000, size 00000000 KERN: PCI: cardbus_CIS 00000000, subsystem_id 3048, subsystem_vendor_id 17aa KERN: PCI: interrupt_line 12, interrupt_pin 03, min_grant 00, max_latency 00 KERN: PCI: base reg 0: host fc528000, pci fc528000, size 00000400, flags 00 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, DebugPort, AdvancedFeatures KERN: PCI: [dom 0, bus 0] bus 0, device 27, function 0: vendor 8086, device 3a6e, revision 02 KERN: PCI: class_base 04, class_function 03, class_api 00 KERN: PCI: vendor 8086: Intel Corporation KERN: PCI: device 3a6e: 82801JD/DO (ICH10 Family) HD Audio Controller KERN: PCI: info: Multimedia controller (Audio device) KERN: PCI: line_size 08, latency 00, header_type 00, BIST 00 KERN: PCI: ROM base host 00000000, pci 00000000, size 00000000 KERN: PCI: cardbus_CIS 00000000, subsystem_id 3048, subsystem_vendor_id 17aa KERN: PCI: interrupt_line 10, interrupt_pin 01, min_grant 00, max_latency 00 KERN: PCI: base reg 0: host fc520000, pci fc520000, size 00004000, 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: Virtual Channel, Root Complex Link Declaration KERN: PCI: [dom 0, bus 0] bus 0, device 29, function 0: vendor 8086, device 3a64, revision 02 KERN: PCI: class_base 0c, class_function 03, class_api 00 KERN: PCI: vendor 8086: Intel Corporation KERN: PCI: device 3a64: 82801JD/DO (ICH10 Family) USB UHCI Controller #1 KERN: PCI: info: Serial bus controller (USB controller, UHCI) KERN: PCI: line_size 00, latency 00, header_type 80, BIST 00 KERN: PCI: ROM base host 00000000, pci 00000000, size 00000000 KERN: PCI: cardbus_CIS 00000000, subsystem_id 3048, subsystem_vendor_id 17aa KERN: PCI: interrupt_line 10, interrupt_pin 01, min_grant 00, max_latency 00 KERN: PCI: base reg 0: host 00000000, pci 00000000, size 00000000, flags 00 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 000018a0, pci 000018a0, size 00000020, flags 01 KERN: PCI: base reg 5: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: Capabilities: AdvancedFeatures KERN: PCI: [dom 0, bus 0] bus 0, device 29, function 1: vendor 8086, device 3a65, revision 02 KERN: PCI: class_base 0c, class_function 03, class_api 00 KERN: PCI: vendor 8086: Intel Corporation KERN: PCI: device 3a65: 82801JD/DO (ICH10 Family) USB UHCI Controller #2 KERN: PCI: info: Serial bus controller (USB controller, UHCI) KERN: PCI: line_size 00, latency 00, header_type 00, BIST 00 KERN: PCI: ROM base host 00000000, pci 00000000, size 00000000 KERN: PCI: cardbus_CIS 00000000, subsystem_id 3048, subsystem_vendor_id 17aa KERN: PCI: interrupt_line 11, interrupt_pin 02, min_grant 00, max_latency 00 KERN: PCI: base reg 0: host 00000000, pci 00000000, size 00000000, flags 00 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 000018c0, pci 000018c0, size 00000020, flags 01 KERN: PCI: base reg 5: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: Capabilities: AdvancedFeatures KERN: PCI: [dom 0, bus 0] bus 0, device 29, function 2: vendor 8086, device 3a66, revision 02 KERN: PCI: class_base 0c, class_function 03, class_api 00 KERN: PCI: vendor 8086: Intel Corporation KERN: PCI: device 3a66: 82801JD/DO (ICH10 Family) USB UHCI Controller #3 KERN: PCI: info: Serial bus controller (USB controller, UHCI) KERN: PCI: line_size 00, latency 00, header_type 00, BIST 00 KERN: PCI: ROM base host 00000000, pci 00000000, size 00000000 KERN: PCI: cardbus_CIS 00000000, subsystem_id 3048, subsystem_vendor_id 17aa KERN: PCI: interrupt_line 12, interrupt_pin 03, min_grant 00, max_latency 00 KERN: PCI: base reg 0: host 0000KERN: 0000, pci 00000000, size 00000000, flags 00 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 000018e0, pci 000018e0, size 00000020, flags 01 KERN: PCI: base reg 5: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: Capabilities: AdvancedFeatures KERN: PCI: [dom 0, bus 0] bus 0, device 29, function 7: vendor 8086, device 3a6a, revision 02 KERN: PCI: class_base 0c, class_function 03, class_api 20 KERN: PCI: vendor 8086: Intel Corporation KERN: PCI: device 3a6a: 82801JD/DO (ICH10 Family) USB2 EHCI Controller #1 KERN: PCI: info: Serial bus controller (USB controller, EHCI) KERN: PCI: line_size 00, latency 00, header_type 00, BIST 00 KERN: PCI: ROM base host 00000000, pci 00000000, size 00000000 KERN: PCI: cardbus_CIS 00000000, subsystem_id 3048, subsystem_vendor_id 17aa KERN: PCI: interrupt_line 10, interrupt_pin 01, min_grant 00, max_latency 00 KERN: PCI: base reg 0: host fc529000, pci fc529000, size 00000400, flags 00 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, DebugPort, AdvancedFeatures KERN: PCI: [dom 0, bus 0] bus 0, device 30, function 0: vendor 8086, device 244e, revision a2 KERN: PCI: class_base 06, class_function 04, class_api 01 KERN: PCI: vendor 8086: Intel Corporation KERN: PCI: device 244e: 82801 PCI Bridge KERN: PCI: info: Bridge (PCI bridge, Subtractive decode) KERN: PCI: line_size 00, latency 00, header_type 01, BIST 00 KERN: PCI: subsystem_id 0000, subsystem_vendor_id 0050 KERN: PCI: primary_bus 00, secondary_bus 11, subordinate_bus 11, secondary_latency 20 KERN: PCI: I/O window f000-0fff KERN: PCI: memory window fff00000-000fffff KERN: PCI: prefetchable memory window 00000000fff00000-00000000000fffff KERN: PCI: bridge_control 0827, secondary_status 0280 KERN: PCI: interrupt_line ff, interrupt_pin 00 KERN: PCI: ROM base host 00000000, pci 00000000, size ?? KERN: PCI: base reg 0: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 1: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: Capabilities: subvendor KERN: PCI: [dom 0, bus 0] bus 0, device 31, function 0: vendor 8086, device 3a14, revision 02 KERN: PCI: class_base 06, class_function 01, class_api 00 KERN: PCI: vendor 8086: Intel Corporation KERN: PCI: device 3a14: 82801JDO (ICH10DO) LPC Interface Controller KERN: PCI: info: Bridge (ISA bridge) KERN: PCI: line_size 00, latency 00, header_type 80, BIST 00 KERN: PCI: ROM base host 00000000, pci 00000000, size 00000000 KERN: PCI: cardbus_CIS 00000000, subsystem_id 3048, subsystem_vendor_id 17aa KERN: PCI: interrupt_line 00, interrupt_pin 00, min_grant 00, max_latency 00 KERN: PCI: base reg 0: host 00000000, pci 00000000, size 00000000, flags 00 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: vendspec KERN: PCI: [dom 0, bus 0] bus 0, device 31, function 2: vendor 8086, device 3a02, revision 02 KERN: PCI: class_base 01, class_function 06, class_api 01 KERN: PCI: vendor 8086: Intel Corporation KERN: PCI: device 3a02: 82801JD/DO (ICH10 Family) SATA AHCI Controller KERN: PCI: info: Mass storage controller (SATA controller, AHCI 1.0) KERN: PCI: line_size 00, latency 00, header_type 00, BIST 00 KERN: PCI: ROM base host 00000000, pci 00000000, size 00000000 KERN: PCI: cardbus_CIS 00000000, subsystem_id 3048, subsystem_vendor_id 17aa KERN: PCI: interrupt_line 11, interrupt_pin 02, min_grant 00, max_latency 00 KERN: PCI: base reg 0: host 00001ca8, pci 00001ca8, size 00000008, flags 01 KERN: PCI: base reg 1: host 00001c9c, pci 00001c9c, size 00000004, flags 01 KERN: PCI: base reg 2: host 00001ca0, pci 00001ca0, size 00000008, flags 01 KERN: PCI: base reg 3: host 00001c98, pci 00001c98, size 00000004, flags 01 KERN: PCI: base reg 4: host 00001c00, pci 00001c00, size 00000020, flags 01 KERN: PCI: base reg 5: host fc52a000, pci fc52a000, size 00000800, flags 00 KERN: PCI: Capabilities: MSI, PM, SATA, AdvancedFeatures KERN: PCI: [dom 0, bus 0] bus 0, device 31, function 3: vendor 8086, device 3a60, revision 02 KERN: PCI: class_base 0c, class_function 05, class_api 00 KERN: PCI: vendor 8086: Intel Corporation KERN: PCI: device 3a60: 82801JD/DO (ICH10 Family) SMBus Controller KERN: PCI: info: Serial bus controller (SMBus) KERN: PCI: line_size 00, latency 00, header_type 00, BIST 00 KERN: PCI: ROM base host 00000000, pci 00000000, size 00000000 KERN: PCI: cardbus_CIS 00000000, subsystem_id 3048, subsystem_vendor_id 17aa KERN: PCI: interrupt_line 11, interrupt_pin 02, min_grant 00, max_latency 00 KERN: PCI: base reg 0: host fc52b000, pci fc52b000, size 00000100, 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 00001c20, pci 00001c20, size 00000020, flags 01 KERN: PCI: base reg 5: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: Capabilities: (not supported) KERN: kdebug> co
comment:33 by , 19 months ago
Sorry, I completely forgot about this... I found some time to test Version: R1/beta4 Release date: December 23, 2022, and I'm able to surf the web.
Note:
See TracTickets
for help on using tickets.
What model nic? Yes, please provide logs. It would be interesting if you could update to the nightlies and grab the logs from that since debug levels are higher.