Summary: | [irq] Unknown error generates IRQ address decoding error | ||||||
---|---|---|---|---|---|---|---|
Product: | Base System | Reporter: | Tyler S <tyler> | ||||
Component: | arm | Assignee: | freebsd-arm (Nobody) <freebsd-arm> | ||||
Status: | Open --- | ||||||
Severity: | Affects Only Me | CC: | imp | ||||
Priority: | Normal | ||||||
Version: | Unspecified | ||||||
Hardware: | Any | ||||||
OS: | Any | ||||||
Attachments: |
|
Description
Tyler S
2010-09-15 03:10:01 UTC
Actually, this may not be an issue. I realized I applied patches meant for -stable to -current. I will checkout the source again and rebuild to see what happens. On Tue, Sep 14, 2010 at 10:10 PM, <FreeBSD-gnats-submit@freebsd.org> wrote: > Thank you very much for your problem report. > It has the internal identification `arm/150581'. > The individual assigned to look at your > report is: freebsd-arm. > > You can access the state of your problem report at any time > via this link: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=150581 > > >Category: arm > >Responsible: freebsd-arm > >Synopsis: Unknown error generates IRQ address decoding error > >Arrival-Date: Wed Sep 15 02:10:01 UTC 2010 > Hi Tyler, The issue could be the same that I'm having on my PogoPlug (stripped down version of the Sheevaplug essentially). I don't have a serial console on it, so I haven't been able to get any actual error messages, but I do experience the same hard hang when I have heavy USB I/O. I'm still working on resolving this issue properly, but I have found a work-around. If rolling back those patches didn't fix the problem for you, try limiting the amount of RAM the kernel sees down to 128MiB. For me, going from the actual 256MiB down to 128MiB prevents the I/O lock-up and I have a stable system (I can in fact push it up to 131MiB, but above that it's bad news). To limit the RAM, open /usr/src/sys/boot/fdt/dts/sheevaplug.dts, find the "memory" entry and reduce it to 0x08000000, then rebuild your kernel. I'd be very interested in hearing whether this fixes your issue, as it's been quite frustrating to troubleshoot this without seeing what goes on the console when the hang occurs! Regards, /Johny For bugs matching the following criteria: Status: In Progress Changed: (is less than) 2014-06-01 Reset to default assignee and clear in-progress tags. Mail being skipped The patch appears to be required to work around a quirk in the Marvell hardware. It has not been applied yet. |