Re: Raspberry Pi kernel panic with current sources as of today

[Ryo ONODERA <ryo_on%yk.rim.or.jp@localhost>]

From: Nick Hudson <skrll%netbsd.org@localhost>, Date: Thu, 02 Jan 2014 15:54:17 
+0000

> On 01/02/14 11:00, Ryo ONODERA wrote:
>> From: Nick Hudson <skrll%netbsd.org@localhost>, Date: Thu, 02 Jan 2014 
>> 09:46:26
>> +0000
>>
>>> On 01/02/14 06:44, David H. Gutteridge wrote:
>>>> Hi all,
>>>>
>>>> Is anyone else seeing a kernel panic with sources checked out today
>>>> on a Raspberry Pi?
>>> Just tried here and it boots for me. Anything interesting about your
>>> setup? A dmesg might help here.
>>>
>>>>    My prior kernel was built a month ago, and works
>>>> fine. I wasn't able to get the USB keyboard to respond to get a
>>>> full backtrace. (And I'm not running through a serial console, so
>>>> it's a pain to copy out all the details...)
>>> Please battle through the pain :) or setup a serial console.
>>>> The panic message ends with:
>>>>
>>>> Stopped in pid 0.5 (system) at netbsd:callout_softclock+0x40: str
>>>> r1,[r2
>>>>    #0x004]
>>> This doesn't tell us much other than r2 is wrong.
>> Hi,
>>
>> I have today's evbearmvnh6-el RPI kernel on Raspberry Pi
>> And I have gotten the following panic message.
>>
>> ld0: 30604 MB, 7772 cyl, 128 head, 63 sec, 512byte/sect x 62676992
>> sectors
>> ld0: 4-bit width, bus clock 50.000 MHz
>> panic: kernel diagnostic assertion
>> "!callout_pendinf(&dxfer->xfer.timeout_handle)" failed: file
>> "/mnt/cvs/src-current/src/sys/external/bsd/dwc2/dwc2.c", line 346
>> Stopping in pid o.3 (system) at netbsd:cpu_Debugger+0x4: bx r14
>> db>
>>
> Should be fixed now.

Hi,

Thank you very much.
It works fine for me.

--
Ryo ONODERA // ryo_on%yk.rim.or.jp@localhost
PGP fingerprint = 82A2 DC91 76E0 A10A 8ABB  FD1B F404 27FA C7D1 15F3