On Sun, 29 Jul 2001, Helen McCall <[EMAIL PROTECTED]> wrote: [...]
>I then rebooted 2.2.19pre17 on the machine with the ISA card properly >configured under 2.2.17, and got a kernel crash: > >Unable to handle kernel paging request at virtual address 81009f8c > >And other such paging errors bringing the kernel tracing into play. > >There seems to be something inherantly broken about the >kernel-image-2.2.19pre17 and kernel-image-2.2.19 on Debian 2.2r3 I can't comment on the kernel-image-* packages as I've never used kernel images for anything but the basic install. I have been succesfully running various kernel releases from 2.2.9 through 2.2.19 with my ISDN card (switched to DSL now, but it's still working), all built from kernel-source-* debs. ISDN support was flaky very early in the 2.2.x cycle, but that's not a Debian issue. >> Can't help with the certificate, although I'm getting the same message >> with kernel 2.2.19 and an Elsa card. I believe that this is a legal >> issue, though, and that it won't affect the driver's functionality. > >I think this is again something to do with the broken nature of the kernel >in Debian 2.2r3. I have got the Debian source for 2.2.19, and also the >source from the kernel project, and I will compare them next week if I can >find the time to compare and compile both sources. This has been the first >time in many years of using Debian that I have found a fundamental >instability in a "stable" release. I recommend building 2.2.19 from a kernel-source-* deb, that works fine for me. [...] >For the time being I have got the ISDN firewall router running properly on >kernel 2.2.17 which I know from past experience is a very stable kernel. >I am also quickly changing the default kernel on this workstation to use >2.2.17 until I can figure out what is wrong with 2.2.19 and 2.2.19pre17. > >Now of course I am going to have to learn how to submit a Debian bug >report, because this is the first time I have needed to, and I have been >using Debian since version 1 (I was using Slackware before that). It's straightforward, just see http://www.debian.org/Bugs/ and follow the instructions. >I might try 2.4.7 on the workstation, and leave 2.2.17 on the firewall >router. I don't want 2.4.x on the firewall because I have a good set of >ipchains definitions for that machine, and I don't want to mess around >converting it all to iptables until I have some free time to learn the new >system. The late 2.2.x kernels have been very stable for me. I'd recommend sticking with that and give 2.4.x some more time. -- Philipp Lehman <[EMAIL PROTECTED]>
