Re: HP 380 G4 - ciss kernel page fault.
On Tue, 27 Apr 2010, John Baldwin wrote: > On Tuesday 27 April 2010 9:30:12 am kama wrote: > > > > Hi. > > > > I have problem when probing the ciss device. Causing a kernel panic. This > > happened when I upgraded from 6.3 to 7.3-stable. Booting the old kernel > > works. So something has changed. I am also getting the error on both the > > 7.3 and the 8.0 install cd's. > > > > The ciss that causing the problem is a Smart Array 6404 and its the addon > > card that it faults at. The server disconnect it due to an error. But > > since it works on 6.3 it is something that have changed. FreeBSD should > > not panic, it should just disable it. > > > > Also I tried to disable the card in the BIOS, but FreeBSD try to probe it > > anyway and panic. > > > > This whats comes up on a verbose boot through the ILO remote console. > > (typed in manually from a screenshot) > > > > ciss2: port 0x6400-0x64ff mem > > 0xfdf7-0xfdf71fff irq 98 at device 5.0 on pcill > > ciss2: Reserved 0x2000 bytes for rid 0x10 type 3 at 0xfdf7 > > pci11: child ciss2 requested type 3 for rid 0, but the BAR says it is an > > ioport > > ciss2: can't allocate config window > > kernel trap 12 with interupts disabled > > Can you get the ciss2 boot messages from a working 6.x kernel? This is the verbose boot on 6.3. FreeBSD 6.3-STABLE #3: Thu Mar 6 14:29:33 CET 2008 ciss1: 10 physical devices ciss1: 4 logical drives ciss1: logical drive (b0t0): RAID 1, 69120MB online ciss1: logical drive (b0t1): RAID 1, 69120MB online ciss1: logical drive (b0t2): RAID 1, 139776MB online ciss1: logical drive (b0t3): RAID 1, 139776MB online ciss2: port 0x6400-0x64ff mem 0xfdf7-0xfdf71fff,0xfdf0-0xfdf3 irq 98 at device 5.0 on pci11 ciss2: Reserved 0x2000 bytes for rid 0x10 type 3 at 0xfdf7 pci11: child ciss2 requested type 3 for rid 0, but the BAR says it is an ioport ciss2: can't allocate config window device_attach: ciss2 attach returned 6 uhci0: port 0x2000-0x201f irq 16 at device 29.0 on pci0 /Bjorn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
resizing xterminal while in vi-session forces vi to coredump
Hello, vi coredumps if one is resizing the xterm within the vi session runs. OS is FreeBSD 8.0-STABLE/amd64 r207308: Wed Apr 28 09:10:03 CEST 2010, ports are most recent, X11 has been recompiled in favor of WITHOUT_NOUVEAU=YES Kernel also utilises options TEKEN_UTF8 options TEKEN_XTERM but I think this is for console only. Should I file a PR? Thanks for your patience, O. Hartmann ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: puc(4) timedia baudrate problem
On Tue, 27 Apr 2010 21:46:08 -0700 Marcel Moolenaar wrote: > On Apr 27, 2010, at 12:47 PM, Paul Schenkeveld wrote: > >puc0: port > > 0xe500-0xe51f,0xe520-0xe52f,0xe530-0xe537,0xe538-0xe53f,0xe540-0xe547,0xe548-0xe54f > > irq 10 at device 14.0 on pci0 > *snip* > > The first two ports work correctly but the baudrate of the other six > > is incorrect, i.e. I have to use 'tip -76800 uart5' to get the port > > to communicate at 9600 baud. I 'know' that this particular hardware > > has a baudrate multiplier on the first two ports but not on the other > > six. > *snip* > Can you show me the output of ``pciconf -lbv'' for this device so that > I can create a patch for you to test? > Also: do you happen to know if all 8-port Timedia cards have a non- > uniform RCLK or only a select set (maybe only yours)? Seems the same issue as: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/129663 -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD 7.3, reboot after panic: double fault
I also tryed to use GIF interface istead of GRE - same result and same backtrace in kgdb - kernel panic. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: HP 380 G4 - ciss kernel page fault.
On Wednesday 28 April 2010 3:22:44 am kama wrote: > > On Tue, 27 Apr 2010, John Baldwin wrote: > > > On Tuesday 27 April 2010 9:30:12 am kama wrote: > > > > > > Hi. > > > > > > I have problem when probing the ciss device. Causing a kernel panic. This > > > happened when I upgraded from 6.3 to 7.3-stable. Booting the old kernel > > > works. So something has changed. I am also getting the error on both the > > > 7.3 and the 8.0 install cd's. > > > > > > The ciss that causing the problem is a Smart Array 6404 and its the addon > > > card that it faults at. The server disconnect it due to an error. But > > > since it works on 6.3 it is something that have changed. FreeBSD should > > > not panic, it should just disable it. > > > > > > Also I tried to disable the card in the BIOS, but FreeBSD try to probe it > > > anyway and panic. > > > > > > This whats comes up on a verbose boot through the ILO remote console. > > > (typed in manually from a screenshot) > > > > > > ciss2: port 0x6400-0x64ff mem > > > 0xfdf7-0xfdf71fff irq 98 at device 5.0 on pcill > > > ciss2: Reserved 0x2000 bytes for rid 0x10 type 3 at 0xfdf7 > > > pci11: child ciss2 requested type 3 for rid 0, but the BAR says it is an > > > ioport > > > ciss2: can't allocate config window > > > kernel trap 12 with interupts disabled > > > > Can you get the ciss2 boot messages from a working 6.x kernel? > > This is the verbose boot on 6.3. > > FreeBSD 6.3-STABLE #3: Thu Mar 6 14:29:33 CET 2008 > > ciss1: 10 physical devices > ciss1: 4 logical drives > ciss1: logical drive (b0t0): RAID 1, 69120MB online > ciss1: logical drive (b0t1): RAID 1, 69120MB online > ciss1: logical drive (b0t2): RAID 1, 139776MB online > ciss1: logical drive (b0t3): RAID 1, 139776MB online > > ciss2: port 0x6400-0x64ff mem > 0xfdf7-0xfdf71fff,0xfdf0-0xfdf3 irq 98 at device 5.0 on pci11 > ciss2: Reserved 0x2000 bytes for rid 0x10 type 3 at 0xfdf7 > pci11: child ciss2 requested type 3 for rid 0, but the BAR says it is an > ioport > ciss2: can't allocate config window > device_attach: ciss2 attach returned 6 Oh, so it didn't work in 6.x either, it just handles failure less gracefully in 7.0+? -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: HP 380 G4 - ciss kernel page fault.
On Wed, 28 Apr 2010, John Baldwin wrote: > On Wednesday 28 April 2010 3:22:44 am kama wrote: > > > > On Tue, 27 Apr 2010, John Baldwin wrote: > > > > > On Tuesday 27 April 2010 9:30:12 am kama wrote: > > > > > > > > Hi. > > > > > > > > I have problem when probing the ciss device. Causing a kernel panic. > This > > > > happened when I upgraded from 6.3 to 7.3-stable. Booting the old kernel > > > > works. So something has changed. I am also getting the error on both the > > > > 7.3 and the 8.0 install cd's. > > > > > > > > The ciss that causing the problem is a Smart Array 6404 and its the > addon > > > > card that it faults at. The server disconnect it due to an error. But > > > > since it works on 6.3 it is something that have changed. FreeBSD should > > > > not panic, it should just disable it. > > > > > > > > Also I tried to disable the card in the BIOS, but FreeBSD try to probe > it > > > > anyway and panic. > > > > > > > > This whats comes up on a verbose boot through the ILO remote console. > > > > (typed in manually from a screenshot) > > > > > > > > ciss2: port 0x6400-0x64ff mem > > > > 0xfdf7-0xfdf71fff irq 98 at device 5.0 on pcill > > > > ciss2: Reserved 0x2000 bytes for rid 0x10 type 3 at 0xfdf7 > > > > pci11: child ciss2 requested type 3 for rid 0, but the BAR says it is an > > > > ioport > > > > ciss2: can't allocate config window > > > > kernel trap 12 with interupts disabled > > > > > > Can you get the ciss2 boot messages from a working 6.x kernel? > > > > This is the verbose boot on 6.3. > > > > FreeBSD 6.3-STABLE #3: Thu Mar 6 14:29:33 CET 2008 > > > > ciss1: 10 physical devices > > ciss1: 4 logical drives > > ciss1: logical drive (b0t0): RAID 1, 69120MB online > > ciss1: logical drive (b0t1): RAID 1, 69120MB online > > ciss1: logical drive (b0t2): RAID 1, 139776MB online > > ciss1: logical drive (b0t3): RAID 1, 139776MB online > > > > ciss2: port 0x6400-0x64ff mem > > 0xfdf7-0xfdf71fff,0xfdf0-0xfdf3 irq 98 at device 5.0 on pci11 > > ciss2: Reserved 0x2000 bytes for rid 0x10 type 3 at 0xfdf7 > > pci11: child ciss2 requested type 3 for rid 0, but the BAR says it is an > > ioport > > ciss2: can't allocate config window > > device_attach: ciss2 attach returned 6 > > Oh, so it didn't work in 6.x either, it just handles failure less gracefully > in 7.0+? No, ciss2 is disabled. The difference is that 6.x continue to boot instead of a kernel panic as in 7.x and 8.x. I dont have any disks attached to ciss2, so I dont really need it. But ciss1 and ciss2 is on the same physical card, so I cant just remove it. /Bjorn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: HP 380 G4 - ciss kernel page fault.
On Wednesday 28 April 2010 10:07:56 am kama wrote: > > On Wed, 28 Apr 2010, John Baldwin wrote: > > > On Wednesday 28 April 2010 3:22:44 am kama wrote: > > > > > > On Tue, 27 Apr 2010, John Baldwin wrote: > > > > > > > On Tuesday 27 April 2010 9:30:12 am kama wrote: > > > > > > > > > > Hi. > > > > > > > > > > I have problem when probing the ciss device. Causing a kernel panic. > > This > > > > > happened when I upgraded from 6.3 to 7.3-stable. Booting the old kernel > > > > > works. So something has changed. I am also getting the error on both the > > > > > 7.3 and the 8.0 install cd's. > > > > > > > > > > The ciss that causing the problem is a Smart Array 6404 and its the > > addon > > > > > card that it faults at. The server disconnect it due to an error. But > > > > > since it works on 6.3 it is something that have changed. FreeBSD should > > > > > not panic, it should just disable it. > > > > > > > > > > Also I tried to disable the card in the BIOS, but FreeBSD try to probe > > it > > > > > anyway and panic. > > > > > > > > > > This whats comes up on a verbose boot through the ILO remote console. > > > > > (typed in manually from a screenshot) > > > > > > > > > > ciss2: port 0x6400-0x64ff mem > > > > > 0xfdf7-0xfdf71fff irq 98 at device 5.0 on pcill > > > > > ciss2: Reserved 0x2000 bytes for rid 0x10 type 3 at 0xfdf7 > > > > > pci11: child ciss2 requested type 3 for rid 0, but the BAR says it is an > > > > > ioport > > > > > ciss2: can't allocate config window > > > > > kernel trap 12 with interupts disabled > > > > > > > > Can you get the ciss2 boot messages from a working 6.x kernel? > > > > > > This is the verbose boot on 6.3. > > > > > > FreeBSD 6.3-STABLE #3: Thu Mar 6 14:29:33 CET 2008 > > > > > > ciss1: 10 physical devices > > > ciss1: 4 logical drives > > > ciss1: logical drive (b0t0): RAID 1, 69120MB online > > > ciss1: logical drive (b0t1): RAID 1, 69120MB online > > > ciss1: logical drive (b0t2): RAID 1, 139776MB online > > > ciss1: logical drive (b0t3): RAID 1, 139776MB online > > > > > > ciss2: port 0x6400-0x64ff mem > > > 0xfdf7-0xfdf71fff,0xfdf0-0xfdf3 irq 98 at device 5.0 on pci11 > > > ciss2: Reserved 0x2000 bytes for rid 0x10 type 3 at 0xfdf7 > > > pci11: child ciss2 requested type 3 for rid 0, but the BAR says it is an > > > ioport > > > ciss2: can't allocate config window > > > device_attach: ciss2 attach returned 6 > > > > Oh, so it didn't work in 6.x either, it just handles failure less gracefully > > in 7.0+? > > No, ciss2 is disabled. The difference is that 6.x continue to boot instead > of a kernel panic as in 7.x and 8.x. > > I dont have any disks attached to ciss2, so I dont really need it. But > ciss1 and ciss2 is on the same physical card, so I cant just remove it. Can you try this patch? Index: ciss.c === --- ciss.c (revision 207062) +++ ciss.c (working copy) @@ -417,6 +417,7 @@ sc = device_get_softc(dev); sc->ciss_dev = dev; mtx_init(&sc->ciss_mtx, "cissmtx", NULL, MTX_DEF); +callout_init_mtx(&sc->ciss_periodic, &sc->ciss_mtx, 0); /* * Do PCI-specific init. @@ -429,7 +430,6 @@ */ ciss_initq_free(sc); ciss_initq_notify(sc); -callout_init_mtx(&sc->ciss_periodic, &sc->ciss_mtx, 0); /* * Initalize device sysctls. -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: MFC of "Large set of CAM improvements" breaks I/O to Adaptec 29160 SCSI controller
Andy Farkas wrote: > RELENG_8 csup'd with date=2010.02.14.00.00 works perfectly for days. > > RELENG_8 csup'd with date=2010.02.15.00.00 dead-locks the disk I/O > subsystem. Network still operational but anything needing disk hangs. > Power-cycle required. > > kernel config is GENERIC with KDB, DDB and BREAK_TO_DEBUGGER options added. > > hardware: > ahc0: port 0x4000-0x40ff mem > 0xefa0-0xefa00fff irq 16 at device 0.0 on pci10 > ahc0: [ITHREAD] > aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs > > da0: Fixed Direct Access SCSI-3 device > da1: Fixed Direct Access SCSI-3 device > > > The dead-lock can happen at any time, but I can provoke it by running > a bonnie++ disk test. It happens doing rm -rf /usr/obj/usr and it has > happened doing a make installworld. It can survive a make buildworld > (the system runs normally until it decides to dead-lock). > > The box (HP ProLiant ML 110) has 2 scsi disks and 4 sata disks. The > 2010.02.15 kernel will run perfectly for days on the SATA disks. *Only* > when the scsi disks are accessed will the system dead-lock. Note that > the SATA disks do not work either if the system has dead-locked. > > I can provide more details and a vmcore.0 if anyone is interested. I have some 29160N locally and I'll try to reproduce this. -- Alexander Motin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: HP 380 G4 - ciss kernel page fault.
On Wed, Apr 28, 2010 at 4:07 PM, kama wrote:
>
>
> On Wed, 28 Apr 2010, John Baldwin wrote:
>
>> On Wednesday 28 April 2010 3:22:44 am kama wrote:
>> >
>> > On Tue, 27 Apr 2010, John Baldwin wrote:
>> >
>> > > On Tuesday 27 April 2010 9:30:12 am kama wrote:
>> > > >
>> > > > Hi.
>> > > >
>> > > > I have problem when probing the ciss device. Causing a kernel panic.
>> This
>> > > > happened when I upgraded from 6.3 to 7.3-stable. Booting the old kernel
>> > > > works. So something has changed. I am also getting the error on both
>> > > > the
>> > > > 7.3 and the 8.0 install cd's.
>> > > >
>> > > > The ciss that causing the problem is a Smart Array 6404 and its the
>> addon
>> > > > card that it faults at. The server disconnect it due to an error. But
>> > > > since it works on 6.3 it is something that have changed. FreeBSD should
>> > > > not panic, it should just disable it.
>> > > >
>> > > > Also I tried to disable the card in the BIOS, but FreeBSD try to probe
>> it
>> > > > anyway and panic.
>> > > >
>> > > > This whats comes up on a verbose boot through the ILO remote console.
>> > > > (typed in manually from a screenshot)
>> > > >
>> > > > ciss2: port 0x6400-0x64ff mem
>> > > > 0xfdf7-0xfdf71fff irq 98 at device 5.0 on pcill
>> > > > ciss2: Reserved 0x2000 bytes for rid 0x10 type 3 at 0xfdf7
>> > > > pci11: child ciss2 requested type 3 for rid 0, but the BAR says it is
>> > > > an
>> > > > ioport
>> > > > ciss2: can't allocate config window
>> > > > kernel trap 12 with interupts disabled
>> > >
>> > > Can you get the ciss2 boot messages from a working 6.x kernel?
>> >
>> > This is the verbose boot on 6.3.
>> >
>> > FreeBSD 6.3-STABLE #3: Thu Mar 6 14:29:33 CET 2008
>> >
>> > ciss1: 10 physical devices
>> > ciss1: 4 logical drives
>> > ciss1: logical drive (b0t0): RAID 1, 69120MB online
>> > ciss1: logical drive (b0t1): RAID 1, 69120MB online
>> > ciss1: logical drive (b0t2): RAID 1, 139776MB online
>> > ciss1: logical drive (b0t3): RAID 1, 139776MB online
>> >
>> > ciss2: port 0x6400-0x64ff mem
>> > 0xfdf7-0xfdf71fff,0xfdf0-0xfdf3 irq 98 at device 5.0 on pci11
>> > ciss2: Reserved 0x2000 bytes for rid 0x10 type 3 at 0xfdf7
>> > pci11: child ciss2 requested type 3 for rid 0, but the BAR says it is an
>> > ioport
>> > ciss2: can't allocate config window
>> > device_attach: ciss2 attach returned 6
>>
>> Oh, so it didn't work in 6.x either, it just handles failure less gracefully
>> in 7.0+?
>
> No, ciss2 is disabled. The difference is that 6.x continue to boot instead
> of a kernel panic as in 7.x and 8.x.
>
> I dont have any disks attached to ciss2, so I dont really need it. But
> ciss1 and ciss2 is on the same physical card, so I cant just remove it.
>
Could you try this one if you are looking for a patch to 7-STABLE.
Thank you
diff -r ffd3e5d37758 sys/dev/ciss/ciss.c
--- a/sys/dev/ciss/ciss.c Wed Apr 28 10:20:41 2010 -0400
+++ b/sys/dev/ciss/ciss.c Wed Apr 28 11:39:05 2010 -0400
@@ -394,6 +394,8 @@ ciss_attach(device_t dev)
sc = device_get_softc(dev);
sc->ciss_dev = dev;
+mtx_init(&sc->ciss_mtx, "cissmtx", NULL, MTX_DEF);
+callout_init_mtx(&sc->ciss_periodic, &sc->ciss_mtx, 0);
/*
* Work out adapter type.
@@ -428,8 +430,6 @@ ciss_attach(device_t dev)
ciss_initq_busy(sc);
ciss_initq_complete(sc);
ciss_initq_notify(sc);
-mtx_init(&sc->ciss_mtx, "cissmtx", NULL, MTX_DEF);
-callout_init_mtx(&sc->ciss_periodic, &sc->ciss_mtx, 0);
/*
* Initalize device sysctls.
@@ -494,8 +494,11 @@ ciss_attach(device_t dev)
error = 0;
out:
-if (error != 0)
- ciss_free(sc);
+if (error != 0) {
+ /* ciss_free() expects the mutex to be held */
+ mtx_lock(&sc->ciss_mtx);
+ ciss_free(sc);
+ }
return(error);
}
--
Gianni
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: HP 380 G4 - ciss kernel page fault.
On Wed, Apr 28, 2010 at 5:41 PM, Giovanni Trematerra wrote: > On Wed, Apr 28, 2010 at 4:07 PM, kama wrote: >> >> >> On Wed, 28 Apr 2010, John Baldwin wrote: >> >>> On Wednesday 28 April 2010 3:22:44 am kama wrote: >>> > >>> > On Tue, 27 Apr 2010, John Baldwin wrote: >>> > >>> > > On Tuesday 27 April 2010 9:30:12 am kama wrote: >>> > > > >>> > > > Hi. >>> > > > >>> > > > I have problem when probing the ciss device. Causing a kernel panic. >>> This >>> > > > happened when I upgraded from 6.3 to 7.3-stable. Booting the old >>> > > > kernel >>> > > > works. So something has changed. I am also getting the error on both >>> > > > the >>> > > > 7.3 and the 8.0 install cd's. >>> > > > >>> > > > The ciss that causing the problem is a Smart Array 6404 and its the >>> addon >>> > > > card that it faults at. The server disconnect it due to an error. But >>> > > > since it works on 6.3 it is something that have changed. FreeBSD >>> > > > should >>> > > > not panic, it should just disable it. >>> > > > >>> > > > Also I tried to disable the card in the BIOS, but FreeBSD try to probe >>> it >>> > > > anyway and panic. >>> > > > >>> > > > This whats comes up on a verbose boot through the ILO remote console. >>> > > > (typed in manually from a screenshot) >>> > > > >>> > > > ciss2: port 0x6400-0x64ff mem >>> > > > 0xfdf7-0xfdf71fff irq 98 at device 5.0 on pcill >>> > > > ciss2: Reserved 0x2000 bytes for rid 0x10 type 3 at 0xfdf7 >>> > > > pci11: child ciss2 requested type 3 for rid 0, but the BAR says it is >>> > > > an >>> > > > ioport >>> > > > ciss2: can't allocate config window >>> > > > kernel trap 12 with interupts disabled >>> > > >>> > > Can you get the ciss2 boot messages from a working 6.x kernel? >>> > >>> > This is the verbose boot on 6.3. >>> > >>> > FreeBSD 6.3-STABLE #3: Thu Mar 6 14:29:33 CET 2008 >>> > >>> > ciss1: 10 physical devices >>> > ciss1: 4 logical drives >>> > ciss1: logical drive (b0t0): RAID 1, 69120MB online >>> > ciss1: logical drive (b0t1): RAID 1, 69120MB online >>> > ciss1: logical drive (b0t2): RAID 1, 139776MB online >>> > ciss1: logical drive (b0t3): RAID 1, 139776MB online >>> > >>> > ciss2: port 0x6400-0x64ff mem >>> > 0xfdf7-0xfdf71fff,0xfdf0-0xfdf3 irq 98 at device 5.0 on pci11 >>> > ciss2: Reserved 0x2000 bytes for rid 0x10 type 3 at 0xfdf7 >>> > pci11: child ciss2 requested type 3 for rid 0, but the BAR says it is an >>> > ioport >>> > ciss2: can't allocate config window >>> > device_attach: ciss2 attach returned 6 >>> >>> Oh, so it didn't work in 6.x either, it just handles failure less gracefully >>> in 7.0+? >> >> No, ciss2 is disabled. The difference is that 6.x continue to boot instead >> of a kernel panic as in 7.x and 8.x. >> >> I dont have any disks attached to ciss2, so I dont really need it. But >> ciss1 and ciss2 is on the same physical card, so I cant just remove it. >> > > Could you try this one if you are looking for a patch to 7-STABLE. > > Thank you > [snip patch] I think it's worth to have mtx_assert(&sc->ciss_mtx, MA_OWNED); in ciss_free just to be on safe side. -- Gianni ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: HP 380 G4 - ciss kernel page fault.
On Wed, 28 Apr 2010, Giovanni Trematerra wrote: > On Wed, Apr 28, 2010 at 5:41 PM, Giovanni Trematerra > wrote: > > On Wed, Apr 28, 2010 at 4:07 PM, kama wrote: > >> > >> > >> On Wed, 28 Apr 2010, John Baldwin wrote: > >> > >>> On Wednesday 28 April 2010 3:22:44 am kama wrote: > >>> > > >>> > On Tue, 27 Apr 2010, John Baldwin wrote: > >>> > > >>> > > On Tuesday 27 April 2010 9:30:12 am kama wrote: > >>> > > > > >>> > > > Hi. > >>> > > > > >>> > > > I have problem when probing the ciss device. Causing a kernel panic. > >>> This > >>> > > > happened when I upgraded from 6.3 to 7.3-stable. Booting the old > >>> > > > kernel > >>> > > > works. So something has changed. I am also getting the error on > >>> > > > both the > >>> > > > 7.3 and the 8.0 install cd's. > >>> > > > > >>> > > > The ciss that causing the problem is a Smart Array 6404 and its the > >>> addon > >>> > > > card that it faults at. The server disconnect it due to an error. > >>> > > > But > >>> > > > since it works on 6.3 it is something that have changed. FreeBSD > >>> > > > should > >>> > > > not panic, it should just disable it. > >>> > > > > >>> > > > Also I tried to disable the card in the BIOS, but FreeBSD try to > >>> > > > probe > >>> it > >>> > > > anyway and panic. > >>> > > > > >>> > > > This whats comes up on a verbose boot through the ILO remote > >>> > > > console. > >>> > > > (typed in manually from a screenshot) > >>> > > > > >>> > > > ciss2: port 0x6400-0x64ff mem > >>> > > > 0xfdf7-0xfdf71fff irq 98 at device 5.0 on pcill > >>> > > > ciss2: Reserved 0x2000 bytes for rid 0x10 type 3 at 0xfdf7 > >>> > > > pci11: child ciss2 requested type 3 for rid 0, but the BAR says it > >>> > > > is an > >>> > > > ioport > >>> > > > ciss2: can't allocate config window > >>> > > > kernel trap 12 with interupts disabled > >>> > > > >>> > > Can you get the ciss2 boot messages from a working 6.x kernel? > >>> > > >>> > This is the verbose boot on 6.3. > >>> > > >>> > FreeBSD 6.3-STABLE #3: Thu Mar 6 14:29:33 CET 2008 > >>> > > >>> > ciss1: 10 physical devices > >>> > ciss1: 4 logical drives > >>> > ciss1: logical drive (b0t0): RAID 1, 69120MB online > >>> > ciss1: logical drive (b0t1): RAID 1, 69120MB online > >>> > ciss1: logical drive (b0t2): RAID 1, 139776MB online > >>> > ciss1: logical drive (b0t3): RAID 1, 139776MB online > >>> > > >>> > ciss2: port 0x6400-0x64ff mem > >>> > 0xfdf7-0xfdf71fff,0xfdf0-0xfdf3 irq 98 at device 5.0 on > >>> > pci11 > >>> > ciss2: Reserved 0x2000 bytes for rid 0x10 type 3 at 0xfdf7 > >>> > pci11: child ciss2 requested type 3 for rid 0, but the BAR says it is an > >>> > ioport > >>> > ciss2: can't allocate config window > >>> > device_attach: ciss2 attach returned 6 > >>> > >>> Oh, so it didn't work in 6.x either, it just handles failure less > >>> gracefully > >>> in 7.0+? > >> > >> No, ciss2 is disabled. The difference is that 6.x continue to boot instead > >> of a kernel panic as in 7.x and 8.x. > >> > >> I dont have any disks attached to ciss2, so I dont really need it. But > >> ciss1 and ciss2 is on the same physical card, so I cant just remove it. > >> > > > > Could you try this one if you are looking for a patch to 7-STABLE. > > > > Thank you > > > > [snip patch] > > I think it's worth to have > > mtx_assert(&sc->ciss_mtx, MA_OWNED); > > in ciss_free just to be on safe side. Where in ciss_free()? /Bjorn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: MFC of "Large set of CAM improvements" breaks I/O to Adaptec 29160 SCSI controller
> I have some 29160N locally and I'll try to reproduce this. I would suggest you try gmirror across two drives - that is how both myself and the original poster first noticed the issue. cheers, -pete. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: HP 380 G4 - ciss kernel page fault.
On Wed, 28 Apr 2010, Giovanni Trematerra wrote:
> On Wed, Apr 28, 2010 at 4:07 PM, kama wrote:
> >
> >
> > On Wed, 28 Apr 2010, John Baldwin wrote:
> >
> >> On Wednesday 28 April 2010 3:22:44 am kama wrote:
> >> >
> >> > On Tue, 27 Apr 2010, John Baldwin wrote:
> >> >
> >> > > On Tuesday 27 April 2010 9:30:12 am kama wrote:
> >> > > >
> >> > > > Hi.
> >> > > >
> >> > > > I have problem when probing the ciss device. Causing a kernel panic.
> >> This
> >> > > > happened when I upgraded from 6.3 to 7.3-stable. Booting the old
> >> > > > kernel
> >> > > > works. So something has changed. I am also getting the error on both
> >> > > > the
> >> > > > 7.3 and the 8.0 install cd's.
> >> > > >
> >> > > > The ciss that causing the problem is a Smart Array 6404 and its the
> >> addon
> >> > > > card that it faults at. The server disconnect it due to an error. But
> >> > > > since it works on 6.3 it is something that have changed. FreeBSD
> >> > > > should
> >> > > > not panic, it should just disable it.
> >> > > >
> >> > > > Also I tried to disable the card in the BIOS, but FreeBSD try to
> >> > > > probe
> >> it
> >> > > > anyway and panic.
> >> > > >
> >> > > > This whats comes up on a verbose boot through the ILO remote console.
> >> > > > (typed in manually from a screenshot)
> >> > > >
> >> > > > ciss2: port 0x6400-0x64ff mem
> >> > > > 0xfdf7-0xfdf71fff irq 98 at device 5.0 on pcill
> >> > > > ciss2: Reserved 0x2000 bytes for rid 0x10 type 3 at 0xfdf7
> >> > > > pci11: child ciss2 requested type 3 for rid 0, but the BAR says it
> >> > > > is an
> >> > > > ioport
> >> > > > ciss2: can't allocate config window
> >> > > > kernel trap 12 with interupts disabled
> >> > >
> >> > > Can you get the ciss2 boot messages from a working 6.x kernel?
> >> >
> >> > This is the verbose boot on 6.3.
> >> >
> >> > FreeBSD 6.3-STABLE #3: Thu Mar 6 14:29:33 CET 2008
> >> >
> >> > ciss1: 10 physical devices
> >> > ciss1: 4 logical drives
> >> > ciss1: logical drive (b0t0): RAID 1, 69120MB online
> >> > ciss1: logical drive (b0t1): RAID 1, 69120MB online
> >> > ciss1: logical drive (b0t2): RAID 1, 139776MB online
> >> > ciss1: logical drive (b0t3): RAID 1, 139776MB online
> >> >
> >> > ciss2: port 0x6400-0x64ff mem
> >> > 0xfdf7-0xfdf71fff,0xfdf0-0xfdf3 irq 98 at device 5.0 on pci11
> >> > ciss2: Reserved 0x2000 bytes for rid 0x10 type 3 at 0xfdf7
> >> > pci11: child ciss2 requested type 3 for rid 0, but the BAR says it is an
> >> > ioport
> >> > ciss2: can't allocate config window
> >> > device_attach: ciss2 attach returned 6
> >>
> >> Oh, so it didn't work in 6.x either, it just handles failure less
> >> gracefully
> >> in 7.0+?
> >
> > No, ciss2 is disabled. The difference is that 6.x continue to boot instead
> > of a kernel panic as in 7.x and 8.x.
> >
> > I dont have any disks attached to ciss2, so I dont really need it. But
> > ciss1 and ciss2 is on the same physical card, so I cant just remove it.
> >
>
> Could you try this one if you are looking for a patch to 7-STABLE.
>
> Thank you
>
> diff -r ffd3e5d37758 sys/dev/ciss/ciss.c
> --- a/sys/dev/ciss/ciss.c Wed Apr 28 10:20:41 2010 -0400
> +++ b/sys/dev/ciss/ciss.c Wed Apr 28 11:39:05 2010 -0400
> @@ -394,6 +394,8 @@ ciss_attach(device_t dev)
>
> sc = device_get_softc(dev);
> sc->ciss_dev = dev;
> +mtx_init(&sc->ciss_mtx, "cissmtx", NULL, MTX_DEF);
> +callout_init_mtx(&sc->ciss_periodic, &sc->ciss_mtx, 0);
>
> /*
> * Work out adapter type.
> @@ -428,8 +430,6 @@ ciss_attach(device_t dev)
> ciss_initq_busy(sc);
> ciss_initq_complete(sc);
> ciss_initq_notify(sc);
> -mtx_init(&sc->ciss_mtx, "cissmtx", NULL, MTX_DEF);
> -callout_init_mtx(&sc->ciss_periodic, &sc->ciss_mtx, 0);
>
> /*
> * Initalize device sysctls.
> @@ -494,8 +494,11 @@ ciss_attach(device_t dev)
>
> error = 0;
> out:
> -if (error != 0)
> - ciss_free(sc);
> +if (error != 0) {
> + /* ciss_free() expects the mutex to be held */
> + mtx_lock(&sc->ciss_mtx);
> + ciss_free(sc);
> + }
> return(error);
> }
>
This patch made the system boot again.
FreeBSD 7.3-STABLE #2: Wed Apr 28 19:17:43 CEST 2010
ciss1: 4 logical drives
ciss1: logical drive (b0t0): RAID 1, 69120MB online
ciss1: logical drive (b0t1): RAID 1, 69120MB online
ciss1: logical drive (b0t2): RAID 1, 139776MB online
ciss1: logical drive (b0t3): RAID 1, 139776MB online
ciss2: port 0x6400-0x64ff mem
0xfdf7-0xfdf71fff irq 98 at device 5.0 on pci11
ciss2: Reserved 0x2000 bytes for rid 0x10 type 3 at 0xfdf7
pci11: child ciss2 requested type 3 for rid 0, but the BAR says it is an
ioport
ciss2: can't allocate config window
device_attach: ciss2 attach returned 6
uhci0: port 0x2000-0x201f irq
16 at device 29.0 on pci0
uhci0: Reserved 0x20 bytes for rid 0x20 type 4 at 0x2000
ioapic0: routing intpin 16 (PCI IRQ 16) to vector 55
uhci0: [GIANT-LOCKED]
uhci0: [ITHREAD]
usb0: on uhc
BCM5704 routing problem
I upgraded my gateway last week to RELENG_8 and noticed that I can no longer forward or receive IP packets from hosts on internal LAN. When trying to ping a host or the gateway IP itself, you get. # ping 192.168.1.10 PING 192.168.1.10 (192.168.1.10): 56 data bytes ^C --- 192.168.1.10 ping statistics --- 5 packets transmitted, 0 packets received, 100% packet loss All rc.conf files on gateway and hosts themselves had correct settings. b...@pci0:10:9:1: class=0x02 card=0x164414e4 chip=0x164814e4 rev=0x03 hdr=0x00 vendor = 'Broadcom Corporation' device = 'NetXtreme Dual Gigabit Adapter (BCM5704)' class = network subclass = ethernet bar [10] = type Memory, range 64, base 0xdf33, size 65536, enabled bar [18] = type Memory, range 64, base 0xdf32, size 65536, enabled cap 07[40] = PCI-X 64-bit supports 133MHz, 2048 burst read, 1 split transaction cap 01[48] = powerspec 2 supports D0 D3 current D0 cap 03[50] = VPD cap 05[58] = MSI supports 8 messages, 64 bit Previously I was running 7.2 as gateway and never encountered any problems. I've since gone back to release 7.3 and routing works as expected. Any input would be appreciated. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
buildworld fails on ifmcstat
Hi, I tried to make buildworld with a custom src.conf to prevent many useless things since I want to build for a jail. This is what I added: .if defined(BUILD_JAIL) WITHOUT_ACPI="YES" WITHOUT_APM="YES" WITHOUT_GAMES="YES" WITHOUT_AMD="YES" WITHOUT_AUTHPF="YES" WITHOUT_AUDIT="YES" WITHOUT_BLUETOOTH="YES" WITHOUT_BOOT="YES" WITHOUT_BSNMP="YES" WITHOUT_CDDL="YES" WITHOUT_DICT="YES" WITHOUT_EXAMPLES="YES" WITHOUT_FORTH="YES" WITHOUT_GCOV="YES" WITHOUT_FLOPPY="YES" WITHOUT_GPIB="YES" WITHOUT_HTML="YES" WITHOUT_IPFILTER="YES" WITHOUT_IPX="YES" WITHOUT_IPFW="YES" WITHOUT_JAIL="YES" WITHOUT_KVM="YES" WITHOUT_LEGACY_CONSOLE="YES" WITHOUT_LIB32="YES" WITHOUT_LPR="YES" WITHOUT_NDIS="YES" WITHOUT_NETCAT="YES" WITHOUT_NETGRAPH="YES" WITHOUT_NIS="YES" WITHOUT_NTP="YES" WITHOUT_PF="YES" WITHOUT_PORTSNAP="YES" WITHOUT_PPP="YES" WITHOUT_QUOTAS="YES" WITHOUT_SENDMAIL="YES" WITHOUT_RESCUE="YES" WITHOUT_SHAREDOCS="YES" WITHOUT_SYSCONS="YES" WITHOUT_SYSINSTALL="YES" WITHOUT_USB="YES" WITHOUT_WIRELESS="YES" .endif make BUILD_JAIL=yes buildworld now fails on : ===> usr.sbin/ifmcstat (all) cc -O2 -pipe -DINET6 -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -c /usr/src/usr.sbin/ifmcstat/ifmcstat.c cc1: warnings being treated as errors /usr/src/usr.sbin/ifmcstat/ifmcstat.c:170: warning: 'in6_ifinfo' used but never defined *** Error code 1 Is my src.conf wrong ? King regards, David. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: buildworld fails on ifmcstat
On Wed, Apr 28, 2010 at 11:49 AM, Demelier David wrote: > Hi, > I tried to make buildworld with a custom src.conf to prevent many > useless things since I want to build for a jail. > > This is what I added: > > .if defined(BUILD_JAIL) > WITHOUT_ACPI="YES" > WITHOUT_APM="YES" > WITHOUT_GAMES="YES" > WITHOUT_AMD="YES" > WITHOUT_AUTHPF="YES" > WITHOUT_AUDIT="YES" > WITHOUT_BLUETOOTH="YES" > WITHOUT_BOOT="YES" > WITHOUT_BSNMP="YES" > WITHOUT_CDDL="YES" > WITHOUT_DICT="YES" > WITHOUT_EXAMPLES="YES" > WITHOUT_FORTH="YES" > WITHOUT_GCOV="YES" > WITHOUT_FLOPPY="YES" > WITHOUT_GPIB="YES" > WITHOUT_HTML="YES" > WITHOUT_IPFILTER="YES" > WITHOUT_IPX="YES" > WITHOUT_IPFW="YES" > WITHOUT_JAIL="YES" > WITHOUT_KVM="YES" > WITHOUT_LEGACY_CONSOLE="YES" > WITHOUT_LIB32="YES" > WITHOUT_LPR="YES" > WITHOUT_NDIS="YES" > WITHOUT_NETCAT="YES" > WITHOUT_NETGRAPH="YES" > WITHOUT_NIS="YES" > WITHOUT_NTP="YES" > WITHOUT_PF="YES" > WITHOUT_PORTSNAP="YES" > WITHOUT_PPP="YES" > WITHOUT_QUOTAS="YES" > WITHOUT_SENDMAIL="YES" > WITHOUT_RESCUE="YES" > WITHOUT_SHAREDOCS="YES" > WITHOUT_SYSCONS="YES" > WITHOUT_SYSINSTALL="YES" > WITHOUT_USB="YES" > WITHOUT_WIRELESS="YES" > .endif > > make BUILD_JAIL=yes buildworld now fails on : > > ===> usr.sbin/ifmcstat (all) > cc -O2 -pipe -DINET6 -std=gnu99 -fstack-protector -Wsystem-headers > -Werror -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -c > /usr/src/usr.sbin/ifmcstat/ifmcstat.c > cc1: warnings being treated as errors > /usr/src/usr.sbin/ifmcstat/ifmcstat.c:170: warning: 'in6_ifinfo' used > but never defined > *** Error code 1 I would avoid the cross-post next time. The issue might be that that application should be properly compiled when WITHOUT_INET6 is specified, but it's kind of odd though because you don't have that specified above... If you looked through the source around line 170 you'll find out that that function requires WITH_KVM to be defined as well in order for you to use the function definition (and not just the prototype). I've CCed bms@ for assistance. Thanks, -Garrett ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: BCM5704 routing problem
On Wed, Apr 28, 2010 at 02:25:56PM -0400, Gardner Bell wrote: > I upgraded my gateway last week to RELENG_8 and noticed that I can no > longer forward or receive IP packets from hosts on internal LAN. When > trying to ping a host or the gateway IP itself, you get. > > # ping 192.168.1.10 > PING 192.168.1.10 (192.168.1.10): 56 data bytes > ^C > > --- 192.168.1.10 ping statistics --- > 5 packets transmitted, 0 packets received, 100% packet loss > > All rc.conf files on gateway and hosts themselves had correct settings. > > b...@pci0:10:9:1: class=0x02 card=0x164414e4 chip=0x164814e4 > rev=0x03 hdr=0x00 > vendor = 'Broadcom Corporation' > device = 'NetXtreme Dual Gigabit Adapter (BCM5704)' > class = network > subclass = ethernet > bar [10] = type Memory, range 64, base 0xdf33, size 65536, > enabled > bar [18] = type Memory, range 64, base 0xdf32, size 65536, > enabled > cap 07[40] = PCI-X 64-bit supports 133MHz, 2048 burst read, 1 split > transaction > cap 01[48] = powerspec 2 supports D0 D3 current D0 > cap 03[50] = VPD > cap 05[58] = MSI supports 8 messages, 64 bit > > Previously I was running 7.2 as gateway and never encountered any > problems. I've since gone back to release 7.3 and routing works as > expected. > > Any input would be appreciated. Output from the following when the machine is running RELENG_8: - ifconfig -a - netstat -i - netstat -rn - sysctl -a | grep bge - Contents of /etc/rc.conf -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: BCM5704 routing problem
On Wed, Apr 28, 2010 at 12:19:01PM -0700, Jeremy Chadwick wrote: > On Wed, Apr 28, 2010 at 02:25:56PM -0400, Gardner Bell wrote: > > I upgraded my gateway last week to RELENG_8 and noticed that I can no > > longer forward or receive IP packets from hosts on internal LAN. When > > trying to ping a host or the gateway IP itself, you get. > > > > # ping 192.168.1.10 > > PING 192.168.1.10 (192.168.1.10): 56 data bytes > > ^C > > > > --- 192.168.1.10 ping statistics --- > > 5 packets transmitted, 0 packets received, 100% packet loss > > > > All rc.conf files on gateway and hosts themselves had correct settings. > > > > b...@pci0:10:9:1: class=0x02 card=0x164414e4 chip=0x164814e4 > > rev=0x03 hdr=0x00 > > vendor = 'Broadcom Corporation' > > device = 'NetXtreme Dual Gigabit Adapter (BCM5704)' > > class = network > > subclass = ethernet > > bar [10] = type Memory, range 64, base 0xdf33, size 65536, > > enabled > > bar [18] = type Memory, range 64, base 0xdf32, size 65536, > > enabled > > cap 07[40] = PCI-X 64-bit supports 133MHz, 2048 burst read, 1 split > > transaction > > cap 01[48] = powerspec 2 supports D0 D3 current D0 > > cap 03[50] = VPD > > cap 05[58] = MSI supports 8 messages, 64 bit > > > > Previously I was running 7.2 as gateway and never encountered any > > problems. I've since gone back to release 7.3 and routing works as > > expected. > > > > Any input would be appreciated. > > Output from the following when the machine is running RELENG_8: > > - ifconfig -a > - netstat -i > - netstat -rn > - sysctl -a | grep bge > - Contents of /etc/rc.conf I forgot one more: dmesg | grep -C 10 bge1 -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: puc(4) timedia baudrate problem
On Apr 27, 2010, at 10:10 PM, Artem Belevich wrote: > I've got another PCI UART card based on OX16PCI952 that needs its > clock multiplied by 8 in order to work correctly. It was some > el-cheapo card I've got at Fry's. > > p...@pci0:1:0:0:class=0x070006 card=0x00011415 chip=0x95211415 > rev=0x00 hdr=0x00 >vendor = 'Oxford Semiconductor Ltd' >device = 'OX16PCI952 Integrated Dual UART' >class = simple comms >subclass = UART >bar [10] = type I/O Port, range 32, base 0xd480, size 8, enabled >bar [14] = type I/O Port, range 32, base 0xd400, size 8, enabled >bar [18] = type I/O Port, range 32, base 0xd080, size 32, enabled >bar [1c] = type Memory, range 32, base 0xf9ffd000, size 4096, enabled >bar [20] = type Memory, range 32, base 0xf9ffc000, size 4096, enabled > > Perhaps we can add some sort of tunable to override UART clock, if necessary? That's a good idea. I've seen with the Oxford that the RCLK can different even for the same vendor/device ID. There's no way for us to do the right thing. This may also be the case for Timedia chipsets... -- Marcel Moolenaar xcl...@mac.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: MFC of "Large set of CAM improvements" breaks I/O to Adaptec 29160 SCSI controller
Pete French wrote: >> I have some 29160N locally and I'll try to reproduce this. > > I would suggest you try gmirror across two drives - that is how > both myself and the original poster first noticed the issue. Thanks. First step successful - I can steadily reproduce problem on CURRENT. raidtest with 200 I/O streams over gmirror of two disks on same channel triggers issue in seconds. Any I/O on channel dying after both disks report "Queue full" error same time. The rest of system works fine. If I preliminarily manually adjust queue depth of one disk - everything works fine. I'll investigate it tomorrow. -- Alexander Motin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: HP 380 G4 - ciss kernel page fault.
On Wednesday 28 April 2010 1:38:15 pm kama wrote:
>
> On Wed, 28 Apr 2010, Giovanni Trematerra wrote:
>
> > On Wed, Apr 28, 2010 at 4:07 PM, kama wrote:
> > >
> > >
> > > On Wed, 28 Apr 2010, John Baldwin wrote:
> > >
> > >> On Wednesday 28 April 2010 3:22:44 am kama wrote:
> > >> >
> > >> > On Tue, 27 Apr 2010, John Baldwin wrote:
> > >> >
> > >> > > On Tuesday 27 April 2010 9:30:12 am kama wrote:
> > >> > > >
> > >> > > > Hi.
> > >> > > >
> > >> > > > I have problem when probing the ciss device. Causing a kernel
panic.
> > >> This
> > >> > > > happened when I upgraded from 6.3 to 7.3-stable. Booting the old
kernel
> > >> > > > works. So something has changed. I am also getting the error on
both the
> > >> > > > 7.3 and the 8.0 install cd's.
> > >> > > >
> > >> > > > The ciss that causing the problem is a Smart Array 6404 and its
the
> > >> addon
> > >> > > > card that it faults at. The server disconnect it due to an error.
But
> > >> > > > since it works on 6.3 it is something that have changed. FreeBSD
should
> > >> > > > not panic, it should just disable it.
> > >> > > >
> > >> > > > Also I tried to disable the card in the BIOS, but FreeBSD try to
probe
> > >> it
> > >> > > > anyway and panic.
> > >> > > >
> > >> > > > This whats comes up on a verbose boot through the ILO remote
console.
> > >> > > > (typed in manually from a screenshot)
> > >> > > >
> > >> > > > ciss2: port 0x6400-0x64ff mem
> > >> > > > 0xfdf7-0xfdf71fff irq 98 at device 5.0 on pcill
> > >> > > > ciss2: Reserved 0x2000 bytes for rid 0x10 type 3 at 0xfdf7
> > >> > > > pci11: child ciss2 requested type 3 for rid 0, but the BAR says
it is an
> > >> > > > ioport
> > >> > > > ciss2: can't allocate config window
> > >> > > > kernel trap 12 with interupts disabled
> > >> > >
> > >> > > Can you get the ciss2 boot messages from a working 6.x kernel?
> > >> >
> > >> > This is the verbose boot on 6.3.
> > >> >
> > >> > FreeBSD 6.3-STABLE #3: Thu Mar 6 14:29:33 CET 2008
> > >> >
> > >> > ciss1: 10 physical devices
> > >> > ciss1: 4 logical drives
> > >> > ciss1: logical drive (b0t0): RAID 1, 69120MB online
> > >> > ciss1: logical drive (b0t1): RAID 1, 69120MB online
> > >> > ciss1: logical drive (b0t2): RAID 1, 139776MB online
> > >> > ciss1: logical drive (b0t3): RAID 1, 139776MB online
> > >> >
> > >> > ciss2: port 0x6400-0x64ff mem
> > >> > 0xfdf7-0xfdf71fff,0xfdf0-0xfdf3 irq 98 at device 5.0 on
pci11
> > >> > ciss2: Reserved 0x2000 bytes for rid 0x10 type 3 at 0xfdf7
> > >> > pci11: child ciss2 requested type 3 for rid 0, but the BAR says it is
an
> > >> > ioport
> > >> > ciss2: can't allocate config window
> > >> > device_attach: ciss2 attach returned 6
> > >>
> > >> Oh, so it didn't work in 6.x either, it just handles failure less
gracefully
> > >> in 7.0+?
> > >
> > > No, ciss2 is disabled. The difference is that 6.x continue to boot
instead
> > > of a kernel panic as in 7.x and 8.x.
> > >
> > > I dont have any disks attached to ciss2, so I dont really need it. But
> > > ciss1 and ciss2 is on the same physical card, so I cant just remove it.
> > >
> >
> > Could you try this one if you are looking for a patch to 7-STABLE.
> >
> > Thank you
> >
> > diff -r ffd3e5d37758 sys/dev/ciss/ciss.c
> > --- a/sys/dev/ciss/ciss.c Wed Apr 28 10:20:41 2010 -0400
> > +++ b/sys/dev/ciss/ciss.c Wed Apr 28 11:39:05 2010 -0400
> > @@ -394,6 +394,8 @@ ciss_attach(device_t dev)
> >
> > sc = device_get_softc(dev);
> > sc->ciss_dev = dev;
> > +mtx_init(&sc->ciss_mtx, "cissmtx", NULL, MTX_DEF);
> > +callout_init_mtx(&sc->ciss_periodic, &sc->ciss_mtx, 0);
> >
> > /*
> > * Work out adapter type.
> > @@ -428,8 +430,6 @@ ciss_attach(device_t dev)
> > ciss_initq_busy(sc);
> > ciss_initq_complete(sc);
> > ciss_initq_notify(sc);
> > -mtx_init(&sc->ciss_mtx, "cissmtx", NULL, MTX_DEF);
> > -callout_init_mtx(&sc->ciss_periodic, &sc->ciss_mtx, 0);
> >
> > /*
> > * Initalize device sysctls.
> > @@ -494,8 +494,11 @@ ciss_attach(device_t dev)
> >
> > error = 0;
> > out:
> > -if (error != 0)
> > - ciss_free(sc);
> > +if (error != 0) {
> > + /* ciss_free() expects the mutex to be held */
> > + mtx_lock(&sc->ciss_mtx);
> > + ciss_free(sc);
> > + }
> > return(error);
> > }
> >
>
> This patch made the system boot again.
>
> FreeBSD 7.3-STABLE #2: Wed Apr 28 19:17:43 CEST 2010
>
> ciss1: 4 logical drives
> ciss1: logical drive (b0t0): RAID 1, 69120MB online
> ciss1: logical drive (b0t1): RAID 1, 69120MB online
> ciss1: logical drive (b0t2): RAID 1, 139776MB online
> ciss1: logical drive (b0t3): RAID 1, 139776MB online
> ciss2: port 0x6400-0x64ff mem
> 0xfdf7-0xfdf71fff irq 98 at device 5.0 on pci11
> ciss2: Reserved 0x2000 bytes for rid 0x10 type 3 at 0xfdf7
> pci11: child ciss2 requested type 3 for rid 0, but the BAR says it is an
> ioport
> ciss2: can't allocate config window
> de
Re: BCM5704 routing problem
On Wed, Apr 28, 2010 at 12:26:34PM -0700, Jeremy Chadwick wrote: > On Wed, Apr 28, 2010 at 12:19:01PM -0700, Jeremy Chadwick wrote: > > On Wed, Apr 28, 2010 at 02:25:56PM -0400, Gardner Bell wrote: > > > I upgraded my gateway last week to RELENG_8 and noticed that I can no > > > longer forward or receive IP packets from hosts on internal LAN. When > > > trying to ping a host or the gateway IP itself, you get. > > > > > > # ping 192.168.1.10 > > > PING 192.168.1.10 (192.168.1.10): 56 data bytes > > > ^C > > > > > > --- 192.168.1.10 ping statistics --- > > > 5 packets transmitted, 0 packets received, 100% packet loss > > > > > > All rc.conf files on gateway and hosts themselves had correct settings. > > > > > > b...@pci0:10:9:1: class=0x02 card=0x164414e4 chip=0x164814e4 > > > rev=0x03 hdr=0x00 > > > vendor = 'Broadcom Corporation' > > > device = 'NetXtreme Dual Gigabit Adapter (BCM5704)' > > > class = network > > > subclass = ethernet > > > bar [10] = type Memory, range 64, base 0xdf33, size 65536, > > > enabled > > > bar [18] = type Memory, range 64, base 0xdf32, size 65536, > > > enabled > > > cap 07[40] = PCI-X 64-bit supports 133MHz, 2048 burst read, 1 split > > > transaction > > > cap 01[48] = powerspec 2 supports D0 D3 current D0 > > > cap 03[50] = VPD > > > cap 05[58] = MSI supports 8 messages, 64 bit > > > > > > Previously I was running 7.2 as gateway and never encountered any > > > problems. I've since gone back to release 7.3 and routing works as > > > expected. > > > > > > Any input would be appreciated. > > > > Output from the following when the machine is running RELENG_8: > > > > - ifconfig -a > > - netstat -i > > - netstat -rn > > - sysctl -a | grep bge > > - Contents of /etc/rc.conf > > I forgot one more: > > dmesg | grep -C 10 bge1 > OK, will take a day or so as I'll be offline the next several hours while a tech from my ISP repairs some cables here. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
loader.conf problem
Gents, I recent build of FreeBSD8-STABLE (amd64)is not parsing /boot/loader.conf properly. While the machine boots I am getting the following error: > \ \: unknown command \ -- This is right before it loads the kernel. I was wondering if anyone else is running into such problems or knows which source files I can examine to see where the problem might be? A side effect of this is that my modules that I'd like to be loaded aren't being loaded. Thanks, -- Paul A. Procacci Manager, UNIX Support Services Datapipe Managed Global IT Services 1.201.792.4847 (international) 1.888.749.5821 (toll free) This message may contain confidential or privileged information. If you are not the intended recipient, please advise us immediately and delete this message. See http://www.datapipe.com/about-us-legal-email-disclaimer.htm for further information on confidentiality and the risks of non-secure electronic communication. If you cannot access these links, please notify us by reply message and we will send the contents to you. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: HP 380 G4 - ciss kernel page fault.
On Wed, 28 Apr 2010, John Baldwin wrote: > > Thank you both for looking in to it and making such a fast fix! > > > > Now Im off to upgrade to 8.0-STABLE if I find what to edit. Or if you want > > to send a patch. > > I've committed the smaller patch to HEAD to fix just the callout_init_mtx(). > I can MFC that fix and the other patch to fix the mutex that is already in > HEAD in a few days. Just a note that I also got 8.0-STABLE to boot with those changes. /Bjorn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: loader.conf problem
On Wed, Apr 28, 2010 at 04:26:13PM -0500, Paul A. Procacci wrote: > Gents, > > I recent build of FreeBSD8-STABLE (amd64)is not parsing /boot/loader.conf > properly. While the machine boots I am getting the following error: > > > \ > \: unknown command > \ > -- Please provide: - Contents of /boot/loader.conf - ls -l /boot Thanks. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: loader.conf problem
On Apr 28, 2010, at 2:26 PM, Paul A. Procacci wrote: > Gents, > > I recent build of FreeBSD8-STABLE (amd64)is not parsing /boot/loader.conf > properly. While the machine boots I am getting the following error: > >> \ > \: unknown command > \ > -- > > This is right before it loads the kernel. I was wondering if anyone else is > running into such problems or knows which source files I can examine to see > where the problem might be? > > A side effect of this is that my modules that I'd like to be loaded aren't > being loaded. > > Thanks, > -- > Paul A. Procacci > Manager, UNIX Support Services > Datapipe Managed Global IT Services > 1.201.792.4847 (international) > 1.888.749.5821 (toll free) > > This message may contain confidential or privileged information. If you are > not the intended recipient, please advise us immediately and delete this > message. See http://www.datapipe.com/about-us-legal-email-disclaimer.htm for > further information on confidentiality and the risks of non-secure electronic > communication. If you cannot access these links, please notify us by reply > message and we will send the contents to you. > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" When the system boot, go to the loader prompt. Type: unload Type: load /boot/kernel/kernel Then load in your modules in with the same process. Finally, type: boot You can then look at your loader.conf and diagnose any issue that might be in it, or file a bug if there is really something wrong. Hope this helps! > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: BCM5704 routing problem
On Wed, Apr 28, 2010 at 02:25:56PM -0400, Gardner Bell wrote: > I upgraded my gateway last week to RELENG_8 and noticed that I can no > longer forward or receive IP packets from hosts on internal LAN. When > trying to ping a host or the gateway IP itself, you get. > > # ping 192.168.1.10 > PING 192.168.1.10 (192.168.1.10): 56 data bytes > ^C If you're using ipfw, there's still some instability with it. Reconfirm your rule-load with "ipfw show" Cheers. -- Jonathan Chen -- Experience is a hard teacher because she gives the test first, the lesson afterwards ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: loader.conf problem
On Wed, Apr 28, 2010 at 06:05:24PM -0400, Jeremy Chadwick wrote: > On Wed, Apr 28, 2010 at 04:26:13PM -0500, Paul A. Procacci wrote: > > Gents, > > > > I recent build of FreeBSD8-STABLE (amd64)is not parsing /boot/loader.conf > > properly. While the machine boots I am getting the following error: > > > > > \ > > \: unknown command > > \ > > -- > > Please provide: > > - Contents of /boot/loader.conf > - ls -l /boot > > Thanks. > > -- > | Jeremy Chadwick j...@parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | > Something I should have provided. Sorry. %cat /boot/loader.conf geom_mirror_load="YES" %ls -l /boot/ total 748 -r--r--r-- 1 root wheel7643 Apr 28 15:54 beastie.4th -r--r--r-- 1 root wheel8192 Apr 28 15:54 boot -r--r--r-- 1 root wheel 512 Apr 28 15:54 boot0 -r--r--r-- 1 root wheel 512 Apr 28 15:54 boot0sio -r--r--r-- 1 root wheel 512 Apr 28 15:54 boot1 -r--r--r-- 1 root wheel7680 Apr 28 15:54 boot2 -r--r--r-- 1 root wheel1201 Apr 28 15:54 cdboot drwxr-xr-x 2 root wheel 512 Apr 28 15:54 defaults -r--r--r-- 1 root wheel 699 Apr 27 22:40 device.hints drwxr-xr-x 2 root wheel 512 Nov 21 08:29 firmware -r--r--r-- 1 root wheel2258 Apr 28 15:54 frames.4th -r--r--r-- 1 root wheel7535 Apr 28 15:54 gptboot -r--r--r-- 1 root wheel 25219 Nov 21 08:30 gptzfsboot drwxr-xr-x 2 root wheel 11776 Apr 28 15:53 kernel drwxr-xr-x 2 root wheel 11776 Apr 27 22:36 kernel.old -r-xr-xr-x 1 root wheel 184320 Apr 28 15:54 loader -r--r--r-- 1 root wheel5861 Apr 28 15:54 loader.4th -rw-r--r-- 1 root wheel 41 Apr 27 23:52 loader.conf -r--r--r-- 1 root wheel 15219 Apr 28 15:54 loader.help -r-xr-xr-x 1 root wheel 184320 Apr 27 22:38 loader.old -r--r--r-- 1 root wheel 396 Nov 21 08:30 loader.rc -r--r--r-- 1 root wheel 512 Apr 28 15:54 mbr drwxr-xr-x 2 root wheel 512 Apr 28 15:56 modules -r--r--r-- 1 root wheel 512 Apr 28 15:54 pmbr -r--r--r-- 1 root wheel 186368 Apr 28 15:54 pxeboot -r--r--r-- 1 root wheel 699 Apr 28 15:54 screen.4th -r--r--r-- 1 root wheel 35132 Apr 28 15:54 support.4th drwxr-xr-x 2 root wheel 512 Nov 21 08:29 zfs -r--r--r-- 1 root wheel 33280 Nov 21 08:30 zfsboot %md5 /boot/* MD5 (/boot/beastie.4th) = d7d88e7385f2eb456e2628ffb81dce5c MD5 (/boot/boot) = 91296cd94bc075de685318df2a4afc9f MD5 (/boot/boot0) = d5019f554b1a6649dd64e479b36ae90d MD5 (/boot/boot0sio) = 4f2616f956de41c0949f07ba234edfdb MD5 (/boot/boot1) = fe3c577c089ac9db8f31abaa081ea945 MD5 (/boot/boot2) = bc4e2df8bf72a7e3b70e34a800638097 MD5 (/boot/cdboot) = f2fe4225957001913769f3d1b247d5e4 MD5 (/boot/defaults) = 4553259374ff97e232e86f813c16a8b8 MD5 (/boot/device.hints) = 992bdbbdb069a4300384e3fe1eb92fd0 MD5 (/boot/firmware) = 09f25114d80dbd121f92ffc126f33e85 MD5 (/boot/frames.4th) = 7e9e14adeb0179c96dfc2e4de31687ce MD5 (/boot/gptboot) = 72e2bb50b09650320b25ec7a09f5b68e MD5 (/boot/gptzfsboot) = e5a49dd7837df4093d4c1051566fe7bf MD5 (/boot/kernel) = 13c4c3d256c2993ba9525fc34b98907e MD5 (/boot/kernel.old) = 0e73c4caf72fd22594339a6d814516a7 MD5 (/boot/loader) = e459148bffaca8e0fc2633759499d62d MD5 (/boot/loader.4th) = ef3d7bcf3a6f8fdeed3dee4eca86473e MD5 (/boot/loader.conf) = 098bd0fbe26459911454967ded77af16 MD5 (/boot/loader.help) = b553af5cf09e399b1ce850991ef386c4 MD5 (/boot/loader.old) = 845f8d0e5c9eec3b45ac76ce2c553620 MD5 (/boot/loader.rc) = 73e4ee17ce1f287f529211cd2cb6c170 MD5 (/boot/mbr) = db3f526667d01f5851ef3d0ddafb86db MD5 (/boot/modules) = fcf04f3c1546b550b3e12ba6d84750c5 MD5 (/boot/pmbr) = 6daee450f256507904e0aebe78187cf6 MD5 (/boot/pxeboot) = 4d75944d497e98a4a1f5bfe1719ee944 MD5 (/boot/screen.4th) = 47d16a951e9f88f52ff0811cdebeeb26 MD5 (/boot/support.4th) = 04feeb00e7f52a81744713365524e5cf MD5 (/boot/zfs) = 91bb58c037aae3afcadec85b553d MD5 (/boot/zfsboot) = 9232895a063604025059b5b42fddf0fc Thanks, -- Paul A. Procacci Manager, UNIX Support Services Datapipe Managed Global IT Services 1.201.792.4847 (international) 1.888.749.5821 (toll free) This message may contain confidential or privileged information. If you are not the intended recipient, please advise us immediately and delete this message. See http://www.datapipe.com/about-us-legal-email-disclaimer.htm for further information on confidentiality and the risks of non-secure electronic communication. If you cannot access these links, please notify us by reply message and we will send the contents to you. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: loader.conf problem
On Wed, Apr 28, 2010 at 07:00:10PM -0500, Paul A. Procacci wrote: > On Wed, Apr 28, 2010 at 06:05:24PM -0400, Jeremy Chadwick wrote: > > On Wed, Apr 28, 2010 at 04:26:13PM -0500, Paul A. Procacci wrote: > > > Gents, > > > > > > I recent build of FreeBSD8-STABLE (amd64)is not parsing /boot/loader.conf > > > properly. While the machine boots I am getting the following error: > > > > > > > \ > > > \: unknown command > > > \ > > > -- > > > > Please provide: > > > > - Contents of /boot/loader.conf > > - ls -l /boot > > > > Thanks. > > > > -- > > | Jeremy Chadwick j...@parodius.com | > > | Parodius Networking http://www.parodius.com/ | > > | UNIX Systems Administrator Mountain View, CA, USA | > > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > > > Something I should have provided. Sorry. > > %cat /boot/loader.conf > geom_mirror_load="YES" > > %ls -l /boot/ > total 748 > -r--r--r-- 1 root wheel7643 Apr 28 15:54 beastie.4th > -r--r--r-- 1 root wheel8192 Apr 28 15:54 boot > -r--r--r-- 1 root wheel 512 Apr 28 15:54 boot0 > -r--r--r-- 1 root wheel 512 Apr 28 15:54 boot0sio > -r--r--r-- 1 root wheel 512 Apr 28 15:54 boot1 > -r--r--r-- 1 root wheel7680 Apr 28 15:54 boot2 > -r--r--r-- 1 root wheel1201 Apr 28 15:54 cdboot > drwxr-xr-x 2 root wheel 512 Apr 28 15:54 defaults > -r--r--r-- 1 root wheel 699 Apr 27 22:40 device.hints > drwxr-xr-x 2 root wheel 512 Nov 21 08:29 firmware > -r--r--r-- 1 root wheel2258 Apr 28 15:54 frames.4th > -r--r--r-- 1 root wheel7535 Apr 28 15:54 gptboot > -r--r--r-- 1 root wheel 25219 Nov 21 08:30 gptzfsboot > drwxr-xr-x 2 root wheel 11776 Apr 28 15:53 kernel > drwxr-xr-x 2 root wheel 11776 Apr 27 22:36 kernel.old > -r-xr-xr-x 1 root wheel 184320 Apr 28 15:54 loader > -r--r--r-- 1 root wheel5861 Apr 28 15:54 loader.4th > -rw-r--r-- 1 root wheel 41 Apr 27 23:52 loader.conf > -r--r--r-- 1 root wheel 15219 Apr 28 15:54 loader.help > -r-xr-xr-x 1 root wheel 184320 Apr 27 22:38 loader.old > -r--r--r-- 1 root wheel 396 Nov 21 08:30 loader.rc > -r--r--r-- 1 root wheel 512 Apr 28 15:54 mbr > drwxr-xr-x 2 root wheel 512 Apr 28 15:56 modules > -r--r--r-- 1 root wheel 512 Apr 28 15:54 pmbr > -r--r--r-- 1 root wheel 186368 Apr 28 15:54 pxeboot > -r--r--r-- 1 root wheel 699 Apr 28 15:54 screen.4th > -r--r--r-- 1 root wheel 35132 Apr 28 15:54 support.4th > drwxr-xr-x 2 root wheel 512 Nov 21 08:29 zfs > -r--r--r-- 1 root wheel 33280 Nov 21 08:30 zfsboot > > %md5 /boot/* > MD5 (/boot/beastie.4th) = d7d88e7385f2eb456e2628ffb81dce5c > MD5 (/boot/boot) = 91296cd94bc075de685318df2a4afc9f > MD5 (/boot/boot0) = d5019f554b1a6649dd64e479b36ae90d > MD5 (/boot/boot0sio) = 4f2616f956de41c0949f07ba234edfdb > MD5 (/boot/boot1) = fe3c577c089ac9db8f31abaa081ea945 > MD5 (/boot/boot2) = bc4e2df8bf72a7e3b70e34a800638097 > MD5 (/boot/cdboot) = f2fe4225957001913769f3d1b247d5e4 > MD5 (/boot/defaults) = 4553259374ff97e232e86f813c16a8b8 > MD5 (/boot/device.hints) = 992bdbbdb069a4300384e3fe1eb92fd0 > MD5 (/boot/firmware) = 09f25114d80dbd121f92ffc126f33e85 > MD5 (/boot/frames.4th) = 7e9e14adeb0179c96dfc2e4de31687ce > MD5 (/boot/gptboot) = 72e2bb50b09650320b25ec7a09f5b68e > MD5 (/boot/gptzfsboot) = e5a49dd7837df4093d4c1051566fe7bf > MD5 (/boot/kernel) = 13c4c3d256c2993ba9525fc34b98907e > MD5 (/boot/kernel.old) = 0e73c4caf72fd22594339a6d814516a7 > MD5 (/boot/loader) = e459148bffaca8e0fc2633759499d62d > MD5 (/boot/loader.4th) = ef3d7bcf3a6f8fdeed3dee4eca86473e > MD5 (/boot/loader.conf) = 098bd0fbe26459911454967ded77af16 > MD5 (/boot/loader.help) = b553af5cf09e399b1ce850991ef386c4 > MD5 (/boot/loader.old) = 845f8d0e5c9eec3b45ac76ce2c553620 > MD5 (/boot/loader.rc) = 73e4ee17ce1f287f529211cd2cb6c170 > MD5 (/boot/mbr) = db3f526667d01f5851ef3d0ddafb86db > MD5 (/boot/modules) = fcf04f3c1546b550b3e12ba6d84750c5 > MD5 (/boot/pmbr) = 6daee450f256507904e0aebe78187cf6 > MD5 (/boot/pxeboot) = 4d75944d497e98a4a1f5bfe1719ee944 > MD5 (/boot/screen.4th) = 47d16a951e9f88f52ff0811cdebeeb26 > MD5 (/boot/support.4th) = 04feeb00e7f52a81744713365524e5cf > MD5 (/boot/zfs) = 91bb58c037aae3afcadec85b553d > MD5 (/boot/zfsboot) = 9232895a063604025059b5b42fddf0fc Can you provide the following output please (not a typo): hd /boot/loader.conf Thanks. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: loader.conf problem
On Wed, Apr 28, 2010 at 10:07:27PM -0400, Jeremy Chadwick wrote: > On Wed, Apr 28, 2010 at 07:00:10PM -0500, Paul A. Procacci wrote: > > On Wed, Apr 28, 2010 at 06:05:24PM -0400, Jeremy Chadwick wrote: > > > On Wed, Apr 28, 2010 at 04:26:13PM -0500, Paul A. Procacci wrote: > > > > Gents, > > > > > > > > I recent build of FreeBSD8-STABLE (amd64)is not parsing > > > > /boot/loader.conf > > > > properly. While the machine boots I am getting the following error: > > > > > > > > > \ > > > > \: unknown command > > > > \ > > > > -- > > > > > > Please provide: > > > > > > - Contents of /boot/loader.conf > > > - ls -l /boot > > > > > > Thanks. > > > > > > -- > > > | Jeremy Chadwick j...@parodius.com | > > > | Parodius Networking http://www.parodius.com/ | > > > | UNIX Systems Administrator Mountain View, CA, USA | > > > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > > > > > > Something I should have provided. Sorry. > > > > %cat /boot/loader.conf > > geom_mirror_load="YES" > > > > %ls -l /boot/ > > total 748 > > -r--r--r-- 1 root wheel7643 Apr 28 15:54 beastie.4th > > -r--r--r-- 1 root wheel8192 Apr 28 15:54 boot > > -r--r--r-- 1 root wheel 512 Apr 28 15:54 boot0 > > -r--r--r-- 1 root wheel 512 Apr 28 15:54 boot0sio > > -r--r--r-- 1 root wheel 512 Apr 28 15:54 boot1 > > -r--r--r-- 1 root wheel7680 Apr 28 15:54 boot2 > > -r--r--r-- 1 root wheel1201 Apr 28 15:54 cdboot > > drwxr-xr-x 2 root wheel 512 Apr 28 15:54 defaults > > -r--r--r-- 1 root wheel 699 Apr 27 22:40 device.hints > > drwxr-xr-x 2 root wheel 512 Nov 21 08:29 firmware > > -r--r--r-- 1 root wheel2258 Apr 28 15:54 frames.4th > > -r--r--r-- 1 root wheel7535 Apr 28 15:54 gptboot > > -r--r--r-- 1 root wheel 25219 Nov 21 08:30 gptzfsboot > > drwxr-xr-x 2 root wheel 11776 Apr 28 15:53 kernel > > drwxr-xr-x 2 root wheel 11776 Apr 27 22:36 kernel.old > > -r-xr-xr-x 1 root wheel 184320 Apr 28 15:54 loader > > -r--r--r-- 1 root wheel5861 Apr 28 15:54 loader.4th > > -rw-r--r-- 1 root wheel 41 Apr 27 23:52 loader.conf > > -r--r--r-- 1 root wheel 15219 Apr 28 15:54 loader.help > > -r-xr-xr-x 1 root wheel 184320 Apr 27 22:38 loader.old > > -r--r--r-- 1 root wheel 396 Nov 21 08:30 loader.rc > > -r--r--r-- 1 root wheel 512 Apr 28 15:54 mbr > > drwxr-xr-x 2 root wheel 512 Apr 28 15:56 modules > > -r--r--r-- 1 root wheel 512 Apr 28 15:54 pmbr > > -r--r--r-- 1 root wheel 186368 Apr 28 15:54 pxeboot > > -r--r--r-- 1 root wheel 699 Apr 28 15:54 screen.4th > > -r--r--r-- 1 root wheel 35132 Apr 28 15:54 support.4th > > drwxr-xr-x 2 root wheel 512 Nov 21 08:29 zfs > > -r--r--r-- 1 root wheel 33280 Nov 21 08:30 zfsboot > > > > %md5 /boot/* > > MD5 (/boot/beastie.4th) = d7d88e7385f2eb456e2628ffb81dce5c > > MD5 (/boot/boot) = 91296cd94bc075de685318df2a4afc9f > > MD5 (/boot/boot0) = d5019f554b1a6649dd64e479b36ae90d > > MD5 (/boot/boot0sio) = 4f2616f956de41c0949f07ba234edfdb > > MD5 (/boot/boot1) = fe3c577c089ac9db8f31abaa081ea945 > > MD5 (/boot/boot2) = bc4e2df8bf72a7e3b70e34a800638097 > > MD5 (/boot/cdboot) = f2fe4225957001913769f3d1b247d5e4 > > MD5 (/boot/defaults) = 4553259374ff97e232e86f813c16a8b8 > > MD5 (/boot/device.hints) = 992bdbbdb069a4300384e3fe1eb92fd0 > > MD5 (/boot/firmware) = 09f25114d80dbd121f92ffc126f33e85 > > MD5 (/boot/frames.4th) = 7e9e14adeb0179c96dfc2e4de31687ce > > MD5 (/boot/gptboot) = 72e2bb50b09650320b25ec7a09f5b68e > > MD5 (/boot/gptzfsboot) = e5a49dd7837df4093d4c1051566fe7bf > > MD5 (/boot/kernel) = 13c4c3d256c2993ba9525fc34b98907e > > MD5 (/boot/kernel.old) = 0e73c4caf72fd22594339a6d814516a7 > > MD5 (/boot/loader) = e459148bffaca8e0fc2633759499d62d > > MD5 (/boot/loader.4th) = ef3d7bcf3a6f8fdeed3dee4eca86473e > > MD5 (/boot/loader.conf) = 098bd0fbe26459911454967ded77af16 > > MD5 (/boot/loader.help) = b553af5cf09e399b1ce850991ef386c4 > > MD5 (/boot/loader.old) = 845f8d0e5c9eec3b45ac76ce2c553620 > > MD5 (/boot/loader.rc) = 73e4ee17ce1f287f529211cd2cb6c170 > > MD5 (/boot/mbr) = db3f526667d01f5851ef3d0ddafb86db > > MD5 (/boot/modules) = fcf04f3c1546b550b3e12ba6d84750c5 > > MD5 (/boot/pmbr) = 6daee450f256507904e0aebe78187cf6 > > MD5 (/boot/pxeboot) = 4d75944d497e98a4a1f5bfe1719ee944 > > MD5 (/boot/screen.4th) = 47d16a951e9f88f52ff0811cdebeeb26 > > MD5 (/boot/support.4th) = 04feeb00e7f52a81744713365524e5cf > > MD5 (/boot/zfs) = 91bb58c037aae3afcadec85b553d > > MD5 (/boot/zfsboot) = 9232895a063604025059b5b42fddf0fc > > Can you provide the following output please (not a typo): > > hd /boot/loader.conf > I just solved my problem. Apparently someone *points to self* included an option in src.conf by mistake: %fgrep FORTH /etc/src.conf WITHOUT_FORTH=true I assume this was the root of the problem as I now have no problems with the initially reported error message. This has been a waste of bits, and I ap
Re: HP 380 G4 - ciss kernel page fault.
On Wed, Apr 28, 2010 at 6:06 PM, kama wrote: > > > On Wed, 28 Apr 2010, Giovanni Trematerra wrote: > >> On Wed, Apr 28, 2010 at 5:41 PM, Giovanni Trematerra >> wrote: >> > On Wed, Apr 28, 2010 at 4:07 PM, kama wrote: >> >> >> >> >> >> On Wed, 28 Apr 2010, John Baldwin wrote: >> >> >> >>> On Wednesday 28 April 2010 3:22:44 am kama wrote: >> >>> > >> >>> > On Tue, 27 Apr 2010, John Baldwin wrote: >> >>> > >> >>> > > On Tuesday 27 April 2010 9:30:12 am kama wrote: >> >>> > > > >> >>> > > > Hi. >> >>> > > > >> >>> > > > I have problem when probing the ciss device. Causing a kernel >> >>> > > > panic. >> >>> This >> >>> > > > happened when I upgraded from 6.3 to 7.3-stable. Booting the old >> >>> > > > kernel >> >>> > > > works. So something has changed. I am also getting the error on >> >>> > > > both the >> >>> > > > 7.3 and the 8.0 install cd's. >> >>> > > > >> >>> > > > The ciss that causing the problem is a Smart Array 6404 and its the >> >>> addon >> >>> > > > card that it faults at. The server disconnect it due to an error. >> >>> > > > But >> >>> > > > since it works on 6.3 it is something that have changed. FreeBSD >> >>> > > > should >> >>> > > > not panic, it should just disable it. >> >>> > > > >> >>> > > > Also I tried to disable the card in the BIOS, but FreeBSD try to >> >>> > > > probe >> >>> it >> >>> > > > anyway and panic. >> >>> > > > >> >>> > > > This whats comes up on a verbose boot through the ILO remote >> >>> > > > console. >> >>> > > > (typed in manually from a screenshot) >> >>> > > > >> >>> > > > ciss2: port 0x6400-0x64ff mem >> >>> > > > 0xfdf7-0xfdf71fff irq 98 at device 5.0 on pcill >> >>> > > > ciss2: Reserved 0x2000 bytes for rid 0x10 type 3 at 0xfdf7 >> >>> > > > pci11: child ciss2 requested type 3 for rid 0, but the BAR says it >> >>> > > > is an >> >>> > > > ioport >> >>> > > > ciss2: can't allocate config window >> >>> > > > kernel trap 12 with interupts disabled >> >>> > > >> >>> > > Can you get the ciss2 boot messages from a working 6.x kernel? >> >>> > >> >>> > This is the verbose boot on 6.3. >> >>> > >> >>> > FreeBSD 6.3-STABLE #3: Thu Mar 6 14:29:33 CET 2008 >> >>> > >> >>> > ciss1: 10 physical devices >> >>> > ciss1: 4 logical drives >> >>> > ciss1: logical drive (b0t0): RAID 1, 69120MB online >> >>> > ciss1: logical drive (b0t1): RAID 1, 69120MB online >> >>> > ciss1: logical drive (b0t2): RAID 1, 139776MB online >> >>> > ciss1: logical drive (b0t3): RAID 1, 139776MB online >> >>> > >> >>> > ciss2: port 0x6400-0x64ff mem >> >>> > 0xfdf7-0xfdf71fff,0xfdf0-0xfdf3 irq 98 at device 5.0 on >> >>> > pci11 >> >>> > ciss2: Reserved 0x2000 bytes for rid 0x10 type 3 at 0xfdf7 >> >>> > pci11: child ciss2 requested type 3 for rid 0, but the BAR says it is >> >>> > an >> >>> > ioport >> >>> > ciss2: can't allocate config window >> >>> > device_attach: ciss2 attach returned 6 >> >>> >> >>> Oh, so it didn't work in 6.x either, it just handles failure less >> >>> gracefully >> >>> in 7.0+? >> >> >> >> No, ciss2 is disabled. The difference is that 6.x continue to boot instead >> >> of a kernel panic as in 7.x and 8.x. >> >> >> >> I dont have any disks attached to ciss2, so I dont really need it. But >> >> ciss1 and ciss2 is on the same physical card, so I cant just remove it. >> >> >> > >> > Could you try this one if you are looking for a patch to 7-STABLE. >> > >> > Thank you >> > >> >> [snip patch] >> >> I think it's worth to have >> >> mtx_assert(&sc->ciss_mtx, MA_OWNED); >> >> in ciss_free just to be on safe side. > > Where in ciss_free()? at begin. but that is only a seat belt for further development and is no needed to resolve your issue. -- Gianni ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
