Re: problem booting aic7xxx-old with reiserfs

Re: problem booting aic7xxx-old with reiserfs

[Andreas Theofilu]

martin f krafft wrote:

> [please CC me on replies!]
> 
> Hi all,
> 
> I configured the 2.6.0 kernel [2] with the old aic7xxx driver, as well
> as the 3c59x and 8139too drivers. Now, when I start the system, it
> loads the kernel just fine, the SCSI driver recognises the
> harddrive, but when it tries to mount / (reiserfs) (right after
> initialising TCP, GRE, IPsec, IPv6 and SCTP), it just hangs with the

The old aic7xxx driver seems to be broken. Whenever possible use the new
AIC7xxx driver. It works perfect here.

-- 
Andreas Theofilu
http://www.TheosSoft.net
E-Mail: andreas at TheosSoft dot net

Re: problem booting aic7xxx-old with reiserfs

[martin f krafft]

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

also sprach Andreas Theofilu <noreply@TheosSoft.net> [2004.01.06.0941 +0100]:
> The old aic7xxx driver seems to be broken. Whenever possible use
> the new AIC7xxx driver. It works perfect here.

I tried that, but at first, the driver spat out thousands of lines
of errors before the kernel failed to mount the root filesystem, and
then upon reboot, I still got various errors related to SCSI. When
I looked in the description of the aic7xxx drivers, I only found the
294x covered by the old driver.

I'll try again, I guess...

-- 
martin;              (greetings from the heart of the sun.)
  \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck
 
invalid/expired pgp subkeys? use subkeys.pgp.net as keyserver!
 
microsoft windoze - the best solitaire game you can buy.

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

Re: problem booting aic7xxx-old with reiserfs

[martin f krafft]

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

also sprach martin f krafft <madduck@madduck.net> [2004.01.06.0947 +0100]:
> I tried that, but at first, the driver spat out thousands of lines
> of errors before the kernel failed to mount the root filesystem, and
> then upon reboot, I still got various errors related to SCSI. When
> I looked in the description of the aic7xxx drivers, I only found the
> 294x covered by the old driver.

I tried the new driver again, and there were no thousand lines.
However, I did get error messages:

  scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.35
          <Adaptec 2940 Ultra SCSI adapter>
          aic7880: Ultra Single Channel A, SCSI Id=7, 16/253 SCBs

  scsi0:A:0:0: DV failed to configure device.  Please file a bug report against th
  is driver.
  (scsi0:A:1): 20.000MB/s transfers (20.000MHz, offset 15)
  (scsi0:A:0): 20.000MB/s transfers (20.000MHz, offset 15)
    Vendor: QUANTUM   Model: FIREBALL ST4.3S   Rev: 0F0C
    Type:   Direct-Access                      ANSI SCSI revision: 02
  scsi0:A:0:0: Tagged Queuing enabled.  Depth 32
    Vendor: NEC       Model: CD-ROM DRIVE:465  Rev: 1.03
    Type:   CD-ROM                             ANSI SCSI revision: 02
    Vendor: PHILIPS   Model: CDD2600           Rev: 1.07
    Type:   CD-ROM                             ANSI SCSI revision: 02
  SCSI device sda: 8519216 512-byte hdwr sectors (4362 MB)
  SCSI device sda: drive cache: write through
  sda: sda1 sda2 sda3 < sda5 sda6 sda7 >
  Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
  sr0: scsi3-mmc drive: 14x/32x cd/rw xa/form2 cdda tray
  Uniform CD-ROM driver Revision: 3.12
  Attached scsi CD-ROM sr0 at scsi0, channel 0, id 1, lun 0
  sr1: scsi-1 drive
  Attached scsi CD-ROM sr1 at scsi0, channel 0, id 2, lun 0
  Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0,  type 0
  Attached scsi generic sg1 at scsi0, channel 0, id 1, lun 0,  type 5
  Attached scsi generic sg2 at scsi0, channel 0, id 2, lun 0,  type 5

It says I should file a bug report. First, I'd like to investigate
this on this mailing list.

Do you have a clue what this is about? The system seems to boot
fine, and it appears to be working.

Thanks,

-- 
martin;              (greetings from the heart of the sun.)
  \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck
 
invalid/expired pgp subkeys? use subkeys.pgp.net as keyserver!
 
"when in doubt, parenthesize. at the very least it will let some
 poor schmuck bounce on the % key in vi."
                                                         -- larry wall

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

Re: problem booting aic7xxx-old with reiserfs

[Justin T. Gibbs]

> I tried the new driver again, and there were no thousand lines.
> However, I did get error messages:
> 
>   scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.35
>           <Adaptec 2940 Ultra SCSI adapter>
>           aic7880: Ultra Single Channel A, SCSI Id=7, 16/253 SCBs
> 
>   scsi0:A:0:0: DV failed to configure device.  Please file a bug report
>   against this driver.

This means that Domain Validation was unable to probe the your Quantum
Fireball correctly.  For me to understand why, you need to compile
the driver with debugging enabled and the debug mask set to 0x3F.
Both of these settings can be performed via the standard kernel
configuration tools.  Just boot with those settings and send me the
complete boot output.  You may need to increase the size of your dmesg
buffer for all of the output to be recorded.

--
Justin

Re: problem booting aic7xxx-old with reiserfs

[martin f krafft]

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

Justin <gibbs@scsiguy.com> wrote:
> This means that Domain Validation was unable to probe the your
> Quantum Fireball correctly.  For me to understand why, you need to
> compile the driver with debugging enabled and the debug mask set
> to 0x3F. Both of these settings can be performed via the standard
> kernel configuration tools.  Just boot with those settings and
> send me the complete boot output.  You may need to increase the
> size of your dmesg buffer for all of the output to be recorded.

Thanks, I will try that and let you know. Please keep me on this
thread CC as I can't read the list.

Thanks,

-- 
martin;              (greetings from the heart of the sun.)
  \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck
 
invalid/expired pgp subkeys? use subkeys.pgp.net as keyserver!
 
when compared to windoze, unix is an operating system.

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

Re: problem booting aic7xxx-old with reiserfs

[martin f krafft]

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

also sprach Justin T. Gibbs <gibbs@scsiguy.com> [2004.01.06.1748 +0100]:
> This means that Domain Validation was unable to probe the your
> Quantum Fireball correctly.  For me to understand why, you need to
> compile the driver with debugging enabled and the debug mask set
> to 0x3F. Both of these settings can be performed via the standard
> kernel configuration tools.  Just boot with those settings and
> send me the complete boot output.  You may need to increase the
> size of your dmesg buffer for all of the output to be recorded.

With debug level to 0x3f (decimal 63) and debugging code enabled,
the resulting boot messages are captured here:

  ftp://ftp.madduck.net/scratch/dmesg-aic7xxx-debug.gz [3.5 Kb]

Another peculiarity: if I soft reset the machine from within 2.6.0
and then start 2.6.0 again, it gets stuck again after the

  found reiserfs format "3.6" with standard journal

message, this time logging furiously to the console. I will verify
this again and let it run forever (with maximum kernel buffer size)
in the hope that you can do something with that too. You'll hear
from me.

Thanks for your time.

-- 
martin;              (greetings from the heart of the sun.)
  \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck
 
invalid/expired pgp subkeys? use subkeys.pgp.net as keyserver!
 
"alle vorurteile kommen aus den eingeweiden."
                                                 - friedrich nietzsche

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

Re: problem booting aic7xxx-old with reiserfs

[martin f krafft]

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

also sprach Justin T. Gibbs <gibbs@scsiguy.com> [2004.01.06.2105 +0100]:
> My bad.  The debug level needs to be 0x7f to get the output I need.
> Can you run the test again?

Please find the updated version here:

  ftp://ftp.madduck.net/scratch/dmesg-aix7xxx-debug-0x7f.gz

Thank you!

-- 
martin;              (greetings from the heart of the sun.)
  \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck
 
invalid/expired pgp subkeys? use subkeys.pgp.net as keyserver!
 
"if one cannot enjoy reading a book over and over again,
 there is no use in reading it at all."
                                                        -- oscar wilde

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

problem booting aic7xxx-old with reiserfs

[martin f krafft]

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

[please CC me on replies!]

Hi all,

I just tried to migrate my 200million year old router/firewall
machine to 2.6.0 without much success. The machine is a K6/200 with
an Adaptec 2940 controlling a Quantum Fireball drive, with an ext3
/boot partition. The whole thing is connected to the external
network with a 3c509 and the internal network with a RTL8139. The
machine works just fine with kernel 2.4.23, grsecurity and freeswan.
The configuration is here: [1].

I configured the 2.6.0 kernel [2] with the old aic7xxx driver, as well
as the 3c59x and 8139too drivers. Now, when I start the system, it
loads the kernel just fine, the SCSI driver recognises the
harddrive, but when it tries to mount / (reiserfs) (right after
initialising TCP, GRE, IPsec, IPv6 and SCTP), it just hangs with the
following message:

  found reiserfs format "3.6" with standard journal

This will stay for a couple of minutes, when the system finally
proceeds, coming to another hang after it told me that init is
booting.

I haven't gotten further than that yet. I imaging this is a problem
with the SCSI driver, but there are no errors logged, and in 2.4.23
it works just fine.

What is also curious is that after booting 2.6.0, if I don't
physically shut off and then restart the system, 2.4.23 can't seem
to communicate via eth0 (3c59x) anymore. It gives messages of the
following form:

  eth0: command 0x3002 did not complete! status=0xffff

and can't even obtain an IP address from the DHCP server. Only
physically powering off the system and starting it from zero will
fix this problem, allowing 2.4.23 to boot as normal.

I wonder if the two are related, but I don't think so. If I can boot
2.6.0, I couldn't care less about the 3c59x card, which is
apparently being configured by 2.6.0 in such a way that 2.4.23 can't
handle it.

Thus, I would be eternally grateful for hints as to why 2.6.0 causes
my system to hang. Thanks!

[please CC me on replies!]

  1. ftp://ftp.madduck.net/scratch/config-2.4.23-wall.gz [5.5 Kb]
  2. ftp://ftp.madduck.net/scratch/config-2.6.0-wall.gz [4.5 Kb]

-- 
martin;              (greetings from the heart of the sun.)
  \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck
 
invalid/expired pgp subkeys? use subkeys.pgp.net as keyserver!
 
"in a country where the sole employer is the state, opposition means
 death by slow starvation. the old principle: who does not work shall
 not eat, has been replaced by a new one: who does not obey shall not
 eat."
                                                 -- leon trotsky, 1937

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