On 10/25/2014 11:18 AM, Udo van den Heuvel wrote:
> Hello,
>
> Here's a 3.16.2 dmesg that is a tad m ore complete but still the usb
> errors fill up the buffer.
> I want to try a bisect and cloned Linus' tree but need commit numbers
> for 3.16.2 and .3 to start the bisect process.
> Where can I
On 10/25/2014 11:18 AM, Udo van den Heuvel wrote:
Hello,
Here's a 3.16.2 dmesg that is a tad m ore complete but still the usb
errors fill up the buffer.
I want to try a bisect and cloned Linus' tree but need commit numbers
for 3.16.2 and .3 to start the bisect process.
Where can I find
Hello,
Here's a 3.16.2 dmesg that is a tad m ore complete but still the usb
errors fill up the buffer.
I want to try a bisect and cloned Linus' tree but need commit numbers
for 3.16.2 and .3 to start the bisect process.
Where can I find these?
Do we have a suspect 3.16.3 commit that I could try
Hello,
Here's a 3.16.2 dmesg that is a tad m ore complete but still the usb
errors fill up the buffer.
I want to try a bisect and cloned Linus' tree but need commit numbers
for 3.16.2 and .3 to start the bisect process.
Where can I find these?
Do we have a suspect 3.16.3 commit that I could try
On 2014-10-13 14:26, Chuck Ebbert wrote:
>> How can I capture the output easily?
>
> Add "boot_delay=3000" to the kernel command line. This will add a 3
> second delay between each line. Then take pictures of the screen
> while it boots. And try to time the shots so you take them during the
>
On 2014-10-13 14:26, Chuck Ebbert wrote:
How can I capture the output easily?
Add boot_delay=3000 to the kernel command line. This will add a 3
second delay between each line. Then take pictures of the screen
while it boots. And try to time the shots so you take them during the
delays.
On
On 10/13/2014 08:22 AM, Udo van den Heuvel wrote:
> On 2014-10-13 14:14, Peter Hurley wrote:
>>> Incomplete dmesg attached for 3.16.2.
>>
>> Why incomplete? No kernel command line, no version stamp, no CPU info,
>> no memory map, no IRQ routing info, etc.
>
> Because the buffer is filled with
On 2014-10-13 14:14, Peter Hurley wrote:
> Why incomplete? No kernel command line, no version stamp, no CPU info,
> no memory map, no IRQ routing info, etc.
>
# cat /proc/cmdline
ro root=/dev/myvg/rootlv noexec=on noexec32=on vga=0x0F01
SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEYTABLE=us
On Mon, 13 Oct 2014 12:14:40 +0200
Udo van den Heuvel wrote:
> On 2014-10-12 19:42, Peter Hurley wrote:
> > On 10/12/2014 09:57 AM, Udo van den Heuvel wrote:
> >> The problem:
> >> During the first few seconds of bootup the kernel gets into some sort of
> >> loop and rapidly prints loads of
On 2014-10-13 14:14, Peter Hurley wrote:
>> Incomplete dmesg attached for 3.16.2.
>
> Why incomplete? No kernel command line, no version stamp, no CPU info,
> no memory map, no IRQ routing info, etc.
Because the buffer is filled with other stuff and scrolls out.
>>> And rubbish is not
>> very
On 10/13/2014 06:14 AM, Udo van den Heuvel wrote:
> On 2014-10-12 19:42, Peter Hurley wrote:
>> On 10/12/2014 09:57 AM, Udo van den Heuvel wrote:
>>> The problem:
>>> During the first few seconds of bootup the kernel gets into some sort of
>>> loop and rapidly prints loads of register-like things
On 2014-10-12 19:42, Peter Hurley wrote:
> On 10/12/2014 09:57 AM, Udo van den Heuvel wrote:
>> The problem:
>> During the first few seconds of bootup the kernel gets into some sort of
>> loop and rapidly prints loads of register-like things and then a load of
>> rubbish.
>> I did `make clean` and
On 2014-10-12 19:42, Peter Hurley wrote:
On 10/12/2014 09:57 AM, Udo van den Heuvel wrote:
The problem:
During the first few seconds of bootup the kernel gets into some sort of
loop and rapidly prints loads of register-like things and then a load of
rubbish.
I did `make clean` and then a
On 10/13/2014 06:14 AM, Udo van den Heuvel wrote:
On 2014-10-12 19:42, Peter Hurley wrote:
On 10/12/2014 09:57 AM, Udo van den Heuvel wrote:
The problem:
During the first few seconds of bootup the kernel gets into some sort of
loop and rapidly prints loads of register-like things and then a
On 2014-10-13 14:14, Peter Hurley wrote:
Incomplete dmesg attached for 3.16.2.
Why incomplete? No kernel command line, no version stamp, no CPU info,
no memory map, no IRQ routing info, etc.
Because the buffer is filled with other stuff and scrolls out.
And rubbish is not
very
On Mon, 13 Oct 2014 12:14:40 +0200
Udo van den Heuvel udo...@xs4all.nl wrote:
On 2014-10-12 19:42, Peter Hurley wrote:
On 10/12/2014 09:57 AM, Udo van den Heuvel wrote:
The problem:
During the first few seconds of bootup the kernel gets into some sort of
loop and rapidly prints loads of
On 2014-10-13 14:14, Peter Hurley wrote:
Why incomplete? No kernel command line, no version stamp, no CPU info,
no memory map, no IRQ routing info, etc.
# cat /proc/cmdline
ro root=/dev/myvg/rootlv noexec=on noexec32=on vga=0x0F01
SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEYTABLE=us
On 10/13/2014 08:22 AM, Udo van den Heuvel wrote:
On 2014-10-13 14:14, Peter Hurley wrote:
Incomplete dmesg attached for 3.16.2.
Why incomplete? No kernel command line, no version stamp, no CPU info,
no memory map, no IRQ routing info, etc.
Because the buffer is filled with other stuff and
On 10/12/2014 09:57 AM, Udo van den Heuvel wrote:
> Hello,
>
> 3.16.2 boots and works fine.
> Kernels 3.16.3 and newer crash very early during boot. (did not yet try
> 3.17)
>
> The problem:
> During the first few seconds of bootup the kernel gets into some sort of
> loop and rapidly prints
Hello,
3.16.2 boots and works fine.
Kernels 3.16.3 and newer crash very early during boot. (did not yet try
3.17)
The problem:
During the first few seconds of bootup the kernel gets into some sort of
loop and rapidly prints loads of register-like things and then a load of
rubbish.
I did `make
Hello,
3.16.2 boots and works fine.
Kernels 3.16.3 and newer crash very early during boot. (did not yet try
3.17)
The problem:
During the first few seconds of bootup the kernel gets into some sort of
loop and rapidly prints loads of register-like things and then a load of
rubbish.
I did `make
On 10/12/2014 09:57 AM, Udo van den Heuvel wrote:
Hello,
3.16.2 boots and works fine.
Kernels 3.16.3 and newer crash very early during boot. (did not yet try
3.17)
The problem:
During the first few seconds of bootup the kernel gets into some sort of
loop and rapidly prints loads of
22 matches
Mail list logo
