public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ronny Buchmann <rbla@gmx.de>
To: Kai Germaschewski <kai@thphy.uni-duesseldorf.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: bug (isdn-subsystem?) in 2.4.0
Date: Tue, 16 Jan 2001 20:49:43 +0100	[thread overview]
Message-ID: <3A64A5D7.5020801@gmx.de> (raw)
In-Reply-To: <Pine.LNX.4.30.0101152306480.2419-100000@vaio>



Kai Germaschewski wrote:

> On Mon, 15 Jan 2001, Ronny Buchmann wrote:
> 
> 
>> i have the following problem with kernel 2.4.0 (also with -ac6):
>> 
>> kernel BUG at slab.c:1095!
>> invalid operand: 0000
>> CPU: 0
> 
> 
> I could reproduce the problem, the appended patch fixes it here. Linus,
> could you please apply this for 2.4.1?
but a part of the problem remains: i can't get a succesful connection

the calling side gets a CONNECT message, but on the called side i only 
get the RING
and after some seconds on both lines NO CARRIER

syslog only shows the RING and no connect

the same when i'm calling from gsm phone

btw, when calling from mobile phone i have to leave S19=197 (with 2.2.17 
S19=0 is working as described in the isdn faq, has this changed now?)

>> (if you need the other numbers or anything else, ask me, i can reproduce
>> it easily)
> 
> 
> A decoded oops would be nice the next time, see
> 
> 	<your linux kernel source>/REPORTING-BUGS
> 
sorry, my fault

tia
ronny

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

      reply	other threads:[~2001-01-16 20:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-15 18:51 bug (isdn-subsystem?) in 2.4.0 Ronny Buchmann
2001-01-15 22:13 ` Kai Germaschewski
2001-01-16 19:49   ` Ronny Buchmann [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3A64A5D7.5020801@gmx.de \
    --to=rbla@gmx.de \
    --cc=kai@thphy.uni-duesseldorf.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox