[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

awe problems



i just upgraded to the latest awe-* packages from unstable, and now
when i tried to play a midi file i got:

 AWE32 Sound Driver v0.3.3d (DRAM 0k)
 general protection: 0000
 CPU:    0
 EIP:    0010:[<0282e0be>]
 EFLAGS: 00010206
 eax: 000005d0   ebx: 766f6d09   ecx: 62652525   

 esi: 0285e5d0   edi: 78646525   ebp: 0000001f   

 ds: 0018   es: 0018   fs: 002b   gs: 002b   ss: 

 Process drvmidi (pid: 6084, process nr: 14, stac

 Stack: 00000000 0000001f 00000008 0000001f 00000

        0282d938 0000001f 028a0020 028a3020 0282f

        02848884 00000008 00000000 00ad3005 00000

 Call Trace: [<0282d93f>] [<0282d938>] [<028a0020
02848884>] [<02860000>] 
        [ext2_lookup+129/368] [ext2_lookup+180/36
eaf3>] [<028a3020>] [<0283d87a>] [<028a3020>] [<0

        [<0283d91c>] [<028a3020>] [<02848884>] [<
f39>] [<02848884>] [<0282a08c>] 
        [<02848884>] [sys_write+271/328] [error_c
 
 Code: 66 83 7b 5a 00 7d 0e 53 e8 b5 22 00 00 83 

this used to work fine with the previous release of the awe patch. does
anybody else see this?

--alex--

-- 
| I believe the moment is at hand when, by a paranoiac and active |
|  advance of the mind, it will be possible (simultaneously with  |
|  automatism and other passive states) to systematize confusion  |
|  and thus to help to discredit completely the world of reality. |


Reply to: