Re: Badness in device_release at drivers/base/core.c:84

Re: Badness in device_release at drivers/base/core.c:84

[Andrew Morton]

Diffie <diffie@blazebox.homeip.net> wrote:
>
> Unable to handle kernel NULL pointer dereference at virtual address 00000120
> printing eip:
> c02a8cae
> *pde = 00000000
> Oops: 0000 [#1]
> PREEMPT
> CPU:    0
> EIP:    0060:[<c02a8cae>]    Not tainted VLI
> EFLAGS: 00210286
> EIP is at aic7xxx_proc_info+0x2e/0xc80
> eax: c1bb25b0   ebx: c1bb2400   ecx: c038bb20   edx: 00000000
> esi: 00000400   edi: f1715000   ebp: 412de000   esp: f620fecc
> ds: 007b   es: 007b   ss: 0068
> Process nautilus (pid: 3555, threadinfo=f620e000 task=f6216720)
> Stack: 000001f7 00000000 00000000 c013c612 c0379eb0 00000000 00000000 f6613340
>        00000000 00000000 c0379eb0 00000400 00000400 f1715000 412de000 c02956fc
>        c1bb2400 f1715000 f620ff60 00000000 00000400 00000000 c02956c0 c018bc91
> Call Trace:
> [<c013c612>] __alloc_pages+0x92/0x320
> [<c02956fc>] proc_scsi_read+0x3c/0x60
> [<c02956c0>] proc_scsi_read+0x0/0x60

This patch should fix the oops.

As for why the proc reading code was unable to locate the HBA: dunno, but
this is a first step.

Or maybe you don't have any adaptec controllers in the machine?

(jejb, please apply..)


 25-akpm/drivers/scsi/aic7xxx_old/aic7xxx_proc.c |    2 +-
 1 files changed, 1 insertion(+), 1 deletion(-)

diff -puN drivers/scsi/aic7xxx_old/aic7xxx_proc.c~aic7xxx_old-oops-fix drivers/scsi/aic7xxx_old/aic7xxx_proc.c
--- 25/drivers/scsi/aic7xxx_old/aic7xxx_proc.c~aic7xxx_old-oops-fix	Fri Aug  1 14:41:14 2003
+++ 25-akpm/drivers/scsi/aic7xxx_old/aic7xxx_proc.c	Fri Aug  1 14:41:20 2003
@@ -92,7 +92,7 @@ aic7xxx_proc_info ( struct Scsi_Host *HB
 
   HBAptr = NULL;
 
-  for(p=first_aic7xxx; p->host != HBAptr; p=p->next)
+  for(p=first_aic7xxx; p && p->host != HBAptr; p=p->next)
     ;
 
   if (!p)

_

Re: Badness in device_release at drivers/base/core.c:84

[Mike Anderson]

Andrew Morton [akpm@osdl.org] wrote:
> This patch should fix the oops.
> 
> As for why the proc reading code was unable to locate the HBA: dunno, but
> this is a first step.
> 
> Or maybe you don't have any adaptec controllers in the machine?
> 
> (jejb, please apply..)
> 
> 
>  25-akpm/drivers/scsi/aic7xxx_old/aic7xxx_proc.c |    2 +-
>  1 files changed, 1 insertion(+), 1 deletion(-)
> 
> diff -puN drivers/scsi/aic7xxx_old/aic7xxx_proc.c~aic7xxx_old-oops-fix drivers/scsi/aic7xxx_old/aic7xxx_proc.c
> --- 25/drivers/scsi/aic7xxx_old/aic7xxx_proc.c~aic7xxx_old-oops-fix	Fri Aug  1 14:41:14 2003
> +++ 25-akpm/drivers/scsi/aic7xxx_old/aic7xxx_proc.c	Fri Aug  1 14:41:20 2003
> @@ -92,7 +92,7 @@ aic7xxx_proc_info ( struct Scsi_Host *HB
>  
>    HBAptr = NULL;
>  
> -  for(p=first_aic7xxx; p->host != HBAptr; p=p->next)
> +  for(p=first_aic7xxx; p && p->host != HBAptr; p=p->next)
>      ;
>  
>    if (!p)

Is this really the right thing to add. The only purpose of these few lines
is a poor sanity check as down further in the code a pointer to the
structure is already present in hostdata. 

Adding the "p" is an indication that this drivers list got corrupted some
where.

I agree it may be better than an oops, but what else is invalid?

You need to have adaptec controllers in the system to get a procfs node
to read / write, but this error could be related to the node not getting
cleaned up correctly on a remove which a patch has previously been
posted.

-andmike
--
Michael Anderson
andmike@us.ibm.com

Re: Badness in device_release at drivers/base/core.c:84

[Andrew Morton]

Diffie <diffie@blazebox.homeip.net> wrote:
>
> After applaying the above patch and testing it still oopses the kernel.
> 
> I noticed same patch in today's mm3 which i compiled and use right now.
> 
> When using cat /proc/scsi/aic7xxx/0 i get segmentation fault and oops
> which i'll attach to this email.
>
> ...
>
>  EIP is at aic7xxx_proc_info+0xc28/0xc80

This is crashing in a different place.  Probably the same bug, showing up
later on.

I don't know if anyone is maintaining aic7xxx_old in 2.7.  It looks like it
was subject to some random untested change a couple of months back.

Re: Badness in device_release at drivers/base/core.c:84

[Diffie]

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

On Sat, Aug 02, 2003 at 07:07:37PM -0700, Andrew Morton wrote:
> Diffie <diffie@blazebox.homeip.net> wrote:
> >
> > After applaying the above patch and testing it still oopses the kernel.
> > 
> > I noticed same patch in today's mm3 which i compiled and use right now.
> > 
> > When using cat /proc/scsi/aic7xxx/0 i get segmentation fault and oops
> > which i'll attach to this email.
> >
> > ...
> >
> >  EIP is at aic7xxx_proc_info+0xc28/0xc80
> 
> This is crashing in a different place.  Probably the same bug, showing up
> later on.
> 
> I don't know if anyone is maintaining aic7xxx_old in 2.7.  It looks like it
> was subject to some random untested change a couple of months back.
> 
> 
> 

Hi Andrew,

I think this bug is due to me using the aic7xxx_old code ver 5.x.x.

Under kernel 2.4.21 the aic7xxx (new) is ver 6.2.8 and it works great
with Adaptec AHA-2940U2W controller i have.

On 2.6.0-test2-mm3 (tried Linus test1,test2,mm1 and mm2) the NEW aic7xxx
uses ver 6.2.35 and will not scan my IBM drive even though it
initializes the correct SCSI ID,LUN etc...

I would like to contact and report this issue to the aic7xxx maintaner
and perhaps get it resolved.Where would be the best place to report this
kind of problem?

I have taken few screen captures which are available at:
http://www.blazebox.homeip.net:81/diffie/images/2.6.0-test2/ and show
the aic7xxx (new) failure.


Regards,

Paul B.


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: Badness in device_release at drivers/base/core.c:84

[Andrew Morton]

Diffie <diffie@blazebox.homeip.net> wrote:
>
> I think this bug is due to me using the aic7xxx_old code ver 5.x.x.
> 
>  Under kernel 2.4.21 the aic7xxx (new) is ver 6.2.8 and it works great
>  with Adaptec AHA-2940U2W controller i have.
> 
>  On 2.6.0-test2-mm3 (tried Linus test1,test2,mm1 and mm2) the NEW aic7xxx
>  uses ver 6.2.35 and will not scan my IBM drive even though it
>  initializes the correct SCSI ID,LUN etc...
> 
>  I would like to contact and report this issue to the aic7xxx maintaner
>  and perhaps get it resolved.Where would be the best place to report this
>  kind of problem?
> 
>  I have taken few screen captures which are available at:
>  http://www.blazebox.homeip.net:81/diffie/images/2.6.0-test2/ and show
>  the aic7xxx (new) failure.

An appropriate way to report this would be to email Justin (CC'ed here)
and linux-scsi@vger.kernel.org.

Re: Badness in device_release at drivers/base/core.c:84

[Diffie]

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

On Sun, Aug 03, 2003 at 02:52:11PM -0700, Andrew Morton wrote:
> Diffie <diffie@blazebox.homeip.net> wrote:
> >
> > I think this bug is due to me using the aic7xxx_old code ver 5.x.x.
> > 
> >  Under kernel 2.4.21 the aic7xxx (new) is ver 6.2.8 and it works great
> >  with Adaptec AHA-2940U2W controller i have.
> > 
> >  On 2.6.0-test2-mm3 (tried Linus test1,test2,mm1 and mm2) the NEW aic7xxx
> >  uses ver 6.2.35 and will not scan my IBM drive even though it
> >  initializes the correct SCSI ID,LUN etc...
> > 
> >  I would like to contact and report this issue to the aic7xxx maintaner
> >  and perhaps get it resolved.Where would be the best place to report this
> >  kind of problem?
> > 
> >  I have taken few screen captures which are available at:
> >  http://www.blazebox.homeip.net:81/diffie/images/2.6.0-test2/ and show
> >  the aic7xxx (new) failure.
> 
> An appropriate way to report this would be to email Justin (CC'ed here)
> and linux-scsi@vger.kernel.org.
> 
> 

Andrew,

Thank you for all your help.Sorry but i gave the wrong URL in previous
email.The correct one is http://www.blazebox.homeip.net:81/diffie/images/linux-2.6.0-test2/ 

Attached is the dmesg,lspci and aic7xxx /proc information from 2.4.21
kernel.

Regards,

Paul B.


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: Badness in device_release at drivers/base/core.c:84

[Diffie]

[-- Attachment #1.1: Type: text/plain, Size: 1481 bytes --]

On Sun, Aug 03, 2003 at 06:23:13PM -0400, Diffie wrote:
> On Sun, Aug 03, 2003 at 02:52:11PM -0700, Andrew Morton wrote:
> > Diffie <diffie@blazebox.homeip.net> wrote:
> > >
> > > I think this bug is due to me using the aic7xxx_old code ver 5.x.x.
> > > 
> > >  Under kernel 2.4.21 the aic7xxx (new) is ver 6.2.8 and it works great
> > >  with Adaptec AHA-2940U2W controller i have.
> > > 
> > >  On 2.6.0-test2-mm3 (tried Linus test1,test2,mm1 and mm2) the NEW aic7xxx
> > >  uses ver 6.2.35 and will not scan my IBM drive even though it
> > >  initializes the correct SCSI ID,LUN etc...
> > > 
> > >  I would like to contact and report this issue to the aic7xxx maintaner
> > >  and perhaps get it resolved.Where would be the best place to report this
> > >  kind of problem?
> > > 
> > >  I have taken few screen captures which are available at:
> > >  http://www.blazebox.homeip.net:81/diffie/images/2.6.0-test2/ and show
> > >  the aic7xxx (new) failure.
> > 
> > An appropriate way to report this would be to email Justin (CC'ed here)
> > and linux-scsi@vger.kernel.org.
> > 
> > 
> 
> Andrew,
> 
> Thank you for all your help.Sorry but i gave the wrong URL in previous
> email.The correct one is http://www.blazebox.homeip.net:81/diffie/images/linux-2.6.0-test2/ 
> 
> Attached is the dmesg,lspci and aic7xxx /proc information from 2.4.21
> kernel.
> 
> Regards,
> 
> Paul B.
> 

I am sorry again for not including the attachement.


[-- Attachment #1.2: dmesg-2.4.txt --]
[-- Type: text/plain, Size: 14726 bytes --]

Linux version 2.4.21-xfs (root@blaze.homeip.net) (gcc version 3.2.2) #1 Mon Jun 30 10:29:27 EDT 2003
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 000000003fff0000 (usable)
 BIOS-e820: 000000003fff0000 - 000000003fff3000 (ACPI NVS)
 BIOS-e820: 000000003fff3000 - 0000000040000000 (ACPI data)
 BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
 BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
 BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
127MB HIGHMEM available.
896MB LOWMEM available.
ACPI: have wakeup address 0xc0001000
found SMP MP-table at 000f52c0
hm, page 000f5000 reserved twice.
hm, page 000f6000 reserved twice.
hm, page 000f0000 reserved twice.
hm, page 000f1000 reserved twice.
On node 0 totalpages: 262128
zone(0): 4096 pages.
zone(1): 225280 pages.
zone(2): 32752 pages.
Intel MultiProcessor Specification v1.4
    Virtual Wire compatibility mode.
OEM ID: OEM00000 Product ID: PROD00000000 APIC at: 0xFEE00000
Processor #0 Pentium(tm) Pro APIC version 17
I/O APIC #2 Version 17 at 0xFEC00000.
Enabling APIC mode: Flat.	Using 1 I/O APICs
Processors: 1
Kernel command line: BOOT_IMAGE=Slackware-2.4 ro root=803 rootflags=quota acpi=off
Initializing CPU#0
Detected 2204.995 MHz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 4404.01 BogoMIPS
Memory: 1032968k/1048512k available (1930k kernel code, 15156k reserved, 347k data, 284k init, 131008k highmem)
Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
Inode cache hash table entries: 65536 (order: 7, 524288 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer-cache hash table entries: 65536 (order: 6, 262144 bytes)
Page-cache hash table entries: 262144 (order: 8, 1048576 bytes)
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU:     After generic, caps: 0383fbff c1c3fbff 00000000 00000000
CPU:             Common caps: 0383fbff c1c3fbff 00000000 00000000
CPU: AMD Athlon(tm) XP 3200+ stepping 00
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
enabled ExtINT on CPU#0
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
Using local APIC timer interrupts.
calibrating APIC timer ...
..... CPU clock speed is 2205.0712 MHz.
..... host bus clock speed is 400.9219 MHz.
cpu: 0, clocks: 4009219, slice: 2004609
CPU0<T0:4009216,T1:2004592,D:15,S:2004609,C:4009219>
mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
mtrr: detected mtrr type: Intel
ACPI: Subsystem revision 20030619
ACPI: Disabled via command line (acpi=off)
PCI: PCI BIOS revision 2.10 entry at 0xfad30, last bus=3
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: ACPI tables contain no PCI IRQ routing entries
PCI: Probing PCI hardware (bus 00)
PCI: Discovered primary peer bus 02 [IRQ]
PCI: Using IRQ router default [10de/01e0] at 00:00.0
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
allocated 32 pages and 32 bhs reserved for the highmem bounces
VFS: Disk quotas vdquot_6.5.1
devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x0
SGI-XFS CVS-2003-06-14_05:00_UTC with ACLs, no debug enabled
SGI XFS Quota Management subsystem
pty: 512 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
Floppy drive(s): fd0 is 1.44M
spurious 8259A interrupt: IRQ7.
keyboard: Timeout - AT keyboard not present?(00)
FDC 0 is a post-1991 82077
RAMDISK driver initialized: 16 RAM disks of 7777K size 1024 blocksize
loop: loaded (max 8 devices)
Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
NFORCE2: IDE controller at PCI slot 00:09.0
NFORCE2: chipset revision 162
NFORCE2: not 100% native mode: will probe irqs later
AMD_IDE: Bios didn't set cable bits corectly. Enabling workaround.
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
AMD_IDE: PCI device 10de:0065 (nVidia Corporation) (rev a2) UDMA100 controller on pci00:09.0
    ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
    ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
hda: IBM-DJNA-372200, ATA DISK drive
blk: queue c03b01c0, I/O limit 4095Mb (mask 0xffffffff)
hdc: IOMEGA ZIP 100 ATAPI, ATAPI FLOPPY drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: attached ide-disk driver.
hda: host protected area => 1
hda: 44150400 sectors (22605 MB) w/1966KiB Cache, CHS=2920/240/63
Partition check:
 /dev/ide/host0/bus0/target0/lun0: p1
 hdc:end_request: I/O error, dev 16:00 (hdc), sector 0
end_request: I/O error, dev 16:00 (hdc), sector 2
end_request: I/O error, dev 16:00 (hdc), sector 4
end_request: I/O error, dev 16:00 (hdc), sector 6
end_request: I/O error, dev 16:00 (hdc), sector 0
end_request: I/O error, dev 16:00 (hdc), sector 2
end_request: I/O error, dev 16:00 (hdc), sector 4
end_request: I/O error, dev 16:00 (hdc), sector 6
ldm_validate_partition_table(): Disk read failed.
end_request: I/O error, dev 16:00 (hdc), sector 0
end_request: I/O error, dev 16:00 (hdc), sector 2
end_request: I/O error, dev 16:00 (hdc), sector 4
end_request: I/O error, dev 16:00 (hdc), sector 6
 unable to read partition table
SCSI subsystem driver Revision: 1.00
scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.8
        <Adaptec 2940 Ultra2 SCSI adapter>
        aic7890/91: Ultra2 Wide Channel A, SCSI Id=7, 32/253 SCBs

blk: queue f7eca494, I/O limit 4095Mb (mask 0xffffffff)
  Vendor: IBM       Model: DDYS-T36950N      Rev: S80D
  Type:   Direct-Access                      ANSI SCSI revision: 03
blk: queue f7eca594, I/O limit 4095Mb (mask 0xffffffff)
  Vendor: PLEXTOR   Model: CD-ROM PX-40TW    Rev: 1.05
  Type:   CD-ROM                             ANSI SCSI revision: 02
blk: queue f7eca694, I/O limit 4095Mb (mask 0xffffffff)
  Vendor: PLEXTOR   Model: CD-R   PX-W1210S  Rev: 1.06
  Type:   CD-ROM                             ANSI SCSI revision: 02
blk: queue f7eca794, I/O limit 4095Mb (mask 0xffffffff)
scsi0:A:0:0: Tagged Queuing enabled.  Depth 8
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
(scsi0:A:0): 80.000MB/s transfers (40.000MHz, offset 63, 16bit)
SCSI device sda: 71687340 512-byte hdwr sectors (36704 MB)
 /dev/scsi/host0/bus0/target0/lun0: p1 p2 p3 p4 < p5 p6 p7 p8 p9 p10 >
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 8192 buckets, 64Kbytes
TCP: Hash tables configured (established 262144 bind 65536)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
XFS mounting filesystem sd(8,3)
Ending clean XFS mount for filesystem: sd(8,3)
VFS: Mounted root (xfs filesystem) readonly.
Freeing unused kernel memory: 284k freed
Adding Swap: 248968k swap-space (priority -1)
XFS mounting filesystem sd(8,1)
Ending clean XFS mount for filesystem: sd(8,1)
NTFS driver v1.1.22 [Flags: R/O MODULE]
NTFS: Warning! NTFS volume version is Win2k+: Mounting read-only
XFS mounting filesystem sd(8,5)
Ending clean XFS mount for filesystem: sd(8,5)
XFS mounting filesystem sd(8,6)
Ending clean XFS mount for filesystem: sd(8,6)
XFS mounting filesystem sd(8,7)
Ending clean XFS mount for filesystem: sd(8,7)
XFS mounting filesystem sd(8,8)
Ending clean XFS mount for filesystem: sd(8,8)
XFS mounting filesystem sd(8,9)
Ending clean XFS mount for filesystem: sd(8,9)
XFS mounting filesystem ide0(3,1)
Ending clean XFS mount for filesystem: ide0(3,1)
Real Time Clock Driver v1.10e
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
PCI: Setting latency timer of device 00:02.0 to 64
usb-ohci.c: USB OHCI at membase 0xf8850000, IRQ 11
usb-ohci.c: usb-00:02.0, PCI device 10de:0067 (nVidia Corporation)
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 3 ports detected
PCI: Setting latency timer of device 00:02.1 to 64
usb-ohci.c: USB OHCI at membase 0xf8852000, IRQ 9
usb-ohci.c: usb-00:02.1, PCI device 10de:0067 (nVidia Corporation)
usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
hub.c: 3 ports detected
usb.c: registered new driver hiddev
usb.c: registered new driver hid
hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik <vojtech@suse.cz>
hid-core.c: USB HID support drivers
mice: PS/2 mouse device common for all mice
Intel(R) PRO/1000 Network Driver - version 5.0.43-k1
Copyright (c) 1999-2003 Intel Corporation.
eth0: Intel(R) PRO/1000 Network Connection
hub.c: new USB device 00:02.0-1, assigned address 2
hub.c: USB hub found
hub.c: 3 ports detected
hub.c: new USB device 00:02.0-2, assigned address 3
input0: USB HID v1.10 Mouse [Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)] on usb1:3.0
hub.c: new USB device 00:02.0-1.1, assigned address 4
input1: USB HID v1.10 Keyboard [045e:001d] on usb1:4.0
input2: USB HID v1.10 Pointer [045e:001d] on usb1:4.1
e1000: eth0 NIC Link is Up 100 Mbps Full Duplex
ohci1394: $Rev: 896 $ Ben Collins <bcollins@debian.org>
PCI: Setting latency timer of device 00:0d.0 to 64
ohci1394_0: OHCI-1394 1.1 (PCI): IRQ=[11]  MMIO=[ce084000-ce0847ff]  Max Packet=[2048]
ohci1394_0: SelfID received outside of bus reset sequence
hub.c: new USB device 00:02.1-1, assigned address 2
Intel 810 + AC97 Audio, version 0.24, 10:34:08 Jun 30 2003
PCI: Setting latency timer of device 00:06.0 to 64
i810: NVIDIA nForce Audio found at IO 0xd000 and 0xe400, MEM 0x0000 and 0x0000, IRQ 5
usb.c: USB device 2 (vend/prod 0x46d/0x840) is not claimed by any active driver.
ieee1394: Host added: Node[00:1023]  GUID[8a1cc7ffff0020ed]  [Linux OHCI-1394]
i810_audio: Audio Controller supports 6 channels.
i810_audio: Defaulting to base 2 channel mode.
i810_audio: Resetting connection 0
ac97_codec: AC97 Audio codec, id: ALG32 (ALC650)
i810_audio: AC'97 codec 0, new EID value = 0x05c7
i810_audio: AC'97 codec 0, DAC map configured, total channels = 6
PCI: Setting latency timer of device 00:02.2 to 64
ehci-hcd 00:02.2: PCI device 10de:0068 (nVidia Corporation)
ehci-hcd 00:02.2: irq 5, pci mem f88c0000
usb.c: new USB bus registered, assigned bus number 3
PCI: 00:02.2 PCI cache line size set incorrectly (0 bytes) by BIOS/FW.
PCI: 00:02.2 PCI cache line size corrected to 64.
ehci-hcd 00:02.2: USB 2.0 enabled, EHCI 1.00, driver 2003-Jan-22
hub.c: USB hub found
hub.c: 6 ports detected
usb.c: USB disconnect on device 00:02.1-1 address 2
usb.c: USB disconnect on device 00:02.0-1 address 2
usb.c: USB disconnect on device 00:02.0-1.1 address 4
usb.c: USB disconnect on device 00:02.0-2 address 3
hub.c: new USB device 00:02.0-1, assigned address 5
hub.c: USB hub found
hub.c: 3 ports detected
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
hub.c: new USB device 00:02.0-2, assigned address 6
input0: USB HID v1.10 Mouse [Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)] on usb1:6.0
hub.c: new USB device 00:02.0-1.1, assigned address 7
input1: USB HID v1.10 Keyboard [045e:001d] on usb1:7.0
input2: USB HID v1.10 Pointer [045e:001d] on usb1:7.1
hub.c: new USB device 00:02.1-1, assigned address 3
usb.c: USB device 3 (vend/prod 0x46d/0x840) is not claimed by any active driver.
parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE]
parport0: irq 7 detected
lp0: using parport0 (polling).
[fglrx] Maximum main memory to use for locked dma buffers: 927 MBytes.
[fglrx] module loaded - fglrx 2.9.13 [Jun 12 2003] on minor 0
Fire GL built-in AGP-support
Based on agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 816M
agpgart: Detected NVIDIA nForce2 chipset
agpgart: AGP aperture is 512M @ 0xa0000000
[fglrx] AGP detected, AgpState   = 0x1f000217 (hardware caps of chipset)
AGP: Found 2 AGPv2 devices
AGP: Doing enable for AGPv2
[fglrx] To use AGP on this CPU with this kernel, you really should have 4MB pages disabled. Use `mem=nopentium` on the bootloader commandline.
[fglrx] AGP enabled,  AgpCommand = 0x1f000314 (selected caps)
[fglrx] free  AGP = 524562432
[fglrx] max   AGP = 524562432
[fglrx] free  LFB = 49283072
[fglrx] max   LFB = 49283072
[fglrx] free  Inv = 0
[fglrx] max   Inv = 0
[fglrx] total Inv = 0
[fglrx] total TIM = 0
keyboard: Timeout - AT keyboard not present?(f4)
keyboard: Timeout - AT keyboard not present?(f4)
Attached scsi CD-ROM sr0 at scsi0, channel 0, id 3, lun 0
Attached scsi CD-ROM sr1 at scsi0, channel 0, id 4, lun 0
(scsi0:A:3): 40.000MB/s transfers (20.000MHz, offset 15, 16bit)
sr0: scsi-1 drive
Uniform CD-ROM driver Revision: 3.12
(scsi0:A:4): 20.000MB/s transfers (20.000MHz, offset 16)
sr1: scsi3-mmc drive: 32x/32x writer cd/rw xa/form2 cdda tray
keyboard: Timeout - AT keyboard not present?(f4)
mtrr: no MTRR for c0000000,400000 found
mtrr: no MTRR for c0400000,200000 found
mtrr: no MTRR for c0600000,100000 found
[fglrx] free  AGP = 524562432
[fglrx] max   AGP = 524562432
[fglrx] free  LFB = 49283072
[fglrx] max   LFB = 49283072
[fglrx] free  Inv = 0
[fglrx] max   Inv = 0
[fglrx] total Inv = 0
[fglrx] total TIM = 0
keyboard: Timeout - AT keyboard not present?(f4)
keyboard: Timeout - AT keyboard not present?(f4)
keyboard: Timeout - AT keyboard not present?(f4)
mtrr: no MTRR for c0000000,400000 found
mtrr: no MTRR for c0400000,200000 found
mtrr: no MTRR for c0600000,100000 found
[fglrx] module unloaded - fglrx 2.9.13 [Jun 12 2003] on minor 0
[fglrx] Maximum main memory to use for locked dma buffers: 927 MBytes.
[fglrx] module loaded - fglrx 2.9.13 [Jun 12 2003] on minor 0
Fire GL built-in AGP-support
Based on agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 816M
agpgart: Detected NVIDIA nForce2 chipset
agpgart: AGP aperture is 512M @ 0xa0000000
[fglrx] AGP detected, AgpState   = 0x1f000217 (hardware caps of chipset)
AGP: Found 2 AGPv2 devices
AGP: Doing enable for AGPv2
[fglrx] To use AGP on this CPU with this kernel, you really should have 4MB pages disabled. Use `mem=nopentium` on the bootloader commandline.
[fglrx] AGP enabled,  AgpCommand = 0x1f000314 (selected caps)
[fglrx] free  AGP = 524562432
[fglrx] max   AGP = 524562432
[fglrx] free  LFB = 49283072
[fglrx] max   LFB = 49283072
[fglrx] free  Inv = 0
[fglrx] max   Inv = 0
[fglrx] total Inv = 0
[fglrx] total TIM = 0

[-- Attachment #1.3: lspci-2.4.txt --]
[-- Type: text/plain, Size: 12936 bytes --]

00:00.0 Host bridge: nVidia Corporation: Unknown device 01e0 (rev c1)
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Region 0: Memory at a0000000 (32-bit, prefetchable) [size=512M]
	Capabilities: [40] AGP version 2.0
		Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3- Rate=x1,x2,x4
		Command: RQ=1 ArqSz=0 Cal=0 SBA+ AGP+ GART64- 64bit- FW+ Rate=x4
	Capabilities: [60] #08 [2001]

00:00.1 RAM memory: nVidia Corporation: Unknown device 01eb (rev c1)
	Subsystem: nVidia Corporation: Unknown device 0c17
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-

00:00.2 RAM memory: nVidia Corporation: Unknown device 01ee (rev c1)
	Subsystem: nVidia Corporation: Unknown device 0c17
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-

00:00.3 RAM memory: nVidia Corporation: Unknown device 01ed (rev c1)
	Subsystem: nVidia Corporation: Unknown device 0c17
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-

00:00.4 RAM memory: nVidia Corporation: Unknown device 01ec (rev c1)
	Subsystem: nVidia Corporation: Unknown device 0c17
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-

00:00.5 RAM memory: nVidia Corporation: Unknown device 01ef (rev c1)
	Subsystem: nVidia Corporation: Unknown device 0c17
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-

00:01.0 ISA bridge: nVidia Corporation nForce2 ISA Bridge (rev a4)
	Subsystem: Giga-byte Technology: Unknown device 0c11
	Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Capabilities: [48] #08 [01e1]

00:01.1 SMBus: nVidia Corporation nForce2 SMBus (MCP) (rev a2)
	Subsystem: Giga-byte Technology: Unknown device 0c11
	Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Interrupt: pin A routed to IRQ 5
	Region 0: I/O ports at dc00 [size=32]
	Capabilities: [44] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:02.0 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4) (prog-if 10 [OHCI])
	Subsystem: Giga-byte Technology: Unknown device 5004
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0 (750ns min, 250ns max)
	Interrupt: pin A routed to IRQ 11
	Region 0: Memory at ce087000 (32-bit, non-prefetchable) [size=4K]
	Capabilities: [44] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:02.1 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4) (prog-if 10 [OHCI])
	Subsystem: Giga-byte Technology: Unknown device 5004
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0 (750ns min, 250ns max)
	Interrupt: pin B routed to IRQ 9
	Region 0: Memory at ce082000 (32-bit, non-prefetchable) [size=4K]
	Capabilities: [44] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:02.2 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4) (prog-if 20 [EHCI])
	Subsystem: Giga-byte Technology: Unknown device 5004
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0 (750ns min, 250ns max)
	Interrupt: pin C routed to IRQ 5
	Region 0: Memory at ce083000 (32-bit, non-prefetchable) [size=256]
	Capabilities: [44] #0a [2080]
	Capabilities: [80] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:04.0 Ethernet controller: nVidia Corporation nForce2 Ethernet Controller (rev a1)
	Subsystem: Giga-byte Technology: Unknown device e000
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0 (250ns min, 5000ns max)
	Interrupt: pin A routed to IRQ 9
	Region 0: Memory at ce086000 (32-bit, non-prefetchable) [size=4K]
	Region 1: I/O ports at e000 [size=8]
	Capabilities: [44] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:05.0 Multimedia audio controller: nVidia Corporation nForce MultiMedia audio [Via VT82C686B] (rev a2)
	Subsystem: nVidia Corporation: Unknown device 0c11
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0 (250ns min, 3000ns max)
	Interrupt: pin A routed to IRQ 9
	Region 0: Memory at ce000000 (32-bit, non-prefetchable) [size=512K]
	Capabilities: [44] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:06.0 Multimedia audio controller: nVidia Corporation nForce2 AC97 Audio Controler (MCP) (rev a1)
	Subsystem: nVidia Corporation: Unknown device 4144
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0 (500ns min, 1250ns max)
	Interrupt: pin A routed to IRQ 5
	Region 0: I/O ports at e400 [size=256]
	Region 1: I/O ports at d000 [size=128]
	Region 2: Memory at ce080000 (32-bit, non-prefetchable) [size=4K]
	Capabilities: [44] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:08.0 PCI bridge: nVidia Corporation: Unknown device 006c (rev a3) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
	Status: Cap- 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
	I/O behind bridge: 00008000-0000afff
	Memory behind bridge: cc000000-cdffffff
	Prefetchable memory behind bridge: fff00000-000fffff
	BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- >Reset- FastB2B-

00:09.0 IDE interface: nVidia Corporation nForce2 IDE (rev a2) (prog-if 8a [Master SecP PriP])
	Subsystem: Giga-byte Technology: Unknown device 5002
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0 (750ns min, 250ns max)
	Region 4: I/O ports at f000 [size=16]
	Capabilities: [44] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:0d.0 FireWire (IEEE 1394): nVidia Corporation nForce2 FireWire (IEEE 1394) Controller (rev a3) (prog-if 10 [OHCI])
	Subsystem: Giga-byte Technology: Unknown device 1000
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0 (750ns min, 250ns max)
	Interrupt: pin A routed to IRQ 11
	Region 0: Memory at ce084000 (32-bit, non-prefetchable) [size=2K]
	Region 1: Memory at ce085000 (32-bit, non-prefetchable) [size=64]
	Capabilities: [44] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME+

00:1e.0 PCI bridge: nVidia Corporation nForce2 AGP (rev c1) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
	Status: Cap- 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 32
	Bus: primary=00, secondary=03, subordinate=03, sec-latency=32
	I/O behind bridge: 0000c000-0000cfff
	Memory behind bridge: ca000000-cbffffff
	Prefetchable memory behind bridge: c0000000-c7ffffff
	BridgeCtl: Parity- SERR+ NoISA- VGA+ MAbort- >Reset- FastB2B-

01:0a.0 SCSI storage controller: Adaptec AHA-2940U2/U2W
	Subsystem: Adaptec AHA-2940U2W SCSI Controller
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 32 (9750ns min, 6250ns max)
	Interrupt: pin A routed to IRQ 11
	BIST result: 00
	Region 0: I/O ports at 8000 [disabled] [size=256]
	Region 1: Memory at cd020000 (64-bit, non-prefetchable) [size=4K]
	Expansion ROM at <unassigned> [disabled] [size=128K]
	Capabilities: [dc] Power Management version 1
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

01:0b.0 Ethernet controller: Intel Corp. 82540EM Gigabit Ethernet Controller (rev 02)
	Subsystem: Intel Corp.: Unknown device 3013
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 32 (63750ns min), cache line size 08
	Interrupt: pin A routed to IRQ 5
	Region 0: Memory at cd000000 (32-bit, non-prefetchable) [size=128K]
	Region 2: I/O ports at 8400 [size=64]
	Capabilities: [dc] Power Management version 2
		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=1 PME-
	Capabilities: [e4] PCI-X non-bridge device.
		Command: DPERE- ERO+ RBC=0 OST=0
		Status: Bus=0 Dev=0 Func=0 64bit- 133MHz- SCD- USC-, DC=simple, DMMRBC=0, DMOST=0, DMCRS=0, RSCEM-	Capabilities: [f0] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
		Address: 0000000000000000  Data: 0000

03:00.0 VGA compatible controller: ATI Technologies Inc Radeon R250 If [Radeon 9000] (rev 01) (prog-if 00 [VGA])
	Subsystem: ATI Technologies Inc: Unknown device 0002
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B-
	Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 255 (2000ns min), cache line size 08
	Interrupt: pin A routed to IRQ 11
	Region 0: Memory at c0000000 (32-bit, prefetchable) [size=64M]
	Region 1: I/O ports at c000 [size=256]
	Region 2: Memory at cb000000 (32-bit, non-prefetchable) [size=64K]
	Expansion ROM at <unassigned> [disabled] [size=128K]
	Capabilities: [58] AGP version 2.0
		Status: RQ=48 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3- Rate=x1,x2,x4
		Command: RQ=32 ArqSz=0 Cal=0 SBA+ AGP+ GART64- 64bit- FW+ Rate=x4
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

03:00.1 Display controller: ATI Technologies Inc Radeon R250 [Radeon 9000] (Secondary) (rev 01)
	Subsystem: ATI Technologies Inc: Unknown device 0003
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B-
	Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 32 (2000ns min), cache line size 08
	Region 0: Memory at c4000000 (32-bit, prefetchable) [size=64M]
	Region 1: Memory at cb010000 (32-bit, non-prefetchable) [size=64K]
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-


[-- Attachment #1.4: aic7xxx-proc.txt --]
[-- Type: text/plain, Size: 3288 bytes --]

Attached devices: 
Host: scsi0 Channel: 00 Id: 00 Lun: 00
  Vendor: IBM      Model: DDYS-T36950N     Rev: S80D
  Type:   Direct-Access                    ANSI SCSI revision: 03
Host: scsi0 Channel: 00 Id: 03 Lun: 00
  Vendor: PLEXTOR  Model: CD-ROM PX-40TW   Rev: 1.05
  Type:   CD-ROM                           ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 04 Lun: 00
  Vendor: PLEXTOR  Model: CD-R   PX-W1210S Rev: 1.06
  Type:   CD-ROM                           ANSI SCSI revision: 02
Adaptec AIC7xxx driver version: 6.2.8
aic7890/91: Ultra2 Wide Channel A, SCSI Id=7, 32/253 SCBs

Serial EEPROM:
0xc3bb 0xc3bb 0xc3bb 0xc3bb 0xc3bb 0xc3bb 0xc3bb 0xc3bb 
0xc3bb 0xc3bb 0xc3bb 0xc3bb 0xc3bb 0xc3bb 0xc3bb 0xc3bb 
0xb8e4 0x745d 0x2807 0x0010 0xffff 0xffff 0xffff 0xffff 
0xffff 0xffff 0xffff 0xffff 0xffff 0xffff 0x0250 0x934e 

Channel A Target 0 Negotiation Settings
	User: 80.000MB/s transfers (40.000MHz, offset 255, 16bit)
	Goal: 80.000MB/s transfers (40.000MHz, offset 63, 16bit)
	Curr: 80.000MB/s transfers (40.000MHz, offset 63, 16bit)
	Channel A Target 0 Lun 0 Settings
		Commands Queued 11825
		Commands Active 0
		Command Openings 8
		Max Tagged Openings 8
		Device Queue Frozen Count 0
Channel A Target 1 Negotiation Settings
	User: 80.000MB/s transfers (40.000MHz, offset 255, 16bit)
Channel A Target 2 Negotiation Settings
	User: 80.000MB/s transfers (40.000MHz, offset 255, 16bit)
Channel A Target 3 Negotiation Settings
	User: 80.000MB/s transfers (40.000MHz, offset 255, 16bit)
	Goal: 40.000MB/s transfers (20.000MHz, offset 15, 16bit)
	Curr: 40.000MB/s transfers (20.000MHz, offset 15, 16bit)
	Channel A Target 3 Lun 0 Settings
		Commands Queued 36
		Commands Active 0
		Command Openings 1
		Max Tagged Openings 0
		Device Queue Frozen Count 0
Channel A Target 4 Negotiation Settings
	User: 80.000MB/s transfers (40.000MHz, offset 255, 16bit)
	Goal: 20.000MB/s transfers (20.000MHz, offset 16)
	Curr: 20.000MB/s transfers (20.000MHz, offset 16)
	Channel A Target 4 Lun 0 Settings
		Commands Queued 3
		Commands Active 0
		Command Openings 1
		Max Tagged Openings 0
		Device Queue Frozen Count 0
Channel A Target 5 Negotiation Settings
	User: 80.000MB/s transfers (40.000MHz, offset 255, 16bit)
Channel A Target 6 Negotiation Settings
	User: 80.000MB/s transfers (40.000MHz, offset 255, 16bit)
Channel A Target 7 Negotiation Settings
	User: 80.000MB/s transfers (40.000MHz, offset 255, 16bit)
Channel A Target 8 Negotiation Settings
	User: 80.000MB/s transfers (40.000MHz, offset 255, 16bit)
Channel A Target 9 Negotiation Settings
	User: 80.000MB/s transfers (40.000MHz, offset 255, 16bit)
Channel A Target 10 Negotiation Settings
	User: 80.000MB/s transfers (40.000MHz, offset 255, 16bit)
Channel A Target 11 Negotiation Settings
	User: 80.000MB/s transfers (40.000MHz, offset 255, 16bit)
Channel A Target 12 Negotiation Settings
	User: 80.000MB/s transfers (40.000MHz, offset 255, 16bit)
Channel A Target 13 Negotiation Settings
	User: 80.000MB/s transfers (40.000MHz, offset 255, 16bit)
Channel A Target 14 Negotiation Settings
	User: 80.000MB/s transfers (40.000MHz, offset 255, 16bit)
Channel A Target 15 Negotiation Settings
	User: 80.000MB/s transfers (40.000MHz, offset 255, 16bit)

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: Badness in device_release at drivers/base/core.c:84

[Patrick Mansfield]

On Sun, Aug 03, 2003 at 06:31:15PM -0400, Diffie wrote:
> On Sun, Aug 03, 2003 at 06:23:13PM -0400, Diffie wrote:

> > Thank you for all your help.Sorry but i gave the wrong URL in previous
> > email.The correct one is http://www.blazebox.homeip.net:81/diffie/images/linux-2.6.0-test2/ 
> > 

Per your screen dump - it found the cd-rom's on id 3 and 4, but not your
disk drive that was at id 0, and the adapter found something at id 6 (host
adapter is at id 7).

You could try turning on scan logging, it might give more information.
You can turn on the logging at boot time, make sure you have
CONFIG_SCSI_LOGGING on, the information of interest (scan of host 0 chan 0
id 0 lun 0) likely will scroll off screen.

For scan logging, add to your boot line:

	scsi_mod.scsi_logging_level=0x140

To limit the logging info, make sure max_scsi_luns=1 via config or boot
time option scsi_mod.max_scsi_luns=1.

-- Patrick Mansfield

Re: Badness in device_release at drivers/base/core.c:84

[Paul Blazejowski]

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

On Mon, 2003-08-04 at 12:30, Patrick Mansfield wrote:
> On Sun, Aug 03, 2003 at 06:31:15PM -0400, Diffie wrote:
> > On Sun, Aug 03, 2003 at 06:23:13PM -0400, Diffie wrote:
> 
> > > Thank you for all your help.Sorry but i gave the wrong URL in previous
> > > email.The correct one is http://www.blazebox.homeip.net:81/diffie/images/linux-2.6.0-test2/
> > > 
> 
> Per your screen dump - it found the cd-rom's on id 3 and 4, but not your
> disk drive that was at id 0, and the adapter found something at id 6 (host
> adapter is at id 7).
> 
> You could try turning on scan logging, it might give more information.
> You can turn on the logging at boot time, make sure you have
> CONFIG_SCSI_LOGGING on, the information of interest (scan of host 0 chan 0
> id 0 lun 0) likely will scroll off screen.
> 
> For scan logging, add to your boot line:
> 
> 	scsi_mod.scsi_logging_level=0x140
> 
> To limit the logging info, make sure max_scsi_luns=1 via config or boot
> time option scsi_mod.max_scsi_luns=1.
> 
> -- Patrick Mansfield
> 

Patrick,

That's correct Plextor 40TW (ultraplex wide) is on ID3 and Plextor
plexwriter 32/10/12s is on ID4.Originally i had the IBM 36LZX drive at
ID6 (factory setting) but when using the aic7xxx_old driver it was
detected as /dev/sdb for some reason.I've changed the ID to 0 and it
became /dev/sda again...strange it is.

The Adaptec AHA-2940U2W card is set to boot from ID0 by default and it
has 2.57.2 BIOS (the latest i think).

I tried the latest 2.6.36 driver from Justin's site on kernel 2.4.21 and
it works great.I was unable to boot the 2.5 driver on 2.6.0-test2 it
game oops and i had to define blkdev.h in few places.

I will try your suggestions and report back.

Regards,

Paul B.



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: Badness in device_release at drivers/base/core.c:84

[Paul Blazejowski]

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

On Mon, 2003-08-04 at 12:30, Patrick Mansfield wrote:
> On Sun, Aug 03, 2003 at 06:31:15PM -0400, Diffie wrote:
> > On Sun, Aug 03, 2003 at 06:23:13PM -0400, Diffie wrote:
> 
> > > Thank you for all your help.Sorry but i gave the wrong URL in previous
> > > email.The correct one is http://www.blazebox.homeip.net:81/diffie/images/linux-2.6.0-test2/
> > > 
> 
> Per your screen dump - it found the cd-rom's on id 3 and 4, but not your
> disk drive that was at id 0, and the adapter found something at id 6 (host
> adapter is at id 7).
> 
> You could try turning on scan logging, it might give more information.
> You can turn on the logging at boot time, make sure you have
> CONFIG_SCSI_LOGGING on, the information of interest (scan of host 0 chan 0
> id 0 lun 0) likely will scroll off screen.
> 
> For scan logging, add to your boot line:
> 
> 	scsi_mod.scsi_logging_level=0x140
> 
> To limit the logging info, make sure max_scsi_luns=1 via config or boot
> time option scsi_mod.max_scsi_luns=1.
> 
> -- Patrick Mansfield
> 

Patrick,

I enabled CONFIG_SCSI_LOGGING=y in kernel then i used
scsi_mod.scsi_logging_level=0x140 and scsi_mod.max_scsi_luns=1 when
booting the kernel from lilo.I can see some debug information scroll on
the screen and i did see ID0 LUN0 get probed even the correct transfer
rate for the SCSI disk is set.I forgot but isn't there a key sequence
when pressed it will stop the screen output like pause/break key?

I have few screen snaps which can be viewed at 
http://www.blazebox.homeip.net:81/diffie/images/linux-2.6.0-test2/aic7xxx/

Thanks for your help.

Paul B.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: Badness in device_release at drivers/base/core.c:84

[Patrick Mansfield]

On Mon, Aug 04, 2003 at 02:26:54PM -0400, Paul Blazejowski wrote:
> 
> Patrick,
> 
> I enabled CONFIG_SCSI_LOGGING=y in kernel then i used
> scsi_mod.scsi_logging_level=0x140 and scsi_mod.max_scsi_luns=1 when
> booting the kernel from lilo.I can see some debug information scroll on
> the screen and i did see ID0 LUN0 get probed even the correct transfer
> rate for the SCSI disk is set.I forgot but isn't there a key sequence
> when pressed it will stop the screen output like pause/break key?
> 
> I have few screen snaps which can be viewed at 
> http://www.blazebox.homeip.net:81/diffie/images/linux-2.6.0-test2/aic7xxx/

Yep, the shot that might have useful information is blurred.

I assume you are unable to use a serial console.

I can usually "Shift + page-up" as long as there is not too much data, and
depending on your console, AFAIR I can't pause my console output.

Also, does the adapter bios show the drive at boot time?

Hopefully Justin will add more useful suggestions for debugging.

-- Patrick Mansfield

Re: Badness in device_release at drivers/base/core.c:84

[Justin T. Gibbs]

> Patrick,
> 
> I enabled CONFIG_SCSI_LOGGING=y in kernel then i used
> scsi_mod.scsi_logging_level=0x140 and scsi_mod.max_scsi_luns=1 when
> booting the kernel from lilo.I can see some debug information scroll on
> the screen and i did see ID0 LUN0 get probed even the correct transfer
> rate for the SCSI disk is set.I forgot but isn't there a key sequence
> when pressed it will stop the screen output like pause/break key?

You might be able to get useful information without using a serial
console if you turn off your CDROM drives so they don't add extra output,
but your best bet is to use a serial console.

--
Justin

Re: Badness in device_release at drivers/base/core.c:84

[Paul Blazejowski]

>
> You might be able to get useful information without using a serial
> console if you turn off your CDROM drives so they don't add extra output,
> but your best bet is to use a serial console.
>
> --
> Justin
>
>
>

Justin,

I am going to try with the SCSI disk drive alone after diconnecting the
cdrom drivers.

I'll look into serial console and try to set it up.Do i need extra
hardware or cables to run serial console? any poniters or setup
suggestions would be welcome as i never used serial consoles before.
Regards,

Paul

Re: Badness in device_release at drivers/base/core.c:84

[Paul Blazejowski]

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

On Mon, 2003-08-04 at 15:36, Justin T. Gibbs wrote:
> > Patrick,
> > 
> > I enabled CONFIG_SCSI_LOGGING=y in kernel then i used
> > scsi_mod.scsi_logging_level=0x140 and scsi_mod.max_scsi_luns=1 when
> > booting the kernel from lilo.I can see some debug information scroll on
> > the screen and i did see ID0 LUN0 get probed even the correct transfer
> > rate for the SCSI disk is set.I forgot but isn't there a key sequence
> > when pressed it will stop the screen output like pause/break key?
> 
> You might be able to get useful information without using a serial
> console if you turn off your CDROM drives so they don't add extra output,
> but your best bet is to use a serial console.
> 
> --
> Justin
> 
> 

Hi Justin,

This time with both plextor cdroms removed i get this in console:

scsi scan: INQUIRY to host 0 chanel 0 id0 lun 0
scsi scan: 1st INQUIRY failed with code 0x10000

and this repeats for all 15 id's on the cards with same 0x10000 code.

When using aic7xxx_old driver i get this in dmesg:

(scsi0) <Adaptec AHA-294X Ultra2 SCSI host adapter> found at PCI 1/10/0
(scsi0) Wide Channel, SCSI ID=7, 32/255 SCBs
(scsi0) Downloading sequencer code... 398 instructions downloaded
scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.2.6/5.2.0
       <Adaptec AHA-294X Ultra2 SCSI host adapter>
scsi scan: INQUIRY to host 0 channel 0 id 0 lun 0
scsi scan: 1st INQUIRY successful with code 0x0
  Vendor:           Model:                   Rev:
  Type:   Direct-Access                      ANSI SCSI revision: 00
scsi scan: Sequential scan of host 0 channel 0 id 0
scsi scan: INQUIRY to host 0 channel 0 id 1 lun 0
scsi: Device offlined - not ready after error recovery: host 0 channel 0
id 1 lun 0
scsi scan: 1st INQUIRY failed with code 0x6030000
scsi scan: INQUIRY to host 0 channel 0 id 2 lun 0
scsi scan: 1st INQUIRY failed with code 0x30000
scsi scan: INQUIRY to host 0 channel 0 id 3 lun 0
scsi scan: 1st INQUIRY failed with code 0x30000
scsi scan: INQUIRY to host 0 channel 0 id 4 lun 0
scsi scan: 1st INQUIRY failed with code 0x30000
scsi scan: INQUIRY to host 0 channel 0 id 5 lun 0
scsi scan: 1st INQUIRY failed with code 0x30000
scsi scan: INQUIRY to host 0 channel 0 id 6 lun 0
scsi scan: 1st INQUIRY failed with code 0x30000
scsi scan: INQUIRY to host 0 channel 0 id 8 lun 0
scsi scan: 1st INQUIRY failed with code 0x30000
scsi scan: INQUIRY to host 0 channel 0 id 9 lun 0
scsi scan: 1st INQUIRY failed with code 0x30000
scsi scan: INQUIRY to host 0 channel 0 id 10 lun 0
scsi scan: 1st INQUIRY failed with code 0x30000
scsi scan: INQUIRY to host 0 channel 0 id 11 lun 0
scsi scan: 1st INQUIRY failed with code 0x30000
scsi scan: INQUIRY to host 0 channel 0 id 12 lun 0
scsi scan: 1st INQUIRY failed with code 0x30000
scsi scan: INQUIRY to host 0 channel 0 id 13 lun 0
scsi scan: 1st INQUIRY failed with code 0x30000
scsi scan: INQUIRY to host 0 channel 0 id 14 lun 0
scsi scan: 1st INQUIRY failed with code 0x30000
scsi scan: INQUIRY to host 0 channel 0 id 15 lun 0
scsi scan: 1st INQUIRY failed with code 0x30000
SCSI device sda: 71687340 512-byte hdwr sectors (36704 MB)
SCSI device sda: drive cache: write back
 /dev/scsi/host0/bus0/target0/lun0: p1 p2 p3 p4 < p5 p6 p7 p8 p9 p10 >
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0,  type 0

Once i get null modem serial cable i will try to get more info from
serial console.

Regards,

Paul

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: Badness in device_release at drivers/base/core.c:84

[wb]

> 
> I'll look into serial console and try to set it up.Do i need extra
> hardware or cables to run serial console? any poniters or setup
> suggestions would be welcome as i never used serial consoles before.
> Regards,
> 
> Paul
> -

  Your need a NULL modem serial cable available
  from any computer store.

Install uucp - I use on the HOST :

uucp-1.06.1-33.7.2.

Also , LILO is broken on some machines and ignores
serial input so make sure you use at least

lilo-21.6-71

On the TARGET

1. Connect the serial ports together ( COM1->COM1 ) with
    the serial cable .

2. Modify LILO to use serial line on the TARGET
    add to lilo.conf:
       append="console=ttyS0,9600n8  console=tty0 "
       serial=0,9600N8

    Run lilo

3. Add to /etc/inittab on the HOST

       S0:s12345:respawn:/sbin/agetty 9600 ttyS0

4. To see ALL THE CONSOLE MESSAGES during boot on the TARGET

    mv /dev/console /dev/console.org
    ln  /dev/ttyS0 /dev/console

5. Start uucp on the HOST:

     cu -l /dev/ttyS0 -s 9600

6. Boot your target

///

John Donnelly AT HP DOT com

Re: Badness in device_release at drivers/base/core.c:84

[Ishikawa]

(Sorry this is not strictly related to SCSI, but I could not help it.)

Regarding the use of a program from uucp suite
for console output capture,
we can use C-Kermit as well.

>   Your need a NULL modem serial cable available
>   from any computer store.
> 
> Install uucp - I use on the HOST :
> 
> uucp-1.06.1-33.7.2.

Or you can use C-Kermit.
See

   http://www.columbia.edu/kermit/ckermit.html

for details. There are precompiled packages.

>  ... [omission ] ...

> 5. Start uucp on the HOST:
> 
>      cu -l /dev/ttyS0 -s 9600

       kermit
       set line /dev/ttyS0
       set speed 9600
       connect
 
and you can issue other commands.
        set [space] ?
will print all the available options at that point.
(You can log the interaction into a file by issueing
a command to kermit, too, but using script and then run kermit
inside the scripted session might be easier.)
(Generally speaking hitting ? somewhere on the kermit command line
prints usable options/setting/keywords, and so
you can learn the basics very quickly.)
You can set up a startup file that sets
the device name, speed, parity, data size, etc. and
so you don't have to type all the command every time.

While I agree cu might work well for one shot job,
running a full terminal emulator like C-Kermit
helps us in the long term.

Just thought to let you know a full-featured terminal
emulator is available under linux.

> John Donnelly AT HP DOT com

Is the succinct and to the point steps
part of a widely available document?

I wish I knew this a few years ago.


-- 
int main(void){int j=2003;/*(c)2003 cishikawa. */
char t[] ="<CI> @abcdefghijklmnopqrstuvwxyz.,\n\"";
char *i ="g>qtCIuqivb,gCwe\np@.ietCIuqi\"tqkvv is>dnamz";
while(*i)((j+=strchr(t,*i++)-(int)t),(j%=sizeof t-1),
(putchar(t[j])));return 0;}/* under GPL */

Re: Badness in device_release at drivers/base/core.c:84

[Paul Blazejowski]

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

On Tue, 2003-08-05 at 06:20, wb wrote:
> > 
> > I'll look into serial console and try to set it up.Do i need extra
> > hardware or cables to run serial console? any poniters or setup
> > suggestions would be welcome as i never used serial consoles before.
> > Regards,
> > 
> > Paul
> > -
> 
>   Your need a NULL modem serial cable available
>   from any computer store.
> 
> Install uucp - I use on the HOST :
> 
> uucp-1.06.1-33.7.2.
> 
> Also , LILO is broken on some machines and ignores
> serial input so make sure you use at least
> 
> lilo-21.6-71
> 
> On the TARGET
> 
> 1. Connect the serial ports together ( COM1->COM1 ) with
>     the serial cable .
> 
> 2. Modify LILO to use serial line on the TARGET
>     add to lilo.conf:
>        append="console=ttyS0,9600n8  console=tty0 "
>        serial=0,9600N8
> 
>     Run lilo
> 
> 3. Add to /etc/inittab on the HOST
> 
>        S0:s12345:respawn:/sbin/agetty 9600 ttyS0
> 
> 4. To see ALL THE CONSOLE MESSAGES during boot on the TARGET
> 
>     mv /dev/console /dev/console.org
>     ln  /dev/ttyS0 /dev/console
> 
> 5. Start uucp on the HOST:
> 
>      cu -l /dev/ttyS0 -s 9600
> 
> 6. Boot your target
> 
> ///
> 
> John Donnelly AT HP DOT com
> 

John,

I appreciate your writing short and sweet howto :-).

I was able to get it going from FreeBSD 5.1 box with cu -l /dev/ttyd0
2&<1 > log to my Linux machine.

Thank you for helping.

Paul B.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: Badness in device_release at drivers/base/core.c:84

[Paul Blazejowski]

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

On Tue, 2003-08-05 at 12:10, Ishikawa wrote:
> (Sorry this is not strictly related to SCSI, but I could not help it.)
> 
> Regarding the use of a program from uucp suite
> for console output capture,
> we can use C-Kermit as well.
> 
> >   Your need a NULL modem serial cable available
> >   from any computer store.
> > 
> > Install uucp - I use on the HOST :
> > 
> > uucp-1.06.1-33.7.2.
> 
> Or you can use C-Kermit.
> See
> 
>    http://www.columbia.edu/kermit/ckermit.html
> 
> for details. There are precompiled packages.
> 
> >  ... [omission ] ...
> 
> > 5. Start uucp on the HOST:
> > 
> >      cu -l /dev/ttyS0 -s 9600
> 
>        kermit
>        set line /dev/ttyS0
>        set speed 9600
>        connect
>  
> and you can issue other commands.
>         set [space] ?
> will print all the available options at that point.
> (You can log the interaction into a file by issueing
> a command to kermit, too, but using script and then run kermit
> inside the scripted session might be easier.)
> (Generally speaking hitting ? somewhere on the kermit command line
> prints usable options/setting/keywords, and so
> you can learn the basics very quickly.)
> You can set up a startup file that sets
> the device name, speed, parity, data size, etc. and
> so you don't have to type all the command every time.
> 
> While I agree cu might work well for one shot job,
> running a full terminal emulator like C-Kermit
> helps us in the long term.
> 
> Just thought to let you know a full-featured terminal
> emulator is available under linux.
> 
> > John Donnelly AT HP DOT com
> 
> Is the succinct and to the point steps
> part of a widely available document?
> 
> I wish I knew this a few years ago.
> 

Kermit was very helpful but due to my inexperience i was not able to get
the log due to Linux's box resetting of /dev/ttyS0 when booting, i would
get disconnect...

Thanks a lot for suggesting ckermit.

Regards,

Paul B.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: Badness in device_release at drivers/base/core.c:84

[Chiaki]

> 
> Kermit was very helpful but due to my inexperience i was not able to get
> the log due to Linux's box resetting of /dev/ttyS0 when booting, i would
> get disconnect...
> 

Oh, I forgot some details. You might be able to
circumvent the problem by
issueing
set carrier-watch off

I use the direct-wire connetion with
a device from a Linux PC's tty port using ckermit and
so let me check the setup again tomorrow at the office.

> Thanks a lot for suggesting ckermit.
> 
> Regards,
> 
> Paul B.


-- 
int main(void){int j=2003;/*(c)2003 cishikawa. */
char t[] ="<CI> @abcdefghijklmnopqrstuvwxyz.,\n\"";
char *i ="g>qtCIuqivb,gCwe\np@.ietCIuqi\"tqkvv is>dnamz";
while(*i)((j+=strchr(t,*i++)-(int)t),(j%=sizeof t-1),
(putchar(t[j])));return 0;}/* under GPL */

Re: Badness in device_release at drivers/base/core.c:84

[Chiaki]

Chiaki wrote:

>> Kermit was very helpful but due to my inexperience i was not able to get
>> the log due to Linux's box resetting of /dev/ttyS0 when booting, i would
>> get disconnect...
>>
> 
> Oh, I forgot some details. You might be able to
> circumvent the problem by
> issueing
> set carrier-watch off
> 
> I use the direct-wire connetion with
> a device from a Linux PC's tty port using ckermit and
> so let me check the setup again tomorrow at the office.

Sorry for the delay. Below is the copy of kermit startup file
that I use for talking to a device that does not echo back characters.
I also power-on/off the device while connecting kermit to it, and
I don't think I got kicked off. : so
set carrier-watch off (abbreviated below as set carrier off)
should get you going talking to a linux box via
serial line during booting. (However,
I believe you already captured the necessary log using
uucp suite of tools.)

  set line /dev/ttyS0
  set speed 38400
  set carrier off                    <-  This is key to the disconnect 
problem.
  set terminal echo local   <--- lines below here are for local echo back
  set terminal newline on
  set terminal cr-display crlf

>> Thanks a lot for suggesting ckermit.

You are very welcome.

 From a happy Kermit user.
If you need to ask elaborate ckermit questions,
comp.protocols.kermit.misc is where the original
developers of Kermit hang around.

Happy Hacking,

Ishikawa, Chiaki


-- 
int main(void){int j=2003;/*(c)2003 cishikawa. */
char t[] ="<CI> @abcdefghijklmnopqrstuvwxyz.,\n\"";
char *i ="g>qtCIuqivb,gCwe\np@.ietCIuqi\"tqkvv is>dnamz";
while(*i)((j+=strchr(t,*i++)-(int)t),(j%=sizeof t-1),
(putchar(t[j])));return 0;}/* under GPL */