Re: [ANOMALIES]: 2.4.2 - __alloc_pages: failed - Causes more thenjust msgs
On Tue, 27 Feb 2001, Shawn Starr wrote: > When added with BUG(); it will hang /dev/dsp. If the device is opened and we oops before closing it, subsequent open attempts will fail (busy). If it hangs after a failed high order allocation attempt without the BUG() insertion, that could be called a driver bug. -Mike - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ANOMALIES]: 2.4.2 - __alloc_pages: failed - Causes more thenjust msgs
On Tue, 27 Feb 2001, Shawn Starr wrote: When added with BUG(); it will hang /dev/dsp. If the device is opened and we oops before closing it, subsequent open attempts will fail (busy). If it hangs after a failed high order allocation attempt without the BUG() insertion, that could be called a driver bug. -Mike - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ANOMALIES]: 2.4.2 - __alloc_pages: failed - Causes more thenjust msgs
When added with BUG(); it will hang /dev/dsp. I'm not sure if it did without it. I'll be restarting with the removed BUG(); soon. On Tue, 27 Feb 2001, Mike Galbraith wrote: > On Mon, 26 Feb 2001, Shawn Starr wrote: > > > It may not be an important message but what does happen is /dev/dsp becomes > > hung and no sound works after the fault. So something is definately wrong. > > Do you mean it hangs without the BUG() inserted, or only after the oops? > > -Mike > > > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ANOMALIES]: 2.4.2 - __alloc_pages: failed - Causes more thenjust msgs
On Mon, 26 Feb 2001, Shawn Starr wrote: > It may not be an important message but what does happen is /dev/dsp becomes > hung and no sound works after the fault. So something is definately wrong. Do you mean it hangs without the BUG() inserted, or only after the oops? -Mike - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ANOMALIES]: 2.4.2 - __alloc_pages: failed - Causes more thenjust msgs
On Mon, 26 Feb 2001, Shawn Starr wrote: It may not be an important message but what does happen is /dev/dsp becomes hung and no sound works after the fault. So something is definately wrong. Do you mean it hangs without the BUG() inserted, or only after the oops? -Mike - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ANOMALIES]: 2.4.2 - __alloc_pages: failed - Causes more thenjust msgs
When added with BUG(); it will hang /dev/dsp. I'm not sure if it did without it. I'll be restarting with the removed BUG(); soon. On Tue, 27 Feb 2001, Mike Galbraith wrote: On Mon, 26 Feb 2001, Shawn Starr wrote: It may not be an important message but what does happen is /dev/dsp becomes hung and no sound works after the fault. So something is definately wrong. Do you mean it hangs without the BUG() inserted, or only after the oops? -Mike - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
