Re: ncplogin panic
ejc <[EMAIL PROTECTED]> schrieb am 01.08.2006 20:28:46: > > I found your backtrace by digging a bit through the freebsd-fs list > and we appear to be reaching selrecord though different paths. Mine > is in sopoll() at ../../../kern/uipc_socket.c:2059 In which way different? Mine is in sopoll() at ../../../kern/uipc_socket.c:2059 too. > I don't know if it makes a difference, but I'm trying to use IP > instead of IPX to access our server. I also use IP only. Sorry if didn't mention that. Regards, Maik ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: GEOM_BDE: where is my partition?
On Tuesday 01 August 2006 17:57, Stefan Bethke wrote: > Maybe you got lucky, and only the first sector of the disk got lost > in that crash. If you know how you had partitioned that disk > *exactly*, or you have another disk of the same size that is > partitioned *exactly* the same, you might try to re-create the slices > usign fdisk, or copying over the first sector with dd. Otherwise, > you need to restore from backup. Not sure if it will help you, but there is a tool called gpart (sysutils/gpart) in the ports witch tries to recover your slices/partitions information so you can recreate them. -- Exceptions prove the rule, and wreck the budget. -- Miller pgpLfIcoSelYt.pgp Description: PGP signature
Re: ncplogin panic [backtrace with module symbols loaded]
Hi,
here is mine backtrace with module symbols loaded.
Thanks,
Maik
Kernel Source: /usr/obj/usr/src/sys/GENERIC
Getting KLD information and locations...
Traceback (most recent call last):
File "kld_deb.py", line 139, in ?
a = int(j[5], 16)
ValueError: invalid literal for int(): file
source /tmp/kgdb.asf.6179
[GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so:
Undefined symbol "ps_pglobal_lookup"]
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-marcel-freebsd".
Ready to go. Enter 'tr' to connect to the remote target
with /dev/cuad0, 'tr /dev/cuad1' to connect to a different port
or 'trf portno' to connect to the remote target with the firewire
interface. portno defaults to 5556.
Type 'getsyms' after connection to load kld symbols.
If you're debugging a local system, you can use 'kldsyms' instead
to load the kld symbols. That's a less obnoxious interface.
Unread portion of the kernel message buffer:
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x0
fault code = supervisor write, page not present
instruction pointer= 0x20:0xc068a3fc
stack pointer= 0x28:0xdcebc8dc
frame pointer= 0x28:0xdcebc8e4
code segment = base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 772 (ncplogin)
trap number= 12
panic: page fault
Uptime: 16m46s
Dumping 494 MB (2 chunks)
chunk 0: 1MB (159 pages) ... ok
chunk 1: 495MB (126511 pages) 479 463 447 431 415 399 383 367 351 335 319 303
287 271 255 239 223 207 191 175 159 143 127 111 95
79 63 47 31 15
#0 doadump () at pcpu.h:165
165 __asm __volatile("movl %%fs:0,%0" : "=r" (td));
(kgdb) getsm yms
During symbol reading, Incomplete CFI data; unspecified registers at 0xc0666959.
Id Refs AddressSize Name
1 18 0xc040 6e15d0 kernel
21 0xc0ae2000 5f60 snd_ich.ko
32 0xc0ae8000 22b88sound.ko
42 0xc0b0b000 fd68 drm.ko
51 0xc0b1b000 615c i915.ko
61 0xc0b22000 5984cacpi.ko
71 0xc3574000 16000linux.ko
81 0xc369b000 4000 logo_saver.ko
91 0xc3816000 8000 ncp.ko
101 0xc381e000 3000 libmchain.ko
Select the list above with the mouse, paste into the screen
and then press ^D. Yes, this is annoying.
1 18 0xc040 6e15d0 kernel
21 0xc0ae2000 5f60 snd_ich.ko
32 0xc0ae8000 22b88sound.ko
42 0xc0b0b000 fd68 drm.ko
51 0xc0b1b000 615c i915.ko
61 0xc0b22000 5984cacpi.ko
71 0xc3574000 16000linux.ko
81 0xc369b000 4000 logo_saver.ko
91 0xc3816000 8000 ncp.ko
101 0xc381e000 3000 libmchain.ko
^Dadd symbol table from file
"/usr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/acpi/acpi/acpi.ko.debug"
at
.text_addr = 0xc0b32de0
.data_addr = 0xc0b661a0
.bss_addr = 0xc0b684e0
add symbol table from file
"/usr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/drm/drm/drm.ko.debug"
at
.text_addr = 0xc0b0e68c
.data_addr = 0xc0b18100
.bss_addr = 0xc0b18b24
add symbol table from file
"/usr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/drm/i915/i915.ko.debug"
at
.text_addr = 0xc0b1c1b4
.data_addr = 0xc0b1fd80
.bss_addr = 0xc0b1fff4
add symbol table from file
"/usr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/libmchain/libmchain.ko.debug"
at
.text_addr = 0xc381e60c
.data_addr = 0xc38200b8
.bss_addr = 0xc3820150
add symbol table from file
"/usr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/linux/linux.ko.debug"
at
.text_addr = 0xc357ab44
.data_addr = 0xc3588000
.bss_addr = 0xc35896c0
add symbol table from file
"/usr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/ncp/ncp.ko.debug" at
.text_addr = 0xc3817e40
.data_addr = 0xc381d280
.bss_addr = 0xc381db80
add symbol table from file
"/usr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/sound/sound/sound.ko.debug"
at
.text_addr = 0xc0af0c30
.data_addr = 0xc0aff4c0
.bss_addr = 0xc0b02d80
add symbol table from file
"/usr/obj/usr/src/sys/GENERIC/modules/usr/src/sys/modules/sound/driver/ich/snd_ich.ko.debug"
at
.text_addr = 0xc0ae3b08
.data_addr = 0xc0ae6960
Re: Safe card to replace for ICP Vortex GDT8514RZ ...
Freddie Cash wrote: We've been bitten bad by these cards. LSI MegaRAID 150-6 SATA RAID controllers (PCI-X format). The management tools are crap, the throughput is crap, the onboard SATA chipset is a Silicon Image. The design is three years old and is showing its age. Their performance is not on par with modern cards like 3ware 9550, the price is however considerably lower. The newer MegaRAID 300-8x (and coming -4e, -8e) are modern designs with faster processors and acceptable performance. And they will not run reliably when plugged into a riser card. Wasn't that problem caused by a Tyan motherboard with a substandard riser? I have used lots of 150-4/6 with Supermicro boards and risers without any problems. We lost data on several servers before narrowing down the cause to these cards. We lost several weeks of time diagnosing these things. And we lost several hundred dollars when the vendor wouldn't take them all back (we got them to trade most of them for 3Ware 9550SX cards). Buy things from vendors who know what they sell :-) It will be more expensive but in the long run you will save both money and especially time. In our experience, these cards are crap, and their tech support isn't much better. LSI's tech support is top notch and very helpful. Tyan is the real stinker in the business. Uneducated, without any lab resources and hard to get hold of. (excluding the Taiwanese server wanna-be manufacturers who's support is virtually non-existent) /Martin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ncplogin panic
On 8/1/06, John Baldwin <[EMAIL PROTECTED]> wrote:
On Tuesday 01 August 2006 14:28, ejc wrote:
> On 8/1/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> >
> > Hi,
> >
> > i had the same problem. See my thread on the freebsd-fs mailinglist
> >
> > http://lists.freebsd.org/pipermail/freebsd-fs/2006-July/002060.html
> >
> >
> > After some research i use the attached patch against ncp_sock.c.
> >
> > So it is not the real solution to this problem it only avoids the panics.
I'm using it quiet a while without any other known
> > problems.
> > Hopefully someone with more knowledge can help on this.
> >
> > I also get some "md_get_mem(461): incomplete copy" messages which seem to
do no harm, so far.
> >
> > Regards,
> >
> > Maik
> >
> >
> > !!! Use atyour own risk !!!
> >
> > --- ncp_sock.c.origFri Jan 7 02:45:49 2005
> > +++ ncp_sock.c Thu Jul 20 14:12:45 2006
> > @@ -189,7 +189,12 @@
> > struct thread *td = curthread;
> > struct ucred *cred = NULL;
> >
> > -return so->so_proto->pr_usrreqs->pru_sopoll(so, events, cred, td);
> > +if ( td->td_selq.tqh_last == NULL ) {
> > +printf("ncp_poll: td->td_selq.tqh_last == NULL\n");
> > +return 0;
> > +}
> > +
> > + return so->so_proto->pr_usrreqs->pru_sopoll(so, events, cred, td);
> > }
> >
> > int
> >
> > pach ends here ---
>
> After setting my bios to only use one CPU I was able to get a core
> dump and the panic is happening at the exact same place as yours:
> in selrecord (../../../kern/sys_generic.c:1105)
> 1100 * it alone as we've already added pointed it at us
> and added it to
> 1101 * our list.
> 1102 */
> 1103if (sip->si_thread == NULL) {
> 1104sip->si_thread = selector;
> 1105TAILQ_INSERT_TAIL(&selector->td_selq, sip,
si_thrlist);
> 1106} else if (sip->si_thread != selector) {
> 1107sip->si_flags |= SI_COLL;
> 1108}
> 1109
>
> I found your backtrace by digging a bit through the freebsd-fs list
> and we appear to be reaching selrecord though different paths. Mine
> is in sopoll() at ../../../kern/uipc_socket.c:2059
>
> I don't know if it makes a difference, but I'm trying to use IP
> instead of IPX to access our server.
> My dump backtrace is attached.
It would be very helpful if you could get the symbols loaded for the modules
in you backtrace. You can either compile everything into a static kernel or
you can use the 'asf' tool to generate appropriate gdb script commands to
source to get symbols for your modules. You can find a kldstat gdb command
in src/tools/debugscripts/ that would be helpful to use with asf.
--
John Baldwin
Backtrace with module symbols loaded. It looks almost exactly the
same as Maik's .
Thanks
Eric
dump.out
Description: Binary data
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: GEOM_BDE: where is my partition?
Hi Iulian, ok, I'll try gpart here and tell you about the results. Thank you, Felipe Neuwald. Iulian M escreveu: On Tuesday 01 August 2006 17:57, Stefan Bethke wrote: Maybe you got lucky, and only the first sector of the disk got lost in that crash. If you know how you had partitioned that disk *exactly*, or you have another disk of the same size that is partitioned *exactly* the same, you might try to re-create the slices usign fdisk, or copying over the first sector with dd. Otherwise, you need to restore from backup. Not sure if it will help you, but there is a tool called gpart (sysutils/gpart) in the ports witch tries to recover your slices/partitions information so you can recreate them. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ncplogin panic
On 8/2/06, ejc <[EMAIL PROTECTED]> wrote: Backtrace with module symbols loaded. It looks almost exactly the same as Maik's . I messed up that last one and loaded the local module symbols with 'kldsyms'. Here's one with 'getsyms'. Thanks Eric dump.out Description: Binary data ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
re interface broken
Hi folks, I've got a notebook (HP/Compaq nx7010) with which I'm tracking 6-stable. Some days (maybe two weeks?) ago my internal network interface (re driver) became inoperational. The hardware shows a link, but nothing goes over the wire. I cannot ping, cannot get a dhcp address, nothing. Meanwhile I did various updates using the old kernel (earlier 6.1-stable), and I saw several changes affecting if*, re* and so on. However, even after the latest cvsup today, the interface still doesn't work. Is there work going on to fix this, can I provide further information to track this problem down? cu Gerrit ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ncplogin panic
On Wednesday 02 August 2006 09:33, ejc wrote: > On 8/2/06, ejc <[EMAIL PROTECTED]> wrote: > > Backtrace with module symbols loaded. It looks almost exactly the > > same as Maik's . > > I messed up that last one and loaded the local module symbols with > 'kldsyms'. Here's one with 'getsyms'. Can you jump to the 'selrecord' frame and do 'p selector->td_selq' and 'p *sip'? -- John Baldwin -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ncplogin panic
> Can you jump to the 'selrecord' frame and do 'p selector->td_selq' and
> 'p *sip'?
Here is what i get.
(kgdb) up 7
#7 0xc068a3fc in selrecord (selector=0xc33f9a80, sip=0xc363a8a8) at
/usr/src/sys/kern/sys_generic.c:1105
1105 TAILQ_INSERT_TAIL(&selector->td_selq, sip,
si_thrlist);
(kgdb) p selector->td_selq
$1 = {
tqh_first = 0x0,
tqh_last = 0x0
}
(kgdb) p *sip
$2 = {
si_thrlist = {
tqe_next = 0x0,
tqe_prev = 0x0
},
si_thread = 0xc33f9a80,
si_note = {
kl_list = {
slh_first = 0x0
},
kl_lock = 0xc064bf08 ,
kl_unlock = 0xc064bf3c ,
kl_locked = 0xc064bf78 ,
kl_lockarg = 0xc363a8cc
},
si_flags = 0x0
}
(kgdb)
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ncplogin panic
On 8/2/06, John Baldwin <[EMAIL PROTECTED]> wrote:
On Wednesday 02 August 2006 09:33, ejc wrote:
> On 8/2/06, ejc <[EMAIL PROTECTED]> wrote:
> > Backtrace with module symbols loaded. It looks almost exactly the
> > same as Maik's .
>
> I messed up that last one and loaded the local module symbols with
> 'kldsyms'. Here's one with 'getsyms'.
Can you jump to the 'selrecord' frame and do 'p selector->td_selq' and
'p *sip'?
(kgdb) frame 7
#7 0xc0507520 in selrecord (selector=0xc174d000, sip=0xc17755e0) at
../../../kern/sys_generic.c:1105
1105TAILQ_INSERT_TAIL(&selector->td_selq, sip, si_thrlist);
(kgdb) p selector->td_selq
$1 = {
tqh_first = 0x0,
tqh_last = 0x0
}
(kgdb) p *sip
$2 = {
si_thrlist = {
tqe_next = 0x0,
tqe_prev = 0x0
},
si_thread = 0xc174d000,
si_note = {
kl_list = {
slh_first = 0x0
},
kl_lock = 0xc04c6b1c ,
kl_unlock = 0xc04c6b54 ,
kl_locked = 0xc04c6b90 ,
kl_lockarg = 0xc1775604
},
si_flags = 0x0
}
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ncplogin panic
On Wednesday 02 August 2006 11:43, ejc wrote: > On 8/2/06, John Baldwin <[EMAIL PROTECTED]> wrote: > > On Wednesday 02 August 2006 09:33, ejc wrote: > > > On 8/2/06, ejc <[EMAIL PROTECTED]> wrote: > > > > Backtrace with module symbols loaded. It looks almost exactly the > > > > same as Maik's . > > > > > > I messed up that last one and loaded the local module symbols with > > > 'kldsyms'. Here's one with 'getsyms'. > > > > Can you jump to the 'selrecord' frame and do 'p selector->td_selq' and > > 'p *sip'? Ok, can you try http://www.FreeBSD.org/~jhb/patches/ncp_poll.patch -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ncplogin panic
On 8/2/06, John Baldwin <[EMAIL PROTECTED]> wrote: On Wednesday 02 August 2006 11:43, ejc wrote: > On 8/2/06, John Baldwin <[EMAIL PROTECTED]> wrote: > > On Wednesday 02 August 2006 09:33, ejc wrote: > > > On 8/2/06, ejc <[EMAIL PROTECTED]> wrote: > > > > Backtrace with module symbols loaded. It looks almost exactly the > > > > same as Maik's . > > > > > > I messed up that last one and loaded the local module symbols with > > > 'kldsyms'. Here's one with 'getsyms'. > > > > Can you jump to the 'selrecord' frame and do 'p selector->td_selq' and > > 'p *sip'? Ok, can you try http://www.FreeBSD.org/~jhb/patches/ncp_poll.patch I had to massage the patch a bit to get it to apply to v1.15 of ncp_sock.c (I'm running 6.1-STABLE) but I don't get the panics anymore. Thanks Eric ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: re interface broken
On Wed, Aug 02, 2006 at 04:16:34PM +0200, Gerrit K?hn wrote: > Hi folks, > > I've got a notebook (HP/Compaq nx7010) with which I'm tracking 6-stable. > Some days (maybe two weeks?) ago my internal network interface (re driver) > became inoperational. The hardware shows a link, but nothing goes over the > wire. I cannot ping, cannot get a dhcp address, nothing. > Meanwhile I did various updates using the old kernel (earlier 6.1-stable), > and I saw several changes affecting if*, re* and so on. However, even > after the latest cvsup today, the interface still doesn't work. Is there > work going on to fix this, can I provide further information to track this > problem down? > I think you should show 'dmesg' and 'pciconf -lv' output first. -- Regards, Pyun YongHyeon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
fdisk problem on 3ware based system (6.1-RELEASE-p3)
I see to have an fdisk issue on one of our boxes with a 3ware card. Relevant lines from dmesg: twe0: <3ware Storage Controller. Driver version 1.50.01.002> port 0x9c00-0x9c0f mem 0xfc00-0xfc7f irq 20 at device 1.0 on pci2 twe0: 2 ports, Firmware FE8S 1.05.00.068, BIOS BE7X 1.08.00.048 twed0: on twe0 twed0: 76318MB (156299440 sectors) This started out because I am unable to create a new partition on a machine running 6.1-RELEASE-p3 and am beginning to suspect something is wrong in fdisk. If I run sysinstall and go to the partition editor, I get the following, which seems correct: Disk name: twed0 FDISK Partition Editor DISK Geometry: 9729 cyls/255 heads/63 sectors = 156296385 sectors (76316MB) Offset Size(ST)End Name PType Desc SubtypeFlags 0 63 62- 12 unused0 63 31455207 31455269 twed0s1 8freebsd 165 31455270 58717575 90172844 twed0s2 8freebsd 165 90172845 66126595 156299439- 12 unused0 But, I am unable to create a third partition. Every time I do that, I get: ERROR: Unable to write data to disk twed0! This machine is not running with an elevated security level: kern.securelevel: -1 So, I decided to go in with fdisk and see what was up. It looks like fdisk is very confused on partition 2, which is likely why I can not create a partition 3 (even using fdisk): > fdisk /dev/twed0 *** Working on device /dev/twed0 *** parameters extracted from in-core disklabel are: cylinders=9729 heads=255 sectors/track=63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=9729 heads=255 sectors/track=63 (16065 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 31455207 (15358 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 254/ sector 63 The data for partition 2 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 31455270, size 58717575 (28670 Meg), flag 0 beg: cyl 1023/ head 255/ sector 63; end: cyl 1023/ head 254/ sector 63 < !! The data for partition 3 is: The data for partition 4 is: At this point, I'm suspecting that fdisk is computing something incorrectly and am not sure how to proceed as I'd prefer not to corrupt my disk label. Before I consider filing a PR, is this a known problem? /\/\ \/\/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
