Kernel panic, rsync corruption, intel q8200, 2.6.28-rc8
Hardware summary: http://tinyurl.com/ap79ra
APIC details: http://intertwingly.net/stories/2009/01/22/
Note acpidump.err: Wrong checksum for OEMB!
Messages on boot using Intrepid, Jaunty Alpha 3, or Fedora 10:
[ 0.296001] ..MP-BIOS bug: 8254 timer not connected to IO-APIC [ 0.296001] Kernel panic - not syncing: IO-APIC + timer doesn't work! Boot with apic=debug and send a report. Then try booting with the 'noapic' option. [ 0.296001]
Able to get past this issue using "noapic", at which point things mostly work, but rsync of large iso images result in corrupt files. Able to copy those same files using Vista on the same machine, or using Hardy on another machine. This problem may not be related to the above, but it seems plausible to me that this might be an interrupt issue.
memtest86+ runs clean.
Quite willing to invest time in installing kernels or distributions on fresh hard drives, run tests, obtain debug information, and report back.
More background here: http://intertwingly.net/blog/2009/01/20/noAPIC
Not subscribed, but will actively monitor the web archives for this mailing list for the next several days.
- Sam Ruby
Quoted 6 lines · On Thu, 22 Jan 2009 08:37:01 -0500 Sam Ruby <[email protected]> wrote:
Hardware summary: http://tinyurl.com/ap79ra
APIC details: http://intertwingly.net/stories/2009/01/22/
Note acpidump.err: Wrong checksum for OEMB!Messages on boot using Intrepid, Jaunty Alpha 3, or Fedora 10:
Quoted 8 lines
[ 0.296001] ..MP-BIOS bug: 8254 timer not connected to IO-APIC [ 0.296001] Kernel panic - not syncing: IO-APIC + timer doesn't work! Boot with apic=debug and send a report. Then try booting with the 'noapic' option. [ 0.296001]Able to get past this issue using "noapic", at which point things mostly work,
Join the ever-growing noapic club :(
I assume this is an ACPI problem. Or at least, a BIOS problem which ACPI can solve for us.
Quoted 4 lines
but rsync of large iso images result in corrupt files. Able to copy those same files using Vista on the same machine, or using Hardy on another machine. This problem may not be related to the above, but it seems plausible to me that this might be an interrupt issue.
Yes, it might be unrelated. There are no kernel messages when it happens?
Quoted 9 lines
memtest86+ runs clean.
Quite willing to invest time in installing kernels or distributions on fresh hard drives, run tests, obtain debug information, and report back.
More background here: http://intertwingly.net/blog/2009/01/20/noAPIC
Not subscribed, but will actively monitor the web archives for this mailing list for the next several days.
It'd be best to raise a report against ACPI?BIOS (I think) at bugzilla.kernel.org, please.
If any previous kernel version worked OK, please be sure to note that.
Thanks.
Quoted 14 lines · Andrew Morton
Quoted 12 lines · On Thu, 22 Jan 2009 08:37:01 -0500 Sam Ruby <[email protected]> wrote:
Hardware summary: http://tinyurl.com/ap79ra
APIC details: http://intertwingly.net/stories/2009/01/22/
Note acpidump.err: Wrong checksum for OEMB!Messages on boot using Intrepid, Jaunty Alpha 3, or Fedora 10:
[ 0.296001] ..MP-BIOS bug: 8254 timer not connected to IO-APIC [ 0.296001] Kernel panic - not syncing: IO-APIC + timer doesn't work! Boot with apic=debug and send a report. Then try booting with the 'noapic' option. [ 0.296001]
Quoted 6 lines
Quoted 1 line
Able to get past this issue using "noapic", at which point things mostly work,
Join the ever-growing noapic club :(
I assume this is an ACPI problem. Or at least, a BIOS problem which ACPI can solve for us.
My understanding is that APCI and APIC are two different things.
Quoted 3 lines
Quoted 1 line
but rsync of large iso images result in corrupt files. Able to copy those same files using Vista on the same machine, or using Hardy on another machine. This problem may not be related to the above, but it seems plausible to me that this might be an interrupt issue.
Yes, it might be unrelated. There are no kernel messages when it happens?
I see no messages to /var/log/messages while doing the following (which involves rsync'ing a 2618793984 byte file from an NTFS to ext3 drive on the same machine:
rubys@rubix4:~/tmp$ rsync /mnt/shared/windows7_7000.iso . rubys@rubix4:~/tmp$ openssl md5 windows7_7000.iso MD5(windows7_7000.iso)= 953b9ac92d58f5edef525004bcce048d rubys@rubix4:~/tmp$ rsync /mnt/shared/windows7_7000.iso . rubys@rubix4:~/tmp$ openssl md5 windows7_7000.iso MD5(windows7_7000.iso)= 695328ef1280708eb73303656f6ef0b2
Quoted 10 lines
Quoted 7 lines
memtest86+ runs clean.
Quite willing to invest time in installing kernels or distributions on fresh hard drives, run tests, obtain debug information, and report back.
More background here: http://intertwingly.net/blog/2009/01/20/noAPIC
Not subscribed, but will actively monitor the web archives for this mailing list for the next several days.
It'd be best to raise a report against ACPI?BIOS (I think) at bugzilla.kernel.org, please.
Once again, I'm talking about apic not acpi... does this advice still hold?
Quoted 1 line
If any previous kernel version worked OK, please be sure to note that.
I don't believe that's the case. Put another way, I've yet to find a Linux kernel that can boot without the noapic option on this machine.
Quoted 1 line
Thanks.
- Sam Ruby
Quoted 18 lines · On Tue, 03 Feb 2009 12:58:36 -0500 Sam Ruby <[email protected]> wrote:
Quoted 17 lines · Andrew Morton
Quoted 14 lines · On Thu, 22 Jan 2009 08:37:01 -0500 Sam Ruby <[email protected]> wrote:
Hardware summary: http://tinyurl.com/ap79ra
APIC details: http://intertwingly.net/stories/2009/01/22/
Note acpidump.err: Wrong checksum for OEMB!Messages on boot using Intrepid, Jaunty Alpha 3, or Fedora 10:
[ 0.296001] ..MP-BIOS bug: 8254 timer not connected to IO-APIC [ 0.296001] Kernel panic - not syncing: IO-APIC + timer doesn't work! Boot with apic=debug and send a report. Then try booting with the 'noapic' option. [ 0.296001]Able to get past this issue using "noapic", at which point things mostly work,
Quoted 6 lines
Quoted 4 lines
Join the ever-growing noapic club :(
I assume this is an ACPI problem. Or at least, a BIOS problem which ACPI can solve for us.
My understanding is that APCI and APIC are two different things.
They sure are. But it is ACPI which communicates with the BIOS to tell the kernel about the APIC, hwo it's wired up, etc.
Although in this case it looks like the problem might be with the mp-bios tables, which ACPI does not handle. In which case it would be core x86 code which will have to fix this up, not ACPI.
Did you try updating the BIOS?
Quoted 25 lines
Quoted 6 lines
Quoted 4 lines
but rsync of large iso images result in corrupt files. Able to copy those same files using Vista on the same machine, or using Hardy on another machine. This problem may not be related to the above, but it seems plausible to me that this might be an interrupt issue.
Yes, it might be unrelated. There are no kernel messages when it happens?
I see no messages to
/var/log/messageswhile doing the following (which involves rsync'ing a 2618793984 byte file from an NTFS to ext3 drive on the same machine:rubys@rubix4:~/tmp$ rsync /mnt/shared/windows7_7000.iso . rubys@rubix4:~/tmp$ openssl md5 windows7_7000.iso MD5(windows7_7000.iso)= 953b9ac92d58f5edef525004bcce048d rubys@rubix4:~/tmp$ rsync /mnt/shared/windows7_7000.iso . rubys@rubix4:~/tmp$ openssl md5 windows7_7000.iso MD5(windows7_7000.iso)= 695328ef1280708eb73303656f6ef0b2Quoted 7 lines
Quoted 7 lines
memtest86+ runs clean.
Quite willing to invest time in installing kernels or distributions on fresh hard drives, run tests, obtain debug information, and report back.
More background here: http://intertwingly.net/blog/2009/01/20/noAPIC
Quoted 7 lines
Quoted 5 lines
Quoted 2 lines
Not subscribed, but will actively monitor the web archives for this mailing list for the next several days.
It'd be best to raise a report against ACPI?BIOS (I think) at bugzilla.kernel.org, please.
Once again, I'm talking about apic not acpi... does this advice still hold?
Not sure. Perhaps platform_i386/platform_x86_64 would be correct. Can the x86 maintainers please advise?
Quoted 25 lines · Andrew Morton
Quoted 15 lines · On Tue, 03 Feb 2009 12:58:36 -0500 Sam Ruby <[email protected]> wrote:
Quoted 14 lines · Andrew Morton
Quoted 12 lines · On Thu, 22 Jan 2009 08:37:01 -0500 Sam Ruby <[email protected]> wrote:
Hardware summary: http://tinyurl.com/ap79ra
APIC details: http://intertwingly.net/stories/2009/01/22/
Note acpidump.err: Wrong checksum for OEMB!Messages on boot using Intrepid, Jaunty Alpha 3, or Fedora 10:
[ 0.296001] ..MP-BIOS bug: 8254 timer not connected to IO-APIC [ 0.296001] Kernel panic - not syncing: IO-APIC + timer doesn't work! Boot with apic=debug and send a report. Then try booting with the 'noapic' option. [ 0.296001]Quoted 6 lines
Quoted 5 lines
Quoted 1 line
Able to get past this issue using "noapic", at which point things mostly work,
Join the ever-growing noapic club :(
I assume this is an ACPI problem. Or at least, a BIOS problem which ACPI can solve for us.
My understanding is that APCI and APIC are two different things.
Quoted 8 lines
They sure are. But it is ACPI which communicates with the BIOS to tell the kernel about the APIC, hwo it's wired up, etc.
Although in this case it looks like the problem might be with the mp-bios tables, which ACPI does not handle. In which case it would be core x86 code which will have to fix this up, not ACPI.
Did you try updating the BIOS?
My understanding is that a BIOS may be specific to the machine.
In the past, I've been able to find BIOS updates at manufacturer web sites. This one is difficult to navigate, but the closest I have been able to find is:
Product Line => Desktop
Aspire M3640
Search
In the list that results, I see "INT15 Driver for AMI BIOS Core" for Vista, but no BIOS. It could be that I just don't know where to look.
Note: my actual machine is designated AM3641-EQ8200A
Quoted 17 lines
Quoted 17 lines
Quoted 2 lines
Quoted 1 line
but rsync of large iso images result in corrupt files. Able to copy those same files using Vista on the same machine, or using Hardy on another machine. This problem may not be related to the above, but it seems plausible to me that this might be an interrupt issue.
Yes, it might be unrelated. There are no kernel messages when it happens?
I see no messages to
/var/log/messageswhile doing the following (which involves rsync'ing a 2618793984 byte file from an NTFS to ext3 drive on the same machine:rubys@rubix4:~/tmp$ rsync /mnt/shared/windows7_7000.iso . rubys@rubix4:~/tmp$ openssl md5 windows7_7000.iso MD5(windows7_7000.iso)= 953b9ac92d58f5edef525004bcce048d rubys@rubix4:~/tmp$ rsync /mnt/shared/windows7_7000.iso . rubys@rubix4:~/tmp$ openssl md5 windows7_7000.iso MD5(windows7_7000.iso)= 695328ef1280708eb73303656f6ef0b2Quoted 6 lines
Quoted 6 lines
memtest86+ runs clean.
Quite willing to invest time in installing kernels or distributions on fresh hard drives, run tests, obtain debug information, and report back.
More background here: http://intertwingly.net/blog/2009/01/20/noAPIC
Quoted 7 lines
Quoted 4 lines
Quoted 3 lines
Quoted 1 line
Not subscribed, but will actively monitor the web archives for this mailing list for the next several days.
It'd be best to raise a report against ACPI?BIOS (I think) at bugzilla.kernel.org, please.
Once again, I'm talking about apic not acpi... does this advice still hold?
Not sure. Perhaps platform_i386/platform_x86_64 would be correct. Can the x86 maintainers please advise?
- Sam Ruby
Quoted 2 lines · Andrew Morton
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
[ 0.296001] ..MP-BIOS bug: 8254 timer not connected to IO-APIC [ 0.296001] Kernel panic - not syncing: IO-APIC + timer doesn't work!
Sigh.
Quoted 2 lines
Not sure. Perhaps platform_i386/platform_x86_64 would be correct. Can the x86 maintainers please advise?
Yup. That's correct
@Sam: I just checked, that your machine has a serial port. That's a good start :)
Do you have a second computer around with a serial port ? If yes, then please add the following to the kernel command line:
earlyprintk=serial,ttyS0,115200 apic=debug
and connect the serial ports with a null modem cable. Fire up a terminal program on the second machine and capture the output.
Thanks,
tglx
Quoted 13 lines · Thomas Gleixner
Quoted 2 lines · Andrew Morton
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
[ 0.296001] ..MP-BIOS bug: 8254 timer not connected to IO-APIC [ 0.296001] Kernel panic - not syncing: IO-APIC + timer doesn't work!Sigh.
Quoted 2 lines
Not sure. Perhaps platform_i386/platform_x86_64 would be correct. Can the x86 maintainers please advise?
Yup. That's correct
@Sam: I just checked, that your machine has a serial port. That's a good start :)
Quoted 7 lines
Do you have a second computer around with a serial port ? If yes, then please add the following to the kernel command line:
earlyprintk=serial,ttyS0,115200 apic=debugand connect the serial ports with a null modem cable. Fire up a terminal program on the second machine and capture the output.
I do have a second computer, and went out and bought a null modem adapter for my serial cable and connected the two machines. I've tried installing minicom and also connecting it to ttyS0 at 115200 baud on the second machine, but when I boot the first machine I don't see any output on the terminal.
What am I missing?
Quoted 3 lines
Thanks,
tglx
- Sam Ruby
Len Brown
reviewerQuoted 5 lines
Quoted 5 lines
Do you have a second computer around with a serial port ? If yes, then please add the following to the kernel command line:
earlyprintk=serial,ttyS0,115200 apic=debug
Quoted 7 lines
Quoted 2 lines
and connect the serial ports with a null modem cable. Fire up a terminal program on the second machine and capture the output.
I do have a second computer, and went out and bought a null modem adapter for my serial cable and connected the two machines. I've tried installing minicom and also connecting it to ttyS0 at 115200 baud on the second machine, but when I boot the first machine I don't see any output on the terminal.
/boot/grub/menu.lst:
serial --unit=0 --speed=115200 --word=8 --parity=no --stop=1 terminal --timeout=300 serial console
is what I use.
this will give you a prompt from grub even before the kernel boots so you can select (and edit) your kernel via menu over the serial line if you wish.
If this doesn't work, then the kernel earlyprintk is unlikely to work also.
Note that there may be some BIOS SETUP options related to the serial port -- worth checking.
Also, in minicom, be sure to turn off HW flow control
there is a fancy serial console document someplace on this, probably at http://tldp.org/
good luck,
-Len
Quoted 14 lines · Len Brown
Quoted 11 lines
Quoted 7 lines
Do you have a second computer around with a serial port ? If yes, then please add the following to the kernel command line:
earlyprintk=serial,ttyS0,115200 apic=debugand connect the serial ports with a null modem cable. Fire up a terminal program on the second machine and capture the output.
I do have a second computer, and went out and bought a null modem adapter for my serial cable and connected the two machines. I've tried installing minicom and also connecting it to ttyS0 at 115200 baud on the second machine, but when I boot the first machine I don't see any output on the terminal.
/boot/grub/menu.lst:
Quoted 8 lines
serial --unit=0 --speed=115200 --word=8 --parity=no --stop=1 terminal --timeout=300 serial console
is what I use.
this will give you a prompt from grub even before the kernel boots so you can select (and edit) your kernel via menu over the serial line if you wish.
I've got that working now. I used minicom on the remote machine, capturing the output. You can see me fumbling around, editing the kernel command and booting here:
http://intertwingly.net/stories/2009/02/09/minicom.out
While it is difficult to make out what I did given line wrapping, etc, what I started with was:
/boot/vmlinuz-2.6.27-11-generic root=UUID=4fce230e-fe72-4685-aab0-294ef1c20efa ro noapic quiet splash
After editing, what I had was
/boot/vmlinuz-2.6.27-11-generic root=UUID=4fce230e-fe72-4685-aab0-294ef1c20efa ro quiet splash earlyprintk=serial,ttyS0,115200 apic=debug
As you can see, the last line I saw was "Starting up ...", after which point the "MP-BIOS bug: 8254 timer not connected to IO-APIC" etc output appeared on the monitor that is directly connected to the machine being booted (i.e., this text did not appear on the minicom session).
Quoted 1 line
If this doesn't work, then the kernel earlyprintk is unlikely to work also.
At the moment, it looks like it works, but earlyprintk does not work for me, at least not on Ubuntu 8.10, kernel 2.6.27-11-generic.
Quoted 7 lines
Note that there may be some BIOS SETUP options related to the serial port -- worth checking.
Also, in minicom, be sure to turn off HW flow control
there is a fancy serial console document someplace on this, probably at http://tldp.org/
As I have managed to get grub to talk to the serial console, I did not explore these options further. Please let me know if there is something in particular I should explore.
Quoted 2 lines
good luck,
-Len
- Sam Ruby
Quoted 13 lines · Sam Ruby
Quoted 12 lines · Len Brown
Quoted 11 lines
Quoted 7 lines
Do you have a second computer around with a serial port ? If yes, then please add the following to the kernel command line:
earlyprintk=serial,ttyS0,115200 apic=debugand connect the serial ports with a null modem cable. Fire up a terminal program on the second machine and capture the output.
I do have a second computer, and went out and bought a null modem adapter for my serial cable and connected the two machines. I've tried installing minicom and also connecting it to ttyS0 at 115200 baud on the second machine, but when I boot the first machine I don't see any output on the terminal.
Quoted 4 lines
Quoted 4 lines
/boot/grub/menu.lst:serial --unit=0 --speed=115200 --word=8 --parity=no --stop=1 terminal --timeout=300 serial console
Do you have an opportunity to try the boot option of "acpi=off" as suggested by Lenb?
From the log it seems that there exists the following warning
message:
Quoted 1 line
MP-BIOS bug: 8254 timer not connected to IO-APIC
Can you try the following boot options?
a. acpi_use_timer_override
b. acpi_skip_timer_override
c. noapic
Thanks.
Quoted 48 lines
Quoted 6 lines
is what I use.
this will give you a prompt from grub even before the kernel boots so you can select (and edit) your kernel via menu over the serial line if you wish.
I've got that working now. I used minicom on the remote machine, capturing the output. You can see me fumbling around, editing the kernel command and booting here:
http://intertwingly.net/stories/2009/02/09/minicom.out
While it is difficult to make out what I did given line wrapping, etc, what I started with was:
/boot/vmlinuz-2.6.27-11-genericroot=UUID=4fce230e-fe72-4685-aab0-294ef1c20efa ro noapic quiet splashAfter editing, what I had was
/boot/vmlinuz-2.6.27-11-genericroot=UUID=4fce230e-fe72-4685-aab0-294ef1c20efa ro quiet splash earlyprintk=serial,ttyS0,115200 apic=debugAs you can see, the last line I saw was "Starting up ...", after which point the "MP-BIOS bug: 8254 timer not connected to IO-APIC" etc output appeared on the monitor that is directly connected to the machine being booted (i.e., this text did not appear on the minicom session).
Quoted 2 lines
If this doesn't work, then the kernel earlyprintk is unlikely to work also.
At the moment, it looks like it works, but earlyprintk does not work for me, at least not on Ubuntu 8.10, kernel 2.6.27-11-generic.
Quoted 7 lines
Note that there may be some BIOS SETUP options related to the serial port -- worth checking.
Also, in minicom, be sure to turn off HW flow control
there is a fancy serial console document someplace on this, probably at http://tldp.org/
As I have managed to get grub to talk to the serial console, I did not explore these options further. Please let me know if there is something in particular I should explore.
Quoted 8 lines
Quoted 2 lines
good luck,
-Len- Sam Ruby
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 13 lines · yakui_zhao
Quoted 12 lines · Sam Ruby
Quoted 11 lines · Len Brown
Quoted 11 lines
Quoted 7 lines
Do you have a second computer around with a serial port ? If yes, then please add the following to the kernel command line:
earlyprintk=serial,ttyS0,115200 apic=debugand connect the serial ports with a null modem cable. Fire up a terminal program on the second machine and capture the output.
I do have a second computer, and went out and bought a null modem adapter for my serial cable and connected the two machines. I've tried installing minicom and also connecting it to ttyS0 at 115200 baud on the second machine, but when I boot the first machine I don't see any output on the terminal.
Quoted 6 lines
Quoted 4 lines
Quoted 4 lines
/boot/grub/menu.lst:serial --unit=0 --speed=115200 --word=8 --parity=no --stop=1 terminal --timeout=300 serial console
Do you have an opportunity to try the boot option of "acpi=off" as suggested by Lenb?
That also produces the "MP-BIOS bug" message and halts.
Quoted 6 lines
From the log it seems that there exists the following warning
message:Quoted 1 line
MP-BIOS bug: 8254 timer not connected to IO-APIC
Can you try the following boot options?
a.acpi_use_timer_override
That also produces the "MP-BIOS bug" message and halts.
Quoted 1 line
b.
acpi_skip_timer_override
That also produces the "MP-BIOS bug" message and halts.
Quoted 1 line
c. noapic
With that, I can boot, but I get data corruption problems. Data corruption problems I don't see when using the same hardware but with Microsoft Vista. More details can be found here:
http://intertwingly.net/blog/2009/01/20/noAPIC
http://intertwingly.net/stories/2009/01/22/
I am willing to install new kernels on fresh hard drives, run diagnostic programs and report the output, including capturing serial output. Is there any data I can gather to help diagnose this problem?
Quoted 39 lines
Thanks.
Quoted 38 lines
Quoted 5 lines
is what I use.
this will give you a prompt from grub even before the kernel boots so you can select (and edit) your kernel via menu over the serial line if you wish.
I've got that working now. I used minicom on the remote machine, capturing the output. You can see me fumbling around, editing the kernel command and booting here:
http://intertwingly.net/stories/2009/02/09/minicom.out
While it is difficult to make out what I did given line wrapping, etc, what I started with was:
/boot/vmlinuz-2.6.27-11-genericroot=UUID=4fce230e-fe72-4685-aab0-294ef1c20efa ro noapic quiet splashAfter editing, what I had was
/boot/vmlinuz-2.6.27-11-genericroot=UUID=4fce230e-fe72-4685-aab0-294ef1c20efa ro quiet splash earlyprintk=serial,ttyS0,115200 apic=debugAs you can see, the last line I saw was "Starting up ...", after which point the "MP-BIOS bug: 8254 timer not connected to IO-APIC" etc output appeared on the monitor that is directly connected to the machine being booted (i.e., this text did not appear on the minicom session).
Quoted 1 line
If this doesn't work, then the kernel earlyprintk is unlikely to work also.
At the moment, it looks like it works, but earlyprintk does not work for me, at least not on Ubuntu 8.10, kernel 2.6.27-11-generic.
Quoted 7 lines
Note that there may be some BIOS SETUP options related to the serial port -- worth checking.
Also, in minicom, be sure to turn off HW flow control
there is a fancy serial console document someplace on this, probably at http://tldp.org/
As I have managed to get grub to talk to the serial console, I did not explore these options further. Please let me know if there is something in particular I should explore.
Quoted 2 lines
good luck,
-Len- Sam Ruby
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
- Sam Ruby
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 14 lines · Sam Ruby
Quoted 13 lines · yakui_zhao
Quoted 12 lines · Sam Ruby
Quoted 11 lines · Len Brown
Quoted 11 lines
Quoted 7 lines
Do you have a second computer around with a serial port ? If yes, then please add the following to the kernel command line:
earlyprintk=serial,ttyS0,115200 apic=debugand connect the serial ports with a null modem cable. Fire up a terminal program on the second machine and capture the output.
I do have a second computer, and went out and bought a null modem adapter for my serial cable and connected the two machines. I've tried installing minicom and also connecting it to ttyS0 at 115200 baud on the second machine, but when I boot the first machine I don't see any output on the terminal.
Quoted 8 lines
Quoted 6 lines
Quoted 4 lines
Quoted 4 lines
/boot/grub/menu.lst:serial --unit=0 --speed=115200 --word=8 --parity=no --stop=1 terminal --timeout=300 serial console
Do you have an opportunity to try the boot option of "acpi=off" as suggested by Lenb?
That also produces the "MP-BIOS bug" message and halts.
Do you mean that the box still can't be booted with ACPI disabled? If so, it should be a BIOS bug. It had better be fixed by bios upgrading.
From the following test it seems that there exists the MPS table,
which describes how the timer is connected with I/O APIC. But unfortunately it is still incorrect.
And the timer still can't work w/o the timer override.
Only when I/O apic is skipped can the box be booted. The timer is
connected with 8259. And the timer can work as expected. But there still exist other issue.
Quoted 74 lines
Quoted 7 lines
From the log it seems that there exists the following warning
message:Quoted 1 line
MP-BIOS bug: 8254 timer not connected to IO-APIC
Can you try the following boot options?
a.acpi_use_timer_overrideThat also produces the "MP-BIOS bug" message and halts.
Quoted 1 line
b.
acpi_skip_timer_overrideThat also produces the "MP-BIOS bug" message and halts.
Quoted 1 line
c. noapic
With that, I can boot, but I get data corruption problems. Data corruption problems I don't see when using the same hardware but with Microsoft Vista. More details can be found here:
http://intertwingly.net/blog/2009/01/20/noAPIC
http://intertwingly.net/stories/2009/01/22/I am willing to install new kernels on fresh hard drives, run diagnostic programs and report the output, including capturing serial output. Is there any data I can gather to help diagnose this problem?
Quoted 47 lines
Thanks.
Quoted 46 lines
Quoted 5 lines
is what I use.
this will give you a prompt from grub even before the kernel boots so you can select (and edit) your kernel via menu over the serial line if you wish.
I've got that working now. I used minicom on the remote machine, capturing the output. You can see me fumbling around, editing the kernel command and booting here:
http://intertwingly.net/stories/2009/02/09/minicom.out
While it is difficult to make out what I did given line wrapping, etc, what I started with was:
/boot/vmlinuz-2.6.27-11-genericroot=UUID=4fce230e-fe72-4685-aab0-294ef1c20efa ro noapic quiet splashAfter editing, what I had was
/boot/vmlinuz-2.6.27-11-genericroot=UUID=4fce230e-fe72-4685-aab0-294ef1c20efa ro quiet splash earlyprintk=serial,ttyS0,115200 apic=debugAs you can see, the last line I saw was "Starting up ...", after which point the "MP-BIOS bug: 8254 timer not connected to IO-APIC" etc output appeared on the monitor that is directly connected to the machine being booted (i.e., this text did not appear on the minicom session).
Quoted 2 lines
If this doesn't work, then the kernel earlyprintk is unlikely to work also.
At the moment, it looks like it works, but earlyprintk does not work for me, at least not on Ubuntu 8.10, kernel 2.6.27-11-generic.
Quoted 7 lines
Note that there may be some BIOS SETUP options related to the serial port -- worth checking.
Also, in minicom, be sure to turn off HW flow control
there is a fancy serial console document someplace on this, probably at http://tldp.org/
As I have managed to get grub to talk to the serial console, I did not explore these options further. Please let me know if there is something in particular I should explore.
Quoted 2 lines
good luck,
-Len
Quoted 7 lines
Quoted 5 lines
Quoted 5 lines
- Sam Ruby
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html- Sam Ruby
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 17 lines · yakui_zhao
Quoted 16 lines · Sam Ruby
Quoted 15 lines · yakui_zhao
Quoted 14 lines · Sam Ruby
Quoted 13 lines · Len Brown
Quoted 11 lines
Quoted 7 lines
Do you have a second computer around with a serial port ? If yes, then please add the following to the kernel command line:
earlyprintk=serial,ttyS0,115200 apic=debugand connect the serial ports with a null modem cable. Fire up a terminal program on the second machine and capture the output.
I do have a second computer, and went out and bought a null modem adapter for my serial cable and connected the two machines. I've tried installing minicom and also connecting it to ttyS0 at 115200 baud on the second machine, but when I boot the first machine I don't see any output on the terminal.
/boot/grub/menu.lst:
Quoted 7 lines
Quoted 5 lines
Quoted 4 lines
Quoted 2 lines
Quoted 2 lines
serial --unit=0 --speed=115200 --word=8 --parity=no --stop=1 terminal --timeout=300 serial console
Do you have an opportunity to try the boot option of "acpi=off" as suggested by Lenb?
That also produces the "MP-BIOS bug" message and halts.
Do you mean that the box still can't be booted with ACPI disabled? If so, it should be a BIOS bug. It had better be fixed by bios upgrading.
Yes, that's what I mean. Linux won't boot with acpi=off, but will boot with noapic.
This is a fairly new machine, and I have yet to see where ACER has posted a more recent BIOS for this model.
Quoted 5 lines
From the following test it seems that there exists the MPS table,
which describes how the timer is connected with I/O APIC. But unfortunately it is still incorrect.
And the timer still can't work w/o the timer override.
Quoted 63 lines
Only when I/O apic is skipped can the box be booted. The timer is
connected with 8259. And the timer can work as expected. But there still exist other issue.Quoted 59 lines
Quoted 6 lines
From the log it seems that there exists the following warning
message:Quoted 1 line
MP-BIOS bug: 8254 timer not connected to IO-APIC
Can you try the following boot options?
a.acpi_use_timer_overrideThat also produces the "MP-BIOS bug" message and halts.
Quoted 1 line
b.
acpi_skip_timer_overrideThat also produces the "MP-BIOS bug" message and halts.
Quoted 1 line
c. noapic
With that, I can boot, but I get data corruption problems. Data corruption problems I don't see when using the same hardware but with Microsoft Vista. More details can be found here:
http://intertwingly.net/blog/2009/01/20/noAPIC
http://intertwingly.net/stories/2009/01/22/I am willing to install new kernels on fresh hard drives, run diagnostic programs and report the output, including capturing serial output. Is there any data I can gather to help diagnose this problem?
Quoted 39 lines
Thanks.
Quoted 38 lines
Quoted 5 lines
is what I use.
this will give you a prompt from grub even before the kernel boots so you can select (and edit) your kernel via menu over the serial line if you wish.
I've got that working now. I used minicom on the remote machine, capturing the output. You can see me fumbling around, editing the kernel command and booting here:
http://intertwingly.net/stories/2009/02/09/minicom.out
While it is difficult to make out what I did given line wrapping, etc, what I started with was:
/boot/vmlinuz-2.6.27-11-genericroot=UUID=4fce230e-fe72-4685-aab0-294ef1c20efa ro noapic quiet splashAfter editing, what I had was
/boot/vmlinuz-2.6.27-11-genericroot=UUID=4fce230e-fe72-4685-aab0-294ef1c20efa ro quiet splash earlyprintk=serial,ttyS0,115200 apic=debugAs you can see, the last line I saw was "Starting up ...", after which point the "MP-BIOS bug: 8254 timer not connected to IO-APIC" etc output appeared on the monitor that is directly connected to the machine being booted (i.e., this text did not appear on the minicom session).
Quoted 1 line
If this doesn't work, then the kernel earlyprintk is unlikely to work also.
At the moment, it looks like it works, but earlyprintk does not work for me, at least not on Ubuntu 8.10, kernel 2.6.27-11-generic.
Quoted 7 lines
Note that there may be some BIOS SETUP options related to the serial port -- worth checking.
Also, in minicom, be sure to turn off HW flow control
there is a fancy serial console document someplace on this, probably at http://tldp.org/
As I have managed to get grub to talk to the serial console, I did not explore these options further. Please let me know if there is something in particular I should explore.
Quoted 2 lines
good luck,
-Len- Sam Ruby
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html- Sam Ruby
- Sam Ruby
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 17 lines · yakui_zhao
Quoted 16 lines · Sam Ruby
Quoted 15 lines · yakui_zhao
Quoted 14 lines · Sam Ruby
Quoted 13 lines · Len Brown
Quoted 11 lines
Quoted 7 lines
Do you have a second computer around with a serial port ? If yes, then please add the following to the kernel command line:
earlyprintk=serial,ttyS0,115200 apic=debugand connect the serial ports with a null modem cable. Fire up a terminal program on the second machine and capture the output.
I do have a second computer, and went out and bought a null modem adapter for my serial cable and connected the two machines. I've tried installing minicom and also connecting it to ttyS0 at 115200 baud on the second machine, but when I boot the first machine I don't see any output on the terminal.
/boot/grub/menu.lst:
Quoted 7 lines
Quoted 5 lines
Quoted 4 lines
Quoted 2 lines
Quoted 2 lines
serial --unit=0 --speed=115200 --word=8 --parity=no --stop=1 terminal --timeout=300 serial console
Do you have an opportunity to try the boot option of "acpi=off" as suggested by Lenb?
That also produces the "MP-BIOS bug" message and halts.
Do you mean that the box still can't be booted with ACPI disabled? If so, it should be a BIOS bug. It had better be fixed by bios upgrading.
BIOS information, in case it is helpful to anyone:
http://intertwingly.net/stories/2009/02/11/dmidecode.out
Quoted 5 lines
From the following test it seems that there exists the MPS table,
which describes how the timer is connected with I/O APIC. But unfortunately it is still incorrect.
And the timer still can't work w/o the timer override.
Quoted 64 lines
Only when I/O apic is skipped can the box be booted. The timer is
connected with 8259. And the timer can work as expected. But there still exist other issue.Quoted 59 lines
Quoted 6 lines
From the log it seems that there exists the following warning
message:Quoted 1 line
MP-BIOS bug: 8254 timer not connected to IO-APIC
Can you try the following boot options?
a.acpi_use_timer_overrideThat also produces the "MP-BIOS bug" message and halts.
Quoted 1 line
b.
acpi_skip_timer_overrideThat also produces the "MP-BIOS bug" message and halts.
Quoted 1 line
c. noapic
With that, I can boot, but I get data corruption problems. Data corruption problems I don't see when using the same hardware but with Microsoft Vista. More details can be found here:
http://intertwingly.net/blog/2009/01/20/noAPIC
http://intertwingly.net/stories/2009/01/22/I am willing to install new kernels on fresh hard drives, run diagnostic programs and report the output, including capturing serial output. Is there any data I can gather to help diagnose this problem?
Quoted 39 lines
Thanks.
Quoted 38 lines
Quoted 5 lines
is what I use.
this will give you a prompt from grub even before the kernel boots so you can select (and edit) your kernel via menu over the serial line if you wish.
I've got that working now. I used minicom on the remote machine, capturing the output. You can see me fumbling around, editing the kernel command and booting here:
http://intertwingly.net/stories/2009/02/09/minicom.out
While it is difficult to make out what I did given line wrapping, etc, what I started with was:
/boot/vmlinuz-2.6.27-11-genericroot=UUID=4fce230e-fe72-4685-aab0-294ef1c20efa ro noapic quiet splashAfter editing, what I had was
/boot/vmlinuz-2.6.27-11-genericroot=UUID=4fce230e-fe72-4685-aab0-294ef1c20efa ro quiet splash earlyprintk=serial,ttyS0,115200 apic=debugAs you can see, the last line I saw was "Starting up ...", after which point the "MP-BIOS bug: 8254 timer not connected to IO-APIC" etc output appeared on the monitor that is directly connected to the machine being booted (i.e., this text did not appear on the minicom session).
Quoted 1 line
If this doesn't work, then the kernel earlyprintk is unlikely to work also.
At the moment, it looks like it works, but earlyprintk does not work for me, at least not on Ubuntu 8.10, kernel 2.6.27-11-generic.
Quoted 7 lines
Note that there may be some BIOS SETUP options related to the serial port -- worth checking.
Also, in minicom, be sure to turn off HW flow control
there is a fancy serial console document someplace on this, probably at http://tldp.org/
As I have managed to get grub to talk to the serial console, I did not explore these options further. Please let me know if there is something in particular I should explore.
Quoted 2 lines
good luck,
-Len- Sam Ruby
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html- Sam Ruby
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Len Brown
reviewerQuoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
[ 0.296001] ..MP-BIOS bug: 8254 timer not connected to IO-APIC [ 0.296001] Kernel panic - not syncing: IO-APIC + timer doesn't work!
just for the record, check_timer() is x86 IO-APIC code, not ACPI code. So if the machine actually has MPS support, you'll probably get the same result with "acpi=off". (of course if it doesn't have MPS, then acpi=off would boot in uniprocessor legacy PIC mode)
cheers,
-Len
Quoted 14 lines · Andrew Morton
Quoted 14 lines
Quoted 13 lines
Quoted 8 lines
[ 0.296001] ..MP-BIOS bug: 8254 timer not connected to IO-APIC [ 0.296001] Kernel panic - not syncing: IO-APIC + timer doesn't work! Boot with apic=debug and send a report. Then try booting with the 'noapic' option. [ 0.296001]Able to get past this issue using "noapic", at which point things mostly work,
Join the ever-growing noapic club :(
I assume this is an ACPI problem. Or at least, a BIOS problem which ACPI can solve for us.
Quoted 8 lines
Quoted 1 line
My understanding is that APCI and APIC are two different things.
They sure are. But it is ACPI which communicates with the BIOS to tell the kernel about the APIC, hwo it's wired up, etc.
Although in this case it looks like the problem might be with the mp-bios tables, which ACPI does not handle. In which case it would be core x86 code which will have to fix this up, not ACPI.
The message is misleading. It predates the ACPI and has never been
updated. It applies equally to both MPS and ACPI systems. Earlier bootstrap messages can be used to determine which configuration method has been used by the kernel on this system (many systems provide both).
Maciej
Quoted 14 lines · Andrew Morton
Quoted 12 lines · On Thu, 22 Jan 2009 08:37:01 -0500 Sam Ruby <[email protected]> wrote:
Hardware summary: http://tinyurl.com/ap79ra
APIC details: http://intertwingly.net/stories/2009/01/22/
Note acpidump.err: Wrong checksum for OEMB!Messages on boot using Intrepid, Jaunty Alpha 3, or Fedora 10:
[ 0.296001] ..MP-BIOS bug: 8254 timer not connected to IO-APIC [ 0.296001] Kernel panic - not syncing: IO-APIC + timer doesn't work! Boot with apic=debug and send a report. Then try booting with the 'noapic' option. [ 0.296001]
Quoted 6 lines
Quoted 1 line
Able to get past this issue using "noapic", at which point things mostly work,
Join the ever-growing noapic club :(
I assume this is an ACPI problem. Or at least, a BIOS problem which ACPI can solve for us.
My understanding is that APCI and APIC are two different things.
Quoted 3 lines
Quoted 1 line
but rsync of large iso images result in corrupt files. Able to copy those same files using Vista on the same machine, or using Hardy on another machine. This problem may not be related to the above, but it seems plausible to me that this might be an interrupt issue.
Yes, it might be unrelated. There are no kernel messages when it happens?
I see no messages to /var/log/messages while doing the following (which involves rsync'ing a 2618793984 byte file from an NTFS to ext3 drive on the same machine:
rubys@rubix4:~/tmp$ rsync /mnt/shared/windows7_7000.iso . rubys@rubix4:~/tmp$ openssl md5 windows7_7000.iso MD5(windows7_7000.iso)= 953b9ac92d58f5edef525004bcce048d rubys@rubix4:~/tmp$ rsync /mnt/shared/windows7_7000.iso . rubys@rubix4:~/tmp$ openssl md5 windows7_7000.iso MD5(windows7_7000.iso)= 695328ef1280708eb73303656f6ef0b2
Quoted 10 lines
Quoted 7 lines
memtest86+ runs clean.
Quite willing to invest time in installing kernels or distributions on fresh hard drives, run tests, obtain debug information, and report back.
More background here: http://intertwingly.net/blog/2009/01/20/noAPIC
Not subscribed, but will actively monitor the web archives for this mailing list for the next several days.
It'd be best to raise a report against ACPI?BIOS (I think) at bugzilla.kernel.org, please.
Once again, I'm talking about apic not acpi... does this advice still hold?
Quoted 1 line
If any previous kernel version worked OK, please be sure to note that.
I don't believe that's the case.
Quoted 1 line
Thanks.
- Sam Ruby