Freebsd 5.3 Drivers cause Kernel Panic

OSS specific BSD discussion (FreeBSD/NetBSD/OpenBSD)

Moderators: cesium, dev, kodachi, hannu

Freebsd 5.3 Drivers cause Kernel Panic

Postby Freedevil » Sun Nov 07, 2004 7:10 am

OSS 3.99.1i oss3991i-freebsd-x86-v5.3-RELEASE.tar.gz used upon running oss-install it detects the cards fine if you run self audio test machine panics and hangs but i was logged into X at that time.

Upon reboot reinstalled them ran soundon

SBLIVE: CANT ALLOCATE PTA TABLE
fault code = supervisor write, page not present
instruction pointer = 0x8:0xc0340f7f
stack pointer = 0x10:0xd885ee28
frame pointer = 0x10:0xd885ee4c
code segment = base 0x0, limit 0xfffff, type 0x1b
=DPL 0, pres 1, def32 1, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 599 (sndconf)
trap number = 12
panic: page fault
Freedevil
 

Re: Freebsd 5.3 Drivers cause Kernel Panic

Postby dev » Sun Nov 07, 2004 6:26 pm

Freedevil wrote:OSS 3.99.1i oss3991i-freebsd-x86-v5.3-RELEASE.tar.gz used upon running oss-install it detects the cards fine if you run self audio test machine panics and hangs but i was logged into X at that time.

Upon reboot reinstalled them ran soundon

SBLIVE: CANT ALLOCATE PTA TABLE
fault code = supervisor write, page not present
instruction pointer = 0x8:0xc0340f7f
stack pointer = 0x10:0xd885ee28
frame pointer = 0x10:0xd885ee4c
code segment = base 0x0, limit 0xfffff, type 0x1b
=DPL 0, pres 1, def32 1, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 599 (sndconf)
trap number = 12
panic: page fault



I've just tested SBLive on my 5.3-RELEASE wiith the latest OSS
and no problems here. I'd recommend that you use the "RELEASE"
kernel - make sure that the kernel drivers aren't being loaded.

Is this a dualproc or single proc machine?


regards
Dev
dev
Developer
 
Posts: 578
Joined: Fri Sep 12, 2003 6:08 am
Location: Culver City, CA

Re: Freebsd 5.3 Drivers cause Kernel Panic

Postby dev » Sun Nov 07, 2004 6:49 pm

Freedevil wrote:OSS 3.99.1i oss3991i-freebsd-x86-v5.3-RELEASE.tar.gz used upon running oss-install it detects the cards fine if you run self audio test machine panics and hangs but i was logged into X at that time.

Upon reboot reinstalled them ran soundon

SBLIVE: CANT ALLOCATE PTA TABLE
fault code = supervisor write, page not present
instruction pointer = 0x8:0xc0340f7f
stack pointer = 0x10:0xd885ee28
frame pointer = 0x10:0xd885ee4c
code segment = base 0x0, limit 0xfffff, type 0x1b
=DPL 0, pres 1, def32 1, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 599 (sndconf)
trap number = 12
panic: page fault



BTW, how much memory does you system have?

best regards
Dev Mazumdar
dev
Developer
 
Posts: 578
Joined: Fri Sep 12, 2003 6:08 am
Location: Culver City, CA

Postby Guest » Sun Nov 07, 2004 7:07 pm

hey dev

vampire# uname -a
FreeBSD vampire.bloodlust.net 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Sat Nov 6 07:38:35 EST 2004 root@vampire.bloodlust.net:/usr/src/sys/i386/compile/ESCAFLOWNE i386

Memory = 1 gb
Swap = 2gb

Single Processor System

No Sound drivers in kernel as you know 5.3 has a new sound.ko module system you can directly load emu10k with kldload.Ii still get the same error with oss drivers

OSS: UNABLE TO ALLOCATE 4096 bytes for a DMA Buffer and the kernel panic message previously posted.

If by RELEASE kernel you mean GENERIC? then no i have built my own kernel.
For furthur clarification you can view my kernel here htttp://unixdaemon.org/ESCAFLOWNE.txt

vampire# cat /boot/loader.conf
linux_load="YES"
nvidia_load="YES"
agp_load="YES"
#snd_emu10k1_load="YES"
hw.ata.atapi_dma=1
hw.ata.ata_dma=1
#bktr_load="YES"

As soon you can see no sound being loaded as far as i know soundconf will not run unless all modules connected to sound are loaded, so i am guessing that is not the problem. I am surprised it worked for you cuz uhh my machine has hung 3 times now with kernel panics.
Guest
 

Postby Freedevil » Sun Nov 07, 2004 9:55 pm

Well i booted kernel.old the GENERIC kernel and the drivers work fine.

Few problems here
a) what does oss need specifically from the kernel
b) Mainly hardware is tuned in my kernel which does not concern sound as far as i know

I am gonna try and fiddle with the settings i guess but do take a look at my kernel cuz i am pretty sure other users migth face this too
Freedevil
 

Postby Guest » Sun Nov 07, 2004 10:54 pm

Well i had to unhash useless stuff from my kernel cuz i guess i dont have the time or spare machine to test this out at the moment, so i have oss drivers working now. I have 6 speaker logitech set but i cannot hear my front left speaker all other 5 are working. Not sure what to do here any help would be appreciated. by the way its sb live 5.1 card
Guest
 

Postby Guest » Sun Nov 07, 2004 10:57 pm

err nevermind i seemed to have fixed the issue all 6 speakers work now but i'll try and work on the kernel trouble
Guest
 

Postby Guest » Tue Nov 09, 2004 5:57 pm

i've the same problem:
FreeBSD 5.3 with custom kernel -> kernel panic
i hope u find it out whats so important in the GENERIC kernel, and what misses at ours.

cya
Benjamin
Guest
 

Postby dev » Tue Nov 09, 2004 6:52 pm

Freedevil wrote:Well i booted kernel.old the GENERIC kernel and the drivers work fine.

Few problems here
a) what does oss need specifically from the kernel
b) Mainly hardware is tuned in my kernel which does not concern sound as far as i know

I am gonna try and fiddle with the settings i guess but do take a look at my kernel cuz i am pretty sure other users migth face this too


Perhaps you should diff between /usr/src/sys/i386/conf/GENERIC and your kernel and see what's different.

Does OSS bomb if you compile the GENERIC kernel (what I mean is if you generate a GENERIC kernel on your machine and reboot and run soundon)?


best regards
Dev
dev
Developer
 
Posts: 578
Joined: Fri Sep 12, 2003 6:08 am
Location: Culver City, CA

Postby Guest » Wed Nov 10, 2004 12:34 am

hey dev the diferences like i pointed there are maninly hardware options like raid scsi etc. Now when i say GNERIC kernel its the 5.3-RELEASE kernel i rebuilt that the one you tested oss on and sure it runs fine. But when i look at my own kernel ESCAFLOWNE and GENERIC the differences are here i dont use raid ro scsi so i have them #'ed out I have picked my own usb and ethernet options. Added firewall suport and dvd bruning thats it!!! The fact that soundon panics by this leaves me baffled.
Guest
 

panic

Postby devm » Wed Nov 10, 2004 4:50 pm

Anonymous wrote:hey dev the diferences like i pointed there are maninly hardware options like raid scsi etc. Now when i say GNERIC kernel its the 5.3-RELEASE kernel i rebuilt that the one you tested oss on and sure it runs fine. But when i look at my own kernel ESCAFLOWNE and GENERIC the differences are here i dont use raid ro scsi so i have them #'ed out I have picked my own usb and ethernet options. Added firewall suport and dvd bruning thats it!!! The fact that soundon panics by this leaves me baffled.



I really cannot tell you why recompiling your kernel causes the segfault.
The thing I would like you to do is just recompile GENERIC on your
machine and see if the compiled kernel has problems or not.


Send us your kernel config so that we can recompile it on our machines. It (will take time unless you have a paid OSS license key.).
devm
 

Postby Freedevil » Thu Nov 11, 2004 2:15 am

YEs i do have a paid license my kernel was posted previously like i said in my previous posts its running fine with GENERIC you can grab a copy of my kernel where oss segfaults http://unixdaemon.org/ESCAFLOWNE.txt <--- feel free to build it and test it
Freedevil
 

Postby Guest » Thu Nov 11, 2004 2:18 am

really cannot tell you why recompiling your kernel causes the segfault.
The thing I would like you to do is just recompile GENERIC on your
machine and see if the compiled kernel has problems or not.


This is the main reason i decided to post it here.
Guest
 

Postby Freedevil » Thu Nov 11, 2004 2:22 am

Heres the current working kernel for oss http://unixdaemon.org/NEWKERNEL.txt

Heres the diffrence between ESCAFLOWNE where oss kernel panics and NEWKERNEL where it works.

Usless stuff no good to me irrevalant to sound

# SCSI Controllers
device ahb # EISA AHA1742 family
device ahc # AHA2940 and onboard AIC7xxx devices
device ahd # AHA39320/29320 and onboard AIC79xx devices
device amd # AMD 53C974 (Tekram DC-390(T))
device isp # Qlogic family
device mpt # LSI-Logic MPT-Fusion
#device ncr # NCR/Symbios Logic
device sym # NCR/Symbios Logic (newer chipsets + those of `ncr')
device trm # Tekram DC395U/UW/F DC315U adapters
device adv # Advansys SCSI adapters
device adw # Advansys wide SCSI adapters
device aha # Adaptec 154x SCSI adapters
device aic # Adaptec 15[012]x SCSI adapters, AIC-6[23]60.
device bt # Buslogic/Mylex MultiMaster SCSI adapters

device ncv # NCR 53C500
device nsp # Workbit Ninja SCSI-3
device stg # TMC 18C30/18C50
Freedevil
 

Postby Freedevil » Thu Nov 11, 2004 2:27 am

Benjamin unhash the scsci part and take a look at NEWKERNEL.txt it works fine as far as i can tell SCSI was the option that stopped it from panicking wweird yeah tell me about it its a pain to fsck 300gb hard disks :)
Freedevil
 

Next

Return to BSD

Who is online

Users browsing this forum: No registered users and 1 guest

cron