Adding RT-mailing list.. 2009/8/24 Vivek Satpute <vivek@xxxxxxxxxxxxxx>: > Hi Bo, > > 2009/8/21 Bo Hansen <bh@xxxxxxxxx> >> >> Hi Uwe, >> >> I cannot find anything in the dmesg or serial output regarding the >> WARN_ON_ONCE(...) >> I guess the WARN_ON_ONCE(...) should show up in dmesg output? > > I am not sure that it is directly shown up in dmesg output, but you can > add printks to verify whether WARN_ON_ONCE() code path hits or not. >> >> What puzzles me is that I tried the CONFIG_DEBUG_BUGVERBOSE=y >> also when I enabled CONFIG_DEBUG_INFO. When I do >> this I don't get the kernel panic. Is this somehow related to the >> WARN_ON_ONCE? > > I have encountered this scenario. If there is any race condition in code > then it might get suppressed when debugging options are enabled and > kernel does not panic. >> >> Attachments only sent to Uwe - anybody are welcome to get a copy. >> >> Best regards, >> Bo > > Thanks, > Vivek Satpute >> >> >> Uwe Kleine-König wrote: >>> >>> Hello, >>> >>> >>>> >>>> PC is at clkevt32k_next_event+0x70/0xac >>>> >>> >>> This function has a WARN_ON_ONCE(...). Can you check if this triggers? >>> >>> Can you provide me a kernel image with CONFIG_DEBUG_INFO=y and a >>> matching oops? >>> >>> Best regards >>> Uwe >>> >>> >> >> -- >> To unsubscribe from this list: send the line "unsubscribe linux-rt-users" >> in >> the body of a message to majordomo@xxxxxxxxxxxxxxx >> More majordomo info at http://vger.kernel.org/majordomo-info.html > > -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
