public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* 2.6.18-mm2 networking problem + IRQ panic
@ 2006-10-02 23:07 Badari Pulavarty
  2006-10-02 23:22 ` Andrew Morton
  0 siblings, 1 reply; 4+ messages in thread
From: Badari Pulavarty @ 2006-10-02 23:07 UTC (permalink / raw)
  To: Eric W. Biederman, akpm; +Cc: lkml, suka

[-- Attachment #1: Type: text/plain, Size: 1919 bytes --]

Hi,

I am having problem bringing up networking on 2.6.18-mm2.
I don't see any interrupts for eth0. I also see "cannot 
handle IRQ" panic on shutdown - wondering if they are related..

           CPU0       CPU1       CPU2       CPU3
  0:     112736     117883     117738     123737    IO-APIC-edge  timer
  1:          0          0          1         10    IO-APIC-edge  i8042
  4:          0          1          0        477    IO-APIC-edge  serial
  6:          0          0          0          5    IO-APIC-edge  floppy
  8:          0          0          0          0    IO-APIC-edge  rtc
  9:          0          0          0          0   IO-APIC-level  acpi
 12:          0         42          6         65    IO-APIC-edge  i8042
 14:       4869       1911       3449       6079    IO-APIC-edge  ide0
 15:          0      11051       4806        847    IO-APIC-edge  ide1
 17:      55636          0          5          0   IO-APIC-level  eth0
NMI:        216         40         38         41
LOC:     471992     471992     472046     471481
ERR:          0
MIS:          0


Everything works fine on 2.6.18.

(I saw similar report by Sukadev on 2.6.18-mm1).
dmesg shows (similar messages about unable to allocate messages):

PCI: Cannot allocate resource region 0 of device 0000:08:01.1
PCI: Cannot allocate resource region 0 of device 0000:08:02.1
PCI: Cannot allocate resource region 0 of device 0000:08:03.1
PCI: Cannot allocate resource region 0 of device 0000:08:04.1

Thanks,
Badari


INIT:do_IRQ: cannot handle IRQ -1
----------- [cut here ] --------- [please bite here ] ---------
Kernel BUG at arch/x86_64/kernel/irq.c:118
invalid opcode: 0000 [1] SMP
last sysfs file: /devices/pci0000:00/0000:00:06.0/irq
CPU 1
Modules linked in: acpi_cpufreq ipv6 thermal processor fan button
battery ac dm_mod floppy parport_pc lp parport
Pid: 1, comm: init Not tainted 2.6.18-mm2 #1
RIP: 0010:[<ffffffff8020ced0>]



[-- Attachment #2: lspci.out --]
[-- Type: text/plain, Size: 10243 bytes --]

00:06.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8111 PCI (rev 07) (prog-if 00 [Normal decode])
	Flags: bus master, 66MHz, medium devsel, latency 64
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=68
	I/O behind bridge: 00002000-00002fff
	Memory behind bridge: fa000000-fa0fffff
	Prefetchable memory behind bridge: e2000000-e20fffff
	Capabilities: [c0] HyperTransport: Slave or Primary Interface
	Capabilities: [f0] HyperTransport: Interrupt Discovery and Configuration

00:07.0 ISA bridge: Advanced Micro Devices [AMD] AMD-8111 LPC (rev 05)
	Subsystem: Advanced Micro Devices [AMD] AMD-8111 LPC
	Flags: bus master, 66MHz, medium devsel, latency 0

00:07.1 IDE interface: Advanced Micro Devices [AMD] AMD-8111 IDE (rev 03) (prog-if 8a [Master SecP PriP])
	Subsystem: Advanced Micro Devices [AMD] AMD-8111 IDE
	Flags: bus master, medium devsel, latency 64
	I/O ports at 1020 [size=16]

00:07.3 Bridge: Advanced Micro Devices [AMD] AMD-8111 ACPI (rev 05)
	Subsystem: Advanced Micro Devices [AMD] AMD-8111 ACPI
	Flags: medium devsel

00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
	Flags: fast devsel
	Capabilities: [80] HyperTransport: Host or Secondary Interface
	Capabilities: [a0] HyperTransport: Host or Secondary Interface
	Capabilities: [c0] HyperTransport: Host or Secondary Interface

00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
	Flags: fast devsel

00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
	Flags: fast devsel

00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
	Flags: fast devsel

00:19.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
	Flags: fast devsel
	Capabilities: [80] HyperTransport: Host or Secondary Interface
	Capabilities: [a0] HyperTransport: Host or Secondary Interface
	Capabilities: [c0] HyperTransport: Host or Secondary Interface

00:19.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
	Flags: fast devsel

00:19.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
	Flags: fast devsel

00:19.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
	Flags: fast devsel

00:1a.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
	Flags: fast devsel
	Capabilities: [80] HyperTransport: Host or Secondary Interface
	Capabilities: [a0] HyperTransport: Host or Secondary Interface
	Capabilities: [c0] HyperTransport: Host or Secondary Interface

00:1a.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
	Flags: fast devsel

00:1a.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
	Flags: fast devsel

00:1a.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
	Flags: fast devsel

00:1b.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
	Flags: fast devsel
	Capabilities: [80] HyperTransport: Host or Secondary Interface
	Capabilities: [a0] HyperTransport: Host or Secondary Interface
	Capabilities: [c0] HyperTransport: Host or Secondary Interface

00:1b.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
	Flags: fast devsel

00:1b.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
	Flags: fast devsel

00:1b.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
	Flags: fast devsel

01:00.0 USB Controller: Advanced Micro Devices [AMD] AMD-8111 USB (rev 0b) (prog-if 10 [OHCI])
	Flags: bus master, medium devsel, latency 64, IRQ 11
	Memory at fa000000 (32-bit, non-prefetchable) [size=4K]

01:00.1 USB Controller: Advanced Micro Devices [AMD] AMD-8111 USB (rev 0b) (prog-if 10 [OHCI])
	Flags: bus master, medium devsel, latency 64, IRQ 11
	Memory at fa001000 (32-bit, non-prefetchable) [size=4K]

01:04.0 SCSI storage controller: QLogic Corp. QLA2200 64-bit Fibre Channel Adapter (rev 05)
	Subsystem: QLogic Corp. QLA2200
	Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 5
	I/O ports at 2000 [size=256]
	Memory at fa002000 (32-bit, non-prefetchable) [size=4K]
	[virtual] Expansion ROM at e2000000 [disabled] [size=128K]
	Capabilities: [44] Power Management version 1

01:05.0 SCSI storage controller: QLogic Corp. QLA2200 64-bit Fibre Channel Adapter (rev 05)
	Subsystem: QLogic Corp. QLA2200
	Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 10
	I/O ports at 2400 [size=256]
	Memory at fa003000 (32-bit, non-prefetchable) [size=4K]
	[virtual] Expansion ROM at e2020000 [disabled] [size=128K]
	Capabilities: [44] Power Management version 1

08:01.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8131 PCI-X Bridge (rev 12) (prog-if 00 [Normal decode])
	Flags: bus master, 66MHz, medium devsel, latency 99
	Bus: primary=08, secondary=09, subordinate=0e, sec-latency=64
	Memory behind bridge: fa400000-faffffff
	Prefetchable memory behind bridge: 00000000fc000000-00000000fdf00000
	Capabilities: [a0] PCI-X bridge device
	Capabilities: [b8] HyperTransport: Interrupt Discovery and Configuration
	Capabilities: [c0] HyperTransport: Slave or Primary Interface

08:01.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X IOAPIC (rev 01) (prog-if 10 [IO-APIC])
	Subsystem: Advanced Micro Devices [AMD] Unknown device 7450
	Flags: bus master, medium devsel, latency 0
	Memory at e2300000 (64-bit, non-prefetchable) [size=4K]

08:02.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8131 PCI-X Bridge (rev 12) (prog-if 00 [Normal decode])
	Flags: bus master, 66MHz, medium devsel, latency 64
	Bus: primary=08, secondary=0f, subordinate=13, sec-latency=64
	I/O behind bridge: 00003000-00003fff
	Memory behind bridge: fb000000-fb0fffff
	Prefetchable memory behind bridge: 00000000e2100000-00000000e2100000
	Capabilities: [a0] PCI-X bridge device
	Capabilities: [b8] HyperTransport: Interrupt Discovery and Configuration

08:02.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X IOAPIC (rev 01) (prog-if 10 [IO-APIC])
	Subsystem: Advanced Micro Devices [AMD] Unknown device 7450
	Flags: bus master, medium devsel, latency 0
	Memory at e2301000 (64-bit, non-prefetchable) [size=4K]

08:03.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8131 PCI-X Bridge (rev 12) (prog-if 00 [Normal decode])
	Flags: bus master, 66MHz, medium devsel, latency 64
	Bus: primary=08, secondary=14, subordinate=18, sec-latency=64
	Capabilities: [a0] PCI-X bridge device
	Capabilities: [b8] HyperTransport: Interrupt Discovery and Configuration
	Capabilities: [c0] HyperTransport: Slave or Primary Interface

08:03.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X IOAPIC (rev 01) (prog-if 10 [IO-APIC])
	Subsystem: Advanced Micro Devices [AMD] Unknown device 7450
	Flags: bus master, medium devsel, latency 0
	Memory at e2302000 (64-bit, non-prefetchable) [size=4K]

08:04.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8131 PCI-X Bridge (rev 12) (prog-if 00 [Normal decode])
	Flags: bus master, 66MHz, medium devsel, latency 64
	Memory at fa3e3000 (64-bit, non-prefetchable) [size=4K]
	Bus: primary=08, secondary=19, subordinate=1d, sec-latency=64
	I/O behind bridge: 00004000-00004fff
	Memory behind bridge: fb100000-fb1fffff
	Prefetchable memory behind bridge: 00000000e2200000-00000000e2200000
	Capabilities: [a0] PCI-X bridge device
	Capabilities: [b8] HyperTransport: Interrupt Discovery and Configuration
	Capabilities: [90] #0c [000a]
	Capabilities: [98] Power Management version 2

08:04.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X IOAPIC (rev 01) (prog-if 10 [IO-APIC])
	Subsystem: Advanced Micro Devices [AMD] Unknown device 7450
	Flags: bus master, medium devsel, latency 0
	Memory at e2303000 (64-bit, non-prefetchable) [size=4K]

09:01.0 PCI bridge: Hint Corp HB6 Universal PCI-PCI bridge (non-transparent mode) (rev 12) (prog-if 00 [Normal decode])
	Flags: bus master, medium devsel, latency 99
	Bus: primary=09, secondary=0a, subordinate=0a, sec-latency=69
	Memory behind bridge: fa400000-faffffff
	Prefetchable memory behind bridge: 00000000fc000000-00000000fdf00000
	Capabilities: [80] Power Management version 2
	Capabilities: [90] #06 [0000]
	Capabilities: [a0] Vital Product Data

0a:00.0 VGA compatible controller: Matrox Graphics, Inc. G400/G450 (rev 85) (prog-if 00 [VGA])
	Subsystem: Matrox Graphics, Inc. Millennium G450 Dual Head PCI
	Flags: medium devsel, IRQ 10
	Memory at fc000000 (32-bit, prefetchable) [size=32M]
	Memory at fa400000 (32-bit, non-prefetchable) [size=16K]
	Memory at fa800000 (32-bit, non-prefetchable) [size=8M]
	[virtual] Expansion ROM at fa420000 [disabled] [size=128K]
	Capabilities: [dc] Power Management version 2
	Capabilities: [f0] AGP version 2.0

0f:01.0 Fibre Channel: QLogic Corp. QLA2312 Fibre Channel Adapter (rev 02)
	Subsystem: QLogic Corp. Unknown device 0100
	Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 10
	I/O ports at 3000 [size=256]
	Memory at fb000000 (64-bit, non-prefetchable) [size=4K]
	[virtual] Expansion ROM at e2100000 [disabled] [size=128K]
	Capabilities: [44] Power Management version 2
	Capabilities: [4c] PCI-X non-bridge device
	Capabilities: [54] Message Signalled Interrupts: 64bit+ Queue=0/3 Enable-
	Capabilities: [64] #06 [0080]

19:01.0 SCSI storage controller: QLogic Corp. QLA2200 64-bit Fibre Channel Adapter (rev 05)
	Subsystem: QLogic Corp. QLA2200
	Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 10
	I/O ports at 4000 [size=256]
	Memory at fb110000 (32-bit, non-prefetchable) [size=4K]
	[virtual] Expansion ROM at e2200000 [disabled] [size=128K]
	Capabilities: [44] Power Management version 1

19:02.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5701 Gigabit Ethernet (rev 15)
	Subsystem: 3Com Corporation 3C996B-T 1000Base-T
	Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 38
	Memory at fb100000 (64-bit, non-prefetchable) [size=64K]
	Capabilities: [40] PCI-X non-bridge device
	Capabilities: [48] Power Management version 2
	Capabilities: [50] Vital Product Data
	Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/3 Enable-


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: 2.6.18-mm2 networking problem + IRQ panic
  2006-10-02 23:07 2.6.18-mm2 networking problem + IRQ panic Badari Pulavarty
@ 2006-10-02 23:22 ` Andrew Morton
  2006-10-03  1:41   ` Badari Pulavarty
  2006-10-03 17:39   ` Badari Pulavarty
  0 siblings, 2 replies; 4+ messages in thread
From: Andrew Morton @ 2006-10-02 23:22 UTC (permalink / raw)
  To: Badari Pulavarty; +Cc: Eric W. Biederman, lkml, suka

On Mon, 02 Oct 2006 16:07:12 -0700
Badari Pulavarty <pbadari@us.ibm.com> wrote:

> Hi,
> 
> I am having problem bringing up networking on 2.6.18-mm2.
> I don't see any interrupts for eth0. I also see "cannot 
> handle IRQ" panic on shutdown - wondering if they are related..
> 
>            CPU0       CPU1       CPU2       CPU3
>   0:     112736     117883     117738     123737    IO-APIC-edge  timer
>   1:          0          0          1         10    IO-APIC-edge  i8042
>   4:          0          1          0        477    IO-APIC-edge  serial
>   6:          0          0          0          5    IO-APIC-edge  floppy
>   8:          0          0          0          0    IO-APIC-edge  rtc
>   9:          0          0          0          0   IO-APIC-level  acpi
>  12:          0         42          6         65    IO-APIC-edge  i8042
>  14:       4869       1911       3449       6079    IO-APIC-edge  ide0
>  15:          0      11051       4806        847    IO-APIC-edge  ide1
>  17:      55636          0          5          0   IO-APIC-level  eth0
> NMI:        216         40         38         41
> LOC:     471992     471992     472046     471481
> ERR:          0
> MIS:          0
> 
> 
> Everything works fine on 2.6.18.
> 
> (I saw similar report by Sukadev on 2.6.18-mm1).
> dmesg shows (similar messages about unable to allocate messages):
> 
> PCI: Cannot allocate resource region 0 of device 0000:08:01.1
> PCI: Cannot allocate resource region 0 of device 0000:08:02.1
> PCI: Cannot allocate resource region 0 of device 0000:08:03.1
> PCI: Cannot allocate resource region 0 of device 0000:08:04.1
> 

yes, this is probably the insert-ioapics-and-local-apic-into-resource-map
patch.  Does mainline crash too?  It should.  Or at least, it should have
the same resource allocation errors.

I've backed that out and applied an updated version.  My current rollup
(which actually seems to mostly compile now) is at

http://userweb.kernel.org/~akpm/badari.bz2

That's against 2.6.18.  Can you see if that fixes things?

> 
> INIT:do_IRQ: cannot handle IRQ -1
> ----------- [cut here ] --------- [please bite here ] ---------
> Kernel BUG at arch/x86_64/kernel/irq.c:118
> invalid opcode: 0000 [1] SMP
> last sysfs file: /devices/pci0000:00/0000:00:06.0/irq
> CPU 1
> Modules linked in: acpi_cpufreq ipv6 thermal processor fan button
> battery ac dm_mod floppy parport_pc lp parport
> Pid: 1, comm: init Not tainted 2.6.18-mm2 #1
> RIP: 0010:[<ffffffff8020ced0>]
> 

Once upon a time we'd have got a backtrace from that.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: 2.6.18-mm2 networking problem + IRQ panic
  2006-10-02 23:22 ` Andrew Morton
@ 2006-10-03  1:41   ` Badari Pulavarty
  2006-10-03 17:39   ` Badari Pulavarty
  1 sibling, 0 replies; 4+ messages in thread
From: Badari Pulavarty @ 2006-10-03  1:41 UTC (permalink / raw)
  To: Andrew Morton; +Cc: Eric W. Biederman, lkml, suka

Andrew Morton wrote:
> On Mon, 02 Oct 2006 16:07:12 -0700
> Badari Pulavarty <pbadari@us.ibm.com> wrote:
>
>   
>> Hi,
>>
>> I am having problem bringing up networking on 2.6.18-mm2.
>> I don't see any interrupts for eth0. I also see "cannot 
>> handle IRQ" panic on shutdown - wondering if they are related..
>>
>> ...
>>     
> yes, this is probably the insert-ioapics-and-local-apic-into-resource-map
> patch.  Does mainline crash too?  It should.  Or at least, it should have
> the same resource allocation errors.
>
>   
Yes. Backing out this solved the problem. (I got the patch from your -mm1
broken out directory and reverted that).

x86_64-mm-insert-ioapics-and-local-apic-into-resource-map

> I've backed that out and applied an updated version.  My current rollup
> (which actually seems to mostly compile now) is at
>
> http://userweb.kernel.org/~akpm/badari.bz2
>
> That's against 2.6.18.  Can you see if that fixes things?
>
>   
>> INIT:do_IRQ: cannot handle IRQ -1
>> ----------- [cut here ] --------- [please bite here ] ---------
>> Kernel BUG at arch/x86_64/kernel/irq.c:118
>> invalid opcode: 0000 [1] SMP
>> last sysfs file: /devices/pci0000:00/0000:00:06.0/irq
>> CPU 1
>> Modules linked in: acpi_cpufreq ipv6 thermal processor fan button
>> battery ac dm_mod floppy parport_pc lp parport
>> Pid: 1, comm: init Not tainted 2.6.18-mm2 #1
>> RIP: 0010:[<ffffffff8020ced0>]
>>
>>     
>
> Once upon a time we'd have got a backtrace from that.
>   
 :)

Thanks,
Badari



^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: 2.6.18-mm2 networking problem + IRQ panic
  2006-10-02 23:22 ` Andrew Morton
  2006-10-03  1:41   ` Badari Pulavarty
@ 2006-10-03 17:39   ` Badari Pulavarty
  1 sibling, 0 replies; 4+ messages in thread
From: Badari Pulavarty @ 2006-10-03 17:39 UTC (permalink / raw)
  To: Andrew Morton; +Cc: Eric W. Biederman, lkml, suka

On Mon, 2006-10-02 at 16:22 -0700, Andrew Morton wrote:
..
> yes, this is probably the insert-ioapics-and-local-apic-into-resource-map
> patch.  Does mainline crash too?  It should.  Or at least, it should have
> the same resource allocation errors.

Here is the update. I took -mm2 and backed out that patch. Networking
came up fine. But I still get panic on shutdown :( 

I tried -mm3 and got a panic on boot (so can't really test it).

do_IRQ: cannot handle IRQ -1
----------- [cut here ] --------- [please bite here ] ---------
Kernel BUG at arch/x86_64/kernel/irq.c:118
invalid opcode: 0000 [1] SMP
last sysfs file: /block/sdo/size
CPU 0
Modules linked in: sg sd_mod qla2xxx firmware_class scsi_transport_fc
scsi_mod acpi_cpufreq ipv6 thermal processor fan button battery ac
dm_mod floppy parport_pc lp parport
Pid: 30830, comm: init Not tainted 2.6.18-mm2 #3
RIP: 0010:[<ffffffff8020ced0>]  [<ffffffff8020ced0>] do_IRQ+0x60/0xb0
RSP: 0018:ffffffff80733e58  EFLAGS: 00010092
RAX: 0000000000000020 RBX: 00000000ffffffff RCX: ffffffff805f3768
RDX: ffffffff805f3768 RSI: 0000000000000082 RDI: ffffffff805f3760
RBP: ffffffff80733e68 R08: 0000000000000000 R09: ffff81018013fc20
R10: ffffffffffffffff R11: 0000000000000000 R12: ffffffff80733e58
R13: ffff8101c7b63b98 R14: 0000000000000000 R15: 0000000000000004
FS:  000000000058b850(0063) GS:ffffffff80676000(0000)
knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 0000000000463f00 CR3: 00000001ccdd4000 CR4: 00000000000006e0
Process init (pid: 30830, threadinfo ffff8101c7b62000, task
ffff8101d14b2780)
Stack:  ffff810175e2a800 0000000000000000 ffffffff80733e80
ffffffff8020a141
 ffffffff80733e80 ffffffff80733f48 0000000000000016 0000000008000000
 00000000000000a7 ffffffff8073d418 0000000000000000 00000000000009a7
Call Trace:
 [<ffffffff8020a141>] ret_from_intr+0x0/0xa
 [<ffffffff803e1c61>] serial8250_interrupt+0x1/0x100
 [<ffffffff80255e03>] handle_IRQ_event+0x33/0x70
 [<ffffffff8025777c>] handle_edge_irq+0x10c/0x160
 [<ffffffff8020cf00>] do_IRQ+0x90/0xb0
 [<ffffffff8020a141>] ret_from_intr+0x0/0xa
 [<ffffffff804da62c>] _spin_unlock_irqrestore+0xc/0x10
 [<ffffffff803e1b39>] serial8250_startup+0x539/0x5c0
 [<ffffffff803dc9fd>] uart_startup+0x8d/0x170
 [<ffffffff803dce21>] uart_open+0x221/0x520
 [<ffffffff803c4ece>] tty_open+0x1ce/0x3b0
 [<ffffffff80285762>] chrdev_open+0x182/0x1d0
 [<ffffffff802806c1>] __dentry_open+0xf1/0x210
 [<ffffffff8028088d>] nameidata_to_filp+0x2d/0x50
 [<ffffffff802808e9>] do_filp_open+0x39/0x50
 [<ffffffff8028095a>] do_sys_open+0x5a/0xf0
 [<ffffffff80280a1b>] sys_open+0x1b/0x20
 [<ffffffff80209c2e>] system_call+0x7e/0x83
 [<0000000000416e22>]


> 
> I've backed that out and applied an updated version.  My current rollup
> (which actually seems to mostly compile now) is at
> 
> http://userweb.kernel.org/~akpm/badari.bz2
> 
> That's against 2.6.18.  Can you see if that fixes things?

I am going to try it now..

Thanks,
Badari




^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2006-10-03 17:40 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-10-02 23:07 2.6.18-mm2 networking problem + IRQ panic Badari Pulavarty
2006-10-02 23:22 ` Andrew Morton
2006-10-03  1:41   ` Badari Pulavarty
2006-10-03 17:39   ` Badari Pulavarty

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox