| To: | David Daney <ddaney@caviumnetworks.com> |
|---|---|
| Subject: | Re: Kernel crash in 2.6.32.6 / bcm1480 with 16k page size |
| From: | Guenter Roeck <guenter.roeck@ericsson.com> |
| Date: | Fri, 29 Jan 2010 11:58:01 -0800 |
| Cc: | Ralf Baechle <ralf@linux-mips.org>, "linux-mips@linux-mips.org" <linux-mips@linux-mips.org> |
| In-reply-to: | <4B6336F1.8070208@caviumnetworks.com> |
| References: | <20100128155514.GA31611@ericsson.com> <20100129132406.GD5685@linux-mips.org> <20100129151220.GA3882@ericsson.com> <4B6316D2.1060006@caviumnetworks.com> <20100129180619.GA20113@linux-mips.org> <20100129183926.GB9895@ericsson.com> <4B632F60.4000604@caviumnetworks.com> <20100129192532.GA11123@ericsson.com> <4B6336F1.8070208@caviumnetworks.com> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mutt/1.5.18 (2008-05-17) |
On Fri, Jan 29, 2010 at 02:28:49PM -0500, David Daney wrote: ... > > I suspect you are hitting a maximum valid address bits limit and getting > the Address Exception. Limiting VMALLOC_END so that you don't hit the > limit seems to be the solution. I don't have the manual for the sibyte, > so I don't know what the limit is. The architecture specification > doesn't state a fixed limit, although it tells what should happen when > the limit is reached. > You mean there might be a CPU-specific limit ? I hope not - that would be quite messy. I'll see if I can dig up a sibyte manual. Guenter |
| Previous by Date: | Re: Kernel crash in 2.6.32.6 / bcm1480 with 16k page size, David Daney |
|---|---|
| Next by Date: | Re: Kernel crash in 2.6.32.6 / bcm1480 with 16k page size, Guenter Roeck |
| Previous by Thread: | Re: Kernel crash in 2.6.32.6 / bcm1480 with 16k page size, David Daney |
| Next by Thread: | Re: Kernel crash in 2.6.32.6 / bcm1480 with 16k page size, Maciej W. Rozycki |
| Indexes: | [Date] [Thread] [Top] [All Lists] |