A possible bug in the interrupt thread preemption code [Was: Kernel panic in irq14: ata0]

2001-02-22 Thread Maxim Sobolev

Dag-Erling Smorgrav wrote:

> Maxim Sobolev <[EMAIL PROTECTED]> writes:
> > It's not an ata specific problem, but rather a problem of all ISA
> > devices (I have an ISA based ata controller).
>
> I don't think it has anything to do with ISA. I've had similar
> problems on a PCI-only system (actually, PCI+EISA motherboard with no
> EISA cards) with no ATA devices (disks, CD-ROM and streamer are all
> SCSI).
>
> Considering that backing out rev 1.14 of ithread.c eliminates the
> panics, and that that revision is supposed to enable interrupt thread
> preemption, and that the crashed kernels show signs of stack smashing,
> I'd say the cause is probably a bug in the preemption code.

Update: the bug is still here, as of -current from 22 Feb. Hovewer, this time
it even doesn't let to boot into single-user with following panic message:
kernel trap 12 with interrupts disabled
panic: mutex sched lock recursed at ../../kern/kern_synch.c:872

syncing disks...

-Maxim



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Kernel panic in irq14: ata0

2001-02-20 Thread Dag-Erling Smorgrav

Maxim Sobolev <[EMAIL PROTECTED]> writes:
> It's not an ata specific problem, but rather a problem of all ISA
> devices (I have an ISA based ata controller).

I don't think it has anything to do with ISA. I've had similar
problems on a PCI-only system (actually, PCI+EISA motherboard with no
EISA cards) with no ATA devices (disks, CD-ROM and streamer are all
SCSI).

Considering that backing out rev 1.14 of ithread.c eliminates the
panics, and that that revision is supposed to enable interrupt thread
preemption, and that the crashed kernels show signs of stack smashing,
I'd say the cause is probably a bug in the preemption code.

DES
-- 
Dag-Erling Smorgrav - [EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Kernel panic in irq14: ata0

2001-02-20 Thread Soren Schmidt

It seems Maxim Sobolev wrote:
> >
> > Well, I cant reproduce this problem and I havn't heard from others with
> > this problem
> 
> It's not an ata specific problem, but rather a problem of all ISA devices (I have an 
> ISA
> based ata controller).

Well, seems -current is broken in yet another way

-Søren

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Kernel panic in irq14: ata0

2001-02-20 Thread Maxim Sobolev

Soren Schmidt wrote:

> It seems Maxim Sobolev wrote:
> > > Soren Schmidt wrote:
> > > > It seems Maxim Sobolev wrote:
> > > > [Charset koi8-r unsupported, filtering to ASCII...]
> > > > > Hi,
> > > > >
> > > > > I'm not sure whether it's related to ata driver, but starting from several 
>days
> > > > > ago (my previous kernel was from 30 January) my kernel panices on every more 
>or
> > > > > less active ad0 usage (for example, dd if=/dev/ad0 of=/dev/null kills it
> > > > > perfectly). The system in question is Toshiba Satellite Pro 445CDX with
> > > > > isa-based ATA controller. Following is relevant dmesg, kernel config and
> > > > > backtrace of crash dump.
> > > >
> > > > Try to go back to -current from about feb. 8 or there abouts...
> > >
> > > Reverting sys/i386/isa/ithread.c to r1.13 did the trick (credit goes to 
>Alexander N.
> > > Kabaev).
> >
> > Just to let you know that the problem in question is still here (r1.17 of 
>ithread.c).
>
> Well, I cant reproduce this problem and I havn't heard from others with
> this problem

It's not an ata specific problem, but rather a problem of all ISA devices (I have an  
ISA
based ata controller).

-Maxim



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Kernel panic in irq14: ata0

2001-02-20 Thread Soren Schmidt

It seems Maxim Sobolev wrote:
> > Soren Schmidt wrote:
> > > It seems Maxim Sobolev wrote:
> > > [Charset koi8-r unsupported, filtering to ASCII...]
> > > > Hi,
> > > >
> > > > I'm not sure whether it's related to ata driver, but starting from several days
> > > > ago (my previous kernel was from 30 January) my kernel panices on every more or
> > > > less active ad0 usage (for example, dd if=/dev/ad0 of=/dev/null kills it
> > > > perfectly). The system in question is Toshiba Satellite Pro 445CDX with
> > > > isa-based ATA controller. Following is relevant dmesg, kernel config and
> > > > backtrace of crash dump.
> > >
> > > Try to go back to -current from about feb. 8 or there abouts...
> >
> > Reverting sys/i386/isa/ithread.c to r1.13 did the trick (credit goes to Alexander 
>N.
> > Kabaev).
> 
> Just to let you know that the problem in question is still here (r1.17 of ithread.c).

Well, I cant reproduce this problem and I havn't heard from others with
this problem

-Søren

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Kernel panic in irq14: ata0

2001-02-20 Thread Maxim Sobolev

Maxim Sobolev wrote:

> Soren Schmidt wrote:
>
> > It seems Maxim Sobolev wrote:
> > [Charset koi8-r unsupported, filtering to ASCII...]
> > > Hi,
> > >
> > > I'm not sure whether it's related to ata driver, but starting from several days
> > > ago (my previous kernel was from 30 January) my kernel panices on every more or
> > > less active ad0 usage (for example, dd if=/dev/ad0 of=/dev/null kills it
> > > perfectly). The system in question is Toshiba Satellite Pro 445CDX with
> > > isa-based ATA controller. Following is relevant dmesg, kernel config and
> > > backtrace of crash dump.
> >
> > Try to go back to -current from about feb. 8 or there abouts...
>
> Reverting sys/i386/isa/ithread.c to r1.13 did the trick (credit goes to Alexander N.
> Kabaev).

Just to let you know that the problem in question is still here (r1.17 of ithread.c).

-Maxim


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Kernel panic in irq14: ata0

2001-02-12 Thread Maxim Sobolev

Soren Schmidt wrote:

> It seems Maxim Sobolev wrote:
> [Charset koi8-r unsupported, filtering to ASCII...]
> > Hi,
> >
> > I'm not sure whether it's related to ata driver, but starting from several days
> > ago (my previous kernel was from 30 January) my kernel panices on every more or
> > less active ad0 usage (for example, dd if=/dev/ad0 of=/dev/null kills it
> > perfectly). The system in question is Toshiba Satellite Pro 445CDX with
> > isa-based ATA controller. Following is relevant dmesg, kernel config and
> > backtrace of crash dump.
>
> Try to go back to -current from about feb. 8 or there abouts...

Reverting sys/i386/isa/ithread.c to r1.13 did the trick (credit goes to Alexander N.
Kabaev).

-Maxim



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Kernel panic in irq14: ata0

2001-02-12 Thread Soren Schmidt

It seems Maxim Sobolev wrote:
[Charset koi8-r unsupported, filtering to ASCII...]
> Hi,
> 
> I'm not sure whether it's related to ata driver, but starting from several days
> ago (my previous kernel was from 30 January) my kernel panices on every more or
> less active ad0 usage (for example, dd if=/dev/ad0 of=/dev/null kills it
> perfectly). The system in question is Toshiba Satellite Pro 445CDX with
> isa-based ATA controller. Following is relevant dmesg, kernel config and
> backtrace of crash dump.

Try to go back to -current from about feb. 8 or there abouts...

-Søren


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Kernel panic in irq14: ata0

2001-02-12 Thread Maxim Sobolev

Hi,

I'm not sure whether it's related to ata driver, but starting from several days
ago (my previous kernel was from 30 January) my kernel panices on every more or
less active ad0 usage (for example, dd if=/dev/ad0 of=/dev/null kills it
perfectly). The system in question is Toshiba Satellite Pro 445CDX with
isa-based ATA controller. Following is relevant dmesg, kernel config and
backtrace of crash dump.

-Maxim


Copyright (c) 1992-2001 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 5.0-CURRENT #0: Sun Feb 11 02:05:32 EET 2001
root@notebook:/usr/src/sys/compile/NOTEBOOK
Timecounter "i8254"  frequency 1193136 Hz
CPU: Pentium/P55C (132.63-MHz 586-class CPU)
  Origin = "GenuineIntel"  Id = 0x543  Stepping = 3
  Features=0x8001bf
real memory  = 33685504 (32896K bytes)
avail memory = 29745152 (29048K bytes)
Preloaded elf kernel "kernel" at 0xc0302000.
Preloaded elf module "snd_pcm.ko" at 0xc030209c.
Preloaded elf module "snd_mss.ko" at 0xc030213c.
Intel Pentium detected, installing workaround for F00F bug
VESA: v2.0, 2048k memory, flags:0x0, mode table:0xc0293d20 (140)
VESA: CHIPS 6x554 Super VGA
apm0:  on motherboard
apm0: found APM BIOS v1.2, connected at v1.2
npx0:  on motherboard
npx0: INT 16 interface
isa0:  on motherboard
ata0 at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0
ata1 at port 0x170-0x177,0x376 irq 15 on isa0
atkbdc0:  at port 0x60,0x64 on isa0
atkbd0:  irq 1 on atkbdc0
psm0:  irq 12 on atkbdc0
psm0: model GlidePoint, device ID 0
fdc0:  at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
pcic0:  at port 0x3e0-0x3e1 on isa0
pcic0: Polling mode
pccard0:  on pcic0
pccard1:  on pcic0
pcm0:  at port 0x530-0x537,0x370-0x371 irq 5 drq 1 flags 0xc110 on 
isa0
pmtimer0 on isa0
ppc0:  at port 0x378-0x37f irq 7 flags 0x1 on isa0
ppc0: Generic chipset (NIBBLE-only) in NIBBLE mode
plip0:  on ppbus0
sc0:  on isa0
sc0: VGA <16 virtual consoles, flags=0x200>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
vga0:  at port 0x3c0-0x3df iomem 0xa-0xb on isa0
unknown:  can't assign resources
unknown:  can't assign resources
unknown:  can't assign resources
unknown:  can't assign resources
unknown:  can't assign resources
unknown:  can't assign resources
unknown:  can't assign resources
unknown:  can't assign resources
unknown:  can't assign resources
unknown:  can't assign resources
lp0 XXX: driver didn't initialize queue mtx
lo0 XXX: driver didn't initialize queue mtx
ad0: 1376MB  [2796/16/63] at ata0-master BIOSPIO
acd0: CDROM  at ata1-master using BIOSPIO
Mounting root from ufs:/dev/ad0s1a
pccard: card inserted, slot 0
pccard: card inserted, slot 1
WARNING: / was not properly dismounted
ed0 at port 0x240-0x25f irq 3 slot 0 on pccard0
ed0: address 00:80:c8:88:86:b1, type NE2000 (16 bit) 
sio1 at port 0x2e8-0x2ef irq 10 slot 1 on pccard1
sio1: type 16550A

 debug.log

machine i386
cpu I586_CPU # Coz we don't need stuff for I386, I486 and I686
ident   GENERIC
maxusers10

#optionsKTRACE
options FFS
#optionsFFS_ROOT
options NFS
options MSDOSFS
options INET#InterNETworking
options PROCFS  #Process filesystem
options COMPAT_43   #Compatible with BSD 4.3 [KEEP THIS!]
options USERCONFIG  #boot -c editor
options VISUAL_USERCONFIG   #visual boot -c editor
options NSWAPDEV=1
options CLK_USE_I8254_CALIBRATION
options CLK_USE_TSC_CALIBRATION
options USER_LDT
options P1003_1B
options _KPOSIX_PRIORITY_SCHEDULING
options _KPOSIX_VERSION=199309L

device  random

device  isa

#device pcm

device  fdc

device  ata
device  atadisk
device  atapicd

device  atkbdc  1
device  atkbd
device  psm
#optionsPSM_HOOKAPM

device  vga
device  sc  1
options VESA
options SC_PIXEL_MODE
#optionsSC_NO_SYSMOUSE
options SC_TWOBUTTON_MOUSE
options SC_HISTORY_SIZE=1024

device  npx

device  sio

device  apm
device  pmtimer

device  card
device  pcic
device  ed
options PCIC_RESUME_RESET
options POWERFAIL_NMI

# Zip Stuff - comment out if not needed
#device vpo0
#device scbus0 at vpo0
#device  da0

device  ppc
device  ppbus
device  plip
options PPC_PROBE_CHIPSET

# Various Pseudo-Devices
device  loop
device  ether
device  pty
device  splash
device  bpf

options SYSVSHM
options SYSVSEM
options SYSVMSG
options SHMSEG=100