Summary: | FCDSL causes Kernel Panic when downloading files | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | MonkeyIsland <parkmann> |
Component: | [OLD] Core system | Assignee: | Gentoo Dialup Developers <net-dialup> |
Status: | RESOLVED FIXED | ||
Severity: | critical | CC: | bs.net, sbriesen |
Priority: | High | Keywords: | Bug |
Version: | 2004.3 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
fcdsl-2.6.20.7-r2.ebuild
fcdsl.diff |
Description
MonkeyIsland
2005-01-05 16:44:59 UTC
did your machine displayed an ops message? try to deactivate acpi. You can read the oops in the german forum post, where this report comes from: http://forums.gentoo.org/viewtopic.php?t=275028 (As he mentioned there, he typed it manually from the screen, so it must have been really hard work) By running without XDM i finally got this kernel Panic Message: Oops: 0000 [#2] PREEMPT Modules linked in : ppp_synctty ppp-generic slhc fcdsl capi capifs kernelcapi CPU: 0 EIP: 0060:[<c0102b88>] Tainted: P VLI EIP is at show_trace+0x28/0x90 eax:00000019 ebx:00030001 ecx:07070707 edx:00000082 esi:00030001 edi:00030000 ebp:000030ffd esp:c049cf48 ds:007b es:007b ss:0068 Process swapper (pid:0,threadinfo=c049c000 task=c03e2b00 Stack: c039b60e c01042de c049d150 00000018 00000000 00000001 c0102c70 00000000 c049d0f0 c649d0bc 00000000 c0102c00 00000000 c049d0f0 00000000 c049c000 c03e2b00 00010017 c03e53c2 c049d0bc c039c44b c010dc30 00000000 Call trace: [<c01042dc>] do_IRQ+0x3c/0x60 [<c0102c70>] show_stack+0x80(0xa0 [<c0102e00>] show_register+0x150/0x1b0 [<c010dc30>] do_page_fault+0x0/0x5c7 [<c0103007>] die+0xf7/0x140 [<c010dc30>] do_page_fault+0x0/0x5c7 [<c01133b7>] printk+0x17/0x20 [<c010de61>] do_page_fault+0x231/05c7 ======================================= [<c01307a4>] irq_exit+0x34/0x40 [<c01042e5>] do_irq+0x45/0x60 [<c010289a>] common_interruput+0x1a/0x20 [<c01005f0>] default_idle+0x0/0x30 [<c010068a>] cpu_idle+0x3a/0x60 [<c0470762>] start_kernel+0x142/0x160 [<c0470360>] unknown_bootoption+0x0/0x1b0 Code: 00 00 00 55 57 56 53 83 ec c8 8b 5c 24 20 89 df 89 de 81 e7 00 f0 ff ff 8d af fd 0f 00 00 90 8 d 74 26 00 39 fe 76 43 39 fe 76 43 39 ee 73 3f <8b> 1e 83 c6 04 84 1c 24 e8 eb 10 02 00 85 00 74 e7 84 5c 24 04 <0> Kernel panit - not syncing : Fatal exeption in interrupt Here is what cat /proc/interrupts shows: CPU0 0: 417780 XT-PIC timer 1: 935 XT-PIC i8042 2: 0 XT-PIC cascade 10: 0 XT-PIC ohci_hcd 11: 2 XT-PIC ehci_hcd 12: 27766 XT-PIC ohci_hcd, fcdsl 14: 78123 XT-PIC ide0 15: 22 XT-PIC ide1 NMI: 0 ERR: 0 As he stated in the forum, he solved it by downloading the source from: ftp://ftp.avm.de/cardware/fritzcrd.dsl/linux/suse.91/fcdsl-suse9.1-3.11-02.tar.gz and applying this patch: http://freiburg.linux.de/~zeisberg/howtos/fcdsl.diff I will leave the inclusion in the ebuild up to you, as the bug is ASSIGNED. this package already have an ebuild (net-dialup/fcpci). do you think we should patch fcpci? net-dialup/fcdsl-2.6.20.7 is the ebuild in question .. and I think we should reSRC_URI and epatch it at least, to get a newer version: For old tarballs and some patches: (rpm2targz to extract the patches) ftp://ftp.gwdg.de/pub/linux/suse/ftp.suse.com/suse/i386/9.2/suse/src/avm_fcdsl-2.6-27.src.rpm ftp://ftp.avm.de/cardware/ fritzcrd.ds*/linux dirs for the latest tarballs. patches referred to by the user: http://freiburg.linux.de/~zeisberg/howtos/fcdsl.diff http://freiburg.linux.de/~zeisberg/howtos/fcdsl-sl.diff http://freiburg.linux.de/~zeisberg/howtos/fcdsl-sl-usb.diff Should I sort that out, or would you like to do that? I am very busy at work right now. If you sorted out this issues, please do the changes. MonkeyIsland: How do you find out the real driver version from an source archive? I need something to judge which archive is newer .. I haven't a problem with the driver with any 2.6.10 version (now gentoo-sources-2.6.10-r6), but that means nothing. Well, the driver from AVM homepage is newer... src/devfs.h => 0.4.1 the version in net-dialup/fcdsl-2.6.20.7 src/devfs.h => 0.4.0 The ebuild pointing to the driver for SuSE 9.1. The current version could be for SuSE 9.2. I think it would be good to reSRC the whole ebuild and applying the patches... That could solve that problem... This is the current packaged SuSE version (2.6.27) ftp://ftp.suse.com/pub/suse/i386/9.2/suse/src/avm_fcdsl-2.6-27.src.rpm The package version is younger than the homepage one, but the version is 0.4.0, too. When reSRC the package, should we split it into own ebuild for each card? Created attachment 49107 [details]
fcdsl-2.6.20.7-r2.ebuild
ok, this is the new ebuild for the avm sources
I did not add the patch as it did not apply cleanly here ..
Can you please test if it works for you out of the box and if the patch is
really needed?
Created attachment 49108 [details, diff]
fcdsl.diff
fixed diff for the avm sources, I am not sure if this is even needed .. I left
one hunk out because it was changed in the current revision.
Well I'm trying to test tonight. As far as I know the patch is for stability reasons. IMHO, MonkeyIsland should look if this solve his problems. When so, I think it would be good that this version become stable as soon as possible... what do you think about the versioning? I think we should have this one named -0.4.1, as the driver-revision and not some strange suse-numbers count imo. Should I add this to portage, have you tested it? 0.4.1 vor all package aren't the right version for all of the five packages included in this ebuild. The version for fcdsl package is only 0.4.1 the other packages could have other revision numbers. IMHO, one could be going to net-dialup/fcdsl-2.6.ebuild (generally for 2.6, revision by -r*) or net-dialup/fcdsl-2.6.0.ebuild (generally for 2.6, driver revisions 0-n, package revision by -r*) because the package (and therefore all drivers, now) is created for kernel 2.6 I prefer the second scheme. What do you think? Haven't tested it, yet. But, I think in 3-4 hours. O.K. tests are running... Well one problem I notice: installation target for fcdsl.ko was /lib/modules/.../misc. Now it is /lib/modules.../net. /lib/modules/.../misc ist cfgpro therefore there a two different versions of the driver when upgrading. IMHO a info for the user is helpful. The other results in one hour. Without the patch it seems to work for me. Well I'm switching to SMP no, so I post my results here, too. Using gentoo-sources-2.6.10-r6. Well are the MonkeyIsland's problems are gone, now? Well, smp (ht) seems to work, too. Now, seeing and waiting what MonkeyIsland says. MonkeyIsland: Could you please try it and comment? Sorry guys, I fried my PC (actually only the Mainboard), here is a little advice to all of you, when you want to use self soldered circuits on your pc <- make shure you insulate the properly ... AHHHH but everything is fine again now, the new MB has the same nforce2 chipset as the board i fried so gentoo is running as if nothing happened ...puh Back to the kernel panic issue, I will test the patch as soon as someone tells me what to do. Which driver to use etc, or should I just emerge the new ebuild? Again sorry for answering so late hope we can finish this soon. emerge -va =fcdsl-2.6.20.7-r3 ^ That will test what we have currently in portage w/o the patch. if you want to apply the patch make CTRL+Z after "source unpacked" and cd into /var/tmp/portage/fcdsl-2.6.20.7-r3/work then do patch -p1 < /path/to/patch finally fg to resume emerge need info if the patch is really needed Cant emerge the new ebuild it keeps saying no digest file avaible and download failed :( the new ebuild is already in portage for ~x86, you only need to verify if the attached patch is really needed. Hi Currently I was one of the other people having kernel panics while downloading files. More info about this could be found here: http://forums.gentoo.org/viewtopic.php?t=218125 Currently I gave the new ebuilds a new try. I'm now running gentoo-dev-sources-2.6.10-r7 and applied the diff-file-patch to fcdsl-2.6.20.7-r3 Without the patches I got the same kernel panics as before and I'm now running some stress tests to see if the patch gives me a stable connection. I got some bigger downoads finished, so as far as I could tell at this time THE PATCH IS NEEDED, or at least it's more stable with it If I run into any further troubles I will report back so long pi I think we then need this patch for all fcdsl's: fcdsl fcdsl2 fcdslsl fcdslusb fcdslslusb I do not own the hardware and therefore cannot test it. It needs to be modified for the different cards. Stefan: can you please test the patch for what you own? I have nothing of it. I have: 1. AVM B1 -> active card, needs only firmware 2. AVM Fritz! USB v2.0 -> 'fritzcapi' 3. AVM Fritz! PCI -> 'fritzcapi' 4. AVM Fritz! PCMCIA -> 'fritzcapi' 5. AVM Fritz!Box SL -> driverless (Router/DSL-Modem) 'fcdsl' is for the AVM DSL/ISDN-Cards with CAPI support. I don't have such card. :-/ ok, I adjustet the patch for all fritzcarddsl's, I need testing now. http://dev.gentoo.org/~genstef/files/overlay/fcdsl.tar You can see the single patches there: http://dev.gentoo.org/~genstef/files/overlay/fcdsl/files I added a -r4 ebuild with the patches to the portage tree. Thank you all |