VIA x86-64 bootlogs needed
Hi,
For some APIC code rework I would like to collect some statistics on VIA APIC setups.
If you have a system with VIA chipset running a recent (2.6.16+) x86-64 kernel please boot the system with apic=verbose on the kernel command and send me
- boot output (/var/log/boot.msg or dmesg -s100000000 output after boot)
- dmidecode output
- lspci -v output
Thanks,
-Andi
Quoted 11 lines · Andi Kleen
Hi,
For some APIC code rework I would like to collect some statistics on VIA APIC setups.
If you have a system with VIA chipset running a recent (2.6.16+) x86-64 kernel please boot the system with apic=verbose on the kernel command and send me
- boot output (
/var/log/boot.msgor dmesg -s100000000 output after boot)
- dmidecode output
- lspci -v output
MSI Master2-FAR with VIA K8T800, kernel-2.6.17-1.2157_FC5
With any luck, this APIC rework will fix this board's habit of spontaneously turning off interrupts at the IOAPIC level without the kernel's knowledge.
Signature · 1 line
Nicholas Miell <[email protected]>
Quoted 9 lines · Andi Kleen
Hi,
For some APIC code rework I would like to collect some statistics on VIA APIC setups.
If you have a system with VIA chipset running a recent (2.6.16+) x86-64 kernel please boot the system with apic=verbose on the kernel command and send me
Quoted 7 lines
- boot output (
/var/log/boot.msgor dmesg -s100000000 output after boot)
- dmidecode output
- lspci -v outputThanks,
This is a MSI K8T Master2 FAR with the VIA® K8T800 + 8237 chipset, kernel 2.6.17-mm1
Quoted 2 lines
MSI Master2-FAR with VIA K8T800, kernel-2.6.17-1.2157_FC5
Thanks.
Quoted 3 lines
With any luck, this APIC rework will fix this board's habit of spontaneously turning off interrupts at the IOAPIC level without the kernel's knowledge.
Unlikely unfortunately. How does it look like when they get turned off?
-Andi
Quoted 10 lines · Andi Kleen
Quoted 1 line
MSI Master2-FAR with VIA K8T800, kernel-2.6.17-1.2157_FC5
Thanks.
Quoted 3 lines
With any luck, this APIC rework will fix this board's habit of spontaneously turning off interrupts at the IOAPIC level without the kernel's knowledge.
Unlikely unfortunately. How does it look like when they get turned off?
I stop getting any interrupts from the device in question (either the on-board UHCI controllers or the on-board SATA controller) -- i.e. mouse movement gets jerky because uhci-hcd is operating purely by polling or I start getting libata timeouts in my logs.
I have an abomination of a systemtap script which calls unmask_IO_APIC_irq directly which instantly "fixes" it when things go wrong.
I also have another stap script which records stack traces when mask_IO_APIC_irq and unmask_IO_APIC_irq called in order to check if the IRQs are actually getting turned off without the kernel's knowledge, but when I run that in the background, the problem doesn't ever manifest itself.
Signature · 1 line
Nicholas Miell <[email protected]>
Quoted 14 lines · Bongani Hlope
Quoted 13 lines · Andi Kleen
Hi,
For some APIC code rework I would like to collect some statistics on VIA APIC setups.
If you have a system with VIA chipset running a recent (2.6.16+) x86-64 kernel please boot the system with apic=verbose on the kernel command and send me
- boot output (
/var/log/boot.msgor dmesg -s100000000 output after boot)
- dmidecode output
- lspci -v output
Quoted 7 lines
Quoted 3 lines
Thanks,
This is a MSI K8T Master2 FAR with the VIA? K8T800 + 8237 chipset, kernel 2.6.17-mm1
I have the same mobo running latest 2.6.18. Let me know if you need my info too.
Thanks,
Jon
This APIC rework have the goal of resolve problem with lost tickets ?
Quoted 20 lines · Andi Kleen
Hi,
For some APIC code rework I would like to collect some statistics on VIA APIC setups.
If you have a system with VIA chipset running a recent (2.6.16+) x86-64 kernel please boot the system with apic=verbose on the kernel command and send me
- boot output (
/var/log/boot.msgor dmesg -s100000000 output after boot)
- dmidecode output
- lspci -v outputThanks,
(quoted diff) +0
-2-Andi -To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Signature · 1 line
Sérgio M.B.
Hi, where is my Pentium Dual Core on a 775Dual-880Pro
http://www.asrock.com/product/775Dual-880Pro.htm
Kernel is 2.6.18-rc2 (with some minor patches) from Fedora/RedHat development.
I have to boot with notsc, details of the bugs on this computer:
http://bugme.osdl.org/show_bug.cgi?id=6419
Thanks,
Quoted 15 lines · Andi Kleen
Hi,
For some APIC code rework I would like to collect some statistics on VIA APIC setups.
If you have a system with VIA chipset running a recent (2.6.16+) x86-64 kernel please boot the system with apic=verbose on the kernel command and send me
- boot output (
/var/log/boot.msgor dmesg -s100000000 output after boot)
- dmidecode output
- lspci -v outputThanks,
-Andi
Quoted 1 line · Sergio Monteiro Basto
This APIC rework have the goal of resolve problem with lost tickets ?
What is a lost ticket?
But unlikely. In fact it only cleans up some code.
-Andi
dmesg | grep -i lost
Bootdata ok (command line is ro root=LABEL=/1 report_lost_ticks notsc apic=verbose)
Kernel command line: ro root=LABEL=/1 report_lost_ticks notsc apic=verbosetime.c: Lost 576 timer tick(s)! rip console_init+0x0/0x2e) time.c: Lost 2 timer tick(s)! rip release_console_sem+0x185/0x201) time.c: Lost 9 timer tick(s)! rip setup_boot_APIC_clock+0x11f/0x121) time.c: Lost 1 timer tick(s)! rip __do_softirq+0x48/0xca)
Quoted 8 lines · Andi Kleen
Quoted 1 line · Sergio Monteiro Basto
This APIC rework have the goal of resolve problem with lost tickets ?
What is a lost ticket?
But unlikely. In fact it only cleans up some code.
-Andi