Op woensdag 07-03-2012 om 22:51 uur [tijdzone +0100], schreef Nils: > Op dinsdag 06-03-2012 om 22:25 uur [tijdzone -0500], schreef Kevin > O'Connor: > > You could try, dumping the value of cntl->regs->periodicstart and > > cntl->regs->fminterval at the end of start_ohci() to see if there's > > something odd there. > > > > You could also try setting the Skip bit in ohci_alloc_intr_pipe > > (ed->hwINFO |= ED_SKIP) to see if the issue is with the TDs or EDs. > > You could also try replacing malloc_low calls with malloc_high calls > > in ohci_alloc_intr_pipe to see if maybe the controller doesn't like > > the memory addresses. > Ok now i have some results! > With the original ohci pipe free fix and the 3 malloc's changed to > malloc_high the controller seems to keep running. :) > > There is probably also another problem.(see attached log) > While booting i did not touch the keyboard, but it received (partly > unknown) keycodes. > At the end of the log SeaBIOS crashed. > This sequence is reproducible at every boot. > When i unplug the keyboard then boot and then plug in again after > SeaBIOS finished, then linux runs fine. > > Thanks, Nils. Also if repeat booting i get often the following lines in the log: KBD: int09h_handler(): unknown scancode read: 0x5b!
KBD: int09h_handler(): unknown scancode read: 0x5c! _______________________________________________ SeaBIOS mailing list [email protected] http://www.seabios.org/mailman/listinfo/seabios
