Kernel cannot allocate resource region

Michael Schmitz schmitz at
Mon Nov 5 01:17:11 EST 2001

> I'm wondering if it's significant that the last message printed before the
> hang (it's not a panic, no reboot after 180 seconds) is "Macinto"?  When
> I boot without the G3 enabled, the full line is:
> Macintosh CUDA driver v0.5 for Unified ADB.

That may be a timing difference hitting in some driver - in the m68k ADB
code, I had been using a local (stack) adb_request struct for some
asyncronous ADB request. Most of the time the async operation would
complete while that variable was still valid (the calling routine hadn't
returned yet). Someetimes it would only complete later ;-(

The current ADB code should be free from such gross errors, but maybe
something else doesn't cope with async probing of devices? ADB probing
happens asynchronously these days (but then, BenH won't have used
non-static variables for that). And I'd expect the kernel to throw a
panic() for data or illegal instruction errors. Maybe some deadlock - what
other task is active during ADB probe?


** Sent via the linuxppc-dev mail list. See

More information about the Linuxppc-dev mailing list