| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <CAJXQGfJwMGF=N+35YToQDJfNDLsHZJmofxF1EQV_V5YMBwVHjA@mail.gmail.com>
Date: Wed, 8 Feb 2012 13:44:09 +0530
From: Naresh Bhat <nareshgbhat@...il.com>
To: Yong Zhang <yong.zhang0@...il.com>
Cc: linux-kernel@...r.kernel.org
Subject: Re: x86_64 arch+SMP ON+linux-2.6.32.46+E1000+KGDBOE = Timed out.
Ignoring packet error, continuing...
Hi Yong,
Thank you very much for the suggestion.
Yes, I am able to use other KGDB methods like KGDB over serial,
console..But I want to make it work KGDBOE. Hence I am requesting is
there anybody tried and come across the "Ignoring packet error,
continuing..." error ?
Thanks
-Naresh Bhat
On 2/8/12, Yong Zhang <yong.zhang0@...il.com> wrote:
> On Wed, Feb 08, 2012 at 12:46:04PM +0530, Naresh Bhat wrote:
>> Hi Yong,
>>
>> Yes, I know they have removed the KGDBOE support. I have forward
>> ported the patch to linux-2.6.32.46 kernel. I was just trying to
>> understand this issue belongs to which of the category ?
>
> Maybe you can try with other KGDB method to debug your system, like
> KGDB_SERIAL_CONSOLE.
> Thus you can narrow down your problem.
>
> Thanks,
> Yong
>
>>
>> 1. Is there any issue with Ethernet driver E1000 issue ?
>> 2. Is it belongs to KGDB ?
>> 3. Is there any kernel SMP hang issue for x86 64bit architecture which
>> is fixed in upstream kernel ?
>> 4. None of the above and something else is broken ?
>>
>> Is there any available patch ? any guidance to fix the error in E1000
>> driver. I will really appreciate your help.
>>
>> Thanks and Regards
>> -Naresh Bhat
>>
>> On 2/8/12, Yong Zhang <yong.zhang0@...il.com> wrote:
>> > On Tue, Feb 07, 2012 at 09:38:49PM +0530, Naresh Bhat wrote:
>> >> Hi,
>> >>
>> >> I am trying KGDBOE on the following kernel
>> >
>> > Is KGDBOE supported by upstream? Actually I don't find it
>> > in the source tree.
>> >
>> > Thanks,
>> > Yong
>> >
>> >>
>> >> Kernel - linux-2.6.32.46 (With SMP set)
>> >> Hardware - x86 64bit machine (Intel Nehlaum)
>> >> Ethernet - E1000 driver is used
>> >>
>> >> But I am getting the following error
>> >>
>> >> ........
>> >> ............
>> >> .................
>> >> Breakpoint 2, sys_sync () at fs/sync.c:130
>> >> 130 wakeup_flusher_threads(0);
>> >> (gdb) s
>> >> wakeup_flusher_threads (nr_pages=0) at fs/fs-writeback.c:1005
>> >> 1005 {
>> >> (gdb) s
>> >>
>> >> Ignoring packet error, continuing...
>> >> Ignoring packet error, continuing...
>> >> Ignoring packet error, continuing...
>> >>
>> >>
>> >> Detailed logs with debug set :
>> >> -----------------------------------------
>> >>
>> >> ...................
>> >> ................................
>> >> .......................................
>> >> Sending packet: $z0,ffffffff810ad687,1#66...Ack
>> >> Packet received: OK
>> >> target_remove_breakpoint (0x810ad687, xxx) = 0
>> >> target_terminal_ours ()
>> >> kgdb_register_io_module (new_kgdb_io_ops=0xffffffff81a9d5b0) at
>> >> kernel/kgdb.c:1778
>> >> 1778 }
>> >> (gdb) n
>> >> Sending packet: $Z0,ffffffff810ad687,1#46...Ack
>> >> Packet received: OK
>> >> target_insert_breakpoint (0x810ad687, xxx) = 0
>> >> target_terminal_inferior ()
>> >> Sending packet: $s#73...Ack
>> >> target_resume (-1, step, 0)
>> >> Packet received: T05thread:0000000000000001;
>> >> target_wait (-1, status) = 42000, status->kind = stopped, signal =
>> >> SIGTRAP
>> >> target_thread_architecture (Thread 1) = 0xa2e45c0 [i386:x86-64]
>> >> Sending packet: $g#67...Ack
>> >> Packet received:
>> >> 0000000000000000b0d5a981ffffffffffffffff00000000ffffffff0000000086020000000000004602000000000000b07e0b2f0088ffffa87e0b2f0088ffff000000000000000058f8b081ffffffff507d0b2f0088ffff18b20681ffffffff000000000000000008000000000000000800000000000000b0610300000000005cda0a81ffffffff820300001000000018000000
>> >> target_fetch_registers (rip) = 5cda0a81ffffffff 0xffffffff810ada5c
>> >> -2129995172
>> >> target_stopped_by_watchpoint () = 0
>> >> target_terminal_inferior ()
>> >> Sending packet: $s#73...Ack
>> >> target_resume (-1, step, 0)
>> >> Packet received: T05thread:0000000000000001;
>> >> target_wait (-1, status) = 42000, status->kind = stopped, signal =
>> >> SIGTRAP
>> >> target_thread_architecture (Thread 1) = 0xa2e45c0 [i386:x86-64]
>> >> Sending packet: $g#67...Ack
>> >> Packet received:
>> >> 00000000000000000000000000000000ffffffff00000000ffffffff0000000086020000000000004602000000000000b07e0b2f0088ffffb07e0b2f0088ffff000000000000000058f8b081ffffffff507d0b2f0088ffff18b20681ffffffff000000000000000008000000000000000800000000000000b0610300000000005dda0a81ffffffff820300001000000018000000
>> >> target_fetch_registers (rip) = 5dda0a81ffffffff 0xffffffff810ada5d
>> >> -2129995171
>> >> target_stopped_by_watchpoint () = 0
>> >> target_terminal_inferior ()
>> >> Sending packet: $s#73...Ack
>> >> target_resume (-1, step, 0)
>> >> Packet received: T05thread:0000000000000001;
>> >> target_wait (-1, status) = 42000, status->kind = stopped, signal =
>> >> SIGTRAP
>> >> target_thread_architecture (Thread 1) = 0xa2e45c0 [i386:x86-64]
>> >> Sending packet: $g#67...Ack
>> >> Packet received:
>> >> 00000000000000000000000000000000ffffffff00000000ffffffff0000000086020000000000004602000000000000c07e0b2f0088ffffb87e0b2f0088ffff000000000000000058f8b081ffffffff507d0b2f0088ffff18b20681ffffffff000000000000000008000000000000000800000000000000b0610300000000005eda0a81ffffffff820300001000000018000000
>> >> target_fetch_registers (rip) = 5eda0a81ffffffff 0xffffffff810ada5e
>> >> -2129995170
>> >> target_stopped_by_watchpoint () = 0
>> >> target_terminal_inferior ()
>> >> Sending packet: $s#73...Ack
>> >> target_resume (-1, step, 0)
>> >> Packet received: T05thread:0000000000000001;
>> >> target_wait (-1, status) = 42000, status->kind = stopped, signal =
>> >> SIGTRAP
>> >> target_thread_architecture (Thread 1) = 0xa2e45c0 [i386:x86-64]
>> >> Sending packet: $g#67...Ack
>> >> Packet received:
>> >> 00000000000000000000000000000000ffffffff00000000ffffffff0000000086020000000000004602000000000000c07e0b2f0088ffffc07e0b2f0088ffff000000000000000058f8b081ffffffff507d0b2f0088ffff18b20681ffffffff000000000000000008000000000000000800000000000000b061030000000000180d3e81ffffffff820300001000000018000000
>> >> target_fetch_registers (rip) = 180d3e81ffffffff 0xffffffff813e0d18
>> >> -2126639848
>> >> target_stopped_by_watchpoint () = 0
>> >> target_terminal_ours_for_output ()
>> >> Sending packet: $mffffffff813e0d18,1#f8...Ack
>> >> Packet received: 85
>> >> remote:target_xfer_partial (2, (null), 0xbfe00edb, 0x0,
>> >> 0xffffffff813e0d18, 1) = 1, bytes = 85
>> >> Sending packet: $mffffffff813e0d18,1#f8...Ack
>> >> Packet received: 85
>> >> remote:target_xfer_partial (2, (null), 0xbfe00edb, 0x0,
>> >> 0xffffffff813e0d18, 1) = 1, bytes = 85
>> >> Sending packet: $mffff88002f0b7ec0,40#be...Ack
>> >> Packet received:
>> >> e07e0b2f0088ffff510d3e81ffffffff0800000000000000380d3e81ffffffff107f0b2f0088ffff5fa00081ffffffff107f0b2f0088ffffb0bcb881ffffffff
>> >> remote:target_xfer_partial (3, (null), 0xa944050, 0x0,
>> >> 0xffff88002f0b7ec0, 64) = 64, bytes =
>> >> e0 7e 0b 2f 00 88 ff ff 51 0d 3e 81 ff ff ff ff ...
>> >> remote:target_xfer_partial (4, (null), 0xa944030, 0x0,
>> >> 0xffff88002f0b7ec8, 8) = 8, bytes =
>> >> 51 0d 3e 81 ff ff ff ff
>> >> remote:target_xfer_partial (4, (null), 0xa944030, 0x0,
>> >> 0xffff88002f0b7ec0, 8) = 8, bytes =
>> >> e0 7e 0b 2f 00 88 ff ff
>> >> target_terminal_inferior ()
>> >> Sending packet: $s#73...Ack
>> >> target_resume (-1, step, 0)
>> >> Packet received: T05thread:0000000000000001;
>> >> target_wait (-1, status) = 42000, status->kind = stopped, signal =
>> >> SIGTRAP
>> >> target_thread_architecture (Thread 1) = 0xa2e45c0 [i386:x86-64]
>> >> Sending packet: $g#67...Ack
>> >> Packet received:
>> >> 00000000000000000000000000000000ffffffff00000000ffffffff0000000086020000000000004602000000000000c07e0b2f0088ffffc07e0b2f0088ffff000000000000000058f8b081ffffffff507d0b2f0088ffff18b20681ffffffff000000000000000008000000000000000800000000000000b0610300000000001a0d3e81ffffffff460300001000000018000000
>> >> target_fetch_registers (rip) = 1a0d3e81ffffffff 0xffffffff813e0d1a
>> >> -2126639846
>> >> target_stopped_by_watchpoint () = 0
>> >> target_terminal_inferior ()
>> >> Sending packet: $s#73...Ack
>> >> target_resume (-1, step, 0)
>> >> Packet received: T05thread:0000000000000001;
>> >> target_wait (-1, status) = 42000, status->kind = stopped, signal =
>> >> SIGTRAP
>> >> target_thread_architecture (Thread 1) = 0xa2e45c0 [i386:x86-64]
>> >> Sending packet: $g#67...Sending packet: $g#67...Sending packet:
>> >> $g#67...Sending packet: $g#67...Timed out.
>> >> Timed out.
>> >> Timed out.
>> >> Ignoring packet error, continuing...
>> >> Bad register packet; fetching a new packet
>> >> Timed out.
>> >> Timed out.
>> >> Timed out.
>> >> Ignoring packet error, continuing...
>> >> Bad register packet; fetching a new packet
>> >> Timed out.
>> >> Timed out.
>> >> Timed out.
>> >> Ignoring packet error, continuing...
>> >> Bad register packet; fetching a new packet
>> >> Timed out.
>> >> ..........................
>> >> .................................
>> >>
>> >>
>> >> Please help me to identify any available patch in kernel.org or any
>> >> guidance to fix the above error. I will really appreciate your help
>> >> on this.
>> >>
>> >>
>> >> -- Thanks and Regards
>> >> "For things to change, we must change"
>> >> -Naresh Bhat
>> >> --
>> >> To unsubscribe from this list: send the line "unsubscribe linux-kernel"
>> >> in
>> >> the body of a message to majordomo@...r.kernel.org
>> >> More majordomo info at http://vger.kernel.org/majordomo-info.html
>> >> Please read the FAQ at http://www.tux.org/lkml/
>> >
>> > --
>> > Only stand for myself
>> >
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>> the body of a message to majordomo@...r.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at http://www.tux.org/lkml/
>
> --
> Only stand for myself
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists