On Fri, 5 Aug 2005, Martin Loschwitz wrote:
> On Fri, Aug 05, 2005 at 03:40:26PM -0400, linux-os (Dick Johnson) wrote:
>>
>> On Fri, 5 Aug 2005, Martin Loschwitz wrote:
>>
>>> Hi folks,
>>>
>>> I just ran into the following problem: Having updated my box to 2.6.12.3,
>>> I tried to start YaST2 an
>>> I just ran into the following problem: Having updated my box to 2.6.12.3,
>>> I tried to start YaST2 and noticed a kernel panic (see below). Some quick
Hm I always have a slack feeling that vanilla does not play hand in hand with
SUSE. (E.g.: showconsole)
>>> Ooops and ksymoops-output is at
On Sat, Aug 06, 2005 at 01:29:09AM +0200, Marc Ballarin wrote:
> On Fri, 5 Aug 2005 23:52:47 +0200
> Martin Loschwitz <[EMAIL PROTECTED]> wrote:
>
> >
> > The situation in this case is somewhat obscene ... Originally, I had exactly
> > this problem while using the Knoppix standard kernel (2.6.11
On Fri, 5 Aug 2005 23:52:47 +0200
Martin Loschwitz <[EMAIL PROTECTED]> wrote:
>
> The situation in this case is somewhat obscene ... Originally, I had exactly
> this problem while using the Knoppix standard kernel (2.6.11 vanilla SMP). I
> then went to compile 2.6.12.3, also with SMP, and it show
On Fri, Aug 05, 2005 at 03:33:44PM -0700, Andrew Morton wrote:
> Martin Loschwitz <[EMAIL PROTECTED]> wrote:
> >
> > On Fri, Aug 05, 2005 at 03:40:26PM -0400, linux-os (Dick Johnson) wrote:
> > >
> > > On Fri, 5 Aug 2005, Martin Loschwitz wrote:
> > >
> > > > Hi folks,
> > > >
> > > > I just ran
Martin Loschwitz <[EMAIL PROTECTED]> wrote:
>
> On Fri, Aug 05, 2005 at 03:40:26PM -0400, linux-os (Dick Johnson) wrote:
> >
> > On Fri, 5 Aug 2005, Martin Loschwitz wrote:
> >
> > > Hi folks,
> > >
> > > I just ran into the following problem: Having updated my box to 2.6.12.3,
> > > I tried to s
On Fri, Aug 05, 2005 at 04:03:07PM -0400, Lee Revell wrote:
> On Fri, 2005-08-05 at 21:26 +0200, Martin Loschwitz wrote:
> > Ooops and ksymoops-output is attached.
>
> Also, don't use ksymoops for 2.6, it's redundant at best and at worst
> actually removes information. Check oops-tracing.txt, the
On Fri, Aug 05, 2005 at 12:50:56PM -0700, Chris Wright wrote:
> * Martin Loschwitz ([EMAIL PROTECTED]) wrote:
> > I just ran into the following problem: Having updated my box to 2.6.12.3,
> > I tried to start YaST2 and noticed a kernel panic (see below). Some quick
> > debugging brought the result
On Fri, Aug 05, 2005 at 03:40:26PM -0400, linux-os (Dick Johnson) wrote:
>
> On Fri, 5 Aug 2005, Martin Loschwitz wrote:
>
> > Hi folks,
> >
> > I just ran into the following problem: Having updated my box to 2.6.12.3,
> > I tried to start YaST2 and noticed a kernel panic (see below). Some quick
On Fri, 2005-08-05 at 21:26 +0200, Martin Loschwitz wrote:
> Ooops and ksymoops-output is attached.
Also, don't use ksymoops for 2.6, it's redundant at best and at worst
actually removes information. Check oops-tracing.txt, the docs have
been updated.
Lee
-
To unsubscribe from this list: send t
* Martin Loschwitz ([EMAIL PROTECTED]) wrote:
> I just ran into the following problem: Having updated my box to 2.6.12.3,
> I tried to start YaST2 and noticed a kernel panic (see below). Some quick
> debugging brought the result that the kernel crashes while some user (not
> even root ...) tries t
On Fri, 5 Aug 2005, Martin Loschwitz wrote:
> Hi folks,
>
> I just ran into the following problem: Having updated my box to 2.6.12.3,
> I tried to start YaST2 and noticed a kernel panic (see below). Some quick
> debugging brought the result that the kernel crashes while some user (not
> even root
Hi folks,
I just ran into the following problem: Having updated my box to 2.6.12.3,
I tried to start YaST2 and noticed a kernel panic (see below). Some quick
debugging brought the result that the kernel crashes while some user (not
even root ...) tries to access /proc/ioports. Is this a known pro
13 matches
Mail list logo
