Re: kernel panic on kldload in 6.1
On Fri, May 19, 2006 at 04:59:44PM -0400, Joe Auty wrote: > > On May 19, 2006, at 2:38 PM, Kris Kennaway wrote: > > >On Thu, May 18, 2006 at 10:54:19PM -0400, Joe Auty wrote: > >> > >>On May 18, 2006, at 12:36 AM, Kris Kennaway wrote: > >> > >>>On Wed, May 17, 2006 at 07:06:59PM -0400, Joe Auty wrote: > Hello, > > A problem I've had since 6.0 remains in 6.1 where my machine kernel > panics at boot trying to kldload some module (it doesn't say which > one). It also does not log this panic. > > I suppose this isn't terribly helpful information, but if there is > anything you can suggest I do (including pass this on to an > interested party), please let me know how I can help =) > >>> > >>>It sounds like you have an old (6.0) module you're still trying to > >>>load. Things like the nvidia driver and other ports are prime > >>>candidates. > >>> > >> > >> > >>Hi, I tried commenting out all of the kernel modules in /boot/ > >>loader.conf, and I'm still panicing. I wrote down some of the panic > >>message this time. > >> > >>The code is "superviser read, page not present" > >> > >>the panic output is: > >> > >>panic: page fault > >> > >> > >>Unless you guys have any ideas of things I can try, I'll just file > >>this. > >> > >>Any ideas? > > > >So you claimed originally that it was due to kldloading "some module", > >but now you're still getting the same panic when you're not kldloading > >anything? Can you please clarify exactly what is the situation? > > > >I suspect you're still actually kldloading something (modules are > >loaded on demand for some things): did you boot into single-user mode > >and confirm that all modules are up-to-date? > > > > > I'm getting this error message during boot time, not during manual > loading of modules. As I said, some modules are loaded on demand. Not when booting single-user though. > I'm getting this error message despite disabling > all my third-party modules listed in /boot/loader.conf. I'm assuming > that all modules stored in /boot/kernel are system modules, and it > would be expected that they would all be able to run without kernel > panicing during boot? > > Sorry for my lack of clarity! Where I became unclear was probably in > saying "some module". During boot time, once this panic is spewed > onto my screen, it doesn't indicate which (system) module it is > choking on. The rest of the panic message would have given more details though. > This panic occurred in single user mode under 6.0 too, I haven't > tried single user mode in 6.1 yet Kris pgpXjY9PVxWY4.pgp Description: PGP signature
Re: kernel panic on kldload in 6.1
On May 19, 2006, at 2:38 PM, Kris Kennaway wrote: On Thu, May 18, 2006 at 10:54:19PM -0400, Joe Auty wrote: On May 18, 2006, at 12:36 AM, Kris Kennaway wrote: On Wed, May 17, 2006 at 07:06:59PM -0400, Joe Auty wrote: Hello, A problem I've had since 6.0 remains in 6.1 where my machine kernel panics at boot trying to kldload some module (it doesn't say which one). It also does not log this panic. I suppose this isn't terribly helpful information, but if there is anything you can suggest I do (including pass this on to an interested party), please let me know how I can help =) It sounds like you have an old (6.0) module you're still trying to load. Things like the nvidia driver and other ports are prime candidates. Hi, I tried commenting out all of the kernel modules in /boot/ loader.conf, and I'm still panicing. I wrote down some of the panic message this time. The code is "superviser read, page not present" the panic output is: panic: page fault Unless you guys have any ideas of things I can try, I'll just file this. Any ideas? So you claimed originally that it was due to kldloading "some module", but now you're still getting the same panic when you're not kldloading anything? Can you please clarify exactly what is the situation? I suspect you're still actually kldloading something (modules are loaded on demand for some things): did you boot into single-user mode and confirm that all modules are up-to-date? I'm getting this error message during boot time, not during manual loading of modules. I'm getting this error message despite disabling all my third-party modules listed in /boot/loader.conf. I'm assuming that all modules stored in /boot/kernel are system modules, and it would be expected that they would all be able to run without kernel panicing during boot? Sorry for my lack of clarity! Where I became unclear was probably in saying "some module". During boot time, once this panic is spewed onto my screen, it doesn't indicate which (system) module it is choking on. This panic occurred in single user mode under 6.0 too, I haven't tried single user mode in 6.1 yet --- Joe Auty NetMusician: web publishing software for musicians http://www.netmusician.org [EMAIL PROTECTED] PGP.sig Description: This is a digitally signed message part
Re: kernel panic on kldload in 6.1
On Thu, May 18, 2006 at 10:54:19PM -0400, Joe Auty wrote: > > On May 18, 2006, at 12:36 AM, Kris Kennaway wrote: > > > On Wed, May 17, 2006 at 07:06:59PM -0400, Joe Auty wrote: > >> Hello, > >> > >> A problem I've had since 6.0 remains in 6.1 where my machine kernel > >> panics at boot trying to kldload some module (it doesn't say which > >> one). It also does not log this panic. > >> > >> I suppose this isn't terribly helpful information, but if there is > >> anything you can suggest I do (including pass this on to an > >> interested party), please let me know how I can help =) > > > > It sounds like you have an old (6.0) module you're still trying to > > load. Things like the nvidia driver and other ports are prime > > candidates. > > > > > Hi, I tried commenting out all of the kernel modules in /boot/ > loader.conf, and I'm still panicing. I wrote down some of the panic > message this time. > > The code is "superviser read, page not present" > > the panic output is: > > panic: page fault > > > Unless you guys have any ideas of things I can try, I'll just file this. > > Any ideas? So you claimed originally that it was due to kldloading "some module", but now you're still getting the same panic when you're not kldloading anything? Can you please clarify exactly what is the situation? I suspect you're still actually kldloading something (modules are loaded on demand for some things): did you boot into single-user mode and confirm that all modules are up-to-date? Kris pgpm1YMEwUxXq.pgp Description: PGP signature
Re: kernel panic on kldload in 6.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On May 18, 2006, at 12:36 AM, Kris Kennaway wrote: On Wed, May 17, 2006 at 07:06:59PM -0400, Joe Auty wrote: Hello, A problem I've had since 6.0 remains in 6.1 where my machine kernel panics at boot trying to kldload some module (it doesn't say which one). It also does not log this panic. I suppose this isn't terribly helpful information, but if there is anything you can suggest I do (including pass this on to an interested party), please let me know how I can help =) It sounds like you have an old (6.0) module you're still trying to load. Things like the nvidia driver and other ports are prime candidates. Hi, I tried commenting out all of the kernel modules in /boot/ loader.conf, and I'm still panicing. I wrote down some of the panic message this time. The code is "superviser read, page not present" the panic output is: panic: page fault Unless you guys have any ideas of things I can try, I'll just file this. Any ideas? - --- Joe Auty NetMusician: web publishing software for musicians http://www.netmusician.org [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (Darwin) iD8DBQFEbTNcCgdfeCwsL5ERAvchAJ4toYHlfKLLcZV6XoedQQi3DDKLqwCeLZsX BHq3DxDtX+cg2gSPNqAaUVo= =XNLD -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kernel panic on kldload in 6.1
On Thu, May 18, 2006 at 10:57:51AM +0200, Frank Steinborn wrote: > Kris Kennaway wrote: > > It sounds like you have an old (6.0) module you're still trying to > > load. Things like the nvidia driver and other ports are prime > > candidates. > > > > Kris > > Does that mean that all the panic-issues with kld(un)load are fixed in > 6.1? I crashed an important 6.0-STABLE box several times by trying to > unload procfs for example and I don't want to run in such nightmares > again by fiddling with klds unless I'm sure it's safe now. No, it means that modules are not cross-compatible between releases. Please retest your problem with 6.1 and file a PR if you encounter it again; it's the only way it will get fixed. Kris pgpZEQzA6e4Uv.pgp Description: PGP signature
Re: kernel panic on kldload in 6.1
Kris Kennaway wrote: > It sounds like you have an old (6.0) module you're still trying to > load. Things like the nvidia driver and other ports are prime > candidates. > > Kris Does that mean that all the panic-issues with kld(un)load are fixed in 6.1? I crashed an important 6.0-STABLE box several times by trying to unload procfs for example and I don't want to run in such nightmares again by fiddling with klds unless I'm sure it's safe now. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kernel panic on kldload in 6.1
On Wed, May 17, 2006 at 07:06:59PM -0400, Joe Auty wrote: > Hello, > > A problem I've had since 6.0 remains in 6.1 where my machine kernel > panics at boot trying to kldload some module (it doesn't say which > one). It also does not log this panic. > > I suppose this isn't terribly helpful information, but if there is > anything you can suggest I do (including pass this on to an > interested party), please let me know how I can help =) It sounds like you have an old (6.0) module you're still trying to load. Things like the nvidia driver and other ports are prime candidates. Kris pgpYkbmbQlDEV.pgp Description: PGP signature
Re: kernel panic on kldload in 6.1
On Wed, 17 May 2006, Joe Auty wrote: A problem I've had since 6.0 remains in 6.1 where my machine kernel panics at boot trying to kldload some module (it doesn't say which one). It also does not log this panic. I suppose this isn't terribly helpful information, but if there is anything you can suggest I do (including pass this on to an interested party), please let me know how I can help =) If it were me, I would: 1. Boot from a fixit CD 2. Mount my partitions from the afflicted disk(s) 3. Start commenting out lines in /boot/loader.conf I'd probably start by commenting everything in /boot/loader.conf, but you could also use a binary search type procedure. Eventually it should become clear what the culprit is. HTH. -- Chris Hill [EMAIL PROTECTED] ** [ Busy Expunging <|> ] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
