150241 - kernel panic when receiving message headers via IMAP

Status: RESOLVED WORKSFORME

(MailNews Core :: Networking: IMAP, defect)

Description

[Glenn Colaco]

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.14; Mac_PowerPC)
BuildID:    2002052918

While receiving message headers via IMAP, 1.0 PR3, and relase 1.0 
causes a kernel panic on Mac OS X 10.1.5 while using Cisco's VPN 5000 
tunneling software.  This happens with Netscape 7.0 PR1 (based on 1.0 
PR 2).

Panic does not happen with netsacpe 6.2.3 or other mail readers.

The initial stack trace is from the VPN client which causes an invalid trap.

I cannot get a stack trace etc. since OS and firmware require a remote 
machine to debug, which I do not have.

Reproducible: Always
Steps to Reproduce:
1. create tunnel using Cisco's VPN 5000 client ver. 5.2.2 (or 5.1.4) on Mac 
OS 10.1.5
2. check IMAP mail to receive headers
3. wait until panic

Actual Results:  kernel panic, invalid system trap

Expected Results:  should not panic the system

my guess has something to do with the tcp socket/network interaction 
with the stack.  1.0 is doing something that the kernel (atleast the VPN 
client) doesn't like.

Comment 1

[Matthias Versen [:Matti]]

no blocker

Why should this be a mozilla bug ?
Isn't there something wron with the cisco software ?
(Mozilla triggers only this bug)

Comment 2

[Greg K.]

Glenn, have you contacted Cisco about this? Since their VPN client is the
crasher, the problem may well lie there.

Comment 3

[Glenn Colaco]

I have not yet reported this to Cisco, but I need to.  Granted, there is 
sufficient  data to warrant  Cisco to look into this, there is cause for 
concern from the userland side (in this case it is always Mozilla or 
Netsacpe 7PR1).

My concern is the interaction Mozilla has with the network stack w/ OS X 
10.1.5.  I use various other network based apps. on the same system with 
the VPN, which doesn't cause a kernel panic.  The only time I get a kernel 
panic consistently is during the use of Mozilla, which is why I filed this 
bug. 

I am aware that this is not very much information to diagnose the issue, 
let alone fix the bug.  I am just hoping that this may be a good indicator to 
profile the app. for any gaping issues with OS X.

Comment 4

[Matthias Versen [:Matti]]

Mozilla can't cause a kernel Panic, it can only trigger it.
(Mozilla doesn't use kernel mode drivers)

Comment 5

[Glenn Colaco]

I agree, but it can issue something into the kernel (network stack) that 
sends it into a disarray, maybe a race condition?  I have just filed an issue 
with Cisco, hopefully this will give us some insight.

Comment 6

[Greg K.]

(It should be noted that Cisco is openly and fanatically hostile to Macs. I
know, I worked there for several years. Thus, they may not pay any attention to
a problem involving them.)

Comment 7

[Greg K.]

Glenn, can you still reproduce this problem using a current nightly build and
current OS X?

Comment 8

[Glenn Colaco]

Since upgrading the OS, mozilla version etc. this issue has not occurred,
however I am not 100% sure the bug has disapeared.  It was sporadic to begin
with.  Most likely, it was with the Cisco VPN kernel module.

Comment 9

[Greg K.]

Resolving WFM per comment 8. Glenn, if this problem recurs, feel free to reopen
this bug.