lkml.org 
[lkml]   [1998]   [Jun]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectYet another panic
Kernel: 2.1.105ac5, devfs patch (devfs mounted before init), SMP (on
SMP). Even though my BIOS seems to be Ok (but I didn't try those
activities), I disabled it in kernel and everything else PCI-related
there is ON.

Jun 12 22:52:08 vadim kernel: PCI: Using configuration type 1
Jun 12 22:52:08 vadim kernel: PCI: Probing PCI hardware
Jun 12 22:52:08 vadim kernel: PCI->APIC IRQ transform: (B0,I17,P0) -> 16
Jun 12 22:52:08 vadim kernel: PCI->APIC IRQ transform: (B1,I4,P0) -> 17
Jun 12 22:52:08 vadim kernel: PCI->APIC IRQ transform: (B1,I5,P0) -> 18
Jun 12 22:52:08 vadim kernel: PCI->APIC IRQ transform: (B1,I8,P0) -> 17
Jun 12 22:52:08 vadim kernel: PCI->APIC IRQ transform: (B1,I12,P0) -> 17
Jun 12 22:52:08 vadim kernel: PCI->APIC IRQ transform: (B0,I19,P0) -> 18
Jun 12 22:52:08 vadim kernel: PCI->APIC IRQ transform: (B0,I20,P0) -> 19
Jun 12 22:52:08 vadim kernel: PCI: 00:00 [8086/1237]: Passive release
enable (00)
Jun 12 22:52:08 vadim kernel: PIIX3: Enabling Passive Release
Jun 12 22:52:08 vadim kernel: PCI: 00:90 [1011/0001]: Bridge
optimization (00)
Jun 12 22:52:08 vadim kernel: Cache L2: Not supported.
Jun 12 22:52:08 vadim kernel: CPU-PCI posted write: off -> on.
Jun 12 22:52:08 vadim kernel: CPU-Memory posted write: off -> on.
Jun 12 22:52:08 vadim kernel: PCI-Memory posted write: off -> on.
Jun 12 22:52:08 vadim kernel: PCI burst: off -> on.

BTW, I wonder if these 2 lines are good:
Jun 12 22:52:08 vadim kernel: PCI->APIC IRQ transform: (B1,I5,P0) -> 18
Jun 12 22:52:08 vadim kernel: PCI->APIC IRQ transform: (B0,I19,P0) -> 18

but this should't be related to the problem (B1,I5,P0 is 7810, not used.
B0,I19,P0 is S3 card)

Related hardware: AHA-3985 (3*7870), disks used were both quantums on
channels 1 and 2 (i.e. 2nd and 3rd). Partitions were small (800mb) in
the beginning of the disk.

Bus 1, device 4, function 0:
SCSI storage controller: Adaptec AIC-7873 (rev 3).
Medium devsel. Fast back-to-back capable. IRQ 11. Master
Capable. Latency=32. Min Gnt=8.Max Lat=8.
I/O at 0xd000 [0xd001].
Non-prefetchable 32 bit memory at 0xf6afc000 [0xf6afc000].
Bus 1, device 5, function 0:
Memory: Adaptec AIC-7810 RAID (rev 0).
Medium devsel. Fast back-to-back capable. IRQ 12. Master
Capable. Latency=32. Min Gnt=2.Max Lat=2.
I/O at 0xd400 [0xd401].
Non-prefetchable 32 bit memory at 0xf6afd000 [0xf6afd000].
Prefetchable 32 bit memory at 0xf5600000 [0xf5600008].
Bus 1, device 8, function 0:
SCSI storage controller: Adaptec AIC-7873 (rev 3).
Medium devsel. Fast back-to-back capable. IRQ 11. Master
Capable. Latency=32. Min Gnt=8.Max Lat=8.
I/O at 0xd800 [0xd801].
Non-prefetchable 32 bit memory at 0xf6afe000 [0xf6afe000].
Bus 1, device 12, function 0:
SCSI storage controller: Adaptec AIC-7873 (rev 3).
Medium devsel. Fast back-to-back capable. IRQ 11. Master
Capable. Latency=32. Min Gnt=8.Max Lat=8.
I/O at 0xdc00 [0xdc01].
Non-prefetchable 32 bit memory at 0xf6aff000 [0xf6aff000].
a) 7810 isn't used at all
b) *note* that it's on bus *1*. I.e. that thing has PCI-to-PCI bridge on
board.


Activity: playing with raid0/raid1:
a) mkraid on raid1
b) mke2fs on raid0
Either of these activities results in following:

Sorry, copied stuff by hand, so there might be an error. I skipped some
info (like stack trace). If you need more - tell me & I'll type it in.

page fault from irq handler
CPU: 1
EIP: 0010:[<c01d8ad7>]
eax: 00000006 ebx: c0004874 ecx: c8800000 edx: 00000000
esi: c0004874 edi: 00000011 ebp: 00000246 esp: c0107ee0
ds == es == ss == 0018
Process swapper (bla-bla)
Stack: bla
Call Trace: bla
Code: bla
Aiee, killing interrupt handler
Kernel panic: attemted to kill the idle task!
In swapper - not syncing

Using `/usr/src/linux/System.map' to map addresses to symbols.

>>EIP: c01d8ad7 <pci_read_config_byte+f/24>
Trace: c0167eff <ip_setsockopt+12f/7ac>
Trace: c01ce64b <aic7xxx_pci_intr+1b/14c>
Trace: c0107eff <this_must_match_init_task+1eff/2000>
Trace: c01ce7e8 <aic7xxx_isr+6c/588>
Trace: c01ced74 <do_aic7xxx_isr+70/2f8>
Trace: c0107fa4 <this_must_match_init_task+1fa4/2000>
Trace: c0107fa4 <this_must_match_init_task+1fa4/2000>
Trace: c010d63d <handle_IRQ_event+35/58>
Trace: c0107fa4 <this_must_match_init_task+1fa4/2000>
Trace: c0112077 <do_level_ioapic_IRQ+d3/168>
Trace: c0107fa4 <this_must_match_init_task+1fa4/2000>
Trace: c0107fa4 <this_must_match_init_task+1fa4/2000>
Trace: c0107fa4 <this_must_match_init_task+1fa4/2000>
Trace: c0106000 <init_task_union>
Trace: c0107f9c <this_must_match_init_task+1f9c/2000>
Trace: c011d54d <do_bottom_half+7d/a0>
Trace: c010d7cc <do_IRQ+38/58>
Trace: c0107fa4 <this_must_match_init_task+1fa4/2000>
Trace: c010b15c <ret_from_intr>
Trace: c0106000 <init_task_union>
Trace: c0107fa4 <this_must_match_init_task+1fa4/2000>
Trace: c0106000 <init_task_union>
Trace: c01094d0 <cpu_idle+40/11c>
Trace: c01001c4 <L6>
Code: c01d8ad7 <pci_read_config_byte+f/24>
Code: c01d8ad7 <pci_read_config_byte+f/24> 0f b6 42 14 movzbl
0x14(%edx),%eax
Code: c01d8adb <pci_read_config_byte+13/24> 50 pushl
%eax
Code: c01d8adc <pci_read_config_byte+14/24> 86 02 xchgb
%al,(%edx)
Code: c01d8ade <pci_read_config_byte+16/24> 0f b6 40 1c movzbl
0x1c(%eax),%eax
Code: c01d8ae2 <pci_read_config_byte+1a/24> e8 08 88 f3 ff call
fff38818 <_EIP+0xfff38818>
Code: c01d8ae7 <pci_read_config_byte+1f/24> 83 c4 10 addl
$0x10,%esp
Code: c01d8aea <pci_read_config_byte+22/24> 00 00 addb
%al,(%eax)
Code: c01d8aec <pci_read_config_word> 90 nop
Code: c01d8aed <pci_read_config_word+1/24> 90 nop
Code: c01d8aee <pci_read_config_word+2/24> 90 nop

Main question: should I try using by BIOS now & report, or no need for
that info?


Vadim

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu

\
 
 \ /
  Last update: 2005-03-22 13:43    [from the cache]
©2003-2011 Jasper Spaans