Bug 164539 – SAGEM F@st 800 driver causing kernel panic w/ 2.6.19 kernels

• Status: RESOLVED NEEDINFO
• Product: Gentoo Linux

[Description Jakub Bomba 2007-01-30 12:56:28 UTC]

When I boot my system with modem SAGEM F@ST 800(http://www.sagem.com/index.php?id=182&L=0) plugged into usb I see kernel panic - unable to kill init. This error is since 2.6.19 kernel.Modem worked fine with 2.6.18 kernels. There is another post about this error: http://forums.gentoo.org/viewtopic-p-3849075.html#3849075

Reproducible: Always

Steps to Reproduce:
1.turn computer on with sagem in usb
2.
3.

Actual Results:  
I see <0>Kernel panic - not syncing: attempted to kill init!

Expected Results:  
n/a

n/a

[Comment 1 Jakub Moc (RETIRED) 2007-01-30 18:17:27 UTC]

Reopen once you've posted all relevant info here. We can't guess and won't wade thru the noise on forums.gentoo.org

[Comment 2 Jakub Bomba 2007-01-31 00:40:09 UTC]

(In reply to comment #1)
> Reopen once you've posted all relevant info here. We can't guess and won't wade
> thru the noise on forums.gentoo.org
> 

You need more info? I can't nothing more. Sorry, but English isn't my native language.
Other people have this error too.

[Comment 3 Jakub Bomba 2007-01-31 00:43:19 UTC]

(In reply to comment #2)
> (In reply to comment #1)
> > Reopen once you've posted all relevant info here. We can't guess and won't wade
> > thru the noise on forums.gentoo.org
> > 
> 

**I can't add anything to this bug - that's all what i know. 

[Comment 4 Jakub Moc (RETIRED) 2007-01-31 00:47:34 UTC]

Well, either post all the info here, or don't file bugs. We will NOT read the forums.

[Comment 5 Jakub Bomba 2007-01-31 09:38:00 UTC]

(In reply to comment #4)
> Well, either post all the info here, or don't file bugs. We will NOT read the
> forums.
> 

Ok, more info? It looks so:

Code: 488b7ew4889434881
RIP[<ffff8026330f>create_dir+0x11/0x1da
RSP<ffff81003f111680>
GR2:0000000000000000000010

<0>Kernel panic - not syncing: attempted to kill init!

When i plug this modem after boot, it works fine.

Expected Results? Everything should work fine. 

I have this kernel panic only with this modem. Other USB devices are ok, when I turn my computer on. That's all the info about this bug.

[Comment 6 Daniel Drake (RETIRED) 2007-01-31 15:09:37 UTC]

Is this hardware powered by an in-kernel driver or is there a separate package in portage which you are using for it?

Please post the entire crash dump, not just parts of it. Feel free to leave out the magic numbers and addresses if you are transcribing by hand.

[Comment 7 Daniel Drake (RETIRED) 2007-02-24 18:43:15 UTC]

see comment #6

[Comment 8 Jakub Bomba 2007-02-24 21:13:06 UTC]

(In reply to comment #7)
> see comment #6
> 

I use only uaegle-atm from portage. Other things are from kernel. I see this bug only when I compile driver for this modem in to the kernel. As a module it works great ;-]

[Comment 9 Daniel Drake (RETIRED) 2007-02-24 22:18:50 UTC]

So ueagle-atm isn't the driver used for this device?

We still need the whole crash dump including call trace.

[Comment 10 Daniel Drake (RETIRED) 2007-03-10 04:45:29 UTC]

see comment #9