[SOLVED] hde: timeout waiting for DMA

[tinypoodle]

Indeed sounds like a timing issue.

For more debugging you could use following boot params:

Code: [Select]

debug printk.time=y earlyprintk=vga,keep syslog
If boot is successful you could then analyze syslog with

Code: [Select]

less /var/log/messages
This may sound unorthodox if not abusive, but if I were you I might just start to experiment what happens with generously yanking waitusb= in.

[Rich]

Hi jason
Try these 2 boot codes by themselves.
ide-core.nodma=0.0:0
ide-core.nodma=0.0:1
and see what each does.

tinypoodle: There are no USB ports involved yet.

[EDIT]: Also try irqpoll by itself.

[tinypoodle]

tinypoodle: There are no USB ports involved yet.

Hence the "unorthodox if not abusive"  

[Rich]

Ok, but trying that would only make sense without the nodma code since adding any
other code after nodma seems to make it work

[maro]

The 'xsetup' boot code is specific to TC and gets picked up by '/usr/init.d/tc-config'. It just sets a flag (i.e. '/tmp/xsetup_requested') which forces the execution of '/usr/bin/xsetup.sh' when 'startx' gets executed (as part of '~/.profile'). So IMHO there is a lot of other stuff happening between the kernel boot (which seems to be when the DMA issues are happening) and the start of the X server.

Still, I'm equally perplexed about this apparent connection of the number of boot codes and 'nodma' being ignored or not.

[jason.ritzke]

@TP
That does not work. If I don't turn off dma on the CD drive, the system simply does not boot. So no syslog to work with. And by yank waitusb to you mean remove or apply. I can't tell with your writing style.
@rich
I've reinstalled all of the HDDs, so I'm now using "ide-core.nodma=2.0". So you want me to give "ide-core.nodma=2.0:0" and "ide-core.nodma=2.0:1" a shot? Along with irqpoll?
@maro
especially considering that adding "xsetup" after "ide-core.nodma" has an effect. I wonder if the command isn't even getting passed to ide-core because the system doesn't parse it without an additional parameter. But with that hypothesis, the thing that doesn't make sense to me is that it is ordering sensitive.

[Rich]

Hi jason
tinypoodle was just suggesting trying something like waitusb=2 to alter the startup
timing. Regardless, you might want to pull off a copy of the output from dmesg to
use as a hardware reference.

[EDIT] Yes, if you have a chance please try those three by themselves and note
          ANY changes in behaviour.

[tinypoodle]

What I meant was for example to add waitusb= either before or after the nodma as the only additional boot parameter.

I suspect you might have overlooked the "if" in my statement about the debugging parameters: 'If boot is successful'

[jason.ritzke]

What I meant was for example to add waitusb= either before or after the nodma as the only additional boot parameter.

I suspect you might have overlooked the "if" in my statement about the debugging parameters: 'If boot is successful'

Your antecedents are still vague and unclear. Those debug parameters, do you want them with or without "ide-core.nodma=2.0". Without "ide-core.nodma=2.0", there is not boot. Also it is still unclear as to where exactly where waitusb fits in with all of this. do you want it with the other parameters?

I guess what I'm saying is that since this is a issue that is clearly dependent upon the place and order of the boot time parameters, I need you to be more clear and definite about what you are interested in me putting in to this system. Because the output will depend on the input a great deal.

EDIT: even used verbatim after "ide-core.nodma=2.0" that bootcode does not output to /var/log/messages. I don't know why.

EDIT: tried after another reboot and got an output. Must have typoed somewhere. I'll post below.

[jason.ritzke]

Hi jason
tinypoodle was just suggesting trying something like waitusb=2 to alter the startup
timing. Regardless, you might want to pull off a copy of the output from dmesg to
use as a hardware reference.

[EDIT] Yes, if you have a chance please try those three by themselves and note
          ANY changes in behaviour.

I'll pull a dmesg and also see what I can do

Edit: about the other options, I mean.

[tinypoodle]

Boot with
1. ide-core.nodma=2.0 waitusb=1
2. waitusb=1 ide-core.nodma=2.0
without any other additional params and see what happens in either case.

If you don't get any output to /var/log/messages after booting with 'syslog', check if daemons are running:

Code: [Select]

ps |grep logd

[jason.ritzke]

waitusb=1 in conjunction with ide-core.nodma=2.0 boots fine, either way.
irqpoll in conjunction with ide-core.nodma=2.0 boots fine, either way.
ide=core.nodma=2.0:0  with or without an additional parameter does not boot.
ide=core.nodma=2.0:1 with an additional parameter boots. Without does not boot.

All of the boot failures are "waiting for dma" timeouts.


First three are dmesg outputs, last one is output of "less /var/log/messages"

Edit : sorry, the first two are duplicates. Other than that my previous statment was true.

[tinypoodle]

From all those errors I'd guess that either the medium is faulty or the reader.

[jason.ritzke]

Which explains why it runs flawlessly?

EDIT:
I guess to be more precise and less terse, I've seen errors like this during boots on a number of systems with livcds. Do you really think that these I/O errors have to do with an actual deficiency of the drive (used a new medium, same errors). Could you explain how, if you were certain? Or point me in the direction of some documentation?

[tinypoodle]

Which explains all the randomess, look at your own logs how "flawlessly" it runs...