On Sun, 30 Aug 2015, Fernando Rodriguez wrote:
> And you should still try suggestion #2 because it's very likely to only affect
> one specific configuration.
Thanks, I did that just now. Took another, but didn't give me any more
data to go by. Getting set up for bisecting and doing real work on t
On Sunday, August 30, 2015 6:11:00 PM Fernando Rodriguez wrote:
> On Sunday, August 30, 2015 10:51:57 PM Peter Weilbacher wrote:
> > Hi Fernando,
> >
> > On Sun, 30 Aug 2015, Fernando Rodriguez wrote:
> >
> > > 1. Add loglevel=7 to your kernel parameters and see what it prints
before
> it
> > >
On Sunday, August 30, 2015 10:51:57 PM Peter Weilbacher wrote:
> Hi Fernando,
>
> On Sun, 30 Aug 2015, Fernando Rodriguez wrote:
>
> > 1. Add loglevel=7 to your kernel parameters and see what it prints before
it
> > hangs.
>
> That helped, it showed me something about drm, so...
>
> > 3. From
Hi Fernando,
On Sun, 30 Aug 2015, Fernando Rodriguez wrote:
> 1. Add loglevel=7 to your kernel parameters and see what it prints before it
> hangs.
That helped, it showed me something about drm, so...
> 3. From your kernel parameters I assume you're using the radeon free driver
> right? If that
On Tuesday, August 25, 2015 6:40:01 PM Peter Weilbacher wrote:
> Hi Alexander,
>
> On Sun, 23 Aug 2015, Alexander Kapshuk wrote:
>
> > On Sun, Aug 23, 2015 at 4:08 PM, Peter Weilbacher
wrote:
> > >
> > > after successfully using kernel 4.0.5 (vanilla-sources) for a while, I
> > > upgraded to 4.
On Sat, 29 Aug 2015, Alexander Kapshuk wrote:
> You probably did look into this yourself, but did you double-check
> your /etc/lilo.conf? Is everything fine there?
At least it's identical between 4.0.5 and 4.1.6:
image=/boot/kernel-genkernel-x86_64-4.0.5
label=Linux405
read-only # read-onl
On Sat, Aug 29, 2015 at 3:09 PM, Peter Weilbacher
wrote:
> On Tue, 25 Aug 2015, Alexander Kapshuk wrote:
>
>> I've never experienced this particular kernel trouble myself, so I'm
>> not sure if my input would be of much help.
>> Here's what the kernel documentation has to say about this kind of is
On Tue, 25 Aug 2015, Alexander Kapshuk wrote:
> I've never experienced this particular kernel trouble myself, so I'm
> not sure if my input would be of much help.
> Here's what the kernel documentation has to say about this kind of issue:
>
> /usr/src/linux/Documentation/RCU/stallwarn.txt:29,33
[.
On Tue, Aug 25, 2015 at 7:40 PM, Peter Weilbacher
wrote:
> Hi Alexander,
>
> On Sun, 23 Aug 2015, Alexander Kapshuk wrote:
>
>> On Sun, Aug 23, 2015 at 4:08 PM, Peter Weilbacher
>> wrote:
>> >
>> > after successfully using kernel 4.0.5 (vanilla-sources) for a while, I
>> > upgraded to 4.1.5 last
Hi Alexander,
On Sun, 23 Aug 2015, Alexander Kapshuk wrote:
> On Sun, Aug 23, 2015 at 4:08 PM, Peter Weilbacher
> wrote:
> >
> > after successfully using kernel 4.0.5 (vanilla-sources) for a while, I
> > upgraded to 4.1.5 last week and 4.1.6 today. I cannot boot either of
> > them. On the scree
On Sun, Aug 23, 2015 at 4:08 PM, Peter Weilbacher
wrote:
> Dear all,
>
> after successfully using kernel 4.0.5 (vanilla-sources) for a while, I
> upgraded to 4.1.5 last week and 4.1.6 today. I cannot boot either of
> them. On the screen I see
>
>Decompressing Linux... Parsing ELF... done.
>
Dear all,
after successfully using kernel 4.0.5 (vanilla-sources) for a while, I
upgraded to 4.1.5 last week and 4.1.6 today. I cannot boot either of
them. On the screen I see
Decompressing Linux... Parsing ELF... done.
Booting the kernel.
as the last thing, then it just sits there.
To up
12 matches
Mail list logo
