RE: FW: [Bug 117] New: [KVM-IPF] RTL8139 emulated network card can not work

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Jes Sorensen wrote:
> Jes Sorensen wrote:
>> Now I am seeing this in my syslog:
>> 
>> Oct 10 07:21:34 a4700rac kernel: vcpu 5 irq check
>> Oct 10 07:21:34 a4700rac kernel: vcpu 3 irq check
>> Oct 10 07:21:34 a4700rac kernel: vcpu 2 irq check
>> Oct 10 07:21:34 a4700rac kernel: vcpu 5 irq check
>> Oct 10 07:21:34 a4700rac kernel: vcpu 3 irq check
>> Oct 10 07:21:34 a4700rac kernel: vcpu 2 irq check
>> Oct 10 07:21:34 a4700rac kernel: vcpu 5 irq check
>> Oct 10 07:21:34 a4700rac kernel: vcpu 3 irq check
>> Oct 10 07:21:34 a4700rac kernel: vcpu 2 irq check
>> Oct 10 07:21:34 a4700rac kernel: vcpu 5 irq check
>> Oct 10 07:21:34 a4700rac kernel: vcpu 3 irq check
>> Oct 10 07:21:34 a4700rac kernel: vcpu 2 irq check
>> Oct 10 07:21:34 a4700rac kernel: vcpu 5 irq check
>> Oct 10 07:21:34 a4700rac kernel: vcpu 3 irq check
>> 
>> Note that I never seem to see irq checks for cpus 4, 6, 7 ..... maybe
>> syslog is chewing them up though, but it seems strange that they
>> never seem to appear.
> 
> Now, this is where it gets strange - I pulled out the above snapshot
> why the system was stuck in the boot process. However after a bit it
> came back and irqs showed up on cpu 4, 6, 7 as well..... adding the
> printk seems to have have an impact.... strange.
Hi, Jes
	Interesting finding!  Since this is a regression issue, maybe we
can use git-bisect to identify it.  Anyone wants to take it ? Thanks!
Thanks
Xiantao

--
To unsubscribe from this list: send the line "unsubscribe kvm-ia64" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux KVM Devel]     [Linux Virtualization]     [Big List of Linux Books]     [Linux SCSI]     [Yosemite Forum]

  Powered by Linux