On Wed, Nov 11, 2009 at 10:30 AM, Luis R. Rodriguez <firstname.lastname@example.org> wrote:
> On Wed, Nov 11, 2009 at 9:54 AM, Luis R. Rodriguez <email@example.com> wrote:
>> On Tue, Nov 10, 2009 at 2:40 PM, Luis R. Rodriguez <firstname.lastname@example.org> wrote:
>>> On Tue, Nov 10, 2009 at 7:30 AM, Andy Whitcroft <email@example.com> wrote:
>>>> Now that the compilers are working again (yay!) a new Lucid kernel has
>>>> been uploaded. *This rebases the Ubuntu kernel to 2.6.32-rc6. *Note the
>>>> ABI bump.
>>> Very nice Andy
>>> If you are like me and just need to test 2.6.32-rc6 on an x86 box here
>>> is the one deb file you'll need:
>> BTW how long does it take the build machine to build this?
>> And is do you guys lurk on an IRC channel?
> Well sow what I wanted to ask if if you can enable something like
> CONFIG_BOOT_PRINTK_DELAY during development of lucid and later perhaps
> remove it.
> It seems getting an oops trace on a netbook during early boot proves
> almost impossible unless you have a "Hi-Speed USB 2.0 Host-to-Host
> Debug Device" and a usb controller  (seems most of them do) that
> has USB debug port enabled , or the netbook would have a serial
> port but I am not sure how many comes with these, maybe they're
> hidden, I haven't seen one.
>  http://www.semiconductorstore.com/cart/pc/viewPrd.asp?idproduct=12083
>  Running 'lspci -vvv | grep -i debug' would yield:
> Capabilities:  Debug port: BAR=1 offset=00a0
I enabled BOOT_DELAY on my own kernel and set lpj as per the original
boot kernel's calibrated setting and enabed boot_delay=100 and was
unable to get actual delays between prinks, even if I did nosmp. So
this proved not useful anyway.
kernel-team mailing list