Bug 407683

attach yast logs please

Created attachment 228535 [details]
excerpt of y2log and y2log.SuSEconfig

I'm using two different ISDN-cards
a) AVM Fritz-Card DSL with binary drivers
b) ASUSTEK ISDNLink P-IN100-ST-D rev.2 with HiSax-driver nr.35
in two different systems.
I can confirm that the ISDN-cards are always marked as "not configured" although they are configured and working without problems.

This already occured in openSUSE 10.3 and I remember having problems there with duplicate devices/configurations and also deleting them.
With 11.0, I can not confirm these problems (except the "not configured" problem).

Please attach full YaST log, this is not helpful for me.

Created attachment 240903 [details]
y2log

Hope this helps.

Created attachment 264100 [details]
y2logs - Opensuse 11.1

Bug seems also to happen on Opensuse 11.1 
yast2 logs attached
Customer cannot configure ISDN card in YasT - Configuration is not saved. 
And with every try the contrx is counted up

I can confirm that, this bug still exist on 11.1. and now it causes kernel and X11 segmentation faults om my system !

I've updated from 11.0 to 11.1 yesterday and the result was a desaster:
After reboot, the x-server didn't start anymore and I end up at the console. I tried to start it manually and got


Backtrace:
0: /usr/bin/X(xf86SigHandler+0x79) [0x80c0c19]
1: [0xffffe400]
2: /usr/lib/libpciaccess.so.0(pci_device_next+0x14b) [0xb7f26dbb]
3: /usr/bin/X(xf86AccResFromOS+0x4b) [0x80b0aeb]
4: /usr/bin/X(xf86ResourceBrokerInit+0x2f) [0x80b798f]
5: /usr/bin/X(InitOutput+0x49d) [0x80a813d]
6: /usr/bin/X(main+0x279) [0x8070b49]
7: /lib/libc.so.6(__libc_start_main+0xe5) [0xb7ad0705]
8: /usr/bin/X [0x8070131]

Fatal server error:
Caught signal 11.  Server aborting


Then I tried to reboot and the kernel crashed with a segmentation fault after the "Please stand by while rebooting the system..." message.
(Btw: this also caused ext3-filesystem errors...:-( )

I decided to make a clean installation with a formatted root partition:
The card was detected properly as "ASUSCOM ISDNLink P-IN100-ST-D", but I wasn't asked for further configuration steps (I don't know if it should do so... ?).
After (successful) installation, I configured the card (displayed by YaST as "not configured") and a provider manually.
At the next system start I got the the same segmentation faults again... :-(

I finally solved the problem by deleting cfg-contr1 in /etc/sysconfig/isdn.


YaST creates one additional cfg-contrX at every configuration attempt and they are all identic.
After configuration, YaST still displays the device as "not configured".
The following messages appear during boot-process (I don't remember if they were already there in 10.3 an 11.0):


Setting up ISDN card contr0 Asus PCI (CCD HFC)			done
                     contr1 Asus PCI (CCD HFC)			done
                     ...
                     contrX Asus PCI (CCD HFC)			done
Loading Driver contr0 hisax					done
Loading Driver contr1						failed
...
Loading Driver contrX						failed

Created attachment 264314 [details]
Yet another YaST-log (openSUSE 11.1, clean installation)

Created attachment 264315 [details]
X-server-log

Created attachment 264316 [details]
Boot-messages

Created attachment 264317 [details]
controller-configuration from /etc/sysconfig/isdn (cfg-contr1, ... are identic)

Misconfiguartion is caused by YaST, but the kernel/driver should be able to manage this situation properly, right ? So this is a kernel-bug, too...

Same problem here in 11.0 and 11.1. No configured Card in Yast are displayed.

I'll try to reproduce 
re comment#8: this is kernel bug, please write separate bugreport

(In reply to comment #15)
> I'll try to reproduce 
> re comment#8: this is kernel bug, please write separate bugreport

Ok, I'll do that. Thanks for feedback !
Tell me, if I can do something else.

Created attachment 265059 [details]
package to test

I created rpm which seems fixes described problem. Please test it.
And please also test, if other network-related modules are not affected (lan, dsl, etc) - just to be sure

Note:
It uses UDI option to match hardware into configuration. That means you need to remove your old configuration manually (rm /etc/sysconfig/isdn/cfg-*) or write there UDI option (hwinfo --isdn|grep UDI)
Newly configuration should work ok
This also means, that in case of several devices with same UDI it wouldn't work

Please give me feedback from testing to submit that code

Michal

Thank you works great for 11.1. Sorry on my Notebook there is no DSL-HArdware, so I cant test it. Lan works fine too.
Your RPM seems to be only for 11.1. On 11.0 I got too much unresolveld depencies.
Could you build an other RPM 4 11.0 so I can test it too?

thanks

olly

Ah, 11.0 ... but ok, I can do it, but it takes me some time ;-)

Great, works for me, too. Thanks !

It works for a single card, but seems to fail for more as one identical cards, no config files are saved in this case.

Ok, Karsten, I'll change UDI -> UNIQUE and re-test again

With UNIQUE works fine also with serveral devices from same vendor
fixed yast2-network-2.17.64
I'll create maintenance update

The SWAMPID for this issue is 22134.
Please submit the patch and patchinfo file using this ID.
(https://swamp.suse.de/webswamp/wf/22134)

there is no package submission.. please submit yast2-network for 11.0

Update released for: yast2-network, yast2-network-devel-doc
Products:
openSUSE 11.1 (i586, ppc, x86_64)

according comment #26 closed as fixed