Bug #796

Problem upgrading to 1.10.1

Added by elekktretterr about 7 years ago. Updated 8 months ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Unverifiable
Target version:3.8.0

Description

Hi,
I just attempted upgrade on 1 of the boxes from 1.8 to 1.10.1 but now the
server freezes during boot. It freezes on ppi0 parallel port stuff, but it
seems not to be related to it because this is after i removed usb stuff
from the kernel as it used to freeze on usb stuff and i thought by
removing the usb stuff it might fix it. Theres absolutely no debug
messages. Is there anything i can try?

Petr

History

#1 Updated by elekktretterr about 7 years ago

Btw, i tried with/without acpi, safemode,single user mode, nothing helps.

#2 Updated by corecode about 7 years ago

You could try a kernel with ata instead of nata. Don't forget to remove the PCI_MAP_FIXUP option as well.

cheers
simon

#3 Updated by elekktretterr about 7 years ago

Already tried it, that was actually the first thing i tried
(unintentionally as my kernel config file had the old ata stuff enabled,
and therefore nata was disabled) but doesnt fix anything.

Petr

#4 Updated by corecode about 7 years ago

can you break into the debugger?

cheers
simon

#5 Updated by elekktretterr about 7 years ago

It seems that removing APIC_IO fixes the problem. The question now is, why
APIC_IO worked in 1.8 and not in 1.10.

Is there any disadvantage to not having APIC_IO? If so, Id like to keep
debugging it untill we find the fix. What do you suggest?

#6 Updated by dillon about 7 years ago

:Hi,
:I just attempted upgrade on 1 of the boxes from 1.8 to 1.10.1 but now the
:server freezes during boot. It freezes on ppi0 parallel port stuff, but it
:seems not to be related to it because this is after i removed usb stuff
:from the kernel as it used to freeze on usb stuff and i thought by
:removing the usb stuff it might fix it. Theres absolutely no debug
:messages. Is there anything i can try?
:
:Petr

booting with -v (option 6 to break to boot prompt, then 'boot -v')
might yield more information.

-Matt
Matthew Dillon
<>

#7 Updated by elekktretterr about 7 years ago

the problem seemes to be a when apic_io is enabled. it worked in 1.8 but
not in 1.10. Is it worthwhile pursueing apic_io back to working state?

Petr

#8 Updated by tuxillo over 6 years ago

Now, I think this problem is rather related to issues 179 or 869 instead of an
upgrading problem.

Links:
http://bugs.dragonflybsd.org/issue179
http://bugs.dragonflybsd.org/issue869

We might consider closing this. What do you think, guys?

#9 Updated by tuxillo about 5 years ago

APIC_IO is non working on a lot of machines as far as I can tell.
I don't know the effort that would take to make APIC_IO back in shape, but maybe
hackers can tell a word about this.

#10 Updated by tuxillo 8 months ago

  • Description updated (diff)
  • Category set to Unverifiable
  • Status changed from New to Closed
  • Assignee deleted (0)
  • Target version set to 3.8.0

There have been huge changes since this ticket was opened.
In the case the issue still persists as of 3.6, 3.7, please open a new ticket.

Also available in: Atom PDF