Re: panic: resource_list_alloc: resource entry is busy
On Friday, September 12, 2014 10:03:26 PM Marcin Cieslak wrote: > On Fri, 12 Sep 2014, John Baldwin wrote: > >> Please note I originally loaded "i915.ko", not "i915kms.ko" > > > > Oh, that is probably your problem. X loaded i915kms automatically and > > i915 and i915kms do not get along. i915 had already allocated the IRQ > > when i915kms tried to alloc the same IRQ causing the issue. > > Would that be possible to fail with EBUSY or something instead of panic? Yes, though in this case you probably will end up with a black screen and an apparent hang due to how KMS works which wouldn't be a lot better. :( -- John Baldwin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: panic: resource_list_alloc: resource entry is busy
On Fri, 12 Sep 2014, Kevin Oberman wrote: On Fri, Sep 12, 2014 at 1:57 PM, Marcin Cieslak wrote: Please note I originally loaded "i915.ko", not "i915kms.ko" Unfortunately, "kldunload i915kms" makes my screen blank and probably crashes the system (disk activity stops after a short while and there is no response to the keyboard input). //Marcin That explains most of it. You need i915kms. It is conflicting with i915 which already has the IRQ allocated. The black screen is expected. Once KMS starts talking to the graphics system, syscons can no longer talk to the display, so you get a black screen. To have a working display, you must enable vt(4). Add "kern.vty=vt" to /boot/loader.conf to enable vt(4) which will keep the display alive. Yes, I do have "kern.vty=vt" enabled in the loader and without i915kms loaded my system boots correctly. I can load i915kms later per hand or when starting X, but it does not work with bootloader. I think it's a known problem as of September 2nd as stated on the http://wiki.freebsd.org/Newcons page. (My machine is Sony VAIO SZ5MN). //Marcin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: panic: resource_list_alloc: resource entry is busy
On Fri, Sep 12, 2014 at 1:57 PM, Marcin Cieslak wrote: > > > On Fri, 12 Sep 2014, John Baldwin wrote: > > at /usr/src/sys/dev/pci/vga_pci.c:318 >>> 318 return (bus_alloc_resource(dev, type, rid, start, end, >>> count, >>> >> flags)); >> >>> Current language: auto; currently minimal >>> (kgdb) p *rid >>> $1 = 0 >>> >> >> Hmm, type 1 is SYS_RES_IRQ. IRQ resources should not be marked reserved. >> >> Oh, some other child of vgapci has already allocated the IRQ. That seems >> odd. >> >> Can you get 'devinfo -r' output before you kldload i915kms and again after >> doing the kldload? (No need to run startx) >> > > Please note I originally loaded "i915.ko", not "i915kms.ko" > > > Unfortunately, "kldunload i915kms" makes my screen blank > and probably crashes the system (disk activity stops after > a short while and there is no response to the keyboard input). > > //Marcin > > That explains most of it. You need i915kms. It is conflicting with i915 which already has the IRQ allocated. The black screen is expected. Once KMS starts talking to the graphics system, syscons can no longer talk to the display, so you get a black screen. To have a working display, you must enable vt(4). Add "kern.vty=vt" to /boot/loader.conf to enable vt(4) which will keep the display alive. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkober...@gmail.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: panic: resource_list_alloc: resource entry is busy
On Fri, 12 Sep 2014, John Baldwin wrote: Please note I originally loaded "i915.ko", not "i915kms.ko" Oh, that is probably your problem. X loaded i915kms automatically and i915 and i915kms do not get along. i915 had already allocated the IRQ when i915kms tried to alloc the same IRQ causing the issue. Would that be possible to fail with EBUSY or something instead of panic? //Marcin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: panic: resource_list_alloc: resource entry is busy
On Friday, September 12, 2014 08:57:55 PM Marcin Cieslak wrote: > On Fri, 12 Sep 2014, John Baldwin wrote: > >> at /usr/src/sys/dev/pci/vga_pci.c:318 > >> > >> 318return (bus_alloc_resource(dev, type, rid, start, end, > >> count, > > > > flags)); > > > >> Current language: auto; currently minimal > >> (kgdb) p *rid > >> $1 = 0 > > > > Hmm, type 1 is SYS_RES_IRQ. IRQ resources should not be marked reserved. > > > > Oh, some other child of vgapci has already allocated the IRQ. That seems > > odd. > > > > Can you get 'devinfo -r' output before you kldload i915kms and again after > > doing the kldload? (No need to run startx) > > Please note I originally loaded "i915.ko", not "i915kms.ko" Oh, that is probably your problem. X loaded i915kms automatically and i915 and i915kms do not get along. i915 had already allocated the IRQ when i915kms tried to alloc the same IRQ causing the issue. -- John Baldwin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: panic: resource_list_alloc: resource entry is busy
On Fri, 12 Sep 2014, John Baldwin wrote: at /usr/src/sys/dev/pci/vga_pci.c:318 318 return (bus_alloc_resource(dev, type, rid, start, end, count, flags)); Current language: auto; currently minimal (kgdb) p *rid $1 = 0 Hmm, type 1 is SYS_RES_IRQ. IRQ resources should not be marked reserved. Oh, some other child of vgapci has already allocated the IRQ. That seems odd. Can you get 'devinfo -r' output before you kldload i915kms and again after doing the kldload? (No need to run startx) Please note I originally loaded "i915.ko", not "i915kms.ko" Full output of the devinfo -r attached (no modules, w/i915 and w/i915kms), snippets: pcib0 I/O ports: 0xcf8-0xcff pci0 PCI domain 0 bus numbers: 0 hostb0 vgapci0 I/O ports: 0x1800-0x1807 I/O memory addresses: 0xd000-0xdfff 0xf830-0xf837 0xf840-0xf843 agp0 I/O memory addresses: 0x8000-0x8fff acpi_video0 vgapci1 I/O memory addresses: 0xf838-0xf83f With i915.ko loaded: pcib0 I/O ports: 0xcf8-0xcff pci0 PCI domain 0 bus numbers: 0 hostb0 vgapci0 Interrupt request lines: 16 I/O ports: 0x1800-0x1807 I/O memory addresses: 0xd000-0xdfff 0xf830-0xf837 0xf840-0xf843 agp0 I/O memory addresses: 0x8000-0x8fff acpi_video0 drm0 vgapci1 I/O memory addresses: 0xf838-0xf83f with i915kms.ko loaded: pcib0 I/O ports: 0xcf8-0xcff pci0 PCI domain 0 bus numbers: 0 hostb0 vgapci0 Interrupt request lines: 16 I/O ports: 0x1800-0x1807 I/O memory addresses: 0xd000-0xdfff 0xf830-0xf837 0xf840-0xf843 agp0 I/O memory addresses: 0x8000-0x8fff acpi_video0 drmn0 intel_iicbb0 iicbb0 iicbus0 iicsmb0 smbus0 smb0 iic0 intel_gmbus0 iicbus1 iicsmb1 smbus1 smb1 iic1 intel_iicbb1 iicbb1 iicbus2 iicsmb2 smbus2 smb2 iic2 intel_gmbus1 iicbus3 iicsmb3 smbus3 smb3 iic3 intel_iicbb2 iicbb2 iicbus4 iicsmb4 smbus4 smb4 iic4 intel_gmbus2 iicbus5 iicsmb5 smbus5 smb5 iic5 intel_iicbb3 iicbb3 iicbus6 iicsmb6 smbus6 smb6 iic6 intel_gmbus3 iicbus7 iicsmb7 smbus7 smb7 iic7 intel_iicbb4 iicbb4 iicbus8 iicsmb8 smbus8 smb8 iic8 intel_gmbus4 iicbus9 iicsmb9 smbus9 smb9 iic9 intel_iicbb5 iicbb5 iicbus10 iicsmb10 smbus10 smb10 iic10 intel_gmbus5 iicbus11 iicsmb11 smbus11 smb11 iic11 intel_iicbb6 iicbb6 iicbus12 iicsmb12 smbus12 smb12 iic12 intel_gmbus6 iicbus13 iicsmb13 smbus13 smb13 iic13 intel_iicbb7 iicbb7 iicbus14 iicsmb14 smbus14 smb14 iic14 intel_gmbus7 iicbus15 iicsmb15 smbus15 smb15 iic15 fbd0 vgapc
Re: panic: resource_list_alloc: resource entry is busy
On Friday, September 12, 2014 05:45:31 PM Marcin Cieslak wrote: > On Wed, 10 Sep 2014, John Baldwin wrote: > > On Wednesday, September 10, 2014 12:45:08 PM Marcin Cieslak wrote: > >> On my CURRENT as of 6 Sep (r271197): > >> > >> What I did was that: > >> > >> - kldload i915 > >> > >> - startx > >> > >> During X server start I get the following: > >> > >> #10 0x808c2947 in resource_list_alloc (rl=, > >> bus=, child=, type= >> optimized out>, > >> > >> rid=, start=, end= >> > >> optimized out>, count=, flags=) > >> > >> at /usr/src/sys/kern/subr_bus.c:3304 > >> > >> #11 0x8061ddae in pci_alloc_resource (dev=, > >> child=, type=, rid= >> optimized out>, > >> > >> start=, end=, count= >> > >> optimized out>, flags=) at > >> /usr/src/sys/dev/pci/pci.c:4604 #12 0x808c4420 in > >> bus_alloc_resource (dev=0xf800026d8800, type=1, > >> rid=0x811effc8, > >> start=632, end=18446744071580876744, count=464, flags=100707968) at > >> bus_if.h:284 > >> #13 0x80626092 in vga_pci_alloc_resource (dev=0xf800026d8800, > >> child=, type=1, rid=0xf80008c0b2d4, start=0, > >> > >> end=, count=18446744071580876744, flags= >> > >> optimized out>) at /usr/src/sys/dev/pci/vga_pci.c:318 > > > > Can you load the core dump in kgdb and run 'f 13' and 'p *rid'? > > Sure, here it goes: > > (kgdb) f 13 > #13 0x80626092 in vga_pci_alloc_resource ( > dev=0xf800026d8800, child=, type=1, > rid=0xf80008c0b2d4, start=0, end=, > count=18446744071580876744, flags=) > at /usr/src/sys/dev/pci/vga_pci.c:318 > 318 return (bus_alloc_resource(dev, type, rid, start, end, count, flags)); > Current language: auto; currently minimal > (kgdb) p *rid > $1 = 0 Hmm, type 1 is SYS_RES_IRQ. IRQ resources should not be marked reserved. Oh, some other child of vgapci has already allocated the IRQ. That seems odd. Can you get 'devinfo -r' output before you kldload i915kms and again after doing the kldload? (No need to run startx) -- John Baldwin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: panic: resource_list_alloc: resource entry is busy
On Wed, 10 Sep 2014, John Baldwin wrote: On Wednesday, September 10, 2014 12:45:08 PM Marcin Cieslak wrote: On my CURRENT as of 6 Sep (r271197): What I did was that: - kldload i915 - startx During X server start I get the following: #10 0x808c2947 in resource_list_alloc (rl=, bus=, child=, type=, rid=, start=, end=, count=, flags=) at /usr/src/sys/kern/subr_bus.c:3304 #11 0x8061ddae in pci_alloc_resource (dev=, child=, type=, rid=, start=, end=, count=, flags=) at /usr/src/sys/dev/pci/pci.c:4604 #12 0x808c4420 in bus_alloc_resource (dev=0xf800026d8800, type=1, rid=0x811effc8, start=632, end=18446744071580876744, count=464, flags=100707968) at bus_if.h:284 #13 0x80626092 in vga_pci_alloc_resource (dev=0xf800026d8800, child=, type=1, rid=0xf80008c0b2d4, start=0, end=, count=18446744071580876744, flags=) at /usr/src/sys/dev/pci/vga_pci.c:318 Can you load the core dump in kgdb and run 'f 13' and 'p *rid'? Sure, here it goes: (kgdb) f 13 #13 0x80626092 in vga_pci_alloc_resource ( dev=0xf800026d8800, child=, type=1, rid=0xf80008c0b2d4, start=0, end=, count=18446744071580876744, flags=) at /usr/src/sys/dev/pci/vga_pci.c:318 318 return (bus_alloc_resource(dev, type, rid, start, end, count, flags)); Current language: auto; currently minimal (kgdb) p *rid $1 = 0 //Marcin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: panic: resource_list_alloc: resource entry is busy
On Wednesday, September 10, 2014 12:45:08 PM Marcin Cieslak wrote: > On my CURRENT as of 6 Sep (r271197): > > What I did was that: > > - kldload i915 > > - startx > > During X server start I get the following: > > #10 0x808c2947 in resource_list_alloc (rl=, > bus=, child=, type= optimized out>, > rid=, start=, end= optimized out>, count=, flags=) > at /usr/src/sys/kern/subr_bus.c:3304 > #11 0x8061ddae in pci_alloc_resource (dev=, > child=, type=, rid= optimized out>, > start=, end=, count= optimized out>, flags=) at > /usr/src/sys/dev/pci/pci.c:4604 #12 0x808c4420 in > bus_alloc_resource (dev=0xf800026d8800, type=1, rid=0x811effc8, > start=632, end=18446744071580876744, count=464, flags=100707968) at > bus_if.h:284 > #13 0x80626092 in vga_pci_alloc_resource (dev=0xf800026d8800, > child=, type=1, rid=0xf80008c0b2d4, start=0, > end=, count=18446744071580876744, flags= optimized out>) at /usr/src/sys/dev/pci/vga_pci.c:318 Can you load the core dump in kgdb and run 'f 13' and 'p *rid'? -- John Baldwin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: panic: resource_list_alloc
On Sun, Mar 25, 2001 at 05:58:53AM +0100, Cameron Grant wrote: > can you try http://people.freebsd.org/~cg/mssfix.diff.gz ? Fixed my panics too. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic: resource_list_alloc
>From: "Cameron Grant" <[EMAIL PROTECTED]> >Date: Sun, 25 Mar 2001 05:58:53 +0100 >can you try http://people.freebsd.org/~cg/mssfix.diff.gz ? Yup. Works -- thanks! (Same kernel config that I had been using: I didn't disable sound.) Cheers, david -- David H. Wolfskill [EMAIL PROTECTED] As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic: resource_list_alloc
> just upgraded my tree and did a reinstall ... trace is: > > resource_list_alloc(c0d9eec0,c0d90180,c0d99b80,4,c0d4a30c) at resource_list_alloc+0xd3 > isa_alloc_resource() @ +0xd0 > bus_alloc_resource() @ +0x5f > opti_detect @ +0x99 > mss_detect @ +0x52 > mss_probe @ +0x30a > device_probe_child @ +0xca > device_probe_and_attach @ +0x41 > isa_probe_children @ +0xde > configure @ +0x32 > mi_startup @ +0x6e > begin @ +0x29 can you try http://people.freebsd.org/~cg/mssfix.diff.gz ? -cg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: panic: resource_list_alloc
On 25-Mar-01 The Hermit Hacker wrote:
>
> removing pcm fixes the panic, it appears ...
David O`Brien just confirmed it on his box as well.
> On Sat, 24 Mar 2001, John Baldwin wrote:
>
>>
>> On 25-Mar-01 The Hermit Hacker wrote:
>> >
>> > just upgraded my tree and did a reinstall ... trace is:
>> >
>> > resource_list_alloc(c0d9eec0,c0d90180,c0d99b80,4,c0d4a30c) at
>> > resource_list_alloc+0xd3
>> > isa_alloc_resource() @ +0xd0
>> > bus_alloc_resource() @ +0x5f
>> > opti_detect @ +0x99
>>
>> This is the second such one I've seen in opti_detect. I'm guessing that
>> 'mms'
>> is a sound driver? If so, can you try taking it out of your kernel to see
>> if
>> that is what is causing the panic?
>>
>> > mss_detect @ +0x52
>> > mss_probe @ +0x30a
>> > device_probe_child @ +0xca
>> > device_probe_and_attach @ +0x41
>> > isa_probe_children @ +0xde
>> > configure @ +0x32
>> > mi_startup @ +0x6e
>> > begin @ +0x29
>> >
>> > Marc G. Fournier ICQ#7615664 IRC Nick:
>> > Scrappy
>> > Systems Administrator @ hub.org
>> > primary: [EMAIL PROTECTED] secondary:
>> > scrappy@{freebsd|postgresql}.org
>> >
>> >
>> > To Unsubscribe: send mail to [EMAIL PROTECTED]
>> > with "unsubscribe freebsd-current" in the body of the message
>>
>> --
>>
>> John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/
>> PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
>> "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
>>
>
> Marc G. Fournier ICQ#7615664 IRC Nick:
> Scrappy
> Systems Administrator @ hub.org
> primary: [EMAIL PROTECTED] secondary:
> scrappy@{freebsd|postgresql}.org
>
--
John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
RE: panic: resource_list_alloc
On 25-Mar-01 The Hermit Hacker wrote:
>
> doing so right now ... one quick/stupid question ... how does one
> 'reinstall' a new kernel so that you don't lose the /boot/kernel.old (aka
> backup that worked)? I've been moving files around before installing the
> rebuilt kernel, but that doesn't sound very efficient ... :)
>
> thanks ..
# cd /sys/compile/FOO
# < build like normal >
# make reinstall
Also, if you want to be super careful, keep a /boot/kernel.good lying around
that has a known working kernel in it.
> On Sat, 24 Mar 2001, John Baldwin wrote:
>
>>
>> On 25-Mar-01 The Hermit Hacker wrote:
>> >
>> > just upgraded my tree and did a reinstall ... trace is:
>> >
>> > resource_list_alloc(c0d9eec0,c0d90180,c0d99b80,4,c0d4a30c) at
>> > resource_list_alloc+0xd3
>> > isa_alloc_resource() @ +0xd0
>> > bus_alloc_resource() @ +0x5f
>> > opti_detect @ +0x99
>>
>> This is the second such one I've seen in opti_detect. I'm guessing that
>> 'mms'
>> is a sound driver? If so, can you try taking it out of your kernel to see
>> if
>> that is what is causing the panic?
>>
>> > mss_detect @ +0x52
>> > mss_probe @ +0x30a
>> > device_probe_child @ +0xca
>> > device_probe_and_attach @ +0x41
>> > isa_probe_children @ +0xde
>> > configure @ +0x32
>> > mi_startup @ +0x6e
>> > begin @ +0x29
>> >
>> > Marc G. Fournier ICQ#7615664 IRC Nick:
>> > Scrappy
>> > Systems Administrator @ hub.org
>> > primary: [EMAIL PROTECTED] secondary:
>> > scrappy@{freebsd|postgresql}.org
>> >
>> >
>> > To Unsubscribe: send mail to [EMAIL PROTECTED]
>> > with "unsubscribe freebsd-current" in the body of the message
>>
>> --
>>
>> John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/
>> PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
>> "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
>>
>
> Marc G. Fournier ICQ#7615664 IRC Nick:
> Scrappy
> Systems Administrator @ hub.org
> primary: [EMAIL PROTECTED] secondary:
> scrappy@{freebsd|postgresql}.org
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
--
John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: panic: resource_list_alloc
Try "make reinstall". I have been doing quite a bit of this since my kernel panics before it ever gets all the way up. The last good kernel I have is about a month old. Actually, I moved /boot/kernel.old to another name in case I accidentally did an install instead of a reinstall. I don't want to leave my machine unable to boot. Jim Bloom [EMAIL PROTECTED] The Hermit Hacker wrote: > > doing so right now ... one quick/stupid question ... how does one > 'reinstall' a new kernel so that you don't lose the /boot/kernel.old (aka > backup that worked)? I've been moving files around before installing the > rebuilt kernel, but that doesn't sound very efficient ... :) > > thanks .. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic: resource_list_alloc
On Sat, Mar 24, 2001 at 11:24:47PM -0400, The Hermit Hacker wrote: > > doing so right now ... one quick/stupid question ... how does one > 'reinstall' a new kernel so that you don't lose the /boot/kernel.old (aka make reinstall -or- make kernel-reinstall > removing pcm fixes the panic, it appears ... Yep! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: panic: resource_list_alloc
removing pcm fixes the panic, it appears ...
On Sat, 24 Mar 2001, John Baldwin wrote:
>
> On 25-Mar-01 The Hermit Hacker wrote:
> >
> > just upgraded my tree and did a reinstall ... trace is:
> >
> > resource_list_alloc(c0d9eec0,c0d90180,c0d99b80,4,c0d4a30c) at
> > resource_list_alloc+0xd3
> > isa_alloc_resource() @ +0xd0
> > bus_alloc_resource() @ +0x5f
> > opti_detect @ +0x99
>
> This is the second such one I've seen in opti_detect. I'm guessing that 'mms'
> is a sound driver? If so, can you try taking it out of your kernel to see if
> that is what is causing the panic?
>
> > mss_detect @ +0x52
> > mss_probe @ +0x30a
> > device_probe_child @ +0xca
> > device_probe_and_attach @ +0x41
> > isa_probe_children @ +0xde
> > configure @ +0x32
> > mi_startup @ +0x6e
> > begin @ +0x29
> >
> > Marc G. Fournier ICQ#7615664 IRC Nick:
> > Scrappy
> > Systems Administrator @ hub.org
> > primary: [EMAIL PROTECTED] secondary:
> > scrappy@{freebsd|postgresql}.org
> >
> >
> > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > with "unsubscribe freebsd-current" in the body of the message
>
> --
>
> John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/
> PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
> "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
>
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
RE: panic: resource_list_alloc
doing so right now ... one quick/stupid question ... how does one
'reinstall' a new kernel so that you don't lose the /boot/kernel.old (aka
backup that worked)? I've been moving files around before installing the
rebuilt kernel, but that doesn't sound very efficient ... :)
thanks ..
On Sat, 24 Mar 2001, John Baldwin wrote:
>
> On 25-Mar-01 The Hermit Hacker wrote:
> >
> > just upgraded my tree and did a reinstall ... trace is:
> >
> > resource_list_alloc(c0d9eec0,c0d90180,c0d99b80,4,c0d4a30c) at
> > resource_list_alloc+0xd3
> > isa_alloc_resource() @ +0xd0
> > bus_alloc_resource() @ +0x5f
> > opti_detect @ +0x99
>
> This is the second such one I've seen in opti_detect. I'm guessing that 'mms'
> is a sound driver? If so, can you try taking it out of your kernel to see if
> that is what is causing the panic?
>
> > mss_detect @ +0x52
> > mss_probe @ +0x30a
> > device_probe_child @ +0xca
> > device_probe_and_attach @ +0x41
> > isa_probe_children @ +0xde
> > configure @ +0x32
> > mi_startup @ +0x6e
> > begin @ +0x29
> >
> > Marc G. Fournier ICQ#7615664 IRC Nick:
> > Scrappy
> > Systems Administrator @ hub.org
> > primary: [EMAIL PROTECTED] secondary:
> > scrappy@{freebsd|postgresql}.org
> >
> >
> > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > with "unsubscribe freebsd-current" in the body of the message
>
> --
>
> John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/
> PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
> "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
>
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
RE: panic: resource_list_alloc
On 25-Mar-01 The Hermit Hacker wrote:
>
> just upgraded my tree and did a reinstall ... trace is:
>
> resource_list_alloc(c0d9eec0,c0d90180,c0d99b80,4,c0d4a30c) at
> resource_list_alloc+0xd3
> isa_alloc_resource() @ +0xd0
> bus_alloc_resource() @ +0x5f
> opti_detect @ +0x99
This is the second such one I've seen in opti_detect. I'm guessing that 'mms'
is a sound driver? If so, can you try taking it out of your kernel to see if
that is what is causing the panic?
> mss_detect @ +0x52
> mss_probe @ +0x30a
> device_probe_child @ +0xca
> device_probe_and_attach @ +0x41
> isa_probe_children @ +0xde
> configure @ +0x32
> mi_startup @ +0x6e
> begin @ +0x29
>
> Marc G. Fournier ICQ#7615664 IRC Nick:
> Scrappy
> Systems Administrator @ hub.org
> primary: [EMAIL PROTECTED] secondary:
> scrappy@{freebsd|postgresql}.org
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
--
John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
